RE: [Xen-ia64-devel] Xen is now runnnig at Bull

["Xu, Anthony" <anthony.xu@xxxxxxxxx>]

>       *cmdline_p = __va(ia64_boot_param->command_line);
>is generating an alt dtlb miss, which is certainly not expected, right ?
>I am now trying to understand why!

The VTI domain0 can boot on my local machine based on ver. 6456. I also changed 
double mapping to single mapping on vti domain.
I'll merge this patch into latest version, and send out the patch ASAP.
Currently VTI domain0 can boot, VTI domainN can't.

Thanks
Anthony

>-----Original Message-----
>From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Tristan
>Gingold
>Sent: 2005年9月7日 17:27
>To: Tian, Kevin; xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: Re: [Xen-ia64-devel] Xen is now runnnig at Bull
>
>Le Mercredi 07 Septembre 2005 03:54, Tian, Kevin a écrit :
>> From: Tristan Gingold
>[...]
>
>> >Sorry, I was unable to create a changeset, hg tried to open this file:
>> >.hg/data/.hgtags.d
>> >and I suppose it has been removed by a 'make clean'...
>>
>> I'm not sure whether it's clean to do that, but you may copy .hgtags.d
>> from another repository if both have the same parent. I usually have one
>> copy cloned from xen-ia64-unstable.hg, and with another working copy
>> child of the former. When working copy failed like above reason, I can
>> retrieve from another one.
>Thanks to the tip.  To be investigated...
>
>> >I will try to run xen+xenlinux on our novascale machine.
>I tried yesterday but unfortunatly it doesn't work.  The messages are:
>(XEN) *** LOADING DOMAIN 0 ***
>(XEN) METAPHYSICAL MEMORY ARRANGEMENT:
>(XEN)  Kernel image:  4000000->4afda48
>(XEN)  Entry address: 4018160
>(XEN)  Init. ramdisk:   (NOT IMPLEMENTED YET)
>(XEN) Sync i/d cache for dom0 image SUCC
>(XEN) Dom0: 0xf0000000040ac1f0, domain: 0xf0000000040ac1f0
>(XEN) Domain0 EFI passthrough:enable lsapic entry: 0xf00000007ff5d25c
>(XEN) ACPI: [APIC:0x07] ignored 127 entries of 128 found
>(XEN) Total 128 lsapic entry
>(XEN)  ACPI 2.0=7ff5d000lx ACPI=7ff5e000lx SMBIOS=f00a0lx HCDP=7ff4b000lx
>(XEN) domain mem: type=4, attr=0x8,
>range=[0x0000000010000000-0x0000000010100000) (1MB)
>(XEN) domain mem: type=13, attr=0x8,
>range=[0x0000000010100000-0x0000000010200000) (1MB)
>(XEN) domain mem: type=7, attr=0x8,
>range=[0x0000000010200000-0x0000000030000000) (510MB)
>(XEN) domain mem: type=12, attr=0x8000000000000001,
>range=[0x00000ffffc000000-0x0000100000000000) (64MB)
>(XEN) Scrubbing Free RAM: .....................done.
>(XEN) About to call init_trace_bufs()
>(XEN) About to call startup_cpu_idle_loop()
>(XEN) vcpu_get_lrr0: Unmasked interrupts unsupported
>(XEN) vcpu_get_lrr1: Unmasked interrupts unsupported
>(XEN) ****** vcpu_set_next_timer called during idle!!
>(XEN) ****** vcpu_set_next_timer called during idle!!
>(XEN) ****** vcpu_set_next_timer called during idle!!
>(XEN) ****** vcpu_set_next_timer called during idle!!
>The 'called during idle' line is repeated endlessly.
>
>> >As it was already said, we are interested by using xen-vti.
>> Unfortunatly, it
>> >still doesn't work.  No output on the console.  We had had messages
>> > with a previous version.  To be investigated.
>> Now we're in process of merging non-vti and vti code, and then sometimes
>> you may see instability. We're also looking at it now. ;-)
>Sure, but it boots on a tiger2.
>With the ITP, I found this line in setup.c(early_setup_arch)
>       *cmdline_p = __va(ia64_boot_param->command_line);
>is generating an alt dtlb miss, which is certainly not expected, right ?
>I am now trying to understand why!
>
>Thanks.
>Tristan.
>
>
>_______________________________________________
>Xen-ia64-devel mailing list
>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-ia64-devel

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