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

Re: [Xen-devel] exception handler caused by context switching and setting trap flag

  • To: lijiandm <lijiandm@xxxxxxx>
  • From: "Paul Samon" <paul.samon@xxxxxxxxx>
  • Date: Wed, 29 Oct 2008 09:49:17 +0800
  • Cc: xen组 <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Tue, 28 Oct 2008 18:49:39 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=MjoNwLlTjQZbrf3SUywH80i4jI4iykpzVY9r+ZdE3i70cMVta5RkgUcKNxqjZaEHMt uGp3H3bl8qDhI9YMGjnXPMZBBM5SA/F2GI6czpWm5UdoTS4SYUrl/wACwyGDAJ+R75+0 32n7g7uZaU6GhdKNLnET626BpNBths0QJSrAA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

HVM guest's VMexit is handled by Xen itself (see xen/arch/x86/hvm/vmx/entry.S: vmx_asm_vmexit_handler if you're using an Intel VT-capable host) , not Dom0 (a PV guest) at all.
vcpu context switch itself doesn't cause VMexit.
-- Paul S.

On Wed, Oct 29, 2008 at 9:32 AM, lijiandm <lijiandm@xxxxxxx> wrote:
      I have two trivial question.
      In dom0,which exception handler is used to handle VMexit caused by context switching in domU?
      If I want to replace the handler ,what should I do?

Xen-devel mailing list



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