linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 02/12] ARM/ARM64: KVM: Add common header for PSCI related defines
Date: Mon, 31 Mar 2014 11:36:29 -0700	[thread overview]
Message-ID: <20140331183629.GF4756@lvm> (raw)
In-Reply-To: <CAJ5Y-eaGsM4Moz815P7QM=7qh87RyzU-MVyeLOT64CLEaR0HQA@mail.gmail.com>

On Mon, Mar 31, 2014 at 02:18:20PM -0400, Ashwin Chaugule wrote:
> Hello,
> 
> On 31 March 2014 14:07, Christoffer Dall <christoffer.dall@linaro.org> wrote:
> > On Mon, Mar 31, 2014 at 04:16:03PM +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>
> >> ---
> >>  include/uapi/linux/Kbuild |    1 +
> >>  include/uapi/linux/psci.h |   55 +++++++++++++++++++++++++++++++++++++++++++++
> >>  2 files changed, 56 insertions(+)
> >>  create mode 100644 include/uapi/linux/psci.h
> >>
> >
> > You should coordinate with Ashwin's work so you don't step on each
> > other's definitions and one patch set should depend on the other one.
> 
> So, apart from some extra #defines we mostly differ on style. Whats
> the general recommendation here?
> Mine looks simpler [1] ;)
> 
I think Marc brought up the point previously that we may get to PSCI
spec v42.17 and the defines should perhaps encompass the version we are
defining things for right now...

That being said, assuming new spec versions don't break backwards
compatibility in the numbering, the wording proposed by your patch does
look simpler.

I do like the hardcoded IDs because that's how it's presented in the
spec itself.

-Christoffer

  reply	other threads:[~2014-03-31 18:36 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 10:46 [PATCH v6 00/12] In-kernel PSCI v0.2 emulation for KVM ARM/ARM64 Anup Patel
2014-03-31 10:46 ` [PATCH v6 01/12] KVM: Add capability to advertise PSCI v0.2 support Anup Patel
2014-03-31 10:46 ` [PATCH v6 02/12] ARM/ARM64: KVM: Add common header for PSCI related defines Anup Patel
2014-03-31 18:07   ` Christoffer Dall
2014-03-31 18:18     ` Ashwin Chaugule
2014-03-31 18:36       ` Christoffer Dall [this message]
2014-03-31 19:26         ` Ashwin Chaugule
2014-03-31 19:43           ` Ashwin Chaugule
2014-04-01  4:11             ` Anup Patel
2014-04-02  4:22   ` Rob Herring
2014-04-02  4:31     ` Anup Patel
2014-04-02  5:00       ` Anup Patel
2014-03-31 10:46 ` [PATCH v6 03/12] ARM/ARM64: KVM: Add base for PSCI v0.2 emulation Anup Patel
2014-03-31 18:14   ` Christoffer Dall
2014-03-31 10:46 ` [PATCH v6 04/12] KVM: Documentation: Add info regarding KVM_ARM_VCPU_PSCI_0_2 feature Anup Patel
2014-03-31 10:46 ` [PATCH v6 05/12] ARM/ARM64: KVM: Make kvm_psci_call() return convention more flexible Anup Patel
2014-03-31 10:46 ` [PATCH v6 06/12] KVM: Add KVM_EXIT_SYSTEM_EVENT to user space API header Anup Patel
2014-03-31 10:46 ` [PATCH v6 07/12] ARM/ARM64: KVM: Emulate PSCI v0.2 SYSTEM_OFF and SYSTEM_RESET Anup Patel
2014-03-31 10:46 ` [PATCH v6 08/12] ARM/ARM64: KVM: Emulate PSCI v0.2 AFFINITY_INFO Anup Patel
2014-03-31 10:46 ` [PATCH v6 09/12] ARM/ARM64: KVM: Emulate PSCI v0.2 MIGRATE_INFO_TYPE and related functions Anup Patel
2014-03-31 10:46 ` [PATCH v6 10/12] ARM/ARM64: KVM: Fix CPU_ON emulation for PSCI v0.2 Anup Patel
2014-03-31 10:46 ` [PATCH v6 11/12] ARM/ARM64: KVM: Emulate PSCI v0.2 CPU_SUSPEND Anup Patel
2014-03-31 17:40   ` Christoffer Dall
2014-04-01  5:14     ` Anup Patel
2014-03-31 10:46 ` [PATCH v6 12/12] ARM/ARM64: KVM: Advertise KVM_CAP_ARM_PSCI_0_2 to user space 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=20140331183629.GF4756@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 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).