From: Eric B Munson <emunson@mgebm.net>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org, ryanh@linux.vnet.ibm.com,
aliguori@us.ibm.com, kvm@vger.kernel.org, mtosatti@redhat.com,
linux-kernel@vger.kernel.org, avi@redhat.com
Subject: Re: [PATCH] Guest stop notification
Date: Thu, 1 Dec 2011 12:22:44 -0500 [thread overview]
Message-ID: <20111201172244.GB8803@mgebm.net> (raw)
In-Reply-To: <4ED79138.60603@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 2169 bytes --]
On Thu, 01 Dec 2011, Jan Kiszka wrote:
> On 2011-11-29 22:36, 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.
> >
> > Signed-off-by: Eric B Munson <emunson@mgebm.net>
> > Cc: ryanh@linux.vnet.ibm.com
> > Cc: aliguori@us.ibm.com
> > Cc: mtosatti@redhat.com
> > Cc: avi@redhat.com
> > Cc: kvm@vger.kernel.org
> > Cc: linux-kernel@vger.kernel.org
> > ---
> > target-i386/kvm.c | 6 ++++++
> > 1 files changed, 6 insertions(+), 0 deletions(-)
> >
> > diff --git a/target-i386/kvm.c b/target-i386/kvm.c
> > index 5bfc21f..defd364 100644
> > --- a/target-i386/kvm.c
> > +++ b/target-i386/kvm.c
> > @@ -336,12 +336,18 @@ static int kvm_inject_mce_oldstyle(CPUState *env)
> > return 0;
> > }
> >
> > +static void kvm_put_guest_paused(CPUState *penv)
> > +{
> > + kvm_vcpu_ioctl(penv, KVM_GUEST_PAUSED, 0);
> > +}
>
> I see no need in encapsulating this in a separate function.
>
> > +
> > static void cpu_update_state(void *opaque, int running, RunState state)
> > {
> > CPUState *env = opaque;
> >
> > if (running) {
> > env->tsc_valid = false;
> > + kvm_put_guest_paused(env);
>
> checkpatch.pl would have asked you to remove this tab.
>
> More general:
>
> Why is this x86-only? If the kernel interface is x86-only, what prevents
> making it generic right from the beginning?
Sorry, missed this question on the first pass, this is x86 only because the
flag used lives in the pvclock structure. AFAICT, there aren't any other
architectures out there that implement paravirtualized clocks yet.
>
> Why do we need a new IOCTL for this? Was there no space left in the
> kvm_run structure e.g. to pass this flag down on next vcpu execution? No
> big deal, just wondering.
>
> Jan
>
> --
> Siemens AG, Corporate Technology, CT T DE IT 1
> Corporate Competence Center Embedded Linux
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-12-01 17:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 21:36 Eric B Munson
2011-11-29 22:10 ` Anthony Liguori
2011-12-01 14:37 ` Jan Kiszka
2011-12-01 17:19 ` Eric B Munson
2011-12-01 17:31 ` Arend van Spriel
2011-12-01 17:35 ` Jan Kiszka
2011-12-01 17:35 ` Jan Kiszka
2011-12-01 21:22 ` Marcelo Tosatti
2011-12-01 17:22 ` Eric B Munson [this message]
2011-12-01 17:36 ` Jan Kiszka
2011-12-01 21:25 ` Marcelo Tosatti
2011-12-01 21:32 ` Eric B Munson
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=20111201172244.GB8803@mgebm.net \
--to=emunson@mgebm.net \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®