From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 11/14] ARM64: KVM: fix vgic_bitmap_get_reg function for BE 64bit case
Date: Mon, 26 May 2014 17:49:10 +0200 [thread overview]
Message-ID: <20140526154910.GC31431@lvm> (raw)
In-Reply-To: <1399997646-4716-12-git-send-email-victor.kamensky@linaro.org>
On Tue, May 13, 2014 at 09:14:03AM -0700, Victor Kamensky wrote:
> Fix vgic_bitmap_get_reg function to return 'right' word address of
> 'unsigned long' bitmap value in case of BE 64bit image.
>
> Signed-off-by: Victor Kamensky <victor.kamensky@linaro.org>
> ---
> virt/kvm/arm/vgic.c | 24 ++++++++++++++++++++++--
> 1 file changed, 22 insertions(+), 2 deletions(-)
>
> diff --git a/virt/kvm/arm/vgic.c b/virt/kvm/arm/vgic.c
> index 529c336..d0a1a24 100644
> --- a/virt/kvm/arm/vgic.c
> +++ b/virt/kvm/arm/vgic.c
> @@ -101,14 +101,34 @@ static u32 vgic_nr_lr;
>
> static unsigned int vgic_maint_irq;
>
> +/*
> + * struct vgic_bitmap contains union that provides two view of
it contains two unions, so:
...contains unions that provide
s/two view/two views/
> + * the same data. In one case it is an array of registers of
> + * u32 type (.reg), and in the other case it is a bitmape, which is
s/bitmape/bitmap/
> + * an array of 'unsgined long' (.reg_ul). It all works well in
> + * case of 32-bit (u32 and 'unsigned long' have the same size).
"in case of 32-bit" is too vague. Write 'on 32-bit systems' if that's
what you mean.
> + * It alos works well in 64-bit LE, but breaks on 64-bit BE.
s/alos/also/
same with "in 64-bit" as above.
> + * In this case word sized register of even index actually resides
the word sized register
> + * in least significant word of 'unsigned long' which has address
in the least significant word of the 'unsigned long' at the register
offset plus 4 bytes.
> + * at offset plus 4 bytes. And word sized register of odd index
the
> + * resides at most significant of 'unsigned long' which has offset
> + * minus 4 bytes. Define REG_OFFSET_SWIZZLE that would help to
> + * change offset of register in case of BE 64bit system.
> + */
I actually think this is quite hard to understand, how about:
/*
* struct vgic_bitmap contains unions that provide two views of
* the same data. In one case it is an array of registers of
* u32's, and in the other case it is a bitmap of unsigned
* longs.
*
* This does not work on 64-bit BE systems, because the bitmap access
* will store two consecutive 32-bit words with the higher-addressed
* register's bits at the lower index and the lower-addressed register's
* bits at the higher index.
*
* Therefore, swizzle the register index when accessing the 32-bit word
* registers to access the right register's value.
*/
> +#if defined(CONFIG_CPU_BIG_ENDIAN) && BITS_PER_LONG == 64
> +#define REG_OFFSET_SWIZZLE 1
> +#else
> +#define REG_OFFSET_SWIZZLE 0
> +#endif
> +
> static u32 *vgic_bitmap_get_reg(struct vgic_bitmap *x,
> int cpuid, u32 offset)
> {
> offset >>= 2;
> if (!offset)
> - return x->percpu[cpuid].reg;
> + return x->percpu[cpuid].reg + (offset ^ REG_OFFSET_SWIZZLE);
> else
> - return x->shared.reg + offset - 1;
> + return x->shared.reg + ((offset - 1) ^ REG_OFFSET_SWIZZLE);
> }
>
> static int vgic_bitmap_get_irq_val(struct vgic_bitmap *x,
> --
> 1.8.1.4
>
next prev parent reply other threads:[~2014-05-26 15:49 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 16:13 [PATCH v3 00/14] ARM/ARM64: KVM: big endian host support Victor Kamensky
2014-05-13 16:13 ` [PATCH v3 01/14] ARM: KVM: switch hypervisor into BE mode in case of BE host Victor Kamensky
2014-05-27 14:23 ` Marc Zyngier
2014-05-13 16:13 ` [PATCH v3 02/14] ARM: KVM: fix vgic V7 assembler code to work in BE image Victor Kamensky
2014-05-27 14:24 ` Marc Zyngier
2014-05-13 16:13 ` [PATCH v3 03/14] ARM: KVM: handle 64bit values passed to mrcc or from mcrr instructions in BE case Victor Kamensky
2014-05-26 15:28 ` Christoffer Dall
2014-05-28 6:09 ` Victor Kamensky
2014-05-27 14:30 ` Marc Zyngier
2014-05-13 16:13 ` [PATCH v3 04/14] ARM: KVM: __kvm_vcpu_run function return result fix " Victor Kamensky
2014-05-27 15:02 ` Marc Zyngier
2014-05-28 6:10 ` Victor Kamensky
2014-05-13 16:13 ` [PATCH v3 05/14] ARM: KVM: vgic mmio should hold data as LE bytes array " Victor Kamensky
2014-05-27 15:07 ` Marc Zyngier
2014-05-13 16:13 ` [PATCH v3 06/14] ARM: KVM: MMIO support BE host running LE code Victor Kamensky
2014-05-27 15:49 ` Marc Zyngier
2014-05-13 16:13 ` [PATCH v3 07/14] ARM: KVM: one_reg coproc set and get BE fixes Victor Kamensky
2014-05-25 19:14 ` Christoffer Dall
2014-05-28 6:19 ` Victor Kamensky
2014-05-28 8:03 ` Christoffer Dall
2014-05-27 18:22 ` Marc Zyngier
2014-05-28 6:23 ` Victor Kamensky
2014-05-13 16:14 ` [PATCH v3 08/14] ARM: KVM: enable KVM in Kconfig on big-endian systems Victor Kamensky
2014-05-13 16:14 ` [PATCH v3 09/14] ARM64: KVM: MMIO support BE host running LE code Victor Kamensky
2014-05-27 18:25 ` Marc Zyngier
2014-05-13 16:14 ` [PATCH v3 10/14] ARM64: KVM: store kvm_vcpu_fault_info est_el2 as word Victor Kamensky
2014-05-27 18:34 ` Marc Zyngier
2014-05-13 16:14 ` [PATCH v3 11/14] ARM64: KVM: fix vgic_bitmap_get_reg function for BE 64bit case Victor Kamensky
2014-05-26 15:49 ` Christoffer Dall [this message]
2014-05-13 16:14 ` [PATCH v3 12/14] ARM64: KVM: vgic_elrsr and vgic_eisr need to be byteswapped in BE case Victor Kamensky
2014-05-26 17:35 ` Christoffer Dall
2014-05-27 19:11 ` Marc Zyngier
2014-05-13 16:14 ` [PATCH v3 13/14] ARM64: KVM: set and get of sys registers " Victor Kamensky
2014-05-14 8:45 ` Marc Zyngier
2014-05-14 14:18 ` Victor Kamensky
2014-05-25 18:26 ` Christoffer Dall
2014-05-13 16:14 ` [PATCH v3 14/14] ARM64: KVM: fix big endian issue in access_vm_reg for 32bit guest Victor Kamensky
2014-05-26 17:52 ` Christoffer Dall
2014-05-28 6:11 ` Victor Kamensky
2014-05-28 9:14 ` Christoffer Dall
2014-05-28 13:56 ` Victor Kamensky
2014-05-28 14:09 ` Christoffer Dall
2014-05-28 14:20 ` Marc Zyngier
2014-05-26 15:49 ` [PATCH v3 00/14] ARM/ARM64: KVM: big endian host support Christoffer Dall
2014-05-28 6:31 ` Victor Kamensky
2014-05-28 8:12 ` Christoffer Dall
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=20140526154910.GC31431@lvm \
--to=christoffer.dall@linaro.org \
--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).