From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-user@lists.sourceforge.net,
Jason Lunz <lunz@falooley.org>,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: (implementation idea) Re: uml and nonstandard memory splits?
Date: Tue, 28 Mar 2006 15:02:19 -0500 [thread overview]
Message-ID: <20060328200219.GC21540@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200603280030.05911.blaisorblade@yahoo.it>
On Mon, Mar 27, 2006 at 11:30:05PM +0100, Blaisorblade wrote:
> That is problem #1, and exists; but when answering I thought to problem #2,
> i.e. that the stub code currently hardcodes the location of the stub data
> page, and that this must be fixed; I didn't notice that we must first put the
> stubs somewhere.
I see - you're one problem ahead of me.
I'm wondering if we can play some linker tricks for this. Stick a
word of data on the code page and put the data page address in it.
Then the stub just reads that in order to get the data.
>
> So I remembered that trick to get EIP which I read time ago (the purpose was
> to make some code Position-Independent exactly injecting some code into
> another process address space).
That's the standard way of getting your EIP on x86 since there's no
move from EIP instruction. That will work, too, but (as you point
out) requires a register.
> > Another approach is to start with the current top of stack
Hmmmm :-) Maybe easier said than done. I was thinking about figuring
that out as basically the first thing in main, but I can think of
reasons that wouldn't be robust.
Other schemes, which involve a binary search for the boundary by using
test mmaps, involve the risk of unmapping part of the stack.
Jeff
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2006-03-28 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dvv6ir$ajn$1@sea.gmane.org>
[not found] ` <20060323235044.GA7273@ccure.user-mode-linux.org>
[not found] ` <20060324004052.GA1897@knob.reflex>
2006-03-24 0:56 ` [uml-devel] (implementation idea) Re: uml and nonstandard memory splits? Blaisorblade
2006-03-24 2:30 ` [uml-devel] " Jeff Dike
2006-03-24 14:34 ` Blaisorblade
2006-03-24 16:40 ` Jason Lunz
2006-03-24 17:26 ` Jeff Dike
2006-03-27 22:30 ` Blaisorblade
2006-03-28 20:02 ` Jeff Dike [this message]
2006-03-28 22:05 ` [uml-devel] Re: [uml-user] " Blaisorblade
2006-03-28 22:09 ` Blaisorblade
2006-03-28 20:09 [uml-devel] " Jeff Dike
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=20060328200219.GC21540@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=blaisorblade@yahoo.it \
--cc=lunz@falooley.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
--cc=user-mode-linux-user@lists.sourceforge.net \
/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.