On 17/02/17 04:10, Vipin K Parashar wrote: > kvm_ppc_mmu_book3s_32/64 xlat() logs "KVM can't copy data" error > upon failing to copy user data to kernel space. This floods kernel > log once such fails occur in short time period. Ratelimit this > error to avoid flooding kernel logs upon copy data failures. > > Signed-off-by: Vipin K Parashar <vipin@xxxxxxxxxxxxxxxxxx> > --- What causes the flooding, can it be triggered on demand from user space? I presume you'll need to have permissions to /dev/kvm to trigger it? Could you clarify the scope, is it just called during emulation with KVM_PR? Balbir Singh.
