All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Don Zickus <dzickus@redhat.com>,
	Robert Richter <robert.richter@amd.com>,
	"x86@kernel.org" <x86@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"ying.huang@intel.com" <ying.huang@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"paulmck@linux.vnet.ibm.com" <paulmck@linux.vnet.ibm.com>,
	"jeremy@goop.org" <jeremy@goop.org>
Subject: Re: [V6][PATCH 4/6] x86, nmi:  add in logic to handle multiple events and unknown NMIs
Date: Sun, 02 Oct 2011 16:04:39 +0200	[thread overview]
Message-ID: <4E886F77.9000909@redhat.com> (raw)
In-Reply-To: <20111002134802.GH7761@one.firstfloor.org>

On 10/02/2011 03:48 PM, Andi Kleen wrote:
> >  Second, I wanted to use NMIs as a way of waking up a vcpu sleeping with
> >  interrupts disabled (in the context of Jeremy's paravirt spinlock
> >  patches).  Looks like we'll have to use paravirtualization for that.
>
> Just use a mode of perf that doesn't use NMIs.
> Interrupt off profiling is rarely needed if at all on modern kernels.

I tend to agree.   But that's not my call.

(note 'perf kvm' will need adjustment if we make that change - likely 
need to capture the interrupt during vmexit and dispatch it manually; 
not sure if it's workable for svm at all)

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2011-10-02 14:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-23 19:17 [V6][PATCH 0/6] x86, nmi: new NMI handling routines Don Zickus
2011-09-23 19:17 ` [V6][PATCH 1/6] x86, nmi: split out nmi from traps.c Don Zickus
2011-09-23 19:17 ` [V6][PATCH 2/6] x86, nmi: create new NMI handler routines Don Zickus
2011-09-23 19:17 ` [V6][PATCH 3/6] x86, nmi: wire up NMI handlers to new routines Don Zickus
2011-09-30 14:25   ` Robert Richter
2011-09-23 19:17 ` [V6][PATCH 4/6] x86, nmi: add in logic to handle multiple events and unknown NMIs Don Zickus
2011-09-26  8:59   ` Peter Zijlstra
2011-09-26 12:55     ` Don Zickus
2011-09-28 10:31   ` Robert Richter
2011-09-28 12:37     ` Don Zickus
2011-09-28 16:51       ` Jeremy Fitzhardinge
2011-09-28 17:44         ` Don Zickus
2011-09-28 17:52           ` Jeremy Fitzhardinge
2011-10-02 10:07       ` Avi Kivity
2011-10-02 13:48         ` Andi Kleen
2011-10-02 14:04           ` Avi Kivity [this message]
2011-10-03 13:13         ` Don Zickus
2011-09-23 19:17 ` [V6][PATCH 5/6] x86, nmi: track NMI usage stats Don Zickus
2011-09-23 19:17 ` [V6][PATCH 6/6] x86, nmi: print out NMI stats in /proc/interrupts Don Zickus

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=4E886F77.9000909@redhat.com \
    --to=avi@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=dzickus@redhat.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=robert.richter@amd.com \
    --cc=x86@kernel.org \
    --cc=ying.huang@intel.com \
    /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.