Re: [Qemu-devel] [RFC PATCH 1/1] s390x/css: unresrict cssids

[Halil Pasic <pasic@linux.vnet.ibm.com>]

On 11/24/2017 05:15 PM, Cornelia Huck wrote:
>>> In theory this should work. 
>>>
>>> In reality it seems more complicated. A per-device property is easy and can be
>>> inspected on the command line (e.g. -device virtio-blk-ccw,help), while a new 
>>> machine property would require to change the qemu help output and qemu-options 
>>> file (which makes it visible for all architectures).  
>> And then we have the fun of describing, that this property is weird, and can
>> not be set, and it's value does not matter.
> Well, that's the case for both, no?


I don't think we have to document _device_ properites in qemu-options.hx
I don't see any documented neither for virtio-ccw nor for vfio-ccw. The
machine properties, on the contrary, are documented in this file.
> 
> (Unless we simply make this a "default cssid" prop after all - then it
> would be more than just a simple indication for libvirt...)
> 

We are now talking about the "cssid-unrestricted" property. The default
cssid is not something I would like to do any time soon.