From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jan Kiszka <jan.kiszka@web.de>
Subject: qemu vs. kvm: When to flush the coalesced mmio buffer?
Date: Mon, 03 Jan 2011 13:11:32 +0100
Message-ID: <4D21BCF4.6020904@web.de>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enig3FDDCC10E43ABAE0508E56A9"
To: kvm <kvm@vger.kernel.org>, qemu-devel <qemu-devel@nongnu.org>
Return-path: <kvm-owner@vger.kernel.org>
Received: from fmmailgate01.web.de ([217.72.192.221]:48301 "EHLO
	fmmailgate01.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751908Ab1ACMLe (ORCPT <rfc822;kvm@vger.kernel.org>);
	Mon, 3 Jan 2011 07:11:34 -0500
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig3FDDCC10E43ABAE0508E56A9
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

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


--------------enig3FDDCC10E43ABAE0508E56A9
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.15 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/

iEYEARECAAYFAk0hvPQACgkQitSsb3rl5xRGeQCgyghB42YErbtqIPhlW2ZbkmHn
sRQAn2bSu+fFOZk48UsFMA6fQ3WWBVI2
=6Mgk
-----END PGP SIGNATURE-----

--------------enig3FDDCC10E43ABAE0508E56A9--