From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel@nongnu.org, Glauber Costa <glommer@redhat.com>,
Kevin O'Connor <kevin@koconnor.net>,
gpxe@etherboot.org, Naphtali Sprei <nsprei@redhat.com>
Subject: Re: [Qemu-devel] Stack corruption problem with SeaBIOS/gPXE under QEMU
Date: Wed, 18 Nov 2009 16:21:34 +0200 [thread overview]
Message-ID: <4B0402EE.6070609@redhat.com> (raw)
In-Reply-To: <20091118141949.GA3193@redhat.com>
On 11/18/2009 04:19 PM, Gleb Natapov wrote:
>>>
>>> Do we have the same problem with tpr patching rom (vapic,bin)? It modifies
>>> itself too.
>>>
>> But a reset will reload it.
>>
>>
> Correct, but Kevin says "sendkey ctrl-alt-delete" jumps to SeaBIOS's
> reboot vector without issuing system reset. I am talking about this situation.
>
That's only if we're in the bios. If an OS has taken over, it will
issue a proper reset. If an OS has not taken over (DOS won't, probably)
then it isn't Windows and the vapic payload hasn't had a chance to
modify itself.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-11-18 14:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-12 11:20 [Qemu-devel] Stack corruption problem with SeaBIOS/gPXE under QEMU Naphtali Sprei
2009-11-14 19:47 ` Kevin O'Connor
2009-11-15 9:43 ` Naphtali Sprei
2009-11-16 13:36 ` Avi Kivity
2009-11-16 14:02 ` Avi Kivity
2009-11-17 2:26 ` Kevin O'Connor
2009-11-17 13:23 ` Avi Kivity
2009-11-21 0:47 ` Kevin O'Connor
2009-11-29 10:58 ` Avi Kivity
2009-11-18 9:39 ` Gleb Natapov
2009-11-18 9:49 ` Alexander Graf
2009-11-18 9:53 ` Gleb Natapov
2009-11-18 12:58 ` Kevin O'Connor
2009-11-18 13:06 ` Kevin O'Connor
2009-11-18 14:22 ` Gleb Natapov
2009-11-18 15:38 ` [gPXE] " Joshua Oreman
2009-11-19 1:07 ` Kevin O'Connor
2009-11-18 13:50 ` Avi Kivity
2009-11-18 14:19 ` Gleb Natapov
2009-11-18 14:21 ` Avi Kivity [this message]
2009-11-20 22:39 ` Kevin O'Connor
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=4B0402EE.6070609@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=glommer@redhat.com \
--cc=gpxe@etherboot.org \
--cc=kevin@koconnor.net \
--cc=nsprei@redhat.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).