qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Markus Armbruster <armbru@redhat.com>, Alexander Graf <agraf@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] qom-test: Run for all available machines
Date: Thu, 23 Jan 2014 15:41:26 +0100	[thread overview]
Message-ID: <52E12A16.1020705@suse.de> (raw)
In-Reply-To: <52D000DF.60600@suse.de>

Am 10.01.2014 15:17, schrieb Andreas Färber:
> Am 10.01.2014 14:42, schrieb Markus Armbruster:
>> armbru@redhat.com writes:
>>
>>> From: Markus Armbruster <armbru@redhat.com>
>>>
>>> Get available machines via QMP instead of hardcoding a list that's
>>> perpetually out of date.
>>>
>>> A few machines don't work out of the box:
>>>
>>> * Several ppcemb machines can't initialize their CPU.
> 
> That's why we had the rather complicated ppc machine grouping:
> 
> http://git.qemu.org/?p=qemu.git;a=commit;h=7c41f2177e280dec1f1d4c5cd72333c5c55943af
> 
>> Alex, any chance these could be fixed?
>>
>> ppce500     Unable to initialize CPU!
>> mac99       Unable to find PowerPC CPU definition
>> g3beige     Unable to find PowerPC CPU definition
>> mpc8544ds   Unable to initialize CPU!
> 
> => shouldn't be compiled into ppcemb

Still TBD, Alex has not volunteered :(

> 
> easiest: add #ifndef TARGET_PPCEMB in machine registration functions
> better: use CONFIG_* in Makefile.objs and ppcemb-softmmu.mak
> 
>> ref405ep    Unable to find PowerPC 405ep CPU definition
>> taihu       Unable to find PowerPC 405ep CPU definition
> 
> http://lists.nongnu.org/archive/html/qemu-devel/2013-08/msg03697.html
> 
> As per Alex, these should be made to work. How???

Unanswered!

> -> target-ppc/translate_init.c
> 
>> prep        le to find PowerPC CPU definition
> 
> => shouldn't be compiled in, will look into this one as maintainer

Done: http://patchwork.ozlabs.org/patch/313620/

TBD: Macs and ppc405

As indicated on IRC, I want to get those fixed before transforming one
notation to another. Especially this patch is throwing them all in one
bucket dropping any annotation hinting at why and how it may be fixed.

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2014-01-23 14:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10 13:31 [Qemu-devel] [PATCH 0/2] qom-test: Improve coverage armbru
2014-01-10 13:31 ` [Qemu-devel] [PATCH 1/2] qom-test: Run for all available machines armbru
2014-01-10 13:42   ` Markus Armbruster
2014-01-10 13:51     ` Alexander Graf
2014-01-10 14:17     ` Andreas Färber
2014-01-23 14:41       ` Andreas Färber [this message]
2014-01-23 15:40         ` Peter Maydell
2014-01-23 15:45           ` Andreas Färber
2014-01-23 16:00             ` Peter Maydell
2014-01-23 17:14               ` Andreas Färber
2014-01-23 14:54   ` Markus Armbruster
2014-01-31 12:33   ` Andreas Färber
2014-01-31 13:42     ` Markus Armbruster
2014-02-03 12:40     ` Markus Armbruster
2014-02-05 15:47   ` Andreas Färber
2014-02-05 17:51     ` Stefano Stabellini
2014-01-10 13:31 ` [Qemu-devel] [PATCH 2/2] qom-test: Test shutdown in addition to startup armbru

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=52E12A16.1020705@suse.de \
    --to=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=armbru@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).