2012/10/29 Steven Rostedt :
> On Mon, 2012-10-29 at 14:28 +0100, Frederic Weisbecker wrote:
>> klogd is woken up asynchronously from the tick in order
>> to do it safely.
>>
>> However if printk is called when the tick is stopped, the reader
>> won't be woken up until the next interrupt, which
On Mon, 2012-10-29 at 14:28 +0100, Frederic Weisbecker wrote:
> klogd is woken up asynchronously from the tick in order
> to do it safely.
>
> However if printk is called when the tick is stopped, the reader
> won't be woken up until the next interrupt, which might not fire
> before a while. As a
klogd is woken up asynchronously from the tick in order
to do it safely.
However if printk is called when the tick is stopped, the reader
won't be woken up until the next interrupt, which might not fire
before a while. As a result, the user may miss some message.
To fix this, lets implement the
2012/10/29 Steven Rostedt rost...@goodmis.org:
On Mon, 2012-10-29 at 14:28 +0100, Frederic Weisbecker wrote:
klogd is woken up asynchronously from the tick in order
to do it safely.
However if printk is called when the tick is stopped, the reader
won't be woken up until the next interrupt,
klogd is woken up asynchronously from the tick in order
to do it safely.
However if printk is called when the tick is stopped, the reader
won't be woken up until the next interrupt, which might not fire
before a while. As a result, the user may miss some message.
To fix this, lets implement the
On Mon, 2012-10-29 at 14:28 +0100, Frederic Weisbecker wrote:
klogd is woken up asynchronously from the tick in order
to do it safely.
However if printk is called when the tick is stopped, the reader
won't be woken up until the next interrupt, which might not fire
before a while. As a
6 matches
Mail list logo
