From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: ryanh@linux.vnet.ibm.com, kvm@vger.kernel.org,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>,
Avi Kivity <avi@redhat.com>, Eric B Munson <emunson@mgebm.net>
Subject: Re: [PATCH V7] Guest stop notification
Date: Fri, 27 Jan 2012 22:49:13 +0100 [thread overview]
Message-ID: <4F231BD9.70302@web.de> (raw)
In-Reply-To: <4F230D9A.8020502@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 2945 bytes --]
On 2012-01-27 21:48, Anthony Liguori wrote:
> On 01/17/2012 12:27 PM, Eric B Munson wrote:
>> Often when a guest is stopped from the qemu console, it will report
>> spurious
>> soft lockup warnings on resume. There are kernel patches being
>> discussed that
>> will give the host the ability to tell the guest that it is being
>> stopped and
>> should ignore the soft lockup warning that generates. This patch uses
>> the qemu
>> Notifier system to tell the guest it is about to be stopped.
>>
>> Signed-off-by: Eric B Munson<emunson@mgebm.net>
>>
>> Cc: Avi Kivity<avi@redhat.com>
>> Cc: Marcelo Tosatti<mtosatti@redhat.com>
>> Cc: Jan Kiszka<jan.kiszka@siemens.com>
>> Cc: ryanh@linux.vnet.ibm.com
>> Cc: aliguori@us.ibm.com
>> Cc: kvm@vger.kernel.org
>> ---
>> Changes from V6:
>> Remove unnecessary include
>>
>> Changes from V5:
>> KVM_GUEST_PAUSED is now a per vm ioctl instead of per vcpu
>>
>> Changes from V4:
>> Test if the guest paused capability is available before use
>>
>> Changes from V3:
>> Collapse new state change notification function into existsing
>> function.
>> Correct whitespace issues
>> Change ioctl name to KVMCLOCK_GUEST_PAUSED
>> Use for loop to iterate vpcu's
>>
>> Changes from V2:
>> Move ioctl into hw/kvmclock.c so as other arches can use it as it is
>> implemented
>>
>> Changes from V1:
>> Remove unnecessary encapsulating function
>>
>> hw/kvmclock.c | 11 +++++++++++
>> 1 files changed, 11 insertions(+), 0 deletions(-)
>>
>> diff --git a/hw/kvmclock.c b/hw/kvmclock.c
>> index 3b9fb20..ad79f52 100644
>> --- a/hw/kvmclock.c
>> +++ b/hw/kvmclock.c
>> @@ -64,10 +64,21 @@ static int kvmclock_post_load(void *opaque, int
>> version_id)
>> static void kvmclock_vm_state_change(void *opaque, int running,
>> RunState state)
>> {
>> + int ret;
>> KVMClockState *s = opaque;
>> + int cap_guest_paused = kvm_check_extension(kvm_state,
>> KVM_CAP_GUEST_PAUSED);
>>
>> if (running) {
>> s->clock_valid = false;
>> +
>> + if (!cap_guest_paused) {
>> + return;
>> + }
>> +
>> + ret = kvm_vm_ioctl(kvm_state, KVMCLOCK_GUEST_PAUSED, 0);
>> + if (ret) {
>> + fprintf(stderr, "kvmclock_vm_state_change: %s\n",
>> strerror(-ret));
>> + }
>> }
>> }
>
>
> This change looks harmless enough.
Yep, but needs to be redirected after the file renaming in upstream.
> What's the state of the kernel
> bits? I would expect this through uq/master.
Kernel bits aren't merged yet. And the kernel headers will have to be
updated in a previous step.
BTW, this series [1] would be nice to have. Dunno if there is a pull
planned, but anyone trying to extend the KVM interface current runs
against this.
Jan
[1] http://thread.gmane.org/gmane.comp.emulators.qemu/132962
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: ryanh@linux.vnet.ibm.com, kvm@vger.kernel.org,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>,
Avi Kivity <avi@redhat.com>, Eric B Munson <emunson@mgebm.net>
Subject: Re: [Qemu-devel] [PATCH V7] Guest stop notification
Date: Fri, 27 Jan 2012 22:49:13 +0100 [thread overview]
Message-ID: <4F231BD9.70302@web.de> (raw)
In-Reply-To: <4F230D9A.8020502@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 2945 bytes --]
On 2012-01-27 21:48, Anthony Liguori wrote:
> On 01/17/2012 12:27 PM, Eric B Munson wrote:
>> Often when a guest is stopped from the qemu console, it will report
>> spurious
>> soft lockup warnings on resume. There are kernel patches being
>> discussed that
>> will give the host the ability to tell the guest that it is being
>> stopped and
>> should ignore the soft lockup warning that generates. This patch uses
>> the qemu
>> Notifier system to tell the guest it is about to be stopped.
>>
>> Signed-off-by: Eric B Munson<emunson@mgebm.net>
>>
>> Cc: Avi Kivity<avi@redhat.com>
>> Cc: Marcelo Tosatti<mtosatti@redhat.com>
>> Cc: Jan Kiszka<jan.kiszka@siemens.com>
>> Cc: ryanh@linux.vnet.ibm.com
>> Cc: aliguori@us.ibm.com
>> Cc: kvm@vger.kernel.org
>> ---
>> Changes from V6:
>> Remove unnecessary include
>>
>> Changes from V5:
>> KVM_GUEST_PAUSED is now a per vm ioctl instead of per vcpu
>>
>> Changes from V4:
>> Test if the guest paused capability is available before use
>>
>> Changes from V3:
>> Collapse new state change notification function into existsing
>> function.
>> Correct whitespace issues
>> Change ioctl name to KVMCLOCK_GUEST_PAUSED
>> Use for loop to iterate vpcu's
>>
>> Changes from V2:
>> Move ioctl into hw/kvmclock.c so as other arches can use it as it is
>> implemented
>>
>> Changes from V1:
>> Remove unnecessary encapsulating function
>>
>> hw/kvmclock.c | 11 +++++++++++
>> 1 files changed, 11 insertions(+), 0 deletions(-)
>>
>> diff --git a/hw/kvmclock.c b/hw/kvmclock.c
>> index 3b9fb20..ad79f52 100644
>> --- a/hw/kvmclock.c
>> +++ b/hw/kvmclock.c
>> @@ -64,10 +64,21 @@ static int kvmclock_post_load(void *opaque, int
>> version_id)
>> static void kvmclock_vm_state_change(void *opaque, int running,
>> RunState state)
>> {
>> + int ret;
>> KVMClockState *s = opaque;
>> + int cap_guest_paused = kvm_check_extension(kvm_state,
>> KVM_CAP_GUEST_PAUSED);
>>
>> if (running) {
>> s->clock_valid = false;
>> +
>> + if (!cap_guest_paused) {
>> + return;
>> + }
>> +
>> + ret = kvm_vm_ioctl(kvm_state, KVMCLOCK_GUEST_PAUSED, 0);
>> + if (ret) {
>> + fprintf(stderr, "kvmclock_vm_state_change: %s\n",
>> strerror(-ret));
>> + }
>> }
>> }
>
>
> This change looks harmless enough.
Yep, but needs to be redirected after the file renaming in upstream.
> What's the state of the kernel
> bits? I would expect this through uq/master.
Kernel bits aren't merged yet. And the kernel headers will have to be
updated in a previous step.
BTW, this series [1] would be nice to have. Dunno if there is a pull
planned, but anyone trying to extend the KVM interface current runs
against this.
Jan
[1] http://thread.gmane.org/gmane.comp.emulators.qemu/132962
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-01-27 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 18:27 [PATCH V7] Guest stop notification Eric B Munson
2012-01-17 18:27 ` [Qemu-devel] " Eric B Munson
2012-01-27 20:46 ` Eric B Munson
2012-01-27 20:46 ` [Qemu-devel] " Eric B Munson
2012-01-27 20:48 ` Anthony Liguori
2012-01-27 20:48 ` Anthony Liguori
2012-01-27 21:49 ` Jan Kiszka [this message]
2012-01-27 21:49 ` Jan Kiszka
2012-01-28 2:39 ` Alexander Graf
2012-01-28 2:39 ` [Qemu-devel] " Alexander Graf
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=4F231BD9.70302@web.de \
--to=jan.kiszka@web.de \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=emunson@mgebm.net \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ryanh@linux.vnet.ibm.com \
/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.