qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	David Gibson <david@gibson.dropbear.id.au>,
	qemu-ppc@nongnu.org, Laurent Vivier <lvivier@redhat.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, Andrea Arcangeli <aarcange@redhat.com>,
	Eric Blake <eblake@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] tests/postcopy: Use KVM on ppc64 only if it is KVM-HV
Date: Wed, 16 Nov 2016 13:37:56 +0100	[thread overview]
Message-ID: <20161116133756.76854958@bahia> (raw)
In-Reply-To: <20161116122450.GC2050@work-vm>

On Wed, 16 Nov 2016 12:24:50 +0000
"Dr. David Alan Gilbert" <dgilbert@redhat.com> wrote:

> * Greg Kurz (groug@kaod.org) wrote:
> > On Wed, 16 Nov 2016 09:39:31 +0100
> > Thomas Huth <thuth@redhat.com> wrote:
> >   
> > > The ppc64 postcopy test does not work with KVM-PR, and it is also
> > > causing annoying warning messages when run on a x86 host. So let's
> > > use KVM here only if we know that we're running with KVM-HV (which
> > > automatically also means that we're running on a ppc64 host), and
> > > fall back to TCG otherwise.
> > >   
> > 
> > This patch addresses two issues actually:
> > - the annoying warning when running on a ppc64 guest on a non-ppc64 host
> > - the fact that KVM-PR seems to be currently broken
> > 
> > I agree that the former makes sense, but what about the case of running
> > a x86 guest on a non-x86 host ?
> > 
> > I'm still feeling uncomfortable with the KVM-PR case... is this a workaround
> > we want to keep until we find out what's going on or are we starting to
> > partially deprecate KVM PR ? In any case, I guess we should document this
> > and probably print some meaningful error message.  
> 
> This is certainly a work around for now, it doesn't suggest anything about
> deprecation.
> 

Well it doesn't suggest anything actually, it just silently skips KVM PR...
I would at least expect a comment in the code mentioning this is a
workaround and maybe an explicit warning for the user. If the user really
wants to run this test with KVM on ppc64, then she should ensure it is
KVM HV.

Cheers.

--
Greg

> Dave
> 
> > > Signed-off-by: Thomas Huth <thuth@redhat.com>
> > > ---
> > >  tests/postcopy-test.c | 12 ++++++++----
> > >  1 file changed, 8 insertions(+), 4 deletions(-)
> > > 
> > > diff --git a/tests/postcopy-test.c b/tests/postcopy-test.c
> > > index d6613c5..dafe8be 100644
> > > --- a/tests/postcopy-test.c
> > > +++ b/tests/postcopy-test.c
> > > @@ -380,17 +380,21 @@ static void test_migrate(void)
> > >                                    " -incoming %s",
> > >                                    tmpfs, bootpath, uri);
> > >      } else if (strcmp(arch, "ppc64") == 0) {
> > > +        const char *accel;
> > > +
> > > +        /* On ppc64, the test only works with kvm-hv, but not with kvm-pr */
> > > +        accel = access("/sys/module/kvm_hv", F_OK) ? "tcg" : "kvm:tcg";
> > >          init_bootfile_ppc(bootpath);
> > > -        cmd_src = g_strdup_printf("-machine accel=kvm:tcg -m 256M"
> > > +        cmd_src = g_strdup_printf("-machine accel=%s -m 256M"
> > >                                    " -name pcsource,debug-threads=on"
> > >                                    " -serial file:%s/src_serial"
> > >                                    " -drive file=%s,if=pflash,format=raw",
> > > -                                  tmpfs, bootpath);
> > > -        cmd_dst = g_strdup_printf("-machine accel=kvm:tcg -m 256M"
> > > +                                  accel, tmpfs, bootpath);
> > > +        cmd_dst = g_strdup_printf("-machine accel=%s -m 256M"
> > >                                    " -name pcdest,debug-threads=on"
> > >                                    " -serial file:%s/dest_serial"
> > >                                    " -incoming %s",
> > > -                                  tmpfs, uri);
> > > +                                  accel, tmpfs, uri);
> > >      } else {
> > >          g_assert_not_reached();
> > >      }  
> >   
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2016-11-16 12:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-16  8:39 [Qemu-devel] [PATCH] tests/postcopy: Use KVM on ppc64 only if it is KVM-HV Thomas Huth
2016-11-16  9:19 ` Laurent Vivier
2016-11-16  9:43   ` Thomas Huth
2016-11-16 10:37 ` Laurent Vivier
2016-11-16 12:13 ` Greg Kurz
2016-11-16 12:24   ` Dr. David Alan Gilbert
2016-11-16 12:37     ` Greg Kurz [this message]
2016-11-16 13:17       ` Thomas Huth
2016-11-16 14:17         ` Greg Kurz
2016-11-17 20:22           ` Laurent Vivier
2016-11-18 12:53             ` Greg Kurz
2016-11-18 13:03               ` Laurent Vivier
2016-11-17  3:13         ` David Gibson
2016-11-16 14:18 ` Greg Kurz
2016-11-17  3:18 ` [Qemu-devel] [Qemu-ppc] " David Gibson
2016-11-17  7:46   ` Laurent Vivier

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=20161116133756.76854958@bahia \
    --to=groug@kaod.org \
    --cc=aarcange@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=dgilbert@redhat.com \
    --cc=eblake@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).