xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH qom-next 00/59] QOM CPUState, part 4: CPU_COMMON
Date: Wed, 23 May 2012 17:36:32 +0200	[thread overview]
Message-ID: <4FBD0400.90101@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.00.1205231225510.26786@kaball-desktop>

Am 23.05.2012 13:27, schrieb Stefano Stabellini:
> On Wed, 23 May 2012, Andreas Färber wrote:
>> This series, based on qom-next and the two pending ARM cleanup patches, starts
>> moving fields from CPUArchState (CPU_COMMON) to QOM CPUState. It stops short
>> of moving all easily possible fields (i.e., those not depending on target_ulong
>> or target_phys_addr_t) since the series got too long already and is expected to
>> spark some controversies due to collisions with several other series.
>>
>> The series is structured as preparatory refactorings interwoven with the actual
>> touch-all movement of one field ("cpu: Move ... to CPUState"), optionally
>> followed by type signature cleanups, culminating in the movement of two fields
>> that are tied together by VMState.
>> Thus, unlike part 3, this series cannot randomly be cherry-picked to
>> <arch>-next trees, only select parts thereof (e.g., use of cpu_s390x_init()).
>>
>> Please review and test.
[...]
>> I have checked this to compile on ...
>> * openSUSE 12.1 x86_64 w/KVM,
>> * openSUSE Factory ppc w/KVM,
>> * SLES 11 SP2 s390x w/KVM,
>> * mingw32/64 cross-builds,
>> * OpenBSD 5.1 amd64 (not for final version though, master doesn't build).
>> Untested: Xen.
> 
> I tested it on Xen: it works correctly.
> 
> Tested-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>

Thanks for the quick response! I've cherry-picked the preparatory patch
to qom-next:
http://repo.or.cz/w/qemu/afaerber.git/shortlog/refs/heads/qom-next

/-F

-- 
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:[~2012-05-23 15:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-23  3:07 [PATCH qom-next 00/59] QOM CPUState, part 4: CPU_COMMON Andreas Färber
2012-05-23  3:08 ` [PATCH qom-next 58/59] xen_machine_pv: Use cpu_x86_init() to obtain X86CPU Andreas Färber
2012-05-23  3:08 ` [PATCH qom-next 59/59] cpu: Move halted and interrupt_request to CPUState Andreas Färber
2012-05-23 11:27 ` [PATCH qom-next 00/59] QOM CPUState, part 4: CPU_COMMON Stefano Stabellini
2012-05-23 15:36   ` Andreas Färber [this message]
2012-05-23 15:16 ` [Qemu-devel] " Andreas Färber
2012-05-23 19:36 ` Blue Swirl

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=4FBD0400.90101@suse.de \
    --to=afaerber@suse.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.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).