From: Greg KH <greg@kroah.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH RFC] pci: expose function reset capability in sysfs
Date: Mon, 27 Jul 2009 09:14:23 -0700 [thread overview]
Message-ID: <20090727161423.GC30241@kroah.com> (raw)
In-Reply-To: <20090727155238.GA29853@redhat.com>
On Mon, Jul 27, 2009 at 06:52:38PM +0300, Michael S. Tsirkin wrote:
> On Mon, Jul 27, 2009 at 08:01:46AM -0700, Greg KH wrote:
> > > + if (!pci_probe_reset_function(dev)) {
> > > + retval = device_create_file(&dev->dev, &reset_attr);
> > > + if (retval)
> > > + goto error;
> > > + }
> >
> > So you only add the file if there is a reset function, which is fine,
> > but later on:
> >
> > > @@ -1037,6 +1073,7 @@ static void pci_remove_capabilities_sysfs(struct pci_dev *dev)
> > > }
> > >
> > > pcie_aspm_remove_sysfs_dev_files(dev);
> > > + device_remove_file(&dev->dev, &reset_attr);
> >
> > You always remove the file, if it has been created or not. That could
> > cause problems in the future, please only remove a file if you have
> > actually added it to the sysfs tree.
> >
> > thanks,
> >
> > greg k-h
>
> OK. I think, however, that it's better to avoid probing the function
> on cleanup path just to figure out whether the file needs to be removed.
> Can this info be stored in struct pci_dev?
> Along the lines of:
Fine with me. You forgot the documentation though :)
thanks,
greg k-h
next prev parent reply other threads:[~2009-07-27 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 17:11 [PATCH RFC] pci: expose function reset capability in sysfs Michael S. Tsirkin
2009-07-27 15:01 ` Greg KH
2009-07-27 15:52 ` Michael S. Tsirkin
2009-07-27 16:14 ` Greg KH [this message]
2009-07-27 16:20 ` Jesse Barnes
2009-07-27 20:37 ` Michael S. Tsirkin
2009-07-27 21:03 ` Greg KH
2009-07-28 16:56 ` 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=20090727161423.GC30241@kroah.com \
--to=greg@kroah.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kvm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox