linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: anup.patel@linaro.org (Anup Patel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] PSCI system off and reset for KVM ARM/ARM64
Date: Thu, 12 Dec 2013 21:42:25 +0530	[thread overview]
Message-ID: <1386864747-29006-4-git-send-email-anup.patel@linaro.org> (raw)
In-Reply-To: <1386864747-29006-1-git-send-email-anup.patel@linaro.org>

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)

Change Log:

V2:
 - Replace KVM_EXIT_RESET with KVM_EXIT_SYSTEM_EVENT
 - Make kvm_psci_call() return convention to match 
   KVM ARM return convention

V1:
 - Initial revised patch after RFC PATCH.

Anup Patel (2):
  KVM: Add KVM_EXIT_SYSTEM_EVENT to user space API header
  ARM/ARM64: KVM: Forward PSCI SYSTEM_OFF and SYSTEM_RESET to user
    space

 Documentation/virtual/kvm/api.txt |   15 ++++++++++++
 arch/arm/include/asm/kvm_psci.h   |    2 +-
 arch/arm/include/uapi/asm/kvm.h   |    2 ++
 arch/arm/kvm/handle_exit.c        |   13 +++++++---
 arch/arm/kvm/psci.c               |   48 ++++++++++++++++++++++++++++++-------
 arch/arm64/include/asm/kvm_psci.h |    2 +-
 arch/arm64/include/uapi/asm/kvm.h |    2 ++
 arch/arm64/kvm/handle_exit.c      |   12 +++++++---
 include/uapi/linux/kvm.h          |    8 +++++++
 9 files changed, 88 insertions(+), 16 deletions(-)

-- 
1.7.9.5

  parent reply	other threads:[~2013-12-12 16:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-12 16:12 [PATCH RESEND] arm64: KVM: Add Kconfig option for max VCPUs per-Guest Anup Patel
2013-12-12 16:12 ` [PATCH] arm64: KVM: Force undefined exception for Guest SMC intructions Anup Patel
2013-12-13 17:36   ` Marc Zyngier
2013-12-13 19:16   ` Christoffer Dall
2013-12-12 16:12 ` [PATCH] KVM: Documentation: Fix typo for KVM_ARM_VCPU_INIT ioctl Anup Patel
2013-12-13 19:18   ` Christoffer Dall
2013-12-12 16:12 ` Anup Patel [this message]
2013-12-13 19:19   ` [PATCH v2 0/2] PSCI system off and reset for KVM ARM/ARM64 Christoffer Dall
2013-12-12 16:12 ` [PATCH v2 1/2] KVM: Add KVM_EXIT_SYSTEM_EVENT to user space API header Anup Patel
2013-12-13 19:22   ` Christoffer Dall
2013-12-12 16:12 ` [PATCH v2 2/2] ARM/ARM64: KVM: Forward PSCI SYSTEM_OFF and SYSTEM_RESET to user space Anup Patel
2013-12-13 20:08   ` Christoffer Dall
2013-12-14 13:24     ` Anup Patel
2013-12-14 19:28       ` Christoffer Dall
2013-12-13 17:35 ` [PATCH RESEND] arm64: KVM: Add Kconfig option for max VCPUs per-Guest Marc Zyngier
2013-12-13 19:17 ` Christoffer Dall

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=1386864747-29006-4-git-send-email-anup.patel@linaro.org \
    --to=anup.patel@linaro.org \
    --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).