From: "Rafael Ávila de Espíndola" <rafael.espindola@ic.unicamp.br>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] USE_CODE_COPY breaks clone
Date: Wed, 1 Sep 2004 20:17:21 -0300 [thread overview]
Message-ID: <200409012017.21889.rafael.espindola@ic.unicamp.br> (raw)
In-Reply-To: <200409011432.40742.rafael.espindola@ic.unicamp.br>
On Wednesday 01 September 2004 14:32, Rafael Ávila de Espíndola wrote:
> I think that the problem is in the fact that cpu_init is called in the
> parent process and this functions calls modify_ldt.
>
> Where can I found some documentation about modify_ldt? What is
> USE_CODE_COPY supposed to do?
Ok. It translate i386 to i386 code by copying it.
> I will try to call cpu_init from within the new thread and see if it works.
No it doesn't. If clone is called with CLONE_VM then the kernel does
mm = oldmm;
and both processes share the ldt. So the parent ldt is "also" changed when
cpu_init is called from clone_func.
I could not find out why it is necessary to modify the ltd of the process for
code copy to work. Is there some documentation? Could someone explain?
Does someone have an Idea of how to solve this?
Thanks,
Rafael
prev parent reply other threads:[~2004-09-01 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-01 17:32 [Qemu-devel] USE_CODE_COPY breaks clone Rafael Ávila de Espíndola
2004-09-01 23:17 ` Rafael Ávila de Espíndola [this message]
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=200409012017.21889.rafael.espindola@ic.unicamp.br \
--to=rafael.espindola@ic.unicamp.br \
--cc=qemu-devel@nongnu.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).