From: Francisco Iglesias <frasse.iglesias@gmail.com>
To: Tong Ho <tong.ho@xilinx.com>
Cc: edgar.iglesias@gmail.com, qemu-arm@nongnu.org,
qemu-devel@nongnu.org, alistair@alistair23.me,
peter.maydell@linaro.org
Subject: Re: [PATCH 2/3] hw/nvram: Fix Memory Leak in Xilinx Versal eFuse device
Date: Mon, 18 Oct 2021 13:21:56 +0200 [thread overview]
Message-ID: <20211018112155.GD23846@fralle-msi> (raw)
In-Reply-To: <20211015203532.2463705-3-tong.ho@xilinx.com>
On [2021 Oct 15] Fri 13:35:31, Tong Ho wrote:
> Signed-off-by: Tong Ho <tong.ho@xilinx.com>
Reviewed-by: Francisco Iglesias <frasse.iglesias@gmail.com>
> ---
> hw/nvram/xlnx-versal-efuse-ctrl.c | 20 +++++++++++++++-----
> 1 file changed, 15 insertions(+), 5 deletions(-)
>
> diff --git a/hw/nvram/xlnx-versal-efuse-ctrl.c b/hw/nvram/xlnx-versal-efuse-ctrl.c
> index d362376703..b35ba65ab5 100644
> --- a/hw/nvram/xlnx-versal-efuse-ctrl.c
> +++ b/hw/nvram/xlnx-versal-efuse-ctrl.c
> @@ -439,9 +439,11 @@ static void efuse_pgm_addr_postw(RegisterInfo *reg, uint64_t val64)
> * up to guest to do so (or by reset).
> */
> if (efuse_pgm_locked(s, bit)) {
> + g_autofree char *path = object_get_canonical_path(OBJECT(s));
> +
> qemu_log_mask(LOG_GUEST_ERROR,
> "%s: Denied setting of efuse<%u, %u, %u>\n",
> - object_get_canonical_path(OBJECT(s)),
> + path,
> FIELD_EX32(bit, EFUSE_PGM_ADDR, PAGE),
> FIELD_EX32(bit, EFUSE_PGM_ADDR, ROW),
> FIELD_EX32(bit, EFUSE_PGM_ADDR, COLUMN));
> @@ -478,9 +480,11 @@ static void efuse_rd_addr_postw(RegisterInfo *reg, uint64_t val64)
> s->regs[R_EFUSE_RD_DATA] = xlnx_versal_efuse_read_row(s->efuse,
> bit, &denied);
> if (denied) {
> + g_autofree char *path = object_get_canonical_path(OBJECT(s));
> +
> qemu_log_mask(LOG_GUEST_ERROR,
> "%s: Denied reading of efuse<%u, %u>\n",
> - object_get_canonical_path(OBJECT(s)),
> + path,
> FIELD_EX32(bit, EFUSE_RD_ADDR, PAGE),
> FIELD_EX32(bit, EFUSE_RD_ADDR, ROW));
>
> @@ -625,9 +629,11 @@ static void efuse_ctrl_reg_write(void *opaque, hwaddr addr,
> s = XLNX_VERSAL_EFUSE_CTRL(dev);
>
> if (addr != A_WR_LOCK && s->regs[R_WR_LOCK]) {
> + g_autofree char *path = object_get_canonical_path(OBJECT(s));
> +
> qemu_log_mask(LOG_GUEST_ERROR,
> "%s[reg_0x%02lx]: Attempt to write locked register.\n",
> - object_get_canonical_path(OBJECT(s)), (long)addr);
> + path, (long)addr);
> } else {
> register_write_memory(opaque, addr, data, size);
> }
> @@ -681,16 +687,20 @@ static void efuse_ctrl_realize(DeviceState *dev, Error **errp)
> const uint32_t lks_sz = sizeof(XlnxEFuseLkSpec) / 2;
>
> if (!s->efuse) {
> + g_autofree char *path = object_get_canonical_path(OBJECT(s));
> +
> error_setg(errp, "%s.efuse: link property not connected to XLNX-EFUSE",
> - object_get_canonical_path(OBJECT(dev)));
> + path);
> return;
> }
>
> /* Sort property-defined pgm-locks for bsearch lookup */
> if ((s->extra_pg0_lock_n16 % lks_sz) != 0) {
> + g_autofree char *path = object_get_canonical_path(OBJECT(s));
> +
> error_setg(errp,
> "%s.pg0-lock: array property item-count not multiple of %u",
> - object_get_canonical_path(OBJECT(dev)), lks_sz);
> + path, lks_sz);
> return;
> }
>
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2021-10-18 11:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 20:35 [PATCH 0/3] hw/nvram: Fix Memory Leaks in Xilinx eFUSE Tong Ho
2021-10-15 20:35 ` [PATCH 1/3] hw/nvram: Fix Memory Leak in Xilinx eFuse QOM Tong Ho
2021-10-18 11:21 ` Francisco Iglesias
2021-10-15 20:35 ` [PATCH 2/3] hw/nvram: Fix Memory Leak in Xilinx Versal eFuse device Tong Ho
2021-10-18 11:21 ` Francisco Iglesias [this message]
2021-10-15 20:35 ` [PATCH 3/3] hw/nvram: Fix Memory Leak in Xilinx ZynqMP " Tong Ho
2021-10-18 11:22 ` Francisco Iglesias
2021-10-18 10:31 ` [PATCH 0/3] hw/nvram: Fix Memory Leaks in Xilinx eFUSE Philippe Mathieu-Daudé
2021-10-18 16:20 ` Edgar E. Iglesias
2021-10-19 7:53 ` Laurent Vivier
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=20211018112155.GD23846@fralle-msi \
--to=frasse.iglesias@gmail.com \
--cc=alistair@alistair23.me \
--cc=edgar.iglesias@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=tong.ho@xilinx.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).