On Wed, Sep 16, 2015 at 03:21:05PM +0100, Suzuki K. Poulose wrote: > From: "Suzuki K. Poulose" <[email protected]> > > This patch adds an infrastructure to keep track of the CPU feature > registers on the system. For each register, the infrastructure keeps > track of the system wide safe value of the feature bits. Also, tracks > the which fields of a register should be matched strictly across all > the CPUs on the system for the SANITY check infrastructure. > > The feature bits are classified as one of SCALAR_MIN, SCALAR_MAX and DISCRETE > depending on the implication of the possible values. This information > is used to decide the safe value for a feature. > > SCALAR_MIN - The smaller value is safer > SCALAR_MAX - The bigger value is safer > DISCRETE - We can't decide between the two, so a predefined safe_value is > used.
Can documentation of the meanings of these be added somewhere in the relevant header or in Documentation? Cheers ---Dave [...] -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
