From: Avi Kivity <avi@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 2/3] Don't return to guest after CPU issued S3 command.
Date: Tue, 30 Dec 2008 13:19:22 +0200 [thread overview]
Message-ID: <495A03BA.5060701@redhat.com> (raw)
In-Reply-To: <20081230103723.5604.46564.stgit@dhcp-1-237.tlv.redhat.com>
Gleb Natapov wrote:
> Signed-off-by: Gleb Natapov <gleb@redhat.com>
> ---
>
> qemu/hw/acpi.c | 2 +-
> qemu/qemu-kvm.c | 2 +-
> qemu/qemu-kvm.h | 1 +
> 3 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/qemu/hw/acpi.c b/qemu/hw/acpi.c
> index 0ff8851..219d8ac 100644
> --- a/qemu/hw/acpi.c
> +++ b/qemu/hw/acpi.c
> @@ -159,7 +159,7 @@ static void pm_ioport_writew(void *opaque, uint32_t addr, uint32_t val)
> /* RSM_STS should be set on resume. Pretend that resume
> was caused by power button */
> s->pmsts |= (RSM_STS | PWRBTN_STS);
> - qemu_system_reset_request();
> + kvm_shutdown(NULL, cpu_single_env);
>
if (kvm_enabled)()?
But I think a qemu API is called for here, not a kvm specific API.
> +int kvm_shutdown(void *opaque, void *data);
That's a bad API. What's the opaque? what's the data?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-12-30 11:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 10:37 [PATCH 0/3] Remaining S3 bits Gleb Natapov
2008-12-30 10:37 ` [PATCH 1/3] Reset stack pointer to zero on S3 resume Gleb Natapov
2008-12-30 10:37 ` [PATCH 2/3] Don't return to guest after CPU issued S3 command Gleb Natapov
2008-12-30 11:19 ` Avi Kivity [this message]
2008-12-30 12:32 ` Gleb Natapov
2008-12-30 13:25 ` Avi Kivity
2008-12-30 10:37 ` [PATCH 3/3] KVM does not support SMM. Disable it Gleb Natapov
2008-12-30 11:25 ` [PATCH 0/3] Remaining S3 bits Avi Kivity
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=495A03BA.5060701@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.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