[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAE9FiQW3eWkds12GSg2TStREEeAmAYmZ=ZRieOTZBOB3Z56iQA@mail.gmail.com>
Date: Tue, 15 Jul 2014 17:56:02 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>,
Fabio Coatti <fabio.coatti@...il.com>,
Stephane Eranian <eranian@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
"ak@...ux.intel.com" <ak@...ux.intel.com>,
"Yan, Zheng" <zheng.z.yan@...el.com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>
Subject: Re: WARNING: CPU: 2 PID: 1 at arch/x86/mm/ioremap.c:171 __ioremap_caller+0x290/0x2fa()
On Tue, Jul 15, 2014 at 4:54 PM, H. Peter Anvin <hpa@...or.com> wrote:
> On 07/15/2014 04:40 PM, Yinghai Lu wrote:
> We could quirk it, but we would have to make bloody darn sure that we
> don't break any systems because of unusual configuration and so on.
>
> I agree that we need to treat fixed resources as equivalent to reserved.
> This is also a BIOS bug (it should reserve the whole region), but that
> happens far too frequently. I don't know if we have any way to do that
> without massive surgery to the current code, though.
Should be similar to early_gart_iommu_check(), even less code.
Yinghai
--
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