From: Bhupinder Thakur <bhupinder.thakur@linaro.org>
To: Julien Grall <julien.grall@arm.com>
Cc: xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH 01/12 v3] xen/arm: vpl011: Move vgic register access functions to vreg.h
Date: Mon, 22 May 2017 18:26:42 +0530 [thread overview]
Message-ID: <CACtJ1JQJr0JeEy73bPFb2PJuEn3Szfc8cUje_-pJjqgiQku9_g@mail.gmail.com> (raw)
In-Reply-To: <69429532-22ef-bdb3-a18b-8cd726e82e22@arm.com>
Hi Julien,
>
>> -static inline void vgic_reg##sz##_clearbits(uint##sz##_t *reg, \
>> - register_t bits, \
>> - const mmio_info_t *info) \
>> -{ \
>> - unsigned long tmp = *reg; \
>> - \
>> - vgic_reg_clearbits(&tmp, bits, info->gpa & offmask, \
>> - info->dabt.size); \
>> - \
>> - *reg = tmp; \
>> -}
>> -
>> /*
>> * 64 bits registers are only supported on platform with 64-bit long.
>> * This is also allow us to optimize the 32 bit case by using
>
>
> Can you explain why you didn't move the definition of the helpers below? E.g
>
Earlier I was thinking of providing a macro which different modules
could call to define macros such as
vgic_*, vpl011_*. But later it was to be used as vreg_* irrespective
of which module is using these macros.
So now, the macro calls can be moved to vreg.h as they need not be
defined differently for each module.
> /*
> * 64 bits registers are only supported on platform with 64-bit long.
> * This is also allow us to optimize the 32 bit case by using
> * unsigned long rather than uint64_t
> */
> #if BITS_PER_LONG == 64
> VGIC_REG_HELPERS(64, 0x7);
> #endif
> VGIC_REG_HELPERS(32, 0x3);
>
> #undef VGIC_REG_HELPERS
>
Regards,
Bhupinder
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-05-22 12:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 14:24 [PATCH 01/12 v3] xen/arm: vpl011: Move vgic register access functions to vreg.h Bhupinder Thakur
2017-05-10 14:24 ` [PATCH 02/12 v3] xen/arm: vpl011: Define generic vreg_reg* access functions in vreg.h Bhupinder Thakur
2017-05-22 12:21 ` Julien Grall
2017-05-23 6:14 ` Bhupinder Thakur
2017-05-10 14:24 ` [PATCH 03/12 v3] xen/arm: vpl011: Add pl011 uart emulation in Xen Bhupinder Thakur
2017-05-16 22:42 ` Stefano Stabellini
2017-05-22 14:24 ` Julien Grall
2017-05-26 13:42 ` Bhupinder Thakur
2017-05-29 7:13 ` Bhupinder Thakur
2017-05-29 18:26 ` Julien Grall
2017-06-01 13:34 ` Bhupinder Thakur
2017-06-01 13:56 ` Julien Grall
2017-06-01 10:33 ` Bhupinder Thakur
2017-06-01 12:42 ` Julien Grall
2017-05-22 12:18 ` [PATCH 01/12 v3] xen/arm: vpl011: Move vgic register access functions to vreg.h Julien Grall
2017-05-22 12:56 ` Bhupinder Thakur [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=CACtJ1JQJr0JeEy73bPFb2PJuEn3Szfc8cUje_-pJjqgiQku9_g@mail.gmail.com \
--to=bhupinder.thakur@linaro.org \
--cc=julien.grall@arm.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).