From: Paolo Bonzini <pbonzini@redhat.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: mst@redhat.com, lersek@redhat.com, qemu-devel@nongnu.org,
peterx@redhat.com, dgilbert@redhat.com
Subject: Re: [PATCH v2 2/2] pci: add romsize property
Date: Fri, 29 Jan 2021 20:57:12 +0100 [thread overview]
Message-ID: <9aae8014-8f86-ad1c-1a67-f08312aeb8d9@redhat.com> (raw)
In-Reply-To: <ee924cca-8b90-df77-b544-c6405f6b761@eik.bme.hu>
On 29/01/21 20:51, BALATON Zoltan wrote:
> otherwise the BIOS emulator in the guest firmware crashes and this works
> so I think romfile can be empty and it's a useful feature to have in
> this case for example. I don't know if this patch changes anything about
> that but the commit message saying that romfile cannot be empty may be
> wrong.
The empty property value configures the device not to have a ROM file at
all. The commit message says that ROM files (if they exist) cannot be
empty, corresponding to this code in pci_add_option_rom:
} else if (size == 0) {
error_setg(errp, "romfile \"%s\" is empty", pdev->romfile);
g_free(path);
return;
}
Paolo
next prev parent reply other threads:[~2021-01-29 19:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-29 19:28 [PATCH v2 0/2] pci: add romsize property Paolo Bonzini
2021-01-29 19:28 ` [PATCH v2 1/2] pci: reject too large ROMs Paolo Bonzini
2021-01-29 22:18 ` Peter Xu
2021-02-01 8:34 ` Philippe Mathieu-Daudé
2021-02-02 10:59 ` Laszlo Ersek
2021-01-29 19:28 ` [PATCH v2 2/2] pci: add romsize property Paolo Bonzini
2021-01-29 19:51 ` BALATON Zoltan
2021-01-29 19:57 ` Paolo Bonzini [this message]
2021-01-29 20:06 ` BALATON Zoltan
2021-01-29 20:16 ` Paolo Bonzini
2021-02-01 7:56 ` Gerd Hoffmann
2021-02-01 15:52 ` Peter Xu
2021-02-01 15:54 ` Dr. David Alan Gilbert
2021-02-02 10:05 ` David Edmondson
2021-02-02 11:03 ` 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=9aae8014-8f86-ad1c-1a67-f08312aeb8d9@redhat.com \
--to=pbonzini@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=dgilbert@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--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).