linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] PSCI system off and reset for KVM ARM/ARM64
Date: Wed, 18 Dec 2013 09:42:09 -0600	[thread overview]
Message-ID: <52B1C251.9040801@gmail.com> (raw)
In-Reply-To: <87wqj2ql57.fsf@e102391-lin.cambridge.arm.com>

Adding Mark Rutland.

On 12/18/2013 08:38 AM, Marc Zyngier wrote:
> Christoffer Dall <christoffer.dall@linaro.org> writes:
> 
>> On Tue, Dec 17, 2013 at 05:05:34PM +0530, Anup Patel wrote:
>>> The Power State and Coordination Interface (PSCI) specification defines
>>> SYSTEM_OFF and SYSTEM_RESET functions for system poweroff and reboot.
>>>
>>> This patchset adds emulation of PSCI SYSTEM_OFF and SYSTEM_RESET functions
>>> in KVM ARM/ARM64 by forwarding them to user space (QEMU or KVMTOOL) using
>>> KVM_EXIT_SYSTEM_EVENT exit reason.
>>>
>>> To try this patch from guest kernel, we will need PSCI-based restart and
>>> poweroff support in the guest kenel for both ARM and ARM64.
>>>
>>> Rob Herring has already submitted patches for PSCI-based restart and
>>> poweroff in ARM kernel but these are not merged yet due unstable device
>>> tree bindings of kernel PSCI support. We will be having similar patches
>>> for PSCI-based restart and poweroff in ARM64 kernel.
>>> (Refer http://www.spinics.net/lists/arm-kernel/msg262217.html)
>>> (Refer http://www.spinics.net/lists/devicetree/msg05348.html)
>>
>> Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
>>
>> I can merge this series if Marc acks it as well.
> 
> The patches themselves are mostly fine. One issue though: They implement
> part of the v0.2 spec, but keep on using the range of function IDs that
> we made up for v0.1.
> 
> I just had a chat with the person responsible for the spec, and realized
> that the Function IDs mentionned in the v0.2 spec are not optional, and
> not using them would be in direct violation of the spec (the new numbers
> now come directly from the SMC calling convention).

News to me. That is exactly the opposite of what Mark Rutland told me.
This would certainly simplify things since the SMC calling convention
IDs encode the size and there would be no reason to put the IDs into DT.

> So I rekon we need to create a separate range for those. Also, I'd like
> to progress the DT and kernel side of things as well (otherwise this is
> all a bit pointless).
> 
> Rob: what are your plans regarding your PSCI v0.2 patches?

My plan was to simply add 2 optional properties for reset/off and be
done with it like is done here. I'll leave it to ARM to sort out all of
v0.2 ID and 32-bit vs. 64-bit issues.

Rob

  parent reply	other threads:[~2013-12-18 15:42 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17 11:35 [PATCH v3 0/2] PSCI system off and reset for KVM ARM/ARM64 Anup Patel
2013-12-17 11:35 ` [PATCH v3 1/2] KVM: Add KVM_EXIT_SYSTEM_EVENT to user space API header Anup Patel
2013-12-17 11:35 ` [PATCH v3 2/2] ARM/ARM64: KVM: Forward PSCI SYSTEM_OFF and SYSTEM_RESET to user space Anup Patel
2013-12-17 11:53 ` [PATCH v3 0/2] PSCI system off and reset for KVM ARM/ARM64 Alexander Graf
2013-12-17 18:51 ` Christoffer Dall
2013-12-18 14:38   ` Marc Zyngier
2013-12-18 15:03     ` Anup Patel
2013-12-18 15:41       ` Marc Zyngier
2013-12-18 15:52         ` Anup Patel
2013-12-18 18:11           ` Marc Zyngier
2013-12-18 18:18             ` Anup Patel
2013-12-18 18:25               ` Marc Zyngier
2013-12-18 23:26                 ` Rob Herring
2013-12-19  4:30                   ` Christoffer Dall
2013-12-18 20:38         ` Christoffer Dall
2013-12-19 14:17           ` Paolo Bonzini
2013-12-18 15:42     ` Rob Herring [this message]
2013-12-18 18:10       ` Marc Zyngier
2014-01-07 11:50         ` Mark Rutland
2014-01-08 22:02           ` Christoffer Dall
2014-01-10 14:47           ` Rob Herring

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=52B1C251.9040801@gmail.com \
    --to=robherring2@gmail.com \
    --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 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).