Re: [PATCH -mm] MMCONFIG: Fix x86_64 ioremap base_address

On Sat, 2006-12-23 at 10:02 +0900, OGAWA Hirofumi wrote:
> Current -mm's mmconfig has some problems of remapped range.
> 
> a) In the case of broken MCFG tables on Asus etc., we need to remap
> 256M range, but currently only remap 1M.


Hi,

I respectfully disagree. If the MCFG table is broken, we should not use
it AT ALL. It's either a correct table, and we can use it, or it's so
broken that we know it never has been tested etc etc, we're just better
of to not trust it in that case.

Greetings,
   Arjan van de Ven

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH -mm] MMCONFIG: Fix x86_64 ioremap base_address
    • From: OGAWA Hirofumi <[email protected]>

• References:
  • [PATCH -mm] MMCONFIG: Fix x86_64 ioremap base_address
    • From: OGAWA Hirofumi <[email protected]>

• Prev by Date: Re: Finding hardlinks
• Next by Date: Re: [patch] sched: improve sched_clock() on i686
• Previous by thread: [PATCH -mm] MMCONFIG: Fix x86_64 ioremap base_address
• Next by thread: Re: [PATCH -mm] MMCONFIG: Fix x86_64 ioremap base_address
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]