public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, cohuck@redhat.com, borntraeger@de.ibm.com
Subject: Re: [kvm-unit-tests PATCH] s390x: Add stsi 3.2.2 tests
Date: Mon, 30 Mar 2020 15:09:54 +0200	[thread overview]
Message-ID: <727e1ed5-99ea-e559-ca9c-0f067cbcc153@linux.ibm.com> (raw)
In-Reply-To: <d42ac187-9f8f-81eb-c9b4-4d585fdef236@linux.ibm.com>


[-- Attachment #1.1: Type: text/plain, Size: 767 bytes --]

On 3/30/20 3:03 PM, Janosch Frank wrote:
> On 3/30/20 2:50 PM, David Hildenbrand wrote:
>> On 30.03.20 14:20, Janosch Frank wrote:
>>> +	report(data->vm[0].total_cpus == smp_query_num_cpus(), "cpu # total");
>>> +	report(data->vm[0].conf_cpus == smp_query_num_cpus(), "cpu # configured");
>>> +	report(data->vm[0].standby_cpus == 0, "cpu # standby");
>>> +	report(data->vm[0].reserved_cpus == 0, "cpu # reserved");
>>
>> IIRC, using -smp 1,maxcpus=X, you could also test the reported reserved
>> CPUs.
> 
> Will try that

Just like I thought, QEMU does not manipulate cpu counts and KVM
pre-sets standby and reserved to 0. So we have absolutely no change when
adding the smp parameter.

> 
>>
>>
>> Also passes under TCG, nice :)
>>
> 
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-03-30 13:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-30 12:20 [kvm-unit-tests PATCH] s390x: Add stsi 3.2.2 tests Janosch Frank
2020-03-30 12:50 ` David Hildenbrand
2020-03-30 13:03   ` Janosch Frank
2020-03-30 13:09     ` Janosch Frank [this message]
2020-03-30 13:15       ` David Hildenbrand
2020-03-30 13:30         ` Janosch Frank
2020-03-30 14:00           ` David Hildenbrand
2020-03-30 14:13           ` Christian Borntraeger
2020-03-30 12:51 ` David Hildenbrand
2020-03-30 13:00   ` Janosch Frank
2020-03-30 13:14     ` David Hildenbrand

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=727e1ed5-99ea-e559-ca9c-0f067cbcc153@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@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