linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Chris Friesen <cfriesen@nortel.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: somewhat OT -- trying to build code on the fly then run it
Date: Tue, 05 Apr 2005 11:03:25 +1000	[thread overview]
Message-ID: <1112663005.26086.134.camel@gaston> (raw)
In-Reply-To: <4251CEA4.6070604@nortel.com>

On Mon, 2005-04-04 at 17:32 -0600, Chris Friesen wrote:
> I'm writing a testcase to test some code we wrote to allow userspace to 
> flush the whole dcache and invalidate the whole icache.  This requires 
> me to write self-modifying code.  For the first stage I'm just trying to 
> build a routine (that just increments r3 and returns) on the heap and 
> then call it.
> 
> Everything seems to be fine right up until I jump to the code that I've 
> written, then I get a segfault.  The debugger shows my registers and 
> data values are as expected, and the page of memory has xwr permissions.
> 
> Can anyone tell me what I'm missing?  I'm sure its something simple.
> 
> Thanks,
> 
> Chris.
> 
> 
> PS.  Here's my current test code.
> 
> #include <errno.h>
> #include <sys/types.h>
> #include <sys/stat.h>
> #include <fcntl.h>
> #include <sys/ioctl.h>
> #include <unistd.h>
> #include <stdio.h>
> #include <stdio.h>
> #include <sys/mman.h>
> 
> /* these next two lines are the hex equivalents of the instructions:
>   * addi r3,r3,1
>   * blr
>   */
> unsigned int incr_code[] = {
> 	0x38630001,
> 	0x4e800020
> };
> 
> int dotest(unsigned long *addr)
> {
>          int i=0;
>          asm volatile (" \n\
>                  mr 3,%1 \n\
>                  bla %2  \n\
>                  mr %0,3 \n"
>                  : "=r" (i)
>                  : "r" (i), "r" (addr));
>          return i;
> }

bla can only be used for small addresses (or very high addresses), and
it doesn't take a register argument but an absolute address. You want
something different, more like

	mtctr %2
	bctrl

Though you also need to add proper "clobber" constraints to indicate to
the compiler what will be clobbered by the routine you are calling (look
at the syscall macros of the kernel for an example of rather standard
clobber lists).

> void alter_opcode(unsigned long *addr, unsigned long opcode)
> {
> 	unsigned long offset = 0;
> 	
> 	asm volatile(
>                  "stw    %1,0(%0)  \n\t"
>                  "dcbf   %0,%2     \n\t"
>                  "sync             \n\t"
>                  "icbi   %0,%2     \n\t"
>                  "sync             \n\t"
>                  "isync            \n\t"
>                      :: "r" (addr), "r" (opcode), "r" (offset));
> }
> 
> int main()
> {
> 	unsigned long *addr;
> 	void *p = mmap(0, 4096, PROT_EXEC|PROT_WRITE|PROT_READ,
> 		MAP_PRIVATE|MAP_ANONYMOUS, 0, 0);
> 	if (p == MAP_FAILED) {
> 		perror("mmap");
> 		goto error;
> 	}
> 	
> 	addr = (unsigned long *)p;
> 	
> 	alter_opcode(addr, incr_code[0]);
> 	alter_opcode(addr+1, incr_code[1]);
> 	
> 	printf("%d\n", dotest(addr));
> 	return 0;
> 	
> error:
> 	return -1;
> }
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
-- 
Benjamin Herrenschmidt <benh@kernel.crashing.org>

  reply	other threads:[~2005-04-05  1:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04 23:32 somewhat OT -- trying to build code on the fly then run it Chris Friesen
2005-04-05  1:03 ` Benjamin Herrenschmidt [this message]
2005-04-05 17:03   ` Chris Friesen
  -- strict thread matches above, loose matches on Subject: below --
2005-04-05 15:08 Fillod Stephane
2005-04-05 16:43 ` Chris Friesen

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=1112663005.26086.134.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=cfriesen@nortel.com \
    --cc=linuxppc-dev@ozlabs.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).