From: Mulyadi Santosa <mulyadi.santosa@gmail.com>
To: maheen butt <maheen_butt26@yahoo.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] forking with x86_64
Date: Wed, 12 Jan 2011 23:53:05 +0700 [thread overview]
Message-ID: <AANLkTi=5CbgHTUMvuWghUCDXCSK==L+4VF3-Tq5Nteme@mail.gmail.com> (raw)
In-Reply-To: <326252.57002.qm@web63206.mail.re1.yahoo.com>
On Wed, Jan 12, 2011 at 17:17, maheen butt <maheen_butt26@yahoo.com> wrote:
>
> hi
> why qemu does not provide NPTL support for x86 in user mode? is there any big hindrance behind it?
IMHO, your experiment works since it simply fork(). What qemu wanna do
here is complete NPTL handling...and afaik that means clone(),
pthread_ family function and so on. Yes, fork() is based on clone(),
but it really create wholly new task, while NPTL as we speak here
means thread....
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2011-01-12 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 10:17 [Qemu-devel] forking with x86_64 maheen butt
2011-01-12 16:53 ` Mulyadi Santosa [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='AANLkTi=5CbgHTUMvuWghUCDXCSK==L+4VF3-Tq5Nteme@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--cc=maheen_butt26@yahoo.com \
--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).