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

[Xen-ia64-devel] [PATCH] Fix domainU boot when VTi domain exists


  • To: <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Zhang, Xiantao" <xiantao.zhang@xxxxxxxxx>
  • Date: Tue, 28 Mar 2006 12:49:27 +0800
  • Delivery-date: Tue, 28 Mar 2006 04:55:29 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcZSIv4Bo5NQq7onSQevZLXg8y9u3Q==
  • Thread-topic: [PATCH] Fix domainU boot when VTi domain exists

        This patch intends to fix domainU boot after VTi domain booted
up.
Currently domainU can't boot after domain VTi booted up. The root cause
is 
when VTi domain exists, after DomU createing and being scheduled for
first time,
context_switch won't be executed completely but through another
execution path
to leave kernel. So iva and pta can't be switched to domU in this case.
This will
lead to LP's(run domU) iva and pta point to VTi domain's ivt and pta. So
when DomainU boots, domain VTi and domainU will hang on one LP.

Singed-off-by: Zhang Xiantao <xiantao.zhang@xxxxxxxxx>
Singed-off-by: Kevin Tian   <kevin.tian@xxxxxxxxx>

Thanks
-Xiantao

Attachment: fix_domU_boot_after_vti.patch
Description: fix_domU_boot_after_vti.patch

_______________________________________________
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®.