From: Stefano Stabellini <sstabellini@kernel.org>
To: julien.grall@arm.com
Cc: Stefano Stabellini <stefanos@xilinx.com>,
Achin.Gupta@arm.com, sstabellini@kernel.org,
andrii_anisov@epam.com, xen-devel@lists.xen.org
Subject: [PATCH 4/5] xen/arm: use the physical number of gic lines for boot domains
Date: Wed, 5 Dec 2018 09:28:10 -0800 [thread overview]
Message-ID: <1544030891-11906-4-git-send-email-sstabellini@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.10.1812050923160.527@sstabellini-ThinkPad-X260>
We don't have a clear way to know how many virtual SPIs we need for the
boot domains. For simplicity, allocate as many as natively supported,
just like for dom0.
Signed-off-by: Stefano Stabellini <stefanos@xilinx.com>
---
xen/arch/arm/domain_build.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
index d48f77e..529b674 100644
--- a/xen/arch/arm/domain_build.c
+++ b/xen/arch/arm/domain_build.c
@@ -2239,7 +2239,7 @@ void __init create_domUs(void)
struct domain *d;
struct xen_domctl_createdomain d_cfg = {
.arch.gic_version = XEN_DOMCTL_CONFIG_GIC_NATIVE,
- .arch.nr_spis = 0,
+ .arch.nr_spis = gic_number_lines() - 32,
.flags = XEN_DOMCTL_CDF_hvm_guest | XEN_DOMCTL_CDF_hap,
.max_vcpus = 1,
.max_evtchn_port = -1,
@@ -2250,8 +2250,6 @@ void __init create_domUs(void)
if ( !dt_device_is_compatible(node, "xen,domain") )
continue;
- if ( dt_property_read_bool(node, "vpl011") )
- d_cfg.arch.nr_spis = GUEST_VPL011_SPI - 32 + 1;
dt_property_read_u32(node, "cpus", &d_cfg.max_vcpus);
d = domain_create(++max_init_domid, &d_cfg, false);
--
1.9.1
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-12-05 17:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 17:28 [PATCH 0/5] dom0less device assignment Stefano Stabellini
2018-12-05 17:28 ` [PATCH 1/5] xen/arm: copy dtb fragment to guest dtb Stefano Stabellini
2018-12-24 11:17 ` Julien Grall
2019-01-02 12:22 ` Wei Liu
2019-01-02 23:25 ` Stefano Stabellini
2018-12-05 17:28 ` [PATCH 2/5] xen/arm: assign devices to boot domains Stefano Stabellini
2018-12-24 13:55 ` Julien Grall
2019-01-03 22:07 ` Stefano Stabellini
2019-01-15 12:50 ` Julien Grall
2018-12-05 17:28 ` [PATCH 3/5] xen/arm: handle "multiboot, dtb" compatible nodes Stefano Stabellini
2018-12-24 13:58 ` Julien Grall
2019-01-02 23:28 ` Stefano Stabellini
2018-12-05 17:28 ` Stefano Stabellini [this message]
2018-12-24 14:01 ` [PATCH 4/5] xen/arm: use the physical number of gic lines for boot domains Julien Grall
2019-01-03 19:07 ` Stefano Stabellini
2019-01-15 12:56 ` Julien Grall
2018-12-05 17:28 ` [PATCH 5/5] xen/arm: add dom0less device assignment info to docs Stefano Stabellini
2018-12-24 14:06 ` Julien Grall
2019-01-03 22:07 ` Stefano Stabellini
2019-01-03 23:31 ` Stefano Stabellini
2019-01-15 13:03 ` Julien Grall
2019-01-15 13:02 ` Julien Grall
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=1544030891-11906-4-git-send-email-sstabellini@kernel.org \
--to=sstabellini@kernel.org \
--cc=Achin.Gupta@arm.com \
--cc=andrii_anisov@epam.com \
--cc=julien.grall@arm.com \
--cc=stefanos@xilinx.com \
--cc=xen-devel@lists.xen.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 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).