From: Avi Kivity <avi@redhat.com>
To: Michael Karcher <Michael.Karcher@fu-berlin.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Windows 98 installer
Date: Tue, 25 Oct 2011 10:15:30 +0200 [thread overview]
Message-ID: <4EA67022.3010800@redhat.com> (raw)
In-Reply-To: <1319480506.8603.54.camel@localhost>
On 10/24/2011 08:21 PM, Michael Karcher wrote:
> If you know the 8086 architecture by heart, and also know the qemu code,
> you could get the idea that there might be an emulation bug causing the
> premature acceptance of the second interrupt (would it be accepted after
> cleaning up the stack frames, there would be no problem), namely that
> after an IRET or STI instruction, interrupts are only accepted after one
> further instruction - and only if they are still enabled.
This is true for STI (and only if interrupts were previously disabled),
not IRET.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2011-10-25 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 18:21 [Qemu-devel] Windows 98 installer Michael Karcher
2011-10-25 8:15 ` Avi Kivity [this message]
2011-10-25 15:45 ` Michael Karcher
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=4EA67022.3010800@redhat.com \
--to=avi@redhat.com \
--cc=Michael.Karcher@fu-berlin.de \
--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).