From: Shannon Zhao <zhaoshenglong@huawei.com>
To: qemu-arm@nongnu.org
Cc: qemu-devel@nongnu.org, peter.maydell@linaro.org,
zhaoshenglong@huawei.com, wu.wubin@huawei.com
Subject: [Qemu-devel] [PATCH v2] arm: virt: Fix the segmentation fault when specifying an unsupported CPU
Date: Tue, 17 Jan 2017 10:15:34 +0800 [thread overview]
Message-ID: <1484619334-10488-1-git-send-email-zhaoshenglong@huawei.com> (raw)
From: Shannon Zhao <shannon.zhao@linaro.org>
For example, using -cpu generic will cause qemu segmentation fault.
Signed-off-by: Shannon Zhao <shannon.zhao@linaro.org>
---
V2: Just remove the member NULL instead of checking twice
---
hw/arm/virt.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/arm/virt.c b/hw/arm/virt.c
index 7a03f84..95ac585 100644
--- a/hw/arm/virt.c
+++ b/hw/arm/virt.c
@@ -167,7 +167,6 @@ static const char *valid_cpus[] = {
"cortex-a53",
"cortex-a57",
"host",
- NULL
};
static bool cpuname_valid(const char *cpu)
--
2.0.4
next reply other threads:[~2017-01-17 2:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 2:15 Shannon Zhao [this message]
2017-01-17 11:43 ` [Qemu-devel] [PATCH v2] arm: virt: Fix the segmentation fault when specifying an unsupported CPU Peter Maydell
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=1484619334-10488-1-git-send-email-zhaoshenglong@huawei.com \
--to=zhaoshenglong@huawei.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wu.wubin@huawei.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).