All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Bhupinder Thakur <bhupinder.thakur@linaro.org>,
	xen-devel@lists.xenproject.org
Cc: 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 13:18:19 +0100	[thread overview]
Message-ID: <69429532-22ef-bdb3-a18b-8cd726e82e22@arm.com> (raw)
In-Reply-To: <1494426293-32481-1-git-send-email-bhupinder.thakur@linaro.org>

Hi Bhupinder,

On 10/05/17 15:24, Bhupinder Thakur wrote:
> These functions are generic in nature and can be reused by other emulation
> code in Xen. One recent example is pl011 emulation, which needs similar
> funictions to read/write the registers.

s/funictions/functions/

[...]

> -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

/*
  * 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

Cheers,

-- 
Julien Grall

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

  parent reply	other threads:[~2017-05-22 12:18 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 ` Julien Grall [this message]
2017-05-22 12:56   ` [PATCH 01/12 v3] xen/arm: vpl011: Move vgic register access functions to vreg.h Bhupinder Thakur

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=69429532-22ef-bdb3-a18b-8cd726e82e22@arm.com \
    --to=julien.grall@arm.com \
    --cc=bhupinder.thakur@linaro.org \
    --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 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.