On Wed, Mar 26, 2014 at 10:32 AM, Ashwin Chaugule
[off-list ref] wrote:

Hello,

On 24 March 2014 09:26, Rob Herring [off-list ref] wrote:

quoted

quoted

quoted

My suggestion would be to have:
arch/arm/include/uapi/asm/psci.h
arch/arm64/include/uapi/asm/psci.h

I think the suggestion was to move all this to include/uapi/linux/psci.h
or something equivalent so also arm and arm64 can share these defines,
but maybe I read too much into it.

Yes. It is perfectly fine for a somewhat architecture specific header
to live in include/linux (or include/uapi/linux).

While I'm aware that we wouldn't want to push seemingly irrelevant
stuff into this header, I'm thinking of ways to unify the ARM and
ARM64 PSCI code. A lot of it is reusable between the two.
So, can this header also include all the common PSCI functions between
ARM and ARM64? And can KVM possibly use these functions as well?

Anything under uapi should be related to the PSCI ABI. If there are
headers to be shared that are just kernel implementation specific,
then they can go in include/linux/.

Alternately, is drivers/psci.c a more suitable place? In this case, at
least one function will be guarded by CONFIG_ARM64.

No. For .c files, I don't think we have a good solution. Some of the
kvm stuff does ../../ type includes back to arch/arm, but that's not a
very clean solution.

Rob