From: Dave Hansen <dave.hansen@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, sean.j.christopherson@intel.com,
tglx@linutronix.de, x86@kernel.org, luto@kernel.org
Subject: Re: [RFC][PATCH 3/8] x86/mm: break out user address space handling
Date: Mon, 10 Sep 2018 13:20:06 -0700 [thread overview]
Message-ID: <029066e3-68e9-c6be-add2-a13b1c424818@linux.intel.com> (raw)
In-Reply-To: <20180908093805.GO24082@hirez.programming.kicks-ass.net>
On 09/08/2018 02:38 AM, Peter Zijlstra wrote:
>> + /* Was the fault on kernel-controlled part of the address space? */
>> + if (unlikely(fault_in_kernel_space(address)))
>> + do_kern_addr_space_fault(regs, hw_error_code, address);
>> + else
>> + do_user_addr_space_fault(regs, hw_error_code, address);
>> +}
> How about: do_{user,kernel}_fault() ? That _addr_space_ is just a lot of
> typing for no real benefit imo.
Yeah, totally, the names are long.
I was just trying to make it obvious to differentiate address space from
*mode* when the fault occurred. I can probably do that in comments
instead, though.
next prev parent reply other threads:[~2018-09-10 20:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 19:48 [RFC][PATCH 0/8] x86/mm: page fault handling cleanups Dave Hansen
2018-09-07 19:48 ` [RFC][PATCH 1/8] x86/mm: clarify hardware vs. software "error_code" Dave Hansen
2018-09-07 22:48 ` Andy Lutomirski
2018-09-10 20:07 ` Dave Hansen
2018-09-10 21:17 ` Andy Lutomirski
2018-09-07 19:48 ` [RFC][PATCH 2/8] x86/mm: break out kernel address space handling Dave Hansen
2018-09-07 21:06 ` Sean Christopherson
2018-09-07 21:51 ` Dave Hansen
2018-09-07 22:21 ` Andy Lutomirski
2018-09-07 22:37 ` Dave Hansen
2018-09-07 19:48 ` [RFC][PATCH 3/8] x86/mm: break out user " Dave Hansen
2018-09-08 9:38 ` Peter Zijlstra
2018-09-10 20:20 ` Dave Hansen [this message]
2018-09-07 19:48 ` [RFC][PATCH 4/8] x86/mm: add clarifying comments for user addr space Dave Hansen
2018-09-07 19:49 ` [RFC][PATCH 5/8] x86/mm: fix exception table comments Dave Hansen
2018-09-07 21:04 ` Sean Christopherson
2018-09-07 21:51 ` Dave Hansen
2018-09-10 20:43 ` Sean Christopherson
2018-09-08 0:37 ` Jann Horn
2018-09-07 19:49 ` [RFC][PATCH 6/8] x86/mm: add vsyscall address helper Dave Hansen
2018-09-08 0:46 ` Jann Horn
2018-09-07 19:49 ` [RFC][PATCH 7/8] x86/mm/vsyscall: consider vsyscall page part of user address space Dave Hansen
2018-09-07 22:58 ` Andy Lutomirski
2018-09-08 1:16 ` Jann Horn
2018-09-07 19:49 ` [RFC][PATCH 8/8] x86/mm: remove spurious fault pkey check Dave Hansen
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=029066e3-68e9-c6be-add2-a13b1c424818@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=sean.j.christopherson@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).