Re: [kvm-devel] [PATCH 0/7] Rework irq injection infrastructure

2007-12-06 Thread Avi Kivity
Dong, Eddie wrote: >> What I mean is we pre-load 2 pages where the stack are in, the >> logic may >> be: >> >> If (real mode) >> get 2 pages. >> enter critical path >> >> VM Resume. >> put these 2 pages. >> handle VM Exit normally. >> >> >> > With 2nd thinking, We can cache these 2

Re: [kvm-devel] [PATCH 0/7] Rework irq injection infrastructure

2007-12-06 Thread Dong, Eddie
> >What I mean is we pre-load 2 pages where the stack are in, the >logic may >be: > >If (real mode) > get 2 pages. >enter critical path > >VM Resume. >put these 2 pages. >handle VM Exit normally. > > With 2nd thinking, We can cache these 2 pages. Something like: if (real mode) ca

Re: [kvm-devel] [PATCH 0/7] Rework irq injection infrastructure

2007-12-06 Thread Dong, Eddie
>> >> One of the optimization, which can be used in pure SW is that >> we can shadow APIC state as "RO" to guest so that all guest >> read to APIC registers can run in full speed. T >> >> > >This can still be done with unacked interrupts: modify the >state to "as >if" the interrupt was i

Re: [kvm-devel] [PATCH 0/7] Rework irq injection infrastructure

2007-12-06 Thread Avi Kivity
Dong, Eddie wrote: >>> Mmm, how can you know if it is injected successfully? >>> From the patch, it looks like you know this by checking >>> IDT_Vectoring in next VM Exit. That means the virtual >>> interrupt controller state in memory is incorrect temply. >>> >>> If the injection success & we can

Re: [kvm-devel] [PATCH 0/7] Rework irq injection infrastructure

2007-12-06 Thread Dong, Eddie
>> >> Mmm, how can you know if it is injected successfully? >> From the patch, it looks like you know this by checking >> IDT_Vectoring in next VM Exit. That means the virtual >> interrupt controller state in memory is incorrect temply. >> >> If the injection success & we can get VM Exit before >

Re: [kvm-devel] [PATCH 0/7] Rework irq injection infrastructure

2007-12-06 Thread Avi Kivity
Dong, Eddie wrote: > It is not a small change, I still need to study the whole patch :( > If I can get some question clarified earlier, that helps a lot. > > > >> -Original Message- >> From: [EMAIL PROTECTED] >> [mailto:[EMAIL PROTECTED] On Behalf Of >> Avi Kivity >> Sent: 2007年12月4日 1

Re: [kvm-devel] [PATCH 0/7] Rework irq injection infrastructure

2007-12-05 Thread Dong, Eddie
It is not a small change, I still need to study the whole patch :( If I can get some question clarified earlier, that helps a lot. >-Original Message- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of >Avi Kivity >Sent: 2007年12月4日 17:44 >To: kvm-devel@lists.sourceforge.ne

Re: [kvm-devel] [PATCH 0/7] Rework irq injection infrastructure

2007-12-04 Thread Avi Kivity
Joerg Roedel wrote: > On Tue, Dec 04, 2007 at 11:44:07AM +0200, Avi Kivity wrote: > >> The patchset is also necessary for integrating the tpr optimization branch >> and for injecting interrupts in big real mode. >> > > Interesting work. Do you have an updated tpr optimization patch which >

Re: [kvm-devel] [PATCH 0/7] Rework irq injection infrastructure

2007-12-04 Thread Joerg Roedel
On Tue, Dec 04, 2007 at 11:44:07AM +0200, Avi Kivity wrote: > The patchset is also necessary for integrating the tpr optimization branch > and for injecting interrupts in big real mode. Interesting work. Do you have an updated tpr optimization patch which applys on top of these patches? Joerg --