From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: linux-pci@vger.kernel.org, jbarnes@virtuousgeek.org,
Alex Chiang <achiang@hp.com>,
djwong@us.ibm.com, Trent Piepho <xyzzy@speakeasy.org>,
linux-kernel@vger.kernel.org
Subject: Re: Q: state of pci express hotplug
Date: Sat, 31 Jan 2009 19:13:00 +0100 [thread overview]
Message-ID: <200901311913.00752.rjw@sisk.pl> (raw)
In-Reply-To: <m1fxj06js8.fsf@fess.ebiederm.org>
Hi Eric,
On Saturday 31 January 2009, Eric W. Biederman wrote:
>
> Trying to use the current pciehp code, on real hardware in an
> interesting topology (more later) I'm not finding it very satisfactory
> at all. I am up to at least three show stopper bugs and the code
> is not doing what I really need it to do, so I am looking at a significant
> rewrite patch effort to make this code usable.
>
> Am I unique in thinking there is a lot that needs to be done?
> Is there current work in progress to make the pci hotplug work better?
>
> I would like to avoid duplicate work if I can.
I've recently send some fixes against the PCIe port driver which is used by
PCIe hotplug. In particular, there's a fix that should make the thing work
with MSI-X.
Are your fixes specific to the hotplug driver or do they also affect the PCIe
port driver?
Rafael
next prev parent reply other threads:[~2009-01-31 18:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 7:01 Eric W. Biederman
2009-01-31 18:13 ` Rafael J. Wysocki [this message]
2009-02-02 2:19 ` Kenji Kaneshige
2009-02-02 17:15 ` Krishna Kothapalli
2009-02-03 0:51 ` Kenji Kaneshige
2009-02-03 20:48 ` Krishna Kothapalli
2009-02-04 2:32 ` Krishna Kothapalli
2009-02-04 5:51 ` Kenji Kaneshige
2009-02-04 18:17 ` Krishna Kothapalli
2009-02-04 19:40 ` Mark Lord
2009-02-04 23:49 ` Alex Chiang
2009-02-05 0:02 ` Kenji Kaneshige
2009-02-05 1:53 ` Krishna Kothapalli
2009-02-05 6:42 ` Kenji Kaneshige
2009-02-06 20:37 ` Krishna Kothapalli
2009-02-02 17:01 ` Alex Chiang
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=200901311913.00752.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=achiang@hp.com \
--cc=djwong@us.ibm.com \
--cc=ebiederm@xmission.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=xyzzy@speakeasy.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
Powered by JetHome