From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
qemu-arm@nongnu.org, Igor Mammedov <imammedo@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [PATCH 1/5] hw/smbios: support loading OEM strings values from a file
Date: Wed, 9 Sep 2020 08:35:37 +0100 [thread overview]
Message-ID: <20200909073537.GB1011023@redhat.com> (raw)
In-Reply-To: <cd82e5fe-28d9-39c3-871d-1a538fc1e55b@redhat.com>
On Tue, Sep 08, 2020 at 08:24:35PM +0200, Philippe Mathieu-Daudé wrote:
> Hi Daniel,
>
> On 9/8/20 6:54 PM, Daniel P. Berrangé wrote:
> > Some applications want to pass quite large values for the OEM strings
> > entries. Rather than having huge strings on the command line, it would
> > be better to load them from a file, as supported with -fw_cfg.
> >
> > This introduces the "valuefile" parameter allowing for:
> >
> > $ echo -n "thisthing" > mydata.txt
> > $ qemu-system-x86_64 \
> > -smbios type=11,value=something \
> > -smbios type=11,valuefile=mydata.txt \
> > -smbios type=11,value=somemore \
> > ...other args...
> >
> > Now in the guest
> >
> > $ dmidecide -t 11
> > Getting SMBIOS data from sysfs.
> > SMBIOS 2.8 present.
> >
> > Handle 0x0E00, DMI type 11, 5 bytes
> > OEM Strings
> > String 1: something
> > String 2: thisthing
> > String 3: somemore
> >
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > hw/smbios/smbios.c | 72 +++++++++++++++++++++++++++++++++++++---------
> > 1 file changed, 59 insertions(+), 13 deletions(-)
> >
> > diff --git a/hw/smbios/smbios.c b/hw/smbios/smbios.c
> > index 7cc950b41c..8450fad285 100644
> > --- a/hw/smbios/smbios.c
> > +++ b/hw/smbios/smbios.c
> > @@ -110,7 +110,7 @@ static struct {
> >
> > static struct {
> > size_t nvalues;
> > - const char **values;
> > + char **values;
> > } type11;
> >
> > static struct {
> > @@ -314,6 +314,11 @@ static const QemuOptDesc qemu_smbios_type11_opts[] = {
> > .type = QEMU_OPT_STRING,
> > .help = "OEM string data",
> > },
> > + {
> > + .name = "path",
> > + .type = QEMU_OPT_STRING,
> > + .help = "OEM string data from file",
> > + },
> > };
> >
> > static const QemuOptDesc qemu_smbios_type17_opts[] = {
> > @@ -641,6 +646,8 @@ static void smbios_build_type_11_table(void)
> >
> > for (i = 0; i < type11.nvalues; i++) {
> > SMBIOS_TABLE_SET_STR_LIST(11, type11.values[i]);
> > + g_free(type11.values[i]);
> > + type11.values[i] = NULL;
> > }
> >
> > SMBIOS_BUILD_TABLE_POST;
> > @@ -940,9 +947,8 @@ static void save_opt(const char **dest, QemuOpts *opts, const char *name)
> >
> >
> > struct opt_list {
> > - const char *name;
> > size_t *ndest;
> > - const char ***dest;
> > + char ***dest;
> > };
> >
> > static int save_opt_one(void *opaque,
> > @@ -951,23 +957,61 @@ static int save_opt_one(void *opaque,
> > {
> > struct opt_list *opt = opaque;
> >
> > - if (!g_str_equal(name, opt->name)) {
> > - return 0;
> > + if (g_str_equal(name, "path")) {
> > + g_autoptr(GByteArray) data = g_byte_array_new();
> > + g_autofree char *buf = g_new(char, 4096);
> > + ssize_t ret;
> > + int fd = qemu_open(value, O_RDONLY);
>
> While not use g_file_get_contents()?
qemu_open lets mgmt apps pass in pre-opened FDs using /dev/fdset/NN
syntax.
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:[~2020-09-09 7:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 16:54 [PATCH 0/5] Add support for loading SMBIOS OEM strings from a file Daniel P. Berrangé
2020-09-08 16:54 ` [PATCH 1/5] hw/smbios: support loading OEM strings values " Daniel P. Berrangé
2020-09-08 18:24 ` Philippe Mathieu-Daudé
2020-09-09 7:35 ` Daniel P. Berrangé [this message]
2020-09-09 8:33 ` Philippe Mathieu-Daudé
2020-09-09 8:18 ` Laszlo Ersek
2020-09-09 9:00 ` Daniel P. Berrangé
2020-09-09 9:10 ` Daniel P. Berrangé
2020-09-09 8:24 ` Laszlo Ersek
2020-09-08 16:54 ` [PATCH 2/5] hw/smbios: report error if table size is too large Daniel P. Berrangé
2020-09-08 18:25 ` Philippe Mathieu-Daudé
2020-09-14 8:02 ` Igor Mammedov
2020-09-08 16:54 ` [PATCH 3/5] qemu-options: document SMBIOS type 11 settings Daniel P. Berrangé
2020-09-08 18:27 ` Philippe Mathieu-Daudé
2020-09-08 16:54 ` [PATCH 4/5] hw/smbios: use qapi for SMBIOS entry point type enum Daniel P. Berrangé
2020-09-08 18:29 ` Philippe Mathieu-Daudé
2020-09-09 7:36 ` Daniel P. Berrangé
2020-09-08 18:37 ` Philippe Mathieu-Daudé
2020-12-09 17:56 ` Eduardo Habkost
2020-09-08 16:54 ` [PATCH 5/5] hw/i386: expose a "smbios_ep" PC machine property Daniel P. Berrangé
2020-09-08 18:38 ` Philippe Mathieu-Daudé
2020-09-09 8:28 ` Laszlo Ersek
2020-09-09 9:44 ` [PATCH 0/5] Add support for loading SMBIOS OEM strings from a file Laszlo Ersek
2020-09-09 9:50 ` Daniel P. Berrangé
2020-09-09 10:58 ` Laszlo Ersek
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=20200909073537.GB1011023@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).