From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Mathieu Desnoyers <compudj@krystal.dyndns.org>
Cc: Martin Bligh <mbligh@google.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
prasanna@in.ibm.com, Andrew Morton <akpm@osdl.org>,
Ingo Molnar <mingo@elte.hu>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Paul Mundt <lethal@linux-sh.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Jes Sorensen <jes@sgi.com>, Tom Zanussi <zanussi@us.ibm.com>,
Richard J Moore <richardj_moore@uk.ibm.com>,
Michel Dagenais <michel.dagenais@polymtl.ca>,
Christoph Hellwig <hch@infradead.org>,
Greg Kroah-Hartman <gregkh@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
William Cohen <wcohen@redhat.com>,
ltt-dev@shafik.org, systemtap@sources.redhat.com,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Karim Yaghmour <karim@opersys.com>, Pavel Machek <pavel@suse.cz>,
Joe Perches <joe@perches.com>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
"Jose R. Santos" <jrs@us.ibm.com>
Subject: Re: [PATCH] Linux Kernel Markers 0.13 for 2.6.17
Date: Mon, 25 Sep 2006 17:06:55 -0700 [thread overview]
Message-ID: <45186F1F.8030408@goop.org> (raw)
In-Reply-To: <20060925233349.GA2352@Krystal>
Mathieu Desnoyers wrote:
> +/* Note : max 256 bytes between over_label and near_jump */
> +#define MARK_JUMP(name, format, args...) \
> + do { \
> + asm volatile( ".section .markers, \"a\";\n\t" \
> + ".long 0f, 1f, 2f;\n\t" \
> + ".previous;\n\t" \
> + ".align 16;\n\t" \
> + ".byte 0xeb;\n\t" \
> + "0:\n\t" \
> + ".byte 2f-1f;\n\t" \
> + "1:\n\t" \
> + : "+m" (__marker_sequencer) : ); \
> + MARK_CALL(name, format, ## args); \
> + asm volatile ( "2:\n\t" : "+m" (__marker_sequencer) : ); \
>
Unfortunately this doesn't work either. The two asms are ordered with
respect to each other, but there's nothing to 1) stop the MARK_CALL from
being moved out between them, 2) something else being moved in between
them. I don't really see a way out of this without implementing the
whole call in assembler as well, which is a big pain.
J
prev parent reply other threads:[~2006-09-26 0:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-25 23:33 [PATCH] Linux Kernel Markers 0.13 for 2.6.17 Mathieu Desnoyers
2006-09-25 23:56 ` Mathieu Desnoyers
2006-09-26 0:16 ` Jeremy Fitzhardinge
2006-09-26 0:25 ` Mathieu Desnoyers
2006-09-26 0:45 ` Mathieu Desnoyers
2006-09-26 1:02 ` Jeremy Fitzhardinge
2006-09-26 2:59 ` Mathieu Desnoyers
2006-09-26 5:03 ` Jeremy Fitzhardinge
2006-09-26 18:04 ` Mathieu Desnoyers
2006-09-26 18:57 ` Jeremy Fitzhardinge
2006-09-26 19:08 ` Mathieu Desnoyers
2006-09-26 19:49 ` Frank Ch. Eigler
2006-09-26 20:05 ` Mathieu Desnoyers
2006-09-26 0:06 ` Jeremy Fitzhardinge [this message]
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=45186F1F.8030408@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=compudj@krystal.dyndns.org \
--cc=fche@redhat.com \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=jes@sgi.com \
--cc=joe@perches.com \
--cc=jrs@us.ibm.com \
--cc=karim@opersys.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@shafik.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mbligh@google.com \
--cc=michel.dagenais@polymtl.ca \
--cc=mingo@elte.hu \
--cc=pavel@suse.cz \
--cc=prasanna@in.ibm.com \
--cc=rdunlap@xenotime.net \
--cc=richardj_moore@uk.ibm.com \
--cc=systemtap@sources.redhat.com \
--cc=tglx@linutronix.de \
--cc=wcohen@redhat.com \
--cc=zanussi@us.ibm.com \
/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.