From: "Nico Boehr" <nrb@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 4/5] lib: s390x: snippet: Add function to create a guest of specific length
Date: Thu, 16 Apr 2026 09:50:52 +0200 [thread overview]
Message-ID: <DHUEYN8UX70O.1GM62DLEDMNKZ@linux.ibm.com> (raw)
In-Reply-To: <20260415085145.91197-5-frankja@linux.ibm.com>
On Wed Apr 15, 2026 at 10:45 AM CEST, Janosch Frank wrote:
> While 1MB is certainly enough to store the guest code, it's often not
> enough for memory tests. Let's add a separate function to allow
> arbitrary guest sizes.
>
> Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
Reviewed-by: Nico Boehr <nrb@linux.ibm.com>
next prev parent reply other threads:[~2026-04-16 7:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 8:45 [kvm-unit-tests 0/5] s390x: Cleanup virtualization library Janosch Frank
2026-04-15 8:45 ` [kvm-unit-tests 1/5] lib: s390x: Add function to get page root Janosch Frank
2026-04-15 11:53 ` Nico Boehr
2026-04-15 12:01 ` Janosch Frank
2026-04-15 8:45 ` [kvm-unit-tests 2/5] lib: s390x: sie: Allocate physical guest memory via memalign Janosch Frank
2026-04-15 8:45 ` [kvm-unit-tests 3/5] lib: s390x: sie: Free guest memory on destroy Janosch Frank
2026-04-15 14:21 ` Nico Boehr
2026-04-16 8:03 ` Janosch Frank
2026-04-16 10:24 ` Nico Boehr
2026-04-15 8:45 ` [kvm-unit-tests 4/5] lib: s390x: snippet: Add function to create a guest of specific length Janosch Frank
2026-04-16 7:50 ` Nico Boehr [this message]
2026-04-15 8:45 ` [kvm-unit-tests 5/5] lib: s390x: Remove kvm s390 prefix from sie control block Janosch Frank
2026-04-16 7:48 ` Nico Boehr
2026-04-16 8:00 ` 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=DHUEYN8UX70O.1GM62DLEDMNKZ@linux.ibm.com \
--to=nrb@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 \
/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