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: Fri, 10 Oct 2008 08:49:13 +0200 [thread overview]
Message-ID: <48EEFAE9.4010606@redhat.com> (raw)
In-Reply-To: <200810101046.48480.sheng@linux.intel.com>
Sheng Yang wrote:
> Yeah, I think the condition I mentioned is a example of yours. But in fact
> it's difficult to get a optimize value... I think it's possible that qemu may
> access all memory it owned, if so, no guest mtrr would affect. But how can we
> tell qemu would access which region of memory? We know it for vram, but any
> other cases? Seems it's indeed a big potential problem... If we want to do
> this, maybe we can hack something into host cache consistent check, though
> it's pretty dirty and got limit usage...
>
>
qemu will access all of memory, for example during live migration.
So we need to distinguish between RAM and mmio somehow.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-10-10 6:49 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 ` [PATCH 0/6] MTRR/PAT support for EPT (v3) Avi Kivity
2008-10-09 9:26 ` Sheng Yang
2008-10-09 10:12 ` Avi Kivity
2008-10-10 2:46 ` Sheng Yang
2008-10-10 6:49 ` Avi Kivity [this message]
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=48EEFAE9.4010606@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 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.