block & iov_iter: use bvec iterator to implement iterate_bvec()
Hi Guys, The 1st two patches move bvec iterator helpers out from bio.h, then they can be used even if CONFIG_BLOCK is disabled, so not necessary to u
View Article[PATCH 1/4] block: move bvec iterator into include/linux/bvec_iter.h
bvec iterator helpers should be used to implement iterate_bvec():lib/iov_iter.c too, and this patch moves them into the new header, so that we can kee
View Article[PATCH 2/4] block: make 'struct bvec_iter' not depend on CONFIG_BLOCK
So that we can use bvec iterator to implement iterate_bvec(): lib/iov_iter.c. Signed-off-by: Ming Lei <ming.lei@canonical.com> --- include/linux/blk
View Article[PATCH 3/4] block: mark 1st parameter of bvec_iter_advance as const
bvec_iter_advance() only writes to the parameter of 'iter', so address of 'bvec' can be marked as const safely. Without the change, we can trigger co
View Article[PATCH 4/4] iov_iter: use bvec iterator to implement iterate_bvec()
bvec has provided one iterator already, so not necessary to invent a new wheel for this job. Signed-off-by: Ming Lei <ming.lei@canonical.com> --- li
View Article[PATCH 0/2] KVM: MMU: fix ept=0/pte.u=0/pte.w=0/CR0.WP=0/CR4.SMEP=1/EFER.NX=0
I found this while testing the permission_fault patch with ept=0. Paolo Bonzini (2): KVM: MMU: fix ept=0/pte.u=0/pte.w=0/CR0.WP=0/CR4.SMEP=1/EFER.N
View Article[PATCH 1/2] KVM: MMU: fix ept=0/pte.u=0/pte.w=0/CR0.WP=0/CR4.SMEP=1/EFER.NX=0...
Yes, all of these are needed. :) This is admittedly a bit odd, but kvm-unit-tests access.flat tests this if you run it with "-cpu host" and of course
View Article[PATCH 2/2] KVM: MMU: fix reserved bit check for...
KVM handles supervisor writes of a pte.u=0/pte.w=0/CR0.WP=0 page by setting U=0 and W=1 in the shadow PTE. This will cause a user write to fault and
View Article[PATCH 0/2] KVM: x86: disable MPX if host did not enable MPX XSAVE features
Patch 1 ensures that all aspects of MPX are disabled when eager FPU is disabled on the host. Patch 2 is just a cleanup. Paolo Bonzini (2): KVM: x8
View Article[PATCH 1/2] KVM: x86: disable MPX if host did not enable MPX XSAVE features
When eager FPU is disabled, KVM will still see the MPX bit in CPUID and presumably the MPX vmentry and vmexit controls. However, it will not be able
View Article[PATCH 2/2] KVM: x86: remove eager_fpu field of struct kvm_vcpu_arch
It is now equal to use_eager_fpu(), which simply tests a cpufeature bit. Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> --- arch/x86/include/asm
View Article[RFC PATCH 0/2] KVM: MMU: return page fault error code from permission_fault
Intel's new PKU extension introduces a bit of the page fault error code that must be dynamically computed after the PTE lookup (unlike I/D, U/S and W/
View Article[RFC PATCH 1/2] KVM: MMU: precompute page fault error code
For the next patch, we will want to filter PFERR_FETCH_MASK away early, and not pass it to permission_fault if neither NX nor SMEP are enabled. Prepar
View Article[RFC PATCH 2/2] KVM: MMU: return page fault error code from permission_fault
Intel's new PKU extension introduces a bit of the page fault error code that must be dynamically computed after the PTE lookup (unlike I/D, U/S and W/
View Article[PATCH 1/1] extcon: gpio: queue work only if debounce is NZ
Use queue_delayed_work only when debounce time is required to read gpio state properly, read the gpio state and set the extcon cable state in IRQ hand
View Article[PATCH 0/5] gpio: of: Add error handling and support for multiple gpio in...
This series enhance the error print by adding error number in print message, handle the error if gpio_hogd() fails and returns error to caller, and ad
View Article[PATCH 1/5] gpio: of: Scan available child node for gpio-hog
Look for child node which are available when iterating for gpio hog node for request/set GPIO initial configuration during OF gpio chip registration.
View Article[PATCH 2/5] gpio: gpiolib: Print error number if gpio hog failed
Print the error number of GPIO hog failed during its configurations. This helps in identifying the failure without instrumenting the code. Signed-off
View Article[PATCH 3/5] gpio: of: Return error if gpio hog configuration failed
If GPIO hog configuration failed while adding OF based gpiochip() then return the error instead of ignoring it. This helps of properly handling the g
View Article[PATCH 4/5] gpio: of: Add support to have multiple gpios in gpio-hog
The child node for gpio hogs under gpio controller's node provide the mechanism to automatic GPIO request and configuration as part of the gpio-contro
View Article
