From: "Christoph Schlameuss" <schlameuss@linux.ibm.com>
To: "Janosch Frank" <frankja@linux.ibm.com>, <kvm@vger.kernel.org>
Cc: <linux-s390@vger.kernel.org>, <imbrenda@linux.ibm.com>,
<borntraeger@linux.ibm.com>, <nrb@linux.ibm.com>
Subject: Re: [kvm-unit-tests PATCH v2 1/4] lib: s390x: Add function to get page root
Date: Tue, 21 Apr 2026 17:12:27 +0200 [thread overview]
Message-ID: <DHYXHGUPI6PB.15M7IL9UYO69D@linux.ibm.com> (raw)
In-Reply-To: <20260420084933.251244-2-frankja@linux.ibm.com>
On Mon Apr 20, 2026 at 10:44 AM CEST, Janosch Frank wrote:
> It's time to hide the access to cr1 behind a function and add typing
> to the tests that used void* instead of pgdt_t*.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Reviewed-by: Christoph Schlameuss <schlameuss@linux.ibm.com>
> ---
> lib/s390x/mmu.h | 7 +++++++
> lib/s390x/sie.c | 3 ++-
> s390x/diag258.c | 4 ++--
> s390x/edat.c | 5 +++--
> s390x/mvpg-sie.c | 2 +-
> s390x/pv-edat1.c | 4 ++--
> s390x/sie-dat.c | 2 +-
> s390x/skey.c | 7 +++----
> 8 files changed, 21 insertions(+), 13 deletions(-)
next prev parent reply other threads:[~2026-04-21 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 8:44 [kvm-unit-tests PATCH v2 0/4] s390x: Cleanup virtualization library Janosch Frank
2026-04-20 8:44 ` [kvm-unit-tests PATCH v2 1/4] lib: s390x: Add function to get page root Janosch Frank
2026-04-21 15:12 ` Christoph Schlameuss [this message]
2026-04-22 6:02 ` Nico Boehr
2026-04-20 8:44 ` [kvm-unit-tests PATCH v2 2/4] lib: s390x: sie: Allocate physical guest memory via memalign Janosch Frank
2026-04-21 15:16 ` Christoph Schlameuss
2026-04-21 15:31 ` Christoph Schlameuss
2026-04-22 6:04 ` Nico Boehr
2026-04-20 8:44 ` [kvm-unit-tests PATCH v2 3/4] lib: s390x: sie: Memory rework Janosch Frank
2026-04-21 15:25 ` Christoph Schlameuss
2026-04-20 8:44 ` [kvm-unit-tests PATCH v2 4/4] lib: s390x: snippet: Add function to create a guest of specific length Janosch Frank
2026-04-21 15:30 ` Christoph Schlameuss
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=DHYXHGUPI6PB.15M7IL9UYO69D@linux.ibm.com \
--to=schlameuss@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.