public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Morel <pmorel@linux.ibm.com>
To: david@redhat.com
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-kernel@vger.kernel.org, borntraeger@de.ibm.com,
	frankja@linux.ibm.com, cohuck@redhat.com, thuth@redhat.com,
	imbrenda@linux.ibm.com, hca@linux.ibm.com, gor@linux.ibm.com,
	svens@linux.ibm.com
Subject: [PATCH v3 0/1] KVM: s390: vsie: clarifications on setting the APCB
Date: Tue, 14 Feb 2023 13:28:40 +0100	[thread overview]
Message-ID: <20230214122841.13066-1-pmorel@linux.ibm.com> (raw)

Hi,

This is a v3 of the previously called:
[PATCH] KVM: s390: vsie: fix crycb virtual vs physical usage
and 
[PATCH v2 0/1] KVM: s390: vsie: clarifications on setting the APCB

Changes:

1->2 After David's comment that the patch has not to do with
     virtual vs physical, I reworked the commit message.

2->3 rename crycb_o crycb_gpa and apcb_o apcb_gpa
     gpa = Guest Physical Address 

I resent the patch because I think that even the previous
version is not really buggy, this new version brings clarity.

Regards,
Pierre

Pierre Morel (1):
  KVM: s390: vsie: clarifications on setting the APCB

 arch/s390/kvm/vsie.c | 50 +++++++++++++++++++++++++-------------------
 1 file changed, 29 insertions(+), 21 deletions(-)

-- 
2.31.1


             reply	other threads:[~2023-02-14 12:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-14 12:28 Pierre Morel [this message]
2023-02-14 12:28 ` [PATCH v3 1/1] KVM: s390: vsie: clarifications on setting the APCB Pierre Morel
2023-02-16 13:04   ` David Hildenbrand
2023-02-17  8:21     ` Pierre Morel
2023-02-16 13:41   ` Janosch Frank
2023-02-17  8:21     ` Pierre Morel
  -- strict thread matches above, loose matches on Subject: below --
2022-11-03 15:26 [PATCH v3 0/1] " Pierre Morel

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=20230214122841.13066-1-pmorel@linux.ibm.com \
    --to=pmorel@linux.ibm.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=frankja@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=svens@linux.ibm.com \
    --cc=thuth@redhat.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