From: Ian Campbell <Ian.Campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: vijay.kilari@gmail.com, Prasun.Kapoor@caviumnetworks.com,
Vijaya Kumar K <vijaya.kumar@caviumnetworks.com>,
julien.grall@linaro.org, tim@xen.org, xen-devel@lists.xen.org,
stefano.stabellini@citrix.com, jbeulich@suse.com,
manish.jaggi@caviumnetworks.com
Subject: Re: [PATCH v9 3/7] xen/arm: Add support for GIC v3
Date: Mon, 8 Sep 2014 10:42:32 +0100 [thread overview]
Message-ID: <1410169352.10156.125.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1409050125350.22438@kaball.uk.xensource.com>
On Fri, 2014-09-05 at 01:27 +0100, Stefano Stabellini wrote:
> On Thu, 4 Sep 2014, vijay.kilari@gmail.com wrote:
> > From: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
> >
> > Add support for GIC v3 specification System register access(SRE)
> > is enabled to access cpu and virtual interface registers based
> > on kernel GICv3 driver.
> >
> > This patch adds only basic v3 support.
> > Does not support Interrupt Translation support (ITS)
> >
> > Signed-off-by: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
>
> [...]
>
> > +static void gicv3_irq_set_affinity(struct irq_desc *desc, const cpumask_t *mask)
> > +{
> > + unsigned int cpu;
> > + uint64_t affinity;
> > +
> > + ASSERT(!cpumask_empty(mask));
> > +
> > + spin_lock(&gicv3.lock);
> > +
> > + cpu = gicv3_get_cpu_from_mask(mask);
> > + affinity = gicv3_mpidr_to_affinity(cpu);
> > + /* Make sure we don't broadcast the interrupt */
> > + affinity &= ~GICD_IROUTER_SPI_MODE_ANY;
>
> I would like an ASSERT(affinity != 0);
Should the v2 code do the same then?
There is no way that this value can be controlled by the guest then?
>
> Other than that:
>
> Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
next prev parent reply other threads:[~2014-09-08 9:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-04 13:15 [PATCH v9 0/7] xen/arm: Add GICv3 support vijay.kilari
2014-09-04 13:15 ` [PATCH v9 1/7] xen/arm: move itargets initialization to vgic-v2 vijay.kilari
2014-09-05 0:00 ` Stefano Stabellini
2014-09-09 10:37 ` Ian Campbell
2014-09-09 10:55 ` Vijay Kilari
2014-09-09 21:32 ` Stefano Stabellini
2014-09-08 20:30 ` Julien Grall
2014-09-09 4:43 ` Vijay Kilari
2014-09-04 13:15 ` [PATCH v9 2/7] xen/arm: fallback to vcpu 0 if get_target_vcpu handler not exists vijay.kilari
2014-09-05 0:02 ` Stefano Stabellini
2014-09-04 13:15 ` [PATCH v9 3/7] xen/arm: Add support for GIC v3 vijay.kilari
2014-09-05 0:27 ` Stefano Stabellini
2014-09-08 9:42 ` Ian Campbell [this message]
2014-09-09 4:34 ` Vijay Kilari
2014-09-09 18:18 ` Stefano Stabellini
2014-09-04 13:15 ` [PATCH v9 4/7] xen/arm: Add virtual GICv3 support vijay.kilari
2014-09-05 0:49 ` Stefano Stabellini
2014-09-08 20:35 ` Julien Grall
2014-09-08 22:05 ` Stefano Stabellini
2014-09-09 10:36 ` Ian Campbell
2014-09-09 18:04 ` Stefano Stabellini
2014-09-04 13:15 ` [PATCH v9 5/7] xen/arm: Update Dom0 GIC dt node with GICv3 information vijay.kilari
2014-09-04 13:15 ` [PATCH v9 6/7] xen/arm: add SGI handling for GICv3 vijay.kilari
2014-09-04 13:15 ` [PATCH v9 7/7] xen/arm: check for GICv3 platform support vijay.kilari
2014-09-08 9:45 ` Ian Campbell
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=1410169352.10156.125.camel@kazak.uk.xensource.com \
--to=ian.campbell@citrix.com \
--cc=Prasun.Kapoor@caviumnetworks.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@linaro.org \
--cc=manish.jaggi@caviumnetworks.com \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=vijay.kilari@gmail.com \
--cc=vijaya.kumar@caviumnetworks.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).