From: Marc Zyngier <marc.zyngier@arm.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Will Deacon <Will.Deacon@arm.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"Tim (Xen.org)" <tim@xen.org>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH 1/4] xen/arm: basic PSCI support, implement cpu_on
Date: Wed, 10 Apr 2013 11:41:42 +0100 [thread overview]
Message-ID: <516541E6.90404@arm.com> (raw)
In-Reply-To: <1365588826.26448.1.camel@zakaz.uk.xensource.com>
On 10/04/13 11:13, Ian Campbell wrote:
> On Tue, 2013-04-09 at 15:23 +0100, Marc Zyngier wrote:
>> On 09/04/13 14:57, Ian Campbell wrote:
>>> On Thu, 2013-03-21 at 18:42 +0000, Stefano Stabellini wrote:
>>>> Implement support for ARM Power State Coordination Interface, PSCI in
>>>> short. The current implementation is based on HVC and only supports the
>>>> cpu_on call.
>>>
>>> Doesn't the PSCI interface require the use of SMC not HVC?
>>
>> You can use both, and KVM uses HVC.
>
> It makes good sense for Xen to follow suit then I think.
>
>>> I thought I heard Charles say at connect that there was now a PSCI v2,
>>> and I suspect I'm looking at the v1 document (which mentions HVC only in
>>> passing). Which interface did you implement?
>>>
>>> Anyhow, we can trap SMCs to the hypervisor by setting the right control
>>> register bits. We should do this anyway -- no good can come of a guest
>>> making a call direct to the monitor!
>>
>> Trapping guest access to Secure mode is always a good idea! ;-)
>
> :-)
>
>> Unfortunately, there's a catch on ARMv8. If the CPU doesn't implement
>> secure mode, then SMC will UNDEF at the current exception level (not
>> trapping to EL2). Which means that for ARMv8, you basically have to
>> mandate HVC for PSCI at the HYP level...
>
> That pretty much seals it then!
>
> Do I infer that on v7 SMC w/o security extensions will trap?
ARMv7 mandates security extensions if you have virtualization
extensions, so this is a moot point... ;-)
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2013-04-10 10:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 18:42 [PATCH 0/4] xen/arm: guest SMP support Stefano Stabellini
2013-03-21 18:42 ` [PATCH 1/4] xen/arm: basic PSCI support, implement cpu_on Stefano Stabellini
2013-04-09 13:57 ` Ian Campbell
2013-04-09 14:23 ` Marc Zyngier
2013-04-10 10:13 ` Ian Campbell
2013-04-10 10:41 ` Marc Zyngier [this message]
2013-04-10 10:50 ` Ian Campbell
2013-04-11 12:29 ` Ian Campbell
2013-04-11 23:42 ` Stefano Stabellini
2013-04-12 7:46 ` Ian Campbell
2013-04-18 12:59 ` Stefano Stabellini
2013-04-11 13:32 ` hypervisor/firmware calling conventions (Was: Re: [Xen-devel] [PATCH 1/4] xen/arm: basic PSCI support, implement cpu_on) Ian Campbell
2013-04-11 17:10 ` Dave Martin
2013-04-12 11:16 ` Ian Campbell
2013-04-12 14:22 ` Dave Martin
2013-03-21 18:42 ` [PATCH 2/4] xen/arm: support for guest SGI Stefano Stabellini
2013-04-09 14:01 ` Ian Campbell
2013-04-23 11:50 ` Stefano Stabellini
2013-04-23 11:57 ` Ian Campbell
2013-04-23 12:08 ` Stefano Stabellini
2013-04-23 13:10 ` Ian Campbell
2013-03-21 18:42 ` [PATCH 3/4] xen/arm: support vcpu_op hypercalls Stefano Stabellini
2013-04-09 14:02 ` Ian Campbell
2013-04-23 11:32 ` Stefano Stabellini
2013-04-23 13:52 ` Ian Campbell
2013-03-21 18:42 ` [PATCH 4/4] xen: move VCPUOP_register_vcpu_info to common code Stefano Stabellini
2013-04-09 14:04 ` Ian Campbell
2013-04-12 14:12 ` Ian Campbell
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=516541E6.90404@arm.com \
--to=marc.zyngier@arm.com \
--cc=Ian.Campbell@citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=Will.Deacon@arm.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xensource.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 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).