On Fri, May 15, 2009 at 03:57:44PM +0800, Dong, Eddie wrote:
And what if INTA already happened and CPU is ready to fetch IDT for
interrupt vector and at this very moment CPU faults?
If INTA happens, that means it is delivered. If its delivery triggers another
exception, that is what
Gleb Natapov wrote:
On Thu, May 14, 2009 at 10:34:11PM +0800, Dong, Eddie wrote:
Gleb Natapov wrote:
On Thu, May 14, 2009 at 09:43:33PM +0800, Dong, Eddie wrote:
Avi Kivity wrote:
Dong, Eddie wrote:
OK.
Also back to Gleb's question, the reason I want to do that is to
simplify event
Dong, Eddie wrote:
OK.
Also back to Gleb's question, the reason I want to do that is to simplify event
generation mechanism in current KVM.
Today KVM use additional layer of exception/nmi/interrupt such as
vcpu.arch.exception.pending, vcpu-arch.interrupt.pending
vcpu-arch.nmi_injected.
All
Avi Kivity wrote:
Dong, Eddie wrote:
OK.
Also back to Gleb's question, the reason I want to do that is to
simplify event
generation mechanism in current KVM.
Today KVM use additional layer of exception/nmi/interrupt such as
vcpu.arch.exception.pending, vcpu-arch.interrupt.pending
On Thu, May 14, 2009 at 09:43:33PM +0800, Dong, Eddie wrote:
Avi Kivity wrote:
Dong, Eddie wrote:
OK.
Also back to Gleb's question, the reason I want to do that is to
simplify event
generation mechanism in current KVM.
Today KVM use additional layer of exception/nmi/interrupt such
Gleb Natapov wrote:
On Thu, May 14, 2009 at 09:43:33PM +0800, Dong, Eddie wrote:
Avi Kivity wrote:
Dong, Eddie wrote:
OK.
Also back to Gleb's question, the reason I want to do that is to
simplify event generation mechanism in current KVM.
Today KVM use additional layer of
On Thu, May 14, 2009 at 10:34:11PM +0800, Dong, Eddie wrote:
Gleb Natapov wrote:
On Thu, May 14, 2009 at 09:43:33PM +0800, Dong, Eddie wrote:
Avi Kivity wrote:
Dong, Eddie wrote:
OK.
Also back to Gleb's question, the reason I want to do that is to
simplify event generation mechanism
Dong, Eddie wrote:
I noticed the MACRO for SVM vmcb-control.event_inj and VMX VM_EXIT_INTR_INFO
are almost same, I have a need to query the event injection situation in common
code so plan to expose this register read/write to x86.c. Should we define a new
format for evtinj/VM_EXIT_INTR_INFO
Avi Kivity wrote:
Dong, Eddie wrote:
I noticed the MACRO for SVM vmcb-control.event_inj and VMX
VM_EXIT_INTR_INFO are almost same, I have a need to query the event
injection situation in common code so plan to expose this register
read/write to x86.c. Should we define a new format for
On Tue, May 12, 2009 at 03:38:59PM +0800, Dong, Eddie wrote:
I noticed the MACRO for SVM vmcb-control.event_inj and VMX VM_EXIT_INTR_INFO
are almost same, I have a need to query the event injection situation in
common code so plan to expose this register read/write to x86.c. Should we
10 matches
Mail list logo
