[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 24/36] printk: Remove trace_.*_rcuidle() usage
 
- To: Sergey Senozhatsky <senozhatsky@xxxxxxxxxxxx>
 
- From: Petr Mladek <pmladek@xxxxxxxx>
 
- Date: Thu, 9 Jun 2022 15:02:20 +0200
 
- Cc: Peter Zijlstra <peterz@xxxxxxxxxxxxx>, ink@xxxxxxxxxxxxxxxxxxxx,	mattst88@xxxxxxxxx, vgupta@xxxxxxxxxx, linux@xxxxxxxxxxxxxxx,	ulli.kroll@xxxxxxxxxxxxxx, linus.walleij@xxxxxxxxxx,	shawnguo@xxxxxxxxxx, Sascha Hauer <s.hauer@xxxxxxxxxxxxxx>,	kernel@xxxxxxxxxxxxxx, festevam@xxxxxxxxx, linux-imx@xxxxxxx,	tony@xxxxxxxxxxx, khilman@xxxxxxxxxx, catalin.marinas@xxxxxxx,	will@xxxxxxxxxx, guoren@xxxxxxxxxx, bcain@xxxxxxxxxxx,	chenhuacai@xxxxxxxxxx, kernel@xxxxxxxxxx, geert@xxxxxxxxxxxxxx,	sammy@xxxxxxxxx, monstr@xxxxxxxxx, tsbogend@xxxxxxxxxxxxxxxx,	dinguyen@xxxxxxxxxx, jonas@xxxxxxxxxxxx,	stefan.kristiansson@xxxxxxxxxxxxx, shorne@xxxxxxxxx,	James.Bottomley@xxxxxxxxxxxxxxxxxxxxx, deller@xxxxxx,	mpe@xxxxxxxxxxxxxx, benh@xxxxxxxxxxxxxxxxxxx, paulus@xxxxxxxxx,	paul.walmsley@xxxxxxxxxx, palmer@xxxxxxxxxxx, aou@xxxxxxxxxxxxxxxxx,	hca@xxxxxxxxxxxxx, gor@xxxxxxxxxxxxx, agordeev@xxxxxxxxxxxxx,	borntraeger@xxxxxxxxxxxxx, svens@xxxxxxxxxxxxx,	ysato@xxxxxxxxxxxxxxxxxxxx, dalias@xxxxxxxx, davem@xxxxxxxxxxxxx,	richard@xxxxxx, anton.ivanov@xxxxxxxxxxxxxxxxxx,	johannes@xxxxxxxxxxxxxxxx, tglx@xxxxxxxxxxxxx, mingo@xxxxxxxxxx,	bp@xxxxxxxxx, dave.hansen@xxxxxxxxxxxxxxx, x86@xxxxxxxxxx,	hpa@xxxxxxxxx, acme@xxxxxxxxxx, mark.rutland@xxxxxxx,	alexander.shishkin@xxxxxxxxxxxxxxx, jolsa@xxxxxxxxxx,	namhyung@xxxxxxxxxx, jgross@xxxxxxxx, srivatsa@xxxxxxxxxxxxx,	amakhalov@xxxxxxxxxx, pv-drivers@xxxxxxxxxx,	boris.ostrovsky@xxxxxxxxxx, chris@xxxxxxxxxx, jcmvbkbc@xxxxxxxxx,	rafael@xxxxxxxxxx, lenb@xxxxxxxxxx, pavel@xxxxxx,	gregkh@xxxxxxxxxxxxxxxxxxx, mturquette@xxxxxxxxxxxx,	sboyd@xxxxxxxxxx, daniel.lezcano@xxxxxxxxxx, lpieralisi@xxxxxxxxxx,	sudeep.holla@xxxxxxx, agross@xxxxxxxxxx, bjorn.andersson@xxxxxxxxxx,	anup@xxxxxxxxxxxxxx, thierry.reding@xxxxxxxxx, jonathanh@xxxxxxxxxx,	jacob.jun.pan@xxxxxxxxxxxxxxx, Arnd Bergmann <arnd@xxxxxxxx>,	yury.norov@xxxxxxxxx, andriy.shevchenko@xxxxxxxxxxxxxxx,	linux@xxxxxxxxxxxxxxxxxx, rostedt@xxxxxxxxxxx,	john.ogness@xxxxxxxxxxxxx, paulmck@xxxxxxxxxx, frederic@xxxxxxxxxx,	quic_neeraju@xxxxxxxxxxx, josh@xxxxxxxxxxxxxxxx,	mathieu.desnoyers@xxxxxxxxxxxx, jiangshanlai@xxxxxxxxx,	joel@xxxxxxxxxxxxxxxxx, juri.lelli@xxxxxxxxxx,	vincent.guittot@xxxxxxxxxx, dietmar.eggemann@xxxxxxx,	bsegall@xxxxxxxxxx, mgorman@xxxxxxx, bristot@xxxxxxxxxx,	vschneid@xxxxxxxxxx, jpoimboe@xxxxxxxxxx,	linux-alpha@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx,	linux-snps-arc@xxxxxxxxxxxxxxxxxxx,	linux-arm-kernel@xxxxxxxxxxxxxxxxxxx, linux-omap@xxxxxxxxxxxxxxx,	linux-csky@xxxxxxxxxxxxxxx, linux-hexagon@xxxxxxxxxxxxxxx,	linux-ia64@xxxxxxxxxxxxxxx, linux-m68k@xxxxxxxxxxxxxxxxxxxx,	linux-mips@xxxxxxxxxxxxxxx, openrisc@xxxxxxxxxxxxxxxxxxxx,	linux-parisc@xxxxxxxxxxxxxxx, linuxppc-dev@xxxxxxxxxxxxxxxx,	linux-riscv@xxxxxxxxxxxxxxxxxxx, linux-s390@xxxxxxxxxxxxxxx,	linux-sh@xxxxxxxxxxxxxxx, sparclinux@xxxxxxxxxxxxxxx,	linux-um@xxxxxxxxxxxxxxxxxxx, linux-perf-users@xxxxxxxxxxxxxxx,	virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx,	xen-devel@xxxxxxxxxxxxxxxxxxxx, linux-xtensa@xxxxxxxxxxxxxxxx,	linux-acpi@xxxxxxxxxxxxxxx, linux-pm@xxxxxxxxxxxxxxx,	linux-clk@xxxxxxxxxxxxxxx, linux-arm-msm@xxxxxxxxxxxxxxx,	linux-tegra@xxxxxxxxxxxxxxx, linux-arch@xxxxxxxxxxxxxxx,	rcu@xxxxxxxxxxxxxxx
 
- Delivery-date: Thu, 09 Jun 2022 13:09:18 +0000
 
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
 
 
 
On Thu 2022-06-09 20:30:58, Sergey Senozhatsky wrote:
> My emails are getting rejected... Let me try web-interface
Bad day for mail sending. I have problems as well ;-)
> Kudos to Petr for the questions and thanks to PeterZ for the answers.
> 
> On Thu, Jun 9, 2022 at 7:02 PM Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:
> > This is the tracepoint used to spool all of printk into ftrace, I
> > suspect there's users, but I haven't used it myself.
> 
> I'm somewhat curious whether we can actually remove that trace event.
Good question.
Well, I think that it might be useful. It allows to see trace and
printk messages together.
It was ugly when it was in the console code. The new location
in vprintk_store() allows to have it even "correctly" sorted
(timestamp) against other tracing messages.
Best Regards,
Petr
 
 
    
     |