Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S933365AbcDFIQE (ORCPT <rfc822;w@1wt.eu>);
	Wed, 6 Apr 2016 04:16:04 -0400
Received: from mx2.suse.de ([195.135.220.15]:56808 "EHLO mx2.suse.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S932760AbcDFIQA (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 6 Apr 2016 04:16:00 -0400
Date: Wed, 6 Apr 2016 10:15:57 +0200
From: Petr Mladek <pmladek@suse.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: Jiri Kosina <jikos@kernel.org>, Jessica Yu <jeyu@redhat.com>,
        Miroslav Benes <mbenes@suse.cz>, linux-kernel@vger.kernel.org,
        live-patching@vger.kernel.org, Vojtech Pavlik <vojtech@suse.com>
Subject: Re: [RFC PATCH v1.9 00/14] livepatch: hybrid consistency model
Message-ID: <20160406081557.GD18968@pathway.suse.cz>
References: <cover.1458933243.git.jpoimboe@redhat.com>
 <20160401133944.GQ5522@pathway.suse.cz>
 <20160405134430.q4pqm2oalivjka4s@treble.redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160405134430.q4pqm2oalivjka4s@treble.redhat.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 919
Lines: 20

On Tue 2016-04-05 08:44:30, Josh Poimboeuf wrote:
> On Fri, Apr 01, 2016 at 03:39:44PM +0200, Petr Mladek wrote:
> > On Fri 2016-03-25 14:34:47, Josh Poimboeuf wrote:
> > > - update documentation for sysfs, proc, livepatch
> > 
> > Also we should publish somewhere the information about TIF_KLP_NEED_UPDATE
> > flag, e.g. /proc/<pid>/klp_need_update. It is handy to see what
> > process blocks the transition. We have something similar in
> > kGraft, see in_progress_show() at
> > https://git.kernel.org/cgit/linux/kernel/git/jirislaby/kgraft.git/commit/?h=kgraft-4.4&id=1c82fbd7b1fe240f4ed178a6506a93033f6a4bed
> 
> Patch 13/14 exposes the per-task patched state in /proc, so I think that
> already does what you're asking for?  It doesn't expose
> TIF_KLP_NEED_UPDATE, but that's more of an internal detail I think.

Heh, I have missed it. Yup, the per-thread patch state info seems to
be enough.

Best Regards,
Petr