On Wed, Feb 07, 2018 at 06:15:58PM +, Suzuki K Poulose wrote:
> On 07/02/18 10:38, Dave Martin wrote:
> >On Wed, Jan 31, 2018 at 06:27:57PM +, Suzuki K Poulose wrote:
> >>KPTI is treated as a system wide feature, where we enable the feature
> >>when all the CPUs on the system suffers from
On Wed, Feb 07, 2018 at 06:15:58PM +, Suzuki K Poulose wrote:
> On 07/02/18 10:38, Dave Martin wrote:
> >On Wed, Jan 31, 2018 at 06:27:57PM +, Suzuki K Poulose wrote:
> >>KPTI is treated as a system wide feature, where we enable the feature
> >>when all the CPUs on the system suffers from
On 07/02/18 10:38, Dave Martin wrote:
On Wed, Jan 31, 2018 at 06:27:57PM +, Suzuki K Poulose wrote:
KPTI is treated as a system wide feature, where we enable the feature
when all the CPUs on the system suffers from the security vulnerability,
Should that be "when any CPU"?
Without this
On 07/02/18 10:38, Dave Martin wrote:
On Wed, Jan 31, 2018 at 06:27:57PM +, Suzuki K Poulose wrote:
KPTI is treated as a system wide feature, where we enable the feature
when all the CPUs on the system suffers from the security vulnerability,
Should that be "when any CPU"?
Without this
On Wed, Jan 31, 2018 at 06:27:57PM +, Suzuki K Poulose wrote:
> KPTI is treated as a system wide feature, where we enable the feature
> when all the CPUs on the system suffers from the security vulnerability,
Should that be "when any CPU"?
> unless it is forced via kernel command line. Also,
On Wed, Jan 31, 2018 at 06:27:57PM +, Suzuki K Poulose wrote:
> KPTI is treated as a system wide feature, where we enable the feature
> when all the CPUs on the system suffers from the security vulnerability,
Should that be "when any CPU"?
> unless it is forced via kernel command line. Also,
6 matches
Mail list logo