From: Ingo Molnar <mingo@elte.hu>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-kernel@vger.kernel.org,
the arch/x86 maintainers <x86@kernel.org>,
Arjan van de Ven <arjan@infradead.org>,
Yinghai Lu <yhlu.kernel@gmail.com>,
greg@kroah.com
Subject: Re: [bug] PCI hotplug, ibmphp_access_ebda: WARNING: at arch/x86/mm/ioremap.c:182 __ioremap_caller+0x2d1/0x340()
Date: Thu, 31 Jul 2008 13:29:28 +0200 [thread overview]
Message-ID: <20080731112928.GC24030@elte.hu> (raw)
In-Reply-To: <200807281531.32640.jbarnes@virtuousgeek.org>
* Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> On Saturday, July 26, 2008 6:15 am Ingo Molnar wrote:
> > FYI, -tip testing triggered the new warning below on a testbox. I
> > suspect it's related to recent commits in drivers/pci/hotplug/.
> > I'm wondering, why does a driver map the EBDA? That's a really lowlevel
> > thing.
>
> AFAICT, this driver digs around in there for hotplug controller
> configuration (cc'ing Greg since he appears to be one of the original
> authors). It's a custom platform driver too, that may be the only
> method available there. Is there a shadow copy of the EDBA somewhere
> we should be using instead?
not that i know of, but it could be provided i guess. Enumerating and
making all hw configuration data available reliably would be a plus i
guess.
Ingo
prev parent reply other threads:[~2008-07-31 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 13:15 [bug] PCI hotplug, ibmphp_access_ebda: WARNING: at arch/x86/mm/ioremap.c:182 __ioremap_caller+0x2d1/0x340() Ingo Molnar
2008-07-28 22:31 ` Jesse Barnes
2008-07-29 4:26 ` Greg KH
2008-07-31 11:29 ` Ingo Molnar [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080731112928.GC24030@elte.hu \
--to=mingo@elte.hu \
--cc=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
--cc=yhlu.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.