From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752514AbbCWNes (ORCPT ); Mon, 23 Mar 2015 09:34:48 -0400 Received: from mail-wi0-f179.google.com ([209.85.212.179]:36725 "EHLO mail-wi0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752221AbbCWNer (ORCPT ); Mon, 23 Mar 2015 09:34:47 -0400 Date: Mon, 23 Mar 2015 14:34:42 +0100 From: Ingo Molnar To: Steven Rostedt Cc: Petr Mladek , Masami Hiramatsu , "David S. Miller" , Anil S Keshavamurthy , Ananth NMavinakayanahalli , Frederic Weisbecker , Ingo Molnar , Jiri Kosina , linux-kernel@vger.kernel.org Subject: Re: [PATCH v3] kprobes: Disable Kprobe when ftrace arming fails Message-ID: <20150323133442.GC23145@gmail.com> References: <1426860127-7896-1-git-send-email-pmladek@suse.cz> <20150323085426.GB28965@gmail.com> <20150323101253.GN11869@pathway.suse.cz> <20150323103327.GA12213@gmail.com> <20150323123955.GE15177@pathway.suse.cz> <20150323093013.15b6070b@gandalf.local.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150323093013.15b6070b@gandalf.local.home> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Steven Rostedt wrote: > On Mon, 23 Mar 2015 13:39:55 +0100 > Petr Mladek wrote: > > > > > wth is a 'universe' in this context? > > > > We use the term "universe" to define whether the system or task uses > > original or patched functions. It is especially important for patches > > that modify semantic of functions. They need more complex consistency > > model. It defines when it is safe time for the system or task to start > > using the new functions (switch to the new universe). > > > > In theory, different tasks might be in more universes if more patches are > > being applied. In practice, we deal with only two universes. The trick is > > that we allow to add new patch only when the whole system has switched > > to the previous one. > > > > Is this terminology documented anywhere upstream yet? Even if it was documented (it isn't), it's pretty weird terminology - please use clearer formulations, like 'patched function' or 'unpatched function' or 'function with pending patch'. No need to redefine existing words in a weird fashion just to create the appearance of being special ... Thanks, Ingo