Re: state of some x86 acpi patches

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

 



* Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:

> Andi Kleen wrote:
>> Jeremy Fitzhardinge <jeremy@xxxxxxxx> writes:
>>   
>>> However, unlike early_ioremap(), __acpi_map_table just maintains a
>>> single mapping which gets replaced each call, and has no corresponding
>>> unmap function.  Implement this by just removing the previous mapping
>>> each time its called.  Unfortunately, this will leave a stray mapping
>>> at the end.
>>>     
>>
>> Stray mappings are dangerous. They can lead to illegal cache aliases
>> later. Better avoid them.
>>
>> I guess ACPI could call a cleanup function after it's done with
>> all early mappings.
>>   
>
> Right.  But Yinghai (I think) went through and made all the acpi 
> mappings get properly mapped and unmapped, so my patch is moot.

yes, right.

	Ingo
--
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