On Wed, May 23, 2012 at 3:07 AM, Andreas Färber wrote:
> Hello,
>
> 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
>
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
On Wed, 23 May 2012, Andreas Färber wrote:
> Hello,
>
> 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
Am 23.05.2012 05:07, schrieb Andreas Färber:
> This series, based on qom-next and the two pending ARM cleanup patches, [...]
Update: I've applied the aforementioned patches, so this series applies
unchanged to qom-next now.
> Available for testing and cherry-picking (not pulling!) from:
> git://g
Hello,
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 al
