From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MruWk-0007Vy-H4
	for qemu-devel@nongnu.org; Sun, 27 Sep 2009 10:15:02 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MruWe-0007TA-Fe
	for qemu-devel@nongnu.org; Sun, 27 Sep 2009 10:15:00 -0400
Received: from [199.232.76.173] (port=52203 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MruWe-0007T1-9n
	for qemu-devel@nongnu.org; Sun, 27 Sep 2009 10:14:56 -0400
Received: from mx1.redhat.com ([209.132.183.28]:24028)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1MruWd-0000yl-Pq
	for qemu-devel@nongnu.org; Sun, 27 Sep 2009 10:14:56 -0400
Message-ID: <4ABF7359.8050404@redhat.com>
Date: Sun, 27 Sep 2009 16:14:49 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [PATCHv2] qemu: target library, use it in msix
References: <20090923200635.GA21246@redhat.com>
	<f43fc5580909241050jc8b82fbsb25eef096f8105eb@mail.gmail.com>
	<20090927082020.GA23513@redhat.com> <4ABF4110.80300@redhat.com>
	<20090927114459.GA24031@redhat.com> <4ABF52A5.5080409@redhat.com>
	<20090927120041.GB24031@redhat.com> <4ABF585D.7000201@redhat.com>
	<20090927140841.GA24769@redhat.com>
In-Reply-To: <20090927140841.GA24769@redhat.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org

On 09/27/2009 04:08 PM, Michael S. Tsirkin wrote:
>
>    
>>> In practice, the only user is now msix and it does not.  It has 0x1000
>>> as a constant parameter.  For target_phys_addr_t users if we ever have
>>> them, we'll just add target_phys_page_align. Generally it's unusual for
>>> devices to care about size of target physical page.
>>>
>>>        
>> I'd fill better with uint64_t, at least that won't truncate.
>>      
> Doesn't naming it target_page_align32 address this concern?
>    

How can the caller (except in your special case) know if it has a 
quantity that will fit in 32 bits?


-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.