public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Hendrik Brueckner <brueckner@linux.ibm.com>
To: Eric Farman <farman@linux.ibm.com>
Cc: Christian Borntraeger <borntraeger@linux.ibm.com>,
	Hendrik Brueckner <brueckner@linux.ibm.com>,
	Janosch Frank <frankja@linux.ibm.com>,
	Claudio Imbrenda <imbrenda@linux.ibm.com>,
	David Hildenbrand <david@kernel.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: Re: [PATCH v2 1/4] KVM: s390: vsie: Allow non-zarch guests
Date: Wed, 1 Apr 2026 19:45:30 +0200	[thread overview]
Message-ID: <ac1ZuhOhDuC_BDRo@linux.ibm.com> (raw)
In-Reply-To: <20260401151221.2272408-2-farman@linux.ibm.com>

On Wed, Apr 01, 2026 at 05:12:18PM +0200, Eric Farman wrote:
> Linux/KVM runs in z/Architecture-only mode. Although z/Architecture
> is built upon a long history of hardware refinements, any other
> CPU mode is not permitted.
> 
> Allow a userspace to explicitly enable the use of ESA mode for
> nested guests, otherwise usage will be rejected.
> 
> Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
> Signed-off-by: Eric Farman <farman@linux.ibm.com>

Reviewed-by: Hendrik Brueckner <brueckner@linux.ibm.com>

  parent reply	other threads:[~2026-04-01 17:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 15:12 [PATCH v2 0/4] KVM: s390: Permit ESA mode guests in VSIE Eric Farman
2026-04-01 15:12 ` [PATCH v2 1/4] KVM: s390: vsie: Allow non-zarch guests Eric Farman
2026-04-01 15:17   ` Christian Borntraeger
2026-04-01 17:45   ` Hendrik Brueckner [this message]
2026-04-01 15:12 ` [PATCH v2 2/4] KVM: s390: vsie: Disable some bits when in ESA mode Eric Farman
2026-04-01 17:48   ` Hendrik Brueckner
2026-04-01 15:12 ` [PATCH v2 3/4] KVM: s390: vsie: Accommodate ESA prefix pages Eric Farman
2026-04-01 17:51   ` Hendrik Brueckner
2026-04-01 15:12 ` [PATCH v2 4/4] KVM: s390: Add KVM capability for ESA mode guests 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=ac1ZuhOhDuC_BDRo@linux.ibm.com \
    --to=brueckner@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=farman@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=pbonzini@redhat.com \
    --cc=skhan@linuxfoundation.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