All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Tejun Heo <tj@kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: git pull request for tip/tracing/urgent
Date: Wed, 11 Feb 2009 10:53:25 +0100	[thread overview]
Message-ID: <20090211095325.GD20518@elte.hu> (raw)
In-Reply-To: <49929763.3080608@kernel.org>


* Tejun Heo <tj@kernel.org> wrote:

> Hello,
> 
> Ingo Molnar wrote:
> > This bit:
> > 
> >   	".section .fixup, \"ax\"\n"
> >  	"4: movl $1, %[faulted]\n"
> >  	"   jmp 3b\n"
> >  	".previous\n"
> > 
> > Can be thought of as an 'embedded' or 'nested' section - the '.previous'
> > directive jumps back to whatever section we were in before. This can be
> > nested multiple times too:
> > 
> >    .section A
> >    [...]
> >      .section B
> >      [...]
> >         .section C
> >         [...]
> >         .previous
> >      [...]
> >      .previous
> >    [...]
> >    .previous
> 
> That will result in...
> 
>  A->B->C->B->C->B
> 
> .pushsection and .popsection should be used for nesting, right?
> 
> Thanks.

hm ... doh, yes. I think we even had a bug in this area.

Why is it implemented like this? These semantics seem to make no sense.

	Ingo

  reply	other threads:[~2009-02-11  9:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10 18:19 git pull request for tip/tracing/urgent Steven Rostedt
2009-02-10 18:30 ` Frederic Weisbecker
2009-02-10 23:00   ` Steven Rostedt
2009-02-11  1:28     ` Frederic Weisbecker
2009-02-11  9:02       ` Ingo Molnar
2009-02-11  9:16         ` Tejun Heo
2009-02-11  9:53           ` Ingo Molnar [this message]
2009-02-12  1:24             ` H. Peter Anvin
2009-02-11 13:40         ` Frederic Weisbecker
2009-02-11  8:49 ` Ingo Molnar

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=20090211095325.GD20518@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.