From: David Hildenbrand <david@redhat.com>
To: Christoph Schlameuss <schlameuss@linux.ibm.com>, kvm@vger.kernel.org
Cc: Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Nico Boehr <nrb@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH RFC 1/5] KVM: s390: Add vsie_sigpif detection
Date: Tue, 18 Mar 2025 23:26:51 +0100 [thread overview]
Message-ID: <0a2e2784-7b5e-47b9-b7f3-59b0e471640d@redhat.com> (raw)
In-Reply-To: <20250318-vsieie-v1-1-6461fcef3412@linux.ibm.com>
On 18.03.25 19:59, Christoph Schlameuss wrote:
> Add sensing of the VSIE Interpretation Extension Facility as vsie_sigpif
> from SCLP. This facility is introduced with IBM Z gen17.
>
> Signed-off-by: Christoph Schlameuss <schlameuss@linux.ibm.com>
> Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
> Reviewed-by: Hendrik Brueckner <brueckner@linux.ibm.com>
> ---
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-03-18 22:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 18:59 [PATCH RFC 0/5] KVM: s390: Add VSIE Interpretation Extension Facility (vsie_sigpif) Christoph Schlameuss
2025-03-18 18:59 ` [PATCH RFC 1/5] KVM: s390: Add vsie_sigpif detection Christoph Schlameuss
2025-03-18 22:26 ` David Hildenbrand [this message]
2025-03-18 18:59 ` [PATCH RFC 2/5] KVM: s390: Add ssca_block and ssca_entry structs for vsie_ie Christoph Schlameuss
2025-03-18 18:59 ` [PATCH RFC 3/5] KVM: s390: Shadow VSIE SCA in guest-1 Christoph Schlameuss
2025-03-19 13:41 ` Janosch Frank
2025-03-19 14:41 ` Christoph Schlameuss
2025-03-19 16:02 ` Janosch Frank
2025-03-20 15:22 ` Nico Boehr
2025-03-20 17:46 ` Christoph Schlameuss
2025-03-18 18:59 ` [PATCH RFC 4/5] KVM: s390: Re-init SSCA on switch to ESCA Christoph Schlameuss
2025-03-18 18:59 ` [PATCH RFC 5/5] KVM: s390: Add VSIE shadow stat counters 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=0a2e2784-7b5e-47b9-b7f3-59b0e471640d@redhat.com \
--to=david@redhat.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 \
--cc=pbonzini@redhat.com \
--cc=schlameuss@linux.ibm.com \
--cc=svens@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox