From: Laurent Vivier <lvivier@redhat.com>
To: Thomas Huth <thuth@redhat.com>, kvm-ppc@vger.kernel.org
Cc: kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [RFC kvm-unit-tests PATCH] powerpc: add tests for XICS
Date: Mon, 16 Oct 2017 17:08:03 +0000 [thread overview]
Message-ID: <5c29e3a9-0ceb-79b3-3bdb-e6e0d20ea4d9@redhat.com> (raw)
In-Reply-To: <ec8a4d24-dff5-4964-c66b-2df864631616@redhat.com>
On 13/10/2017 11:45, Thomas Huth wrote:
> On 12.10.2017 10:07, Laurent Vivier wrote:
>> Check if we can set the xive server and priority, and
>> check we get values that have been set.
>> Check we disable/enable interrupts.
>>
>> This patch also increases NR_CPUS from 8 to 16
>> (maximum for KVM on POWER9, POWER8 allows 96)
>>
>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>> ---
>> Note: I send this as an RFC, because even if this test works well with
>> TCG and POWER8 KVM hosts, it detects some problems with POWER9 KVM hosts
>
> What kind of errors does it detect? Are they expected due to the
> different interrupt controllers?
>
>> main(int argc, char **argv)
>>
>> check_set_time_of_day();
>>
>> + } else if (strcmp(argv[1], "xics") = 0) {
>> +
>
> Superfluous empty line?
>
>> + check_xics();
>> +
This is a standard pattern in kvm-unit-tests:
...
} else if (strcmp(argv[1], "XXXX") = 0) {
function(...);
} else if (strcmp(argv[1], "YYY") = 0) {
...
Laurent
next prev parent reply other threads:[~2017-10-16 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 8:07 [RFC PATCH] powerpc: add tests for XICS Laurent Vivier
2017-10-13 9:45 ` [RFC kvm-unit-tests " Thomas Huth
2017-10-16 12:34 ` Laurent Vivier
2017-11-22 12:39 ` Laurent Vivier
2017-11-23 4:52 ` Benjamin Herrenschmidt
2017-10-16 17:08 ` Laurent Vivier [this message]
2017-10-18 8:11 ` Andrew Jones
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=5c29e3a9-0ceb-79b3-3bdb-e6e0d20ea4d9@redhat.com \
--to=lvivier@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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