On Thu, 2012-11-15 at 13:13 -0500, Steven Rostedt wrote:
> > +
> > +/*
> > + * Run the irq_work entries on this cpu. Requires to be ran from hardirq
> > + * context with local IRQs disabled.
> > + */
> > +void irq_work_run(void)
> > +{
> > + BUG_ON(!in_irq());
> > + __irq_work_run();
> > +}
>
On Thu, 2012-11-15 at 11:34 -0500, Steven Rostedt wrote:
Frederic,
Please add this one fix below:
> Index: linux-rt.git/kernel/irq_work.c
> ===
> --- linux-rt.git.orig/kernel/irq_work.c
> +++ linux-rt.git/kernel/irq_work.c
> @@
2012/11/15 Steven Rostedt :
> On Thu, 2012-11-15 at 16:25 +0100, Frederic Weisbecker wrote:
>> 2012/11/15 Steven Rostedt :
>> > On Wed, 2012-11-14 at 21:37 +0100, Frederic Weisbecker wrote:
>> >> diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
>> >> index f249e8c..822d757 100644
On Thu, 2012-11-15 at 16:25 +0100, Frederic Weisbecker wrote:
> 2012/11/15 Steven Rostedt :
> > On Wed, 2012-11-14 at 21:37 +0100, Frederic Weisbecker wrote:
> >> diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
> >> index f249e8c..822d757 100644
> >> --- a/kernel/time/tick-sched.c
2012/11/15 Frederic Weisbecker :
> ->
> CPU that offilines CPU offlining
> -
> -
> cpu_down() {
> __stop_machine(take_cpu_down)
>
> take_cpu_down() {
>
> __cpu_disable() {
>
> * disable irqs in hw
>
> *
2012/11/15 Steven Rostedt :
> On Wed, 2012-11-14 at 21:37 +0100, Frederic Weisbecker wrote:
>> diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
>> index f249e8c..822d757 100644
>> --- a/kernel/time/tick-sched.c
>> +++ b/kernel/time/tick-sched.c
>> @@ -289,7 +289,7 @@ static ktime_t
2012/11/15 Steven Rostedt rost...@goodmis.org:
On Wed, 2012-11-14 at 21:37 +0100, Frederic Weisbecker wrote:
diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
index f249e8c..822d757 100644
--- a/kernel/time/tick-sched.c
+++ b/kernel/time/tick-sched.c
@@ -289,7 +289,7 @@ static
2012/11/15 Frederic Weisbecker fweis...@gmail.com:
-
CPU that offilines CPU offlining
-
-
cpu_down() {
__stop_machine(take_cpu_down)
take_cpu_down() {
__cpu_disable() {
* disable irqs in hw
*
On Thu, 2012-11-15 at 16:25 +0100, Frederic Weisbecker wrote:
2012/11/15 Steven Rostedt rost...@goodmis.org:
On Wed, 2012-11-14 at 21:37 +0100, Frederic Weisbecker wrote:
diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
index f249e8c..822d757 100644
---
2012/11/15 Steven Rostedt rost...@goodmis.org:
On Thu, 2012-11-15 at 16:25 +0100, Frederic Weisbecker wrote:
2012/11/15 Steven Rostedt rost...@goodmis.org:
On Wed, 2012-11-14 at 21:37 +0100, Frederic Weisbecker wrote:
diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
index
On Thu, 2012-11-15 at 11:34 -0500, Steven Rostedt wrote:
Frederic,
Please add this one fix below:
Index: linux-rt.git/kernel/irq_work.c
===
--- linux-rt.git.orig/kernel/irq_work.c
+++ linux-rt.git/kernel/irq_work.c
@@ -14,6
On Thu, 2012-11-15 at 13:13 -0500, Steven Rostedt wrote:
+
+/*
+ * Run the irq_work entries on this cpu. Requires to be ran from hardirq
+ * context with local IRQs disabled.
+ */
+void irq_work_run(void)
+{
+ BUG_ON(!in_irq());
+ __irq_work_run();
+}
On Wed, 2012-11-14 at 21:37 +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
> for 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
for a while. As a result, the user may miss some message.
To fix this, lets implement the
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
for a while. As a result, the user may miss some message.
To fix this, lets implement the
On Wed, 2012-11-14 at 21:37 +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
for a while. As a result,
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
for a while. As a result, the user may miss some message.
To fix this, lets implement the
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
for a while. As a result, the user may miss some message.
To fix this, lets implement the
18 matches
Mail list logo
