All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: kvm <kvm@vger.kernel.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: qemu vs. kvm: When to flush the coalesced mmio buffer?
Date: Mon, 03 Jan 2011 13:11:32 +0100	[thread overview]
Message-ID: <4D21BCF4.6020904@web.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 305 bytes --]

Hi again,

another subtle difference between qemu-kvm and upstream:

When we leave the guest for an IO window (KVM_RUN returns EINTR or
EAGAIN), we call kvm_flush_coalesced_mmio_buffer in qemu-kvm but not in
upstream. When version is better? I can't find any rationales in both
git logs.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@web.de>
To: kvm <kvm@vger.kernel.org>, qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] qemu vs. kvm: When to flush the coalesced mmio buffer?
Date: Mon, 03 Jan 2011 13:11:32 +0100	[thread overview]
Message-ID: <4D21BCF4.6020904@web.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 305 bytes --]

Hi again,

another subtle difference between qemu-kvm and upstream:

When we leave the guest for an IO window (KVM_RUN returns EINTR or
EAGAIN), we call kvm_flush_coalesced_mmio_buffer in qemu-kvm but not in
upstream. When version is better? I can't find any rationales in both
git logs.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

             reply	other threads:[~2011-01-03 12:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03 12:11 Jan Kiszka [this message]
2011-01-03 12:11 ` [Qemu-devel] qemu vs. kvm: When to flush the coalesced mmio buffer? Jan Kiszka
2011-01-03 12:25 ` Gleb Natapov
2011-01-03 12:25   ` Gleb Natapov
2011-01-03 12:32 ` Avi Kivity
2011-01-03 12:32   ` [Qemu-devel] " Avi Kivity
2011-01-03 12:34   ` Jan Kiszka
2011-01-03 12:34     ` [Qemu-devel] " Jan Kiszka

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=4D21BCF4.6020904@web.de \
    --to=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.