|
Message
From: Matjaz Breskvar<phoenix@o...>
Date: Wed Mar 30 23:33:09 CEST 2005
Subject: [openrisc] or1ksim patches #34, #43, #53-2, #64, #68-#73
* György 'nog' Jeney (nog@s...) wrote:
> > #72 accepted with warning, how difficult would it be to add the 'not
> > working'
> > functionality when using recompiler. For now, please add a printf which will
> > complain if somebody uses recompiler and tries to patch a register or do
> > something else that is not supported in recompiler mode. (this will reduce
> > the number of support questions)
>
> Not that hard. I'll tend to them in due course. For the time being (shouldn't
> be too long), the attached patch should do what you ask.
Great.
> > i just got idea about the exec-schield,... just adding
> >
> > __attribute__ ((__section__ (".text")))
> >
> > to the static definition of variable should fix it. i don't know how
> > convinient is to do this, but it would remove the need for disabling
> > security (i'm guessing all distributions will migrate to
> > exec-protection, especialy with x86-64 extensions...)
>
> That doesn't appear to work. Even on a non exec-shield enabled kernel the
> attached `execs.c' fails, since pfoo_call goes into a write protected section,
> don't know why. Even FC2 comes with this feature enabled by default...
This is not what i ment. The
static void *pfoo_call __attribute__((section(".text")));
only creates pointer in the .text section, which is pointing then to
something in heap. i thought something like
static char __attribute__((section(".text"))) page[PAGE_SIZE];
and then copy some executable code to that page and execute the code
from there...
> - The sim crashes when running `ls' in proc/net.
this is interesting. where it crashes (ethernet ???, but why...)
> - Running the `test' program (in the initrd) fails, same as vi, and some others.
how it fails ?
> Before I go and commint > 40 patches to cvs in one go, is the cvs-checkins list
> going to work anytime soon? It is much easier to do regression tests if the
> commit logs are availible.
agreed, but very unlikely that it will be fixed in forseeable time.
what you could do, and it will actually help with regression tests is to
do a cvs tag after each patch...
best regards,
p.
|
 |
Browse
