From: Thomas Huth <thuth@redhat.com>
To: Steffen Eiden <seiden@linux.ibm.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: Janosch Frank <frankja@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Michael Mueller <mimu@linux.vnet.ibm.com>,
Marc Hartmayer <mhartmay@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v3 4/5] target/s390x/kvm: Refactor AP functionalities
Date: Mon, 21 Aug 2023 09:57:14 +0200 [thread overview]
Message-ID: <7c8784a5-5045-8eec-361c-10852b14cd47@redhat.com> (raw)
In-Reply-To: <20230818111520.698615-5-seiden@linux.ibm.com>
On 18/08/2023 13.15, Steffen Eiden wrote:
> kvm_s390_set_attr() is a misleading name as it only sets attributes for
> the KVM_S390_VM_CRYPTO group. Therefore, rename it to
> kvm_s390_set_crypto_attr().
>
> Add new functions ap_available() and ap_enabled() to avoid code
> duplication later.
>
> Reviewed-by: Michael Mueller <mimu@linux.ibm.com>
> Signed-off-by: Steffen Eiden <seiden@linux.ibm.com>
> ---
> target/s390x/kvm/kvm.c | 24 +++++++++++++++++-------
> 1 file changed, 17 insertions(+), 7 deletions(-)
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2023-08-21 7:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 11:15 [PATCH v3 0/5] s390: Enable AP instructions for pv-guests Steffen Eiden
2023-08-18 11:15 ` [PATCH v3 1/5] s390x/ap: fix missing subsystem reset registration Steffen Eiden
2023-08-18 11:15 ` [PATCH v3 2/5] s390x: switch pv and subsystem reset ordering on reboot Steffen Eiden
2023-08-18 11:15 ` [PATCH v3 3/5] NOTFORMERGE update linux-headers/asm-s390/kvm.h Steffen Eiden
2023-08-18 11:15 ` [PATCH v3 4/5] target/s390x/kvm: Refactor AP functionalities Steffen Eiden
2023-08-21 7:57 ` Thomas Huth [this message]
2023-08-18 11:15 ` [PATCH v3 5/5] target/s390x: AP-passthrough for PV guests Steffen Eiden
2023-08-21 8:31 ` Thomas Huth
2023-08-23 8:55 ` Michael Mueller
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=7c8784a5-5045-8eec-361c-10852b14cd47@redhat.com \
--to=thuth@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=mhartmay@linux.ibm.com \
--cc=mimu@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=seiden@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;
as well as URLs for NNTP newsgroup(s).