[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <478FBBA9.4070300@zytor.com>
Date: Thu, 17 Jan 2008 15:33:45 -0500
From: "H. Peter Anvin" <hpa@...or.com>
To: Ingo Molnar <mingo@...e.hu>
CC: Andreas Herrmann3 <andreas.herrmann3@....com>,
Venki Pallipadi <venkatesh.pallipadi@...el.com>, ak@....de,
ebiederm@...ssion.com, rdreier@...co.com,
torvalds@...ux-foundation.org, gregkh@...e.de, airlied@...net.ie,
davej@...hat.com, tglx@...utronix.de, akpm@...ux-foundation.org,
arjan@...radead.org, jesse.barnes@...el.com, davem@...emloft.net,
linux-kernel@...r.kernel.org, suresh.b.siddha@...el.com
Subject: Re: [patch 0/4] x86: PAT followup - Incremental changes and bug fixes
Ingo Molnar wrote:
> * Andreas Herrmann3 <andreas.herrmann3@....com> wrote:
>
>> For the failed devices I get:
>>
>> sata_sil 0000:00:12.0: version 2.3
>> ACPI: PCI Interrupt 0000:00:12.0[A] -> GSI 22 (level, low) -> IRQ 22
>> ioremap_nocache: addr c0403000, size 200
>> swapper:1 conflicting cache attribute c0403000-c0404000 uncached<->default
>> ACPI: PCI interrupt for device 0000:00:12.0 disabled
>
> hm, is the problem that the two devices share the same physical page,
> and thus get an overlapping area?
>
> as an intermediate fix, how about following the attribute of the already
> existing mapping, instead of rejecting the ioremap due to the conflict?
> I.e. something like below?
The correct behaviour probably would be to go with the most restrictive
caching behaviour, i.e. uncached in this case.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists