From: Stefan Kisdaroczi <kisda@hispeed.ch>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Final call for help: x86: enter instruction bug
Date: Fri, 12 Nov 2004 15:06:00 +0100 [thread overview]
Message-ID: <4194C348.6040008@hispeed.ch> (raw)
In-Reply-To: <Pine.LNX.4.58.0410292045060.12338@wgmdd8.biozentrum.uni-wuerzburg.de>
Hi Johannes,
thank you very much for your help. I implemented yesterday a helper function as you suggested,
and now the enter instruction works like i want and it should.
I was not able to run a "Hello World" without exception before, and now i can start a "big" App with 10 processes, IPC's, lots of Tasks... just great
I try to make a patch to the latest CVS this weekend.
thank you
kisda
Johannes Schindelin wrote:
> Hi,
>
> On Fri, 29 Oct 2004, Stefan Kisdaroczi wrote:
>
>
>>I tried to fix it myself, but how to copy from stack to stack ? I looked
>>at other instructions how to do, T0 and T1 are already used, what else
>>can I use ?
>
>
> You can write a helper. See op.c, function op_divl_EAX_T0 for an example.
> Of course you have to add yet another op_ in op.c, which you then can
> use by adding the respective gen_op_ in gen_enter.
>
>
>>I cant send you a Test-App/Image, because you dont have this OS, and I
>>cant send it to you. ( OS and Compiler are from Intel and not free )
>
>
> That makes it rather hard to help you.
>
> Hth,
> Dscho
>
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
next parent reply other threads:[~2004-11-12 14:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <418288C8.3000501@hispeed.ch>
[not found] ` <Pine.LNX.4.58.0410292045060.12338@wgmdd8.biozentrum.uni-wuerzburg.de>
2004-11-12 14:06 ` Stefan Kisdaroczi [this message]
2004-11-12 14:38 ` [Qemu-devel] Final call for help: x86: enter instruction bug Johannes Schindelin
2004-11-14 14:57 ` [Qemu-devel] Final call for help: x86: enter instruction bug: PATCH Stefan Kisdaroczi
2004-11-14 15:06 ` Fabrice Bellard
2004-11-14 18:01 ` Stefan Kisdaroczi
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=4194C348.6040008@hispeed.ch \
--to=kisda@hispeed.ch \
--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).