From: Paul Ionescu <i_p_a_u_l-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Cc: linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [RFC/PATCH 0/3] ACPI based I/O APIC hot-plug
Date: Tue, 26 Apr 2005 17:03:26 +0300 [thread overview]
Message-ID: <pan.2005.04.26.14.03.23.413590@yahoo.com> (raw)
In-Reply-To: 4267AD0E.3080006@jp.fujitsu.com
Hi Kenji,
On Thu, 21 Apr 2005 22:39:26 +0900, Kenji Kaneshige wrote:
> 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.
Any plans for i386 implementation ?
>
> - 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
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-04-26 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 10:20 ` Kenji Kaneshige
2005-04-26 10:35 ` Andrew Morton
2005-04-26 15:07 ` Kenji Kaneshige
2005-04-26 14:03 ` Paul Ionescu [this message]
[not found] ` <pan.2005.04.26.14.03.23.413590-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
2005-04-26 14:34 ` 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=pan.2005.04.26.14.03.23.413590@yahoo.com \
--to=i_p_a_u_l-/e1597as9lqavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-ia64-u79uwXL29TY76Z2rM5mHXA@public.gmane.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