From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pciehp: Handle interrupts that happen during initialization.
Date: Fri, 20 Feb 2009 15:18:23 +0900 [thread overview]
Message-ID: <499E4B2F.9070607@jp.fujitsu.com> (raw)
In-Reply-To: <m1hc2s5dyp.fsf@fess.ebiederm.org>
Eric W. Biederman wrote:
> Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com> writes:
>
>> In the current pciehp implementation, minimum resources enough to
>> enable devices under the bridge are assigned when P2P bridge is
>> hot-added. My concern is that enough resources are NOT assigned to
>> the bridge if an additional slot is empty. As a result, hot-add
>> adapter card on the additional slot won't work because of resource
>> shortage.
>
> It is a good concern. Right now I know I won't need a bus number
> but you are quite right the mmio and iospace may be a problem.
>
> My preliminary test case doesn't cover that so I will look and
> confirm it is a problem I need to address.
>
>>> kobject_name is not initialized, and slot_name(p_slot) calls
>>> hoptlug_slot_name which calls pci_slot_name which kobj_name.
>>> It looks like this problem was introduced in commit
>>> e1acb24f059defdaa0264e925f19cc21b0a3e592
>> Thank your for the information. I understood what is happening.
>> This needs to be fixed. But, as I mentioned before, I think
>> software notification mechanism should be initialized before
>> sysfs entries are created. I'll consider alternative fix.
>
> Reasonable. I haven't had the need nor gotten brave enough to
> support those sysfs entries in my minimal driver.
>
Eric-san, Jesse-san,
I tried to make alternative fix, but now I have a conclusion that
Eric-san's patch is the best solution. The reasons are
- Eric-san's approach prevents the regression such as commit
e1acb24f059defdaa0264e925f19cc21b0a3e592.
- My concern was that command completion might not be handled if
we enable software notification mechanism after creating sysfs
entries. But it is not true because pciehp uses polling approach
if command is issued before enabling software notification (I
made it, but I forgot it...). Just in case, I confirmed that
hotplug operations (power on/off, attention indication on/off
and so on) works even if I make pciehp_init_notification() NOP.
Jesse-san, could you consider applying Eric-san's patch?
Here are my
Reviewed-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Tested-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Note: I tested Eric-san's patch on Jesse-san's for-linus tree.
Thanks,
Kenji Kaneshige
next prev parent reply other threads:[~2009-02-20 6:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 3:31 [PATCH] pciehp: Handle interrupts that happen during initialization Eric W. Biederman
2009-01-29 7:34 ` Kenji Kaneshige
2009-02-13 19:29 ` Jesse Barnes
2009-02-14 4:06 ` Eric W. Biederman
2009-02-14 12:53 ` Eric W. Biederman
2009-02-14 14:56 ` Eric W. Biederman
2009-02-16 8:02 ` Kenji Kaneshige
2009-02-17 23:17 ` Eric W. Biederman
2009-02-18 5:48 ` Kenji Kaneshige
2009-02-23 11:08 ` Eric W. Biederman
2009-02-24 17:05 ` Jesse Barnes
2009-02-24 17:08 ` Jesse Barnes
2009-02-16 8:00 ` Kenji Kaneshige
2009-02-18 0:40 ` Eric W. Biederman
2009-02-18 7:12 ` Kenji Kaneshige
2009-02-18 8:47 ` Eric W. Biederman
2009-02-20 6:18 ` Kenji Kaneshige [this message]
2009-02-23 11:17 ` Eric W. Biederman
2009-02-24 17:38 ` Jesse Barnes
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=499E4B2F.9070607@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=ebiederm@xmission.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--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