On 05/19/2011 12:24 PM, Jan Kiszka wrote:
On 2011-05-19 10:43, Avi Kivity wrote:
> 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.
You are probably only thinking about x86, which does not provide the
majority of QEMU devices.
The next version of the API will include an overlap property.
--
error compiling committee.c: too many arguments to function
