From: Julien Grall <julien.grall@linaro.org>
To: Frediano Ziglio <frediano.ziglio@huawei.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Tim Deegan <tim@xen.org>
Cc: zoltan.kiss@huawei.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v2 6/7] xen/arm: Force domains to use normal GICv2 driver on Hip04 platform
Date: Tue, 04 Nov 2014 13:33:18 +0000 [thread overview]
Message-ID: <5458D59E.9010703@linaro.org> (raw)
In-Reply-To: <1415033196-30529-7-git-send-email-frediano.ziglio@huawei.com>
Hi Frediano,
FYI, this is only force DOM0 to use the normal GICv2 drivers. I.e the
title of this patch is wrong.
Do you have any plan to support hi-silicon vGIC in Xen? This would allow
guest running with more than 8 cores.
Regards,
On 11/03/2014 04:46 PM, Frediano Ziglio wrote:
> Until vGIC support is not implemented and tested, this will prevent
> guest kernels to use their Hip04 driver, or crash when they don't
> have any.
>
> Signed-off-by: Frediano Ziglio <frediano.ziglio@huawei.com>
> ---
> xen/arch/arm/gic-v2.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/xen/arch/arm/gic-v2.c b/xen/arch/arm/gic-v2.c
> index 411b104..cea9edc 100644
> --- a/xen/arch/arm/gic-v2.c
> +++ b/xen/arch/arm/gic-v2.c
> @@ -639,6 +639,12 @@ static int gicv2_make_dt_node(const struct domain *d,
> return -FDT_ERR_XEN(ENOENT);
> }
>
> + if ( nr_gic_cpu_if == 16 )
> + {
> + compatible = DT_COMPAT_GIC_CORTEX_A15;
> + len = strlen((char*) compatible) + 1;
> + }
> +
> res = fdt_begin_node(fdt, "interrupt-controller");
> if ( res )
> return res;
>
--
Julien Grall
next prev parent reply other threads:[~2014-11-04 13:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 16:46 xen/arm: Add support for Huawei hip04-d01 platform Frediano Ziglio
2014-11-03 16:46 ` [PATCH v2 1/7] xen/device_tree: Add new helper to read arrays from a DTB Frediano Ziglio
2014-11-04 13:14 ` Julien Grall
2014-11-04 13:55 ` Frediano Ziglio
2014-11-04 14:00 ` Julien Grall
2014-11-03 16:46 ` [PATCH v2 2/7] xen/arm: Implement hip04-d01 platform Frediano Ziglio
2014-11-04 13:21 ` Julien Grall
2014-11-04 13:52 ` Frediano Ziglio
2014-11-04 14:03 ` Julien Grall
2014-11-04 14:17 ` Frediano Ziglio
2014-11-04 14:23 ` Julien Grall
2014-11-03 16:46 ` [PATCH v2 3/7] xen/arm: Make gic-v2 code handle " Frediano Ziglio
2014-11-04 13:31 ` Julien Grall
2014-11-04 13:34 ` Julien Grall
2014-11-04 15:54 ` Frediano Ziglio
2014-11-04 13:35 ` Julien Grall
2014-11-03 16:46 ` [PATCH v2 4/7] xen/arm: Add support for DTBs with strange names of Hip04 GICv2 Frediano Ziglio
2014-11-03 16:46 ` [PATCH v2 5/7] xen/arm: handle GICH register changes for hip04-d01 platform Frediano Ziglio
2014-11-03 16:46 ` [PATCH v2 6/7] xen/arm: Force domains to use normal GICv2 driver on Hip04 platform Frediano Ziglio
2014-11-04 13:33 ` Julien Grall [this message]
2014-11-04 14:10 ` Frediano Ziglio
2014-11-03 16:46 ` [PATCH v2 7/7] xen/arm: Move vGIC registers " Frediano Ziglio
2014-11-04 13:38 ` Julien Grall
2014-11-04 14:42 ` Frediano Ziglio
2014-11-04 14:50 ` Ian Campbell
2014-11-04 15:48 ` Frediano Ziglio
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=5458D59E.9010703@linaro.org \
--to=julien.grall@linaro.org \
--cc=frediano.ziglio@huawei.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=zoltan.kiss@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).