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

RE: [Xen-ia64-devel] vcpu_match_tr_entry


  • To: "Tristan Gingold" <Tristan.Gingold@xxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Thu, 30 Mar 2006 16:29:39 +0800
  • Delivery-date: Thu, 30 Mar 2006 08:32:36 +0000
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcZT0wxS1ZGI8dluRGSX2ljQSi2RvgAAC9VA
  • Thread-topic: [Xen-ia64-devel] vcpu_match_tr_entry

>current definition of vcpu_match_tr_entry is:
>#define vcpu_match_tr_entry(_trp,_ifa,_rid)             \
>    ((_trp->p && (_trp->rid==_rid) && (_ifa >= _trp->vadr) &&   \
>    (_ifa < (_trp->vadr + (1L<< _trp->ps)) - 1)))
>                                                          ^^
>Why -1 ?
>I suppose it is either <= (vadr + ps -1) or < (vadr + ps - 1) ?
>
>Thank you for any comment.
Percpu data of guest is put at high address, saying 0xffffffffffff0000,
Thus, vadr+1L<<ps is wrapped to 0, the correct statement maybe,
(_ifa <= (_trp->vadr + (1L<< _trp->ps)) - 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®.