From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Eyal Moscovici <eyal.moscovici@oracle.com>,
kvm@vger.kernel.org, idan.brown@oracle.com,
Krish Sadhukhan <krish.sadhukhan@oracle.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [PATCH] KVM: x86: Allow suppressing prints on RDMSR/WRMSR of unhandled MSRs
Date: Fri, 10 Nov 2017 22:41:58 +0100 [thread overview]
Message-ID: <20171110214157.GH2189@flask> (raw)
In-Reply-To: <68f28ae7-23ec-f2a0-0a51-865a0c17ab52@redhat.com>
2017-11-09 19:30+0100, Paolo Bonzini:
> On 09/11/2017 16:22, Radim Krčmář wrote:
> > 2017-11-08 14:32+0200, Eyal Moscovici:
> >> 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>
> >> ---
> >> arch/x86/kvm/x86.c | 17 +++++++++++++----
> >> 1 file changed, 13 insertions(+), 4 deletions(-)
> >>
> >> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> >> index 03869eb..21c0059 100644
> >> --- a/arch/x86/kvm/x86.c
> >> +++ b/arch/x86/kvm/x86.c
> >> @@ -107,6 +107,9 @@
> >> static bool __read_mostly ignore_msrs = 0;
> >> module_param(ignore_msrs, bool, S_IRUGO | S_IWUSR);
> >>
> >> +static bool __read_mostly suppress_ignore_msrs_prints = false;
> >> +module_param(suppress_ignore_msrs_prints, bool, S_IRUGO | S_IWUSR);
> >
> > What about calling it 'print_ignored_msrs' and default to true?
>
> Makes sense! s/print/report/ perhaps?
s/suppress_ignore_msrs_prints/report_ignored_msrs/ and applied, thanks.
prev parent reply other threads:[~2017-11-10 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 12:32 [PATCH] KVM: x86: Allow suppressing prints on RDMSR/WRMSR of unhandled MSRs Eyal Moscovici
2017-11-08 13:11 ` Paolo Bonzini
2017-11-09 8:15 ` Eyal Moscovici
2017-11-09 9:51 ` Paolo Bonzini
2017-11-09 15:22 ` Radim Krčmář
2017-11-09 18:30 ` Paolo Bonzini
2017-11-10 21:41 ` Radim Krčmář [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171110214157.GH2189@flask \
--to=rkrcmar@redhat.com \
--cc=eyal.moscovici@oracle.com \
--cc=idan.brown@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=krish.sadhukhan@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox