linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 1/2] arm: introduce psci_smp_ops
Date: Fri, 26 Apr 2013 17:10:12 +0100	[thread overview]
Message-ID: <20130426161012.GH30858@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1304261630110.4180@kaball.uk.xensource.com>

On Fri, Apr 26, 2013 at 04:36:26PM +0100, Stefano Stabellini wrote:
> On Thu, 25 Apr 2013, Nicolas Pitre wrote:
> > On Thu, 25 Apr 2013, Will Deacon wrote:
> > > I disagree. You're explicitly stating that we pass the `cpuid of target CPU,
> > > as from MPIDR'. That's simply not true -- the firmware could choose any
> > > numbering scheme to identify the CPUs. For KVM and Xen, it *is* the mpidr,
> > > which is why psci-smp.c works at all, but that's where the comment belongs,
> > > not in this header file.
> > 
> > At some point, the _kernel_ API for interfacing with the firmware's PSCI 
> > will have to ensure uniformity somehow.  The PSCI interface code could 
> > translate the passed MPIDR into whatever the firmware decided to use for 
> > identifying CPUs if needed, keeping this issue localized.
> 
> That is what I had in mind when I said to keep the comment in psci.h
> before.
> We have to draw the line somewhere to expose a uniform internal kernel
> API. However it is a bit difficult to do now given that we have only one
> user of the API.

I see psci.h as representing the firmware interface, and psci-smp.c or
whatever sits on top as exposing the kernel `API'.

> I don't feel to strongly about this, please let me know what is the
> final decision and I'll update the code accordingly. I remind you that
> the merge window is approaching :-)

I'd still like the comment to be in psci-smp.c, or a header separate from
the firmware bits.

Will

  reply	other threads:[~2013-04-26 16:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 18:38 [PATCH 0/2 v8] arm: introduce psci_smp_ops Stefano Stabellini
2013-04-24 18:40 ` [PATCH v8 1/2] " Stefano Stabellini
2013-04-25  8:47   ` Will Deacon
2013-04-25 10:12     ` Stefano Stabellini
2013-04-25 10:45       ` Will Deacon
2013-04-25 11:08         ` Stefano Stabellini
2013-04-25 11:11           ` Will Deacon
2013-04-25 11:13             ` Stefano Stabellini
2013-04-25 14:58         ` Nicolas Pitre
2013-04-26 15:36           ` Stefano Stabellini
2013-04-26 16:10             ` Will Deacon [this message]
2013-04-24 18:40 ` [PATCH v8 2/2] ARM: Enable selection of SMP operations at boot time Stefano Stabellini
2013-04-25  8:49   ` Will Deacon
2013-04-25 10:25     ` Stefano Stabellini
2013-04-25 14:42     ` Nicolas Pitre
2013-04-26 15:36       ` Stefano Stabellini

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=20130426161012.GH30858@mudshark.cambridge.arm.com \
    --to=will.deacon@arm.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).