From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Shobha Ranganathan <rvshobha-/E1597aS9LQAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: VT-x and Performance counter interrupt in KVM mode
Date: Wed, 21 Mar 2007 09:23:29 +0200 [thread overview]
Message-ID: <4600DD71.5060002@qumranet.com> (raw)
In-Reply-To: <826581.57009.qm-jpo5DsbaTqqB9c0Qi4KiSl5cfvJIxWXgQQ4Iyu8u01E@public.gmane.org>
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 interrupt is programmed in the APIC LVT entry
> (set to 0xee)by the guest OS.
On stock kvm, the guest os programs a virtual apic that lives in qemu,
not the real apic, so it would never cause any interrupt. Are you
running with a modified kvm that allows the guest to touch the real apic?
> Similarly, an IDT entry
> connects the interrupt vector to the interrupt
> handler.
> I am not able to catch, in kvm, the PMU interrupt
> happening in VMX non-root mode. It does not seem to
> appear in the VM-exit interruption information nor in
> the IDT-vectoring information. It does not seem to
> be caught by any of the exit handlers yet the host PMU
> interrupt handler catches it which is not what we
> want.
>
> Any idea on what is going on with this interrupt?
>
It looks completely normal, assuming the host also programmed the timer
to the same vector. Look in qemu/hw/apic.c to find your missing interrupt.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2007-03-21 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 4:58 VT-x and Performance counter interrupt in KVM mode Shobha Ranganathan
[not found] ` <826581.57009.qm-jpo5DsbaTqqB9c0Qi4KiSl5cfvJIxWXgQQ4Iyu8u01E@public.gmane.org>
2007-03-21 7:23 ` Avi Kivity [this message]
2007-03-21 7:25 ` Dor Laor
-- strict thread matches above, loose matches on Subject: below --
2007-03-27 16:35 Stephane Eranian
[not found] ` <20070327163515.GE11818-HU54gidqsKnWxDs0y9d3MAC/G2K4zDHf@public.gmane.org>
2007-03-27 17:10 ` Avi Kivity
[not found] ` <46095022.2030209-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-03-28 15:41 ` Stephane Eranian
[not found] ` <20070328154155.GB12647-HU54gidqsKnWxDs0y9d3MAC/G2K4zDHf@public.gmane.org>
2007-03-28 16:03 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4600DD71.5060002@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=rvshobha-/E1597aS9LQAvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox