From: "Andreas Färber" <afaerber@suse.de>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] fix '-cpu ?' Segfault
Date: Thu, 22 Mar 2012 14:46:48 +0100 [thread overview]
Message-ID: <4F6B2D48.6090400@suse.de> (raw)
In-Reply-To: <4F6B28F0.9060301@linux.vnet.ibm.com>
Am 22.03.2012 14:28, schrieb Stefan Berger:
> On 03/21/2012 08:33 AM, Eduardo Habkost wrote:
>> Fix stupid copy&paste mistake at commit
>> ecf40beae7dcbb057d4f115207f9d8276832a774: I moved code around but kept
>> "optarg" on the cpu_list() call.
>>
>> Reported-by: Jiri Denemark<jdenemar@redhat.com>
>> Signed-off-by: Eduardo Habkost<ehabkost@redhat.com>
>> ---
>> vl.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/vl.c b/vl.c
>> index 112b0e0..0fccf50 100644
>> --- a/vl.c
>> +++ b/vl.c
>> @@ -3196,7 +3196,7 @@ int main(int argc, char **argv, char **envp)
>> cpudef_init();
>>
>> if (cpu_model&& *cpu_model == '?') {
>> - list_cpus(stdout,&fprintf, optarg);
>> + list_cpus(stdout,&fprintf, cpu_model);
>> exit(0);
>> }
>>
> Does -cpu ? actually work then? I only see the list of cpus when using
> -cpu ?_ for example.
You're right, it should be cpu_model + 1 from what I recall, i.e. just
the optional argument, not the whole model string.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-03-22 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 12:33 [Qemu-devel] [PATCH] fix '-cpu ?' Segfault Eduardo Habkost
2012-03-21 13:24 ` Stefan Hajnoczi
2012-03-22 13:28 ` Stefan Berger
2012-03-22 13:46 ` Andreas Färber [this message]
2012-03-22 14:05 ` Eduardo Habkost
2012-03-23 20:31 ` Michael Roth
2012-03-23 20:37 ` Alon Levy
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=4F6B2D48.6090400@suse.de \
--to=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=stefanha@gmail.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).