[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-kernel
Subject:    Re: [RFC][PATCH] printk: Fixup the nmi printk mess
From:       Petr Mladek <pmladek () suse ! cz>
Date:       2015-06-26 8:06:03
Message-ID: 20150626080603.GP9409 () pathway ! suse ! cz
[Download RAW message or body]

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
[prev in list] [next in list] [prev in thread] [next in thread]