From: Thomas Huth <thuth@redhat.com>
To: Greg Harmon <gharm@google.com>, kvm@vger.kernel.org
Subject: Re: [kvm-unit-tests PATCH] powerpc: Add SPRs migration test
Date: Thu, 14 Apr 2016 10:18:45 +0200 [thread overview]
Message-ID: <570F5265.9030204@redhat.com> (raw)
In-Reply-To: <loom.20160412T231220-984@post.gmane.org>
On 12.04.2016 23:32, Greg Harmon wrote:
> David Gibson <dgibson <at> redhat.com> writes:
>> On Mon, 11 Apr 2016 11:23:46 +0200
>> Thomas Huth <thuth <at> redhat.com> wrote:
>>> On 11.04.2016 03:55, David Gibson wrote:
>>>> On Fri, 8 Apr 2016 13:35:29 +0200
>>>> Thomas Huth <thuth <at> redhat.com> wrote:
>>>>
>>>>> This test can be used to check whether the SPR (special purpose
>>>>> registers) of the PowerPC CPU are migrated right. It first fills
>>>>> the various SPRs with some non-zero value, then reads the values
>>>>> back into a first array, then waits for a key (with the '-w' option)
>>>>> so that it is possible to migrate the VM, and finally reads the
>>>>> values from the SPRs back into another array and then compares it
>>>>> with the initial values.
>
> Hi,
> In order to make this test automated, what if we extend the test device to
> return a save/restore generation number? It can report that in a
> register,and then the test can spin, waiting for that value to increase.
The test device only works on x86, as far as I know, so I'm afraid it's
not usable for this case here on PowerPC.
Thomas
next prev parent reply other threads:[~2016-04-14 8:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 11:35 [kvm-unit-tests PATCH] powerpc: Add SPRs migration test Thomas Huth
2016-04-08 12:14 ` Andrew Jones
2016-04-08 14:08 ` Thomas Huth
2016-04-08 15:20 ` Andrew Jones
2016-04-11 1:55 ` David Gibson
2016-04-11 9:23 ` Thomas Huth
2016-04-12 1:21 ` David Gibson
2016-04-12 21:32 ` Greg Harmon
2016-04-14 8:18 ` Thomas Huth [this message]
2016-04-14 16:43 ` Greg Harmon
2016-04-15 8:43 ` Andrew Jones
2016-04-19 8:20 ` Thomas Huth
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=570F5265.9030204@redhat.com \
--to=thuth@redhat.com \
--cc=gharm@google.com \
--cc=kvm@vger.kernel.org \
/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).