summaryrefslogtreecommitdiff
path: root/net/x25/x25_out.c
diff options
context:
space:
mode:
authorIlia Mirkin <imirkin@alum.mit.edu>2017-01-19 22:56:30 -0500
committerBen Skeggs <bskeggs@redhat.com>2017-01-31 20:05:26 +1000
commit24bf7ae359b8cca165bb30742d2b1c03a1eb23af (patch)
tree6aeadac4a9dee3adc155b2bf65a72cdc8e1e2ed4 /net/x25/x25_out.c
parentd347583a39e2df609a9e40c835f72d3614665b53 (diff)
drm/nouveau/nv1a,nv1f/disp: fix memory clock rate retrieval
Based on the xf86-video-nv code, NFORCE (NV1A) and NFORCE2 (NV1F) have a different way of retrieving clocks. See the nv_hw.c:nForceUpdateArbitrationSettings function in the original code for how these clocks were accessed. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=54587 Cc: stable@vger.kernel.org Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu> Signed-off-by: Ben Skeggs <bskeggs@redhat.com>
Diffstat (limited to 'net/x25/x25_out.c')
0 files changed, 0 insertions, 0 deletions
se the offending pages to be claimed so they are no longer used in future tasks. SIGKILL is used to ensure that the process does not try to coredump and result in an attempt to read the memory again from within kernel space. Although there is a HV call to scrub the memory (mem_scrub), there is no easy way to guarantee that the real memory address(es) are not used by other tasks. Clearing the error with mem_scrub would zero the memory and cause the other processes to proceed with bad data. The handling of other non-resumable errors remain unchanged and will cause a panic. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/testing/selftests/powerpc/primitives')