[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BEDDF87.4040309@zytor.com>
Date: Fri, 14 May 2010 16:40:55 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Jesse Barnes <jbarnes@...tuousgeek.org>
CC: Mike Travis <travis@....com>, Bjorn Helgaas <bjorn.helgaas@...com>,
Mike Habeck <habeck@....com>, Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>, x86@...nel.org,
Jacob Pan <jacob.jun.pan@...el.com>, Tejun Heo <tj@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Yinghai <yinghai.lu@...cle.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
Myron Stowe <myron.stowe@...com>
Subject: Re: [Patch 1/1] x86 pci: Add option to not assign BAR's if not already
assigned
On 05/14/2010 04:33 PM, Jesse Barnes wrote:
>
> As for BIOS coordination for dynamic reallocation, yeah there'd be some
> of that. I think the basic principles would be:
> 1) use BIOS allocations wherever possible
> 2) get an accurate list of available resources from the BIOS for
> potential remapping later
> 3) allocate resources for BARs and devices as late as possible (e.g.
> at driver bind time) to avoid allocating more than we need
>
> But that's a good chunk of work, and as we've seen, PCs in particular
> are really sensitive to having resources moved around too much, so step
> (2) is probably the hardest part.
>
The real problem that I see, as outlined before, has nothing to do with
the BIOS, but rather the interdependencies between resources.
-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