From: Daniel Walker <dwalker@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: v2.6.21-rt2
Date: Wed, 16 May 2007 15:22:58 -0700 [thread overview]
Message-ID: <1179354178.20519.43.camel@imap.mvista.com> (raw)
In-Reply-To: <20070516220444.GA27081@elte.hu>
On Thu, 2007-05-17 at 00:04 +0200, Ingo Molnar wrote:
> * Daniel Walker <dwalker@mvista.com> wrote:
>
> > I don't know. irqs_off_preempt_count() could get used someplace else,
> > where you would want to flip the preempt_count() check .. It seems
> > sane to combine your patch with mine ..
> >
> > irqs_off_preempt_count() (!__get_cpu_var(trace_cpu_idle) &&
> > preempt_count())
> >
> > You can't call __get_cpu_var() without the a positive preempt_count(),
> > so the check seems backwards regardless of the other factors ..
>
> yeah. The whole trace_preempt_enter_idle() thing looks a bit suspect.
> Why cannot those architectures simply disable/enable preemption and get
> the same effect? It's not like we ever want to allow the preemption of
> the idle task.
They disable interrupts it looks like (i386, and x86_64), around the
same area where those trace_preempt_enter_idle calls are placed .. I'm
not up on the details of Steve's fix .. There's also a
preempt_disable/preempt_enable ..
I'm not up on the details of Steve's fix , but stuff looks a little
odd ..
Daniel
next prev parent reply other threads:[~2007-05-16 22:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 18:04 v2.6.21-rt2 Ingo Molnar
2007-05-16 20:54 ` v2.6.21-rt2 Daniel Walker
2007-05-16 21:01 ` v2.6.21-rt2 Ingo Molnar
2007-05-16 21:20 ` v2.6.21-rt2 Daniel Walker
2007-05-16 21:32 ` v2.6.21-rt2 Ingo Molnar
2007-05-16 21:47 ` v2.6.21-rt2 Daniel Walker
2007-05-16 22:04 ` v2.6.21-rt2 Ingo Molnar
2007-05-16 22:22 ` Daniel Walker [this message]
2007-05-16 23:32 ` v2.6.21-rt2 Free Ekanayaka
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=1179354178.20519.43.camel@imap.mvista.com \
--to=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®