From: Chris Metcalf <cmetcalf@ezchip.com>
To: Marc Zyngier <marc.zyngier@arm.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH] help guest boot up on AArch64 host with GICv2
Date: Fri, 29 Jan 2016 13:29:20 -0500 [thread overview]
Message-ID: <56ABAF80.4090400@ezchip.com> (raw)
In-Reply-To: <56ABA74A.3080500@arm.com>
On 01/29/2016 12:54 PM, Marc Zyngier wrote:
> By the look of it, you're trying to use a GICv3 firmware, and pass a
> GICv2 DT to the kernel. Do not do that. Either you use a GICv2 firmware
> (having spoken to the ATF guys, there is a GICv2 driver in there that
> should work for your case) and pass a GICv2 DT, or you go GICv3 all the way.
>
> A mix of the two things is completely unsupported on the model, and
> solidly places you in the UNPREDICTABLE category when running that on
> actual HW...
Once we upgrade to ATF 1.2 we will remove all of our GICv2
stuff and see if everything works smoothly; till then, at least, we
seem to have a workaround in place for development that will
let us keep moving forward.
From the ATF docs it does seem that using a v3 GIC in v2
compatibility mode should be supported, but it's not pressing
from our side to drill any deeper to try to see why it's not
actually working correctly for us (though I'd be happy to try
any further testing in this configuration if that's helpful).
Thanks!
--
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com
WARNING: multiple messages have this Message-ID (diff)
From: cmetcalf@ezchip.com (Chris Metcalf)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] help guest boot up on AArch64 host with GICv2
Date: Fri, 29 Jan 2016 13:29:20 -0500 [thread overview]
Message-ID: <56ABAF80.4090400@ezchip.com> (raw)
In-Reply-To: <56ABA74A.3080500@arm.com>
On 01/29/2016 12:54 PM, Marc Zyngier wrote:
> By the look of it, you're trying to use a GICv3 firmware, and pass a
> GICv2 DT to the kernel. Do not do that. Either you use a GICv2 firmware
> (having spoken to the ATF guys, there is a GICv2 driver in there that
> should work for your case) and pass a GICv2 DT, or you go GICv3 all the way.
>
> A mix of the two things is completely unsupported on the model, and
> solidly places you in the UNPREDICTABLE category when running that on
> actual HW...
Once we upgrade to ATF 1.2 we will remove all of our GICv2
stuff and see if everything works smoothly; till then, at least, we
seem to have a workaround in place for development that will
let us keep moving forward.
From the ATF docs it does seem that using a v3 GIC in v2
compatibility mode should be supported, but it's not pressing
from our side to drill any deeper to try to see why it's not
actually working correctly for us (though I'd be happy to try
any further testing in this configuration if that's helpful).
Thanks!
--
Chris Metcalf, EZChip Semiconductor
http://www.ezchip.com
next prev parent reply other threads:[~2016-01-29 18:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 20:02 [PATCH] help guest boot up on AArch64 host with GICv2 Chris Metcalf
2016-01-15 20:02 ` Chris Metcalf
2016-01-18 9:28 ` Marc Zyngier
2016-01-18 9:28 ` Marc Zyngier
2016-01-26 20:43 ` Chris Metcalf
2016-01-26 20:43 ` Chris Metcalf
2016-01-27 9:12 ` Marc Zyngier
2016-01-27 9:12 ` Marc Zyngier
2016-01-28 20:12 ` Chris Metcalf
2016-01-28 20:12 ` Chris Metcalf
2016-01-29 7:24 ` Ard Biesheuvel
2016-01-29 7:24 ` Ard Biesheuvel
2016-01-29 17:49 ` Chris Metcalf
2016-01-29 17:49 ` Chris Metcalf
2016-01-29 17:54 ` Marc Zyngier
2016-01-29 17:54 ` Marc Zyngier
2016-01-29 18:29 ` Chris Metcalf [this message]
2016-01-29 18:29 ` Chris Metcalf
2016-01-29 18:55 ` Marc Zyngier
2016-01-29 18:55 ` Marc Zyngier
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=56ABAF80.4090400@ezchip.com \
--to=cmetcalf@ezchip.com \
--cc=christoffer.dall@linaro.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.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.