From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Richard Henderson <rth@twiddle.net>, Jia Liu <proljc@gmail.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] -cpu behavior (was: [PATCH v3 4/4] target-openrisc: Fix cpu_model by name)
Date: Mon, 22 Jul 2013 14:26:18 +0200 [thread overview]
Message-ID: <51ED24EA.6090007@suse.de> (raw)
In-Reply-To: <CAFEAcA9U0jEumpyEzuUXc9Ce4+NAhGD7zmi-713wx0RMCOcL2Q@mail.gmail.com>
Am 22.07.2013 13:34, schrieb Peter Maydell:
> On 22 July 2013 12:17, Andreas Färber <afaerber@suse.de> wrote:
>> Am 22.07.2013 12:40, schrieb Peter Maydell:
>>> In any case we should be
>>> consistent across target architectures about what we allow.
>>
>> alpha allows both, but -cpu ? just gave me a segfault. :/
>
> Odd; that works for me:
> cam-vm-266:precise:qemu$ ./build/x86-all/alpha-softmmu/qemu-system-alpha -cpu ?
> Available CPUs:
> ev4-alpha-cpu
> ev5-alpha-cpu
> ev56-alpha-cpu
> ev6-alpha-cpu
> ev67-alpha-cpu
> ev68-alpha-cpu
> pca56-alpha-cpu
For -cpu ? I got
Program received signal SIGSEGV, Segmentation fault.
0x00005555557323fa in object_class_dynamic_cast (class=0x55555606df20,
typename=typename@entry=0x55555582b82e "virtio-scsi-common")
at /home/andreas/QEMU/qemu/qom/object.c:496
496 if (type->class->interfaces &&
but that might be related to local QOM patches... :/ confirmed, qom-next
is working fine.
For -cpu ev67-alpha-cpu I got:
0x00005555557af890 in access_with_adjusted_size (addr=addr@entry=1021,
value=value@entry=0x7fffe73bb5e0, size=size@entry=1, access_size_min=1,
access_size_max=4, access=access@entry=
0x5555557afb80 <memory_region_read_accessor>, opaque=opaque@entry=
0x5555560bd3b0) at /home/andreas/QEMU/qemu/memory.c:429
429 access_size = MAX(MIN(size, access_size_max), access_size_min);
Seems unrelated and is no longer reproducible either. Hmm.
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:[~2013-07-22 12:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 8:56 [Qemu-devel] [PATCH v3 0/4] target-openrisc hw/openrisc: Some OpenRISC fix Jia Liu
2013-07-22 8:56 ` [Qemu-devel] [PATCH v3 1/4] hw/openrisc: Indent typo Jia Liu
2013-07-22 9:21 ` Peter Maydell
2013-07-22 8:56 ` [Qemu-devel] [PATCH v3 2/4] hw/openrisc: Use stderr output instead of qemu_log Jia Liu
2013-07-22 9:21 ` Peter Maydell
2013-07-22 8:56 ` [Qemu-devel] [PATCH v3 3/4] target-openrisc: Free typename Jia Liu
2013-07-22 9:37 ` Jia Liu
2013-07-22 9:41 ` Peter Maydell
2013-07-22 9:43 ` Jia Liu
2013-07-22 8:56 ` [Qemu-devel] [PATCH v3 4/4] target-openrisc: Fix cpu_model by name Jia Liu
2013-07-22 9:29 ` Peter Maydell
2013-07-22 9:42 ` Jia Liu
2013-07-22 9:43 ` Peter Maydell
2013-07-22 9:54 ` Jia Liu
2013-07-22 10:12 ` Jia Liu
2013-07-22 10:37 ` Andreas Färber
2013-07-22 10:40 ` Peter Maydell
2013-07-22 11:17 ` Andreas Färber
2013-07-22 11:34 ` Peter Maydell
2013-07-22 12:26 ` Andreas Färber [this message]
2013-07-22 12:33 ` Andreas Färber
2013-07-22 15:25 ` Anthony Liguori
2013-07-22 15:38 ` Peter Maydell
2013-07-22 16:29 ` [Qemu-devel] -cpu behavior (was: [PATCH v3 4/4] target-openrisc: Fix cpu_model by name) Andreas Färber
2013-07-22 17:39 ` [Qemu-devel] [PATCH v3 4/4] target-openrisc: Fix cpu_model by name Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2013-07-22 17:34 [Qemu-devel] -cpu behavior (was: [PATCH v3 4/4] target-openrisc: Fix cpu_model by name) Michael Mueller
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=51ED24EA.6090007@suse.de \
--to=afaerber@suse.de \
--cc=peter.maydell@linaro.org \
--cc=proljc@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).