| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 4 Dec 2015 10:01:50 +0100 From: Torsten Duwe <duwe@....de> To: Petr Mladek <pmladek@...e.com> Cc: Steven Rostedt <rostedt@...dmis.org>, Michael Ellerman <mpe@...erman.id.au>, Jiri Kosina <jkosina@...e.cz>, linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org, live-patching@...r.kernel.org Subject: Re: [PATCH v4 4/9] ppc64 ftrace_with_regs configuration variables On Thu, Dec 03, 2015 at 05:20:08PM +0100, Petr Mladek wrote: > > IMHO, we should not define CC_USING_MPROFILE_KERNEL if it is not > supported by the compiler. Yes, true. > I took inspiration from the CC_USING_FENTRY handling in > linux/Makefile. The following code worked for me: > > CC_USING_MPROFILE_KERNEL := $(call cc-option, -pg -mprofile-kernel -DCC_USING_MPROFILE_KERNEL) > CC_FLAGS_FTRACE := $(CC_USING_MPROFILE_KERNEL) > KBUILD_CPPFLAGS += $(CC_USING_MPROFILE_KERNEL) Excellent! > I just do not understand why we need to add the flags also > to KBUILD_CPPFLAGS. It seems that they are duplicated > when compiling kernel/livepatch/core.o. But livepatching > did not work without it. I wonder if you found the culprit. Some assembler-with-cpp files also need to be notified? My plan is to first get this working reliably and then fine tune. Torsten -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists