From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/0] RFC: ARM: Thumb-2: Symbol manipulation macros for function body copying
Date: Wed, 12 Jan 2011 09:32:09 +0000 [thread overview]
Message-ID: <20110112093209.GA18833@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1294790551-17069-1-git-send-email-dave.martin@linaro.org>
On Tue, Jan 11, 2011 at 06:02:30PM -0600, Dave Martin wrote:
> To make it easier to deal with cases like this, I've had a
> go at writing some macros to make copying function bodies
> easier, while being robust for ARM and Thumb-2.
How about instead providing some infrastructure which coes the
copy too? Something like:
#define copy_fn_to_sram(to, fn, size) ({ \
__typeof__(fn) f; \
unsigned long ptr; \
__asm__("" : "=r" (ptr) : "0" (fn)); \
memcpy(to, (void *)(ptr & ~1), size); \
ptr = (ptr & 1) | (unsigned long)to; \
__asm__("" : "=r" (f) : "0" (ptr)); \
f; \
})
Used by:
extern void my_func(int foo);
extern int my_func_size;
void call_my_func(void *to, int arg)
{
void (*fn)(int);
fn = copy_fn_to_sram(to, my_func, my_func_size);
fn(arg);
}
Then if you need to fix the way the copies are done for some
architectural reason, there's only one place to do it.
I'm not sure asm/unified.h is the right place - I don't think this has
anything to do with the unified assembler syntax. Please create a new
header for this.
next prev parent reply other threads:[~2011-01-12 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 0:02 [PATCH 0/0] RFC: ARM: Thumb-2: Symbol manipulation macros for function body copying Dave Martin
2011-01-12 0:02 ` [PATCH 1/1] " Dave Martin
2011-01-12 9:32 ` Russell King - ARM Linux [this message]
2011-01-12 16:00 ` [PATCH 0/0] RFC: " Dave Martin
2011-01-12 16:11 ` Russell King - ARM Linux
2011-01-12 16:55 ` Dave Martin
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=20110112093209.GA18833@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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).