From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Chalapathi V" <chalapathi.v@linux.ibm.com>, <qemu-devel@nongnu.org>
Cc: <qemu-ppc@nongnu.org>, <fbarrat@linux.ibm.com>, <clg@kaod.org>,
<calebs@linux.ibm.com>, <chalapathi.v@ibm.com>,
<saif.abrar@linux.ibm.com>, <dantan@linux.vnet.ibm.com>,
<milesg@linux.ibm.com>, <philmd@linaro.org>,
<alistair@alistair23.me>
Subject: Re: [PATCH-for-9.2 v3 0/3] hw/ssi/pnv_spi: Remove PnvXferBuffer and get_seq_index()
Date: Tue, 08 Oct 2024 17:43:00 +1000 [thread overview]
Message-ID: <D4Q989HQVNJA.3LVK3LEUYT1G4@gmail.com> (raw)
In-Reply-To: <20240918165045.21298-1-chalapathi.v@linux.ibm.com>
On Thu Sep 19, 2024 at 2:50 AM AEST, Chalapathi V wrote:
> Hello,
>
> v3:
> 1. Update the PowerNV maintainer section to include hw/ssi/pnv_spi*
> 2. Use of PnvXferBuffer results in a additonal process overhead due to
> frequent dynamic allocations and hence use an existing Fifo8 buffer.
> 3. Use a local variable seq_index and use it with in while loop instead
> of repeatedly calling get_seq_index() and make sure s->seq_op doesn't
> overrun when seq_index is incremented.
>
> Tested:
> passed make check and make check-avocado
>
> Supersedes: <20240807202804.56038-1-philmd@linaro.org>
Hi Chalapathi,
To be clear, this fixes Coverity CID 1558831? A Resolves:
tag for the CID should be there, I guess it's patch 2?
I like patch 2, but since it is quite a significant change,
should we take the v2 series first which is much smaller,
then add this conversion on top of it?
If it was long-standing code that would be important (because
you don't want to introduce regressions or conflicts when
backporting fixes). Since this is a new model I guess there
is leeway to just take v3 as is.
Thanks,
Nick
>
> Philippe Mathieu-Daudé (1):
> MAINTAINERS: Cover PowerPC SPI model in PowerNV section
>
> Chalapathi V (2):
> hw/ssi/pnv_spi: Replace PnvXferBuffer with Fifo8 structure
> hw/ssi/pnv_spi: Use local var seq_index instead of get_seq_index().
>
> MAINTAINERS | 2 +
> include/hw/ssi/pnv_spi.h | 3 +
> hw/ssi/pnv_spi.c | 228 +++++++++++++++------------------------
> 3 files changed, 89 insertions(+), 144 deletions(-)
next prev parent reply other threads:[~2024-10-08 7:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 16:50 [PATCH-for-9.2 v3 0/3] hw/ssi/pnv_spi: Remove PnvXferBuffer and get_seq_index() Chalapathi V
2024-09-18 16:50 ` [PATCH v3 1/3] MAINTAINERS: Cover PowerPC SPI model in PowerNV section Chalapathi V
2024-10-08 7:44 ` Nicholas Piggin
2024-10-08 17:32 ` Chalapathi V
2024-09-18 16:50 ` [PATCH v3 2/3] hw/ssi/pnv_spi: Replace PnvXferBuffer with Fifo8 structure Chalapathi V
2024-10-08 7:59 ` Nicholas Piggin
2024-10-08 17:18 ` Chalapathi V
2024-09-18 16:50 ` [PATCH v3 3/3] hw/ssi/pnv_spi: Use local var seq_index instead of get_seq_index() Chalapathi V
2024-10-08 8:13 ` Nicholas Piggin
2024-10-08 17:34 ` Chalapathi V
2024-10-08 7:43 ` Nicholas Piggin [this message]
2024-10-08 12:44 ` [PATCH-for-9.2 v3 0/3] hw/ssi/pnv_spi: Remove PnvXferBuffer and get_seq_index() Cédric Le Goater
2024-10-08 17:40 ` Chalapathi V
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=D4Q989HQVNJA.3LVK3LEUYT1G4@gmail.com \
--to=npiggin@gmail.com \
--cc=alistair@alistair23.me \
--cc=calebs@linux.ibm.com \
--cc=chalapathi.v@ibm.com \
--cc=chalapathi.v@linux.ibm.com \
--cc=clg@kaod.org \
--cc=dantan@linux.vnet.ibm.com \
--cc=fbarrat@linux.ibm.com \
--cc=milesg@linux.ibm.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=saif.abrar@linux.ibm.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).