From: Andrea Arcangeli <andrea@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
"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 19:07:47 +0200 [thread overview]
Message-ID: <20010430190747.C19620@athlon.random> (raw)
In-Reply-To: <20010430014653.C923@athlon.random> <E14uGya-0008He-00@the-village.bc.nu>
In-Reply-To: <E14uGya-0008He-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Apr 30, 2001 at 05:56:41PM +0100
On Mon, Apr 30, 2001 at 05:56:41PM +0100, Alan Cox wrote:
> > 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.
>
> Its racy for all cases on the Alpha because the exception table fixes are
> not done.
you're talking about the module races, I was only talking only about
vmalloc lazy pgd mapping, they're different things even if they are
both related to the page fault hanlder.
I don't use modules on the alpha so...
> > OTOH x86 is racy and there's no workaround available at the moment.
>
> -ac fixes all known problems there
I will check that shortly, thanks. (so far all the fixes I seen floating
around for such races were wrong)
Andrea
next prev parent reply other threads:[~2001-04-30 17:09 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
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 [this message]
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=20010430190747.C19620@athlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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.