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

RE: [Xen-ia64-devel] [PATCH] fully virtualize psr and ipsr on non-VTIdomain


  • To: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Wed, 30 Nov 2005 05:50:06 -0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 30 Nov 2005 13:49:53 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcXzytgKo6So03GTShmzfLz5ceuCSgBxm7VwAAi6/CA=
  • Thread-topic: [Xen-ia64-devel] [PATCH] fully virtualize psr and ipsr on non-VTIdomain

I'm still catching up after being gone for a few days and
spent most of yesterday recovering from a trashed disk
on my test machine.  My first priority is to find out
what broke Xen/ia64 in xen-unstable so we have a solid
foundation, then I will catch up on the patch backlog. 

In the meantime, please look at what your patch broke in
FAST_RFI, FAST_BREAK, and FAST_ACCESS_REFLECT, as I won't
be checking in patches with significant performance
regressions.

Thanks,
Dan

> -----Original Message-----
> From: Xu, Anthony [mailto:anthony.xu@xxxxxxxxx] 
> Sent: Wednesday, November 30, 2005 2:36 AM
> To: Xu, Anthony; Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-ia64-devel] [PATCH] fully virtualize psr 
> and ipsr on non-VTIdomain
> 
> Dan,
> 
> What's your opinion about this patch?
> 
> Thanks
> -Anthony
> 
> >-----Original Message-----
> >From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
> >[mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On 
> Behalf Of Xu, Anthony
> >Sent: 2005å11æ28æ 11:22
> >To: Magenheimer, Dan (HP Labs Fort Collins)
> >Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> >Subject: [Xen-ia64-devel] [PATCH] fully virtualize psr and ipsr on
> >non-VTIdomain
> >
> >Dan,
> >This patch is intended to fully virtualize psr and ipsr on non-VTI
> >domain.
> >Following things are done in this patch.
> >1, previously when guest reads psr, it always get psr dt rt 
> it equal to
> >1. that is because HV doesn't restore these information,
> >metaphysical_mode can't present all these information. I save these
> >information into privregs->vpsr. Thus guest can get correct 
> information
> >about dt, rt and it.
> >2, when guest reads psr, we should only return low 32bits 
> and 35 and 36
> >bits, previously return all bits.
> >3, when guest rsm and ssm psr, HV rsm and ssm some bits of 
> current psr
> >which is used by HV, that is not correct, guest rsm and ssm 
> should only
> >impact guest psr(that is regs->ipsr).
> >4, mistakenly uses guest DCR, guest DCR should impact guest psr when
> >injecting interruption into guest, but not impact guest ipsr.
> >When injecting interruption into guest,The current implementation is
> >     Guest ipsr.be=guest dcr.be
> >     Guest ipsr.pp=guest dcr.pp
> >Correct implementation should be,
> >     Guest psr.be=guest dcr.be
> >     Guest psr.pp=guest dcr.pp.
> >
> >Because of above modifications, I turn off FAST_RFI, FAST_BREAK and
> >FAST_ACCESS_REFLECT.
> >
> >Signed-off-by Anthony Xu < anthony.xu@xxxxxxxxx>
> >
> >One question, why do we need to virtualize guest psr.pp and 
> always set
> >guest psr.pp to 1?
> >
> >Thanks
> >-Anthony
> >
> >
> >
> >
> >
> >
> >
> 
> 
_______________________________________________
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®.