From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:57009)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1RLXmZ-0003I7-N2
	for qemu-devel@nongnu.org; Wed, 02 Nov 2011 06:10:56 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1RLXmV-0000qn-Jz
	for qemu-devel@nongnu.org; Wed, 02 Nov 2011 06:10:55 -0400
Received: from mx1.redhat.com ([209.132.183.28]:59914)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <avi@redhat.com>) id 1RLXmV-0000qg-Br
	for qemu-devel@nongnu.org; Wed, 02 Nov 2011 06:10:51 -0400
Message-ID: <4EB11721.80807@redhat.com>
Date: Wed, 02 Nov 2011 12:10:41 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <1319983368-21801-1-git-send-email-avi@redhat.com>
	<4EB03597.2040307@codemonkey.ws>
In-Reply-To: <4EB03597.2040307@codemonkey.ws>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] [PULL 0/3] 128-bit support for the 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: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org, David Gibson <dwg@au1.ibm.com>

On 11/01/2011 08:08 PM, Anthony Liguori wrote:
> On 10/30/2011 09:02 AM, Avi Kivity wrote:
>> This somewhat controversial patchset converts internal arithmetic in the
>> memory API to 128 bits.
>>
>> It has been argued that with careful coding we can make 64-bit work as
>> well.  I don't think this is true in general - a memory router can
>> adjust
>> addresses either forwards or backwards, and some buses (PCIe) need the
>> full 64-bit space - though it's probably the case for all the
>> configurations
>> we support today.  Regardless, the need for careful coding means
>> subtle bugs,
>> which I don't want in a core API that is driven by guest supplied
>> values.
>>
>> Avi Kivity (3):
>>    Add support for 128-bit arithmetic
>>    memory: use 128-bit integers for sizes and intermediates
>>    Adjust system and pci address spaces to full 64-bit
>
> I now notice that this is not a PULL request...  Did you mess up the
> subject or the pull request?
>

I forgot to supply the pull info, which is:

  git://github.com/avikivity/qemu.git memory/int128

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