qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH 00/13] vga: dirty log cleanup, more linear mappi


From: Avi Kivity
Subject: Re: [Qemu-devel] [PATCH 00/13] vga: dirty log cleanup, more linear mapping
Date: Thu, 23 Jun 2011 14:54:09 +0300
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110428 Fedora/3.1.10-1.fc15 Thunderbird/3.1.10

On 06/23/2011 02:52 PM, Jan Kiszka wrote:
On 2011-06-23 13:44, Avi Kivity wrote:
>  On 06/23/2011 02:39 PM, Jan Kiszka wrote:
>>  On 2011-06-23 13:11, Avi Kivity wrote:
>>  >   On 06/14/2011 07:53 PM, Jan Kiszka wrote:
>>  >>   A few optimizations and cleanups I came across when trying to
>>  speed up
>>  >>   slow graphical grub unter non-cirrus vga. This series
>>  >>     - eliminates log_start/stop CPUPhysMemoryClient callbacks
>>  >>     - accelerates chain 4 vga mode under KVM
>>  >>     - fixes reset of vmware-vga
>>  >>     - cleans up vmware-vga a bit
>>  >>
>>  >>   At least patch 8 is a candiate for 0.15 and stable.
>>  >
>>  >   Yikes, most is all going away with the memory API (except the extra
>>  >   acceleration).
>>
>>  Can't follow yet. What goes away?
>
>  All the games with starting and stopping the log.

That's what this series does as well (among other things).

That the new API will look different for the devices is clear, also that
it may differ on the listener side. But if your API will not need any
kind of explicit start/stop callbacks for memory clients, then we are
moving in the right direction.

Yes, looking at them, they certainly match what I'm doing. Will be fun rebasing over them.

>   Now you start the log
>  on the vram memory region and all the aliases, maps/unmaps, and mode
>  changes are handled automatically.
>
>  But I didn't get the patches yet, so no idea how much overlap.

The patches were already sent last week, see [1] for the full history.

Jan

[1] http://thread.gmane.org/gmane.comp.emulators.qemu/106150


Yeah, I missed them, even though you copied me.

--
error compiling committee.c: too many arguments to function




reply via email to

[Prev in Thread] Current Thread [Next in Thread]