From: Nico Boehr <nrb@linux.ibm.com>
To: Pierre Morel <pmorel@linux.ibm.com>, linux-s390@vger.kernel.org
Cc: frankja@linux.ibm.com, thuth@redhat.com, kvm@vger.kernel.org,
imbrenda@linux.ibm.com, david@redhat.com, nsg@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v7 2/2] s390x: topology: Checking Configuration Topology Information
Date: Tue, 28 Mar 2023 14:44:23 +0200 [thread overview]
Message-ID: <168000746363.28355.1842312853535506881@t14-nrb> (raw)
In-Reply-To: <3dcfb02a-84db-1298-1b88-810b52c12818@linux.ibm.com>
Quoting Pierre Morel (2023-03-28 13:37:59)
>
> On 3/28/23 08:25, Nico Boehr wrote:
> > Quoting Pierre Morel (2023-03-27 14:38:35)
> >>> [...]
>
>
> [...]
>
>
> >> If a topology level always exist physically and if it is not specified
> >> on the QEMU command line it is implicitly unique.
> > What do you mean by 'implicitly unique'?
>
> I mean that if the topology level is not explicitly specified on the
> command line, it exists a single entity of this topology level.
OK, makes sense! Thanks!
next prev parent reply other threads:[~2023-03-28 12:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 8:56 [kvm-unit-tests PATCH v7 0/2] S390x: CPU Topology Information Pierre Morel
2023-03-20 8:56 ` [kvm-unit-tests PATCH v7 1/2] s390x: topology: Check the Perform Topology Function Pierre Morel
2023-03-23 15:45 ` Claudio Imbrenda
2023-03-27 11:45 ` Pierre Morel
2023-03-24 10:11 ` Nico Boehr
2023-03-27 11:48 ` Pierre Morel
2023-03-20 8:56 ` [kvm-unit-tests PATCH v7 2/2] s390x: topology: Checking Configuration Topology Information Pierre Morel
2023-03-24 10:59 ` Nico Boehr
2023-03-27 12:38 ` Pierre Morel
2023-03-28 6:25 ` Nico Boehr
2023-03-28 11:37 ` Pierre Morel
2023-03-28 12:44 ` Nico Boehr [this message]
2023-03-27 17:02 ` Pierre Morel
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=168000746363.28355.1842312853535506881@t14-nrb \
--to=nrb@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nsg@linux.ibm.com \
--cc=pmorel@linux.ibm.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).