All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: "Hans J. Koch" <hjk@linutronix.de>,
	anthony@codemonkey.ws, avi@redhat.com, kvm@vger.kernel.org,
	chrisw@redhat.com, gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv4] uio: add generic driver for PCI 2.3 devices
Date: Mon, 20 Jul 2009 21:19:19 +0300	[thread overview]
Message-ID: <20090720181919.GA18747@redhat.com> (raw)
In-Reply-To: <20090720101702.68fee1ab@jbarnes-g45>

On Mon, Jul 20, 2009 at 10:17:02AM -0700, Jesse Barnes wrote:
> On Wed, 15 Jul 2009 23:39:11 +0200
> "Hans J. Koch" <hjk@linutronix.de> wrote:
> 
> > On Wed, Jul 15, 2009 at 11:13:40PM +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.
> > 
> > Well, I'm not enough of a PCI expert to tell whether your 2.3-test
> > works or not (can it have side effects, e.g. trigger an interrupt
> > when you toggle that bit?). I've added Jesse Barnes to Cc: since you
> > modify a PCI core header file. If there are no objections from the
> > PCI people, I guess we can take this.
> 
> pci_reg.h portion looks fine to me, and only supporting devices with
> the interrupt disable bit certainly simplifies things.  There were some
> other questions on the thread though (like Greg's similar driver); not
> sure if you've answered those yet.

Yes, and Greg seems satisfied :). See 20090716181919.GB27811@suse.de.
Chris Wright (author of pci-stub that was mentioned) also acked the
patch.

> -- 
> Jesse Barnes, Intel Open Source Technology Center

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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 20:13 [PATCHv4] uio: add generic driver for PCI 2.3 devices Michael S. Tsirkin
2009-07-15 21:39 ` Hans J. Koch
2009-07-20 17:17   ` Jesse Barnes
2009-07-20 18:19     ` Michael S. Tsirkin [this message]
2009-07-15 22:08 ` Greg KH
2009-07-16 12:31   ` Michael S. Tsirkin
2009-07-16 13:33     ` Sheng Yang
2009-07-16 13:50       ` Michael S. Tsirkin
2009-07-16 18:19     ` Greg KH
2009-07-16 14:07   ` Michael S. Tsirkin
2009-07-16 15:12     ` Hans J. Koch
2009-07-16 15:52       ` Greg KH
2009-07-16 17:03         ` Michael S. Tsirkin
2009-07-16 18:18           ` Greg KH

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=20090720181919.GA18747@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=gregkh@suse.de \
    --cc=hjk@linutronix.de \
    --cc=jbarnes@virtuousgeek.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.