From: Ian Campbell <ian.campbell@citrix.com>
To: Iurii Konovalenko <iurii.konovalenko@globallogic.com>
Cc: Embedded-pv-devel@lists.xenproject.org,
Julien Grall <julien.grall@linaro.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Size of irq field
Date: Thu, 2 Apr 2015 16:19:11 +0100 [thread overview]
Message-ID: <1427987951.4037.92.camel@citrix.com> (raw)
In-Reply-To: <CABc08z+1KgYoXtG7TZTzokOVqT42tAN3NKSeYhGFp+sV1JufMg@mail.gmail.com>
On Thu, 2015-04-02 at 18:05 +0300, Iurii Konovalenko wrote:
> Hi, Julien!
>
> During bringing up Xen on Renesas Lager board we faced with problem.
> A lot of Xen sources relies on statement, that IRQ number is less then
> 256 and variables, parameters, fields etc. are of type uint8_t.
Please can you give some example of this?
Internally most irq stuff is unsigned int I think and "git grep
uint8_t.*irq -- xen" is not showing lots of hits, there are a few but
none which seem terribly scary or hard to fix.
> But we
> can have IRQs, that are greater then 255, for example on RCar H2 SoC.
> Also, as I saw from one of your latest commits, GICv supports 1020
> physical interrupts.
This has always been true, in fact Julien's commit was reducing the
limit (which was too high), not increasing it.
> As a result, overflow can occur. So it seems
> logical to increase all irq staff to uint16_t or uint32_t. We have
> local patches for increasing some structures, functions etc.
> But before pushing these patches I want to know your opinion, what do
> you think about this problem? What type should we use uint16_t or
> uint32_t? How to find all places where uint8_t type is used for IRQ?
We should certainly fix anywhere which is not using a large enough data
type.
Ian.
next prev parent reply other threads:[~2015-04-02 15:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 15:05 Size of irq field Iurii Konovalenko
2015-04-02 15:19 ` Ian Campbell [this message]
2015-04-02 15:34 ` Julien Grall
2015-04-03 12:40 ` Iurii Konovalenko
2015-04-03 13:31 ` Julien Grall
2015-04-14 10:33 ` Ian Campbell
2015-04-14 10:34 ` 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=1427987951.4037.92.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Embedded-pv-devel@lists.xenproject.org \
--cc=iurii.konovalenko@globallogic.com \
--cc=julien.grall@linaro.org \
--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.