All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
	Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>,
	Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
	MUNEDA Takahiro <muneda.takahiro@jp.fujitsu.com>
Subject: Re: [PATCH v1] PCI hotplug: move IOAPIC support from acpiphp to ioapic driver
Date: Mon, 28 Sep 2009 10:21:17 +0900	[thread overview]
Message-ID: <4AC00F8D.7000008@jp.fujitsu.com> (raw)
In-Reply-To: <20090926032424.30285.4832.stgit@bob.kio>

Bjorn Helgaas wrote:
> This patch moves PCI I/O APIC support from acpiphp to a separate driver.
> 
> Like pciehp and shpchp, acpiphp handles PCI hotplug, i.e., addition and
> removal of PCI adapters.  But in addition, acpiphp handles some ACPI
> hotplug, such as the addition of new host bridges, and the I/O APIC
> support was tangled up with that.
> 
> I don't think the I/O APIC support needs to be in acpiphp; PCI I/O APICs
> usually appear as a function on a PCI host bridge, and we'll enumerate the
> APIC before any of the devices behind the bridge that use it.
> 
> As far as I know, nobody actually uses I/O APIC hotplug.  It depends on
> acpi_register_ioapic(), which is only implemented for ia64, and I don't
> think any vendors have supported I/O chassis hotplug yet.
> 
> Kenji-san, I think this new file needs a Fujitsu copyright, but there
> wasn't one in acpiphp_glue to copy.  If you send me one, I'll put it
> in the next version of this patch.
> 

Looks good to me. 

Reviewed-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>

And here is Fujitsu copyright (thank you for asking me about that).

Copyright (C) 2009 Fujitsu Limited.

Thanks,
Kenji Kaneshige

      reply	other threads:[~2009-09-28  1:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-26  3:24 [PATCH v1] PCI hotplug: move IOAPIC support from acpiphp to ioapic driver Bjorn Helgaas
2009-09-28  1:21 ` Kenji Kaneshige [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=4AC00F8D.7000008@jp.fujitsu.com \
    --to=kaneshige.kenji@jp.fujitsu.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=kristen.c.accardi@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=muneda.takahiro@jp.fujitsu.com \
    --cc=takeuchi_satoru@jp.fujitsu.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.