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

[Xen-devel] idtr

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Travis Johnson" <travis.jo@xxxxxxxxx>
  • Date: Tue, 19 Dec 2006 09:37:10 -0500
  • Delivery-date: Tue, 19 Dec 2006 06:36:57 -0800
  • 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; b=gMa1Aw2S8N7CNN8Ckd8b/UvUin65mIyHszhiLcmTOEZSuNimbVQhF4TK4A5GvL+gv9W5CopEfaLnnkszhngToSe2a3wir+QaIFLsPT55Mjql034s+qlFeHniGonqhrz2rF+KPiu8YYtJmK3Gielf9ohoPt/CxyhC9s+EoclD6lc=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

When a guest domain does a "lidt" (the x86 instruction) to update the pointer to the IDT where does this information get stored inside Xen (assuming it does). I know Xen can interject interrupts into a domain and that the "guest_vcpu_context" struct contains an array that represents the virtual IDT but how does the virtual IDT relate to the actual IDT the guest OS uses and is pointed to by it's idtr. It seems logical to me that the idtr must be stored inside the vcpu at some point somewhere since I can run a "sidt" and get what seems like a reasonable address (from the guest's point of view). I've also used "lidt"'s without crashing the system so Xen handles the update correctly.

I'm using HVM(VMX) guests on 64bit Xen (3.0.3 - the stable tarball from xensource). The guests run FC6.

Thanks. This list is always a good read.
Xen-devel mailing list



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