xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>,
	"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Cc: Keir Fraser <keir.xen@gmail.com>,
	eddie.dong@intel.com, "Nakajima, Jun" <jun.nakajima@intel.com>,
	Jan Beulich <JBeulich@suse.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH] pvh: change epte_get_entry_emt() for pvh mem types
Date: Fri, 22 Nov 2013 10:52:21 +0000	[thread overview]
Message-ID: <528F3765.8080806@eu.citrix.com> (raw)
In-Reply-To: <20131121170051.424971fd@mantra.us.oracle.com>

On 22/11/13 01:00, Mukesh Rathor wrote:
> For pvh guests, epte_get_entry_emt() is incorrectly returning WB for
> all mem types because of the following check:
>      if ( !v->domain->arch.hvm_domain.params[HVM_PARAM_IDENT_PT] )
> Skip the check for pvh guests.
>
> Also note, MTRR ranges are not maintained for pvh, and a solution is
> being contrived using PAT.
>
> Signed-off-by: Mukesh Rathor <mukesh.rathor@oracle.com>
> ---
>   xen/arch/x86/hvm/mtrr.c |    7 ++++++-
>   1 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/xen/arch/x86/hvm/mtrr.c b/xen/arch/x86/hvm/mtrr.c
> index 4ff1e55..5427e1c 100644
> --- a/xen/arch/x86/hvm/mtrr.c
> +++ b/xen/arch/x86/hvm/mtrr.c
> @@ -693,7 +693,8 @@ uint8_t epte_get_entry_emt(struct domain *d, unsigned long gfn, mfn_t mfn,
>            ((d->vcpu == NULL) || ((v = d->vcpu[0]) == NULL)) )
>           return MTRR_TYPE_WRBACK;
>   
> -    if ( !v->domain->arch.hvm_domain.params[HVM_PARAM_IDENT_PT] )
> +    if ( !is_pvh_vcpu(v) &&
> +         !v->domain->arch.hvm_domain.params[HVM_PARAM_IDENT_PT] )
>           return MTRR_TYPE_WRBACK;
>   
>       if ( !mfn_valid(mfn_x(mfn)) )
> @@ -717,6 +718,10 @@ uint8_t epte_get_entry_emt(struct domain *d, unsigned long gfn, mfn_t mfn,
>           return MTRR_TYPE_WRBACK;
>       }
>   
> +    /* MTRR ranges are not maintained for pvh. */
> +    if ( is_pvh_vcpu(v) )
> +        return MTRR_TYPE_WRBACK;
> +
>       gmtrr_mtype = get_mtrr_type(&v->arch.hvm_vcpu.mtrr, (gfn << PAGE_SHIFT));
>       hmtrr_mtype = get_mtrr_type(&mtrr_state, (mfn_x(mfn) << PAGE_SHIFT));
>       return ((gmtrr_mtype <= hmtrr_mtype) ? gmtrr_mtype : hmtrr_mtype);

So this will bypass the host mtrr settings, and always return WRBACK, 
even if in mtrr_state it was set to something lower. Presumably that 
"min(host,guest)" was there for a reason.  Are you sure it's safe to 
just ignore it?

This is why I suggested the following instead:

gmtrr_mtype = is_hvm_domain(v) ?
         get_mtrr_type(&v->arch.hvm_vcpu.mtrr, (gfn << PAGE_SHIFT)) :
         MTRR_TYPE_WRBACK;

  -George

  reply	other threads:[~2013-11-22 10:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22  1:00 [PATCH] pvh: change epte_get_entry_emt() for pvh mem types Mukesh Rathor
2013-11-22 10:52 ` George Dunlap [this message]
2013-11-22 11:03   ` George Dunlap
2013-11-22 12:05   ` Jan Beulich
2013-11-22 20:40     ` Mukesh Rathor

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=528F3765.8080806@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Xen-devel@lists.xensource.com \
    --cc=eddie.dong@intel.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir.xen@gmail.com \
    --cc=mukesh.rathor@oracle.com \
    --cc=roger.pau@citrix.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).