From: David Vrabel <david.vrabel@citrix.com>
To: Boris Ostrovsky <boris.ostrovsky@amd.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [PATCH] AMD: Enable WC+ memory type on family 10 processors
Date: Thu, 17 Jan 2013 18:57:12 +0000 [thread overview]
Message-ID: <50F84988.60100@citrix.com> (raw)
In-Reply-To: <1963e398ba0f5dd61818.1358448243@linux-vgzc.amd.com>
On 17/01/13 18:44, Boris Ostrovsky wrote:
> AMD: Enable WC+ memory type on family 10 processors
>
> In some cases BIOS may not enable WC+ memory type on family 10 processors,
> instead converting what would be WC+ memory to CD type. On guests using
> nested pages this could result in performance degradation. This patch
> enables WC+.
>
> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@amd.com>
>
> diff -r b6195e277da5 -r 1963e398ba0f xen/arch/x86/cpu/amd.c
> --- a/xen/arch/x86/cpu/amd.c Wed Jan 16 14:15:44 2013 +0000
> +++ b/xen/arch/x86/cpu/amd.c Thu Jan 17 08:38:34 2013 -0500
> @@ -495,6 +495,18 @@ static void __devinit init_amd(struct cp
> set_bit(X86_FEATURE_ARAT, c->x86_capability);
>
> /*
> + * On family 10h BIOS may not have properly enabled WC+ support, causing
> + * it to be converted to CD memtype. This may result in performance
> + * degradation for certain nested-paging guests. Prevent this conversion
> + * by enabling WC+ support through MSRC001_1024A[24] = 0
This register in the comment doesn't seem to agree with the one used below.
> + */
> + if (c->x86 == 0x10) {
> + rdmsr_safe(0xc001102a, value);
> + value &= ~(1ULL << 24);
> + wrmsr_safe(0xc001102a, value);
> + }
David
prev parent reply other threads:[~2013-01-17 18:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 18:44 [PATCH] AMD: Enable WC+ memory type on family 10 processors Boris Ostrovsky
2013-01-17 18:50 ` Andrew Cooper
2013-01-17 18:53 ` Mats Petersson
2013-01-17 18:57 ` David Vrabel [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=50F84988.60100@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@amd.com \
--cc=xen-devel@lists.xen.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.