From: Chris Wright <chrisw@sous-sol.org>
To: Greg KH <greg@kroah.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Mark McLoughlin <markmc@redhat.com>, kvm <kvm@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Chris Wright <chrisw@redhat.com>,
"Dugger, Donald D" <donald.d.dugger@intel.com>,
"Kay, Allen M" <allen.m.kay@intel.com>
Subject: Re: [PATCH] pci: add remove_id sysfs entry
Date: Mon, 23 Feb 2009 17:26:25 -0800 [thread overview]
Message-ID: <20090224012625.GA7436@sequoia.sous-sol.org> (raw)
In-Reply-To: <20090214033319.GA4591@kroah.com>
* Greg KH (greg@kroah.com) wrote:
> On Fri, Feb 13, 2009 at 06:12:44PM -0800, Chris Wright wrote:
> > This adds a remove_id sysfs entry to allow users of new_id to later
> > remove the added dynid. One use case is management tools that want to
> > dynamically bind/unbind devices to pci-stub driver while devices are
> > assigned to KVM guests. Rather than having to track which driver was
> > originally bound to the driver, a mangement tool can simply:
> >
> > # echo "8086 10f5" > /sys/bus/pci/drivers/pci-stub/new_id
>
> As you're adding a new sysfs file, can you please document it in
> Documentation/ABI? I know the original bind and unbind files aren't
> documented there, they were created before the ABI/ directory showed up.
>
> It would be nice to add them as well if anyone wants to :)
Sure, I'll take a stab at that.
next prev parent reply other threads:[~2009-02-24 1:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 16:32 KVM PCI device assignment issues Mark McLoughlin
2009-02-13 16:56 ` Greg KH
2009-02-13 17:06 ` Mark McLoughlin
2009-02-13 17:36 ` Matthew Wilcox
2009-02-13 18:22 ` Chris Wright
2009-02-13 19:47 ` Chris Wright
2009-02-24 9:20 ` Zhao, Yu
2009-02-14 2:12 ` [PATCH] pci: add remove_id sysfs entry Chris Wright
2009-02-14 3:33 ` Greg KH
2009-02-24 1:26 ` Chris Wright [this message]
2009-02-24 2:17 ` [PATCH 1/2] PCI: add some sysfs ABI docs Chris Wright
2009-02-24 2:18 ` [PATCH 2/2] PCI: add remove_id sysfs entry Chris Wright
2009-02-24 3:47 ` Greg KH
2009-02-24 5:33 ` Chris Wright
2009-02-24 5:43 ` Greg KH
2009-02-24 3:47 ` [PATCH 1/2] PCI: add some sysfs ABI docs Greg KH
2009-02-24 5:08 ` Chris Wright
2009-02-24 5:50 ` [PATCH 1/2 v2] " Chris Wright
2009-02-24 5:52 ` [PATCH 2/2 v2] PCI: add remove_id sysfs entry Chris Wright
2009-02-26 5:37 ` Han, Weidong
2009-02-27 0:27 ` Chris Wright
2009-03-20 0:35 ` Jesse Barnes
2009-02-24 17:37 ` [PATCH 1/2 v2] PCI: add some sysfs ABI docs 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=20090224012625.GA7436@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=allen.m.kay@intel.com \
--cc=chrisw@redhat.com \
--cc=donald.d.dugger@intel.com \
--cc=greg@kroah.com \
--cc=kvm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=markmc@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