Hi,
> On 20 Jan 2021, at 17:58, Julien Grall wrote:
>
> On 08/01/2021 11:50, Wei Chen wrote:
>> Hi Julien
>
> Hi Wei,
>
> Sorry for the late answer. While cleaning my inbox today, I noticied that I
> didn't reply to this thread :(.
>
integer will do unsigned extend while doing some oper
On 08/01/2021 11:50, Wei Chen wrote:
Hi Julien
Hi Wei,
Sorry for the late answer. While cleaning my inbox today, I noticied
that I didn't reply to this thread :(.
integer will do unsigned extend while doing some operations
with 64-bit unsigned integer. This can lead to unexpected
result in
Hi Julien
> -Original Message-
> From: Julien Grall
> Sent: 2021年1月8日 19:46
> To: Wei Chen ; xen-devel@lists.xenproject.org;
> sstabell...@kernel.org
> Cc: Bertrand Marquis ; Penny Zheng
> ; Jiamei Xie ; nd
>
> Subject: Re: [PATCH v2] xen/arm: Using unsigne
Hi Wei,
How about the following title:
"xen/arm: Don't ignore the affinity level 3 in the MPIDR"
On 08/01/2021 06:29, Wei Chen wrote:
Currently, Xen is using UINT32 for MPIDR mask to retrieve
affinity[0,1,2,3] values for MPIDR_EL1 register. The value
of MPIDR_EL1 is 64-bit unsigned long. > The
Currently, Xen is using UINT32 for MPIDR mask to retrieve
affinity[0,1,2,3] values for MPIDR_EL1 register. The value
of MPIDR_EL1 is 64-bit unsigned long. The 32-bit unsinged
integer will do unsigned extend while doing some operations
with 64-bit unsigned integer. This can lead to unexpected
result
