From: Ian Campbell <ian.campbell@citrix.com>
To: Vijay Kilari <vijay.kilari@gmail.com>
Cc: Julien Grall <julien.grall@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: xen/arm: Query - vgic nr_spis value for domU
Date: Tue, 24 Feb 2015 09:41:11 +0000 [thread overview]
Message-ID: <1424770871.27930.268.camel@citrix.com> (raw)
In-Reply-To: <CALicx6sHeUsG3ZzFWbhwU=UroXAjD-VVRkD1QfCpQA+pgSxsng@mail.gmail.com>
On Tue, 2015-02-24 at 14:54 +0530, Vijay Kilari wrote:
> Hi,
>
> In the below snippet, nr_spis is set to 0 from domU based on this
> pending_irq[] is allocated
>
> int domain_vgic_init(struct domain *d)
> {
> ....
> if ( is_hardware_domain(d) )
> d->arch.vgic.nr_spis = gic_number_lines() - 32;
> else
> d->arch.vgic.nr_spis = 0; /* We don't need SPIs for the guest */
> ...
>
> }
>
> Does it mean that no devices are attached to domU. So spis are required?
> If so, for device pass-through (non-pci) how is it managed?
Julien's non-pci passthrough series makes this configurable at domain
creation time.
> For pci-passthrough I am assigning non-zero value to nr_lpis for both
> domU & dom0
> and allocating pending_lpis[] because MSIx are assigned to domU
> directly on ITS commands
> trapped from domain.
>
> Do you see any issue with this?
dom0 should get the underlying h/w platforms value for nr_*, including
spi and lpi
domU should get configurable nr_lpi in the same way Julien has done for
spi. Unless it is possible to make nr_lpi dynamic based on the guests
actual usage patterns (i.e. alloc on demand), that would be ok too.
Ian.
next prev parent reply other threads:[~2015-02-24 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 9:24 xen/arm: Query - vgic nr_spis value for domU Vijay Kilari
2015-02-24 9:41 ` Ian Campbell [this message]
2015-02-24 9:48 ` Julien Grall
2015-02-24 10:23 ` Ian Campbell
2015-02-24 10:49 ` Vijay Kilari
2015-02-24 12:50 ` 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=1424770871.27930.268.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=julien.grall@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=vijay.kilari@gmail.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 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.