mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: Jiri Kosina <jkosina@suse.com>, Jan Kara <jack@suse.com>,
	Tejun Heo <tj@kernel.org>,
	Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
	Byungchul Park <byungchul.park@lge.com>,
	linux-kernel@vger.kernel.org, Petr Mladek <pmladek@suse.com>
Subject: [PATCH POC 0/4] printk: Several fixes of cont buffer and console handling
Date: Fri, 15 Jul 2016 18:58:58 +0200	[thread overview]
Message-ID: <1468601942-18482-1-git-send-email-pmladek@suse.com> (raw)

This patch set is a working POC how to reduce mess with partially
printed lines. In addition, it fixes some races when replying logbuffer
on new consoles.

It can be applied on top of v12 of the async printk patches, see
https://lkml.kernel.org/g/20160513131848.2087-1-sergey.senozhatsky@gmail.com
But it is basically independent on the async printk stuff.

I wanted to see how my proposal could look like in practice
https://lkml.kernel.org/g/20160712162809.GE32373@pathway.suse.cz


IMPORTANT: I have vacation next two weeks and will not have much access
to the newtwork. I wanted to sent what I had before leaving. The last
patch is not much tested. Feel free to take it, rework it yourself
or just send your opinion.

Petr Mladek (4):
  printk: Prepeparation for fake cont buffers
  printk: Do not block cont buffer by partially flushed lines
  printk: Flush the cont buffer after the other lines
  printk: Correctly replay buffer log for a new console

 kernel/printk/printk.c | 235 +++++++++++++++++++++++++++----------------------
 1 file changed, 128 insertions(+), 107 deletions(-)

-- 
1.8.5.6

             reply	other threads:[~2016-07-15 16:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-15 16:58 Petr Mladek [this message]
2016-07-15 16:58 ` [PATCH POC 1/4] printk: Prepeparation for fake cont buffers Petr Mladek
2016-07-15 18:26   ` kbuild test robot
2016-07-15 16:59 ` [PATCH POC 2/4] printk: Do not block cont buffer by partially flushed lines Petr Mladek
2016-07-15 18:31   ` kbuild test robot
2016-07-15 22:08   ` kbuild test robot
2016-07-15 16:59 ` [PATCH POC 3/4] printk: Flush the cont buffer after the other lines Petr Mladek
2016-07-15 16:59 ` [PATCH POC 4/4] printk: Correctly replay buffer log for a new console Petr Mladek
2016-07-15 18:27   ` kbuild test robot

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=1468601942-18482-1-git-send-email-pmladek@suse.com \
    --to=pmladek@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=byungchul.park@lge.com \
    --cc=jack@suse.com \
    --cc=jkosina@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=tj@kernel.org \
    /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

all inboxes | Powered by JetHome®