From: Ian Campbell <ian.campbell@citrix.com>
To: Julien Grall <julien.grall@citrix.com>
Cc: xen-devel@lists.xenproject.org, Chen Baozi <baozich@gmail.com>,
tim@xen.org, stefano.stabellini@citrix.com
Subject: Re: [PATCH] xen/arm: gic-v3: Implement correctly the callback send_SGI
Date: Fri, 8 May 2015 16:51:48 +0100 [thread overview]
Message-ID: <1431100308.2660.523.camel@citrix.com> (raw)
In-Reply-To: <554CC993.6040204@citrix.com>
On Fri, 2015-05-08 at 15:34 +0100, Julien Grall wrote:
> Hi Ian,
>
> On 08/05/15 15:01, Ian Campbell wrote:
> > On Mon, 2015-04-27 at 19:31 +0100, Julien Grall wrote:
> >> Currently, the GICv3 drivers is only able to send an SGI when the cpumask
> >
> > "driver"
> >
> >> is provided. Although with the modes SGI_TARGET_OTHERS and SGI_TARGET_SELF,
> >> no cpumask is provided. Any usage of those modes will crash the hypersivor.
> >>
> >> Move the rename gicv3_send_sgi to gicv3_send_sgi_list and implement the
> >
> > s/Move the r/R/
>
> I missed while reviewing the commit message. I will fix it in the next
> version.
>
> >> different modes:
> >> - SGI_TARGET_OTHERS: Set the Interrupt Routing Mode (bit 40) to 1
> >> (see Table 4 on Section 4.2.6 PRD03-GENC-010745 24.0)
> >> - SGI_TARGET_SELF: Contrawise GICv2, the SGI registers doesn't provide
> >
> > "Contrariwise"? But I think you really mean "Unlike". I'd also say "the
> > GICv3 SGI registers" and s/doesn't/don't/.
>
> Yes, "unlike" is better here.
>
> >
> >> a specific field. So use gicv3_send_sgi_list and pass the cpumask of
> >> the current CPU
> >> - SGI_TARGET_LIST: Directly call gicv3_send_sgi_list with the given
> >> cpumask
> >>
> >> Reported-by: Chen Baozi <baozich@gmail.com>
> >> Signed-off-by: Julien Grall <julien.grall@citrix.com>
> >
> > Apart from the commit message nits one code comment:
> >
> > [...]
> >> + case SGI_TARGET_OTHERS:
> >> + WRITE_SYSREG(ICH_SGI_TARGET_OTHERS << ICH_SGI_IRQMODE_SHIFT |
> >> + (register_t)sgi << ICH_SGI_IRQ_SHIFT,
> >
> > I don't think you want register_t here, unless ICC_SGI1R_EL1 might be a
> > different width on different architectures.
>
> Yes, ICC_SGIR1_EL1 is always 64-bit.
>
> > I think you should just cast to uint64_t and WRITE_SYSREG64.
>
> Right, I blindly re-use the WRITE_SYSREG as it was done on the previous
> implementation.
>
> Although, the gic-v3 code seems to always use {READ,WRITE}_SYSREG. This
> seems wrong too. I will send a patch for replace the calls by the the
> 64-bit version.
Thanks (although do make sure each register really is 64-bit...)
next prev parent reply other threads:[~2015-05-08 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 18:31 [PATCH] xen/arm: gic-v3: Implement correctly the callback send_SGI Julien Grall
2015-04-28 10:00 ` Stefano Stabellini
2015-04-28 10:31 ` Julien Grall
2015-05-08 14:02 ` Ian Campbell
2015-05-08 14:27 ` Julien Grall
2015-05-08 15:51 ` Ian Campbell
2015-05-08 14:01 ` Ian Campbell
2015-05-08 14:34 ` Julien Grall
2015-05-08 15:51 ` Ian Campbell [this message]
2015-05-08 16:55 ` Julien Grall
2015-05-11 8:34 ` Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2015-05-08 17:01 Julien Grall
2015-05-09 13:13 ` Chen Baozi
2015-05-21 14:50 ` 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=1431100308.2660.523.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=baozich@gmail.com \
--cc=julien.grall@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--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.