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: Avi Kivity
Subject: Re: [Qemu-devel] [RFC] Memory API
Date: Thu, 19 May 2011 11:43:23 +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 11:25 AM, Jan Kiszka wrote:
>
>  Unspecified doesn't mean abort.  It means we need to specify something
>  (which translates to: we get to pick the priorities).

Of course, PCI bars would have to be registered via
cpu_register_memory_region_overlap, just specifying the default
priority. Here we know that overlapping can happen and is not a bug in
the board emulation. I want to avoid that such use cases make
overlapping generally legal, papering over real bugs.

But those are the majority of regions. There are a few extra RAM and ROM and fixed function regions, but these are hardly likely to clash.

--
error compiling committee.c: too many arguments to function




reply via email to

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