Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1503474
| From | Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC][PATCHv3 0/6] printk: use printk_safe to handle printk() recursive calls |
| Date | 2016-10-19 03:20 +0200 |
| Message-ID | <stNHX-1YD-3@gated-at.bofh.it> (permalink) |
| References | <stEOm-3Fs-11@gated-at.bofh.it> <stFKq-4lw-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On (10/18/16 09:45), Joe Perches wrote:
> On Wed, 2016-10-19 at 00:40 +0900, Sergey Senozhatsky wrote:
> > This patch set extends a lock-less NMI per-cpu buffers idea to
> > handle recursive printk() calls.
>
> trivia:
>
> recursive or reentrant?
a recursive one.
printk -> {foo} -> printk
reentrant printk() case was addressed by Petr Mladek's nmi patchset:
printk()
foo
-------> NMI
printk()
-ss
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC][PATCHv3 0/6] printk: use printk_safe to handle printk() recursive calls Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2016-10-18 17:50 +0200
[RFC][PATCHv3 5/6] printk: use printk_safe buffers Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2016-10-18 17:50 +0200
[RFC][PATCHv3 2/6] printk: rename nmi.c and exported api Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2016-10-18 17:50 +0200
Re: [RFC][PATCHv3 2/6] printk: rename nmi.c and exported api Steven Rostedt <rostedt@goodmis.org> - 2016-10-18 18:50 +0200
Re: [RFC][PATCHv3 2/6] printk: rename nmi.c and exported api Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2016-10-19 04:00 +0200
[RFC][PATCHv3 6/6] printk: remove zap_locks() function Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2016-10-18 17:50 +0200
[RFC][PATCHv3 4/6] printk: report lost messages in printk safe/nmi contexts Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2016-10-18 17:50 +0200
Re: [RFC][PATCHv3 0/6] printk: use printk_safe to handle printk() recursive calls Joe Perches <joe@perches.com> - 2016-10-18 18:50 +0200
Re: [RFC][PATCHv3 0/6] printk: use printk_safe to handle printk() recursive calls Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2016-10-19 03:20 +0200
Re: [RFC][PATCHv3 0/6] printk: use printk_safe to handle printk() recursive calls Peter Zijlstra <peterz@infradead.org> - 2016-10-18 19:10 +0200
Re: [RFC][PATCHv3 0/6] printk: use printk_safe to handle printk() recursive calls Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2016-10-19 04:00 +0200
Re: [RFC][PATCHv3 0/6] printk: use printk_safe to handle printk() recursive calls Peter Zijlstra <peterz@infradead.org> - 2016-10-19 18:20 +0200
Re: [RFC][PATCHv3 0/6] printk: use printk_safe to handle printk() recursive calls Peter Zijlstra <peterz@infradead.org> - 2016-10-19 16:30 +0200
Re: [RFC][PATCHv3 0/6] printk: use printk_safe to handle printk() recursive calls Sergey Senozhatsky <sergey.senozhatsky@gmail.com> - 2016-10-20 15:20 +0200
Re: [RFC][PATCHv3 0/6] printk: use printk_safe to handle printk() recursive calls Petr Mladek <pmladek@suse.com> - 2016-10-19 16:40 +0200
Re: [RFC][PATCHv3 0/6] printk: use printk_safe to handle printk() recursive calls Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> - 2016-10-19 06:40 +0200
csiph-web