From: Marc Zyngier <marc.zyngier-5wv7dgnIgG8@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: "devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
"david.vrabel-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org"
<david.vrabel-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>,
"rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org"
<rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
"linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org"
<linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org>
Subject: Re: [PATCH v2] ARM: DT: Add binding for GIC virtualization extentions (VGIC)
Date: Thu, 10 May 2012 12:11:06 +0100 [thread overview]
Message-ID: <4FABA24A.9040209@arm.com> (raw)
In-Reply-To: <201205101053.09954.arnd-r2nGTMty4D4@public.gmane.org>
On 10/05/12 11:53, Arnd Bergmann wrote:
> On Wednesday 09 May 2012, Marc Zyngier wrote:
>>>
>>> Sounds good. I don't have a strong preference whether that should be a
>>> property like you suggest or a separate "compatible" value, maybe Rob or
>>> Grant can comment on what they prefer.
>>
>> At the moment, the compatible string should be pretty explicit, as it is
>> not possible to build an A7 or A15 based SoC without the virtualization
>> extensions.
>
> Ok, makes sense. Then again, if you run an A15 guests on an A15 host,
> the virtual GIC would not have those extensions, right?
Indeed, they would be inaccessible (the hypervisor should not map them
into the guest address space). I'd expect the guest kernel not to try to
use them anyway, as it wouldn't be able to use the HYP mode.
But again, this is implementation specific.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2012-05-10 11:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 17:57 [PATCH v2] ARM: DT: Add binding for GIC virtualization extentions (VGIC) Marc Zyngier
[not found] ` <1336586277-28454-1-git-send-email-marc.zyngier-5wv7dgnIgG8@public.gmane.org>
2012-05-09 19:21 ` Arnd Bergmann
2012-05-09 19:36 ` Marc Zyngier
2012-05-09 20:27 ` Arnd Bergmann
[not found] ` <201205092027.50059.arnd-r2nGTMty4D4@public.gmane.org>
2012-05-09 20:42 ` Marc Zyngier
2012-05-09 20:47 ` Arnd Bergmann
[not found] ` <201205092047.06852.arnd-r2nGTMty4D4@public.gmane.org>
2012-05-09 21:34 ` Marc Zyngier
2012-05-10 10:53 ` Arnd Bergmann
[not found] ` <201205101053.09954.arnd-r2nGTMty4D4@public.gmane.org>
2012-05-10 11:11 ` Marc Zyngier [this message]
2012-05-11 15:11 ` Grant Likely
2012-05-11 15:10 ` Grant Likely
2012-05-11 14:14 ` David Vrabel
2012-05-11 14:42 ` Marc Zyngier
[not found] ` <4FAD255A.4080504-5wv7dgnIgG8@public.gmane.org>
2012-05-11 14:43 ` David Vrabel
[not found] ` <4FAD25A1.2080106-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
2012-05-11 15:15 ` Grant Likely
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=4FABA24A.9040209@arm.com \
--to=marc.zyngier-5wv7dgnigg8@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=david.vrabel-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.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 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).