From: Peter Maydell <peter.maydell@linaro.org>
To: Sergey Makarov <s.makarov@syntacore.com>
Cc: Alistar.Francis@wdc.com, bmeng@gmail.com, palmer@dabbelt.com,
qemu-riscv@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] Fixes for standard conformance
Date: Thu, 12 Sep 2024 09:15:02 +0100 [thread overview]
Message-ID: <CAFEAcA_RsAeh-9bAkAX0heMb1PcqqbVe4m0FPDhq8KqiKE9YDA@mail.gmail.com> (raw)
In-Reply-To: <20240911131900.179648-1-s.makarov@syntacore.com>
On Wed, 11 Sept 2024 at 23:30, Sergey Makarov <s.makarov@syntacore.com> wrote:
>
> *** Patchset goal ***
>
> This patchset aims to improve standard conformance for SiFive PLIC
> implementation.
>
> *** Testing cases ***
>
> Currently there are no automated tests for these changes, but there
> are several test cases, with which these changes may be checked:
> 1. Zeroth priority register can be checked by reading it after
> writing to it. Without patch its value would be the same which
> is written there, but with it it would be zero;
> 2. Trigger call of `sifive_plic_irq_request` with level 0.
> Without second patch it will clear pending bit, but with it
> pending bit won't be cleared.
> If anyone knows how this can be turned into automated test, help
> would be appreciated.
>
> Sergey Makarov (2):
> hw/intc: Make zeroth priority register read-only
> hw/intc: Don't clear pending bits on IRQ lowering
>
> hw/intc/sifive_plic.c | 15 +++++++++++----
> 1 file changed, 11 insertions(+), 4 deletions(-)
When you're writing cover letter and patch subject lines,
please can you make them say what part of the codebase
they're touching? This cover letter doesn't say anything in
the subject line that would tell the reader it's about riscv,
for instance, and nor do the patch line subjects.
This is helpful because people scan subject lines to see
whether the patchset is something they're interested in
or not.
thanks
-- PMM
prev parent reply other threads:[~2024-09-12 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 13:18 [PATCH 0/2] Fixes for standard conformance Sergey Makarov
2024-09-11 13:18 ` [PATCH 1/2] hw/intc: Make zeroth priority register read-only Sergey Makarov
2024-09-11 13:19 ` [PATCH 2/2] hw/intc: Don't clear pending bits on IRQ lowering Sergey Makarov
2024-09-12 8:15 ` Peter Maydell [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=CAFEAcA_RsAeh-9bAkAX0heMb1PcqqbVe4m0FPDhq8KqiKE9YDA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=Alistar.Francis@wdc.com \
--cc=bmeng@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=s.makarov@syntacore.com \
/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).