public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	linux-kernel@vger.kernel.org, tglx@linutronix.de, akpm@osdl.org
Subject: Re: VM fixes [1/4]
Date: Fri, 24 Dec 2004 19:48:44 +0100	[thread overview]
Message-ID: <20041224184844.GK13747@dualathlon.random> (raw)
In-Reply-To: <1103913664.3921.2.camel@krustophenia.net>

On Fri, Dec 24, 2004 at 01:41:03PM -0500, Lee Revell wrote:
> On Fri, 2004-12-24 at 19:20 +0100, Andrea Arcangeli wrote:
> > Yep, I remeber this was the case in some old alpha. But did they
> > support smp too? I can't see how that old hardware could support smp.
> > If they're UP they're fine.
> 
> Isn't there still a race with PREEMPT?  Or am I missing something?

I was thinking the same right now, OTOH used_math is most important
during exceptions and sure preempt can't affect exceptions.

There are a few corner cases that you'd need to check to know if
used_math can be changed during normal kernel context and not only
during exceptions. Probably it's racy though. But what's the point of
enabling preempt in such an ancient hardare?

I'm not against fixing it up though, but at least we'd need a

#define _HAVE_BYTE_ATOMIC_GRANULARITY
#define _HAVE_SHORT_ATOMIC_GRANULARITY

(assuming short is the minimal smp atomic granularity we support in
linux)

to be able to write optimal code for anything that 99.999% of the
userbase would be using.

  reply	other threads:[~2004-12-24 18:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-24 17:35 VM fixes [1/4] Andrea Arcangeli
2004-12-24 18:00 ` David S. Miller
2004-12-24 18:20   ` Andrea Arcangeli
2004-12-24 18:41     ` Lee Revell
2004-12-24 18:48       ` Andrea Arcangeli [this message]
2004-12-24 18:52         ` Lee Revell
2004-12-25  4:40     ` Jeff Garzik

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=20041224184844.GK13747@dualathlon.random \
    --to=andrea@suse.de \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox