All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Wei Chen <wei.chen@linaro.org>, xen-devel@lists.xen.org
Cc: sstabellini@kernel.org, steve.capper@arm.com
Subject: Re: [PATCH 0/4] xen/arm: arm64: Widen register access to mpidr to 64-bits
Date: Wed, 25 May 2016 14:41:14 +0100	[thread overview]
Message-ID: <5745AB7A.2000206@arm.com> (raw)
In-Reply-To: <1464142131-32636-1-git-send-email-Wei.Chen@linaro.org>

Hi Wei,

Please try to send all the patches with the cover letter as references. 
git send-email should do it if you send all the patches at once.

This is really helpful to with mail client supporting thread.

Regards,

On 25/05/16 03:08, Wei Chen wrote:
> In ARM64 the MPIDR register is mapped to MPIDR_EL1, and the register
> bits are expanded to 64-bits. But Xen 64-bit ARM code treats this it
> as 32-bit register.
> We have to provide correct accessing to this register to avoid
> unexpected issues that is caused by incorrect MPIDR value.
>
> Wei Chen (4):
>    xen/arm: Change the variable type of cpu_logical_map to register_t
>    xen/arm: Make AFFINITY_MASK generate correct mask for level3
>    xen:arm: arm64: Add correct MPIDR_HWID_MASK value for ARM64
>    xen/arm: arm64: Remove MPIDR multiprocessing extensions check
>
>   xen/arch/arm/arm64/head.S       |  3 +--
>   xen/arch/arm/gic-v3.c           |  2 +-
>   xen/arch/arm/smpboot.c          | 13 +++++++------
>   xen/include/asm-arm/processor.h |  9 +++++++--
>   4 files changed, 16 insertions(+), 11 deletions(-)
>

-- 
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

      reply	other threads:[~2016-05-25 13:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-25  2:08 [PATCH 0/4] xen/arm: arm64: Widen register access to mpidr to 64-bits Wei Chen
2016-05-25 13:41 ` Julien Grall [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5745AB7A.2000206@arm.com \
    --to=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=steve.capper@arm.com \
    --cc=wei.chen@linaro.org \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.