From: Anthony Liguori <anthony@codemonkey.ws>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
KVM General <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH] QEMU kill CR3_CACHE references
Date: Fri, 19 Feb 2010 14:57:02 -0600 [thread overview]
Message-ID: <4B7EFB1E.1020806@codemonkey.ws> (raw)
In-Reply-To: <4B7E330C.4090302@redhat.com>
On 02/19/2010 12:43 AM, Jes Sorensen wrote:
> Hi,
>
> The CR3 caching was never implemented in QEMU and is obsoleted by
> NPT/EPT. This patch removes the unused references to it from
> target-i386/kvm.c.
Let's bring this through uq/master? Sound reasonable Marcelo?
Regards,
Anthony Liguori
> Cheers,
> Jes
>
next prev parent reply other threads:[~2010-02-19 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 6:43 [Qemu-devel] [PATCH] QEMU kill CR3_CACHE references Jes Sorensen
2010-02-19 9:46 ` [Qemu-devel] " Zachary Amsden
2010-02-19 20:57 ` Anthony Liguori [this message]
2010-02-21 9:41 ` Avi Kivity
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=4B7EFB1E.1020806@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Jes.Sorensen@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).