xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: julien.grall@citrix.com, xen-devel@lists.xensource.com,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v5 05/10] xen/arm: nr_lrs should be uint8_t
Date: Tue, 01 Apr 2014 13:12:01 +0100	[thread overview]
Message-ID: <533AAD11.2070809@linaro.org> (raw)
In-Reply-To: <1396353541.8667.127.camel@kazak.uk.xensource.com>

On 04/01/2014 12:59 PM, Ian Campbell wrote:
> On Mon, 2014-03-24 at 18:49 +0000, Stefano Stabellini wrote:
>> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> 
> Does this change anything in practice?

Patch #6 of Stefano's series keep track of LRs with an uint8 bits. I
asked for this patch to stupid issue later because the tracking use an
smaller number of bits.

> Hopefully the compiler doesn't start doing stupid word access + mask on
> every access...
> 
> Might there be more LRs with e.g. gic v3?

The number of LRs is encoded on 5 bits for the GICv3.

-- 
Julien Grall

  reply	other threads:[~2014-04-01 12:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24 18:48 [PATCH v5 0/10] remove maintenance interrupts Stefano Stabellini
2014-03-24 18:49 ` [PATCH v5 01/10] xen/arm: no need to set HCR_VI when using the vgic to inject irqs Stefano Stabellini
2014-03-24 18:49 ` [PATCH v5 02/10] xen/arm: remove unused virtual parameter from vgic_vcpu_inject_irq Stefano Stabellini
2014-03-24 18:49 ` [PATCH v5 03/10] xen/arm: set GICH_HCR_UIE if all the LRs are in use Stefano Stabellini
2014-04-01 11:46   ` Ian Campbell
2014-03-24 18:49 ` [PATCH v5 04/10] xen/arm: support HW interrupts, do not request maintenance_interrupts Stefano Stabellini
2014-04-01 11:56   ` Ian Campbell
2014-04-01 12:13     ` Ian Campbell
2014-04-02 14:59       ` Stefano Stabellini
2014-04-02 15:19     ` Stefano Stabellini
2014-03-24 18:49 ` [PATCH v5 05/10] xen/arm: nr_lrs should be uint8_t Stefano Stabellini
2014-03-25 15:47   ` Julien Grall
2014-04-01 11:59   ` Ian Campbell
2014-04-01 12:12     ` Julien Grall [this message]
2014-04-01 12:15       ` Ian Campbell
2014-03-24 18:49 ` [PATCH v5 06/10] xen/arm: keep track of the GICH_LR used for the irq in struct pending_irq Stefano Stabellini
2014-04-01 12:00   ` Ian Campbell
2014-03-24 18:49 ` [PATCH v5 07/10] xen/arm: s/gic_set_guest_irq/gic_raise_guest_irq Stefano Stabellini
2014-04-01 12:00   ` Ian Campbell
2014-03-24 18:49 ` [PATCH v5 08/10] xen/arm: second irq injection while the first irq is still inflight Stefano Stabellini
2014-04-01 12:14   ` Ian Campbell
2014-04-02 15:31     ` Stefano Stabellini
2014-04-02 15:43       ` Ian Campbell
2014-04-06 16:58         ` Stefano Stabellini
2014-04-07  8:48           ` Ian Campbell
2014-03-24 18:49 ` [PATCH v5 09/10] xen/arm: don't protect GICH and lr_queue accesses with gic.lock Stefano Stabellini
2014-03-24 18:49 ` [PATCH v5 10/10] xen/arm: gic_events_need_delivery and irq priorities Stefano Stabellini

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=533AAD11.2070809@linaro.org \
    --to=julien.grall@linaro.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=julien.grall@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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).