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

RE: [Xen-ia64-devel] pv_ops: entry.S simplification


  • To: "Isaku Yamahata" <yamahata@xxxxxxxxxxxxx>
  • From: "Dong, Eddie" <eddie.dong@xxxxxxxxx>
  • Date: Thu, 27 Mar 2008 17:04:21 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 27 Mar 2008 02:04:53 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AciP1eYTm52nQAqZRaqKANF3RcvskwAEzCZA
  • Thread-topic: [Xen-ia64-devel] pv_ops: entry.S simplification

Isaku Yamahata wrote:
> Hi Eddie.
> 
> I looked into entry.S closely.
> Unfortunately I found that ia64_leave_syscall() and
> ia64_leave_kernel() includes invirtualizable instructions,
> cover instruction with psr.ic = 0 so that those paravirtualization
> is inevitable. (ia64_switch_to() doesn't need paravirtualization
> though.) 

Yes there 2 kind of instructions we must modify, one is cover when
psr.ic=0, another one is RFI which can;t be handled by Xen today.

But I temply put running on xen for now, I am working on using 
indirect function call pv_ops now.

Or do you mean there are still missed "cover" instruction?

> 
> Does it really work? Probably "just seeing login prompt test" doesn't
> reveal the issues.
> 
> thanks,
> 

I can login and do minimal ops, I didn't take stress test.
But in my coding time, if a cover with PSR.ic=0 is missed,
or RFI is missed, guest will soon die.

Thanks, eddie

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