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

[Xen-ia64-devel] RE: [PATCH] use shared version of iva/dcr


  • To: "Matt Chapman" <matthewc@xxxxxxxxxxxxxxx>
  • From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
  • Date: Mon, 22 Aug 2005 09:56:57 -0700
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 22 Aug 2005 16:55:34 +0000
  • List-id: DIscussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: AcWjofPRe5PESdR2RzqMF4fPcZHPwwDl9ufw
  • Thread-topic: [PATCH] use shared version of iva/dcr

For dcr, this may not matter, but for iva, there
are some semantics that need to be checked every
virtual interrupt delivery.  At a minimum, if virtual
iva is not private, bits 0-14 should be zeroed
before every use by Xen, correct?

> -----Original Message-----
> From: Matt Chapman [mailto:matthewc@xxxxxxxxxxxxxxx] 
> Sent: Wednesday, August 17, 2005 9:07 PM
> To: Magenheimer, Dan (HP Labs Fort Collins)
> Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [PATCH] use shared version of iva/dcr
> 
> This patch makes Xen use the iva and dcr located in mapped_regs_t and
> eliminates the private versions in arch_domain.  There seems to be no
> reason to involve the hypervisor when accessing these registers, at
> worst the guest kernel can shoot itself in the foot.
> 
> Matt
> 
> Signed-off-by: Matthew Chapman <matthewc@xxxxxx>
> 

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