From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v10 02/12] ARM/ARM64: KVM: Add common header for PSCI related defines
Date: Mon, 28 Apr 2014 07:16:56 -0700 [thread overview]
Message-ID: <20140428141656.GF2868@lvm> (raw)
In-Reply-To: <1398085206-30555-3-git-send-email-anup.patel@linaro.org>
On Mon, Apr 21, 2014 at 06:29:56PM +0530, Anup Patel wrote:
> We need a common place to share PSCI related defines among ARM kernel,
> ARM64 kernel, KVM ARM/ARM64 PSCI emulation, and user space.
>
> We introduce uapi/linux/psci.h for this purpose. This newly added
> header will be first used by KVM ARM/ARM64 in-kernel PSCI emulation
> and user space (i.e. QEMU or KVMTOOL).
>
> Signed-off-by: Anup Patel <anup.patel@linaro.org>
> Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
> Signed-off-by: Ashwin Chaugule <ashwin.chaugule@linaro.org>
> ---
> include/uapi/linux/Kbuild | 1 +
> include/uapi/linux/psci.h | 85 +++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 86 insertions(+)
> create mode 100644 include/uapi/linux/psci.h
>
> diff --git a/include/uapi/linux/Kbuild b/include/uapi/linux/Kbuild
> index 6929571..24e9033 100644
> --- a/include/uapi/linux/Kbuild
> +++ b/include/uapi/linux/Kbuild
> @@ -317,6 +317,7 @@ header-y += ppp-ioctl.h
> header-y += ppp_defs.h
> header-y += pps.h
> header-y += prctl.h
> +header-y += psci.h
> header-y += ptp_clock.h
> header-y += ptrace.h
> header-y += qnx4_fs.h
> diff --git a/include/uapi/linux/psci.h b/include/uapi/linux/psci.h
> new file mode 100644
> index 0000000..0d4a136
> --- /dev/null
> +++ b/include/uapi/linux/psci.h
> @@ -0,0 +1,85 @@
> +/*
> + * ARM Power State and Coordination Interface (PSCI) header
> + *
> + * This header holds common PSCI defines and macros shared
> + * by: ARM kernel, ARM64 kernel, KVM ARM/ARM64 and user space.
> + *
> + * Copyright (C) 2014 Linaro Ltd.
> + * Author: Anup Patel <anup.patel@linaro.org>
> + */
> +
> +#ifndef _UAPI_LINUX_PSCI_H
> +#define _UAPI_LINUX_PSCI_H
> +
> +/*
> + * PSCI v0.1 interface
> + *
> + * The PSCI v0.1 function numbers are implementation defined.
> + *
> + * Only PSCI return values such as: SUCCESS, NOT_SUPPORTED,
> + * INVALID_PARAMS, and DENIED defined below are applicable
> + * to PSCI v0.1.
> + */
> +
> +/* PSCI v0.2 interface */
> +#define PSCI_0_2_FN_BASE 0x84000000
> +#define PSCI_0_2_FN(n) (PSCI_0_2_FN_BASE + (n))
> +#define PSCI_0_2_64BIT 0x40000000
> +#define PSCI_0_2_FN64_BASE \
> + (PSCI_0_2_FN_BASE + PSCI_0_2_64BIT)
> +#define PSCI_0_2_FN64(n) (PSCI_0_2_FN64_BASE + (n))
> +
> +#define PSCI_0_2_FN_PSCI_VERSION PSCI_0_2_FN(0)
> +#define PSCI_0_2_FN_CPU_SUSPEND PSCI_0_2_FN(1)
> +#define PSCI_0_2_FN_CPU_OFF PSCI_0_2_FN(2)
> +#define PSCI_0_2_FN_CPU_ON PSCI_0_2_FN(3)
> +#define PSCI_0_2_FN_AFFINITY_INFO PSCI_0_2_FN(4)
> +#define PSCI_0_2_FN_MIGRATE PSCI_0_2_FN(5)
> +#define PSCI_0_2_FN_MIGRATE_INFO_TYPE PSCI_0_2_FN(6)
> +#define PSCI_0_2_FN_MIGRATE_INFO_UP_CPU PSCI_0_2_FN(7)
> +#define PSCI_0_2_FN_SYSTEM_OFF PSCI_0_2_FN(8)
> +#define PSCI_0_2_FN_SYSTEM_RESET PSCI_0_2_FN(9)
> +
> +#define PSCI_0_2_FN64_CPU_SUSPEND PSCI_0_2_FN64(1)
> +#define PSCI_0_2_FN64_CPU_ON PSCI_0_2_FN64(3)
> +#define PSCI_0_2_FN64_AFFINITY_INFO PSCI_0_2_FN64(4)
> +#define PSCI_0_2_FN64_MIGRATE PSCI_0_2_FN64(5)
> +#define PSCI_0_2_FN64_MIGRATE_INFO_UP_CPU PSCI_0_2_FN64(7)
> +
> +#define PSCI_0_2_POWER_STATE_ID_MASK 0xffff
> +#define PSCI_0_2_POWER_STATE_ID_SHIFT 0
> +#define PSCI_0_2_POWER_STATE_TYPE_MASK 0x1
Shouldn't this be (0x1 << PSCI_0_2_POWER_STATE_TYPE_SHIFT)?
That seems to be the definition of a mask in the PSCI_VERSION_MAJOR_MASK
below,@least be consistent in this file.
> +#define PSCI_0_2_POWER_STATE_TYPE_SHIFT 16
> +#define PSCI_0_2_POWER_STATE_AFFL_MASK 0x3
same
> +#define PSCI_0_2_POWER_STATE_AFFL_SHIFT 24
> +
> +#define PSCI_0_2_AFFINITY_LEVEL_ON 0
> +#define PSCI_0_2_AFFINITY_LEVEL_OFF 1
> +#define PSCI_0_2_AFFINITY_LEVEL_ON_PENDING 2
I'm confused, what do these defines signify? I spent 10 minutes looking
at the spec and now I think that you probably mean AFFINITY_INFO and
that these are the possible return values? Probably warrants a comment.
> +
> +#define PSCI_0_2_TOS_UP_MIGRATE 0
> +#define PSCI_0_2_TOS_UP_NO_MIGRATE 1
> +#define PSCI_0_2_TOS_MP 2
Should probably also comment that "TOS" are return values for
MIGRATE_INFO_TYPE.
> +
> +/* PSCI version decoding (independent of PSCI version) */
> +#define PSCI_VERSION_MAJOR_SHIFT 16
> +#define PSCI_VERSION_MINOR_MASK \
> + ((1U << PSCI_VERSION_MAJOR_SHIFT) - 1)
> +#define PSCI_VERSION_MAJOR_MASK ~PSCI_VERSION_MINOR_MASK
> +#define PSCI_VERSION_MAJOR(ver) \
> + (((ver) & PSCI_VERSION_MAJOR_MASK) >> PSCI_VERSION_MAJOR_SHIFT)
> +#define PSCI_VERSION_MINOR(ver) \
> + ((ver) & PSCI_VERSION_MINOR_MASK)
I find this really complicated compared to "#define MINOR_MASK 0xffff"
and "#define MAJOR_MASK 0xffff0000" but whatever...
> +
> +/* PSCI return values (inclusive of all PSCI versions) */
> +#define PSCI_RET_SUCCESS 0
> +#define PSCI_RET_NOT_SUPPORTED -1
> +#define PSCI_RET_INVALID_PARAMS -2
> +#define PSCI_RET_DENIED -3
> +#define PSCI_RET_ALREADY_ON -4
> +#define PSCI_RET_ON_PENDING -5
> +#define PSCI_RET_INTERNAL_FAILURE -6
> +#define PSCI_RET_NOT_PRESENT -7
> +#define PSCI_RET_DISABLED -8
> +
> +#endif /* _UAPI_LINUX_PSCI_H */
> --
> 1.7.9.5
>
-Christoffer
WARNING: multiple messages have this Message-ID (diff)
From: Christoffer Dall <christoffer.dall@linaro.org>
To: Anup Patel <anup.patel@linaro.org>
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linaro-kernel@lists.linaro.org, patches@apm.com,
Marc Zyngier <Marc.Zyngier@arm.com>,
Rob Herring <rob.herring@linaro.org>,
Pranavkumar Sawargaonkar <pranavkumar@linaro.org>,
Ashwin Chaugule <ashwin.chaugule@linaro.org>
Subject: Re: [PATCH v10 02/12] ARM/ARM64: KVM: Add common header for PSCI related defines
Date: Mon, 28 Apr 2014 07:16:56 -0700 [thread overview]
Message-ID: <20140428141656.GF2868@lvm> (raw)
In-Reply-To: <1398085206-30555-3-git-send-email-anup.patel@linaro.org>
On Mon, Apr 21, 2014 at 06:29:56PM +0530, Anup Patel wrote:
> We need a common place to share PSCI related defines among ARM kernel,
> ARM64 kernel, KVM ARM/ARM64 PSCI emulation, and user space.
>
> We introduce uapi/linux/psci.h for this purpose. This newly added
> header will be first used by KVM ARM/ARM64 in-kernel PSCI emulation
> and user space (i.e. QEMU or KVMTOOL).
>
> Signed-off-by: Anup Patel <anup.patel@linaro.org>
> Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
> Signed-off-by: Ashwin Chaugule <ashwin.chaugule@linaro.org>
> ---
> include/uapi/linux/Kbuild | 1 +
> include/uapi/linux/psci.h | 85 +++++++++++++++++++++++++++++++++++++++++++++
> 2 files changed, 86 insertions(+)
> create mode 100644 include/uapi/linux/psci.h
>
> diff --git a/include/uapi/linux/Kbuild b/include/uapi/linux/Kbuild
> index 6929571..24e9033 100644
> --- a/include/uapi/linux/Kbuild
> +++ b/include/uapi/linux/Kbuild
> @@ -317,6 +317,7 @@ header-y += ppp-ioctl.h
> header-y += ppp_defs.h
> header-y += pps.h
> header-y += prctl.h
> +header-y += psci.h
> header-y += ptp_clock.h
> header-y += ptrace.h
> header-y += qnx4_fs.h
> diff --git a/include/uapi/linux/psci.h b/include/uapi/linux/psci.h
> new file mode 100644
> index 0000000..0d4a136
> --- /dev/null
> +++ b/include/uapi/linux/psci.h
> @@ -0,0 +1,85 @@
> +/*
> + * ARM Power State and Coordination Interface (PSCI) header
> + *
> + * This header holds common PSCI defines and macros shared
> + * by: ARM kernel, ARM64 kernel, KVM ARM/ARM64 and user space.
> + *
> + * Copyright (C) 2014 Linaro Ltd.
> + * Author: Anup Patel <anup.patel@linaro.org>
> + */
> +
> +#ifndef _UAPI_LINUX_PSCI_H
> +#define _UAPI_LINUX_PSCI_H
> +
> +/*
> + * PSCI v0.1 interface
> + *
> + * The PSCI v0.1 function numbers are implementation defined.
> + *
> + * Only PSCI return values such as: SUCCESS, NOT_SUPPORTED,
> + * INVALID_PARAMS, and DENIED defined below are applicable
> + * to PSCI v0.1.
> + */
> +
> +/* PSCI v0.2 interface */
> +#define PSCI_0_2_FN_BASE 0x84000000
> +#define PSCI_0_2_FN(n) (PSCI_0_2_FN_BASE + (n))
> +#define PSCI_0_2_64BIT 0x40000000
> +#define PSCI_0_2_FN64_BASE \
> + (PSCI_0_2_FN_BASE + PSCI_0_2_64BIT)
> +#define PSCI_0_2_FN64(n) (PSCI_0_2_FN64_BASE + (n))
> +
> +#define PSCI_0_2_FN_PSCI_VERSION PSCI_0_2_FN(0)
> +#define PSCI_0_2_FN_CPU_SUSPEND PSCI_0_2_FN(1)
> +#define PSCI_0_2_FN_CPU_OFF PSCI_0_2_FN(2)
> +#define PSCI_0_2_FN_CPU_ON PSCI_0_2_FN(3)
> +#define PSCI_0_2_FN_AFFINITY_INFO PSCI_0_2_FN(4)
> +#define PSCI_0_2_FN_MIGRATE PSCI_0_2_FN(5)
> +#define PSCI_0_2_FN_MIGRATE_INFO_TYPE PSCI_0_2_FN(6)
> +#define PSCI_0_2_FN_MIGRATE_INFO_UP_CPU PSCI_0_2_FN(7)
> +#define PSCI_0_2_FN_SYSTEM_OFF PSCI_0_2_FN(8)
> +#define PSCI_0_2_FN_SYSTEM_RESET PSCI_0_2_FN(9)
> +
> +#define PSCI_0_2_FN64_CPU_SUSPEND PSCI_0_2_FN64(1)
> +#define PSCI_0_2_FN64_CPU_ON PSCI_0_2_FN64(3)
> +#define PSCI_0_2_FN64_AFFINITY_INFO PSCI_0_2_FN64(4)
> +#define PSCI_0_2_FN64_MIGRATE PSCI_0_2_FN64(5)
> +#define PSCI_0_2_FN64_MIGRATE_INFO_UP_CPU PSCI_0_2_FN64(7)
> +
> +#define PSCI_0_2_POWER_STATE_ID_MASK 0xffff
> +#define PSCI_0_2_POWER_STATE_ID_SHIFT 0
> +#define PSCI_0_2_POWER_STATE_TYPE_MASK 0x1
Shouldn't this be (0x1 << PSCI_0_2_POWER_STATE_TYPE_SHIFT)?
That seems to be the definition of a mask in the PSCI_VERSION_MAJOR_MASK
below, at least be consistent in this file.
> +#define PSCI_0_2_POWER_STATE_TYPE_SHIFT 16
> +#define PSCI_0_2_POWER_STATE_AFFL_MASK 0x3
same
> +#define PSCI_0_2_POWER_STATE_AFFL_SHIFT 24
> +
> +#define PSCI_0_2_AFFINITY_LEVEL_ON 0
> +#define PSCI_0_2_AFFINITY_LEVEL_OFF 1
> +#define PSCI_0_2_AFFINITY_LEVEL_ON_PENDING 2
I'm confused, what do these defines signify? I spent 10 minutes looking
at the spec and now I think that you probably mean AFFINITY_INFO and
that these are the possible return values? Probably warrants a comment.
> +
> +#define PSCI_0_2_TOS_UP_MIGRATE 0
> +#define PSCI_0_2_TOS_UP_NO_MIGRATE 1
> +#define PSCI_0_2_TOS_MP 2
Should probably also comment that "TOS" are return values for
MIGRATE_INFO_TYPE.
> +
> +/* PSCI version decoding (independent of PSCI version) */
> +#define PSCI_VERSION_MAJOR_SHIFT 16
> +#define PSCI_VERSION_MINOR_MASK \
> + ((1U << PSCI_VERSION_MAJOR_SHIFT) - 1)
> +#define PSCI_VERSION_MAJOR_MASK ~PSCI_VERSION_MINOR_MASK
> +#define PSCI_VERSION_MAJOR(ver) \
> + (((ver) & PSCI_VERSION_MAJOR_MASK) >> PSCI_VERSION_MAJOR_SHIFT)
> +#define PSCI_VERSION_MINOR(ver) \
> + ((ver) & PSCI_VERSION_MINOR_MASK)
I find this really complicated compared to "#define MINOR_MASK 0xffff"
and "#define MAJOR_MASK 0xffff0000" but whatever...
> +
> +/* PSCI return values (inclusive of all PSCI versions) */
> +#define PSCI_RET_SUCCESS 0
> +#define PSCI_RET_NOT_SUPPORTED -1
> +#define PSCI_RET_INVALID_PARAMS -2
> +#define PSCI_RET_DENIED -3
> +#define PSCI_RET_ALREADY_ON -4
> +#define PSCI_RET_ON_PENDING -5
> +#define PSCI_RET_INTERNAL_FAILURE -6
> +#define PSCI_RET_NOT_PRESENT -7
> +#define PSCI_RET_DISABLED -8
> +
> +#endif /* _UAPI_LINUX_PSCI_H */
> --
> 1.7.9.5
>
-Christoffer
next prev parent reply other threads:[~2014-04-28 14:16 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-21 12:59 [PATCH v10 00/12] In-kernel PSCI v0.2 emulation for KVM ARM/ARM64 Anup Patel
2014-04-21 12:59 ` Anup Patel
2014-04-21 12:59 ` [PATCH v10 01/12] KVM: Add capability to advertise PSCI v0.2 support Anup Patel
2014-04-21 12:59 ` Anup Patel
2014-04-21 12:59 ` [PATCH v10 02/12] ARM/ARM64: KVM: Add common header for PSCI related defines Anup Patel
2014-04-21 12:59 ` Anup Patel
2014-04-28 14:16 ` Christoffer Dall [this message]
2014-04-28 14:16 ` Christoffer Dall
2014-04-28 17:13 ` Anup Patel
2014-04-28 17:13 ` Anup Patel
2014-04-28 17:19 ` Ashwin Chaugule
2014-04-28 17:19 ` Ashwin Chaugule
2014-04-21 12:59 ` [PATCH v10 03/12] ARM/ARM64: KVM: Add base for PSCI v0.2 emulation Anup Patel
2014-04-21 12:59 ` Anup Patel
2014-04-21 12:59 ` [PATCH v10 04/12] KVM: Documentation: Add info regarding KVM_ARM_VCPU_PSCI_0_2 feature Anup Patel
2014-04-21 12:59 ` Anup Patel
2014-04-21 12:59 ` [PATCH v10 05/12] ARM/ARM64: KVM: Make kvm_psci_call() return convention more flexible Anup Patel
2014-04-21 12:59 ` Anup Patel
2014-04-28 14:17 ` Christoffer Dall
2014-04-28 14:17 ` Christoffer Dall
2014-04-28 14:27 ` Marc Zyngier
2014-04-28 14:27 ` Marc Zyngier
2014-04-21 13:00 ` [PATCH v10 06/12] KVM: Add KVM_EXIT_SYSTEM_EVENT to user space API header Anup Patel
2014-04-21 13:00 ` Anup Patel
2014-04-21 13:00 ` [PATCH v10 07/12] ARM/ARM64: KVM: Emulate PSCI v0.2 SYSTEM_OFF and SYSTEM_RESET Anup Patel
2014-04-21 13:00 ` Anup Patel
2014-04-28 14:34 ` Marc Zyngier
2014-04-28 14:34 ` Marc Zyngier
2014-04-28 17:04 ` Anup Patel
2014-04-28 17:04 ` Anup Patel
2014-04-21 13:00 ` [PATCH v10 08/12] ARM/ARM64: KVM: Emulate PSCI v0.2 AFFINITY_INFO Anup Patel
2014-04-21 13:00 ` Anup Patel
2014-04-28 14:35 ` Marc Zyngier
2014-04-28 14:35 ` Marc Zyngier
2014-04-21 13:00 ` [PATCH v10 09/12] ARM/ARM64: KVM: Emulate PSCI v0.2 MIGRATE_INFO_TYPE and related functions Anup Patel
2014-04-21 13:00 ` Anup Patel
2014-04-21 13:00 ` [PATCH v10 10/12] ARM/ARM64: KVM: Fix CPU_ON emulation for PSCI v0.2 Anup Patel
2014-04-21 13:00 ` Anup Patel
2014-04-21 13:00 ` [PATCH v10 11/12] ARM/ARM64: KVM: Emulate PSCI v0.2 CPU_SUSPEND Anup Patel
2014-04-21 13:00 ` Anup Patel
2014-04-28 14:23 ` Christoffer Dall
2014-04-28 14:23 ` Christoffer Dall
2014-04-28 14:40 ` Marc Zyngier
2014-04-28 14:40 ` Marc Zyngier
2014-04-21 13:00 ` [PATCH v10 12/12] ARM/ARM64: KVM: Advertise KVM_CAP_ARM_PSCI_0_2 to user space Anup Patel
2014-04-21 13:00 ` Anup Patel
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=20140428141656.GF2868@lvm \
--to=christoffer.dall@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 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.