From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:47595)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1SPCPo-0005qr-Mf
	for qemu-devel@nongnu.org; Tue, 01 May 2012 08:42:49 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1SPCPi-0005Lb-JU
	for qemu-devel@nongnu.org; Tue, 01 May 2012 08:42:48 -0400
Received: from mx1.redhat.com ([209.132.183.28]:11691)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1SPCPi-0005Kw-BF
	for qemu-devel@nongnu.org; Tue, 01 May 2012 08:42:42 -0400
Message-ID: <4F9FDA38.6030108@redhat.com>
Date: Tue, 01 May 2012 15:42:32 +0300
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <4F9D797E.500@ilande.co.uk> <4F9D97F3.8080608@codemonkey.ws>
	<4F9E5028.7010306@redhat.com> <4F9E82C7.10706@ilande.co.uk>
	<4F9E9268.70408@redhat.com>
	<CAFEAcA_sKtzmHpFcdhkANLCY0=FuW0Hbof0ifp3uHM66NkWoOQ@mail.gmail.com>
	<4F9E9569.5000700@redhat.com>
	<CAFEAcA_wFfsq=PwHAc_r-2bgdwUpSHaTOaL2VPVCJSs9x_JT6A@mail.gmail.com>
	<4F9FD997.9000403@redhat.com>
	<CAFEAcA9O8yYtJLS8coTruffwAfN4A96f6Y-Cdi6-Y7c1-G9aJA@mail.gmail.com>
In-Reply-To: <CAFEAcA9O8yYtJLS8coTruffwAfN4A96f6Y-Cdi6-Y7c1-G9aJA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] Memory API: handling unassigned physical memory
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: Peter Maydell <peter.maydell@linaro.org>
Cc: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>, qemu-devel@nongnu.org, Anthony Liguori <anthony@codemonkey.ws>

On 05/01/2012 03:41 PM, Peter Maydell wrote:
> On 1 May 2012 13:39, Avi Kivity <avi@redhat.com> wrote:
> > On 04/30/2012 04:40 PM, Peter Maydell wrote:
> >> I wrote it for essentially the purpose described above :-)
> >> If you're the owner of the sysbus device in question then it's
> >> entirely fine as you are the one deciding whether to use the
> >> traditional map function or not.
> >>
> >> It's as good as we're going to get until QOM actually lets
> >> you export memory regions and pins, at which point we can just
> >> convert all the sysbus devices.
> >
> > Sure.  But expect breakage if sysbus changes, for example dropping use
> > of get_system_memory().
>
> That's OK, I'm happy to nak sysbus patches which break this
> use case :-)

sysbus should just die.

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