From: lijun <junmuzi@gmail.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, kraxel@redhat.com, mst@redhat.com
Subject: [Qemu-devel] [PATCH] qemu will core dump with "-smp 254, sockets=2, cores=3, threads=2"
Date: Fri, 13 Dec 2013 02:10:20 +0800 [thread overview]
Message-ID: <52A9FC0C.3040509@gmail.com> (raw)
Hi all,
when set "-smp" more than 160, qemu will give the following warning:
Warning: Number of SMP cpus requested (161) exceeds the recommended cpus
supported by KVM (160)
As the above warning, when set "-smp 160,sockets=2,cores=3,threads=2",
but find that apic_id(hw/i386/acpi-build.c) is 259 not 159 and
id(hw/acpi/piix4.c) is 259 not 159.
As the above warning, when set "-smp 254,sockets=2,cores=3,threads=2",
but find that apic_id(hw/i386/acpi-build.c) is 513 not 253 and
id(hw/acpi/piix4.c) is 513 not 253.
Based on above reasons, we have two methods to fix this issue.
1, Delete "assert(apic_id <= MAX_CPUMASK_BITS)" in file
"hw/i386/acpi-build.c" and delete "g_assert((id / 8) < PIIX4_PROC_LEN)"
in file "hw/acpi/piix4.c".
2, Detect the values of "sockets,cores,threads" when get them from
command line. And modify smp_parse function in file vl.c to do some
restrictions on these parameters when boot qemu.
I will submit the code patch later.
Best Regards,
Jun Li
next reply other threads:[~2013-12-12 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 18:10 lijun [this message]
2013-12-14 17:21 ` [Qemu-devel] [PATCH] qemu will core dump with "-smp 254, sockets=2, cores=3, threads=2" lijun
2013-12-14 19:10 ` Peter Maydell
2013-12-16 14:43 ` Eric Blake
2013-12-16 16:55 ` Eduardo Habkost
-- strict thread matches above, loose matches on Subject: below --
2013-12-16 6:18 jun muzi
2013-12-16 7:54 jun muzi
2013-12-16 16:53 ` Eduardo Habkost
2013-12-17 15:16 [Qemu-devel] [PATCH] qemu will core dump with "-smp 254, , " lijun
2013-12-17 15:51 ` Eduardo Habkost
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=52A9FC0C.3040509@gmail.com \
--to=junmuzi@gmail.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@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).