Re: [Xen-ia64-devel] MCA patches causing Xen to hang on sn2
Hi Jes, I tried this and attached the output below. I was wondering why we seem to allocate pages to MCA handlers on 64 processors even if we only boot 8, but thats a detail. It's OK. The mca_data is allocated up to NR_CPUS(=64) in MCA initialization routine. And I think that your system will boot up if nomca is specified in boot parameters. This didn't make any difference :( Please confirm whether to have specified nomca for not only the Domain0 boot parameter but also Xen. And please send me a boot log with nomca too. Thanks, KAZ ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] MCA patches causing Xen to hang on sn2
SUZUKI Kazuhiro wrote: Hi Jes, I tried this and attached the output below. I was wondering why we seem to allocate pages to MCA handlers on 64 processors even if we only boot 8, but thats a detail. It's OK. The mca_data is allocated up to NR_CPUS(=64) in MCA initialization routine. And I think that your system will boot up if nomca is specified in boot parameters. This didn't make any difference :( Please confirm whether to have specified nomca for not only the Domain0 boot parameter but also Xen. And please send me a boot log with nomca too. Thanks, KAZ Hi Kaz, I just did 'nomca' on the boot line. Can you explain to me how I do it for dom0 too? Thanks, Jes ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] MCA patches causing Xen to hang on sn2
Hi Jes,
For Xen boot option, you have to specify nomca in the left side of append
line.
For Dom0 boot option, you have to specify nomca in the right side of append
line.
Example:
append=nomca com2=115200,8n1 console=com2 -- nomca console=tty0
console=ttyS1,115200,8n1 rhgb root=/dev/sda2
Xen boot options ++ Dom0 boot options
If you cannot start up Xen/Dom0, please stop the salinfod in Dom0.
Nevertheless if you cannot start up Xen/Dom0, could you send the serial log to
me?
Best regards,
Kan
SUZUKI Kazuhiro wrote:
Hi Jes,
I tried this and attached the output below. I was wondering why we
seem to allocate pages to MCA handlers on 64 processors even if we
only boot 8, but thats a detail.
It's OK. The mca_data is allocated up to NR_CPUS(=64) in MCA
initialization routine.
And I think that your system will boot up if nomca is specified
in boot parameters.
This didn't make any difference :(
Please confirm whether to have specified nomca for not only the
Domain0 boot parameter but also Xen. And please send me a boot log
with nomca too.
Thanks,
KAZ
Hi Kaz,
I just did 'nomca' on the boot line. Can you explain to me how I do
it for dom0 too?
Thanks,
Jes
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] Re: [patch 1/4] macvec + sn2 support
On Fri, 2006-11-24 at 17:28 +0100, Jes Sorensen wrote: Ok, it seems we're seeing major operator error here. This time it should be there - otherwise please shoot me :( Hi Jes, I tried a quick boot test, but never got any console output on an HP box. It seemed to MCA after a bit too. I haven't had a chance to debug yet though. Thanks, Alex -- Alex Williamson HP Open Source Linux Org. ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] Re: [patch 1/4] macvec + sn2 support
Alex Williamson wrote: On Fri, 2006-11-24 at 17:28 +0100, Jes Sorensen wrote: Ok, it seems we're seeing major operator error here. This time it should be there - otherwise please shoot me :( Hi Jes, I tried a quick boot test, but never got any console output on an HP box. It seemed to MCA after a bit too. I haven't had a chance to debug yet though. Thanks, H, I wonder if the machvec is setup correctly on the ZX1 or if I am nooping something that needs to be set for you. Sorry I haven't really been able to test this on ZX1 before posting the patches. I tried to add all the stuff I thought was needed. Cheers, Jes ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] Re: [patch 1/4] macvec + sn2 support
On Mon, 2006-11-27 at 16:34 +0100, Jes Sorensen wrote: Alex Williamson wrote: On Fri, 2006-11-24 at 17:28 +0100, Jes Sorensen wrote: Ok, it seems we're seeing major operator error here. This time it should be there - otherwise please shoot me :( Hi Jes, I tried a quick boot test, but never got any console output on an HP box. It seemed to MCA after a bit too. I haven't had a chance to debug yet though. Thanks, H, I wonder if the machvec is setup correctly on the ZX1 or if I am nooping something that needs to be set for you. Sorry I haven't really been able to test this on ZX1 before posting the patches. I tried to add all the stuff I thought was needed. Are the patches known to work on DIG? That would narrow the debugging quite a bit. Unless we start adding IOMMU support, the zx1 machvec doesn't buy us much over DIG. Thanks, Alex -- Alex Williamson HP Open Source Linux Org. ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] Re: [patch 1/4] macvec + sn2 support
Alex Williamson wrote: Sorry I haven't really been able to test this on ZX1 before posting the patches. I tried to add all the stuff I thought was needed. Are the patches known to work on DIG? That would narrow the debugging quite a bit. Unless we start adding IOMMU support, the zx1 machvec doesn't buy us much over DIG. Thanks, Nope, I only have an easy way to test on SN2. The dig and zx1 machvecs should be pretty identical though for now. Cheers, Jes ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] [PATCH] fix p2m table destruction
On Fri, 2006-11-24 at 16:19 +0900, Isaku Yamahata wrote: Modify to introduce delayed p2m table destruction Applied, thanks for fixing this! Alex -- Alex Williamson HP Open Source Linux Org. ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel][PATCH]Idle domain doesn't need to save and restore fph
On Mon, 2006-11-27 at 13:41 +0800, Xu, Anthony wrote: Idle domain doesn't need to save and restore fph. Applied, good find. Thanks, Alex -- Alex Williamson HP Open Source Linux Org. ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] [PATCH 0/7 TAKE 2] xenoprof for xen/ia64
On Wed, 2006-11-22 at 21:03 +0900, Isaku Yamahata wrote:
Now xenoprof/common changes are committed.
(At least they are in staging tree.)
I attached updated xenoprof/ia64 patches as tar ball for convinience.
Hi Isaku,
A few comments:
12592_7aa7bb96eec7_xenoprof_ia64_xen_side.patch
$ grep ^+#if.*def XEN 12592_7aa7bb96eec7_xenoprof_ia64_xen_side.patch | wc -l
126
Wow. Makes perfmon.c a little difficult to read in places, but the file
is so big there are really only a few places where it gets in the way.
Some linux-null headers may clean up a few of the trivial ones towards
the top of the file. I don't have any good suggestions for the others.
+ if ( !softirq_pending(smp_processor_id()) ) {
+ if (!can_do_pal_halt)
+ safe_halt();
+ else
+ cpu_relax();
+ }
Is this logic backwards? It's opposite the kernel.
--- a/xen/include/public/arch-ia64.hThu Oct 26 14:27:25 2006 +0900
+++ b/xen/include/public/arch-ia64.hWed Nov 22 20:41:08 2006 +0900
@@ -388,6 +388,9 @@ DEFINE_XEN_GUEST_HANDLE(vcpu_guest_conte
#define IA64_DOM0VP_tlb_untrack_page10
+/* xen perfmon */
+#define IA64_DOM0VP_perfmon 11
+
We don't have IA64_DOM0VP_tlb_untrack_page in the upstream tree, should
this be IA64_DOM0VP op #8? (or are we missing a patch upstream)
12593_12361c7cc046_xenoprof_ia64_linux_side.patch
Having two different definitions for __perfmon_init/exit() for the
non-Xen code path is confusing. Consider accessing it through a macro
in the Xen path (ex. xen_permon_init). Then __perfmon_init/exit() could
be static for the non-Xen case (not that I'm a fan of adding more
#ifdefs). Perhaps we need a #define LINUX_STATIC (?)
Thanks,
Alex
--
Alex Williamson HP Open Source Linux Org.
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] Re: [patch 1/4] macvec + sn2 support
On Mon, 2006-11-27 at 16:45 +0100, Jes Sorensen wrote: Alex Williamson wrote: Sorry I haven't really been able to test this on ZX1 before posting the patches. I tried to add all the stuff I thought was needed. Are the patches known to work on DIG? That would narrow the debugging quite a bit. Unless we start adding IOMMU support, the zx1 machvec doesn't buy us much over DIG. Thanks, Nope, I only have an easy way to test on SN2. The dig and zx1 machvecs should be pretty identical though for now. Ok, the first problem was actually pretty easy, the hp directory under arch/ia64 wasn't getting built. Now I get to here: (XEN) Time init: (XEN) System Time: 38776ns (XEN) scale: 281426057 (XEN) Boot processor id 0x0/0x0 (XEN) num_online_cpus=1, max_cpus=64 (XEN) cpu_init: current=f7ff (XEN) vhpt_init: vhpt paddr=0x9a61e, end=0x9a61e (hang) Alex -- Alex Williamson HP Open Source Linux Org. ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] xen/ia64 kernel BUG while rebooting
Hi, I'm debugging the following Bugzilla now. RH Bugzilla#203032: xen/ia64 kernel BUG while rebooting https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203032 RHEL5beta and FC6 still show the CallTrace while rebooting. I check why it is shown. I found thd CallTrace is not shown if we reboot after doing the below. # /etc/xen/scripts/network-bridge stop I think it should be happened also by using source of xen-ia64-unstable. (not RH source) But e1000_shutdown() is not called when I use source of xen-ia64-unstable. I don't know why yet. I'll continue to debug it. If you have comments, please tell me. Best Regards, Akio Takebe ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
[Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#12525
Xen/IA64 Healthiness Report Several issues: 1. VTI Linux domain boot slowly, if enabled 'serial=pty'. (performance issues): 2. SMPVTI LTP test has a 100% performance downgrade. 3. UPVTI Kernel build has a performance downgrade. Testing Environment: Platform: Tiger4 Processor: Itanium 2 Processor Logic Processors number: 8 (2 processors with Due Core) PAL version: 8.15 Service OS: RHEL4u3 IA64 SMP with 2 VCPUs VTI Guest OS: RHEL4u2 RHEL4u3 XenU Guest OS: RHEL4u2 Xen IA64 Unstable tree: 12525:7e7846ea4ab3 Xen Schedule: credit VTI Guest Firmware Flash.fd.2006.11.07 MD5: 797c2d6c391a6fc6f16d267e01b382f8 Summary Test Report: - Total cases: 16 Passed:16 Failed: 0 Case Name Status Case Description Four_SMPVTI_Coexistpass 4 VTI (mem=256, vcpus=2) Two_UP_VTI_Co pass 2 UP_VTI (mem=256) One_UP_VTIpass1 UP_VTI (mem=256) One_UP_XenU pass1 UP_xenU(mem=256) SMPVTI_LTPpassVTI (vcpus=4, mem=512) run LTP SMPVTI_and_SMPXenU pass 1 VTI + 1 xenU (mem=256 vcpus=2) Two_SMPXenU_Coexistpass 2 xenU (mem=256, vcpus=2) One_SMPVTI_4096M pass 1 VTI (vcpus=2, mem=4096M) SMPVTI_Network pass 1 VTI (mem=256,vcpu=2) and 'ping' SMPXenU_Networkpass 1 XenU (vcpus=2) and 'ping' One_SMP_XenU pass 1 SMP xenU (vcpus=2) One_SMP_VTIpass 1 SMP VTI (vcpus=2) SMPVTI_Kernel_Build pass VTI (vcpus=4) and do Kernel Build Four_SMPVTI_Coexist pass 4 VTI domains( mem=256, vcpu=2) SMPVTI_Windows pass SMPVTI windows(vcpu=2) SMPWin_SMPVTI_SMPxenU passSMPVTI Linux/Windows XenU UPVTI_Kernel_Build pass 1 UP VTI and do kernel build Notes: - The last stable changeset: - 12014:9c649ca5c1cc Thanks, Zhangjingke ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
