Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1758349AbcLBM6X convert rfc822-to-8bit (ORCPT <rfc822;w@1wt.eu>);
        Fri, 2 Dec 2016 07:58:23 -0500
Received: from mga04.intel.com ([192.55.52.120]:26598 "EHLO mga04.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1751201AbcLBM6W (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Fri, 2 Dec 2016 07:58:22 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.33,729,1477983600"; 
   d="scan'208";a="12646162"
From: "Odzioba, Lukasz" <lukasz.odzioba@intel.com>
To: "Liang, Kan" <kan.liang@intel.com>,
        Peter Zijlstra <peterz@infradead.org>
CC: Stephane Eranian <eranian@google.com>,
        "mingo@redhat.com" <mingo@redhat.com>,
        LKML <linux-kernel@vger.kernel.org>,
        Alexander Shishkin <alexander.shishkin@linux.intel.com>,
        "ak@linux.intel.com" <ak@linux.intel.com>
Subject: RE: [PATCH] perf/x86: fix event counter update issue
Thread-Topic: [PATCH] perf/x86: fix event counter update issue
Thread-Index: AQHSSa1z5JhtztyVjkewN4oL0nBfbaDvsacAgACEqgCAAAMBgIAAGvaAgAAG4ICAABErAIAENv3w
Date: Fri, 2 Dec 2016 12:58:17 +0000
Message-ID: <D6EDEBF1F91015459DB866AC4EE162CC024DCFE5@IRSMSX103.ger.corp.intel.com>
References: <1480361206-1702-1-git-send-email-kan.liang@intel.com>
 <20161129092520.GB3092@twins.programming.kicks-ass.net>
 <CABPqkBQPRBZZB8wbhYGLoS9ww_0vQrt=nkqgDC_fFgG99cqdCg@mail.gmail.com>
 <20161129173055.GP3092@twins.programming.kicks-ass.net>
 <37D7C6CF3E00A74B8858931C1DB2F07750CA4225@SHSMSX103.ccr.corp.intel.com>
 <20161129193201.GE3045@worktop.programming.kicks-ass.net>
 <37D7C6CF3E00A74B8858931C1DB2F07750CA42A3@SHSMSX103.ccr.corp.intel.com>
In-Reply-To: <37D7C6CF3E00A74B8858931C1DB2F07750CA42A3@SHSMSX103.ccr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiODAzMzk1NjItZDA0Yi00ODNmLWE2MTEtYzI2ZTA3YzgwMTI4IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IloyM0FOcHd6RVwvQ1pscU85Um5FNm4zU0o4cDZEOTZmeWg4RFdhOWRvcU44PSJ9
x-ctpclassification: CTP_IC
x-originating-ip: [163.33.239.182]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 181
Lines: 8

On Tuesday, November 29, 2016 9:33 PM, Liang, Kan wrote:
> Yes, the patch as below fixes the issue on my SLM.

It works for me as well. 
Can we still have it in 4.9?

Thanks,
Lukas