[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150305112707.GB7712@e104818-lin.cambridge.arm.com>
Date: Thu, 5 Mar 2015 11:27:08 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Hanjun Guo <guohanjun@...wei.com>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Hanjun Guo <hanjun.guo@...aro.org>,
Mark Rutland <mark.rutland@....com>,
Ashwin Chaugule <ashwinc@...eaurora.org>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
Robert Richter <rric@...nel.org>,
Graeme Gregory <graeme.gregory@...aro.org>,
Arnd Bergmann <arnd@...db.de>, linux-acpi@...r.kernel.org,
Marc Zyngier <marc.zyngier@....com>,
Timur Tabi <timur@...eaurora.org>,
linaro-acpi@...ts.linaro.org, Will Deacon <will.deacon@....com>,
linux-kernel@...r.kernel.org,
Grant Likely <grant.likely@...aro.org>,
Mark Brown <broonie@...nel.org>,
linux-arm-kernel@...ts.infradead.org,
suravee.suthikulpanit@....com, Sudeep Holla <Sudeep.Holla@....com>,
Olof Johansson <olof@...om.net>, Jon Masters <jcm@...hat.com>
Subject: Re: [PATCH v9 14/21] ACPI / processor: Make it possible to get CPU
hardware ID via GICC
On Thu, Mar 05, 2015 at 04:03:21PM +0800, Hanjun Guo wrote:
> On 2015/3/5 6:46, Rafael J. Wysocki wrote:
> > IMO, you really need to define phys_cpuid_t in a common place or people will
> > forget that it may be 64-bit, because they'll only be looking at their arch.
>
> Since x86 and ARM64 are using different types for phys_cpuid_t, we need to
> introduce something like following if define it in common place:
>
> in linux/acpi.h,
>
> #if defined(CONFIG_X86) || defined(CONFIG_IA64)
> typedef u32 phys_cpuid_t;
> #define PHYS_CPUID_INVALID (phys_cpuid_t)(-1)
> #else if defined(CONFIG_ARM64)
> typedef u64 phys_cpuid_t;
> #define PHYS_CPUID_INVALID INVALID_HWID
> #endif
>
> I think it's awful, did I miss something?
I also think that's awful. I'm rather in favour of a per-arch
phys_cpuid_t.
--
Catalin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists