From: Janosch Frank <frankja@linux.ibm.com>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>, kvm@vger.kernel.org
Cc: thuth@redhat.com, david@redhat.com, nrb@linux.ibm.com,
scgl@linux.ibm.com, seiden@linux.ibm.com
Subject: Re: [kvm-unit-tests PATCH v1 0/5] s390x: smp: avoid hardcoded CPU addresses
Date: Thu, 3 Feb 2022 09:45:56 +0100 [thread overview]
Message-ID: <f8f09670-688b-2b12-f09a-860a9edffd54@linux.ibm.com> (raw)
In-Reply-To: <20220128185449.64936-1-imbrenda@linux.ibm.com>
On 1/28/22 19:54, Claudio Imbrenda wrote:
> On s390x there are no guarantees about the CPU addresses, except that
> they shall be unique. This means that in some environments, it's
> possible that there is no match between the CPU address and its
> position (index) in the list of available CPUs returned by the system.
While I support this patch set I've yet to find an environment where
this gave me headaches.
>
> This series fixes a small bug in the SMP initialization code, adds a
> guarantee that the boot CPU will always have index 0, and introduces
> some functions to allow tests to use CPU indexes instead of using
> hardcoded CPU addresses. This will allow the tests to run successfully
> in more environments (e.g. z/VM, LPAR).
I'm wondering if we should do it the other way round and make the smp_*
functions take a idx instead of a cpu addr. The only instance where this
gets a bit ugly is the sigp calls which we would also need to convert.
> Some existing tests are adapted to take advantage of the new
> functionalities.
>
> Claudio Imbrenda (5):
> lib: s390x: smp: add functions to work with CPU indexes
> lib: s390x: smp: guarantee that boot CPU has index 0
> s390x: smp: avoid hardcoded CPU addresses
> s390x: firq: avoid hardcoded CPU addresses
> s390x: skrf: avoid hardcoded CPU addresses
>
> lib/s390x/smp.h | 2 ++
> lib/s390x/smp.c | 28 ++++++++++++-----
> s390x/firq.c | 17 +++++-----
> s390x/skrf.c | 8 +++--
> s390x/smp.c | 83 ++++++++++++++++++++++++++-----------------------
> 5 files changed, 79 insertions(+), 59 deletions(-)
>
next prev parent reply other threads:[~2022-02-03 8:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 18:54 [kvm-unit-tests PATCH v1 0/5] s390x: smp: avoid hardcoded CPU addresses Claudio Imbrenda
2022-01-28 18:54 ` [kvm-unit-tests PATCH v1 1/5] lib: s390x: smp: add functions to work with CPU indexes Claudio Imbrenda
2022-01-31 13:50 ` David Hildenbrand
2022-02-02 16:55 ` Steffen Eiden
2022-02-03 13:33 ` Claudio Imbrenda
2022-01-28 18:54 ` [kvm-unit-tests PATCH v1 2/5] lib: s390x: smp: guarantee that boot CPU has index 0 Claudio Imbrenda
2022-01-31 13:55 ` David Hildenbrand
2022-02-03 11:41 ` Claudio Imbrenda
2022-01-28 18:54 ` [kvm-unit-tests PATCH v1 3/5] s390x: smp: avoid hardcoded CPU addresses Claudio Imbrenda
2022-01-28 18:54 ` [kvm-unit-tests PATCH v1 4/5] s390x: firq: " Claudio Imbrenda
2022-01-28 18:54 ` [kvm-unit-tests PATCH v1 5/5] s390x: skrf: " Claudio Imbrenda
2022-02-03 8:45 ` Janosch Frank [this message]
2022-02-03 13:37 ` [kvm-unit-tests PATCH v1 0/5] s390x: smp: " Claudio Imbrenda
2022-02-03 15:23 ` Janosch Frank
2022-02-03 15:48 ` Claudio Imbrenda
2022-02-04 15:01 ` Janosch Frank
2022-02-04 15:14 ` Claudio Imbrenda
2022-02-04 15:37 ` Janosch Frank
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=f8f09670-688b-2b12-f09a-860a9edffd54@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=scgl@linux.ibm.com \
--cc=seiden@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).