Re: [Xen-ia64-devel] please test machvec+sn2 tree
Hi, Alex, Jes, and all I tested the machvec+sn2 tree on Tiger4(which is montecito machine) and PRIMEQUEST480(which is madison machine). I can boot dom0, up,smp-domU, up,smp-domVTI on Tiger4. And I can boot dom0, up,smp-domU on PRIMEQUEST480. I can run unixbench up-domU, up-domVTI on Tiger4 completely. The test changeset is #13075 of http://free.linux.hp.com/~awilliam/xen-ia64-machvec/. Best Regards, Akio Takebe ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] please test machvec+sn2 tree
On Mon, 2006-12-18 at 00:39 +0900, Akio Takebe wrote: Hi, Alex, Jes, and all I tested the machvec+sn2 tree on Tiger4(which is montecito machine) and PRIMEQUEST480(which is madison machine). I can boot dom0, up,smp-domU, up,smp-domVTI on Tiger4. And I can boot dom0, up,smp-domU on PRIMEQUEST480. I can run unixbench up-domU, up-domVTI on Tiger4 completely. Great! Thanks for your testing help Akio, Alex ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [xen-ia64-devel] dom0 memory not responding to changing dom0_mem
Hi, David My elilo.conf entry looks like this image=vmlinuz-2.6.16.33-xen0 label=2.6.16.33-xen0 vmm=xen-3.0-unstable.gz initrd=initrd-2.6.16.33-xen0.img read-only append=sync_console dom0_mem=262144 root=/dev/sda2 3 I've tried changing dom0_mem to 256M, 128M and the dom0 system keeps coming up with 453M of memory. We need to split options of xen and dom0 with --. So you should use like the following option. append=sync_console dom0_mem=262144 -- root=/dev/sda2 3 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-devel] Question about evtchn_callback reentry
Hi Keir, I have some questions about evtchn_callback, As we know all external interrupts and events are deliver to dom0 by evtchn_callback, Are evtchn_callback reentered? I mean when evtchn_callbacak is executing on dom0, Another external interrupt or event may happen, can this event be deliverred immediately? I found __sti will set vcpu_info- evtchn_upcall_mask=0, which permits event deliverring. and __sti may be called at any device driver. If evtchn_callback can be reentered, how does it hanlde external interrupt privilege? If there is no special handling, low privileged interrupt may interrupt high privileged interrupt. BTW, I do see evtchn_callback reentry happen on IPF dom0, and that incur about 5% performance degradation with KB on VTI-domain compared to non_reentry. Thanks, Anthony ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
