[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20141104171939.GI4042@n2100.arm.linux.org.uk>
Date: Tue, 4 Nov 2014 17:19:40 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Daniel Thompson <daniel.thompson@...aro.org>
Cc: Daniel Drake <drake@...lessm.com>, linaro-kernel@...ts.linaro.org,
patches@...aro.org, Linux Kernel <linux-kernel@...r.kernel.org>,
John Stultz <john.stultz@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Sumit Semwal <sumit.semwal@...aro.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
Jon Medhurst <tixy@...aro.org>,
Marc Zyngier <marc.zyngier@....com>
Subject: Re: [PATCH 3.17-rc4 v7 0/6] arm: Implement
arch_trigger_all_cpu_backtrace
On Tue, Nov 04, 2014 at 05:05:25PM +0000, Daniel Thompson wrote:
> This week with the help of one of my colleagues (thanks Tixy) I have
> been able to run some tests and figure out what it going on on vexpress-a9.
>
> The summary is that on some GICv1 implementations the bit to enable
> group 1 interrupts cannot be accessed using secure memory accesses. More
> specifically the presence/absence of the EnableGrp1 bit in the secure
> version GICD_CTRL register is implementation defined.
>
> My original patches overlooked this and as a result the existing code
> will migrate all interrupts to group but then cannot enable delivery of
> group 1 interrupts.
>
> I'm planning to respin the code so it will automatically disable FIQ
> support when the EnableGrp1 bit is not implemented. This means
> vexpress-a9 will not benefit from FIQ support but will also not be
> harmed by it.
That's good news, and it should mean that the Versatile Express starts
booting on the nightly boot tests again. Thanks for looking into it.
--
FTTC broadband for 0.8mile line: currently at 9.5Mbps down 400kbps up
according to speedtest.net.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists