From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Seth Jennings <sjenning@redhat.com>
Cc: Josh Poimboeuf <jpoimboe@redhat.com>,
Jiri Kosina <jkosina@suse.cz>, Vojtech Pavlik <vojtech@suse.cz>,
Steven Rostedt <rostedt@goodmis.org>,
Petr Mladek <pmladek@suse.cz>, Miroslav Benes <mbenes@suse.cz>,
Christoph Hellwig <hch@infradead.org>,
Greg KH <gregkh@linuxfoundation.org>,
Andy Lutomirski <luto@amacapital.net>,
live-patching@vger.kernel.org, x86@kernel.org, kpatch@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3 3/3] kernel: add sysfs documentation for live patching
Date: Fri, 21 Nov 2014 11:49:46 +0900 [thread overview]
Message-ID: <546EA84A.5070607@hitachi.com> (raw)
In-Reply-To: <1416522580-5593-4-git-send-email-sjenning@redhat.com>
(2014/11/21 7:29), Seth Jennings wrote:
> Adds sysfs interface documentation to Documentation/ABI/testing/
>
Hmm, is there any reason to decouple this documentation from code patch?
I think we'd better merge this to 2/3, or move sysfs interface code from 2/3 to this.
Thank you,
> Signed-off-by: Seth Jennings <sjenning@redhat.com>
> ---
> Documentation/ABI/testing/sysfs-kernel-livepatch | 44 ++++++++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 45 insertions(+)
> create mode 100644 Documentation/ABI/testing/sysfs-kernel-livepatch
>
> diff --git a/Documentation/ABI/testing/sysfs-kernel-livepatch b/Documentation/ABI/testing/sysfs-kernel-livepatch
> new file mode 100644
> index 0000000..5bf42a8
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-kernel-livepatch
> @@ -0,0 +1,44 @@
> +What: /sys/kernel/livepatch
> +Date: Nov 2014
> +KernelVersion: 3.19.0
> +Contact: live-patching@vger.kernel.org
> +Description:
> + Interface for kernel live patching
> +
> + The /sys/kernel/livepatch directory contains subdirectories for
> + each loaded live patch module.
> +
> +What: /sys/kernel/livepatch/<patch>
> +Date: Nov 2014
> +KernelVersion: 3.19.0
> +Contact: live-patching@vger.kernel.org
> +Description:
> + The patch directory contains subdirectories for each kernel
> + object (vmlinux or a module) in which it patched functions.
> +
> +What: /sys/kernel/livepatch/<patch>/enabled
> +Date: Nov 2014
> +KernelVersion: 3.19.0
> +Contact: live-patching@vger.kernel.org
> +Description:
> + A writable attribute that indicates whether the patched
> + code is currently applied. Writing 0 will disable the patch
> + while writing 1 will re-enable the patch.
> +
> +What: /sys/kernel/livepatch/<patch>/<object>
> +Date: Nov 2014
> +KernelVersion: 3.19.0
> +Contact: live-patching@vger.kernel.org
> +Description:
> + The object directory contains subdirectories for each function
> + that is patched within the object.
> +
> +What: /sys/kernel/livepatch/<patch>/<object>/<function>
> +Date: Nov 2014
> +KernelVersion: 3.19.0
> +Contact: live-patching@vger.kernel.org
> +Description:
> + The function directory contains attributes regarding the
> + properties and state of the patched function.
> +
> + There are currently no such attributes.
> diff --git a/MAINTAINERS b/MAINTAINERS
> index c7f49ae..7985293 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5725,6 +5725,7 @@ F: kernel/livepatch/
> F: include/linux/livepatch.h
> F: arch/x86/include/asm/livepatch.h
> F: arch/x86/kernel/livepatch.c
> +F: Documentation/ABI/testing/sysfs-kernel-livepatch
> L: live-patching@vger.kernel.org
>
> LLC (802.2)
>
--
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2014-11-21 2:49 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 22:29 [PATCHv3 0/3] Kernel Live Patching Seth Jennings
2014-11-20 22:29 ` [PATCHv3 1/3] kernel: add TAINT_LIVEPATCH Seth Jennings
2014-11-20 22:29 ` [PATCHv3 2/3] kernel: add support for live patching Seth Jennings
2014-11-21 0:22 ` Jiri Kosina
2014-11-21 14:44 ` Miroslav Benes
2014-11-21 15:00 ` Josh Poimboeuf
2014-11-21 15:46 ` Miroslav Benes
2014-11-21 16:13 ` Seth Jennings
2014-11-21 15:21 ` Josh Poimboeuf
2014-11-21 15:27 ` Jiri Kosina
2014-11-21 15:35 ` Josh Poimboeuf
2014-11-21 16:40 ` Seth Jennings
2014-11-21 17:35 ` Jiri Slaby
2014-11-21 18:29 ` Seth Jennings
2014-11-21 17:53 ` Andy Lutomirski
2014-11-21 2:39 ` Masami Hiramatsu
2014-11-25 16:39 ` Petr Mladek
2014-11-25 16:52 ` Steven Rostedt
2014-11-25 17:04 ` Petr Mladek
2014-11-25 17:16 ` Steven Rostedt
2014-11-25 19:29 ` Jiri Kosina
2014-12-03 8:09 ` Masami Hiramatsu
2014-11-24 11:13 ` Thomas Gleixner
2014-11-24 13:21 ` Jiri Kosina
2014-11-24 13:26 ` Thomas Gleixner
2014-11-24 13:31 ` Vojtech Pavlik
2014-11-24 14:25 ` Masami Hiramatsu
2014-11-24 13:31 ` Jiri Kosina
2014-11-24 13:23 ` Vojtech Pavlik
2014-11-24 13:24 ` Josh Poimboeuf
2014-11-24 13:27 ` Masami Hiramatsu
2014-11-20 22:29 ` [PATCHv3 3/3] kernel: add sysfs documentation " Seth Jennings
2014-11-21 2:49 ` Masami Hiramatsu [this message]
2014-11-21 16:41 ` Seth Jennings
2014-11-21 2:44 ` [PATCHv3 0/3] Kernel Live Patching Masami Hiramatsu
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=546EA84A.5070607@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jkosina@suse.cz \
--cc=jpoimboe@redhat.com \
--cc=kpatch@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mbenes@suse.cz \
--cc=pmladek@suse.cz \
--cc=rostedt@goodmis.org \
--cc=sjenning@redhat.com \
--cc=vojtech@suse.cz \
--cc=x86@kernel.org \
/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
Powered by JetHome