Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp6440277imu; Wed, 30 Jan 2019 14:58:59 -0800 (PST) X-Google-Smtp-Source: ALg8bN6XdC93V2nwHW9yh0noZeM6tevxgpNaZaS51kJaakKzTWZR4TrKlgya7+JRpc37YR6DXFWa X-Received: by 2002:a17:902:6a8c:: with SMTP id n12mr32507506plk.85.1548889139595; Wed, 30 Jan 2019 14:58:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548889139; cv=none; d=google.com; s=arc-20160816; b=Xow8z2H920/ABfD8E4bHcBUMRCOtheJWxkghBjIVBQPT4WiBme95BsuFmGjPkGUjj6 3og4jN69bFx87D32+sVs8evQpNzrRQZh/FnPg0h2T1QPnpov8qj2dR0KHrnCtlk1jA6A 5+1vRYWbLjbf/GGiJF9qM1OQEdOfklIOv8wiGTaxtVsMT+2y621L+XumL66h2RDgjiyr CUHMipgKOmF/O2Pemzqg4dZdkxARlQ/7QCH2uJq3oTCLdlg4LFT0vWTl8rUWVTEBPZyq aikd2DurVOgdAdnAYUCAfmOp+4+f+rSVzqnrRRtwxR9nrybymEig6O3eYrqmyBd5nGT1 ADzQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:message-id :in-reply-to:date:references:subject:cc:to:from; bh=Jtnfj4duheYmWEihvmLEFIMEUn/inZj2go3Z2WW9WqA=; b=hTiZnBhEarut9Lw0P6RhPNX9zUydfiVni97mzBzUUp3s/KJmVE4MpNYTZb87bMvWlW KWq19/uKTtM7ck8CnfVvRuNxibDyS+ybApCrxkbZ3dzQnDCgXq+PNppm+WUPYIe8pAGP pnCvfBu40r/Kl6AhWTMMIvyJ9lBwPtQ5FYmX1Rsd2cyHzKTgWmrhNeCb0bohWnGaqv0Y RBqcQMam7oYdCDb4LWIq2DsaHqWPI7P15emrw7eLOVUzu3xv8DZfTrr3q9U44sYSbcjf jlyfr9gYv+J4dDu1L+lDM64elYI14AMwgMx9yGdSdv3nZ6ITjW9g13pOrBaRh7JI1y4E 0pEA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e4si2815209plk.260.2019.01.30.14.58.43; Wed, 30 Jan 2019 14:58:59 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731730AbfA3Ujs (ORCPT + 99 others); Wed, 30 Jan 2019 15:39:48 -0500 Received: from mga11.intel.com ([192.55.52.93]:58419 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726783AbfA3Ujr (ORCPT ); Wed, 30 Jan 2019 15:39:47 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Jan 2019 12:39:47 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,542,1539673200"; d="scan'208";a="118762043" Received: from tassilo.jf.intel.com (HELO tassilo.localdomain) ([10.7.201.137]) by fmsmga007.fm.intel.com with ESMTP; 30 Jan 2019 12:39:47 -0800 Received: by tassilo.localdomain (Postfix, from userid 1000) id 46A7F3011E7; Wed, 30 Jan 2019 12:39:47 -0800 (PST) From: Andi Kleen To: Jiri Olsa Cc: Ravi Bangoria , lkml , Peter Zijlstra , linux-perf-users@vger.kernel.org, Arnaldo Carvalho de Melo , eranian@google.com, vincent.weaver@maine.edu, "Naveen N. Rao" Subject: Re: System crash with perf_fuzzer (kernel: 5.0.0-rc3) References: <7c7ec3d9-9af6-8a1d-515d-64dcf8e89b78@linux.ibm.com> <20190130183648.GA24233@krava> Date: Wed, 30 Jan 2019 12:39:47 -0800 In-Reply-To: <20190130183648.GA24233@krava> (Jiri Olsa's message of "Wed, 30 Jan 2019 19:36:48 +0100") Message-ID: <87zhrhzxpo.fsf@linux.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Jiri Olsa writes: > > the patch adds check_eriod pmu callback.. I need to check if there's > better way to do this, but so far it fixes the crash for me > > if you guys could check this patch, that'd be great There's already a limit_period callback, perhaps that could be extended. But ok, can do it this way too. I suspect there are some other cases that need this callback, not just BTS, e.g. the checks in hsw_hw_config -Andi