Re: [Qemu-devel] -cpu behavior (was: [PATCH v3 4/4] target-openrisc: Fix cpu_model by name)

[Andreas Färber]

Am 22.07.2013 13:34, schrieb Peter Maydell:
> On 22 July 2013 12:17, Andreas Färber <address@hidden> 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,
    address@hidden "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 (address@hidden,
    address@hidden, address@hidden, access_size_min=1,
    access_size_max=4, address@hidden
    0x5555557afb80 <memory_region_read_accessor>, address@hidden
    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