From: Joe Perches <joe@perches.com>
To: Kautuk Consul <consul.kautuk@gmail.com>
Cc: davem@davemloft.net,
Paul Gortmaker <paul.gortmaker@windriver.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 20/20 v3] sparc/mm/fault_64.c: Port OOM changes to do_sparc64_fault
Date: Mon, 26 Mar 2012 09:31:24 -0700 [thread overview]
Message-ID: <1332779484.6160.95.camel@joe2Laptop> (raw)
In-Reply-To: <1332775997-2197-1-git-send-email-consul.kautuk@gmail.com>
On Mon, 2012-03-26 at 11:33 -0400, Kautuk Consul wrote:
> diff --git a/arch/sparc/mm/fault_64.c b/arch/sparc/mm/fault_64.c
> index 504c062..8322962 100644
> --- a/arch/sparc/mm/fault_64.c
> +++ b/arch/sparc/mm/fault_64.c
> @@ -279,6 +279,7 @@ asmlinkage void __kprobes do_sparc64_fault(struct pt_regs *regs)
> unsigned int insn = 0;
> int si_code, fault_code, fault;
> unsigned long address, mm_rss;
> + unsigned int flags = FAULT_FLAG_ALLOW_RETRY | FAULT_FLAG_KILLABLE;
>
> fault_code = get_thread_fault_code();
>
[]
> @@ -423,7 +426,13 @@ good_area:
> goto bad_area;
> }
>
> - fault = handle_mm_fault(mm, vma, address, (fault_code & FAULT_CODE_WRITE) ? FAULT_FLAG_WRITE : 0);
> + fault = handle_mm_fault(mm, vma, address,
> + flags | ((fault_code & FAULT_CODE_WRITE) ?
> + FAULT_FLAG_WRITE : 0);
A bit redundant and very poor style argument alignment
Make sure your tab indentation is set to 8.
fault = handle_mm_fault(mm, vma, address,
flags | (fault_code & FAULT_CODE_WRITE));
though perhaps fault_code could be unsigned and
perhaps you could use the same style initializer
for fault_code as patch 19/20.
next prev parent reply other threads:[~2012-03-26 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 15:33 Kautuk Consul
2012-03-26 16:31 ` Joe Perches [this message]
2012-03-26 16:50 ` Kautuk Consul
2012-03-26 20:11 ` David Miller
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=1332779484.6160.95.camel@joe2Laptop \
--to=joe@perches.com \
--cc=a.p.zijlstra@chello.nl \
--cc=consul.kautuk@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paul.gortmaker@windriver.com \
--cc=sparclinux@vger.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
all inboxes | Powered by JetHome®