qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Shashi Mallela <shashi.mallela@linaro.org>
Cc: Leif Lindholm <leif@nuviainc.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	qemu-arm <qemu-arm@nongnu.org>,
	Radoslaw Biernacki <rad@semihalf.com>
Subject: Re: [PATCH 1/2] hw/intc: GICv3 ITS implementation
Date: Tue, 16 Mar 2021 16:15:41 +0000	[thread overview]
Message-ID: <CAFEAcA8q9sS-ob7XDKh62OX-R=5icXbhSTqD64KB-K+=yg2gOQ@mail.gmail.com> (raw)
In-Reply-To: <20210315164931.23477-1-shashi.mallela@linaro.org>

On Mon, 15 Mar 2021 at 16:49, Shashi Mallela <shashi.mallela@linaro.org> wrote:
>
> Implementation of Interrupt Translation Service which allows eventid
> from devices to be translated to physical LPI IntIds.Extended the
> redistributor functionality to process LPI Interrupts as well.
>
> Signed-off-by: Shashi Mallela <shashi.mallela@linaro.org>
> ---
>  hw/intc/arm_gicv3.c                    |    6 +
>  hw/intc/arm_gicv3_common.c             |   20 +-
>  hw/intc/arm_gicv3_cpuif.c              |   15 +-
>  hw/intc/arm_gicv3_dist.c               |   22 +-
>  hw/intc/arm_gicv3_its.c                | 1386 ++++++++++++++++++++++++
>  hw/intc/arm_gicv3_its_common.c         |   17 +-
>  hw/intc/arm_gicv3_its_kvm.c            |    2 +-
>  hw/intc/arm_gicv3_redist.c             |  163 ++-
>  hw/intc/gicv3_internal.h               |  169 ++-
>  hw/intc/meson.build                    |    1 +
>  include/hw/intc/arm_gicv3_common.h     |   13 +
>  include/hw/intc/arm_gicv3_its_common.h |   12 +-
>  12 files changed, 1807 insertions(+), 19 deletions(-)
>  create mode 100644 hw/intc/arm_gicv3_its.c

Hi; thanks for posting this. Unfortuantely 1800 lines is much
too large a patch to be reviewable. Could you split the series
up into smaller pieces, please? One possible structure would be
to have a patch with the framework of the device but no actual
implementation of register behaviour or command handling,
followed by patches which add the behaviour piece by piece,
and then finally the patch adding it to the board.

I think it would also be useful to have the virt board
support, as a demonstration that the emulated ITS and
the KVM ITS have the same interface to the board code
and are basically drop-in-replacements.

Finally, for multi-patch series, please always send a cover letter
(the "0/5" email, which the other patch emails are followups to;
git format-patch should do this for you).

thanks
-- PMM


  parent reply	other threads:[~2021-03-16 16:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 16:49 [PATCH 1/2] hw/intc: GICv3 ITS implementation Shashi Mallela
2021-03-15 16:49 ` [PATCH 2/2] hw/arm/sbsa-ref: add ITS support in SBSA GIC Shashi Mallela
2021-03-16 16:15 ` Peter Maydell [this message]
2021-03-23  4:17   ` [PATCH 1/2] hw/intc: GICv3 ITS implementation shashi.mallela

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='CAFEAcA8q9sS-ob7XDKh62OX-R=5icXbhSTqD64KB-K+=yg2gOQ@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=leif@nuviainc.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rad@semihalf.com \
    --cc=shashi.mallela@linaro.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).