[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH qom-next 00/59] QOM CPUState, part 4: CPU_COMMON

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@xxxxxxxxxxxxx>

Thanks for the quick response! I've cherry-picked the preparatory patch
to qom-next:


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

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.