All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel@lists.xenproject.org, stefano.stabellini@citrix.com,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH v2 14/15] arm: Allow the user to specify the GIC version
Date: Tue, 30 Jun 2015 15:23:37 +0100	[thread overview]
Message-ID: <5592A669.1030004@citrix.com> (raw)
In-Reply-To: <1435669615.21469.147.camel@citrix.com>

Hi Ian,

On 30/06/15 14:06, Ian Campbell wrote:
> On Fri, 2015-06-26 at 10:34 +0100, Julien Grall wrote:
>> A platform may have a GIC compatible with previous version of the
>> device.
>>
>> This is allow to virtualize an unmodified OS on new hardware if the GIC
>> is compatible with older version.
>>
>> When a guest is created, the vGIC will emulate same version as the
>> hardware. Although, the user can specify in the configuration file the
>> preferred version (currently on GICv2 and GICv3 are supported).
>                                 ^ly?

Yes. I will fixed on the next version.

[..]

>> diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5
>> index a3e0e2e..663eb2d 100644
>> --- a/docs/man/xl.cfg.pod.5
>> +++ b/docs/man/xl.cfg.pod.5
>> @@ -1688,6 +1688,33 @@ The default is B<en-us>.
>>  
>>  See L<qemu(1)> for more information.
>>  
>> +=head2 Architecture Specific options
>> +
>> +=head3 ARM
>> +
>> +=over 4
>> +
>> +=item B<gic_version="vN">
>> +
>> +Version of the GIC emulated for the guest. Currently, the following versions
>> +are supported:
>> +
>> +=over 4
>> +
>> +=item B<v2>
>> +
>> +Emulate a GICv2 hardware
>> +
>> +=item B<v3>
>> +
>> +Emulate a GICv3 hardware. Note that the GICv2 compatibility is not supported.
> 
> "Note that the emulated GIC does not support the GICv2 compatibility
> mode". (To avoid confusion with such compatibility used to provide the
> other option to the guest)

Good idea. I will use it.

> 
>> +
>> +=back
>> +
>> +Although, all the versions may not be supported on the host.
> 
> "This requires hardware compatibility with the requested version. Either
> natively or via hardware backwards compatibility support".
> 
> 
>> +
>> +=back
>> +
>>  =head1 SEE ALSO
>>  
>>  =over 4
>> diff --git a/tools/libxl/libxl.h b/tools/libxl/libxl.h
>> index 0a7913b..68bc954 100644
>> --- a/tools/libxl/libxl.h
>> +++ b/tools/libxl/libxl.h
>> @@ -200,6 +200,11 @@
>>  #define LIBXL_HAVE_DEVICETREE_PASSTHROUGH 1
>>  
>>  /*
>> + * libxl_domain_build_info has the gic_version field.
>> + */
>> +#define LIBXL_HAVE_BUILDINFO_GIC_VERSION 1
> 
> Mention ARM in the comment and/or name?

Yes, I forgot to update it when I move the field within the "arm" structure.

[..]

>>  
>> +libxl_gic_version = Enumeration("gic_version", [
>> +    (0, "DEFAULT"),
>> +    (1, "2"),
>> +    (2, "3")
> 
> If you call these "V2" and "V3" then you can use
> libxl_gic_version_from_string to make the parsing much easier. If you
> subsequently add e.g. "v2m" then the parsing code in xl will also just
> work,

Will do.

> Better to line up the values with the gic version if possible too. Enums
> don't need to be contiguous. Or maybe use 0x20, 0x30 etc for the value,
> leaving space for gicv2m in 0x21 etc.

I will use 0x20, 0x30...

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-06-30 14:24 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  9:34 [PATCH v2 00/15] xen/arm: Add support for GICv2 on GICv3 Julien Grall
2015-06-26  9:34 ` [PATCH v2 01/15] xen/arm: Gate GICv3 change with HAS_GICV3 rather than CONFIG_ARM_64 Julien Grall
2015-06-30 12:41   ` Ian Campbell
2015-06-26  9:34 ` [PATCH v2 02/15] xen/arm: gic: Rename the callback make_dt_node in make_hwdom_dt_node Julien Grall
2015-06-30 12:43   ` Ian Campbell
2015-06-26  9:34 ` [PATCH v2 03/15] xen/arm: vGIC: Export vgic_vN ops rather than add an indirection Julien Grall
2015-06-30 12:45   ` Ian Campbell
2015-06-30 13:24     ` Julien Grall
2015-06-26  9:34 ` [PATCH v2 04/15] xen/arm: vGIC: Check return of the domain_init callback Julien Grall
2015-06-26  9:34 ` [PATCH v2 05/15] xen/arm: gic-v3: Fix the distributor region to 64kB Julien Grall
2015-06-26  9:34 ` [PATCH v2 06/15] xen/arm: gic-v3: Use the domain redistributor information to make the DT node Julien Grall
2015-06-30 12:46   ` Ian Campbell
2015-06-26  9:34 ` [PATCH v2 07/15] xen/arm: gic-v3: Rework the print message at initialization Julien Grall
2015-06-30 12:49   ` Ian Campbell
2015-06-26  9:34 ` [PATCH v2 08/15] xen/arm: gic-{v2, hip04}: Remove redundant check in {gicv2, hip04gic}_init Julien Grall
2015-06-26  9:34 ` [PATCH v2 09/15] xen/arm: gic-{v2, hip04}: Use SZ_64K rather than our custom value Julien Grall
2015-06-26  9:34 ` [PATCH v2 10/15] xen/arm: gic: Allow the base address to be 0 Julien Grall
2015-06-26  9:34 ` [PATCH v2 11/15] xen/arm: gic-{v2, hip04}: Remove hbase from the global state Julien Grall
2015-06-26  9:34 ` [PATCH v2 12/15] xen/arm: gic: Store the necessary HW information per vGIC Julien Grall
2015-06-30 12:56   ` Ian Campbell
2015-06-30 13:38     ` Julien Grall
2015-06-30 14:00       ` Ian Campbell
2015-06-30 14:11         ` Julien Grall
2015-06-30 14:18           ` Ian Campbell
2015-06-26  9:34 ` [PATCH v2 13/15] xen/arm: Merge gicv_setup with vgic_domain_init Julien Grall
2015-06-30 12:59   ` Ian Campbell
2015-06-30 13:51     ` Julien Grall
2015-06-30 13:56       ` Ian Campbell
2015-06-26  9:34 ` [PATCH v2 14/15] arm: Allow the user to specify the GIC version Julien Grall
2015-06-30 13:06   ` Ian Campbell
2015-06-30 14:23     ` Julien Grall [this message]
2015-06-26  9:34 ` [PATCH v2 15/15] xen/arm: gic-v3: Add support of vGICv2 when available Julien Grall
2015-06-30 13:16   ` Ian Campbell
2015-06-30 17:29     ` Julien Grall
2015-07-01  8:12       ` Ian Campbell
2015-07-01 10:21         ` Julien Grall
2015-06-30  8:05 ` [PATCH v2 00/15] xen/arm: Add support for GICv2 on GICv3 Chen Baozi

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=5592A669.1030004@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.