On Fri, 28 Apr 2023 at 08:45, Richard Henderson
wrote:
>
> On 4/27/23 14:16, Fabiano Rosas wrote:
> > Richard Henderson writes:
> >
> >> On 4/26/23 19:00, Fabiano Rosas wrote:
> >>> We're about to move the 32-bit CPUs under CONFIG_TCG, so adjust the
> >>> query-cpu-model-expansion test to check
Richard Henderson writes:
> On 4/27/23 14:16, Fabiano Rosas wrote:
>> Richard Henderson writes:
>>
>>> On 4/26/23 19:00, Fabiano Rosas wrote:
We're about to move the 32-bit CPUs under CONFIG_TCG, so adjust the
query-cpu-model-expansion test to check against the cortex-a7, which
On 4/27/23 14:16, Fabiano Rosas wrote:
Richard Henderson writes:
On 4/26/23 19:00, Fabiano Rosas wrote:
We're about to move the 32-bit CPUs under CONFIG_TCG, so adjust the
query-cpu-model-expansion test to check against the cortex-a7, which
is already under CONFIG_TCG. That allows the next
Richard Henderson writes:
> On 4/26/23 19:00, Fabiano Rosas wrote:
>> We're about to move the 32-bit CPUs under CONFIG_TCG, so adjust the
>> query-cpu-model-expansion test to check against the cortex-a7, which
>> is already under CONFIG_TCG. That allows the next patch to contain
>> only code
On 4/26/23 19:00, Fabiano Rosas wrote:
We're about to move the 32-bit CPUs under CONFIG_TCG, so adjust the
query-cpu-model-expansion test to check against the cortex-a7, which
is already under CONFIG_TCG. That allows the next patch to contain
only code movement.
While here add comments
On 26/04/2023 20.00, Fabiano Rosas wrote:
We're about to move the 32-bit CPUs under CONFIG_TCG, so adjust the
query-cpu-model-expansion test to check against the cortex-a7, which
is already under CONFIG_TCG. That allows the next patch to contain
only code movement.
While here add comments
We're about to move the 32-bit CPUs under CONFIG_TCG, so adjust the
query-cpu-model-expansion test to check against the cortex-a7, which
is already under CONFIG_TCG. That allows the next patch to contain
only code movement.
While here add comments clarifying what we're testing.
Signed-off-by:
