From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: "Tom \"spot\" Callaway" <tcallawa@redhat.com>,
David Miller <davem@davemloft.net>,
akpm@linux-foundation.org, mark@mtfhpc.demon.co.uk,
linuxppc-dev@ozlabs.org, wli@holomorphy.com, linux-mm@kvack.org,
andrea@suse.de, sparclinux@vger.kernel.org
Subject: Re: [PATCH/RFC] Rework ptep_set_access_flags and fix sun4c
Date: Wed, 23 May 2007 08:59:08 +1000 [thread overview]
Message-ID: <1179874748.32247.868.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0705221738020.22822@blonde.wat.veritas.com>
> Looks pretty good to me.
>
> There was a minor build error in x86 (see below), and ia64 is missing
> (again see below). I've now built and am running this on x86, x86_64
> and powerpc64; but I'm very unlikely to be doing anything which
> actually tickles these changes, or Andrea's original handle_pte_fault
> optimization.
Ok.
> Would the "__changed && __dirty" architectures (x86, x86_64, ia64)
> be better off saying __changed = __dirty && pte_same? I doubt it's
> worth bothering about.
I'd say let gcc figure it out :-)
> You've updated do_wp_page to do "if (ptep_set_access_flags(...",
> but not updated set_huge_ptep_writable in the same way: I'd have
> thought you'd either leave both alone, or update them both: any
> reason for one not the other? But again, not really an issue.
Nah, I must have missed set_huge_ptep_writable(). I don't think the wp
code path matters much anyway, it's likely to always be different.
> These changes came about because the sun4c needs to update_mmu_cache
> even in the pte_same case: might it also need to flush_tlb_page then?
Well, I don't know which is why I'm waiting for Tom Callaway to test.
Davem mentioned update_mmu_cache only though when we discussed the
problem initially.
> > #define __HAVE_ARCH_PTEP_SET_ACCESS_FLAGS
> > #define ptep_set_access_flags(vma, address, ptep, entry, dirty) \
> > -do { \
> > - if (dirty) { \
> > +({ \
> > + int __changed = !pte_same(*(__ptep), __entry); \
>
> That just needs to be:
>
> + int __changed = !pte_same(*(ptep), entry); \
Ah yes, sorry about that. I need to setup an x86 toolchain somewhere :-)
> Here's what I think the ia64 hunk would be, unbuilt and untested.
Ok.
I'll respin a patch later today.
Cheers,
Ben.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-05-22 22:59 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.0704291345480.690@mtfhpc.demon.co.uk>
[not found] ` <1177852457.4390.26.camel@localhost.localdomain>
[not found] ` <Pine.LNX.4.61.0704302159140.3178@mtfhpc.demon.co.uk>
2007-04-30 21:54 ` vm changes from linux-2.6.14 to linux-2.6.15 Andrew Morton
2007-04-30 22:04 ` David Miller, Andrew Morton
2007-04-30 22:33 ` Mark Fortescue
2007-04-30 22:42 ` David Miller, Mark Fortescue
2007-05-01 0:00 ` Benjamin Herrenschmidt
2007-05-01 0:38 ` David Miller, Benjamin Herrenschmidt
2007-05-01 1:45 ` Mark Fortescue
2007-05-01 2:05 ` Benjamin Herrenschmidt
2007-05-01 13:58 ` Mark Fortescue
2007-05-01 21:31 ` Benjamin Herrenschmidt
2007-05-01 23:08 ` Mark Fortescue
2007-05-09 19:44 ` Mark Fortescue
2007-05-09 22:48 ` Benjamin Herrenschmidt
2007-05-10 6:19 ` Andrew Morton
2007-05-10 6:29 ` Benjamin Herrenschmidt
2007-05-10 7:12 ` David Miller, Benjamin Herrenschmidt
2007-05-14 19:19 ` Hugh Dickins
2007-05-14 21:07 ` Benjamin Herrenschmidt
2007-05-15 6:56 ` Benjamin Herrenschmidt
2007-05-21 14:27 ` Tom "spot" Callaway
2007-05-21 22:09 ` Benjamin Herrenschmidt
2007-05-22 6:28 ` [PATCH/RFC] Rework ptep_set_access_flags and fix sun4c Benjamin Herrenschmidt
2007-05-22 17:04 ` Hugh Dickins
2007-05-22 22:59 ` Benjamin Herrenschmidt [this message]
2007-05-22 23:04 ` Tom "spot" Callaway
2007-05-23 4:03 ` Hugh Dickins
2007-05-23 4:21 ` Benjamin Herrenschmidt
2007-05-22 21:52 ` Mark Fortescue
2007-05-22 21:53 ` David Miller, Mark Fortescue
2007-05-22 23:29 ` Benjamin Herrenschmidt
2007-05-22 23:28 ` Benjamin Herrenschmidt
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=1179874748.32247.868.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=andrea@suse.de \
--cc=davem@davemloft.net \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mark@mtfhpc.demon.co.uk \
--cc=sparclinux@vger.kernel.org \
--cc=tcallawa@redhat.com \
--cc=wli@holomorphy.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