From mboxrd@z Thu Jan  1 00:00:00 1970
From: Gerd Hoffmann <kraxel@suse.de>
Subject: Re: access shared_info?
Date: Wed, 07 Jun 2006 18:27:29 +0200
Message-ID: <4486FE71.9090606@suse.de>
References: <4486D496.1070905@suse.de>
	<20b4659f13d0ed8c0ee5d23d93579b4c@cl.cam.ac.uk>
	<4486F676.6080301@suse.de>
	<7c8cd23f1fb1eafe50db8bf82cadad3a@cl.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <7c8cd23f1fb1eafe50db8bf82cadad3a@cl.cam.ac.uk>
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: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Xen devel list <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

>> How about the attached patch?  It makes /proc/iomem under xen dom0 look
>> like on native hardware.  Also for domU it has some sensible values then
>> instead of being empty.
> 
> Plausible, perhaps with cleanup (e.g., why change the prototype of
> legacy_init_iomem_resource

Well, there is no point in carring around those two arguments.  It's not
needed, and the third one (crash kernel area) isn't passed though
anyway.  So while touching it anyway I've dropped them as cleanup.  Not
exactly xen-related, I can try to push that upstream too ;)

> and remove non-Xen code, increasing the diff
> against native?).

Where is non-xen code removed?

cheers,

  Gerd

-- 
Gerd Hoffmann <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg