From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:43769)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1QMjvo-0006kf-7M
	for qemu-devel@nongnu.org; Wed, 18 May 2011 12:49:08 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1QMjvn-0003TC-FI
	for qemu-devel@nongnu.org; Wed, 18 May 2011 12:49:08 -0400
Received: from mx1.redhat.com ([209.132.183.28]:16682)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1QMjvn-0003T6-4H
	for qemu-devel@nongnu.org; Wed, 18 May 2011 12:49:07 -0400
Message-ID: <4DD3F87E.7090505@redhat.com>
Date: Wed, 18 May 2011 19:49:02 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <4DD3C5B9.1080908@redhat.com> <4DD3D236.90708@siemens.com>
	<4DD3E271.2010903@codemonkey.ws> <4DD3E53F.202@redhat.com>
	<4DD3F218.2040807@redhat.com> <4DD3F6EF.5000007@siemens.com>
In-Reply-To: <4DD3F6EF.5000007@siemens.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [RFC] Memory API
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel <qemu-devel@nongnu.org>

On 05/18/2011 07:42 PM, Jan Kiszka wrote:
> On 2011-05-18 18:21, Avi Kivity wrote:
> >  On 05/18/2011 06:26 PM, Avi Kivity wrote:
> >>>  This is about registration.  Right now you can only register IO
> >>>  intercepts in the chipset, not on a per-CPU basis.  We could just as
> >>>  easily have:
> >>>
> >>>  CPUState {
> >>>      MemoryRegion apic_region;
> >>>  };
> >>>
> >>>  per_cpu_register_memory(env,&env->apic_region);
> >>>
> >>
> >>
> >>  Right.  Or all memory per-cpu, with two sub-regions:
> >>
> >>   - global memory
> >>   - overlaid apic memory
> >>
> >>  for this, we need to have well defined semantics for overlap (perhaps
> >>  a priority argument to memory_region_add_subregion).
> >
> >  Or even
> >
> >  cpu_memory_region
> >     |
> >     +-- global memory map (prio 0)
> >     |    |
> >     |    +-- RAM (prio 0)
> >     |    |
> >     |    +-- PCI (prio 1)
>
> It depends on the chipset and its configuration (via PAM e.g.) in what
> region which takes precedence. Fixed prios do not help here.

The priorities are determined by the device code.

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