archive mirror
 help / color / mirror / Atom feed
From: Liu ping fan <>
To: Jiang Liu <>
	Scott Murray <>,
	Bjorn Helgaas <>
Subject: Re: pci: question about the life cycle of pci_dev and its parent pci_bus
Date: Mon, 27 Aug 2012 09:54:42 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Aug 24, 2012 at 10:30 PM, Jiang Liu <> wrote:
> Hi Pingfan,
>         We have realized the same when implementing lock mechanisms for PCI hotplug
> operations, and we are planning to holding a reference to parent bus for each pci dev.

Thanks! You save me from searching such codes.

>         Regards!
>         Gerry
> On 08/23/2012 01:24 PM, Liu ping fan wrote:
>> Hi,
>> I have a question about the life cycle of pci_dev and its parent pci_bus.
>> In pci_destroy_dev(), we remove the pci_dev from the bus_list, so
>> pci_dev is isolated from its parent pci_bus, and their life cycle are
>> independent too. But it seems that in pci_dev, we can still access the
>> pci_bus from the pointer pci_dev->bus.  To resolve such issue, I think
>> during the pci_dev removal,  there should be process to 1.prevent the
>> reader incoming 2. ensure the current reader has exit.  But can not
>> find them.
>> Could anyone tell me?
>> Thanx, pingfan
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to
>> More majordomo info at
>> Please read the FAQ at

      reply	other threads:[~2012-08-27  1:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-23  5:24 pci: question about the life cycle of pci_dev and its parent pci_bus Liu ping fan
2012-08-24 14:30 ` Jiang Liu
2012-08-27  1:54   ` Liu ping fan [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).