Re: [Xen-devel] [Xen-users] Xen 4.2 TODO (io and irq parameter are not evaluated by xl)

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 31.08.12 at 17:01, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> --- a/docs/man/xl.cfg.pod.5   Fri Aug 31 12:03:55 2012 +0100
> +++ b/docs/man/xl.cfg.pod.5   Fri Aug 31 15:54:42 2012 +0100
> @@ -402,6 +402,30 @@ for more information on the "permissive"
>  
>  =back
>  
> +=item B<ioports=[ "IOPORT_RANGE", "IOPORT_RANGE", ... ]>

Is this really with quotes, and requiring an array?

> +
> +=over 4
> +
> +Allow guest to access specific legacy I/O ports. Each B<IOPORT_RANGE>
> +is given in hexadecimal and may either a span e.g. C<2f8-2ff>
> +(inclusive) or a single I/O port C<2f8>.
> +
> +It is recommended to use this option only for trusted VMs under
> +administrator control.
> +
> +=back
> +
> +=item B<irqs=[ NUMBER, NUMBER, ... ]>

Similarly here - is this really requiring an array? I ask because
I had to look at this just last week for a colleague, and what
we got out of inspection of examples/code was that a simple
number (and a simple range without quotes above) are
permitted too.

Jan

> +
> +=over 4
> +
> +Allow a guest to access specific physical IRQs.
> +
> +It is recommended to use this option only for trusted VMs under
> +administrator control.
> +
> +=back
> +
>  =head2 Paravirtualised (PV) Guest Specific Options
>  
>  The following options apply only to Paravirtual guests.



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