public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephane Eranian <eranian@frankl.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Preempt problems
Date: Mon, 03 Feb 2003 21:36:26 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805803@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805801@msgid-missing>

Peter,

On Tue, Feb 04, 2003 at 07:17:01AM +1100, Peter Chubb wrote:
> 
> Hi David,
>    Just a heads up --- there are still two major problems with the
> patch I submitted for preemption support, so I suggest you don't merge
> it yet (although I'd very much appreciate having it reviewed and
> tested by third parties).
> 
> The two problems I see are:
>     -- perfmon missing interrupts *even with CONFIG_PREEMPT turned
> off!*

As for perfmon, there are some known issues with perfmon and the O(1) 
scheduler (deadlocks during ctxsw in SMP). I am not sure it affects your 
particular test case. I had postponed fixing this because I am working on 
a new perfmon code base for 2.5 in which (hopefully) all problems are gone. 
However a somewhat related issue came up last week and I decided to fix 
some of the problems. I will try to give a new patch to David this week.

As for preemption and perfmon, I haven't had a chance to look at the patch
yet. There are some assumptions about not being preemptable at several places.

-- 
-Stephane


  reply	other threads:[~2003-02-03 21:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 20:17 [Linux-ia64] Preempt problems Peter Chubb
2003-02-03 21:36 ` Stephane Eranian [this message]
2003-02-03 22:33 ` Peter Chubb
2003-02-03 23:43 ` David Mosberger
2003-02-05 17:03 ` Joel GUILLET
2003-02-14 20:05 ` Ray Bryant
2003-02-14 20:11 ` Stephane Eranian
2003-02-14 21:04 ` Ray Bryant

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=marc-linux-ia64-105590709805803@msgid-missing \
    --to=eranian@frankl.hpl.hp.com \
    --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