On Tue, 12 Jan 2021 at 21:05, Stefano Stabellini wrote:
>
> On Tue, 12 Jan 2021, Julien Grall wrote:
> > On Tue, 12 Jan 2021 at 19:09, Stefano Stabellini
> > wrote:
> > >
> > > On Tue, 12 Jan 2021, Julien Grall wrote:
> > > > > +aarch32 = c->pfr64.el1 == 2;
> > > >
> > > > This is checking t
On Tue, 12 Jan 2021, Julien Grall wrote:
> On Tue, 12 Jan 2021 at 19:09, Stefano Stabellini
> wrote:
> >
> > On Tue, 12 Jan 2021, Julien Grall wrote:
> > > > +aarch32 = c->pfr64.el1 == 2;
> > >
> > > This is checking that AArch32 is available in EL1. However, it may not be
> > > the
> > > ca
On Tue, 12 Jan 2021 at 19:09, Stefano Stabellini wrote:
>
> On Tue, 12 Jan 2021, Julien Grall wrote:
> > > +aarch32 = c->pfr64.el1 == 2;
> >
> > This is checking that AArch32 is available in EL1. However, it may not be
> > the
> > case yet it would be available in EL0.
> >
> > As a consequenc
On Tue, 12 Jan 2021, Julien Grall wrote:
> > +aarch32 = c->pfr64.el1 == 2;
>
> This is checking that AArch32 is available in EL1. However, it may not be the
> case yet it would be available in EL0.
>
> As a consequence, 32-bit userspace wouldn't work properly after this patch.
>
> The Arm Ar
Hi,
> On 12 Jan 2021, at 14:27, Julien Grall wrote:
>
>
>
> On 12/01/2021 13:28, Rahul Singh wrote:
>> Hello Julien,
>
> Hi Rahul,
>
>>> On 12 Jan 2021, at 11:00 am, Julien Grall wrote:
>>>
>>> Hi Stefano,
>>>
>>> On 12/01/2021 00:16, Stefano Stabellini wrote:
Don't read aarch32 syst
On 12/01/2021 13:28, Rahul Singh wrote:
Hello Julien,
Hi Rahul,
On 12 Jan 2021, at 11:00 am, Julien Grall wrote:
Hi Stefano,
On 12/01/2021 00:16, Stefano Stabellini wrote:
Don't read aarch32 system registers at boot time when the aarch32 state
is not available. They are UNKNOWN, so i
Hello Julien,
> On 12 Jan 2021, at 11:00 am, Julien Grall wrote:
>
> Hi Stefano,
>
> On 12/01/2021 00:16, Stefano Stabellini wrote:
>> Don't read aarch32 system registers at boot time when the aarch32 state
>> is not available. They are UNKNOWN, so it is not useful to read them.
>> Moreover, on
Hi Julien,
> On 12 Jan 2021, at 12:46, Julien Grall wrote:
>
>
>
> On 12/01/2021 10:50, Bertrand Marquis wrote:
>> Hi Stefano,
>>> On 12 Jan 2021, at 00:16, Stefano Stabellini wrote:
>>>
>>> Don't read aarch32 system registers at boot time when the aarch32 state
>>> is not available. They ar
On 12/01/2021 10:50, Bertrand Marquis wrote:
Hi Stefano,
On 12 Jan 2021, at 00:16, Stefano Stabellini wrote:
Don't read aarch32 system registers at boot time when the aarch32 state
is not available. They are UNKNOWN, so it is not useful to read them.
Moreover, on Cavium ThunderX reading ID
Hi Stefano,
On 12/01/2021 00:16, Stefano Stabellini wrote:
Don't read aarch32 system registers at boot time when the aarch32 state
is not available. They are UNKNOWN, so it is not useful to read them.
Moreover, on Cavium ThunderX reading ID_PFR2_EL1 causes a Xen crash.
Instead, only read them wh
Hi Stefano,
> On 12 Jan 2021, at 00:16, Stefano Stabellini wrote:
>
> Don't read aarch32 system registers at boot time when the aarch32 state
> is not available. They are UNKNOWN, so it is not useful to read them.
> Moreover, on Cavium ThunderX reading ID_PFR2_EL1 causes a Xen crash.
> Instead,
Don't read aarch32 system registers at boot time when the aarch32 state
is not available. They are UNKNOWN, so it is not useful to read them.
Moreover, on Cavium ThunderX reading ID_PFR2_EL1 causes a Xen crash.
Instead, only read them when aarch32 is available.
Leave the corresponding fields in st
12 matches
Mail list logo
