|
From: | Avi Kivity |
Subject: | Re: [Qemu-devel] [RFC] Memory API |
Date: | Thu, 19 May 2011 16:26:40 +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.fc14 Lightning/1.0b3pre Thunderbird/3.1.10 |
On 05/19/2011 04:23 PM, Anthony Liguori wrote:
Actually, things are a bit more complicated: This layer has to properly adopt the coalescing properties of underlying regions or we cause performance regressions to VGA emulation. That means it has to register dispatching slots of the corresponding size and set the coalescing flagaccordingly. And it likely need to adjust them as the regions below change.As I mentioned in another thread, I don't think we want to "design" coalescing into the API. Coalescing is something that breaks through abstractions layers and is really just a hack.
It's impossible not to design it into the API. The layer which wants to do coalescing (the device) has no idea if and where its memory is mapped.
-- error compiling committee.c: too many arguments to function
[Prev in Thread] | Current Thread | [Next in Thread] |