On Sat, May 02, 2020 at 07:03:51PM +0530, Anshuman Khandual wrote: > ID_DFR0 based TraceFilt feature should not be exposed to guests. Hence lets > drop it. > > Cc: Catalin Marinas <[email protected]> > Cc: Will Deacon <[email protected]> > Cc: Marc Zyngier <[email protected]> > Cc: Mark Rutland <[email protected]> > Cc: James Morse <[email protected]> > Cc: Suzuki K Poulose <[email protected]> > Cc: [email protected] > Cc: [email protected] > > Suggested-by: Mark Rutland <[email protected]> > Reviewed-by: Suzuki K Poulose <[email protected]> > Signed-off-by: Anshuman Khandual <[email protected]> > --- > arch/arm64/kernel/cpufeature.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c > index 6d032fbe416f..51386dade423 100644 > --- a/arch/arm64/kernel/cpufeature.c > +++ b/arch/arm64/kernel/cpufeature.c > @@ -435,7 +435,6 @@ static const struct arm64_ftr_bits ftr_id_pfr1[] = { > }; > > static const struct arm64_ftr_bits ftr_id_dfr0[] = { > - ARM64_FTR_BITS(FTR_HIDDEN, FTR_STRICT, FTR_LOWER_SAFE, 28, 4, 0),
Hmm, this still confuses me. Is this not now FTR_NONSTRICT? Why is that ok? Will
