From: Mulyadi Santosa <a_mulyadi@softhome.net>
To: qemu-devel@nongnu.org, Josh Triplett <josh@psas.pdx.edu>
Subject: Re: [Qemu-devel] Re: qemu-ppc fails to run clone with CLONE_VM, threaded programs, non-static programs
Date: Sun, 23 Oct 2005 11:21:20 +0700 [thread overview]
Message-ID: <200510231121.20448.a_mulyadi@softhome.net> (raw)
In-Reply-To: <4359E22A.2090904@psas.pdx.edu>
Hello...
> I worked with pbrook on #qemu to debug this issue. The problem turns
> out to be that qemu's do_fork function on PowerPC zeroes out r7-r31
> in the new CPU state structure after a clone, which it should not do,
Josh....at least it proves (to me) that the parameters passed to the
clone() is correct. About the registers....well, this is completely new
for me.
I wonder, what is the function of those registers (r7-r31)? Something
related with the segments?
> as the child's registers should match the parent; it also does not
> zero register r3, which holds the return value and should be zero in
> the child. I've prepared and attached a patch which should solve
> this problem.
Nice...this is something we surely forgot from out last attempt to debug
the problem....return value. I was too focused on checking every memory
accesses were done inside process address space and function address
translation were done correctly :)
Anyway, just a personal suggestion. You can put that patch to
qemu.dad-answers.com along with the description on how you found the
bug and what this patch does.
regards
Mulyadi
next prev parent reply other threads:[~2005-10-23 4:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 1:09 [Qemu-devel] qemu-ppc fails to run clone with CLONE_VM, threaded programs, non-static programs Josh Triplett
2005-10-22 6:54 ` [Qemu-devel] " Josh Triplett
2005-10-23 4:21 ` Mulyadi Santosa [this message]
2005-10-24 11:32 ` Josh Triplett
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=200510231121.20448.a_mulyadi@softhome.net \
--to=a_mulyadi@softhome.net \
--cc=josh@psas.pdx.edu \
--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 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.