From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Kevin O'Connor <kevin@koconnor.net>,
qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] isapc: Shadow ISA BIOS by default
Date: Wed, 12 Sep 2012 09:57:04 +0400 [thread overview]
Message-ID: <50502430.1070108@msgid.tls.msk.ru> (raw)
In-Reply-To: <504F5E94.9070108@siemens.com>
On 11.09.2012 19:53, Jan Kiszka wrote:
> Our one and only BIOS depends on a writable shadowed BIOS in the ISA
> range. As we have no interface to control the write property, make that
> region writable by default.
We've a long-standing bug --
http://bugs.debian.org/605525
https://bugs.launchpad.net/qemu/+bug/1024248
(qemu-system-x86_64 -M isapc shows blank guest screen)
I assume this patch fixes it for qemu/tcg case, but not for
qemu/kvm case right?
I just tested this patch on qemu 1.1 (it applies cleanly), and
it appears to work as expected, ie, the issue mentioned above
is fixed by it. But I also noticed that kvm mode is not
affected -- at least the sympthoms mentioned above does not
apply.
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
>
> This unbreaks isapc for TCG, and keep it working for KVM once it starts
> supporting read-only memslots.
Can you clarify please, -- referring to the above? :)
Thanks,
/mjt
next prev parent reply other threads:[~2012-09-12 5:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 15:53 [Qemu-devel] [PATCH] isapc: Shadow ISA BIOS by default Jan Kiszka
2012-09-12 5:57 ` Michael Tokarev [this message]
2012-09-12 7:39 ` Avi Kivity
2012-09-12 8:20 ` Jan Kiszka
2012-10-08 17:35 ` Jan Kiszka
2012-10-08 18:52 ` Anthony Liguori
2012-10-12 9:29 ` Jan Kiszka
2012-10-12 13:41 ` Anthony Liguori
2012-10-12 15:52 ` Jan Kiszka
2012-10-12 16:13 ` Anthony Liguori
2012-10-12 23:33 ` Kevin O'Connor
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=50502430.1070108@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kevin@koconnor.net \
--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).