From: anup.patel@linaro.org (Anup Patel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] KVM: Add capability to advertise PSCI v0.2 support
Date: Thu, 30 Jan 2014 16:11:17 +0530 [thread overview]
Message-ID: <1391078479-7406-2-git-send-email-anup.patel@linaro.org> (raw)
In-Reply-To: <1391078479-7406-1-git-send-email-anup.patel@linaro.org>
User space (i.e. QEMU or KVMTOOL) should be able to check whether KVM
ARM/ARM64 supports in-kernel PSCI v0.2 emulation. For this purpose, we
define KVM_CAP_ARM_PSCI_0_2 in KVM user space interface header.
Signed-off-by: Anup Patel <anup.patel@linaro.org>
Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
---
include/uapi/linux/kvm.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
index 902f124..d64349e 100644
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@ -674,6 +674,7 @@ struct kvm_ppc_smmu_info {
#define KVM_CAP_ARM_EL1_32BIT 93
#define KVM_CAP_SPAPR_MULTITCE 94
#define KVM_CAP_EXT_EMUL_CPUID 95
+#define KVM_CAP_ARM_PSCI_0_2 96
#ifdef KVM_CAP_IRQ_ROUTING
--
1.7.9.5
next prev parent reply other threads:[~2014-01-30 10:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 10:41 [PATCH v2 0/3] In-kernel PSCI v0.2 emulation for KVM ARM/ARM64 Anup Patel
2014-01-30 10:41 ` Anup Patel [this message]
2014-02-02 4:06 ` [PATCH v2 1/3] KVM: Add capability to advertise PSCI v0.2 support Christoffer Dall
2014-02-03 11:48 ` Mark Rutland
2014-02-03 12:09 ` Anup Patel
2014-02-03 13:46 ` Mark Rutland
2014-01-30 10:41 ` [PATCH v2 2/3] ARM/ARM64: KVM: Add support for PSCI v0.2 emulation Anup Patel
2014-02-02 4:04 ` Christoffer Dall
2014-02-03 10:54 ` Mark Rutland
2014-02-03 11:16 ` Anup Patel
2014-02-03 11:19 ` Anup Patel
2014-02-03 11:46 ` Mark Rutland
2014-02-03 16:26 ` Christoffer Dall
2014-01-30 10:41 ` [PATCH v2 3/3] KVM: Documentation: Add info regarding KVM_ARM_VCPU_PSCI_0_2 feature Anup Patel
2014-02-02 4:06 ` 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=1391078479-7406-2-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).