public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jesse.barnes@intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Greg KH <greg@kroah.com>,
	jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org,
	kvm@vger.kernel.org
Subject: Re: [PATCH RFC] pci: expose function reset capability in sysfs
Date: Tue, 28 Jul 2009 09:56:58 -0700	[thread overview]
Message-ID: <20090728095658.57d62dd3@jbarnes-g45> (raw)
In-Reply-To: <20090727203748.GA30817@redhat.com>

On Mon, 27 Jul 2009 23:37:48 +0300
"Michael S. Tsirkin" <mst@redhat.com> wrote:

> On Mon, Jul 27, 2009 at 09:14:23AM -0700, Greg KH wrote:
> > Fine with me.  You forgot the documentation though :)
> 
> This enough?
> 
> pci: expose function reset capability in sysfs
> 
> Some devices allow an individual function to be reset without
> affecting other functions in the same device: that's what
> pci_reset_function does. For devices that have this support, expose
> reset attribite in sysfs.
> 
> This is useful e.g. for virtualization, where a qemu userspace
> process wants to reset the device when the guest is reset,
> to emulate machine reboot as closely as possible.
> 
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>

Applied to my linux-next branch, thanks.

-- 
Jesse Barnes, Intel Open Source Technology Center

      parent reply	other threads:[~2009-07-28 16:57 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
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 [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:
  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=20090728095658.57d62dd3@jbarnes-g45 \
    --to=jesse.barnes@intel.com \
    --cc=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