Stephane Eranian wrote:
> Avi,
>
> On Fri, Jul 13, 2007 at 09:53:36AM +0300, Avi Kivity wrote:
>
>> Stephane Eranian wrote:
>>
>>> Avi,
>>>
>>> A couple of months back, we had a discussion about PMU virtualization
>>> and the difficulty I encountered trying to catch the PMU interrupt
>>> ve
Avi,
On Fri, Jul 13, 2007 at 09:53:36AM +0300, Avi Kivity wrote:
> Stephane Eranian wrote:
> > Avi,
> >
> > A couple of months back, we had a discussion about PMU virtualization
> > and the difficulty I encountered trying to catch the PMU interrupt
> > vector in kvm on VM-exit. KVM does not set ac
Stephane Eranian wrote:
> Avi,
>
> A couple of months back, we had a discussion about PMU virtualization
> and the difficulty I encountered trying to catch the PMU interrupt
> vector in kvm on VM-exit. KVM does not set ack_intr_on_intr. Would
> you mind reminding me of the reason for this?
>
>
Stephane Eranian wrote:
> Eddie,
>
> On Fri, Jul 13, 2007 at 08:46:06AM +0800, Dong, Eddie wrote:
>> [EMAIL PROTECTED] wrote:
>>> Avi,
>>>
>>> A couple of months back, we had a discussion about PMU
>>> virtualization and the difficulty I encountered trying to catch the
>>> PMU interrupt vector in
Eddie,
On Fri, Jul 13, 2007 at 08:46:06AM +0800, Dong, Eddie wrote:
> [EMAIL PROTECTED] wrote:
> > Avi,
> >
> > A couple of months back, we had a discussion about PMU virtualization
> > and the difficulty I encountered trying to catch the PMU interrupt
> > vector in kvm on VM-exit. KVM does not s
[EMAIL PROTECTED] wrote:
> Avi,
>
> A couple of months back, we had a discussion about PMU virtualization
> and the difficulty I encountered trying to catch the PMU interrupt
> vector in kvm on VM-exit. KVM does not set ack_intr_on_intr. Would
> you mind reminding me of the reason for this?
>
> O
