mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Petr Mladek <pmladek@suse.com>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] printk for 4.13
Date: Thu, 6 Jul 2017 10:18:44 +0900	[thread overview]
Message-ID: <20170706011844.GC7195@jagdpanzerIV.localdomain> (raw)
In-Reply-To: <CA+55aFxXPnNo_tkKb-3iyeRb1Vugfcg=1z9vc7ZmYzxZb5237w@mail.gmail.com>

On (07/05/17 18:15), Linus Torvalds wrote:
> On Wed, Jul 5, 2017 at 5:44 PM, Sergey Senozhatsky
> <sergey.senozhatsky.work@gmail.com> wrote:
> >
> > PRINTK_NMI_DEFERRED_CONTEXT_MASK calls into vprintk_deferred(), which
> > does vprintk_emit(0, LOGLEVEL_SCHED, NULL, 0, fmt, args). and
> > vprintk_emit() LOGLEVEL_SCHED is nothing, but printk_deferred(), which
> > never calls into the scheduler and does not even try to lock console_sem.
> 
> Hmm. Ok. I think I see what you're saying. We're just adding it to the
> log buffer, but not actually going through the whole "lets see if we
> can push it further".

yep ;)

> So I will take another look tomorrow, right now I'm feeling a bit
> merged out for the day,

sure. thanks.

	-ss

      reply	other threads:[~2017-07-06  1:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 14:24 Petr Mladek
2017-07-05 18:23 ` Linus Torvalds
2017-07-06  0:44   ` Sergey Senozhatsky
2017-07-06  0:53     ` Sergey Senozhatsky
2017-07-06  1:15     ` Linus Torvalds
2017-07-06  1:18       ` Sergey Senozhatsky [this message]

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=20170706011844.GC7195@jagdpanzerIV.localdomain \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky@gmail.com \
    --cc=torvalds@linux-foundation.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®