From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: Sven Schnelle <svens@linux.ibm.com>
Cc: Christoph Schlameuss <schlameuss@linux.ibm.com>,
kvm@vger.kernel.org,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>,
David Hildenbrand <david@kernel.org>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
linux-s390@vger.kernel.org
Subject: Re: [PATCH 3/6] KVM: s390: vsie: Convert shift to phys_to_pfn()
Date: Fri, 7 Aug 2026 13:28:44 +0200 [thread overview]
Message-ID: <20260807132844.4cc87356@p-imbrenda> (raw)
In-Reply-To: <yt9d4ih6rxz2.fsf@linux.ibm.com>
On Fri, 07 Aug 2026 13:06:41 +0200
Sven Schnelle <svens@linux.ibm.com> wrote:
> Sven Schnelle <svens@linux.ibm.com> writes:
>
> > Christoph Schlameuss <schlameuss@linux.ibm.com> writes:
> >
> >> Make the code slightly more readable.
> >>
> >> Signed-off-by: Christoph Schlameuss <schlameuss@linux.ibm.com>
> >> ---
> >> arch/s390/kvm/vsie.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/arch/s390/kvm/vsie.c b/arch/s390/kvm/vsie.c
> >> index 3e956c7faa4b..937f9c99bc00 100644
> >> --- a/arch/s390/kvm/vsie.c
> >> +++ b/arch/s390/kvm/vsie.c
> >> @@ -701,7 +701,7 @@ static int pin_guest_page(struct kvm *kvm, gpa_t gpa, hpa_t *hpa)
> >> /* Unpins a page previously pinned via pin_guest_page, marking it as dirty. */
> >> static void unpin_guest_page(struct kvm *kvm, gpa_t gpa, hpa_t hpa)
> >> {
> >> - kvm_release_page_dirty(pfn_to_page(hpa >> PAGE_SHIFT));
> >> + kvm_release_page_dirty(pfn_to_page(phys_to_pfn(hpa)));
> >> /* mark the page always as dirty for migration */
> >> mark_page_dirty(kvm, gpa_to_gfn(gpa));
> >> }
> >
> > Could you add to the commit description what you changed? I.e. use
> > phys_to_pfn() instead of the open coded shift? It's bad if you do a 'git
> > log' and get commit with useless descriptions like 'make code more
> > readable'.
>
> Nevermind - was in a rush and missed that it's in the summary... :-/
I still think the description should be self-contained and not be split
between the subject line and the body, even if it means that the body
of the text repeats the subject line again.
next prev parent reply other threads:[~2026-08-07 11:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 9:57 [PATCH 0/6] KVM: s390: vsie: Small VSIE cleanup and improvements Christoph Schlameuss
2026-08-07 9:57 ` [PATCH 1/6] KVM: s390: Remove double 64bscao feature check Christoph Schlameuss
2026-08-07 9:59 ` sashiko-bot
2026-08-07 10:59 ` Claudio Imbrenda
2026-08-07 9:57 ` [PATCH 2/6] KVM: s390: vsie: Remove duplicate assertion Christoph Schlameuss
2026-08-07 9:59 ` sashiko-bot
2026-08-07 10:32 ` Christian Borntraeger
2026-08-07 11:03 ` Claudio Imbrenda
2026-08-07 9:57 ` [PATCH 3/6] KVM: s390: vsie: Convert shift to phys_to_pfn() Christoph Schlameuss
2026-08-07 10:02 ` sashiko-bot
2026-08-07 10:36 ` Christian Borntraeger
2026-08-07 10:40 ` Sven Schnelle
2026-08-07 11:06 ` Sven Schnelle
2026-08-07 11:28 ` Claudio Imbrenda [this message]
2026-08-07 11:04 ` Claudio Imbrenda
2026-08-07 9:57 ` [PATCH 4/6] KVM: s390: vsie: Assert mcck_info offset in vsie_page Christoph Schlameuss
2026-08-07 10:02 ` sashiko-bot
2026-08-07 10:37 ` Christian Borntraeger
2026-08-07 9:57 ` [PATCH 5/6] KVM: s390: vsie: Assert crycb alignment " Christoph Schlameuss
2026-08-07 10:00 ` sashiko-bot
2026-08-07 10:38 ` Christian Borntraeger
2026-08-07 11:25 ` Claudio Imbrenda
2026-08-07 9:57 ` [PATCH 6/6] KVM: s390: vsie: Create constant SCB_ALIGNMENT_SHIFT Christoph Schlameuss
2026-08-07 10:02 ` sashiko-bot
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=20260807132844.4cc87356@p-imbrenda \
--to=imbrenda@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@kernel.org \
--cc=frankja@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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