From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: access shared_info? Date: Wed, 07 Jun 2006 18:59:16 +0200 Message-ID: <448705E4.80007@suse.de> References: <4486D496.1070905@suse.de> <20b4659f13d0ed8c0ee5d23d93579b4c@cl.cam.ac.uk> <4486F676.6080301@suse.de> <7c8cd23f1fb1eafe50db8bf82cadad3a@cl.cam.ac.uk> <4486FE71.9090606@suse.de> <63a099e0b962a2154960cebf413487c2@cl.cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <63a099e0b962a2154960cebf413487c2@cl.cam.ac.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Xen devel list List-Id: xen-devel@lists.xenproject.org > Oh, I see it's moved to a new function. I guess that's okay, although > couldn't you fake up an e820 map and call legacy_init_iomem_resource on > the domU path, rather than having to pull code out into a new function? Should work equally well, yes. > Does this patch change behaviour for dom0 at all? I think /proc/iomem > already looks like native there? The kernel code and kernel data regions are initialized and registered now. > Also the patch will need to include > x86/64 too. I'll have a look. cheers, Gerd -- Gerd Hoffmann http://www.suse.de/~kraxel/julika-dora.jpeg