[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-ia64-devel] xen on hp rx2600


  • To: "Alex Williamson" <alex.williamson@xxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Thu, 10 Nov 2005 14:24:48 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 10 Nov 2005 06:26:01 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcXluw81tQvwEYDvTomSyD9JFem6wAAA9o1Q
  • Thread-topic: [Xen-ia64-devel] xen on hp rx2600

>From: Alex Williamson [mailto:alex.williamson@xxxxxx]
>
>>
>>      - Currently we have logic to enable only one CPU seen by dom0,
as
>> touch_acpi_table() in dom_fw_init. That can promise no spurious IPI
>> issued before dom0 SMP (guest SMP) ready. Normally touch_acpi_table()
>> will scan MADT table and enable only one entry. Could you check any
>> logic here not adapting to your rx2600 box?
>
>   FWIW, I've been playing around on the same kind of box.  On mine,
>with non-smp xen I get to the same point, but the BSP gives up on the
>secondary, reports it stuck and moves on (10 second timeout iirc).  I
>think maybe the management processor is getting in the way for Aron.
>When I enabled SMP in xen, it correctly saw 2 cpus and dom0 reported 1
>cpu available, 2 cpus total.  Maybe the touch_acpi_table() is only
>getting called in the SMP case?  Thanks,
>
>       Alex

touch_acpi_table is called by dom_fw_init which is always called when
construct dom0 unrelated to SMP. Maybe Aron can add some debug
information to see whether it's called and whether ACPI content gets
changed after that point.

Thanks,
Kevin

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.