From: julien.grall@citrix.com (Julien Grall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/8] xen/arm: vgic: Support 32-bit access for 64-bit register
Date: Fri, 25 Sep 2015 15:52:30 +0100 [thread overview]
Message-ID: <56055FAE.70704@citrix.com> (raw)
In-Reply-To: <1443192667-16112-1-git-send-email-julien.grall@citrix.com>
Please ignore this version, I've sent it to the wrong mailing list.
Sorry for the noise.
On 25/09/15 15:50, Julien Grall wrote:
> Hi all,
>
> This series aims to fix the 32-bit access on 64-bit register. Some guest
> OS such as FreeBSD and Linux (only in the ITS) use 32-bit access and will
> crash at boot time.
>
> I took the opportunity to go further and optimize the way Xen is storing
> registers such as GICD_IPRIORITYR, GICD_ITARGETR and GICD_IROUTER.
>
> Major changes in v2:
> - Use the helpers in GICv2
> - Optimize the assembly input for vgic_regN_* helpers on arm32
> - Add support for sign-extension generically
> - Store GICD_{IPRIORITYR, ITARGETSR, IROUTER} in a better way
>
> For all the changes see in each patch.
>
> A branch has been pushed based on the lastest staging:
>
> git://xenbits.xen.org/people/julieng/xen-unstable.git branch gicv3-32bit-v1
>
> Sincerely yours,
>
> Julien Grall (8):
> xen/arm: io: remove mmio_check_t typedef
> xen/arm: io: Extend write/read handler to pass the register in
> parameter
> xen/arm: Support sign-extension for every read access
> xen/arm: vgic: ctlr stores a 32-bit hardware register so use uint32_t
> xen/arm: vgic: Optimize the way to store GICD_IPRIORITYR in the rank
> xen/arm: vgic: Optimize the way to store the target vCPU in the rank
> xen/arm: vgic: Introduce helpers to read/write/clear/set vGIC register
> ...
> xen/arm: vgic-v3: Support 32-bit access for 64-bit registers
>
> xen/arch/arm/io.c | 42 +++++-
> xen/arch/arm/vgic-v2.c | 295 +++++++++++++++++++++---------------
> xen/arch/arm/vgic-v3.c | 352 +++++++++++++++++++++++++------------------
> xen/arch/arm/vgic.c | 72 ++++++++-
> xen/arch/arm/vuart.c | 16 +-
> xen/include/asm-arm/domain.h | 2 +-
> xen/include/asm-arm/mmio.h | 5 +-
> xen/include/asm-arm/vgic.h | 148 +++++++++++++++---
> 8 files changed, 617 insertions(+), 315 deletions(-)
>
--
Julien Grall
prev parent reply other threads:[~2015-09-25 14:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 14:50 [PATCH v1 0/8] xen/arm: vgic: Support 32-bit access for 64-bit register Julien Grall
2015-09-25 14:51 ` [PATCH v1 1/8] xen/arm: io: remove mmio_check_t typedef Julien Grall
2015-09-25 14:51 ` [PATCH v1 2/8] xen/arm: io: Extend write/read handler to pass the register in parameter Julien Grall
2015-09-25 14:51 ` [PATCH v1 3/8] xen/arm: Support sign-extension for every read access Julien Grall
2015-09-25 14:51 ` [PATCH v1 4/8] xen/arm: vgic: ctlr stores a 32-bit hardware register so use uint32_t Julien Grall
2015-09-25 14:51 ` [PATCH v1 5/8] xen/arm: vgic: Optimize the way to store GICD_IPRIORITYR in the rank Julien Grall
2015-09-25 14:51 ` [PATCH v1 6/8] xen/arm: vgic: Optimize the way to store the target vCPU " Julien Grall
2015-09-25 14:51 ` [PATCH v1 7/8] xen/arm: vgic: Introduce helpers to read/write/clear/set vGIC register Julien Grall
2015-09-25 14:51 ` [PATCH v1 8/8] xen/arm: vgic-v3: Support 32-bit access for 64-bit registers Julien Grall
2015-09-25 14:52 ` 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=56055FAE.70704@citrix.com \
--to=julien.grall@citrix.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).