From: Anish Patel <anish.mailing.list@gmail.com>
To: Keir Fraser <keir.xen@gmail.com>
Cc: Wei Huang <wei.huang2@amd.com>,
"'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Check AMD SYSCFG DramModEn bit for MTRR configuration
Date: Wed, 02 Mar 2011 10:20:15 -0500 [thread overview]
Message-ID: <4D6E602F.6010309@gmail.com> (raw)
In-Reply-To: <C9939BDE.1406A%keir.xen@gmail.com>
Buggy BIOSes are more common than you think. especially from small
shops, and some times they don't tend to release BIOS updates for their
platforms.
On 03/02/11 02:01, Keir Fraser wrote:
> On 01/03/2011 21:11, "Wei Huang"<wei.huang2@amd.com> wrote:
>
>> This patch checks whether SYSCFG DramModEn bit is clear by BIOS. Some
>> buggy BIOS might set this bit to 1, which causes unexpected behavior on
>> AMD platforms. This patch also increase family check for AMD CPUs when
>> setting fixed MTRR ranges.
> How common are these buggy BIOSes? Can't we just get users to update their
> BIOS?
>
> -- Keir
>
>> Signed-off-by: Wei Huang<wei.huang2@amd.com>
>>
>>
>> PS: If OK, please apply it to both xen-4.1 and xen-4.0 trees.
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2011-03-02 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 21:11 [PATCH] Check AMD SYSCFG DramModEn bit for MTRR configuration Wei Huang
2011-03-02 0:52 ` Huang2, Wei
2011-03-02 7:01 ` Keir Fraser
2011-03-02 15:20 ` Anish Patel [this message]
2011-03-02 17:25 ` Wei Huang
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=4D6E602F.6010309@gmail.com \
--to=anish.mailing.list@gmail.com \
--cc=keir.xen@gmail.com \
--cc=wei.huang2@amd.com \
--cc=xen-devel@lists.xensource.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.