From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
David Vrabel <david.vrabel@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: Fri, 12 Jul 2013 11:01:38 -0400 [thread overview]
Message-ID: <20130712150138.GB3846@phenom.dumpdata.com> (raw)
In-Reply-To: <20960.5652.606227.862830@mariner.uk.xensource.com>
On Fri, Jul 12, 2013 at 03:43:32PM +0100, Ian Jackson wrote:
> Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] RFC: Automatically making a PCI device assignable in the config file"):
> > On Fri, Jul 12, 2013 at 02:10:41PM +0100, Ian Jackson wrote:
> > > I think at the very least there should be the ability to have it as a
> > > global config option.
> >
> > Like the seatbelt option or perhaps a better name 'expert' in the /etc/xl.conf?
>
> I was thinking "default.pci.seize" or something.
Why not combine this with the other - the one where you can call
'xl vpcu-set <guest> <huge number of VCPUs>' where the number of
VCPUs is greater than PCPUs. And if the 'expert' option is turned
on it will let you. If it is not, it will notify you about this
being a bad idea.
Which reminds me, I need to send a patch for that..
>
> Ian.
next prev parent reply other threads:[~2013-07-12 15:01 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
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 [this message]
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=20130712150138.GB3846@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=david.vrabel@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.