|
| From: | Avi Kivity |
| Subject: | Re: [Qemu-devel] [RFC] Memory API |
| Date: | Thu, 19 May 2011 17:31:15 +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 05:28 PM, Jan Kiszka wrote:
>> >> Priorities would be local, so the normal tree would look like this: >> >> - CPU:0 >> - i440fx:0 >> - PIIX3:0 >> - DeviceA >> - PCI-DeviceB:0 >> >> If the i440fx would like to map something different over DeviceA (or >> parts of it), it would create a region of prio 1 or higher. > > If it's local, then you need a local dispatch table, no? Not working for the coalescing reason pointed out before.
+ RAM (including framebuffers)
It's also more handy to rely on the core to do the proper dispatching then write your own logic over and over again. The core has to deal with overlapping anyway.
Plus, to reiterate, if you have the information you can calculate a flattened global dispatch table taking into account all offsets and priorities.
-- error compiling committee.c: too many arguments to function
| [Prev in Thread] | Current Thread | [Next in Thread] |