From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: loadvm and APIC
Date: Tue, 17 Jun 2008 23:51:00 +0200 [thread overview]
Message-ID: <485831C4.4000107@bellard.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0806172206020.2110@linmac.oyster.ru>
malc wrote:
> On Tue, 17 Jun 2008, Jan Kiszka wrote:
>
>> malc wrote:
>>> Here's the scenario:
>>>
>
> [..snip..]
>
>>
>> That is basically
>> http://permalink.gmane.org/gmane.comp.emulators.qemu/26215, which I
>> would prefer.
>
> Yes, i never paid enough attention to that patch, and it does indeed
> look better.
No. This is a hack which does not fix the real problem. At least saving
and restoring "interrupt_pending" would bring us closer to a better
solution.
Fabrice.
next prev parent reply other threads:[~2008-06-17 22:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-17 5:19 [Qemu-devel] loadvm and APIC malc
2008-06-17 7:58 ` [Qemu-devel] " Jan Kiszka
2008-06-17 18:07 ` malc
2008-06-17 21:51 ` Fabrice Bellard [this message]
2008-06-18 9:00 ` Jan Kiszka
2008-06-18 20:12 ` malc
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=485831C4.4000107@bellard.org \
--to=fabrice@bellard.org \
--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).