From: Stefano Bonifazi <stefboombastic@gmail.com>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Mulyadi Santosa <mulyadi.santosa@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-user: relocating target code weakness
Date: Mon, 24 Jan 2011 22:52:21 +0100 [thread overview]
Message-ID: <4D3DF495.8000707@gmail.com> (raw)
In-Reply-To: <AANLkTin5Q1eiwu7HcPUE1aF7oYR9Ah3H_And2-yM=kFt@mail.gmail.com>
> but that can happen with the app running natively too, so any app not
> handling MAP_FIXED failures is buggy and not qemu's problem.
> -mike
How? For what I learned each process executing on a OS with an mmu sees
its virtual address space, and normally only its code is loaded there
(well I am learning that the dynamic linker also inject into that space
shared library code used by the process code, but of course a good
dynamic linker would prevent clashes!) so how can it happen that it can
clash with anything??
If I remember fine, at the time of DOS there were some addresses
reserved for the OS, and then only one executable could run at time, but
in modern time with virtual addressing I don't think it is possible
other than in scenarios alike ours..
Regards,
Stefano B.
next prev parent reply other threads:[~2011-01-24 21:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 11:34 [Qemu-devel] qemu-user: relocating target code weakness Stefano Bonifazi
2011-01-24 16:29 ` Mulyadi Santosa
2011-01-24 18:16 ` Stefano Bonifazi
2011-01-24 20:00 ` Mike Frysinger
2011-01-24 20:58 ` Stefano Bonifazi
2011-01-24 21:21 ` Mike Frysinger
2011-01-24 21:52 ` Stefano Bonifazi [this message]
2011-01-24 22:11 ` Mike Frysinger
2011-01-24 22:24 ` Stefano Bonifazi
2011-01-24 22:34 ` Mike Frysinger
2011-01-25 0:06 ` Mike Frysinger
2011-01-25 0:18 ` Mike Frysinger
2011-01-25 8:49 ` Stefano Bonifazi
2011-01-25 8:26 ` Stefano Bonifazi
2011-01-24 19:46 ` Richard Henderson
2011-01-24 21:44 ` Stefano Bonifazi
2011-01-24 23:32 ` Mike Frysinger
2011-01-25 8:25 ` Stefano Bonifazi
2011-01-25 1:36 ` Richard Henderson
2011-01-25 8:47 ` Stefano Bonifazi
2011-01-25 8:53 ` Mike Frysinger
2011-01-25 9:58 ` Stefano Bonifazi
2011-01-25 10:47 ` Stefano Bonifazi
2011-01-25 16:22 ` Richard Henderson
2011-01-25 19:03 ` Stefano Bonifazi
2011-01-25 11:06 ` Stefano Bonifazi
2011-01-25 16:26 ` Richard Henderson
2011-01-25 19:49 ` Stefano Bonifazi
2011-01-25 20:53 ` Lluís
2011-01-26 11:07 ` Stefano Bonifazi
2011-01-26 15:38 ` Richard Henderson
2011-01-26 17:44 ` Stefano Bonifazi
2011-01-26 20:17 ` Lluís
2011-01-26 20:19 ` Richard Henderson
2011-01-26 20:33 ` Stefano Bonifazi
2011-01-26 20:36 ` Lluís
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=4D3DF495.8000707@gmail.com \
--to=stefboombastic@gmail.com \
--cc=mulyadi.santosa@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=vapier.adi@gmail.com \
/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).