public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Tom Lyon <pugs@lyon-about.com>
Cc: Avi Kivity <avi@redhat.com>, Greg KH <gregkh@suse.de>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Hans J. Koch" <hjk@linutronix.de>
Subject: Re: [PATCH 0/1] uio_pci_generic: extensions to allow access for?non-privileged processes
Date: Fri, 9 Apr 2010 13:09:08 -0700	[thread overview]
Message-ID: <20100409200908.GM3168@sequoia.sous-sol.org> (raw)
In-Reply-To: <201004090934.16891.pugs@lyon-about.com>

* Tom Lyon (pugs@lyon-about.com) wrote:
> On Friday 09 April 2010 02:58:19 am Avi Kivity wrote:
> > - access to all config space, but BARs must be translated so userspace 
> > cannot attack the host
> Please elaborate. All of PCI config? All of PCIe config? Seems like a huge mess.

All of config space, but not raw access to all bits.  So the MSI/MSI-X
capability writes need to be intermediated.  There's bits in the
header too.  And it's not just PCI, it's extended config space as well,
drivers may care about finding their whizzybang PCIe capability and doing
someting with it (and worse...they are allowed to put device specific
registers there, and worse yet...they do!).

thanks,
-chris

  parent reply	other threads:[~2010-04-09 20:09 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01  0:08 [PATCH 0/1] uio_pci_generic: extensions to allow access for non-privileged processes Tom Lyon
2010-04-01  0:12 ` [PATCH 1/1] " Tom Lyon
2010-04-09  9:08   ` Joerg Roedel
2010-04-09 16:27     ` Tom Lyon
2010-04-01  9:09 ` [PATCH 0/1] " Avi Kivity
2010-04-01 15:39   ` Tom Lyon
2010-04-01 15:54     ` Avi Kivity
2010-04-01 16:06       ` Tom Lyon
2010-04-01 16:10         ` Avi Kivity
2010-04-01 19:24           ` Tom Lyon
2010-04-01 20:21             ` Joerg Roedel
2010-04-02  6:43             ` Avi Kivity
2010-04-02 17:05               ` Greg KH
2010-04-09  9:58                 ` Avi Kivity
2010-04-09 16:34                   ` Tom Lyon
2010-04-09 16:48                     ` [PATCH 0/1] uio_pci_generic: extensions to allow access for?non-privileged processes Joerg Roedel
2010-04-09 17:43                     ` [PATCH 0/1] uio_pci_generic: extensions to allow access for non-privileged processes Avi Kivity
2010-04-09 20:09                     ` Chris Wright [this message]
2010-04-09 20:05                   ` Chris Wright
2010-04-01 21:27       ` Tom Lyon
2010-04-02  6:44         ` Avi Kivity
2010-04-01 12:52 ` Joerg Roedel
2010-04-01 15:40   ` Tom Lyon
2010-04-01 16:07     ` Joerg Roedel
2010-04-01 19:18       ` Tom Lyon
2010-04-01 20:09         ` Joerg Roedel
2010-04-01 14:25 ` Michael S. Tsirkin
2010-04-01 16:02   ` Tom Lyon
2010-04-01 16:57   ` Joerg Roedel
2010-04-01 19:08 ` Hans J. Koch

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=20100409200908.GM3168@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=avi@redhat.com \
    --cc=gregkh@suse.de \
    --cc=hjk@linutronix.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pugs@lyon-about.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