From: Gleb Natapov <gleb@redhat.com>
To: Sebastian Herbszt <herbszt@gmx.de>
Cc: Kevin O'Connor <kevin@koconnor.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: POST failure (loop) with isapc and seabios
Date: Wed, 25 Nov 2009 12:48:01 +0200 [thread overview]
Message-ID: <20091125104801.GL2999@redhat.com> (raw)
In-Reply-To: <5CC421C2B93B4444A14E88071CC2546A@FSCPC>
On Wed, Nov 25, 2009 at 12:27:06AM +0100, Sebastian Herbszt wrote:
> Gleb Natapov wrote:
> >On Mon, Nov 23, 2009 at 10:30:56PM +0100, Sebastian Herbszt wrote:
> >>Gleb Natapov wrote:
> >>>On Mon, Nov 23, 2009 at 08:19:54PM +0100, Sebastian Herbszt wrote:
> >>>>Gleb Natapov wrote:
> >>>>>On Sun, Nov 22, 2009 at 09:01:45PM +0100, Sebastian Herbszt wrote:
> >>>>>>Gleb Natapov wrote:
> >>>>>>>On Sun, Nov 22, 2009 at 04:31:24PM +0100, Sebastian Herbszt wrote:
> >>>>>>>>
> >>>>>>>>Bad things could happen if someone modifies the BIOS because it's unprotected
> >>>>>>>>(e.g. VM crash).
> >>>>>>>>
> >>>>>>>BIOS is reloaded during VM reset.
> >>>>>>
> >>>>>>The BIOS is not reloaded - tested with "reboot" on Linux and system_reset in monitor.
> >>>>>>
> >>>>>Looks like a bug. Tested with latest QEMU version I assume?
> >>>>
> >>>>Tested with v0.11.0-rc0-1677-gf165b53. Where do you suspect a bug? In the behaviour
> >>>>on "reboot" or system_reset? I think it depends wheter it's a software or hardware reset.
> >>>>
> >>>The bug is that BIOS rom is not reloaded on hardware reset (what do you
> >>>call software reset?). Can you retest with latest git?
> >>
> >>Same with v0.11.0-rc0-1699-gb0293e5.
> >>Bochs has the notion of BX_RESET_SOFTWARE and BX_RESET_HARDWARE. Those
> >>two describe the source of the reset and the hardware, in most cases just the cpu, is reset
> >>differently depending on the source (e.g. hardware reset / power on vs. INIT#). I think this
> >>behaviour is also described in the 440fx spec (chapter "4.5.3 SYSTEM RESET").
> >>
> >>If the monitor command "system_reset" is supposed to be the equivalent of pushing the reset
> >>button of the box, then the bios should be reloaded (i think, not entirely sure what the pin is
> >>wired to). But the bios should not be reloaded if the OS just jumps to the bios reset code.
> >>
> >Correct, but modern OSes never jump to the bios reset code. They use
> >ACPI reset, kbd reset or triple fault to do reset. All of those generate
> >exactly the same kind of reset as "system_reset" monitor command.
>
> With the 440FX you get two sources of a hard reset - power on and i/o write to reset control register.
> Tho the PMC should not be used to generate a hard reset if used with a PIIX3. You get a soft reset on
> CPU shutdown bus cycle, i/o write to keyboard controller, i/o write to port 92h and i/o write to reset
> control register. The latter can be used for hard and soft resets. During a hard reset the PMC sets its
> configuration registers to default values. The PAM registers are set to 0 and the BIOS is accessed thru
> rom and not shadow ram. On a triple fault the CPU generates the shutdown bus cycle and since the PMC
> responds to it with a soft reset the BIOS is not reloaded (?). I might have missed something in some
> specification tho.
>
Nice sum up. Thanks. When I said "all of those generate exactly the same
kind of reset as "system_reset" monitor command" I meant in QEMU, not on
actual HW. QEMU has no notion of different type of resets, though it
should.
--
Gleb.
next prev parent reply other threads:[~2009-11-25 10:48 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 21:30 [Qemu-devel] POST failure (loop) with isapc and seabios Sebastian Herbszt
2009-11-20 22:51 ` [Qemu-devel] " Kevin O'Connor
2009-11-21 14:37 ` Sebastian Herbszt
2009-11-22 12:35 ` Gleb Natapov
2009-11-22 15:07 ` Sebastian Herbszt
2009-11-22 15:10 ` Gleb Natapov
2009-11-22 15:31 ` Sebastian Herbszt
2009-11-22 15:38 ` Gleb Natapov
2009-11-22 17:40 ` Kevin O'Connor
2009-11-22 21:15 ` Sebastian Herbszt
2009-11-22 22:04 ` Sebastian Herbszt
2009-11-23 11:14 ` Gleb Natapov
2009-11-23 11:17 ` Gleb Natapov
2009-11-22 20:01 ` Sebastian Herbszt
2009-11-23 11:11 ` Gleb Natapov
2009-11-23 19:19 ` Sebastian Herbszt
2009-11-23 19:43 ` Gleb Natapov
2009-11-23 21:30 ` Sebastian Herbszt
2009-11-24 6:28 ` Gleb Natapov
2009-11-24 14:38 ` Jamie Lokier
2009-11-24 14:40 ` Gleb Natapov
2009-11-25 6:09 ` Jamie Lokier
2009-11-25 12:20 ` Gleb Natapov
2009-11-25 15:31 ` Kevin O'Connor
2009-11-25 16:42 ` Gleb Natapov
2009-11-25 22:11 ` Sebastian Herbszt
2009-11-27 3:00 ` Jamie Lokier
2009-11-27 19:13 ` Sebastian Herbszt
2009-11-25 22:04 ` Sebastian Herbszt
2009-11-25 22:53 ` Kevin O'Connor
2009-11-26 6:49 ` Gleb Natapov
2009-11-26 7:15 ` Kevin O'Connor
2009-11-26 7:20 ` Gleb Natapov
2009-11-26 7:48 ` Kevin O'Connor
2009-11-26 7:56 ` Gleb Natapov
2009-11-26 8:12 ` Kevin O'Connor
2009-11-26 8:19 ` Gleb Natapov
2009-11-26 16:03 ` Kevin O'Connor
2009-11-26 22:35 ` Sebastian Herbszt
2009-11-27 5:39 ` Kevin O'Connor
2009-11-26 6:45 ` Gleb Natapov
2009-11-26 20:55 ` Sebastian Herbszt
2009-11-27 7:44 ` Gleb Natapov
2009-11-27 20:42 ` Sebastian Herbszt
2009-11-29 8:20 ` Gleb Natapov
2009-11-29 22:53 ` Natalia Portillo
2009-11-30 7:12 ` Gleb Natapov
2009-11-30 20:53 ` Jamie Lokier
2009-11-30 21:02 ` Natalia Portillo
2009-12-01 2:16 ` Kevin O'Connor
2009-11-30 20:34 ` Sebastian Herbszt
2009-12-01 9:37 ` Gleb Natapov
2009-11-25 21:08 ` Sebastian Herbszt
2009-11-24 23:27 ` Sebastian Herbszt
2009-11-25 10:48 ` Gleb Natapov [this message]
2009-11-22 15:38 ` Kevin O'Connor
2009-11-23 11:16 ` Gleb Natapov
2009-11-23 17:57 ` Sebastian Herbszt
2009-11-23 18:07 ` Gleb Natapov
2009-11-23 19:12 ` Sebastian Herbszt
2009-11-23 19:18 ` Gleb Natapov
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=20091125104801.GL2999@redhat.com \
--to=gleb@redhat.com \
--cc=herbszt@gmx.de \
--cc=kevin@koconnor.net \
--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).