From: Andrea Arcangeli <andrea@suse.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Magnus Naeslund(f)" <mag@fbab.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Alpha compile problem solved by Andrea (pte_alloc)
Date: Mon, 30 Apr 2001 01:46:53 +0200 [thread overview]
Message-ID: <20010430014653.C923@athlon.random> (raw)
In-Reply-To: <052901c0ceca$e6a543c0$020a0a0a@totalmef> <20010427155246.O16020@athlon.random> <m1k843qoc1.fsf@frodo.biederman.org>
In-Reply-To: <m1k843qoc1.fsf@frodo.biederman.org>; from ebiederm@xmission.com on Sun, Apr 29, 2001 at 05:27:10PM -0600
On Sun, Apr 29, 2001 at 05:27:10PM -0600, Eric W. Biederman wrote:
>
> Do you know if anyone has fixed the lazy vmalloc code? I know of
> as of early 2.4 it was broken on alpha. At the time I noticed it I didn't
> have time to persue it, but before I forget to even put in a bug
> report I thought I'd ask if you know anything about it?
On alpha it's racy if you set CONFIG_ALPHA_LARGE_VMALLOC y (so don't do
that as you don't need it). As long as you use only 1 entry of the pgd
for the whole vmalloc space (CONFIG_ALPHA_LARGE_VMALLOC n) alpha is
safe.
OTOH x86 is racy and there's no workaround available at the moment.
Andrea
next prev parent reply other threads:[~2001-04-29 23:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-27 3:34 Alpha compile problem solved by Andrea (pte_alloc) Magnus Naeslund(f)
2001-04-27 13:52 ` Andrea Arcangeli
2001-04-27 15:02 ` Magnus Naeslund(f)
2001-04-29 23:27 ` Eric W. Biederman
2001-04-29 23:46 ` Andrea Arcangeli [this message]
2001-04-30 3:55 ` Eric W. Biederman
2001-04-30 16:13 ` Andrea Arcangeli
2001-04-30 16:56 ` Alan Cox
2001-04-30 17:07 ` Andrea Arcangeli
2001-04-30 17:40 ` Andrea Arcangeli
2001-05-01 14:38 ` Hubert Mantel
2001-05-01 15:13 ` Alan Cox
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=20010430014653.C923@athlon.random \
--to=andrea@suse.de \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mag@fbab.net \
/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.