From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9E0374779B2 for ; Fri, 22 May 2026 15:41:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779464465; cv=none; b=KNccqsGv5iYVyyscFnScHteQQMrJ6OFLaSj2g7ASXODOxPnc9qf4o4IqN1RIqBvAPO9wFPu7VAFz7FdqSqxi16hBnTt/iYB4gAUYKsCXFbn9BEbojfSzk+T1bg58Q7BWnrUrV97JTuIb/tWejl32KDOJME3YF3enEfpvX6W+SBo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779464465; c=relaxed/simple; bh=wDU+c5CZmQ0NL4rb4L+JstW2HDWtfcDI7A5aCTbC/to=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=akZUcs08QBDA7LTGQSudT9cr3pxQFMuabNS4YHFRACKqyw5XRb59U6MJQzXDk+5vzTWJ/l3wEjXk3txRtlWqMpGVa0wEh8D/AEztsNmcuHn3Whp9bxw8f5VTCgebNoGJdEkvTHfR2VlXuG5QmPOj+3AkC3k6z3gEr1fcJwHvNx0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=JIP4pTK6; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="JIP4pTK6" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 85A171F00A3D; Fri, 22 May 2026 15:41:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1779464464; bh=wDU+c5CZmQ0NL4rb4L+JstW2HDWtfcDI7A5aCTbC/to=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=JIP4pTK6FNJ+HevFkwVCT51Jvt5anm5//zld+vJkqCeDF5ls/uiRwJNn3V7uLIjbw El0taBEKmZ4gjr4jGEUo++JY+g95bF4o5nf68dXeFQE7uVi8+bduuY1e5ccG9BoT/4 PAin0txJo9fVYNHxALwbtI6DGDYKFxurZIigv+M/yZMhcCu3sBiB392UXue3YuHOt4 Dog/g3nkHMB15ANVQd98oWC2/kIBaK5ShANY5RpY6n33hnTfkrh2BrH7u1m1+cmQ0p fEAnI7xekXB7PTueHMEWQAZPW3r+5zoXruyD1O/81RzpkGjT15RK7P0L1nR0FVCd3n qrGzy2Hw+IySA== Date: Fri, 22 May 2026 11:41:26 -0400 From: Steven Rostedt To: Ian Rogers Cc: linux-kernel@vger.kernel.org, Masami Hiramatsu , Mark Rutland , Mathieu Desnoyers , Andrew Morton , Arnaldo Carvalho de Melo , Jiri Olsa , Peter Zijlstra , Namhyung Kim Subject: Re: [for-next][PATCH 10/15] tracing: Allow perf to read synthetic events Message-ID: <20260522114126.5df2f008@gandalf.local.home> In-Reply-To: References: <20260522143508.298439732@kernel.org> <20260522143526.523134137@kernel.org> X-Mailer: Claws Mail 3.20.0git84 (GTK+ 2.24.33; x86_64-pc-linux-gnu) Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Fri, 22 May 2026 08:19:36 -0700 Ian Rogers wrote: > On Fri, May 22, 2026 at 7:35=E2=80=AFAM Steven Rostedt wrote: > > > > From: Steven Rostedt > > > > Currently, perf can not enable synthetic events. When it does, it either > > causes a warning in the kernel or errors with "no such device". > > > > Add the necessary code to allow perf to also attach to synthetic events= . =20 >=20 > Thanks so much for doing this work! I hoped to spend some time testing > it, but there's never enough time. For the synthetic event I was I totally understand not having time. Heck, I'm currently unemployed and I'm still having a hard time finding time! > wondering what values end up in the perf sample like 'period'? I can You mean to poll on the event? > imagine this being the case and that, if you are doing something like > a futex wait duration, having to interpret the raw data rather than > just getting aggregation for free in `perf report` via the period. > That's not wrong but I was just curious. I guess I'm not quite sure what you mean by "the period". But then again, I don't use perf that much. -- Steve