Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932363AbbBLOIq (ORCPT ); Thu, 12 Feb 2015 09:08:46 -0500 Received: from cantor2.suse.de ([195.135.220.15]:39080 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755858AbbBLOIk (ORCPT ); Thu, 12 Feb 2015 09:08:40 -0500 Date: Thu, 12 Feb 2015 15:08:38 +0100 (CET) From: Jiri Kosina To: Peter Zijlstra cc: Jiri Slaby , Josh Poimboeuf , Ingo Molnar , Masami Hiramatsu , live-patching@vger.kernel.org, linux-kernel@vger.kernel.org, Seth Jennings , Vojtech Pavlik Subject: Re: [RFC PATCH 6/9] livepatch: create per-task consistency model In-Reply-To: <20150212133540.GZ23123@twins.programming.kicks-ass.net> Message-ID: References: <2c3d1e685dae5cccc2dfdb1b24c241b2f1c89348.1423499826.git.jpoimboe@redhat.com> <20150212032121.GA18578@treble.redhat.com> <20150212115628.GL2896@worktop.programming.kicks-ass.net> <20150212125149.GB18578@treble.redhat.com> <20150212130817.GV23123@twins.programming.kicks-ass.net> <54DCA7AC.3080602@suse.cz> <20150212133540.GZ23123@twins.programming.kicks-ass.net> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1349 Lines: 36 On Thu, 12 Feb 2015, Peter Zijlstra wrote: > > > And what's wrong with using known good spots like the freezer? > > > > This was already discussed too. Please STA. > > WTF is STA? You guys want something from me; I don't have time, not > inclination to go hunt down whatever dark corner of the interweb > contains your ramblings. > > If you can't be arsed to explain things, I certainly cannot be arsed to > consider your request. I believe I have provided answer to the freezer question in my previous mail, so please let's continue the discussion there if needed. > So you now have my full NAK on touching the scheduler, have at it, go > deal with someone else. I personally am not a big fan of the task_rq_lock() public exposure either. What might be generally useful though (not only for livepatching) would be an API that would allow for "safe" stack dump (where "safe" means that guarantee, that it wouldn't be interferred by process waking up in the middle of dumping, would be provided). Does that sound like even remotely acceptable idea to you? Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/