From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: npiggin@suse.de, mingo@elte.hu, linux-arch@vger.kernel.org,
rusty@rustcorp.com.au, travis@sgi.com,
linux-kernel@vger.kernel.org, venkatesh.pallipadi@intel.com,
suresh.b.siddha@intel.com, arjan@infradead.org, hpa@zytor.com,
tglx@linutronix.de, Ying Han <yinghan@google.com>,
Mike Waychison <mikew@google.com>
Subject: Re: [git pull] cpus4096 tree, part 3
Date: Mon, 26 Jan 2009 11:30:26 -0800 [thread overview]
Message-ID: <20090126113026.4d9682e3.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0901261107280.5284@localhost.localdomain>
On Mon, 26 Jan 2009 11:09:59 -0800 (PST)
Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>
> On Mon, 26 Jan 2009, Andrew Morton wrote:
> > > + write = error_code & PF_WRITE;
> >
> > What's going on here? We set `error_code' to PF_WRITE, which is some
> > x86-specific thing.
>
> No. We set "write" to non-zero if it was a write fault.
>
> > > fault = handle_mm_fault(mm, vma, address, write);
> >
> > and then pass it into handle_mm_fault(), which is expecting a bunch of
> > flags in the FAULT_FLAG_foo domain.
>
> No. "handle_mm_fault()" takes an integer that is non-zero if it's a write,
> zero if it's a read. That's how it has _always_ worked.
>
> I don't see where you find that FAULT_FLAG_foo thing. That's much deeper
> down, when people do things like
>
> unsigned int flags = FAULT_FLAG_NONLINEAR |
> (write_access ? FAULT_FLAG_WRITE : 0);
>
> based on that whole "write_access" flag.
>
OK, thanks. It's actually page_fault-retry-with-nopage_retry.patch
which got those things confused, and then confused me. I'll go address
that in the other thread..
next prev parent reply other threads:[~2009-01-26 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.00.0901021149020.5086@localhost.localdomain>
[not found] ` <20090102203839.GA26850@elte.hu>
[not found] ` <alpine.LFD.2.00.0901021531140.3179@localhost.localdomain>
[not found] ` <20090103193859.GB9805@elte.hu>
[not found] ` <alpine.LFD.2.00.0901031225020.3179@localhost.localdomain>
[not found] ` <20090103203621.GA2491@elte.hu>
[not found] ` <20090103213856.GA24138@elte.hu>
[not found] ` <alpine.LFD.2.00.0901031347570.3179@localhost.localdomain>
[not found] ` <20090103223723.GA17047@elte.hu>
[not found] ` <20090105011416.GG32239@wotan.suse.de>
2009-01-05 1:16 ` [git pull] cpus4096 tree, part 3 Nick Piggin
2009-01-26 19:00 ` Andrew Morton
2009-01-26 19:09 ` Linus Torvalds
2009-01-26 19:30 ` Andrew Morton [this message]
2009-01-26 20:09 ` Ingo Molnar
2009-01-26 20:44 ` Andrew Morton
[not found] ` <604427e00901261312w23a1f0f5y61fc5c6cc70297fb@mail.gmail.com>
2009-01-26 23:21 ` Ingo Molnar
2009-01-26 23:44 ` Andrew Morton
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=20090126113026.4d9682e3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikew@google.com \
--cc=mingo@elte.hu \
--cc=npiggin@suse.de \
--cc=rusty@rustcorp.com.au \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=travis@sgi.com \
--cc=venkatesh.pallipadi@intel.com \
--cc=yinghan@google.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