|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH] MTRR: clear DramModEn bit of sys_cfg MSR
Sorry for the indention issue... I agree that it is better to move check-and_fixup code to init_amd() function. See the new patch. My understanding is that RdMem and WrMem are never going to become 1: BIOS are supposed to set sys_cfg[DramModEn] bit to 0 before OS takes over. As a result, RdMem and WrMem are read as 0 in fixed MTRRs. Unless Xen turn these bits to 1 (which I don't see from the code), k8_enable_fixed_iorrs() is useless. My 2nd patch removes k8_enable_fixed_iorrs(). If you have concern, we don't have to apply this patch. But I don't think we shouldn't move it to amd.c. k8_enable_fixed_iorrs() is unrelated in that file. Thanks, -Wei On 04/05/2011 06:51 AM, Keir Fraser wrote: On 04/04/2011 23:23, "Wei Huang"<wei.huang2@xxxxxxx> wrote:Some buggy BIOS might set sys_cfg DramModEn bit to 1, which can cause unexpected behavior on AMD platforms. This patch clears DramModEn bit. The patch was derived from upstream kernel patch (see https://patchwork.kernel.org/patch/11425/). Attachment:
amd_fix_syscfg.txt Attachment:
amd_remove_k8_enable_fixed_iorrs.txt _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |