[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130528164801.GA2345@srcf.ucam.org>
Date: Tue, 28 May 2013 17:48:01 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Bjorn Helgaas <bhelgaas@...gle.com>
Cc: Matt Fleming <matt@...sole-pimps.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>,
Matt Fleming <matt.fleming@...el.com>,
Seth Forshee <seth.forshee@...onical.com>,
Jesse Barnes <jbarnes@...tuousgeek.org>, stable@...r.kernel.org
Subject: Re: [PATCH] x86/PCI: setup data may be in highmem
On Tue, May 28, 2013 at 10:31:51AM -0600, Bjorn Helgaas wrote:
> On Tue, May 28, 2013 at 5:36 AM, Matt Fleming <matt@...sole-pimps.org> wrote:
> > On Fri, 24 May, at 08:38:10AM, Bjorn Helgaas wrote:
> >> pcibios_add_device() is mostly called at boot-time, when
> >> early_ioremap() probably works well. But it's also called when we
> >> hot-add devices later, and it looks like early_ioremap() will then
> >> generate warnings because "system_state != SYSTEM_BOOTING".
> >
> > Oops. Good point. Is there any reason we can't use ioremap()?
>
> I assume Matthew had some reason for avoiding that in the first place,
> so I hope he'll chime in.
I have no recollection of why I did it that way. If this is all
happening late enough for ioremap() to work then that sounds fine.
--
Matthew Garrett | mjg59@...f.ucam.org
--
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