On 01/04/2011 10:42 AM, Jan Kiszka wrote:
>
> Sounds really frightening... this glue code is a real breeding ground
> for subtle bugs and merge problems.
...and that's why we are more than late with unifying it into a single
code base.
After that upcoming cleanup round we will have three majo
Am 03.01.2011 17:09, Avi Kivity wrote:
> On 01/03/2011 10:32 AM, Jan Kiszka wrote:
>> All previously sent patches against current uq combined, some smaller
>> tweaks applied, and 4 new patches added. Major news is support for
>> using up to 16M BIOSes and optional code dump for cpu_dump_state. Thos
On 01/03/2011 10:32 AM, Jan Kiszka wrote:
All previously sent patches against current uq combined, some smaller
tweaks applied, and 4 new patches added. Major news is support for
using up to 16M BIOSes and optional code dump for cpu_dump_state. Those
features are already present qemu-kvm but were
All previously sent patches against current uq combined, some smaller
tweaks applied, and 4 new patches added. Major news is support for
using up to 16M BIOSes and optional code dump for cpu_dump_state. Those
features are already present qemu-kvm but were reworked to provide
cleaner upstream versio
