public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Greg KH <gregkh@suse.de>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	"Hans J. Koch" <hjk@linutronix.de>,
	anthony@codemonkey.ws, avi@redhat.com, kvm@vger.kernel.org,
	chrisw@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv5] uio: add generic driver for PCI 2.3 devices
Date: Mon, 20 Jul 2009 16:15:42 -0700	[thread overview]
Message-ID: <20090720161542.25dcddb4@jbarnes-g45> (raw)
In-Reply-To: <20090720195536.GA30483@suse.de>

On Mon, 20 Jul 2009 12:55:36 -0700
Greg KH <gregkh@suse.de> wrote:

> On Mon, Jul 20, 2009 at 10:52:27PM +0300, Michael S. Tsirkin wrote:
> > On Mon, Jul 20, 2009 at 09:09:43PM +0200, Hans J. Koch wrote:
> > > On Mon, Jul 20, 2009 at 10:29:34AM +0300, Michael S. Tsirkin
> > > wrote:
> > > > This adds a generic uio driver that can bind to any PCI
> > > > device.  First user will be virtualization where a qemu
> > > > userspace process needs to give guest OS access to the device.
> > > > 
> > > > Interrupts are handled using the Interrupt Disable bit in the
> > > > PCI command register and Interrupt Status bit in the PCI status
> > > > register.  All devices compliant to PCI 2.3 (circa 2002) and
> > > > all compliant PCI Express devices should support these bits.
> > > > Driver detects this support, and won't bind to devices which do
> > > > not support the Interrupt Disable Bit in the command register.
> > > > 
> > > > It's expected that more features of interest to virtualization
> > > > will be added to this driver in the future. Possibilities are:
> > > > mmap for device resources, MSI/MSI-X, eventfd (to interface
> > > > with kvm), iommu.
> > > 
> > > Thanks for adding the docs! Looks alright to me.
> > > 
> > > Thanks,
> > > Hans
> > > 
> > > > 
> > > > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> > > > Acked-by: Chris Wright <chrisw@redhat.com>
> > > 
> > > Signed-off-by: Hans J. Koch <hjk@linutronix.de>
> > 
> > Jesse just acked this patch in a private mail, as well.
> > Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>
> 
> Odd, but ok...

I just replied to Michael's off-list forward of some of the thread that
I missed, I'm not trying to hide anything. :)

Move along, nothing to see here...

-- 
Jesse Barnes, Intel Open Source Technology Center

      reply	other threads:[~2009-07-20 23:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20  7:29 [PATCHv5] uio: add generic driver for PCI 2.3 devices Michael S. Tsirkin
2009-07-20 19:09 ` Hans J. Koch
2009-07-20 19:52   ` Michael S. Tsirkin
2009-07-20 19:55     ` Greg KH
2009-07-20 23:15       ` 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=20090720161542.25dcddb4@jbarnes-g45 \
    --to=jbarnes@virtuousgeek.org \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=gregkh@suse.de \
    --cc=hjk@linutronix.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@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