Re: [RFC - V2] - Mapping ACPI tables as CACHED

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/26/2010 10:17 AM, Jack Steiner wrote:
> Map ACPI tables as WB on x86_64. No substantive changes to IA64.
> 
> 
> Signed-off-by: Jack Steiner <steiner@xxxxxxx>
> 
> ---
> V2 - Change the patch to unconditionally map ACPI tables as WB on x86_64.
>      I'm still some paranoid about this because of the potential imapct on
>      some platforms with weird BIOSs. However, note that on EFI-enabled
>      systems (like UV), the ACPI tables are already mapped as WB memory.
>      This is done in the EFI function efi_enter_virtual_mode().
>      The ACPI code in acpi_os_map_memory() is not currently aware of the
>      EFI mapping & currently maps the memory as UC. This seems like a bug.
> 

I really think that it's all a consequence of the fact that ioremap()
became implicitly UC when we added PAT support (being the more
conservative choice.)

Len, want to take this one or should I?

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux