[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171016133530.fhspouznccpprjc6@lakrids.cambridge.arm.com>
Date: Mon, 16 Oct 2017 14:35:31 +0100
From: Mark Rutland <mark.rutland@....com>
To: linux-arm-kernel@...ts.infradead.org, marc.zyngier@....com
Cc: linux-kernel@...r.kernel.org, adech.fo@...il.com,
aryabinin@...tuozzo.com, catalin.marinas@....com,
christoffer.dall@...aro.org, dvyukov@...gle.com,
linux-kbuild@...r.kernel.org, will.deacon@....com,
yamada.masahiro@...ionext.com
Subject: Re: [PATCH 0/4] Cleanup instrumentation avoidance
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
>
Powered by blists - more mailing lists