Re: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#10811:254c090854de

[Isaku Yamahata <yamahata@xxxxxxxxxxxxx>]

Hi.

On Thu, Jul 27, 2006 at 05:43:36PM +0800, You, Yongkang wrote:
> Other Issue:
> ----------------------------
> 1. SMP_VTI_Boot may stop to boot after "Calibrating delay loop..."

I'm seeing a similar issue.
My case is UP VTI domain. VTI domain doesn't share pcpu with dom0.
FWIW

- vITV
  By inserting debug print code to vtm_set_itv(), vtm_set_itm() and 
  vtm_timer_fn(), I found that vtm_set_itv() wasn't called.
  vITV.m bit isn't cleared so that VTI domain doesn't receives 
  timer interrupt. Thus the calibrating delay loop isn't terminated.
  On the other hand Linux/ia64 surely clears itv.m in ia64_cpu_local_tick()
  which is called before the calibration.

- struct arch_vmx_struct::vtm
  VTI domain code seems to assume that vtime_t::vtm_timer is running on
  same physical cpu of its vcpu.
  Probably the attached patch is needed for credit scheduler.
  It is only compile tested.


> 2. SMP Xen0 couldn't see all vcpus, no matter dom0_max_vcpus=4 or 2.
> "xm vcpu-list" can show the other vcpus status are "P"

xenLinux default config has CONFIG_NR_CPUS=4.
Does increasing it up to 8 or 16 make difference?

Thanks.
-- 
yamahata

Attachment: 10774:41d895195c5a_vtm_timer.patch
Description: Text document

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