public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Zlatko Calusic <zcalusic@bitsync.net>
Cc: kvm@vger.kernel.org
Subject: Re: kvm: zapping shadow pages for mmio generation wraparound
Date: Tue, 23 Jul 2013 13:50:21 +0200	[thread overview]
Message-ID: <51EE6DFD.6080701@redhat.com> (raw)
In-Reply-To: <51ED9CC0.9070405@bitsync.net>

Il 22/07/2013 22:57, Zlatko Calusic ha scritto:
> I'm getting a lot of these in kernel 3.11.0-rc1:
> 
> Jul 19 19:53:06 ps kernel: kvm: zapping shadow pages for mmio generation
> wraparound
> Jul 19 22:37:47 ps kernel: kvm: zapping shadow pages for mmio generation
> wraparound
> Jul 20 00:07:24 ps kernel: kvm: zapping shadow pages for mmio generation
> wraparound
> Jul 20 00:11:04 ps kernel: kvm: zapping shadow pages for mmio generation
> wraparound
> Jul 20 00:39:14 ps kernel: kvm: zapping shadow pages for mmio generation
> wraparound
> Jul 21 00:25:32 ps kernel: kvm: zapping shadow pages for mmio generation
> wraparound
> 
> There seems to be one line in the kernel log for every reboot of a WinXP
> guest, and I'm getting a bit bored with it. I don't understand what
> those messages mean? What can I do to stop them flooding the log?
> 
> Please Cc: (not subscribed)

The log message would let us correlate any reports with a new
optimization (added in 3.11).  We will probably downgrade it to
KERN_DEBUG before 3.11 goes out (or otherwise cause it to disappear), in
the meanwhile it's harmless.

Paolo


  reply	other threads:[~2013-07-23 11:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22 20:57 kvm: zapping shadow pages for mmio generation wraparound Zlatko Calusic
2013-07-23 11:50 ` Paolo Bonzini [this message]
2013-07-23 12:35   ` Zlatko Calusic
2014-12-21  6:28 ` Michael Tokarev
2014-12-21 16:13   ` Paolo Bonzini

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=51EE6DFD.6080701@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=zcalusic@bitsync.net \
    /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