From: Paolo Bonzini <pbonzini@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Jordan Justen <jordan.l.justen@intel.com>,
Kevin O'Connor <kevin@koconnor.net>,
Jordan Justen <jljusten@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v7 1/4] isapc: Fix non-KVM qemu boot (read/write memory for isapc BIOS)
Date: Fri, 31 May 2013 14:48:27 +0200 [thread overview]
Message-ID: <51A89C1B.80700@redhat.com> (raw)
In-Reply-To: <51A89A29.4090004@redhat.com>
Il 31/05/2013 14:40, Laszlo Ersek ha scritto:
> I think we've been here before...
>
> - always resetting the PAM registers broke S3 resume:
> http://thread.gmane.org/gmane.comp.emulators.qemu/195931/focus=195932
> http://thread.gmane.org/gmane.comp.emulators.qemu/195931/focus=196081
>
> - there was a patch to distinguish soft reset from hard reset:
> http://thread.gmane.org/gmane.comp.emulators.qemu/195351
This is still planned, but it won't touch the PAM registers so as not to
break S3. Peter Stuge said that the memory controller registers keep
their content across S3 in real machines too.
> - another approach for soft vs. hard, and how it relates to resume:
> http://thread.gmane.org/gmane.comp.emulators.qemu/198545/focus=198546
>
> I believe currently qemu doesn't distinguish soft from hard reset. Hard
> reset would have to reset PAM registers, soft reset must not.
Hard reset = powerdown, soft reset = reset or S3.
QEMU only cares about soft reset. There is one case where that matters,
which is "-no-shutdown -no-reboot". Here you can go to S4 or S5 and
then type "cont", and the machine will behave as if you actually did a
soft reset. I don't think it matters much in practice, though.
Paolo
next prev parent reply other threads:[~2013-05-31 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 8:27 [Qemu-devel] [PATCH v7 0/4] KVM flash memory support Jordan Justen
2013-05-29 8:27 ` [Qemu-devel] [PATCH v7 1/4] isapc: Fix non-KVM qemu boot (read/write memory for isapc BIOS) Jordan Justen
2013-05-31 2:06 ` Kevin O'Connor
2013-05-31 4:41 ` Jordan Justen
2013-05-31 12:40 ` Laszlo Ersek
2013-05-31 12:48 ` Paolo Bonzini [this message]
2013-05-31 12:48 ` Paolo Bonzini
2013-06-01 3:44 ` Kevin O'Connor
2013-05-29 8:27 ` [Qemu-devel] [PATCH v7 2/4] kvm: add kvm_readonly_mem_enabled Jordan Justen
2013-05-29 8:27 ` [Qemu-devel] [PATCH v7 3/4] kvm: support using KVM_MEM_READONLY flag for regions Jordan Justen
2013-05-29 8:27 ` [Qemu-devel] [PATCH v7 4/4] pc_sysfw: allow flash (-pflash) memory to be used with KVM Jordan Justen
2013-05-31 18:48 ` [Qemu-devel] [PATCH v7 0/4] KVM flash memory support Anthony Liguori
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=51A89C1B.80700@redhat.com \
--to=pbonzini@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jljusten@gmail.com \
--cc=jordan.l.justen@intel.com \
--cc=kevin@koconnor.net \
--cc=lersek@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.