From: EunTaik Lee <eun.taik.lee@samsung.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
"vladimir.murzin@arm.com" <vladimir.murzin@arm.com>,
"suzuki.poulose@arm.com" <suzuki.poulose@arm.com>,
"will.deacon@arm.com" <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"salyzyn@android.com" <salyzyn@android.com>,
"riandrews@android.com" <riandrews@android.com>,
"james.morse@arm.com" <james.morse@arm.com>,
"Dave.Martin@arm.com" <Dave.Martin@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Re: [PATCH v2] arm64: add alignment fault hanling
Date: Fri, 19 Feb 2016 09:46:37 +0000 (GMT) [thread overview]
Message-ID: <225030523.1150721455875195200.JavaMail.weblogic@epmlwas08c> (raw)
2016-02-17 2:11 GMT+09:00 Catalin Marinas <catalin.marinas@arm.com>:
> On Tue, Feb 16, 2016 at 04:44:38AM +0000, EunTaik Lee wrote:
>> diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
>> index 19211c4..a5ebb99 100644
>> --- a/arch/arm64/mm/fault.c
>> +++ b/arch/arm64/mm/fault.c
>> @@ -371,6 +371,14 @@ static int __kprobes do_translation_fault(unsigned long addr,
>> return 0;
>> }
>>
>> +static int __kprobes do_alignment_fault(unsigned long addr,
>> + unsigned int esr,
>> + struct pt_regs *regs)
>> +{
>> + do_bad_area(addr, esr, regs);
>> + return 0;
>> +}
>> +
>> /*
>> * This abort handler always returns "fault".
>> */
>> @@ -418,7 +426,7 @@ static struct fault_info {
>> { do_bad, SIGBUS, 0, "synchronous parity error (translation table walk" },
>> { do_bad, SIGBUS, 0, "synchronous parity error (translation table walk" },
>> { do_bad, SIGBUS, 0, "unknown 32" },
>> - { do_bad, SIGBUS, BUS_ADRALN, "alignment fault" },
>> + { do_alignment_fault, SIGBUS, BUS_ADRALN, "alignment fault" },
>
> Do you need a new function, can you not just add do_bad_area in the
> fault_info array?
I made a new function since do_bad_area currently does not return any value.
Should I just make it return an integer instead of making a new function for the
unaligned fault?
Euntaik
reply other threads:[~2016-02-19 9:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=225030523.1150721455875195200.JavaMail.weblogic@epmlwas08c \
--to=eun.taik.lee@samsung.com \
--cc=Dave.Martin@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=riandrews@android.com \
--cc=salyzyn@android.com \
--cc=suzuki.poulose@arm.com \
--cc=vladimir.murzin@arm.com \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®