All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
	Sander Eikelenboom <linux@eikelenboom.it>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH 0 of 4] Add commands to automatically prep devices for pass-through
Date: Thu, 10 May 2012 12:15:33 -0400	[thread overview]
Message-ID: <20120510161533.GC3215@phenom.dumpdata.com> (raw)
In-Reply-To: <1336659417.14220.4.camel@zakaz.uk.xensource.com>

> > > Fully hiding the device from dom0 drivers generally seems like it is
> > > always better. That way the first driver to try and touch the hardware
> > > is the one inside the domU. This avoids issues with dom0 drivers setting
> > > stuff up but not tearing it down in a way that domU can cope with and
> > > makes the use of hardware which doesn't support FLR more reliable etc.
> > 
> > Haven't checked it (haven't got the time right now) but:
> > Is using wildcards in the BDF's on the commandline supported already
> > (like the ones supported in the config files for domains)
> 
> Based on a quick scan of the code it doesn't appear so, I don't maintain
> PCI backthough so there might be something in the pipeline.
> 
> > I tend to have quite long commandlines to hide a pci-e card with 8
> > functions (needed to specify 8 BDF's seperatly) for pci passthrough,
> > would be nice if one could just specify 09:00.* for example.
> 
> It sounds useful to me.

Patches are most welcome :-)

  reply	other threads:[~2012-05-10 16:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 10:28 [PATCH 0 of 4] Add commands to automatically prep devices for pass-through George Dunlap
2012-05-09 10:28 ` [PATCH 1 of 4] libxl: Make a helper function write a BDF to a sysfs path George Dunlap
2012-05-10 10:40   ` Ian Campbell
2012-05-09 10:28 ` [PATCH 2 of 4] libxl: Rename pci_list_assignable to pci_assignable_list George Dunlap
2012-05-10 10:43   ` Ian Campbell
2012-05-10 10:54     ` George Dunlap
2012-05-09 10:28 ` [PATCH 3 of 4] libxl: Introduce pci_assignable_add and pci_assignable_remove George Dunlap
2012-05-10 11:19   ` Ian Campbell
2012-05-10 14:55     ` George Dunlap
2012-05-10 15:04       ` Ian Campbell
2012-05-10 16:29         ` George Dunlap
2012-05-10 16:45           ` Ian Campbell
2012-05-09 10:28 ` [PATCH 4 of 4] xl: Add pci_assignable_add and remove commands George Dunlap
2012-05-10 11:31   ` Ian Campbell
2012-05-11 11:13     ` George Dunlap
2012-05-11 11:19       ` Ian Campbell
2012-05-11 12:50         ` George Dunlap
2012-05-11 12:58           ` Ian Campbell
2012-05-09 10:49 ` [PATCH 0 of 4] Add commands to automatically prep devices for pass-through Ian Campbell
2012-05-09 11:03   ` George Dunlap
2012-05-09 11:59     ` Ian Campbell
2012-05-09 13:45       ` George Dunlap
2012-05-10 10:17         ` George Dunlap
2012-05-10 10:38           ` Ian Campbell
2012-05-10 14:12             ` Sander Eikelenboom
2012-05-10 14:16               ` Ian Campbell
2012-05-10 16:15                 ` Konrad Rzeszutek Wilk [this message]
2012-05-09 10:56 ` David Vrabel
2012-05-09 11:11   ` George Dunlap

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=20120510161533.GC3215@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xen.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.