From: Petr Mladek <pmladek@suse.cz>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, jkosina@suse.cz,
paulmck@linux.vnet.ibm.com, Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [RFC][PATCH] printk: Fixup the nmi printk mess
Date: Fri, 26 Jun 2015 10:06:03 +0200 [thread overview]
Message-ID: <20150626080603.GP9409@pathway.suse.cz> (raw)
In-Reply-To: <20150625181459.GB3644@twins.programming.kicks-ass.net>
On Thu 2015-06-25 20:14:59, Peter Zijlstra wrote:
> On Fri, Jun 12, 2015 at 05:35:05PM +0200, Petr Mladek wrote:
> > I have got another idea. We already use a lock to synchronize
> > readers. It might be used to avoid the race and keep the global
> > flush().
> >
> > I played with it, see below. It is based on 2nd Peter's patch
> > where I modified only struct nmi_seq_buf, __printk_nmi_flush(),
> > and vprintk_nmi().
> >
> > It forces the reader to flush everything or nothing. It is less
> > effective than the previous code but much more simple.
> >
> > It seems to work but it is just a proof-of-concept. Also I think that
> > it would be possible to use the normal seq_buf in the end.
>
> Sorry, got side tracked. Yes this looks ok. Want to submit a proper
> patch?
No problem. OK, I will prepare a proper patch the following week if
nothing break my plans ;-)
Thanks for feedback.
Best Regards,
Petr
next prev parent reply other threads:[~2015-06-26 8:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 12:55 [RFC][PATCH] printk: Fixup the nmi printk mess Peter Zijlstra
2015-06-10 14:31 ` Petr Mladek
2015-06-10 14:57 ` Petr Mladek
2015-06-10 15:32 ` Peter Zijlstra
2015-06-10 15:54 ` Steven Rostedt
2015-06-10 15:29 ` Peter Zijlstra
2015-06-10 19:23 ` Peter Zijlstra
2015-06-10 19:36 ` Peter Zijlstra
2015-06-10 19:36 ` Steven Rostedt
2015-06-11 14:55 ` Petr Mladek
2015-06-12 12:00 ` Peter Zijlstra
2015-06-12 14:28 ` Petr Mladek
2015-06-12 15:35 ` Petr Mladek
2015-06-25 18:14 ` Peter Zijlstra
2015-06-26 8:06 ` Petr Mladek [this message]
2015-06-11 9:57 ` Petr Mladek
2015-06-10 15:53 ` Steven Rostedt
2015-06-10 16:02 ` Steven Rostedt
2015-06-10 16:19 ` Joe Perches
2015-06-10 19:25 ` Peter Zijlstra
2015-06-10 19:35 ` Steven Rostedt
2015-06-10 19:39 ` Joe Perches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150626080603.GP9409@pathway.suse.cz \
--to=pmladek@suse.cz \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox