On Wed, May 18, 2011 at 06:42:14PM +0300, Avi Kivity wrote:
> On 05/18/2011 06:36 PM, Jan Kiszka wrote:
> >>
> >> We need to head for the more hardware-like approach. What happens when
> >> you program overlapping BARs? I imagine the result is
> >> implementation-defined, but ends up with one region decoded in
> >> preference to the other. There is simply no way to reject an
> >> overlapping mapping.
> >
> >But there is also now simple way to allow them. At least not without
> >exposing control about their ordering AND allowing to hook up managing
> >code (e.g. of the PCI bridge or the chipset) that controls registrations.
>
> What about memory_region_add_subregion(..., int priority) as I
> suggested in another message?
Haven't saw another message yet, but how caller knows about priority?