WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Xen

xen-devel

[Top] [All Lists]

Re: [Xen-devel] access shared_info?

To: Gerd Hoffmann <kraxel@xxxxxxx>
Subject: Re: [Xen-devel] access shared_info?
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 9 Jun 2006 15:35:09 +0100
Cc: Chris Wright <chrisw@xxxxxxxxxxxx>, Xen devel list <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Delivery-date: 2006年6月09日 07:35:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <448982A7.70804@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4486D496.1070905@xxxxxxx> <20b4659f13d0ed8c0ee5d23d93579b4c@xxxxxxxxxxxx> <4486F676.6080301@xxxxxxx> <7c8cd23f1fb1eafe50db8bf82cadad3a@xxxxxxxxxxxx> <4486FE71.9090606@xxxxxxx> <63a099e0b962a2154960cebf413487c2@xxxxxxxxxxxx> <44870C65.2030603@xxxxxxx> <20060607215500.GI2724@xxxxxxxxxxxxxxxxx> <44897B39.6070100@xxxxxxx> <1149861540.11958.199.camel@xxxxxxxxxxxxxxxxxxxxx> <448982A7.70804@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 9 Jun 2006, at 15:16, Gerd Hoffmann wrote:
The same code is in arch/x86_64/kernel/e820-xen.c and
include/asm-i386/mach-xen/setup_arch_post.h
The x86_64 code has diverged more from native than i386 in this area, it
would nice to reign it back in.
What is best to send patches against? xen-unstable? Or better linux-tip?
If you're looking to unify with your previous e820-faking patch: you can't. One is created before max_pfn is known (and is used by default to work out what max_pfn should be). The one you added depends on knowing max_pfn.
 -- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date: Re: [Xen-devel] access shared_info? , Gerd Hoffmann
Next by Date: [Xen-devel] Kernel panic: Unable to handle kernel paging request , Eric Windisch
Previous by Thread: Re: [Xen-devel] access shared_info? , Gerd Hoffmann
Next by Thread: Re: [Xen-devel] access shared_info? , Chris Wright
Indexes: [Date] [Thread] [Top] [All Lists]

Copyright ©, Citrix Systems Inc. All rights reserved. Legal and Privacy
Citrix This site is hosted by Citrix

AltStyle によって変換されたページ (->オリジナル) /