From: Marcelo Tosatti <mtosatti@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Avi Kivity <avi@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH v2 uq/master] kvmvapic: Disable if there is insufficient memory
Date: Tue, 14 Aug 2012 16:01:23 -0300 [thread overview]
Message-ID: <20120814190123.GB5281@amt.cnet> (raw)
In-Reply-To: <502A39D0.7080702@siemens.com>
On Tue, Aug 14, 2012 at 01:43:12PM +0200, Jan Kiszka wrote:
> We need at least 1M of RAM to map the option ROM. Otherwise, we will
> corrupt host memory or even crash:
>
> $ qemu-system-x86_64 -nodefaults --enable-kvm -vnc :0 -m 640k
> Segmentation fault (core dumped)
>
> Reported-and-tested-by: Markus Armbruster <armbru@redhat.com>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> hw/apic_common.c | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/hw/apic_common.c b/hw/apic_common.c
> index 58e63b0..371f95d 100644
> --- a/hw/apic_common.c
> +++ b/hw/apic_common.c
> @@ -299,7 +299,9 @@ static int apic_init_common(SysBusDevice *dev)
>
> sysbus_init_mmio(dev, &s->io_memory);
>
> - if (!vapic && s->vapic_control & VAPIC_ENABLE_MASK) {
> + /* Note: We need at least 1M to map the VAPIC option ROM */
> + if (!vapic && s->vapic_control & VAPIC_ENABLE_MASK &&
> + ram_size >= 1024 * 1024) {
> vapic = sysbus_create_simple("kvmvapic", -1, NULL);
> }
> s->vapic = vapic;
> --
> 1.7.3.4
Applied, thanks.
prev parent reply other threads:[~2012-08-14 19:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-14 11:12 [PATCH uq/master] kvmvapic: Disable if there is insufficient memory Jan Kiszka
2012-08-14 11:40 ` [Qemu-devel] " Markus Armbruster
2012-08-14 11:43 ` [PATCH v2 " Jan Kiszka
2012-08-14 19:01 ` Marcelo Tosatti [this message]
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=20120814190123.GB5281@amt.cnet \
--to=mtosatti@redhat.com \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.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).