All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	xen-devel@lists.xenproject.org, Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] pv/pvh: disable MTRR feature on cpuid for Dom0
Date: Fri, 13 Dec 2013 12:55:51 +0100	[thread overview]
Message-ID: <52AAF5C7.1040408@citrix.com> (raw)
In-Reply-To: <52AAFD77020000780010CF49@nat28.tlf.novell.com>

On 13/12/13 12:28, Jan Beulich wrote:
>>>> On 12.12.13 at 17:52, Roger Pau Monne <roger.pau@citrix.com> wrote:
>> MTRR is not available for PV/PVH Dom0, so prevent cpuid from
>> reporting it as an available feature.
> 
> Some misunderstanding perhaps? PV certainly has MTRR support for
> Dom0 - see XENPF_*_memtype.

OK, my bad, I was looking for a PV implementation of struct mtrr_ops in
the pvops kernel, but Linux pvops doesn't use MTRR at all, also none of
the XENPF_*_memtype ops seem to be used.

>
>> --- a/xen/arch/x86/traps.c
>> +++ b/xen/arch/x86/traps.c
>> @@ -796,6 +796,7 @@ void pv_cpuid(struct cpu_user_regs *regs)
>>          __clear_bit(X86_FEATURE_DS, &d);
>>          __clear_bit(X86_FEATURE_ACC, &d);
>>          __clear_bit(X86_FEATURE_PBE, &d);
>> +        __clear_bit(X86_FEATURE_MTRR, &d);
> 
> Thus clearing this flag should be limited to PVH.

Will resend now with this fixed, thanks.

Roger.

      reply	other threads:[~2013-12-13 11:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12 16:52 [PATCH] pv/pvh: disable MTRR feature on cpuid for Dom0 Roger Pau Monne
2013-12-13 11:28 ` Jan Beulich
2013-12-13 11:55   ` Roger Pau Monné [this message]

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=52AAF5C7.1040408@citrix.com \
    --to=roger.pau@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=xen-devel@lists.xenproject.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 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.