From: Benjamin LaHaise <bcrl@redhat.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: Andrea Arcangeli <andrea@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.10pre13aa1
Date: Sun, 23 Sep 2001 14:28:09 -0400 [thread overview]
Message-ID: <20010923142809.A11346@redhat.com> (raw)
In-Reply-To: <3BADAF6A.8090400@colorfullife.com>
In-Reply-To: <3BADAF6A.8090400@colorfullife.com>; from manfred@colorfullife.com on Sun, Sep 23, 2001 at 11:46:18AM +0200
On Sun, Sep 23, 2001 at 11:46:18AM +0200, Manfred Spraul wrote:
> I don't think that this is a valid argument:
> you are testing on i386 and make design decisions for the architecture
> independant part.
The hook is only needed for x86-like architectures, as all of the risc like
cpus perform the dirty state modification in the page fault handler while
holding the page_table_lock.
> I'd prefer ptep_get_and_clear_and_flush(), then the arch part can do
> what's needed to get the final pte value. (if a single page is modified,
> otherwise the arch can define a suitable mmu_gather)
mmu_gather is the hook. ia64 for instance can create a gather that uses
the hardware tlb flush instruction to shootdown the entry across all cpus
and eliminates the race.
-ben
next prev parent reply other threads:[~2001-09-23 18:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-23 9:46 2.4.10pre13aa1 Manfred Spraul
2001-09-23 14:32 ` 2.4.10pre13aa1 Andrea Arcangeli
2001-09-23 18:28 ` Benjamin LaHaise [this message]
[not found] <20010921095721.A725@athlon.random>
2001-09-21 17:18 ` 2.4.10pre13aa1 Benjamin LaHaise
2001-09-22 7:28 ` 2.4.10pre13aa1 Andrea Arcangeli
2001-09-22 22:39 ` 2.4.10pre13aa1 Benjamin LaHaise
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=20010923142809.A11346@redhat.com \
--to=bcrl@redhat.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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