From: Mahesh Jagannath Salgaonkar <mahesh@linux.vnet.ibm.com>
To: Michael Ellerman <patch-notifications@ellerman.id.au>,
linuxppc-dev <linuxppc-dev@ozlabs.org>
Cc: syzkaller@googlegroups.com, Paul Mackerras <paulus@samba.org>,
Nicholas Piggin <npiggin@gmail.com>,
Andrew Donnellan <andonnel@au1.ibm.com>
Subject: Re: Disable kcov for slb routines.
Date: Fri, 15 Mar 2019 10:31:25 +0530 [thread overview]
Message-ID: <3e0bd37b-5e34-f056-250c-c36bd495ea94@linux.vnet.ibm.com> (raw)
In-Reply-To: <44Kn0q0xN3z9s71@ozlabs.org>
On 3/14/19 5:13 PM, Michael Ellerman wrote:
> On Mon, 2019-03-04 at 08:25:51 UTC, Mahesh J Salgaonkar wrote:
>> From: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
>>
>> The kcov instrumentation inside SLB routines causes duplicate SLB entries
>> to be added resulting into SLB multihit machine checks.
>> Disable kcov instrumentation on slb.o
>>
>> Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
>> Acked-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
>> Tested-by: Satheesh Rajendran <sathnaga@linux.vent.ibm.com>
>
> Applied to powerpc next, thanks.
>
> https://git.kernel.org/powerpc/c/19d6907521b04206676741b26e05a152
>
> cheers
>
There was a v2 at http://patchwork.ozlabs.org/patch/1051718/, looks like
v1 got picked up. But I see the applied commit does address Andrew's
comments.
Thanks,
-Mahesh.
next prev parent reply other threads:[~2019-03-15 5:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 8:25 [PATCH] Disable kcov for slb routines Mahesh J Salgaonkar
2019-03-05 3:31 ` Andrew Donnellan
2019-03-07 4:37 ` Satheesh Rajendran
2019-03-14 11:43 ` Michael Ellerman
2019-03-15 5:01 ` Mahesh Jagannath Salgaonkar [this message]
2019-03-20 12:51 ` Michael Ellerman
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=3e0bd37b-5e34-f056-250c-c36bd495ea94@linux.vnet.ibm.com \
--to=mahesh@linux.vnet.ibm.com \
--cc=andonnel@au1.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=npiggin@gmail.com \
--cc=patch-notifications@ellerman.id.au \
--cc=paulus@samba.org \
--cc=syzkaller@googlegroups.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;
as well as URLs for NNTP newsgroup(s).