All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Ian Campbell <Ian.Campbell@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: RFC: Automatically making a PCI device assignable in the config file
Date: Wed, 10 Jul 2013 15:48:00 +0100	[thread overview]
Message-ID: <51DD7420.5050803@eu.citrix.com> (raw)
In-Reply-To: <20957.26468.175816.677766@mariner.uk.xensource.com>

On 10/07/13 14:53, Ian Jackson wrote:
> George Dunlap writes ("RFC: Automatically making a PCI device assignable in the config file"):
>> I've been doing some work to try to make driver domains easier to set
>> up and use.  At the moment, in order to pass a device through to a
>> guest, you first need to assign it to pciback.  This involves doing
>> one of three things:
>> * Running xl pci-assignable-add for the device
>> * Specifying the device to be grabbed on the dom0 Linux command-line
>> * Doing some hackery in /etc/modules.d
>>
>> None of these are very satisfying.  What I think would be better is if
>> there was a way to specify in the guest config file, "If device X is
>> not assignable, try to make it assignable".  That way you can have a
>> driver domain grab the appropriate device just by running "xl create
>> domnet"; and once we have the xendomains script up and running with
>> xl, you can simply configure your domnet appropriately, and then put
>> it in /etc/xen/auto, to be started automatically on boot.
>>
>> My initial idea was to add a parameter to the pci argument in the
>> config file; for example:
>>
>> pci = ['08:04.1,permissive=1,seize=1']
>>
>> The 'seize=1' would indicate that if bdf 08:04.1 is not already
>> assignable, that xl should try to make is assignable.
> I think it's a design error that this isn't done automatically by
> default.
>
> It would be nice if there was a safety check that the device isn't
> currently in use by dom0, but I don't think it's essential.  We could
> just put a note in the docs saying "if you specify your dom0 nic it
> will go away, duh" or something.

I think it's a really bad interface decision if a simple typo might 
result in you yanking out your disk.

But in any case, if you think libxl_pci_attach() should automatically 
grab the device, that makes things a lot easier.  I'll write up a patch 
to add a "seize" flag and that will be that.

  -George

  reply	other threads:[~2013-07-10 14:48 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-05 11:01 RFC: Automatically making a PCI device assignable in the config file George Dunlap
2013-07-05 13:39 ` Andrew Cooper
2013-07-05 13:45   ` George Dunlap
2013-07-05 13:48     ` Andrew Cooper
2013-07-05 13:52       ` George Dunlap
2013-07-08 19:23         ` Konrad Rzeszutek Wilk
2013-07-09 12:52           ` George Dunlap
2013-07-09 14:25             ` Konrad Rzeszutek Wilk
2013-07-09 16:38               ` George Dunlap
2013-07-10 13:45                 ` Stefano Stabellini
2013-07-10 13:49               ` Stefano Stabellini
2013-07-10 13:55     ` Ian Jackson
2013-07-10 14:45       ` George Dunlap
2013-07-10 15:12         ` Gordan Bobic
2013-07-10 15:29           ` George Dunlap
2013-07-10 15:37             ` Gordan Bobic
2013-07-10 13:53 ` Ian Jackson
2013-07-10 14:48   ` George Dunlap [this message]
2013-07-11 11:35     ` David Vrabel
2013-07-12  9:36       ` George Dunlap
2013-07-12  9:55         ` David Vrabel
2013-07-12 10:32           ` George Dunlap
2013-07-12 13:10         ` Ian Jackson
2013-07-12 13:48           ` Konrad Rzeszutek Wilk
2013-07-12 14:43             ` Ian Jackson
2013-07-12 15:01               ` Konrad Rzeszutek Wilk
2013-07-12 15:09                 ` George Dunlap
2013-07-12 16:02                   ` Konrad Rzeszutek Wilk
2013-07-12 16:08                     ` George Dunlap
2013-07-12 14:44             ` Sander Eikelenboom

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=51DD7420.5050803@eu.citrix.com \
    --to=george.dunlap@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --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.