From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: DT: Add binding for GIC virtualization extentions (VGIC)
Date: Wed, 9 May 2012 20:47:06 +0000 [thread overview]
Message-ID: <201205092047.06852.arnd@arndb.de> (raw)
In-Reply-To: <37e096905f891fc6abdccf8977bd7447@localhost>
On Wednesday 09 May 2012, Marc Zyngier wrote:
> Ah, I see what you mean. But these registers and interrupt are actually
> only visible on the hypervizor side. The guest shouldn't see any of this.
Rihgt, that makes sense.
> I suppose we could have a "arm,has-virt-extensions" property in devices
> that implement the virtualization extensions (GIC, timers...).
>
> What do you think?
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.
On the guest side, is it guaranteed that the virtual GIC looks like
a real GIC without those extensions? If the actual behavior depends on
the hypervisor, it might still make sense to add another flag in there
to tell that it's virtual, even if we don't require it for now.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: grant.likely@secretlab.ca, devicetree-discuss@lists.ozlabs.org,
david.vrabel@citrix.com, rob.herring@calxeda.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] ARM: DT: Add binding for GIC virtualization extentions (VGIC)
Date: Wed, 9 May 2012 20:47:06 +0000 [thread overview]
Message-ID: <201205092047.06852.arnd@arndb.de> (raw)
In-Reply-To: <37e096905f891fc6abdccf8977bd7447@localhost>
On Wednesday 09 May 2012, Marc Zyngier wrote:
> Ah, I see what you mean. But these registers and interrupt are actually
> only visible on the hypervizor side. The guest shouldn't see any of this.
Rihgt, that makes sense.
> I suppose we could have a "arm,has-virt-extensions" property in devices
> that implement the virtualization extensions (GIC, timers...).
>
> What do you think?
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.
On the guest side, is it guaranteed that the virtual GIC looks like
a real GIC without those extensions? If the actual behavior depends on
the hypervisor, it might still make sense to add another flag in there
to tell that it's virtual, even if we don't require it for now.
Arnd
next prev parent reply other threads:[~2012-05-09 20:47 UTC|newest]
Thread overview: 30+ 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
2012-05-09 17:57 ` Marc Zyngier
2012-05-09 19:21 ` Arnd Bergmann
2012-05-09 19:21 ` Arnd Bergmann
2012-05-09 19:36 ` Marc Zyngier
2012-05-09 19:36 ` Marc Zyngier
2012-05-09 20:27 ` Arnd Bergmann
2012-05-09 20:27 ` Arnd Bergmann
2012-05-09 20:42 ` Marc Zyngier
2012-05-09 20:42 ` Marc Zyngier
2012-05-09 20:47 ` Arnd Bergmann [this message]
2012-05-09 20:47 ` Arnd Bergmann
2012-05-09 21:34 ` Marc Zyngier
2012-05-09 21:34 ` Marc Zyngier
2012-05-10 10:53 ` Arnd Bergmann
2012-05-10 10:53 ` Arnd Bergmann
2012-05-10 11:11 ` Marc Zyngier
2012-05-10 11:11 ` Marc Zyngier
2012-05-11 15:11 ` Grant Likely
2012-05-11 15:11 ` Grant Likely
2012-05-11 15:10 ` Grant Likely
2012-05-11 15:10 ` Grant Likely
2012-05-11 14:14 ` David Vrabel
2012-05-11 14:14 ` David Vrabel
2012-05-11 14:42 ` Marc Zyngier
2012-05-11 14:42 ` Marc Zyngier
2012-05-11 14:43 ` David Vrabel
2012-05-11 14:43 ` David Vrabel
2012-05-11 15:15 ` Grant Likely
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=201205092047.06852.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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.