On Wed, Feb 07, 2018 at 03:16:39PM +, Suzuki K Poulose wrote:
> On 07/02/18 10:37, Dave Martin wrote:
> >On Wed, Jan 31, 2018 at 06:27:51PM +, Suzuki K Poulose wrote:
[...]
> >>As such there is no change in how the capabilities are treated.
> >>
> >>Cc: Dave Martin
> >>Signed-off-by: Suz
On 07/02/18 10:37, Dave Martin wrote:
On Wed, Jan 31, 2018 at 06:27:51PM +, Suzuki K Poulose wrote:
We use arm64_cpu_capabilities to represent CPU ELF HWCAPs exposed
to the userspace and the CPU hwcaps used by the kernel, which
include cpu features and CPU errata work arounds. Capabilities
h
On Wed, Jan 31, 2018 at 06:27:51PM +, Suzuki K Poulose wrote:
> We use arm64_cpu_capabilities to represent CPU ELF HWCAPs exposed
> to the userspace and the CPU hwcaps used by the kernel, which
> include cpu features and CPU errata work arounds. Capabilities
> have some properties that decide h
We use arm64_cpu_capabilities to represent CPU ELF HWCAPs exposed
to the userspace and the CPU hwcaps used by the kernel, which
include cpu features and CPU errata work arounds. Capabilities
have some properties that decide how they should be treated :
1) Detection, i.e scope : A cap could be "de
4 matches
Mail list logo
