From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1J4L7p-0006jj-44
	for qemu-devel@nongnu.org; Mon, 17 Dec 2007 13:55:37 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1J4L7n-0006j4-Pl
	for qemu-devel@nongnu.org; Mon, 17 Dec 2007 13:55:36 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1J4L7n-0006j1-JA
	for qemu-devel@nongnu.org; Mon, 17 Dec 2007 13:55:35 -0500
Received: from mail.codesourcery.com ([65.74.133.4])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1J4L7n-0006RH-4G
	for qemu-devel@nongnu.org; Mon, 17 Dec 2007 13:55:35 -0500
From: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] xen / qemu convergence ?
Date: Mon, 17 Dec 2007 18:55:24 +0000
References: <18269.33299.414015.995882@mariner.uk.xensource.com>
	<200712171622.12475.paul@codesourcery.com>
	<18278.48926.479346.164587@mariner.uk.xensource.com>
In-Reply-To: <18278.48926.479346.164587@mariner.uk.xensource.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200712171855.25639.paul@codesourcery.com>
Reply-To: qemu-devel@nongnu.org
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: qemu-devel@nongnu.org
Cc: xen-devel@lists.xensource.com, Ian Jackson <Ian.Jackson@eu.citrix.com>

> I don't really understand why the vga is handled in this way in qemu
> but then I'm not an expert on PC graphics hardware.  Is it necessary
> or desirable for the VGA RAM to take up virtual address space in this
> way, or is there some other reason why VGA RAM in the ordinary vga
> driver is regarded as a special use of system RAM rather than as a
> special kind of hardware device ?

RAM is RAM. We don't care whether it's nominally owned by the vga controller 
or the "system". If you don't do this then all accesses have to go via 
horribly slow IO callbacks, which is just silly.

I've no idea what you're talking about when you say it's "taking up virtual 
address space".

Paul