From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: nmi is broken?
Date: Tue, 03 May 2011 17:37:17 +0300 [thread overview]
Message-ID: <4DC0131D.5090407@redhat.com> (raw)
In-Reply-To: <4DC0114B.3080907@siemens.com>
On 05/03/2011 05:29 PM, Jan Kiszka wrote:
> On 2011-05-03 15:31, Avi Kivity wrote:
> > On 05/03/2011 01:37 PM, Jan Kiszka wrote:
> >>>
> >>> Yes. Unfortunately that is very vendor and model specific. The
> >>> architectural PMU is supported, but that is only available on Intel.
> >>
> >> Is it supposed to have any practical value already? I did not yet find a
> >> magic -cpu switch to let Linux detect anything, not to speak of perf or
> >> watchdog support.
> >
> > On the guest side it is supported for the watchdog
> > (arch/x86/kernel/cpu/perfctr-watchdog.c, look for
> > X86_FEATURE_ARCH_PERFMON). It's also mentioned in perf_event_intel.c,
> > but I don't know if it will work without the other PMU features being
> > present.
>
> I've tested with some SUSE 2.6.38 guest kernel, and it complained like
> this:
>
> (-cpu kvm64)
> Performance Events: unsupported Netburst CPU model 6 no PMU driver, software events only.
> NMI watchdog disabled (cpu0): hardware events not enabled
>
Sorry, I meant to write, but forgot, that on the host side it is
completely unsupported. It shouldn't be too hard to use perf_events to
emulate the architectural PMU. Once we do that we can expose the
architectural pmu bit and the guest will use it.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-05-03 14:37 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 19:21 nmi is broken? OGAWA Hirofumi
2011-04-23 22:50 ` OGAWA Hirofumi
2011-04-24 6:44 ` Avi Kivity
2011-04-24 9:17 ` OGAWA Hirofumi
2011-04-24 9:46 ` Jan Kiszka
2011-04-24 11:13 ` OGAWA Hirofumi
2011-04-24 11:15 ` OGAWA Hirofumi
2011-04-24 12:24 ` Jan Kiszka
2011-04-27 8:55 ` Avi Kivity
2011-04-27 12:09 ` Jan Kiszka
2011-04-28 1:28 ` OGAWA Hirofumi
2011-04-28 9:59 ` Avi Kivity
2011-04-28 13:44 ` OGAWA Hirofumi
2011-04-28 14:23 ` OGAWA Hirofumi
2011-05-01 1:45 ` OGAWA Hirofumi
2011-05-02 8:46 ` Avi Kivity
2011-05-02 14:30 ` OGAWA Hirofumi
2011-05-03 9:36 ` Avi Kivity
2011-05-03 10:07 ` Avi Kivity
2011-05-03 13:25 ` OGAWA Hirofumi
2011-05-03 13:35 ` Avi Kivity
2011-05-03 16:57 ` OGAWA Hirofumi
2011-05-03 17:09 ` Avi Kivity
2011-05-03 17:45 ` OGAWA Hirofumi
2011-05-04 8:27 ` Avi Kivity
2011-05-04 15:40 ` OGAWA Hirofumi
2011-05-04 16:15 ` Avi Kivity
2011-04-24 14:08 ` Jan Kiszka
2011-05-03 9:43 ` Avi Kivity
2011-05-03 10:37 ` Jan Kiszka
2011-05-03 13:31 ` Avi Kivity
2011-05-03 14:29 ` Jan Kiszka
2011-05-03 14:37 ` Avi Kivity [this message]
2011-05-03 15:01 ` Jan Kiszka
-- strict thread matches above, loose matches on Subject: below --
2001-11-30 9:10 NMI is broken! george anzinger
2001-12-01 7:11 ` george anzinger
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=4DC0131D.5090407@redhat.com \
--to=avi@redhat.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.