mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: linux-arm-kernel@lists.infradead.org, marc.zyngier@arm.com
Cc: linux-kernel@vger.kernel.org, adech.fo@gmail.com,
	aryabinin@virtuozzo.com, catalin.marinas@arm.com,
	christoffer.dall@linaro.org, dvyukov@google.com,
	linux-kbuild@vger.kernel.org, will.deacon@arm.com,
	yamada.masahiro@socionext.com
Subject: Re: [PATCH 0/4] Cleanup instrumentation avoidance
Date: Mon, 16 Oct 2017 14:35:31 +0100	[thread overview]
Message-ID: <20171016133530.fhspouznccpprjc6@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <20171016132440.38098-1-mark.rutland@arm.com>

Sorry Marc, I somehow typo'd your name when sending this out...

Mark.

On Mon, Oct 16, 2017 at 02:24:36PM +0100, Mark Rutland wrote:
> Recently we spotted that some code with special ABI requirements was
> being instrumented by KCOV [1], and we need to avoid all instrumentation
> in this case.
> 
> While it's possible to disable each instrumentation option manually,
> this is tedious and error prone as new options are introduced.
> 
> This series adds a new CC_INSTRUMENT option which can be used to disable
> all instrumentation of a given file or directory, and makes use of this
> throught arm64.
> 
> There are other places where this could be used (e.g. the EFI stub), but
> I've avoided altering those for now in the hope that this can be taken
> via the arm64 tree.
> 
> Thanks,
> Mark.
> 
> [1] http://lists.infradead.org/pipermail/linux-arm-kernel/2017-September/533105.html
> 
> Mark Rutland (4):
>   kbuild: allow global override of CC instrumentation
>   arm64: prevent instrumentation of LL/SC atomics
>   kvm/arm64: simplify CC instrumentation opt-out
>   arm64: vdso: remove pointless gcov option
> 
>  arch/arm64/kernel/vdso/Makefile |  3 ---
>  arch/arm64/kvm/hyp/Makefile     |  5 +----
>  arch/arm64/lib/Makefile         |  1 +
>  scripts/Makefile.lib            | 17 +++++++++++++----
>  4 files changed, 15 insertions(+), 11 deletions(-)
> 
> -- 
> 2.11.0
> 

      parent reply	other threads:[~2017-10-16 13:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16 13:24 Mark Rutland
2017-10-16 13:24 ` [PATCH 1/4] kbuild: allow global override of CC instrumentation Mark Rutland
2017-10-17 10:37   ` Will Deacon
2017-10-16 13:24 ` [PATCH 2/4] arm64: prevent instrumentation of LL/SC atomics Mark Rutland
2017-10-17 10:03   ` Will Deacon
2017-10-17 10:54     ` Mark Rutland
2017-10-17 10:58       ` Will Deacon
2017-10-17 11:10         ` Mark Rutland
2017-10-17 11:38           ` Will Deacon
2017-10-17 12:55             ` Mark Rutland
2017-10-18 14:16               ` Will Deacon
2017-10-16 13:24 ` [PATCH 3/4] kvm/arm64: simplify CC instrumentation opt-out Mark Rutland
2017-10-17 14:50   ` Christoffer Dall
2017-10-16 13:24 ` [PATCH 4/4] arm64: vdso: remove pointless gcov option Mark Rutland
2017-10-17 13:56   ` Mark Rutland
2017-10-16 13:35 ` Mark Rutland [this message]

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=20171016133530.fhspouznccpprjc6@lakrids.cambridge.arm.com \
    --to=mark.rutland@arm.com \
    --cc=adech.fo@gmail.com \
    --cc=aryabinin@virtuozzo.com \
    --cc=catalin.marinas@arm.com \
    --cc=christoffer.dall@linaro.org \
    --cc=dvyukov@google.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=will.deacon@arm.com \
    --cc=yamada.masahiro@socionext.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®