[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <561BE765.1080409@arm.com>
Date: Mon, 12 Oct 2015 18:01:25 +0100
From: "Suzuki K. Poulose" <Suzuki.Poulose@....com>
To: mark.rutland@....com
Cc: Catalin Marinas <catalin.marinas@....com>, Vladimir.Murzin@....com,
steve.capper@...aro.org, ard.biesheuvel@...aro.org,
marc.zyngier@....com, andre.przywara@....com, will.deacon@....com,
linux-kernel@...r.kernel.org, edward.nevill@...aro.org,
aph@...hat.com, james.morse@....com, dave.martin@....com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v2 07/22] arm64: Keep track of CPU feature registers
On 08/10/15 16:03, Catalin Marinas wrote:
> On Thu, Oct 08, 2015 at 10:55:11AM +0100, Suzuki K. Poulose wrote:
...
>
> So we have three types of fields in these registers:
>
> a) features defined but not something we care about in Linux
> b) reserved fields
> c) features important to Linux
>
> I guess for (a), Linux may not even care if they don't match (though we
> need to be careful which fields we ignore). As for (b), even if they
> differ, since we don't know the meaning at this point, I think we should
> just ignore them. If, for example, they add a feature that Linux doesn't
> care about, they practically fall under the (a) category.
>
> Regarding exposing reserved CPUID fields to user, I assume we would
> always return 0.
Mark,
Do you have any comments on this ? The list I have here is what you came
up with in SANITY checks.
Thanks
Suzuki
--
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