Re: [PATCH v3 21/22] arm64: Delay enabling hardware DBM feature

2018-03-08 Thread Mark Rutland
On Thu, Mar 08, 2018 at 01:53:13PM +, Dave Martin wrote: > In practice, we don't race booting of two CPUs against each other > IIUC. Yup. Today, hotplugs are strictly serialized. Several things would have to change for parallel hotplug to be feasible. Thanks, Mark.

Re: [PATCH v3 21/22] arm64: Delay enabling hardware DBM feature

2018-03-08 Thread Dave Martin
On Wed, Mar 07, 2018 at 05:39:09PM +, Suzuki K Poulose wrote: > On 09/02/18 18:58, Dave Martin wrote: > >On Fri, Feb 09, 2018 at 05:55:12PM +, Suzuki K Poulose wrote: > >>We enable hardware DBM bit in a capable CPU, very early in the > >>boot via __cpu_setup. This doesn't give us a flexibil

Re: [PATCH v3 21/22] arm64: Delay enabling hardware DBM feature

2018-03-07 Thread Suzuki K Poulose
On 09/02/18 18:58, Dave Martin wrote: On Fri, Feb 09, 2018 at 05:55:12PM +, Suzuki K Poulose wrote: We enable hardware DBM bit in a capable CPU, very early in the boot via __cpu_setup. This doesn't give us a flexibility of optionally disable the feature, as the clearing the bit is a bit cost

Re: [PATCH v3 21/22] arm64: Delay enabling hardware DBM feature

2018-02-09 Thread Dave Martin
On Fri, Feb 09, 2018 at 05:55:12PM +, Suzuki K Poulose wrote: > We enable hardware DBM bit in a capable CPU, very early in the > boot via __cpu_setup. This doesn't give us a flexibility of > optionally disable the feature, as the clearing the bit > is a bit costly as the TLB can cache the setti

[PATCH v3 21/22] arm64: Delay enabling hardware DBM feature

2018-02-09 Thread Suzuki K Poulose
We enable hardware DBM bit in a capable CPU, very early in the boot via __cpu_setup. This doesn't give us a flexibility of optionally disable the feature, as the clearing the bit is a bit costly as the TLB can cache the settings. Instead, we delay enabling the feature until the CPU is brought up in