[Top][All Lists]
[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 10:08:21 +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 10:06, Avi Kivity wrote:
> On 05/18/2011 10:40 PM, Jan Kiszka wrote:
>> On 2011-05-18 15:12, Avi Kivity wrote:
>> > void cpu_register_memory_region(MemoryRegion *mr,
>> target_phys_addr_t addr);
>>
>> OK, let's allow overlapping, but make it explicit:
>>
>> void cpu_register_memory_region_overlap(MemoryRegion *mr,
>> target_phys_addr_t addr,
>> int priority);
>>
>> We need that ordering, so we need an interface. Regions registered via
>> cpu_register_memory_region must not overlap with existing one or we will
>> throw an hwerror. And they shall get a low default priority.
>>
>
> PCI BARs can overlap with anything. So any region can overlap with any
> other region.
I know, but that result is unspecified anyway. The user (guest OS) can't
expect any reasonable result. We rather need priorities for useful
overlapping.
Jan
signature.asc
Description: OpenPGP digital signature
- Re: [Qemu-devel] [RFC] Memory API, (continued)
Re: [Qemu-devel] [RFC] Memory API, Avi Kivity, 2011/05/18
Re: [Qemu-devel] [RFC] Memory API, Richard Henderson, 2011/05/18
Re: [Qemu-devel] [RFC] Memory API, Avi Kivity, 2011/05/18
Re: [Qemu-devel] [RFC] Memory API, Jan Kiszka, 2011/05/18
- Re: [Qemu-devel] [RFC] Memory API, Avi Kivity, 2011/05/19
- Re: [Qemu-devel] [RFC] Memory API,
Jan Kiszka <=
- Re: [Qemu-devel] [RFC] Memory API, Avi Kivity, 2011/05/19
- Re: [Qemu-devel] [RFC] Memory API, Jan Kiszka, 2011/05/19
- Re: [Qemu-devel] [RFC] Memory API, Avi Kivity, 2011/05/19
- Re: [Qemu-devel] [RFC] Memory API, Jan Kiszka, 2011/05/19
- Re: [Qemu-devel] [RFC] Memory API, Avi Kivity, 2011/05/19
Re: [Qemu-devel] [RFC] Memory API, Anthony Liguori, 2011/05/19