summaryrefslogtreecommitdiff
path: root/tools/testing/selftests/timers
diff options
context:
space:
mode:
authorJan Beulich <JBeulich@suse.com>2017-01-23 08:12:19 -0700
committerKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>2017-01-23 13:27:41 -0500
commitb32728ffef7f233dbdabb3f11814bdf692aaf501 (patch)
tree5bf0326545d0c4525a43f3c50cfcdef09f0baa88 /tools/testing/selftests/timers
parentd61b7f972dab2a7d187c38254845546dfc8eed85 (diff)
xen-blkfront: feature flags handling adjustments
Don't truncate the "feature-persistent" value read from xenstore: Any non-zero value is supposed to enable the feature, just like is already being done for feature_secdiscard. Just like the other feature_* fields, feature_flush and feature_fua are boolean flags, and hence fit well into a single bit. Keep all bit fields together to limit gaps. Signed-off-by: Jan Beulich <jbeulich@suse.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'tools/testing/selftests/timers')
0 files changed, 0 insertions, 0 deletions
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 'drivers/usb/host/ehci-spear.c')