mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Punit Agrawal <punit.agrawal@arm.com>
To: Will Deacon <will.deacon@arm.com>
Cc: catalin.marinas@arm.com,
	"Jonathan \(Zhixiong\) Zhang" <zjzhang@codeaurora.org>,
	tbaicar@codeaurora.org, steve.capper@arm.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, manoj.iyer@canonical.com
Subject: Re: [PATCH v2 2/3] arm64: hwpoison: add VM_FAULT_HWPOISON[_LARGE] handling
Date: Wed, 07 Jun 2017 18:47:05 +0100	[thread overview]
Message-ID: <877f0n1yhy.fsf@e105922-lin.cambridge.arm.com> (raw)
In-Reply-To: <20170607135913.GH30263@arm.com> (Will Deacon's message of "Wed, 7 Jun 2017 14:59:13 +0100")

Will Deacon <will.deacon@arm.com> writes:

> On Wed, May 17, 2017 at 04:23:35PM +0100, Punit Agrawal wrote:
>> From: "Jonathan (Zhixiong) Zhang" <zjzhang@codeaurora.org>
>> 
>> Add VM_FAULT_HWPOISON[_LARGE] handling to the arm64 page fault
>> handler. Handling of VM_FAULT_HWPOISON[_LARGE] is very similar
>> to VM_FAULT_OOM, the only difference is that a different si_code
>> (BUS_MCEERR_AR) is passed to user space and si_addr_lsb field is
>> initialized.
>> 
>> Signed-off-by: Jonathan (Zhixiong) Zhang <zjzhang@codeaurora.org>
>> Signed-off-by: Tyler Baicar <tbaicar@codeaurora.org>
>> (fix new __do_user_fault call-site)
>> Signed-off-by: Punit Agrawal <punit.agrawal@arm.com>
>> Acked-by: Steve Capper <steve.capper@arm.com>
>> ---
>>  arch/arm64/mm/fault.c | 22 +++++++++++++++++++---
>>  1 file changed, 19 insertions(+), 3 deletions(-)
>> 
>> diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
>> index 37b95dff0b07..a85b44343ac6 100644
>> --- a/arch/arm64/mm/fault.c
>> +++ b/arch/arm64/mm/fault.c
>> @@ -31,6 +31,7 @@
>>  #include <linux/highmem.h>
>>  #include <linux/perf_event.h>
>>  #include <linux/preempt.h>
>> +#include <linux/hugetlb.h>
>>  
>>  #include <asm/bug.h>
>>  #include <asm/cpufeature.h>
>> @@ -239,10 +240,11 @@ static void __do_kernel_fault(struct mm_struct *mm, unsigned long addr,
>>   */
>>  static void __do_user_fault(struct task_struct *tsk, unsigned long addr,
>>  			    unsigned int esr, unsigned int sig, int code,
>> -			    struct pt_regs *regs)
>> +			    struct pt_regs *regs, int fault)
>>  {
>>  	struct siginfo si;
>>  	const struct fault_info *inf;
>> +	unsigned int lsb = 0;
>>  
>>  	if (unhandled_signal(tsk, sig) && show_unhandled_signals_ratelimited()) {
>>  		inf = esr_to_fault_info(esr);
>> @@ -259,6 +261,17 @@ static void __do_user_fault(struct task_struct *tsk, unsigned long addr,
>>  	si.si_errno = 0;
>>  	si.si_code = code;
>>  	si.si_addr = (void __user *)addr;
>> +	/*
>> +	 * Either small page or large page may be poisoned.
>> +	 * In other words, VM_FAULT_HWPOISON_LARGE and
>> +	 * VM_FAULT_HWPOISON are mutually exclusive.
>> +	 */
>> +	if (fault & VM_FAULT_HWPOISON_LARGE)
>> +		lsb = hstate_index_to_shift(VM_FAULT_GET_HINDEX(fault));
>> +	else if (fault & VM_FAULT_HWPOISON)
>> +		lsb = PAGE_SHIFT;
>> +	si.si_addr_lsb = lsb;
>> +
>
> If we're going to start handling poison faults, then we should probably
> rejig the perf page fault accounting around here so that we follow x86:
>
>   * Always report PERF_COUNT_SW_PAGE_FAULTS,
>   * Don't report anything else for VM_FAULT_ERROR
>   * Report PERF_COUNT_SW_PAGE_FAULTS_MAJ if VM_FAULT_MAJOR
>   * Otherwise, report PERF_COUNT_SW_PAGE_FAULTS_MIN
>
> at the moment, I think you're accounting VM_FAULT_ERROR as
> PERF_COUNT_SW_PAGE_FAULTS_MIN, which doesn't feel right at all.

Ok. I'd missed the implication of enabling poisoned pages fault handling
on the perf accounting. I'll add a patch to update the reporting.

>
> Will

  reply	other threads:[~2017-06-07 17:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-17 15:23 [PATCH v2 0/3] arm64: Add support for handling memory corruption Punit Agrawal
2017-05-17 15:23 ` [PATCH v2 1/3] arm64: hugetlb: Fix huge_pte_offset to return poisoned page table entries Punit Agrawal
2017-06-07 13:47   ` Will Deacon
2017-06-07 14:30     ` Catalin Marinas
2017-06-07 14:57       ` Will Deacon
2017-06-07 15:32         ` Punit Agrawal
2017-06-07 15:41           ` Will Deacon
2017-06-08 16:28             ` Punit Agrawal
2017-06-07 16:54           ` Catalin Marinas
2017-06-07 14:58   ` Catalin Marinas
2017-05-17 15:23 ` [PATCH v2 2/3] arm64: hwpoison: add VM_FAULT_HWPOISON[_LARGE] handling Punit Agrawal
2017-06-07 13:59   ` Will Deacon
2017-06-07 17:47     ` Punit Agrawal [this message]
2017-05-17 15:23 ` [PATCH v2 3/3] arm64: kconfig: allow support for memory failure handling Punit Agrawal
     [not found] ` <1495081650.3981.15@smtp.canonical.com>
2017-05-18 10:27   ` [PATCH v2 0/3] arm64: Add support for handling memory corruption Punit Agrawal

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=877f0n1yhy.fsf@e105922-lin.cambridge.arm.com \
    --to=punit.agrawal@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manoj.iyer@canonical.com \
    --cc=steve.capper@arm.com \
    --cc=tbaicar@codeaurora.org \
    --cc=will.deacon@arm.com \
    --cc=zjzhang@codeaurora.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®