From: Andrew Jones <drjones@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, mlevitsk@redhat.com
Subject: Re: [RFC PATCH kvm-unit-tests 0/4] add generic stress test
Date: Tue, 19 Jan 2021 19:40:35 +0100 [thread overview]
Message-ID: <20210119184035.7ayrip27hl2euv3g@kamzik.brq.redhat.com> (raw)
In-Reply-To: <YAcYz4nxVXHKfkXu@google.com>
On Tue, Jan 19, 2021 at 09:37:19AM -0800, Sean Christopherson wrote:
> On Mon, Jan 18, 2021, Andrew Jones wrote:
> > On Thu, Jan 14, 2021 at 12:13:22PM -0800, Sean Christopherson wrote:
> > > On Wed, Jan 13, 2021, Paolo Bonzini wrote:
> > > > On 12/01/21 23:28, Sean Christopherson wrote:
> > > > > What's the biggest hurdle for doing this completely within the unit test
> > > > > framework? Is teaching the framework to migrate a unit test the biggest pain?
> > > >
> > > > Yes, pretty much. The shell script framework would show its limits.
> > > >
> > > > That said, I've always treated run_tests.sh as a utility more than an
> > > > integral part of kvm-unit-tests. There's nothing that prevents a more
> > > > capable framework from parsing unittests.cfg.
> > >
> > > Heh, got anyone you can "volunteer" to create a new framework? One-button
> > > migration testing would be very nice to have. I suspect I'm not the only
> > > contributor that doesn't do migration testing as part of their standard workflow.
> > >
> >
> > We have one-button migration tests already with kvm-unit-tests. Just
> > compile the tests that use the migration framework as standalone
> > tests and then run them directly.
>
> Do those exist/work for x86? I see migration stuff for Arm and PPC, but nothing
> for x86.
Right, we don't have migration tests yet for x86. Of course that's just a
matter of programming... We'll also need to add an x86 __getchar() first.
Thanks,
drew
prev parent reply other threads:[~2021-01-19 21:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 1:08 [RFC PATCH kvm-unit-tests 0/4] add generic stress test Paolo Bonzini
2020-12-23 1:08 ` [PATCH kvm-unit-tests 1/4] libcflat: add a few more runtime functions Paolo Bonzini
2021-01-18 17:34 ` Thomas Huth
2020-12-23 1:08 ` [PATCH kvm-unit-tests 2/4] chaos: add generic stress test Paolo Bonzini
2020-12-23 1:08 ` [PATCH kvm-unit-tests 3/4] chaos: add timer interrupt to the workload Paolo Bonzini
2020-12-23 1:08 ` [PATCH kvm-unit-tests 4/4] chaos: add edu device " Paolo Bonzini
2020-12-28 22:25 ` [RFC PATCH kvm-unit-tests 0/4] add generic stress test Sean Christopherson
2021-01-02 8:46 ` Paolo Bonzini
2021-01-12 22:28 ` Sean Christopherson
2021-01-13 12:13 ` Paolo Bonzini
2021-01-14 20:13 ` Sean Christopherson
2021-01-14 21:12 ` Paolo Bonzini
2021-01-14 22:13 ` Sean Christopherson
2021-01-15 13:15 ` Paolo Bonzini
2021-01-18 11:09 ` Andrew Jones
2021-01-19 17:37 ` Sean Christopherson
2021-01-19 18:40 ` Andrew Jones [this message]
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=20210119184035.7ayrip27hl2euv3g@kamzik.brq.redhat.com \
--to=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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.