From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751857AbcBOQat (ORCPT <rfc822;w@1wt.eu>);
	Mon, 15 Feb 2016 11:30:49 -0500
Received: from [198.137.202.9] ([198.137.202.9]:50738 "EHLO
	bombadil.infradead.org" rhost-flags-FAIL-FAIL-OK-OK)
	by vger.kernel.org with ESMTP id S1751182AbcBOQar (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Mon, 15 Feb 2016 11:30:47 -0500
Date: Mon, 15 Feb 2016 17:29:09 +0100
From: Peter Zijlstra <peterz@infradead.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Ingo Molnar <mingo@kernel.org>,
        Alexander Shishkin <alexander.shishkin@linux.intel.com>,
        Stephane Eranian <eranian@google.com>,
        LKML <linux-kernel@vger.kernel.org>, vince@deater.net,
        Andi Kleen <andi@firstfloor.org>, jolsa@redhat.com,
        Thomas Gleixner <tglx@linutronix.de>,
        Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: [RFC][PATCH 00/12] various perf fixes
Message-ID: <20160215162909.GJ6357@twins.programming.kicks-ass.net>
References: <20160111162458.427203780@infradead.org>
 <20160112101109.GC20997@gmail.com>
 <CACT4Y+Zb4VE5HiAvEubFU6W=+iXgoDB-1xCSd_r3MYGzbetMxQ@mail.gmail.com>
 <CACT4Y+bNJi8T031hgbh832f1G9cKofYDx8maH6zSS93KnUQJLw@mail.gmail.com>
 <CACT4Y+Zdn2i0bG3=ALRkm2_RwAJE9WTf9qYb=5vXfDtos8Hzgg@mail.gmail.com>
 <CACT4Y+bAqP78kMGG3QxNUEEVCqesW8PhpL5KS+8U8=D0C4F71A@mail.gmail.com>
 <20160114093529.GU6344@twins.programming.kicks-ass.net>
 <CACT4Y+Ym0TZLkmRrM0ZGgLpu8kqS-YjoWTMrvaLz=tx2tnyO3w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CACT4Y+Ym0TZLkmRrM0ZGgLpu8kqS-YjoWTMrvaLz=tx2tnyO3w@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2012-12-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Thu, Jan 14, 2016 at 11:05:50AM +0100, Dmitry Vyukov wrote:
> There is a way to run it without coverage on a local machine.
> 
> First, you need to setup Go toolchain: download latest Go distribution
> from https://golang.org/dl:
> https://storage.googleapis.com/golang/go1.5.3.linux-amd64.tar.gz
> Unpack it to $HOME/go1.5.
> 
> $ export GOROOT=$HOME/go1.5

> $ export GOPATH=$HOME/gopath

So after I put that in a profile.d file:

> Download syzkaller sources:
> 
> $ go get github.com/google/syzkaller

package github.com/google/syzkaller: no buildable Go source files in /root/gopath/src/github.com/google/syzkaller

> Build necessary syzkaller binaries:
> 
> $ cd $GOPATH/src/github.com/google/syzkaller
> $ make

That seems to have done its thing

> Then save the following content into
> $GOPATH/src/github.com/google/syzkaller/perf.cfg
> 

{
	"http": "localhost:50000",
	"workdir": "root/gopath/src/github.com/google/syzkaller/workdir",
	"syzkaller": "/root/gopath/src/github.com/google/syzkaller",
	"vmlinux": "-",
	"type": "local",
	"count": 1,
	"procs": 160,
	"nocover": true,
	"nodropprivs": true,
	"enable_syscalls": [
		"perf_event_open",
		"ioctl$PERF*",
		"prctl$void",
		"bpf$*",
		"sched_yield"
	]
}

> Alter paths as necessary. Also you can change procs parameter (number
> of parallel test processes), something like NCPU*4 would be a good
> number. Also you can add additional syscalls to the mix.

per the above

> Then run:
> 
> $ bin/syz-manager -config perf.cfg
> 
> If you run it on a separate test machine, then scp syzkaller/bin dir
> and perf.cfg to the machine (the syzkaller param in config is where it
> will search for the bin dir).
> 
> If syz-manager does not appear to be doing anything useful, then pleas
> run it in the following mode and post output:
> 
> $ bin/syz-manager -config perf.cfg -v 1 -debug

root@ivb-ep:~/gopath/src/github.com/google/syzkaller# bin/syz-manager -config perf.cfg -v 1 -debug
2016/02/15 17:12:50 bad config syzkaller param: can't find bin/syz-execprog

And its right, no such thing as bin/syz-execprog