From: "Andreas Färber" <afaerber@suse.de>
To: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, KVM <kvm@vger.kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Qemu-devel <qemu-devel@nongnu.org>,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
"Michael J. Wolf" <mjw@linux.vnet.ibm.com>,
Avi Kivity <avi@redhat.com>, Eric B Munson <emunson@mgebm.net>
Subject: Re: [Qemu-devel] [PATCH V8 1/1] Guest stop notificationorry for rduplicate mail
Date: Fri, 06 Apr 2012 23:09:09 +0200 [thread overview]
Message-ID: <4F7F5B75.5020501@suse.de> (raw)
In-Reply-To: <4F7EE91A.9020204@linux.vnet.ibm.com>
Am 06.04.2012 15:01, schrieb Raghavendra K T:
> On 04/06/2012 03:19 PM, Raghavendra K T wrote:
>> On 04/06/2012 02:29 PM, Andreas Färber wrote:
>>> Am 06.04.2012 09:21, schrieb Raghavendra K T:
>>>> From: Eric B Munson<emunson@mgebm.net>
>>>>
>>>> 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>
>>>> Signed-off-by: Raghavendra K T<raghavendra.kt@linux.vnet.ibm.com>
>>>>
>>>> Cc: Eric B Munson<emunson@mgebm.net>
>>>> Cc: Avi Kivity<avi@redhat.com>
>>>> Cc: Marcelo Tosatti<mtosatti@redhat.com>
>>>> Cc: Anthony Liguori<aliguori@us.ibm.com>
>>>> Cc: Jan Kiszka<jan.kiszka@siemens.com>
>>>> Cc: "Andreas FÀrber"<afaerber@suse.de>
>>>> ---
>>>> Changes from V7:
>>>> capabilty changed to KVM_CAP_KVMCLOCK_CTRL
>>>> KVM_GUEST_PAUSED is pervcpu again
>>>> CPUState renamed to CPUArchState
>>>
>>> Thanks, change looks right to me.
>
> I think I should have added Acked-by and resent full patch. So here is
> it. sorry for duplicate mail.
No, it was not intended as such since I can't ack the ioctl. Resends are
best done with git-send-email, i.e. a v9 with change log (whether as
reply or not, opinions are divided) to make sure the right version gets
applied in the end.
> ---
> From: Eric B Munson <emunson@mgebm.net>
>
> 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.
>
> Acked-by: "Andreas Färber" <afaerber@suse.de>
> Signed-off-by: Eric B Munson <emunson@mgebm.net>
> Signed-off-by: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
*-bys should be added in chronological order, i.e. at the bottom.
>
> Cc: Eric B Munson <emunson@mgebm.net>
> Cc: Avi Kivity <avi@redhat.com>
> Cc: Marcelo Tosatti <mtosatti@redhat.com>
> Cc: Anthony Liguori <aliguori@us.ibm.com>
> Cc: Jan Kiszka <jan.kiszka@siemens.com>
> Cc: "Andreas Färber" <afaerber@suse.de>
> ---
> Changes from V7:
> capabilty changed to KVM_CAP_KVMCLOCK_CTRL
> KVM_GUEST_PAUSED is pervcpu again
> CPUState renamed to CPUArchState
> KVMCLOCK_GUEST_PAUSED changed to KVM_KVMCLOCK_CTRL
> incorporated Andrea's comments (__FUNCTION__) etc
>
> 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
> ---
>
> diff --git a/hw/kvm/clock.c b/hw/kvm/clock.c
> index 446bd62..a6aa6e4 100644
> --- a/hw/kvm/clock.c
> +++ b/hw/kvm/clock.c
> @@ -65,9 +65,27 @@ static void kvmclock_vm_state_change(void *opaque,
> int running,
> RunState state)
> {
> KVMClockState *s = opaque;
> + CPUArchState *penv = first_cpu;
> + int cap_clock_ctrl = kvm_check_extension(kvm_state,
> KVM_CAP_KVMCLOCK_CTRL);
> + int ret;
>
> if (running) {
> s->clock_valid = false;
> +
> + if (!cap_clock_ctrl) {
> + return;
> + }
> + for (penv = first_cpu; penv != NULL; penv = penv->next_cpu) {
> + ret = kvm_vcpu_ioctl(penv, KVM_KVMCLOCK_CTRL, 0);
> + if (ret) {
> + if (ret != -EINVAL) {
> + fprintf(stderr,
> + " %s: %s\n", __FUNCTION__,
Is the whitespace before %s intentional? Wasn't there in v8.
The GCC manual recommends __func__, like I suggested, saying it's C99.
http://gcc.gnu.org/onlinedocs/gcc-4.7.0/gcc/Function-Names.html#Function-Names
__FUNCTION__ usage is currently 432 vs. __func__ 579, so not wrong.
If you want to leave it that way you can add my
Reviewed-by: Andreas Färber <afaerber@suse.de>
Andreas
> + strerror(-ret));
> + }
> + return;
> + }
> + }
> }
> }
>
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2012-04-06 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 7:21 [PATCH V8 1/1] Guest stop notification Raghavendra K T
2012-04-06 8:59 ` Andreas Färber
2012-04-06 9:49 ` Raghavendra K T
2012-04-06 13:01 ` [Qemu-devel] [PATCH V8 1/1] Guest stop notificationorry for rduplicate mail Raghavendra K T
2012-04-06 21:09 ` Andreas Färber [this message]
2012-04-07 0:27 ` [Qemu-devel] [PATCH V8 1/1] Guest stop notificationorry for rduplicate mail ndreas Raghavendra K T
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=4F7F5B75.5020501@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=emunson@mgebm.net \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mjw@linux.vnet.ibm.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=raghavendra.kt@linux.vnet.ibm.com \
--cc=vatsa@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.