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

[Xen-devel] Xen and AMD: VMExit on int 0x80 and 64bit case.

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Necrosoft <necrosoft82@xxxxxxxxx>
  • Date: Mon, 23 Jun 2008 10:29:52 +0200
  • Delivery-date: Mon, 23 Jun 2008 01:30:14 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=qRcPzGKQ4y9wtYGgYrJyMnpVz64G+A3k1Y+l33sPja/3PdVSDnURdczSPICDwZ5Jnz 00bEIG5DCbkG9Lag6OdFLvcj3gz3UI/rBWhDg9SPMzJyZalIns4sli3zFg6AV0r/+DH3 ejGM+VdUlqunqbvFrgFNQlVEn40OwLinKAJoU=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


I'm looking through xen-devel archive and I found an old mail (2007) wich speaks about "VMExit forcing" in AMD/HVM architecture for some "events". M. Williamson said: "It it possible to arrange for a VMEXIT to occur on int 0x80". I would ask you if you know an example or others informations witch may clarify this kind of trick.

I think that this is not required for 64bit-Xen and 32bit/64bit PV-Guest because Xen must intercept all int 0x80 directly, right? In this cases I can hook this event only through ENTRY(int80_direct_trap)
(x86_64/entry.S) procedure or there is another "high level procedure"?

Thanks you very much!


Xen-devel mailing list



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