From: Andrea Arcangeli <andrea@novell.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ptep_establish/establish_pte needs set_pte_atomic and all set_pte must be written in asm
Date: Sun, 26 Sep 2004 17:41:37 +0200 [thread overview]
Message-ID: <20040926154137.GW3309@dualathlon.random> (raw)
In-Reply-To: <228130000.1096209711@[10.10.2.4]>
On Sun, Sep 26, 2004 at 07:41:52AM -0700, Martin J. Bligh wrote:
> Wouldn't it make sense to call set_pte_atomic, and just have that resolve
> to set_pte on 90% of arches? (I'm ignoring the wierdo compiler issue here,
> this is just for arches with pte > long).
I also like this more, since it betters defines that set_pte really
cannot be called on an established pte in common code [i.e. the bug
triggering on x86] (and asm-generic is common code).
next prev parent reply other threads:[~2004-09-26 15:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 15:54 ptep_establish/establish_pte needs set_pte_atomic and all set_pte must be written in asm Andrea Arcangeli
2004-09-25 23:33 ` Benjamin Herrenschmidt
2004-09-26 0:20 ` Andrea Arcangeli
2004-09-26 0:31 ` Rik van Riel
2004-09-26 0:46 ` Andrea Arcangeli
2004-09-26 0:59 ` Benjamin Herrenschmidt
2004-09-26 1:36 ` Andrea Arcangeli
2004-09-26 5:31 ` Benjamin Herrenschmidt
2004-09-26 20:30 ` Paul Mackerras
[not found] ` <20040926203640.GR2499@dualathlon.random>
2004-09-27 16:41 ` Andrea Arcangeli
2004-09-28 9:12 ` Pavel Machek
2004-09-26 0:44 ` Benjamin Herrenschmidt
2004-09-26 1:32 ` Andrea Arcangeli
2004-09-26 5:29 ` Benjamin Herrenschmidt
2004-09-26 15:39 ` Andrea Arcangeli
2004-09-26 14:41 ` Martin J. Bligh
2004-09-26 15:41 ` Andrea Arcangeli [this message]
2004-09-25 23:44 ` Rik van Riel
2004-09-26 0:31 ` Andrea Arcangeli
2004-09-26 0:37 ` Rik van Riel
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=20040926154137.GW3309@dualathlon.random \
--to=andrea@novell.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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