From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752163AbaE1UGD (ORCPT ); Wed, 28 May 2014 16:06:03 -0400 Received: from mga09.intel.com ([134.134.136.24]:58938 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751308AbaE1UGC (ORCPT ); Wed, 28 May 2014 16:06:02 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.98,929,1392192000"; d="scan'208";a="547978385" Date: Wed, 28 May 2014 13:06:00 -0700 From: Andi Kleen To: Stephane Eranian Cc: LKML , Peter Zijlstra , "mingo@elte.hu" , Dave Hansen , "Yan, Zheng" Subject: Re: [RFC] perf/x86: PMU IRQ handler issues Message-ID: <20140528200600.GR29957@tassilo.jf.intel.com> References: <20140528195528.GQ29957@tassilo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 28, 2014 at 09:56:35PM +0200, Stephane Eranian wrote: > On Wed, May 28, 2014 at 9:55 PM, Andi Kleen wrote: > > > >> Another explanation is that because we ACK the NMI early, we leave the > >> door open to other interrupts, incl. NIC, and we are interrupting the execution > > > > PMI executes with interrupts off. > > > And that's coming from where? The interrupt gate. -Andi