From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Jain Priyanka-B32167 <B32167@freescale.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: 3.8.10-rt6 : Observing high latency as preempt_schedule_irq:__schedule is not getting called
Date: Fri, 31 May 2013 13:11:37 +0200 [thread overview]
Message-ID: <51A88569.503@linutronix.de> (raw)
In-Reply-To: <AC83832D6324604BB08FAE5A33553F190B3B849B@039-SN2MPN1-012.039d.mgd.msft.net>
On 05/28/2013 06:01 AM, Jain Priyanka-B32167 wrote:
> Submitted below patch to linuxppc-dev@lists.ozlabs.org to fix this issue
Thank you very much. The problem was introduced in v3.7-rc1 so it is a
v3.8-rt problem only.
Sebastian
prev parent reply other threads:[~2013-05-31 11:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 10:40 3.8.10-rt6 : Observing high latency as timer_interrupt is taking longer to exit Jain Priyanka-B32167
2013-05-15 10:19 ` Jain Priyanka-B32167
2013-05-21 5:42 ` Jain Priyanka-B32167
2013-05-21 7:01 ` 3.8.10-rt6 : Observing high latency as preempt_schedule_irq:__schedule is not getting called Jain Priyanka-B32167
2013-05-28 4:01 ` Jain Priyanka-B32167
2013-05-31 11:11 ` Sebastian Andrzej Siewior [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=51A88569.503@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=B32167@freescale.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.