qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [RFC] Memory API


From: Anthony Liguori
Subject: Re: [Qemu-devel] [RFC] Memory API
Date: Thu, 19 May 2011 09:37:02 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Lightning/1.0b2 Thunderbird/3.1.10

On 05/19/2011 09:28 AM, Jan Kiszka wrote:
On 2011-05-19 16:25, Anthony Liguori wrote:
On 05/19/2011 09:20 AM, Jan Kiszka wrote:
On 2011-05-19 16:15, Anthony Liguori 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. 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.

So....  do you do:

isa_register_region(ISABus *bus, MemoryRegion *mr, int priority)
{
    chipset_register_region(bus->chipset, mr, priority + 1);
}

I don't really understand how you can fold everything into one table and not allow devices to override their parents using priorities.

Regards,

Anthony Liguori


Jan





reply via email to

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