public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: linux-ia64@vger.kernel.org
Subject: Fw: [Bugme-new] [Bug 2885] New: realtime process can't preempt low
Date: Mon, 14 Jun 2004 07:29:31 +0000	[thread overview]
Message-ID: <20040614002931.00b846a4.akpm@osdl.org> (raw)


This would appear to indicate that CONFIG_PREEMPT isn't working
correctly on ia64.


Begin forwarded message:

Date: Mon, 14 Jun 2004 00:25:22 -0700
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
Subject: [Bugme-new] [Bug 2885] New: realtime process can't preempt low priority process in kernel


http://bugme.osdl.org/show_bug.cgi?id(85

           Summary: realtime process can't preempt low priority process in
                    kernel
    Kernel Version: 2.6.5
            Status: NEW
          Severity: normal
             Owner: rml@tech9.net
         Submitter: hong.liu@intel.com
                CC: yi.zhu@intel.com


Distribution:
Hardware Environment: 4 Itanium2 1.4G processors-tiger4
Software Environment: gcc-3.3.3
Problem Description:

After turning on the CONFIG_PREEMPT option and recompile the kernel source 
code, the realtime process still can't preempt the low priority process which 
is doing busy loop in kernel. 
The test case does pass both on a pentium 4 PC and a Xeon 2.4G smp machine.

Steps to reproduce:
in the directory of the test case, 
#make
#insmod ./modules/hog.ko
#mknod /dev/hog c 126 0
#./do_hog

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

             reply	other threads:[~2004-06-14  7:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-14  7:29 Andrew Morton [this message]
2004-06-21 23:57 ` Fw: [Bugme-new] [Bug 2885] New: realtime process can't preempt low priority process in kernel Peter Chubb
2004-06-24  1:48 ` Zhu, Yi
2004-06-29 18:42 ` David Mosberger

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=20040614002931.00b846a4.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=linux-ia64@vger.kernel.org \
    /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