From: "Cédric Le Goater" <clg@kaod.org>
To: Chalapathi V <chalapathi.v@linux.ibm.com>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, fbarrat@linux.ibm.com, npiggin@gmail.com,
calebs@linux.ibm.com, chalapathi.v@ibm.com,
saif.abrar@linux.ibm.com, dantan@us.ibm.com,
milesg@linux.ibm.com
Subject: Re: [PATCH v6 0/6] hw/ppc: SPI model
Date: Tue, 30 Jul 2024 19:31:55 +0200 [thread overview]
Message-ID: <a5d408eb-0a79-49da-902f-a5f79a74d733@kaod.org> (raw)
In-Reply-To: <20240730172343.5818-1-chalapathi.v@linux.ibm.com>
Hello Chalapathi
On 7/30/24 19:23, Chalapathi V wrote:
> Hello,
>
> In patch v6 below issues detected during Coverity Scan were fixed.
> - CID 1558831: Resource leaks (RESOURCE_LEAK)
> Variable "rsp_payload" going out of scope leaks the storage it points to.
> - CID 1558827: (OVERRUN)
> Overrunning array "s->seq_op" of 8 bytes at byte offset 16 using index
> "get_seq_index(s) + 1" (which evaluates to 16).
You don't need to resend a v6 because the PowerNV SPI model is already
merged upstream :
https://gitlab.com/qemu-project/qemu/-/commit/29318db133d0b2523bda771f76aa50c08842527f
What we would need now is a series of two patches on top of upstream
fixing the issues reported by coverity. Each patch should contain
a "Fixes: Coverity CID XYZxyz" tag.
Thanks,
C.
> The qom-tree looks like below.
> (qemu) info qom-tree
> /machine (powernv10-machine)
> /chip[0] (power10_v2.0-pnv-chip)
> /pib_spic[0] (pnv-spi)
> /pnv-spi-bus.0 (SSI)
> /xscom-spi[0] (memory-region)
> /pib_spic[1] (pnv-spi)
> /pnv-spi-bus.1 (SSI)
> /xscom-spi[0] (memory-region)
> /pib_spic[2] (pnv-spi)
> /pnv-spi-bus.2 (SSI)
> /xscom-spi[0] (memory-region)
> /pib_spic[3] (pnv-spi)
> /pnv-spi-bus.3 (SSI)
> /xscom-spi[0] (memory-region)
> /pib_spic[4] (pnv-spi)
> /pnv-spi-bus.4 (SSI)
> /xscom-spi[0] (memory-region)
> /pib_spic[5] (pnv-spi)
> /pnv-spi-bus.5 (SSI)
> /xscom-spi[0] (memory-region)
>
> (qemu) info qom-tree
> /machine (powernv10-machine)
> /peripheral-anon (container)
> /device[0] (25csm04)
> /WP#[0] (irq)
> /ssi-gpio-cs[0] (irq)
>
> Patches overview in v6.
> PATCH1: Remove ppc target dependency from include/hw/ppc/pnv_xscom.h so
> that pnv_xscom.h can be included in hw/ssi/pnv_spi.c in PATCH2.
> PATCH2: Create a PNV SPI model and implement configuration unit
> to model SCOM registers.
> PATCH3: Extend PNV SPI model: implement sequencer FSM and shift engine.
> PATCH4: Add Microchip's SEEPROM 25csm04 model on top of m25p80.
> PATCH5: Connect SPI controllers to p10 chip and connect cs lines.
> PATCH6: Write a qtest pnv-spi-seeprom-test to check the SPI transactions
> between spi controller and seeprom device.
>
> Test covered:
> make check
> make check-avocado
>
> Thank You,
> Chalapathi
>
> Chalapathi V (6):
> ppc/pnv: Remove ppc target dependency from pnv_xscom.h
> hw/ssi: Add SPI model
> hw/ssi: Extend SPI model
> hw/block: Add Microchip's 25CSM04 to m25p80
> hw/ppc: SPI controller wiring to P10 chip
> tests/qtest: Add pnv-spi-seeprom qtest
>
> include/hw/ppc/pnv_chip.h | 3 +
> include/hw/ppc/pnv_xscom.h | 5 +-
> include/hw/ssi/pnv_spi.h | 67 ++
> include/hw/ssi/pnv_spi_regs.h | 133 +++
> hw/block/m25p80.c | 3 +
> hw/ppc/pnv.c | 21 +-
> hw/ssi/pnv_spi.c | 1269 ++++++++++++++++++++++++++++
> tests/qtest/pnv-spi-seeprom-test.c | 110 +++
> hw/ppc/Kconfig | 3 +
> hw/ssi/Kconfig | 4 +
> hw/ssi/meson.build | 1 +
> hw/ssi/trace-events | 21 +
> tests/qtest/meson.build | 1 +
> 13 files changed, 1639 insertions(+), 2 deletions(-)
> create mode 100644 include/hw/ssi/pnv_spi.h
> create mode 100644 include/hw/ssi/pnv_spi_regs.h
> create mode 100644 hw/ssi/pnv_spi.c
> create mode 100644 tests/qtest/pnv-spi-seeprom-test.c
>
prev parent reply other threads:[~2024-07-30 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 17:23 [PATCH v6 0/6] hw/ppc: SPI model Chalapathi V
2024-07-30 17:23 ` [PATCH v6 1/6] ppc/pnv: Remove ppc target dependency from pnv_xscom.h Chalapathi V
2024-07-30 17:23 ` [PATCH v6 2/6] hw/ssi: Add SPI model Chalapathi V
2024-07-30 17:23 ` [PATCH v6 3/6] hw/ssi: Extend " Chalapathi V
2024-07-30 17:23 ` [PATCH v6 4/6] hw/block: Add Microchip's 25CSM04 to m25p80 Chalapathi V
2024-07-30 17:23 ` [PATCH v6 5/6] hw/ppc: SPI controller wiring to P10 chip Chalapathi V
2024-07-30 17:23 ` [PATCH v6 6/6] tests/qtest: Add pnv-spi-seeprom qtest Chalapathi V
2024-07-30 17:31 ` Cédric Le Goater [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=a5d408eb-0a79-49da-902f-a5f79a74d733@kaod.org \
--to=clg@kaod.org \
--cc=calebs@linux.ibm.com \
--cc=chalapathi.v@ibm.com \
--cc=chalapathi.v@linux.ibm.com \
--cc=dantan@us.ibm.com \
--cc=fbarrat@linux.ibm.com \
--cc=milesg@linux.ibm.com \
--cc=npiggin@gmail.com \
--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).