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
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
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?
On the topic of scheduler hooks for use by
Avi,
On Fri, Jun 15, 2007 at 01:49:06PM +0300, Avi Kivity wrote:
> Magicboiz wrote:
> > a little bit better. It Opps'ed again, but this time, my laptop is still
> > usable:
> >
> > sudo /usr/local/kvm/bin/qemu -hda /tmp/disco-qemu -m 128 -boot d
> > -cdrom /tmp/debian-40r0-i386-businesscard.iso -
Avi,
On Thu, May 31, 2007 at 02:52:05PM +0300, Avi Kivity wrote:
> Stephane Eranian wrote:
> >>
> >>If the guest cpuid is set to a least common denominator, it should work.
> >>
> >>
> >There is no common denominator between a P4 and Intel Core
Avi,
On Thu, May 31, 2007 at 02:35:44PM +0300, Avi Kivity wrote:
> >>
> >>
> >In the case of heterogeneous migration, clearly performance counters
> >will not work well, especially for unmodified guests.
>
> Right.
>
> >But I can also
> >see problems when migrating from Intel Core to older
Avi,
On Thu, May 31, 2007 at 11:39:04AM +0300, Avi Kivity wrote:
> Stephane Eranian wrote:
> >Hello,
> >
> >Looking at kvm-26, it seems that the CPUID values as seen by the guest OS
> >are still hardcoded for i386/x86-64 at least.
> >
> >For performance cou
Hello,
Looking at kvm-26, it seems that the CPUID values as seen by the guest OS
are still hardcoded for i386/x86-64 at least.
For performance counter virtualization, the guest needs to see the *actual*
family/model information in order to correctly program the counters.
It would be fairly simpl
Casey,
On Tue, Apr 03, 2007 at 10:46:38PM -0400, Casey Jeffery wrote:
> Stephane,
>
> I'm glad you found this; I thought I was going to have to repost while
> actually remembering to change the subject line.
>
Someone else pointed me to your message. The title was indeed misleading.
> >On Wed,
Casey,
On Wed, Mar 28, 2007 at 01:02:47PM -0400, Casey Jeffery wrote:
> I was messing around with using the perf counters a couple weeks ago
> as a way to get deterministic exits in the instruction stream of the
> guest. I used the h/w msr save/restore area to disable the counters
> and save the v
Avi,
On Tue, Mar 27, 2007 at 07:10:58PM +0200, Avi Kivity wrote:
> >>
> >
> >The Performance counters (PMU) cannot be fully virtualized, they need to
> >run on the actual MSR registers. The PMU interrupt is controlled by the
> >local APIC. To get overflow-based sampling to work in a guest, we
Hi Avi,
>
> Shobha Ranganathan wrote:
> > I am trying to capture in vmx.c the hardware
> > performance counter(PMU) interrupt of a i386 Linux
> > kernel running with perfmon on a Core 2 Duo machine
> > running with kvm-15. host is running kvm with VT-x in
> > x86-64 mode.
> >
> > The PMU interrup
12 matches
Mail list logo
