All of lore.kernel.org
 help / color / mirror / Atom feed
From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, borntraeger@de.ibm.com,
	frankja@linux.ibm.com, pasic@linux.ibm.com,
	mhartmay@linux.ibm.com, david@kernel.org, farman@linux.ibm.com,
	mjrosato@linux.ibm.com, richard.henderson@linaro.org,
	iii@linux.ibm.com, cohuck@redhat.com
Subject: [PATCH v3 0/1] target/s390x: Allow 2G hugepages guest backing
Date: Wed,  5 Aug 2026 12:37:27 +0200	[thread overview]
Message-ID: <20260805103728.97602-1-imbrenda@linux.ibm.com> (raw)

Allow mapping guest with 2G hugepages on hosts that support it.
    
Add new helper functions to check whether hpages are in effect, and
which size.

v2->v3:
* Remove dead code introduced in the previous version.
* Factor out the capability enablement and error reporting to avoid
  duplicating code and error messages.
* Optimize the control flow and bring it back in line with the previous
  behaviour regarding page sizes, i.e. assuming that if the page size
  is neither 4K nor 1M, then it must be 2G.

v1->v2:
* Rename the global variable to cap_hpage
* Use different values of cap_hpage to distinguish between hpage sizes
* Add wrappers to test for specific hpage sizes

Claudio Imbrenda (1):
  target/s390x: Allow 2G hugepages guest backing

 target/s390x/diag.c          |  2 +-
 target/s390x/kvm/kvm.c       | 36 +++++++++++++++++-------------------
 target/s390x/kvm/kvm_s390x.h |  2 +-
 target/s390x/kvm/stubs.c     |  2 +-
 4 files changed, 20 insertions(+), 22 deletions(-)

-- 
2.55.0



             reply	other threads:[~2026-08-05 10:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 10:37 Claudio Imbrenda [this message]
2026-08-05 10:37 ` [PATCH v3 1/1] target/s390x: Allow 2G hugepages guest backing Claudio Imbrenda
2026-08-05 17:17   ` Matthew Rosato
2026-08-10 18:39 ` [PATCH v3 0/1] " Eric Farman

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=20260805103728.97602-1-imbrenda@linux.ibm.com \
    --to=imbrenda@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@kernel.org \
    --cc=farman@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=iii@linux.ibm.com \
    --cc=mhartmay@linux.ibm.com \
    --cc=mjrosato@linux.ibm.com \
    --cc=pasic@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=richard.henderson@linaro.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 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.