From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Andrew Morton <akpm@osdl.org>, Len Brown <len.brown@intel.com>,
"Luck, Tony" <tony.luck@intel.com>, Greg KH <greg@kroah.com>,
acpi-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org,
pcihpd-discuss@lists.sourceforge.net
Subject: [RFC/PATCH 0/3] ACPI based I/O APIC hot-plug
Date: Thu, 21 Apr 2005 22:39:26 +0900 [thread overview]
Message-ID: <4267AD0E.3080006@jp.fujitsu.com> (raw)
Hi,
Here is a set of patches to support ACPI based I/O APIC hotplug. This
code consists of the following three patches.
- Add the new interfaces for I/O APIC hot-add/hot-remove. The
implementation of these interfaces depends on each architecture.
- IA64 implementation of above-mentioned interfeces for I/O APIC
hot-add/hot-remove.
- Add I/O APIC hot-add support to ACPIPHP dirver. PCI root bridge
hot-add will be fully functional with this patch. This will be
also needed to support hot-add of p2p bridge hierarchy that
contains I/O APICs. This code supports only hot-add for now.
These patches support I/O APIC hot-plug on ia64 only for now. These
are against 2.6.12-rc2-mm3.
Thanks,
Kenji Kaneshige
WARNING: multiple messages have this Message-ID (diff)
From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Andrew Morton <akpm@osdl.org>, Len Brown <len.brown@intel.com>,
"Luck, Tony" <tony.luck@intel.com>, Greg KH <greg@kroah.com>,
acpi-devel@lists.sourceforge.net, linux-ia64@vger.kernel.org,
pcihpd-discuss@lists.sourceforge.net
Subject: [RFC/PATCH 0/3] ACPI based I/O APIC hot-plug
Date: Thu, 21 Apr 2005 13:39:26 +0000 [thread overview]
Message-ID: <4267AD0E.3080006@jp.fujitsu.com> (raw)
Hi,
Here is a set of patches to support ACPI based I/O APIC hotplug. This
code consists of the following three patches.
- Add the new interfaces for I/O APIC hot-add/hot-remove. The
implementation of these interfaces depends on each architecture.
- IA64 implementation of above-mentioned interfeces for I/O APIC
hot-add/hot-remove.
- Add I/O APIC hot-add support to ACPIPHP dirver. PCI root bridge
hot-add will be fully functional with this patch. This will be
also needed to support hot-add of p2p bridge hierarchy that
contains I/O APICs. This code supports only hot-add for now.
These patches support I/O APIC hot-plug on ia64 only for now. These
are against 2.6.12-rc2-mm3.
Thanks,
Kenji Kaneshige
next reply other threads:[~2005-04-21 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 13:39 Kenji Kaneshige [this message]
2005-04-21 13:39 ` [RFC/PATCH 0/3] ACPI based I/O APIC hot-plug Kenji Kaneshige
2005-04-26 9:57 ` Andrew Morton
2005-04-26 9:57 ` Andrew Morton
2005-04-26 10:20 ` Kenji Kaneshige
2005-04-26 10:20 ` Kenji Kaneshige
2005-04-26 10:35 ` Andrew Morton
2005-04-26 10:35 ` Andrew Morton
2005-04-26 15:07 ` Kenji Kaneshige
2005-04-26 15:07 ` Kenji Kaneshige
2005-04-26 14:03 ` Paul Ionescu
2005-04-26 14:03 ` Paul Ionescu
[not found] ` <pan.2005.04.26.14.03.23.413590-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
2005-04-26 14:34 ` Kenji Kaneshige
2005-04-26 14:34 ` [ACPI] " Kenji Kaneshige
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=4267AD0E.3080006@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=pcihpd-discuss@lists.sourceforge.net \
--cc=tony.luck@intel.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.