From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir@xensource.com>
Subject: Re: RFC: vaddr_t and vsize_t
Date: Wed, 17 Jan 2007 15:49:35 +0000
Message-ID: <C1D3F60F.7C1A%keir@xensource.com>
References: <200701171617.33273.Christoph.Egger@amd.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <200701171617.33273.Christoph.Egger@amd.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Christoph Egger <Christoph.Egger@amd.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 17/1/07 15:17, "Christoph Egger" <Christoph.Egger@amd.com> wrote:

> vaddr_t is used when a virtual address is meant. It is an unsigned integer and
> its size always matches sizeof(void *).
> vsize_t is used when the virtual address space is meant. It is an unsigned
> integer and its size always matches the whole size of the virtual address
> space.

Is this distinction ever useful?

The assumption that a pointer fits in a long is rather ingrained into Xen's
code base. Any attempt to remove that assumption is going to need some big
patches, and it's really not clear that we ought to care as I'm sure it's
true for any architecture we can conceive of caring one jot about.

 -- Keir