From: Ingo Molnar <mingo@elte.hu>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: preempt timing violations
Date: Mon, 26 Jul 2004 11:25:29 +0200 [thread overview]
Message-ID: <20040726092529.GB25904@elte.hu> (raw)
In-Reply-To: <1090832953.6936.114.camel@mindpipe>
* Lee Revell <rlrevell@joe-job.com> wrote:
> 2 and 1. Now that I think about it, this could have happened during
> bootup, before my rc.local set these. I will try passing them on the
> kernel command line.
the kernel command line option for immediate 2:1 is:
"voluntary-preempt=2 preempt=1"
Ingo
next prev parent reply other threads:[~2004-07-26 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 3:51 Lee Revell
2004-07-26 8:50 ` Ingo Molnar
2004-07-26 9:09 ` Lee Revell
2004-07-26 9:22 ` Ingo Molnar
2004-07-26 9:25 ` Ingo Molnar [this message]
2004-07-26 15:43 ` preempt timing violations (unmap_vmas) Rudo Thomas
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=20040726092529.GB25904@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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®