Subject: Re: [PATCH 0/3] jump label: updates for 2.6.37
From: Steven Rostedt <rostedt@goodmis.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jason Baron <jbaron@redhat.com>, mingo@elte.hu, peterz@infradead.org,
        mathieu.desnoyers@polymtl.ca, tglx@linutronix.de, andi@firstfloor.org,
        roland@redhat.com, rth@redhat.com, masami.hiramatsu.pt@hitachi.com,
        fweisbec@gmail.com, avi@redhat.com, davem@davemloft.net,
        sam@ravnborg.org, ddaney@caviumnetworks.com, michael@ellerman.id.au,
        linux-kernel@vger.kernel.org
In-Reply-To: <4CEC33F6.9090808@zytor.com>
References: <cover.1290546539.git.jbaron@redhat.com>
	 <4CEC33F6.9090808@zytor.com>
Content-Type: text/plain; charset="ISO-8859-15"
Date: Tue, 23 Nov 2010 18:11:54 -0500
Message-ID: <1290553914.30543.408.camel@gandalf.stny.rr.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1552
Lines: 38

On Tue, 2010-11-23 at 13:36 -0800, H. Peter Anvin wrote:
> On 11/23/2010 01:27 PM, Jason Baron wrote:
> > Hi,
> > 
> > A few jump label patches that I want considered for 2.6.37. Patches are against
> > the latest -tip tree.
> > 
> > The first one, which adds 'state' to the jump label mechanism is the most
> > important. Essentially, it ensures that if jump labels are enabled/disabled in
> > the core kernel but the actual call sites are in modules, we properly honor the
> > state of the jump label. This also works for jump labels which may be defined in
> > one module but made use of in another module.
> > 
> > There has been some discussion about using the 'key' variable to store the
> > enabled/disabled state for each jump label. However, I think a better design
> > will be to use the 'key' variable to store a pointer to the appropriate jump
> > label tables. In this way, we can enable/disable jump labels, without the
> > hashing that I'm currently doing. However, I didn't want to propose these more
> > invasive changes until 2.6.38. 
> > 
> 
> I would also like to see a change in the API, preferrably something
> closer to the "SWITCH_POINT" interface I discussed with Stephen before
> Kernel Summit.
> 

Could you explain in more detail what you would like to see.

Thanks,

-- Steve


--
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/