From: "Andreas Färber" <afaerber@suse.de>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH v2 0/4] QOM'ify S/390 CPU
Date: Wed, 04 Apr 2012 17:38:27 +0200 [thread overview]
Message-ID: <4F7C6AF3.2090006@suse.de> (raw)
In-Reply-To: <4F7AEF51.1040807@de.ibm.com>
Am 03.04.2012 14:38, schrieb Christian Borntraeger:
> On 02/04/12 19:09, Andreas Färber wrote:
>> Hello,
>>
>> This series breaks down my S/390 QOM'ification patch from the qom-cpu-others.v1
>> RFC series into better digestable pieces and reorders it next.
>> s390x ignores any user-specified -cpu argument, thus needs only one CPU type.
>>
>> I've tested both TCG by running SLES installation and briefly KVM on SLES.
>>
>> Christian, could you please verify this doesn't break your test cases
>> and add your Tested-by?
>
> (kvm-only) Tested-by: Christian Borntraeger <borntraeger@de.ibm.com>
Thanks a lot, applied to s390-next:
http://repo.or.cz/w/qemu/agraf.git/shortlog/refs/heads/s390-next
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2012-04-04 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-02 17:09 [Qemu-devel] [PATCH v2 0/4] QOM'ify S/390 CPU Andreas Färber
2012-04-02 17:09 ` [Qemu-devel] [PATCH v2 1/4] target-s390x: QOM'ify CPU Andreas Färber
2012-04-02 17:09 ` [Qemu-devel] [PATCH v2 2/4] target-s390x: QOM'ify CPU reset Andreas Färber
2012-04-02 17:09 ` [Qemu-devel] [PATCH v2 3/4] target-s390x: QOM'ify CPU init Andreas Färber
2012-04-02 17:09 ` [Qemu-devel] [PATCH v2 4/4] target-s390x: Update s390x_{tod, cpu}_timer to use S390CPU Andreas Färber
2012-04-03 12:38 ` [Qemu-devel] [PATCH v2 0/4] QOM'ify S/390 CPU Christian Borntraeger
2012-04-04 15:38 ` Andreas Färber [this message]
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=4F7C6AF3.2090006@suse.de \
--to=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.