[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LSU.2.21.1905021341220.16827@pobox.suse.cz>
Date: Thu, 2 May 2019 13:42:20 +0200 (CEST)
From: Miroslav Benes <mbenes@...e.cz>
To: "Tobin C. Harding" <tobin@...nel.org>
cc: Josh Poimboeuf <jpoimboe@...hat.com>,
Jiri Kosina <jikos@...nel.org>, Petr Mladek <pmladek@...e.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Joe Lawrence <joe.lawrence@...hat.com>,
live-patching@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/5] kobject: Add and use init predicate
> Testing
> -------
>
> Kernel build configuration
>
> $ egrep LIVEPATCH .config
> CONFIG_HAVE_LIVEPATCH=y
> CONFIG_LIVEPATCH=y
> CONFIG_TEST_LIVEPATCH=m
>
> $ egrep FTRACE .config
> CONFIG_KPROBES_ON_FTRACE=y
> CONFIG_HAVE_KPROBES_ON_FTRACE=y
> CONFIG_HAVE_DYNAMIC_FTRACE=y
> CONFIG_HAVE_DYNAMIC_FTRACE_WITH_REGS=y
> CONFIG_HAVE_FTRACE_MCOUNT_RECORD=y
> CONFIG_FTRACE=y
> CONFIG_FTRACE_SYSCALLS=y
> CONFIG_DYNAMIC_FTRACE=y
> CONFIG_DYNAMIC_FTRACE_WITH_REGS=y
> CONFIG_FTRACE_MCOUNT_RECORD=y
> # CONFIG_FTRACE_STARTUP_TEST is not set
>
> Builds fine but doesn't boot in Qemu. I've never run dynamic Ftrace, it
> appears to crash during this. Was hoping to run the livepatch tests but
> not sure how to at this moment. Is dynamic Ftrace and livepatch testing
> something that can even be done in a VM or do I need to do this or
> baremetal?
It definitely should work in VM/qemu. We use it like that all the time.
Miroslav
Powered by blists - more mailing lists