From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: "Nico Boehr" <nrb@linux.ibm.com>
Cc: <linux-kernel@vger.kernel.org>, <kvm@vger.kernel.org>,
<linux-s390@vger.kernel.org>, <frankja@linux.ibm.com>,
<borntraeger@de.ibm.com>, <seiden@linux.ibm.com>,
<nsg@linux.ibm.com>, <david@redhat.com>, <hca@linux.ibm.com>,
<agordeev@linux.ibm.com>, <svens@linux.ibm.com>,
<gor@linux.ibm.com>, <schlameuss@linux.ibm.com>
Subject: Re: [PATCH v2 3/5] KVM: s390: refactor some functions in priv.c
Date: Tue, 27 May 2025 11:14:44 +0200 [thread overview]
Message-ID: <20250527111444.701ea84c@p-imbrenda> (raw)
In-Reply-To: <DA6RCZ7FOBOS.1U1CX5REWAGTN@linux.ibm.com>
On Tue, 27 May 2025 09:18:01 +0200
"Nico Boehr" <nrb@linux.ibm.com> wrote:
this patch had so many issues, and brought no real advantages, so I
dropped it from v3 onwards
> On Tue May 20, 2025 at 8:26 PM CEST, Claudio Imbrenda wrote:
> [...]
> > diff --git a/arch/s390/kvm/priv.c b/arch/s390/kvm/priv.c
> > index 9253c70897a8..15843e7e57e6 100644
> > --- a/arch/s390/kvm/priv.c
> > +++ b/arch/s390/kvm/priv.c
> [...]
> > +static int skeys_common_checks(struct kvm_vcpu *vcpu, struct skeys_ops_state *state)
> > +{
> > + int rc;
> > +
> > + if (vcpu->arch.sie_block->gpsw.mask & PSW_MASK_PSTATE) {
> > + rc = kvm_s390_inject_program_int(vcpu, PGM_PRIVILEGED_OP);
> > + return rc ? rc : -EAGAIN;
>
> What has changed that
>
> return kvm_s390_inject_program_int()
>
> is not sufficient any more?
>
> [...]
> > + get_regs_rre_ptr(vcpu, &state->reg1, &state->reg2, &state->r1, &state->r2);
> > +
> > + state->effective = vcpu->run->s.regs.gprs[state->reg2] & PAGE_MASK;
>
> *state->r2?
>
> [...]
> > static int handle_pfmf(struct kvm_vcpu *vcpu)
> > {
> [...]
> > + if (r1.fsc) {
> > + end = kvm_s390_logical_to_effective(vcpu, end);
> > + if (kvm_s390_is_amode_64(vcpu))
> > + replace_selected_bits(r2, PAGE_MASK, end);
> > + else
> > + replace_selected_bits(r2, 0xfffff000, end);
>
> Maybe I'm missing something, but I don't get why you need replace_selected_bits
> here. kvm_s390_logical_to_effective() already does the neccesary masking, no?
next prev parent reply other threads:[~2025-05-27 9:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 18:26 [PATCH v2 0/5] KVM: s390: some cleanup and small fixes Claudio Imbrenda
2025-05-20 18:26 ` [PATCH v2 1/5] s390: remove unneeded includes Claudio Imbrenda
2025-05-20 18:26 ` [PATCH v2 2/5] KVM: s390: remove unneeded srcu lock Claudio Imbrenda
2025-05-22 13:07 ` Christoph Schlameuss
2025-05-20 18:26 ` [PATCH v2 3/5] KVM: s390: refactor some functions in priv.c Claudio Imbrenda
2025-05-21 15:52 ` Heiko Carstens
2025-05-27 7:18 ` Nico Boehr
2025-05-27 9:14 ` Claudio Imbrenda [this message]
2025-05-20 18:26 ` [PATCH v2 4/5] KVM: s390: refactor and split some gmap helpers Claudio Imbrenda
2025-05-21 16:26 ` Heiko Carstens
2025-05-26 11:17 ` Janosch Frank
2025-05-26 11:59 ` Heiko Carstens
2025-05-26 13:21 ` Claudio Imbrenda
2025-05-20 18:26 ` [PATCH v2 5/5] KVM: s390: simplify and move pv code Claudio Imbrenda
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=20250527111444.701ea84c@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nrb@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=schlameuss@linux.ibm.com \
--cc=seiden@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;
as well as URLs for NNTP newsgroup(s).