On Mon, Jan 29, 2018 at 05:22:26PM +, Suzuki K Poulose wrote:
> On 29/01/18 17:14, Dave Martin wrote:
> >On Fri, Jan 26, 2018 at 12:31:18PM +, Suzuki K Poulose wrote:
> >>On 26/01/18 11:47, Dave Martin wrote:
> >>>On Tue, Jan 23, 2018 at 12:28:01PM +, Suzuki K Poulose wrote:
> So fa
On 29/01/18 17:14, Dave Martin wrote:
On Fri, Jan 26, 2018 at 12:31:18PM +, Suzuki K Poulose wrote:
On 26/01/18 11:47, Dave Martin wrote:
On Tue, Jan 23, 2018 at 12:28:01PM +, Suzuki K Poulose wrote:
So far we have had separate routes for triggering errata and feature
"triggering err
On Fri, Jan 26, 2018 at 12:31:18PM +, Suzuki K Poulose wrote:
> On 26/01/18 11:47, Dave Martin wrote:
> >On Tue, Jan 23, 2018 at 12:28:01PM +, Suzuki K Poulose wrote:
> >>So far we have had separate routes for triggering errata and feature
> >
> >"triggering errata" ? ;)
> >
>
> :-). Shoul
On 26/01/18 11:47, Dave Martin wrote:
On Tue, Jan 23, 2018 at 12:28:01PM +, Suzuki K Poulose wrote:
So far we have had separate routes for triggering errata and feature
"triggering errata" ? ;)
:-). Should have been "triggering errata and feature capability *checks*.
Maybe "[...] for
On Tue, Jan 23, 2018 at 12:28:01PM +, Suzuki K Poulose wrote:
> So far we have had separate routes for triggering errata and feature
"triggering errata" ? ;)
Maybe "[...] for determining whether to activate errata workarounds and
whether to enable feature capabilities."
> capabilities. Also,
So far we have had separate routes for triggering errata and feature
capabilities. Also, we never allowed "features" based on local CPU
and "errata" based on System wide safe registers. This patch
groups the handling of errata and features and also allows them
to have all the possible scopes.
So,
6 matches
Mail list logo
