Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1189683

Re: Why linux console designed to work in polling mode?

From yalin wang <yalin.wang2010@gmail.com>
Newsgroups linux.kernel
Subject Re: Why linux console designed to work in polling mode?
Date 2015-07-22 09:00 +0200
Message-ID <pOWau-7Gp-3@gated-at.bofh.it> (permalink)
References <pOVHs-78W-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


> On Jul 22, 2015, at 14:27, Arun KS <arunks.linux@gmail.com> wrote:
> 
> When i checked how kernel printing works, i mentioned that it takes
> messages from log_buffer in console_unlock and gives it to
> call_console_drivers -> ...-> some uart bsp function. Basically, as i
> see this BSP realization tries to flush all message chars in busyloop
> ... so it waits until FIFO_NOT_FULL bit will be dropped by UART and it
> will be able to push the next byte. Basically, as i see userspace
> printing do something different. It puts N_FIFO_BYTES and exits, next,
> when FIFO will be freed - interrupt will be generated, and other
> characters will be put into UART FIFO.
> Can we do something similar for kernel printing? i.e. do not busyloop
> sending char after char, but put N_FIFO chars and flush  other in
> interrupt. When panic will occur we can do busyloop printing again. Is
> it reliable? Suppose we have several cores.
> 
> 

i think it is because printk is very different from other printf  function in user space,
printk()  can be called  in any context  atomic / non- atomic / irq /  soft-irq context ..

so your  bsp->print function can’t be sleep, can’t call any sleep functions .

another reason is that in console_unlock() function, it call bas->print like this:
	call_console_drivers(level, ext_text, ext_len, text, len);
print expect your bsp function print all the text as showed in parameters.
and it doesn’t check the return value ,
so if your driver doesn’t use POLL mode, you should only print N_FIFO_BYTES bytes,
this need prink to check return value or need your bsp function to use some special method
to send the remaining bytes after received FIFO empty interrupt.
it is not easy to implement in a context that you can’t call any sleep function.

Thanks--
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/

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Why linux console designed to work in polling mode? Arun KS <arunks.linux@gmail.com> - 2015-07-22 08:30 +0200
  Re: Why linux console designed to work in polling mode? yalin wang <yalin.wang2010@gmail.com> - 2015-07-22 09:00 +0200
    Re: Why linux console designed to work in polling mode? Alexander <alexhoppus111@gmail.com> - 2015-07-23 08:00 +0200

csiph-web