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

[Xen-devel] HVM initiative

  • To: Xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: John Que <qwejohn@xxxxxxxxx>
  • Date: Fri, 13 Jan 2006 15:26:43 +0200
  • Delivery-date: Fri, 13 Jan 2006 13:33:26 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=iG8/iU1WmpxH2lHSlaHYzt+LJBWlwVDLDPqYz0gMSXYt7CazoQJ6p+TsLNdlVAviQy+f4quaRGzNGqknjruk4A6WKiNaI1BWs/uBHUzQK6uxelysP8lP/JQK3fvdb9lHbsSdca348yA7KK96IMbzuMyebvP+WAT9tgP6YUjbo+s=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hello all,
I had noticed that there is a mrecurial repository for a unified interface
for Vt-x and AMD svm in:

 HVM stands for "Hardware virtual machine", and it is an
 interface that abstracts away from the x86/x86_64 CPU specifics.

 Is there intention that this will be integrated to the main
 tree ? there are some differences between svm and vt-x ; some are
 in terminology, but some are real ones (like the fact the svm has
 tagged TLB and uses ASID while vt-x does not).

 Does anybody knows more on this HVM initiative and shed some light on it?
** John **

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.