From: Paolo Bonzini <pbonzini@redhat.com>
To: "Ning, Yu" <yu.ning@intel.com>,
Alexandro Sanchez Bach <alexandro@phi.nz>
Cc: "'Peter Maydell'" <peter.maydell@linaro.org>,
"'Peter Krempa'" <pkrempa@redhat.com>,
'Qemu-block' <qemu-block@nongnu.org>,
'Libvirt' <libvir-list@redhat.com>,
"'QEMU Developers'" <qemu-devel@nongnu.org>,
"'László Érsek'" <lersek@redhat.com>,
"'Justin Terry (VM)'" <juterry@microsoft.com>,
"'Markus Armbruster'" <armbru@redhat.com>
Subject: Re: [Qemu-devel] Configuring pflash devices for OVMF firmware
Date: Mon, 4 Feb 2019 11:00:12 +0100 [thread overview]
Message-ID: <2294a001-ccfc-ab32-8b07-9f2f2c7f5cbd@redhat.com> (raw)
In-Reply-To: <C29659EAAA3E0143B583467412621C605E408079@SHSMSX101.ccr.corp.intel.com>
On 01/02/19 03:49, Ning, Yu wrote:
> Thank you both for outlining the changes we have to make in order to
> support ROMD memory regions! The only question is whether we should
> pass a new flag to HAX_VM_IOCTL_SET_RAM2 for ROMD, so the hypervisor
> could respond differently to writes to ROM and ROMD regions. Would
> that be useful at all? What would happen if HAXM asked QEMU to
> emulate a write to ROM?
It's more about backwards compatibility. As far as QEMU is concerned
it's okay if all ROM reads are handled as MMIO. However, other
emulators may not expect that, so maybe you want to add another flag.
Paolo
> HAXM didn't implement ROMD support at first, because the guests we
> tested could boot without it (including Chrome OS). Now that this
> feature has become more popular (and we want to be able to boot
> OVMF), I think it's time to get it done. I'd like to get to it after
> the Lunar New Year holidays, but if anyone can finish it sooner, I'll
> be happy to merge their patch into HAXM.
next prev parent reply other threads:[~2019-02-04 10:05 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 15:03 [Qemu-devel] Configuring pflash devices for OVMF firmware Markus Armbruster
2019-01-28 7:58 ` Laszlo Ersek
2019-01-28 10:39 ` Peter Maydell
2019-01-28 12:40 ` [Qemu-devel] [libvirt] " Gerd Hoffmann
2019-01-28 13:06 ` Peter Maydell
2019-01-28 14:55 ` Laszlo Ersek
2019-01-28 14:58 ` Peter Maydell
2019-01-28 15:03 ` Laszlo Ersek
2019-01-30 7:36 ` Markus Armbruster
2019-01-30 8:00 ` Gerd Hoffmann
2019-01-30 7:24 ` [Qemu-devel] " Markus Armbruster
2019-01-30 15:24 ` Peter Maydell
2019-01-30 16:44 ` Laszlo Ersek
2019-01-30 17:24 ` Peter Maydell
2019-01-31 8:52 ` Markus Armbruster
2019-01-31 10:01 ` Peter Maydell
2019-01-31 10:24 ` Markus Armbruster
2019-01-31 10:34 ` Peter Maydell
2019-01-31 12:05 ` Markus Armbruster
2019-01-30 14:13 ` Markus Armbruster
2019-01-30 14:33 ` Paolo Bonzini
2019-01-30 16:38 ` Laszlo Ersek
2019-01-31 8:33 ` Markus Armbruster
2019-01-31 9:19 ` Paolo Bonzini
2019-01-31 9:37 ` Markus Armbruster
2019-01-31 12:02 ` Laszlo Ersek
2019-01-31 12:10 ` Paolo Bonzini
2019-01-31 12:51 ` Markus Armbruster
2019-01-31 8:40 ` Markus Armbruster
2019-01-31 9:19 ` Paolo Bonzini
2019-01-31 9:41 ` Markus Armbruster
2019-01-31 10:12 ` Paolo Bonzini
2019-01-31 12:12 ` Markus Armbruster
2019-01-31 22:57 ` Paolo Bonzini
2019-01-31 23:28 ` Alexandro Sanchez Bach
2019-01-31 23:54 ` Paolo Bonzini
2019-02-01 2:49 ` Ning, Yu
2019-02-04 10:00 ` Paolo Bonzini [this message]
2019-02-01 8:58 ` Markus Armbruster
2019-01-31 11:57 ` Laszlo Ersek
2019-02-19 7:19 ` Markus Armbruster
2019-02-22 13:28 ` Markus Armbruster
2019-02-07 9:30 ` Markus Armbruster
2019-02-07 12:31 ` Laszlo Ersek
2019-02-07 13:49 ` Markus Armbruster
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=2294a001-ccfc-ab32-8b07-9f2f2c7f5cbd@redhat.com \
--to=pbonzini@redhat.com \
--cc=alexandro@phi.nz \
--cc=armbru@redhat.com \
--cc=juterry@microsoft.com \
--cc=lersek@redhat.com \
--cc=libvir-list@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pkrempa@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=yu.ning@intel.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).