From: Li Yu <raise.sail@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: A question about backport jump label
Date: Wed, 11 Apr 2012 13:59:39 +0800 [thread overview]
Message-ID: <4F851DCB.7090304@gmail.com> (raw)
Hi,
We want to backport jump label for 2.6.32 x86_64 kernel on
RHEL5/RHEL6. Such two systems use old versions of gcc 4.1 and 4.4,
so they have not "asm goto" support, which is required for jump label.
I tried some ways to implement jump label without any
modification of core implementation, but all are failed.
My tries are focus on x86's arch_static_branch() modification.
So far, I don't found out any good alternative solution of "asm
goto" in old gcc. The last try is failed since its my implementation
can't be invoked at same function multi times. The reason is GNU as does
not assign different addresses on same symbol.
My question, is possible to implement to jump label under such
constraints? It's best to keep same interface with upstream tree.
Any suggestions is welcome, thanks.
Yu
reply other threads:[~2012-04-11 5:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F851DCB.7090304@gmail.com \
--to=raise.sail@gmail.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).