From: Clark Williams <williams@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>, Mark Knecht <markknecht@gmail.com>,
Robert Crocombe <rwcrocombe@raytheon.com>,
Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>
Subject: Re: [PATCH -rt 0/2] Get x86_64 running with PREEMPT_RT
Date: Fri, 26 May 2006 13:19:11 -0500 [thread overview]
Message-ID: <4477469F.7040103@redhat.com> (raw)
In-Reply-To: <20060526160651.870725515@goodmis.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Steven Rostedt wrote:
> The following two patches get PREEMPT_RT running on x86_64. I'm currently
> writing this from my x86_64 box running 2.6.16-rt23.
>
> The first patch probably only affected me, since it was caused by
> having clocksource=XXX in the command line.
>
> The other patch simply fixes a bad condition in the default_idle
> which prevented the idle task from ever scheduling (that was bad!)
Fixed my problem on Athlon64x2.
Thanks,
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFEd0afHyuj/+TTEp0RAmMsAJ9Zf1n/GMHOB+SYXdI7fWGYfbkcVwCgrK6I
I0pV042x2vtPj7750lzIXeM=
=eMDn
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2006-05-26 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-26 16:06 [PATCH -rt 0/2] Get x86_64 running with PREEMPT_RT Steven Rostedt
2006-05-26 16:06 ` [PATCH -rt 1/2] Dont blindly turn on interrupts in boot_override_clocksource Steven Rostedt
2006-05-26 17:39 ` Ingo Molnar
2006-05-26 16:06 ` [PATCH -rt 2/2] Fix condition in default_idle Steven Rostedt
2006-05-26 17:39 ` Ingo Molnar
2006-05-26 18:19 ` Clark Williams [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=4477469F.7040103@redhat.com \
--to=williams@redhat.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=rwcrocombe@raytheon.com \
--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.