xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Joanna Rutkowska <joanna@invisiblethingslab.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: pciback: question about the permissive flag
Date: Wed, 7 Jul 2010 11:18:51 -0400	[thread overview]
Message-ID: <20100707151851.GA12092@phenom.dumpdata.com> (raw)
In-Reply-To: <4C33A217.3050006@invisiblethingslab.com>

On Tue, Jul 06, 2010 at 11:37:27PM +0200, Joanna Rutkowska wrote:
> I'm trying to understand the purpose of the permissive flag in the Xen
> pciback driver. The comments in the code suggest that setting
> permissive=1 is "potentially unsafe", and I've been wondering why?
> 
> My thinking goes this way -- we either:
> 
> 1) have IOMMU/VT-d in the system, and use it to isolate the device
> assigned to a DomU, in which case allowing the DomU to fully control the
> assigned device's config space should not be a problem because VT-d

But that is not the case. The PCI config writes are actually done by
Dom0. The Xen PCI frontend redirects all config space reads/writes to
the Xen PCI backend that does them on the guest behalf.

There are some backend-backend config space libs that deal with
different regions (power, MSI), and for those that are not present
the permissive flag is used to figure out whether the guest is allowed
to write to that region.

  parent reply	other threads:[~2010-07-07 15:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-06 21:37 pciback: question about the permissive flag Joanna Rutkowska
2010-07-07  6:32 ` Keir Fraser
2010-07-07 13:30   ` Ian Pratt
2010-07-07 14:05     ` Joanna Rutkowska
2010-07-07 15:28       ` Konrad Rzeszutek Wilk
2010-07-07 15:44       ` Ian Pratt
2010-07-07 21:41         ` Joanna Rutkowska
2010-07-07 22:51           ` Ian Pratt
2010-07-07 15:18 ` Konrad Rzeszutek Wilk [this message]
2010-07-07 21:23   ` Joanna Rutkowska
2010-07-09 14:09     ` Konrad Rzeszutek Wilk

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=20100707151851.GA12092@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=joanna@invisiblethingslab.com \
    --cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).