From: Julien Grall <julien.grall@linaro.org>
To: Frediano Ziglio <frediano.ziglio@huawei.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Tim Deegan <tim@xen.org>
Cc: Zoltan Kiss <zoltan.kiss@huawei.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v8 3/4] xen/arm: Make gic-v2 code handle hip04-d01 platform
Date: Tue, 03 Mar 2015 15:42:36 +0000 [thread overview]
Message-ID: <54F5D66C.2060205@linaro.org> (raw)
In-Reply-To: <B944B469BF5302468AC6EB05E56CC70D1A5B07C2@lhreml503-mbs.china.huawei.com>
On 03/03/15 15:36, Frediano Ziglio wrote:
>>
>> Hello Frediano,
>>
>> On 03/03/15 11:19, Frediano Ziglio wrote:
>>> The GIC in this platform is mainly compatible with the standard
>>> GICv2 beside:
>>> - ITARGET is extended to 16 bit to support 16 CPUs;
>>> - SGI mask is extended to support 16 CPUs;
>>> - maximum supported interrupt is 510;
>>
>> 510 is not a multiple of 32. Is it normal?
>>
>> This will result to having nr_lines = 512. What happen is we are trying
>> to access IRQ 510 and 511?
>>
>
> I don't know. I think it's the same reason why in xen/arch/arm/gic.c the limit for irq is 1021 and not 1024 (see "if ( likely(irq >= 16 && irq < 1021) )" line)
IRQ 1021-1023 are reserved by the GIC as spurious interrupt.
If I understand correctly what you say, IRQ 510-511 may be considered
for spurious interrupt?
If so, the check (irq >= 16 && irq < 1021) needs to be changed.
>> Also, is it possible to have GICH.VirtualID >= 510?
>>
>
> I think so, GICH have the same interface of normal GICv2.
But some offsets are different... so I'd like a confirmation based on
some spec.
For instance on GICv2 if we use some VirtualID (1021-1023) the behavior
is unpredictable.
So if you have the a similar things on your board we may need to
restrict the number of VirtualID in order to avoid introduce a possible
host denial from a guest.
>> [..]
>>
>>> -DT_DEVICE_START(gicv2, "GICv2", DEVICE_GIC)
>>> - .dt_match = gicv2_dt_match,
>>> - .init = gicv2_init,
>>> +DT_DEVICE_START(hip04gic, "GIC-HIP04", DEVICE_GIC)
>>> + .dt_match = hip04gic_dt_match,
>>> + .init = hip04gic_init,
>>> DT_DEVICE_END
>>
>> Please keep the same indentation as before.
>>
>
> I was wondering why the indentation is different. Ok
I'm not sure why ... but it looks like we use the same indentation
everywhere for DT_DEVICE_START.
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-03-03 15:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-03 11:19 [PATCH v8 0/4] xen/arm: Add support for Huawei hip04-d01 platform Frediano Ziglio
2015-03-03 11:19 ` [PATCH v8 1/4] xen/arm: Duplicate gic-v2.c file to support hip04 platform version Frediano Ziglio
2015-03-03 11:19 ` [PATCH v8 2/4] xen/arm: Check for interrupt controller directly Frediano Ziglio
2015-03-03 14:45 ` Julien Grall
2015-03-03 15:07 ` Frediano Ziglio
2015-03-03 15:10 ` Julien Grall
2015-03-05 16:36 ` Ian Campbell
2015-03-09 10:55 ` Julien Grall
2015-03-09 16:08 ` Ian Campbell
2015-03-09 16:41 ` Frediano Ziglio
2015-03-09 17:03 ` Ian Campbell
2015-03-03 11:19 ` [PATCH v8 3/4] xen/arm: Make gic-v2 code handle hip04-d01 platform Frediano Ziglio
2015-03-03 15:07 ` Julien Grall
2015-03-03 15:36 ` Frediano Ziglio
2015-03-03 15:42 ` Julien Grall [this message]
2015-03-05 9:31 ` Frediano Ziglio
2015-03-05 10:36 ` Julien Grall
2015-03-03 11:19 ` [PATCH v8 4/4] xen/arm: Force dom0 to use normal GICv2 driver on Hip04 platform Frediano Ziglio
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=54F5D66C.2060205@linaro.org \
--to=julien.grall@linaro.org \
--cc=frediano.ziglio@huawei.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.org \
--cc=zoltan.kiss@huawei.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 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.