On 30/01/18 14:56, Dave Martin wrote:
On Tue, Jan 30, 2018 at 11:17:38AM +, Suzuki K Poulose wrote:
On 26/01/18 10:10, Dave Martin wrote:
On Tue, Jan 23, 2018 at 12:27:58PM +, Suzuki K Poulose wrote:
Add two different flags to indicate if the conflict of a capability
on a late CPU with
On Tue, Jan 30, 2018 at 11:17:38AM +, Suzuki K Poulose wrote:
> On 26/01/18 10:10, Dave Martin wrote:
> >On Tue, Jan 23, 2018 at 12:27:58PM +, Suzuki K Poulose wrote:
> >>Add two different flags to indicate if the conflict of a capability
> >>on a late CPU with the current system state
> >>
On 26/01/18 10:10, Dave Martin wrote:
On Tue, Jan 23, 2018 at 12:27:58PM +, Suzuki K Poulose wrote:
Add two different flags to indicate if the conflict of a capability
on a late CPU with the current system state
1) Can a CPU have a capability when the system doesn't have it ?
Most a
On Tue, Jan 23, 2018 at 12:27:58PM +, Suzuki K Poulose wrote:
> Add two different flags to indicate if the conflict of a capability
> on a late CPU with the current system state
>
> 1) Can a CPU have a capability when the system doesn't have it ?
>
> Most arm64 features could have this s
Add two different flags to indicate if the conflict of a capability
on a late CPU with the current system state
1) Can a CPU have a capability when the system doesn't have it ?
Most arm64 features could have this set. While erratum work arounds
cannot have this, as we may miss work aroun
5 matches
Mail list logo
