From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Jan Beulich" <JBeulich@suse.com>
Cc: "Bjorn Helgaas" <bjorn.helgaas@hp.com>, <linux-pci@vger.kernel.org>
Subject: Re: [PATCH] PCI/IO-APIC: allow PCI_IOAPIC to be user configurable on x86
Date: Mon, 5 Dec 2011 11:28:54 -0800 [thread overview]
Message-ID: <20111205112854.10aceb75@jbarnes-desktop> (raw)
In-Reply-To: <4ED49EEA0200007800063F75@nat28.tlf.novell.com>
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
On Tue, 29 Nov 2011 07:59:22 +0000
"Jan Beulich" <JBeulich@suse.com> wrote:
> This adjusts PCI_IOAPIC to be user configurable (possibly as a module)
> on x86, since the base architecture code for adding IO-APICs
> dynamically isn't there yet (and hence having the code present
> everywhere is pretty pointless).
>
> To make this consistent, a MODULE_DEVICE_TABLE() declaration gets
> added, the class specifications get corrected (by properly using
> PCI_DEVICE_CLASS() intended for purposes like this), and the probe and
> remove functions get their sections adjusted.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
> Cc: Bjorn Helgaas <bjorn.helgaas@hp.com>
>
Oooh, fancy. Should go through the x86 tree though since the APIC code
is really x86 specific (and they're the experts in that anyway).
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-12-05 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 7:59 [PATCH] PCI/IO-APIC: allow PCI_IOAPIC to be user configurable on x86 Jan Beulich
2011-12-05 19:28 ` Jesse Barnes [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-06 7:49 Jan Beulich
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=20111205112854.10aceb75@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=JBeulich@suse.com \
--cc=bjorn.helgaas@hp.com \
--cc=linux-pci@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).