From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 0/6] MTRR/PAT support for EPT (v3)
Date: Thu, 09 Oct 2008 11:03:24 +0200 [thread overview]
Message-ID: <48EDC8DC.5050006@redhat.com> (raw)
In-Reply-To: <1223539317-32379-1-git-send-email-sheng@linux.intel.com>
Sheng Yang wrote:
> Hi, Avi
>
> Here is the latest update of MTRR/PAT support.
>
> Change from v2:
> Discard the using of MSR bitmap, add MSR_IA32_CR_PAT to save/restore, as well
> as rebase on latest upstream.
>
>
Applied all; my comments about shadow can be addressed later.
There is also the danger of the guest setting the wrong MTRR type for
RAM, thus introducing incompatible memory types (between qemu and the
guest). If this is a problem, we should ignore the guest's mtrr (and
pat) for RAM and use write-back instead.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2008-10-09 9:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 8:01 [PATCH 0/6] MTRR/PAT support for EPT (v3) Sheng Yang
2008-10-09 8:01 ` [PATCH 1/6] x86: Rename mtrr_state struct and macro names Sheng Yang
2008-10-09 8:01 ` [PATCH 2/6] x86: Export some definition of MTRR Sheng Yang
2008-10-09 8:01 ` [PATCH 3/6] KVM: Improve MTRR structure Sheng Yang
2008-10-09 8:01 ` [PATCH 4/6] KVM: VMX: Add PAT support for EPT Sheng Yang
2008-10-09 8:01 ` [PATCH 5/6] Add local get_mtrr_type() to support MTRR Sheng Yang
2008-10-09 8:01 ` [PATCH 6/6] Enable MTRR for EPT Sheng Yang
2008-10-09 8:44 ` Avi Kivity
2008-10-09 8:49 ` Sheng Yang
2008-10-09 9:03 ` Avi Kivity [this message]
2008-10-09 9:26 ` [PATCH 0/6] MTRR/PAT support for EPT (v3) Sheng Yang
2008-10-09 10:12 ` Avi Kivity
2008-10-10 2:46 ` Sheng Yang
2008-10-10 6:49 ` Avi Kivity
2008-10-10 7:16 ` Sheng Yang
2008-10-12 9:47 ` 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=48EDC8DC.5050006@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=sheng@linux.intel.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;
as well as URLs for NNTP newsgroup(s).