From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:53286)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1QN3xF-0005WJ-Fq
	for qemu-devel@nongnu.org; Thu, 19 May 2011 10:11:58 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1QN3xE-0004tU-Mm
	for qemu-devel@nongnu.org; Thu, 19 May 2011 10:11:57 -0400
Received: from mx1.redhat.com ([209.132.183.28]:58514)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1QN3xE-0004tH-Bx
	for qemu-devel@nongnu.org; Thu, 19 May 2011 10:11:56 -0400
Message-ID: <4DD52526.3070909@redhat.com>
Date: Thu, 19 May 2011 17:11:50 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <4DD3C5B9.1080908@redhat.com>	<4DD3D236.90708@siemens.com>	<4DD3D95E.2060105@redhat.com>	<4DD3E1B3.3020405@siemens.com>	<BANLkTimYH3-FkVQfdOXO+at2G0NhX-UaVg@mail.gmail.com>	<4DD3E610.1080201@siemens.com>	<4DD4199E.2000702@codemonkey.ws>	<4DD41DBB.2020108@web.de>	<20110519082644.GC28399@redhat.com>
	<4DD4D53F.1090108@web.de>	<4DD52082.1080804@codemonkey.ws>
	<4DD521C8.5020903@siemens.com> <4DD52363.7080201@codemonkey.ws>
In-Reply-To: <4DD52363.7080201@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1; 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: Anthony Liguori <anthony@codemonkey.ws>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel <qemu-devel@nongnu.org>, Gleb Natapov <gleb@redhat.com>, Peter Maydell <peter.maydell@linaro.org>

On 05/19/2011 05:04 PM, Anthony Liguori wrote:
>
> Right, the chipset register is mainly used to program the contents of 
> SMM.
>
> There is a single access pin that has effectively the same semantics 
> as setting the chipset register.
>
> It's not a per-CPU setting--that's the point.  You can't have one CPU 
> reading SMM memory at the exactly same time as accessing VGA.
>
> But I guess you can never have two simultaneous accesses anyway so 
> perhaps it's splitting hairs :-)

Exactly - it just works.

btw, a way to implement it would be to have two memory maps, one for SMM 
and one for non-SMM, and select between them based on the CPU mode.

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