Re: [Xen-devel] RFC: Automatically making a PCI device assignable in the config file

[Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>]

On Fri, Jul 12, 2013 at 02:10:41PM +0100, Ian Jackson wrote:
> George Dunlap writes ("Re: [Xen-devel] RFC: Automatically making a PCI device 
> assignable in the config file"):
> > On Thu, Jul 11, 2013 at 12:35 PM, David Vrabel <david.vrabel@xxxxxxxxxx> 
> > wrot> > I don't think this proposal really helps with avoiding this.  I 
> > think
> > > most people will end up always adding 'seize=1' because to avoid having
> > > to do so means altering config files elsewhere and rebooting.
> > 
> > I guess what I'm worried about is the fact that we would be changing
> > things that are now "safe" to things that are not safe.  At the
> > moment, "xl pci-assignable-add" might yank out a system device if you
> > make a typo; but it was introduced that way, so people always had to
> > be careful.  But currently, "pci=[]" and "xl pci-attach" do *not*
> > behave that way; you have to make the device assignable first.  So you
> > don't need to be particularly careful.  Adding "seize" at least should
> > flag up to people that they need to double-check.
> > 
> > If people really object to the extra flag, I can write up a patch
> > without it, but I'd prefer to have something...
> 
> 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?

> 
> Ian.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel