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 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] Picking the P2M address range

To: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] Picking the P2M address range
From: Jes Sorensen <jes@xxxxxxx>
Date: Fri, 08 Jun 2007 10:08:38 +0200
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 08 Jun 2007 01:06:36 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070608021945.GB29054%yamahata@xxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <46682BCD.7070804@xxxxxxx> <20070608021945.GB29054%yamahata@xxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.4 (X11/20060527)
Isaku Yamahata wrote:
> On Thu, Jun 07, 2007 at 06:01:17PM +0200, Jes Sorensen wrote:
>> Hi,
>>
>> When dom0 boots it prints out a couple of lines like these:
>>
>> Xen p2m: assign p2m table of [0x0000003000000000, 0x0000003024000000)
>> Xen p2m: to [0x000001b040000000, 0x000001b043ffc000) (65536 KBytes)
>>
>> I am trying to figure out where the addresses in the first line
>> originate from. They are obviously picked by Xen and provided to dom0
>> somehow, but how and where?
> 
> I'm not sure I understand your question fully.
> It comes from memory descriptor which xen creates.
> I.e. it is calculated based on ia64_boot_param->efi_memmap.
> 
> dom_fw_init() creates it in xen.
> Presumably you have heavily modified those code and
> real memory map which boot loader(elilo?) creates is passed thourgh to dom0.

I see, so the addresses are calculated by dom0, not by Xen? Yes they
match my memory map, but because I have a hole in that space in the
physical map I see evtchn_set_pending() (in Xen) trying to scribble into
non existing memory which causes me an MCA :-(

Cheers,
Jes


_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel

<Prev in Thread] Current Thread [Next in Thread>