summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorEyal Moscovici <eyal.moscovici@oracle.com>2017-11-08 14:32:08 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2017-11-17 13:20:16 +0100
commitfab0aa3b776f0a3af1db1f50e04f1884015f9082 (patch)
treed317c74ab1ff984ed5e69cdc24ba9a8e8be7e12f /drivers
parent4d772cb85f64c16eca00177089ecb3cd5d292120 (diff)
downloadlinux-fab0aa3b776f0a3af1db1f50e04f1884015f9082.tar.bz2
KVM: x86: Allow suppressing prints on RDMSR/WRMSR of unhandled MSRs
Some guests use these unhandled MSRs very frequently. This cause dmesg to be populated with lots of aggregated messages on usage of ignored MSRs. As ignore_msrs=true means that the user is well-aware his guest use ignored MSRs, allow to also disable the prints on their usage. An example of such guest is ESXi which tends to access a lot to MSR 0x34 (MSR_SMI_COUNT) very frequently. In addition, we have observed this to cause unnecessary delays to guest execution. Such an example is ESXi which experience networking delays in it's guests (L2 guests) because of these prints (even when prints are rate-limited). This can easily be reproduced by pinging from one L2 guest to another. Once in a while, a peak in ping RTT will be observed. Removing these unhandled MSR prints solves the issue. Because these prints can help diagnose issues with guests, this commit only suppress them by a module parameter instead of removing them from code entirely. Signed-off-by: Eyal Moscovici <eyal.moscovici@oracle.com> Reviewed-by: Liran Alon <liran.alon@oracle.com> Reviewed-by: Krish Sadhukhan <krish.sadhukhan@oracle.com> Signed-off-by: Krish Sadhukhan <krish.sadhukhan@oracle.com> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> [Changed suppress_ignore_msrs_prints to report_ignored_msrs - Radim] Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions