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: Jan Kiszka
Subject: Re: [Qemu-devel] [RFC] Memory API
Date: Thu, 19 May 2011 18:25:14 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666

On 2011-05-19 18:17, Gleb Natapov wrote:
> On Thu, May 19, 2011 at 05:40:50PM +0300, Avi Kivity wrote:
>> On 05/19/2011 05:37 PM, Anthony Liguori wrote:
>>>
>>> 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.
>>
>> Think of how a window manager folds windows with priorities onto a
>> flat framebuffer.
>>
>> You do a depth-first walk of the tree.  For each child list, you
>> iterate it from the lowest to highest priority, allowing later
>> subregions override earlier subregions.
>>
> And how you set those priorities in a sensible way? Why two device on a
> PCI bus will want to register their memory region with anything but
> highest priority? And if you let PCI subsystem to assign priorities how
> it will coordinate with ISA subsystem/memory controller what priorities
> to assign to get meaningful system?

Priorities >default will only be used for explicit overlays, e.g. RAM
over MMIO in PAM regions. Non-default priorities won't be assigned to
normal PCI bars or any other device's region.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux



reply via email to

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