The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Tom Lyon <pugs@cisco.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org, randy.dunlap@oracle.com, arnd@arndb.de,
	joro@8bytes.org, hjk@linutronix.de, avi@redhat.com,
	gregkh@suse.de, chrisw@sous-sol.org, alex.williamson@redhat.com,
	mst@redhat.com
Subject: Re: [PATCH 0/3] VFIO V4: VFIO driver: Non-privileged user level PCI drivers
Date: Fri, 24 Sep 2010 10:17:29 -0700	[thread overview]
Message-ID: <20100924101729.6382a2c8@jbarnes-desktop> (raw)
In-Reply-To: <4c9a720d.kfMPk+Yyq+IUUwiw%pugs@cisco.com>

On Wed, 22 Sep 2010 14:15:57 -0700
Tom Lyon <pugs@cisco.com> wrote:

> After a long summer break, it's tanned, it's rested, and it's ready to rumble!
> 
> In this version:	*** REBASE to 2.6.35 ***
> 
> There's new code using generic netlink messages which allows the kernel
> to notify the user level of weird events and allows the user level to 
> respond. This is currently used to handle device removal (whether software
> or hardware driven), PCI error events, and system suspend & hibernate.
> 
> The driver now supports devices which use multiple MSI interrupts, reflecting
> the actual number of interrupts allocated by the system to the user level.
> 
> PCI config accesses are now done through the pci_user_{read,write)_config
> routines from drivers/pci/access.c.
> 

I really don't like to encourage user level drivers (in fact I've
actively tried to kill them in our graphics stack), but I do understand
that they're convenient in many scenarios.

So assuming you can convince someone to apply the VFIO framework, I'm
ok with exporting the user level accessor functions (after all, we
export them to userland already via sysfs, so exporting them as GPL
symbols to another module is fine).

So you can add my Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org> to
the PCI parts, but don't take it as an endorsement of VFIO in
general! :) 

-- 
Jesse Barnes, Intel Open Source Technology Center

      reply	other threads:[~2010-09-24 17:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-22 21:15 [PATCH 0/3] VFIO V4: VFIO driver: Non-privileged user level PCI drivers Tom Lyon
2010-09-24 17:17 ` 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=20100924101729.6382a2c8@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=alex.williamson@redhat.com \
    --cc=arnd@arndb.de \
    --cc=avi@redhat.com \
    --cc=chrisw@sous-sol.org \
    --cc=gregkh@suse.de \
    --cc=hjk@linutronix.de \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pugs@cisco.com \
    --cc=randy.dunlap@oracle.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