From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Ani Sinha <anisinha@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Fabiano Rosas" <farosas@suse.de>,
"Laurent Vivier" <lvivier@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
armbru@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v3] tests/qtest/libqos: add DMA support for writing and reading fw_cfg files
Date: Wed, 8 Jan 2025 13:08:26 +0000 [thread overview]
Message-ID: <Z354ytFhuJnohBXx@redhat.com> (raw)
In-Reply-To: <20250108125751.199929-1-anisinha@redhat.com>
On Wed, Jan 08, 2025 at 06:27:50PM +0530, Ani Sinha wrote:
> At present, the libqos/fw_cfg.c library does not support the modern DMA
> interface which is required to write to the fw_cfg files. It only uses the IO
> interface. Implement read and write methods based on DMA. This will enable
> developers to write tests that writes to the fw_cfg file(s). The structure of
> the code is taken from edk2 fw_cfg implementation. It has been tested by
> writing a qtest that writes to a fw_cfg file. This test will be part of a
> future patch series.
>
> Signed-off-by: Ani Sinha <anisinha@redhat.com>
> ---
> tests/qtest/libqos/fw_cfg.c | 204 ++++++++++++++++++++++++++++++++----
> tests/qtest/libqos/fw_cfg.h | 5 +
> 2 files changed, 186 insertions(+), 23 deletions(-)
> +static bool
> +find_pdir_entry(QFWCFG *fw_cfg, const char *filename,
> + uint16_t *sel, uint32_t *size)
> +{
> + unsigned char *filesbuf = NULL;
Use g_autofree here instead of later g_free.
> + uint32_t count;
> + size_t dsize;
> + FWCfgFile *pdir_entry;
> + uint32_t i;
> + bool found = false;
> +
> + *size = 0;
> + *sel = 0;
> +
> + qfw_cfg_get(fw_cfg, FW_CFG_FILE_DIR, &count, sizeof(count));
> + count = be32_to_cpu(count);
> + dsize = sizeof(uint32_t) + count * sizeof(struct fw_cfg_file);
> + filesbuf = g_malloc(dsize);
> + g_assert(filesbuf);
> + qfw_cfg_get(fw_cfg, FW_CFG_FILE_DIR, filesbuf, dsize);
> + pdir_entry = (FWCfgFile *)(filesbuf + sizeof(uint32_t));
I'm not familiar with fwcfg data format, but I'm wondering
what the initial 'uint32_t' data field is that you're skipping
over, and whether its value should be validated before this
loop ?
> + for (i = 0; i < count; ++i, ++pdir_entry) {
> + if (!strcmp(pdir_entry->name, filename)) {
> + *size = be32_to_cpu(pdir_entry->size);
> + *sel = be16_to_cpu(pdir_entry->select);
> + found = true;
> + break;
> + }
> + }
> +
> + g_free(filesbuf);
> + return found;
> +}
> +
> /*
> * The caller need check the return value. When the return value is
> * nonzero, it means that some bytes have been transferred.
> @@ -73,37 +168,100 @@ static void mm_fw_cfg_select(QFWCFG *fw_cfg, uint16_t key)
> * populated, it has received only a starting slice of the fw_cfg file.
> */
> size_t qfw_cfg_get_file(QFWCFG *fw_cfg, const char *filename,
> - void *data, size_t buflen)
> + void *data, size_t buflen)
> {
> - uint32_t count;
> - uint32_t i;
> - unsigned char *filesbuf = NULL;
> - size_t dsize;
> - FWCfgFile *pdir_entry;
> size_t filesize = 0;
> + uint32_t len;
> + uint16_t sel;
>
> - qfw_cfg_get(fw_cfg, FW_CFG_FILE_DIR, &count, sizeof(count));
> - count = be32_to_cpu(count);
> - dsize = sizeof(uint32_t) + count * sizeof(struct fw_cfg_file);
> - filesbuf = g_malloc(dsize);
> - qfw_cfg_get(fw_cfg, FW_CFG_FILE_DIR, filesbuf, dsize);
> - pdir_entry = (FWCfgFile *)(filesbuf + sizeof(uint32_t));
> - for (i = 0; i < count; ++i, ++pdir_entry) {
> - if (!strcmp(pdir_entry->name, filename)) {
> - uint32_t len = be32_to_cpu(pdir_entry->size);
> - uint16_t sel = be16_to_cpu(pdir_entry->select);
> - filesize = len;
> - if (len > buflen) {
> - len = buflen;
> - }
> - qfw_cfg_get(fw_cfg, sel, data, len);
> - break;
> + if (find_pdir_entry(fw_cfg, filename, &sel, &len)) {
> + filesize = len;
> + if (len > buflen) {
> + len = buflen;
> }
> + qfw_cfg_get(fw_cfg, sel, data, len);
> }
> - g_free(filesbuf);
> +
> return filesize;
> }
I'd recommend refactoring of existnig code, be a separate commit
from the newly added functionality.
>
> +/*
> + * The caller need check the return value. When the return value is
> + * nonzero, it means that some bytes have been transferred.
> + *
> + * If the fw_cfg file in question is smaller than the allocated & passed-in
> + * buffer, then the first len bytes were read.
> + *
> + * If the fw_cfg file in question is larger than the passed-in
> + * buffer, then the return value explains how much was actually read.
> + *
> + * It is illegal to call this function if fw_cfg does not support DMA
> + * interface. The caller should ensure that DMA is supported before
> + * calling this function.
> + *
> + * Passed QOSState pointer qs must be initialized. qs->alloc must also be
> + * properly initialized.
> + */
> +size_t qfw_cfg_read_file(QFWCFG *fw_cfg, QOSState *qs, const char *filename,
> + void *data, size_t buflen)
> +{
> + uint32_t len = 0;
> + uint16_t sel;
> + uint32_t id;
> +
> + g_assert(qs);
> + /* check if DMA is supported since we use DMA for read */
> + id = qfw_cfg_get_u32(fw_cfg, FW_CFG_ID);
> + g_assert(id & FW_CFG_VERSION_DMA);
> +
> + if (find_pdir_entry(fw_cfg, filename, &sel, &len)) {
> + if (len > buflen) {
> + len = buflen;
> + }
> + qfw_cfg_read_entry(fw_cfg, qs, sel, data, len);
> + }
> +
> + return (size_t) len;
The size_t cast is redundant, since we know sizeof(size_t)
will be >= sizeof(uint32_t) on all platforms
> +}
> +
> +/*
> + * The caller need check the return value. When the return value is
> + * nonzero, it means that some bytes have been transferred.
> + *
> + * If the fw_cfg file in question is smaller than the allocated & passed-in
> + * buffer, then the buffer has been partially written.
> + *
> + * If the fw_cfg file in question is larger than the passed-in
> + * buffer, then the return value explains how much was actually written.
> + *
> + * It is illegal to call this function if fw_cfg does not support DMA
> + * interface. The caller should ensure that DMA is supported before
> + * calling this function.
> + *
> + * Passed QOSState pointer qs must be initialized. qs->alloc must also be
> + * properly initialized.
> + */
> +size_t qfw_cfg_write_file(QFWCFG *fw_cfg, QOSState *qs, const char *filename,
> + void *data, size_t buflen)
> +{
> + uint32_t len = 0;
> + uint16_t sel;
> + uint32_t id;
> +
> + g_assert(qs);
> + /* write operation is only valid if DMA is supported */
> + id = qfw_cfg_get_u32(fw_cfg, FW_CFG_ID);
> + g_assert(id & FW_CFG_VERSION_DMA);
> +
> + if (find_pdir_entry(fw_cfg, filename, &sel, &len)) {
> + if (len > buflen) {
> + len = buflen;
> + }
> + qfw_cfg_write_entry(fw_cfg, qs, sel, data, len);
> + }
> + return (size_t) len;
Another redundant cast
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-01-08 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 12:57 [PATCH v3] tests/qtest/libqos: add DMA support for writing and reading fw_cfg files Ani Sinha
2025-01-08 13:08 ` Daniel P. Berrangé [this message]
2025-01-08 13:17 ` Ani Sinha
2025-01-08 13:20 ` Daniel P. Berrangé
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=Z354ytFhuJnohBXx@redhat.com \
--to=berrange@redhat.com \
--cc=anisinha@redhat.com \
--cc=armbru@redhat.com \
--cc=farosas@suse.de \
--cc=kraxel@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.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).