From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758286AbbKSLOv (ORCPT ); Thu, 19 Nov 2015 06:14:51 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:50774 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758232AbbKSLOs (ORCPT ); Thu, 19 Nov 2015 06:14:48 -0500 Date: Thu, 19 Nov 2015 12:14:43 +0100 From: Peter Zijlstra To: "Huang, Ying" Cc: Andi Kleen , lkp@01.org, LKML Subject: Re: [lkp] [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 Message-ID: <20151119111443.GK3816@twins.programming.kicks-ass.net> References: <87fv03u89v.fsf@yhuang-dev.intel.com> <20151118162742.GH3816@twins.programming.kicks-ass.net> <87mvuavn4t.fsf@yhuang-dev.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87mvuavn4t.fsf@yhuang-dev.intel.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 19, 2015 at 08:38:58AM +0800, Huang, Ying wrote: > Hi, Peter, > > Peter Zijlstra writes: > > > On Wed, Nov 18, 2015 at 02:33:00PM +0800, kernel test robot wrote: > >> FYI, we noticed the below changes on > >> > >> https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git perf/core > >> commit 7aba70e47ca4e961acb5af96d5127e3fad651c7c ("x86, perf: Optimize stack walk user accesses") > > > > Of course, that commit no longer exists. I re-create the tree every time > > I push it, this means that if you report something a few days later, its > > highly likely its against non-existant commits :/ > > I am sorry about this. We will try our best to reach real 0day > reporting. Is there any way I can monitor the progress of a given tree through the whole 0-day testing farm? I know the various compile tests are complete because those send email. But after that it goes off into magic land without further feedback, unless something bad happens as per this report. It would be useful for me to know how far along a given tree is before I zap it. From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============2997936835142453689==" MIME-Version: 1.0 From: Peter Zijlstra To: lkp@lists.01.org Subject: Re: [x86, perf] 7aba70e47c: BUG: unable to handle kernel paging request at 696d2f62 Date: Thu, 19 Nov 2015 12:14:43 +0100 Message-ID: <20151119111443.GK3816@twins.programming.kicks-ass.net> In-Reply-To: <87mvuavn4t.fsf@yhuang-dev.intel.com> List-Id: --===============2997936835142453689== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Thu, Nov 19, 2015 at 08:38:58AM +0800, Huang, Ying wrote: > Hi, Peter, > = > Peter Zijlstra writes: > = > > On Wed, Nov 18, 2015 at 02:33:00PM +0800, kernel test robot wrote: > >> FYI, we noticed the below changes on > >> = > >> https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git perf/= core > >> commit 7aba70e47ca4e961acb5af96d5127e3fad651c7c ("x86, perf: Optimize = stack walk user accesses") > > > > Of course, that commit no longer exists. I re-create the tree every time > > I push it, this means that if you report something a few days later, its > > highly likely its against non-existant commits :/ > = > I am sorry about this. We will try our best to reach real 0day > reporting. Is there any way I can monitor the progress of a given tree through the whole 0-day testing farm? I know the various compile tests are complete because those send email. But after that it goes off into magic land without further feedback, unless something bad happens as per this report. It would be useful for me to know how far along a given tree is before I zap it. --===============2997936835142453689==--