LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* [PATCH 1/2] KVM: s390: gaccess: Cleanup access to guest frames
[not found] <20210816150718.3063877-1-scgl@linux.ibm.com>
@ 2021-08-16 15:07 ` Janis Schoetterl-Glausch
2021-08-18 7:46 ` Janosch Frank
2021-08-18 7:54 ` David Hildenbrand
2021-08-16 15:07 ` [PATCH 2/2] KVM: s390: gaccess: Refactor access address range check Janis Schoetterl-Glausch
1 sibling, 2 replies; 12+ messages in thread
From: Janis Schoetterl-Glausch @ 2021-08-16 15:07 UTC (permalink / raw)
To: kvm, borntraeger, frankja, imbrenda, Heiko Carstens, Vasily Gorbik
Cc: scgl, david, cohuck, linux-s390, linux-kernel
Introduce a helper function for guest frame access.
Rewrite the calculation of the gpa and the length of the segment
to be more readable.
Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
---
arch/s390/kvm/gaccess.c | 48 +++++++++++++++++++++++++----------------
1 file changed, 29 insertions(+), 19 deletions(-)
diff --git a/arch/s390/kvm/gaccess.c b/arch/s390/kvm/gaccess.c
index b9f85b2dc053..df83de0843de 100644
--- a/arch/s390/kvm/gaccess.c
+++ b/arch/s390/kvm/gaccess.c
@@ -827,11 +827,26 @@ static int guest_page_range(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar,
return 0;
}
+static int access_guest_frame(struct kvm *kvm, enum gacc_mode mode, gpa_t gpa,
+ void *data, unsigned int len)
+{
+ gfn_t gfn = gpa_to_gfn(gpa);
+ unsigned int offset = offset_in_page(gpa);
+ int rc;
+
+ if (mode == GACC_STORE)
+ rc = kvm_write_guest_page(kvm, gfn, data, offset, len);
+ else
+ rc = kvm_read_guest_page(kvm, gfn, data, offset, len);
+ return rc;
+}
+
int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
unsigned long len, enum gacc_mode mode)
{
psw_t *psw = &vcpu->arch.sie_block->gpsw;
- unsigned long _len, nr_pages, gpa, idx;
+ unsigned long nr_pages, gpa, idx;
+ unsigned int seg;
unsigned long pages_array[2];
unsigned long *pages;
int need_ipte_lock;
@@ -855,15 +870,12 @@ int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
ipte_lock(vcpu);
rc = guest_page_range(vcpu, ga, ar, pages, nr_pages, asce, mode);
for (idx = 0; idx < nr_pages && !rc; idx++) {
- gpa = *(pages + idx) + (ga & ~PAGE_MASK);
- _len = min(PAGE_SIZE - (gpa & ~PAGE_MASK), len);
- if (mode == GACC_STORE)
- rc = kvm_write_guest(vcpu->kvm, gpa, data, _len);
- else
- rc = kvm_read_guest(vcpu->kvm, gpa, data, _len);
- len -= _len;
- ga += _len;
- data += _len;
+ gpa = pages[idx] + offset_in_page(ga);
+ seg = min(PAGE_SIZE - offset_in_page(gpa), len);
+ rc = access_guest_frame(vcpu->kvm, mode, gpa, data, seg);
+ len -= seg;
+ ga += seg;
+ data += seg;
}
if (need_ipte_lock)
ipte_unlock(vcpu);
@@ -875,19 +887,17 @@ int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
int access_guest_real(struct kvm_vcpu *vcpu, unsigned long gra,
void *data, unsigned long len, enum gacc_mode mode)
{
- unsigned long _len, gpa;
+ unsigned long gpa;
+ unsigned int seg;
int rc = 0;
while (len && !rc) {
gpa = kvm_s390_real_to_abs(vcpu, gra);
- _len = min(PAGE_SIZE - (gpa & ~PAGE_MASK), len);
- if (mode)
- rc = write_guest_abs(vcpu, gpa, data, _len);
- else
- rc = read_guest_abs(vcpu, gpa, data, _len);
- len -= _len;
- gra += _len;
- data += _len;
+ seg = min(PAGE_SIZE - offset_in_page(gpa), len);
+ rc = access_guest_frame(vcpu->kvm, mode, gpa, data, seg);
+ len -= seg;
+ gra += seg;
+ data += seg;
}
return rc;
}
--
2.25.1
^ permalink raw reply related [flat|nested] 12+ messages in thread
* [PATCH 2/2] KVM: s390: gaccess: Refactor access address range check
[not found] <20210816150718.3063877-1-scgl@linux.ibm.com>
2021-08-16 15:07 ` [PATCH 1/2] KVM: s390: gaccess: Cleanup access to guest frames Janis Schoetterl-Glausch
@ 2021-08-16 15:07 ` Janis Schoetterl-Glausch
2021-08-18 10:08 ` Claudio Imbrenda
1 sibling, 1 reply; 12+ messages in thread
From: Janis Schoetterl-Glausch @ 2021-08-16 15:07 UTC (permalink / raw)
To: kvm, borntraeger, frankja, imbrenda, Heiko Carstens, Vasily Gorbik
Cc: scgl, david, cohuck, linux-s390, linux-kernel
Do not round down the first address to the page boundary, just translate
it normally, which gives the value we care about in the first place.
Given this, translating a single address is just the special case of
translating a range spanning a single page.
Make the output optional, so the function can be used to just check a
range.
Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
---
arch/s390/kvm/gaccess.c | 91 ++++++++++++++++++-----------------------
1 file changed, 39 insertions(+), 52 deletions(-)
diff --git a/arch/s390/kvm/gaccess.c b/arch/s390/kvm/gaccess.c
index df83de0843de..e5a19d8b30e2 100644
--- a/arch/s390/kvm/gaccess.c
+++ b/arch/s390/kvm/gaccess.c
@@ -794,35 +794,45 @@ static int low_address_protection_enabled(struct kvm_vcpu *vcpu,
return 1;
}
-static int guest_page_range(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar,
- unsigned long *pages, unsigned long nr_pages,
- const union asce asce, enum gacc_mode mode)
+/* Stores the gpas for each page in a real/virtual range into @gpas
+ * Modifies the 'struct kvm_s390_pgm_info pgm' member of @vcpu in the same
+ * way read_guest/write_guest do, the meaning of the return value is likewise
+ * the same.
+ * If @gpas is NULL only the checks are performed.
+ */
+static int guest_range_to_gpas(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar,
+ unsigned long *gpas, unsigned long len,
+ const union asce asce, enum gacc_mode mode)
{
psw_t *psw = &vcpu->arch.sie_block->gpsw;
+ unsigned long gpa;
+ unsigned int seg;
+ unsigned int offset = offset_in_page(ga);
int lap_enabled, rc = 0;
enum prot_type prot;
lap_enabled = low_address_protection_enabled(vcpu, asce);
- while (nr_pages) {
+ while ((seg = min(PAGE_SIZE - offset, len)) != 0) {
ga = kvm_s390_logical_to_effective(vcpu, ga);
if (mode == GACC_STORE && lap_enabled && is_low_address(ga))
return trans_exc(vcpu, PGM_PROTECTION, ga, ar, mode,
PROT_TYPE_LA);
- ga &= PAGE_MASK;
if (psw_bits(*psw).dat) {
- rc = guest_translate(vcpu, ga, pages, asce, mode, &prot);
+ rc = guest_translate(vcpu, ga, &gpa, asce, mode, &prot);
if (rc < 0)
return rc;
} else {
- *pages = kvm_s390_real_to_abs(vcpu, ga);
- if (kvm_is_error_gpa(vcpu->kvm, *pages))
+ gpa = kvm_s390_real_to_abs(vcpu, ga);
+ if (kvm_is_error_gpa(vcpu->kvm, gpa))
rc = PGM_ADDRESSING;
}
if (rc)
return trans_exc(vcpu, rc, ga, ar, mode, prot);
- ga += PAGE_SIZE;
- pages++;
- nr_pages--;
+ if (gpas)
+ *gpas++ = gpa;
+ offset = 0;
+ ga += seg;
+ len -= seg;
}
return 0;
}
@@ -845,10 +855,10 @@ int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
unsigned long len, enum gacc_mode mode)
{
psw_t *psw = &vcpu->arch.sie_block->gpsw;
- unsigned long nr_pages, gpa, idx;
+ unsigned long nr_pages, idx;
unsigned int seg;
- unsigned long pages_array[2];
- unsigned long *pages;
+ unsigned long gpa_array[2];
+ unsigned long *gpas;
int need_ipte_lock;
union asce asce;
int rc;
@@ -860,27 +870,25 @@ int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
if (rc)
return rc;
nr_pages = (((ga & ~PAGE_MASK) + len - 1) >> PAGE_SHIFT) + 1;
- pages = pages_array;
- if (nr_pages > ARRAY_SIZE(pages_array))
- pages = vmalloc(array_size(nr_pages, sizeof(unsigned long)));
- if (!pages)
+ gpas = gpa_array;
+ if (nr_pages > ARRAY_SIZE(gpa_array))
+ gpas = vmalloc(array_size(nr_pages, sizeof(unsigned long)));
+ if (!gpas)
return -ENOMEM;
need_ipte_lock = psw_bits(*psw).dat && !asce.r;
if (need_ipte_lock)
ipte_lock(vcpu);
- rc = guest_page_range(vcpu, ga, ar, pages, nr_pages, asce, mode);
+ rc = guest_range_to_gpas(vcpu, ga, ar, gpas, len, asce, mode);
for (idx = 0; idx < nr_pages && !rc; idx++) {
- gpa = pages[idx] + offset_in_page(ga);
- seg = min(PAGE_SIZE - offset_in_page(gpa), len);
- rc = access_guest_frame(vcpu->kvm, mode, gpa, data, seg);
+ seg = min(PAGE_SIZE - offset_in_page(gpas[idx]), len);
+ rc = access_guest_frame(vcpu->kvm, mode, gpas[idx], data, seg);
len -= seg;
- ga += seg;
data += seg;
}
if (need_ipte_lock)
ipte_unlock(vcpu);
- if (nr_pages > ARRAY_SIZE(pages_array))
- vfree(pages);
+ if (nr_pages > ARRAY_SIZE(gpa_array))
+ vfree(gpas);
return rc;
}
@@ -914,8 +922,6 @@ int access_guest_real(struct kvm_vcpu *vcpu, unsigned long gra,
int guest_translate_address(struct kvm_vcpu *vcpu, unsigned long gva, u8 ar,
unsigned long *gpa, enum gacc_mode mode)
{
- psw_t *psw = &vcpu->arch.sie_block->gpsw;
- enum prot_type prot;
union asce asce;
int rc;
@@ -923,23 +929,7 @@ int guest_translate_address(struct kvm_vcpu *vcpu, unsigned long gva, u8 ar,
rc = get_vcpu_asce(vcpu, &asce, gva, ar, mode);
if (rc)
return rc;
- if (is_low_address(gva) && low_address_protection_enabled(vcpu, asce)) {
- if (mode == GACC_STORE)
- return trans_exc(vcpu, PGM_PROTECTION, gva, 0,
- mode, PROT_TYPE_LA);
- }
-
- if (psw_bits(*psw).dat && !asce.r) { /* Use DAT? */
- rc = guest_translate(vcpu, gva, gpa, asce, mode, &prot);
- if (rc > 0)
- return trans_exc(vcpu, rc, gva, 0, mode, prot);
- } else {
- *gpa = kvm_s390_real_to_abs(vcpu, gva);
- if (kvm_is_error_gpa(vcpu->kvm, *gpa))
- return trans_exc(vcpu, rc, gva, PGM_ADDRESSING, mode, 0);
- }
-
- return rc;
+ return guest_range_to_gpas(vcpu, gva, ar, gpa, 1, asce, mode);
}
/**
@@ -948,17 +938,14 @@ int guest_translate_address(struct kvm_vcpu *vcpu, unsigned long gva, u8 ar,
int check_gva_range(struct kvm_vcpu *vcpu, unsigned long gva, u8 ar,
unsigned long length, enum gacc_mode mode)
{
- unsigned long gpa;
- unsigned long currlen;
+ union asce asce;
int rc = 0;
+ rc = get_vcpu_asce(vcpu, &asce, gva, ar, mode);
+ if (rc)
+ return rc;
ipte_lock(vcpu);
- while (length > 0 && !rc) {
- currlen = min(length, PAGE_SIZE - (gva % PAGE_SIZE));
- rc = guest_translate_address(vcpu, gva, ar, &gpa, mode);
- gva += currlen;
- length -= currlen;
- }
+ rc = guest_range_to_gpas(vcpu, gva, ar, NULL, length, asce, mode);
ipte_unlock(vcpu);
return rc;
--
2.25.1
^ permalink raw reply related [flat|nested] 12+ messages in thread
* Re: [PATCH 1/2] KVM: s390: gaccess: Cleanup access to guest frames
2021-08-16 15:07 ` [PATCH 1/2] KVM: s390: gaccess: Cleanup access to guest frames Janis Schoetterl-Glausch
@ 2021-08-18 7:46 ` Janosch Frank
2021-08-18 7:54 ` David Hildenbrand
1 sibling, 0 replies; 12+ messages in thread
From: Janosch Frank @ 2021-08-18 7:46 UTC (permalink / raw)
To: Janis Schoetterl-Glausch, kvm, borntraeger, imbrenda,
Heiko Carstens, Vasily Gorbik
Cc: david, cohuck, linux-s390, linux-kernel
On 8/16/21 5:07 PM, Janis Schoetterl-Glausch wrote:
> Introduce a helper function for guest frame access.
> Rewrite the calculation of the gpa and the length of the segment
> to be more readable.
>
> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
> ---
> arch/s390/kvm/gaccess.c | 48 +++++++++++++++++++++++++----------------
> 1 file changed, 29 insertions(+), 19 deletions(-)
>
> diff --git a/arch/s390/kvm/gaccess.c b/arch/s390/kvm/gaccess.c
> index b9f85b2dc053..df83de0843de 100644
> --- a/arch/s390/kvm/gaccess.c
> +++ b/arch/s390/kvm/gaccess.c
> @@ -827,11 +827,26 @@ static int guest_page_range(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar,
> return 0;
> }
>
> +static int access_guest_frame(struct kvm *kvm, enum gacc_mode mode, gpa_t gpa,
> + void *data, unsigned int len)
> +{
> + gfn_t gfn = gpa_to_gfn(gpa);
> + unsigned int offset = offset_in_page(gpa);
> + int rc;
> +
> + if (mode == GACC_STORE)
> + rc = kvm_write_guest_page(kvm, gfn, data, offset, len);
> + else
> + rc = kvm_read_guest_page(kvm, gfn, data, offset, len);
> + return rc;
> +}
> +
> int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
> unsigned long len, enum gacc_mode mode)
> {
> psw_t *psw = &vcpu->arch.sie_block->gpsw;
> - unsigned long _len, nr_pages, gpa, idx;
> + unsigned long nr_pages, gpa, idx;
> + unsigned int seg;
> unsigned long pages_array[2];
> unsigned long *pages;
> int need_ipte_lock;
> @@ -855,15 +870,12 @@ int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
> ipte_lock(vcpu);
> rc = guest_page_range(vcpu, ga, ar, pages, nr_pages, asce, mode);
> for (idx = 0; idx < nr_pages && !rc; idx++) {
> - gpa = *(pages + idx) + (ga & ~PAGE_MASK);
> - _len = min(PAGE_SIZE - (gpa & ~PAGE_MASK), len);
> - if (mode == GACC_STORE)
> - rc = kvm_write_guest(vcpu->kvm, gpa, data, _len);
> - else
> - rc = kvm_read_guest(vcpu->kvm, gpa, data, _len);
> - len -= _len;
> - ga += _len;
> - data += _len;
> + gpa = pages[idx] + offset_in_page(ga);
> + seg = min(PAGE_SIZE - offset_in_page(gpa), len);
> + rc = access_guest_frame(vcpu->kvm, mode, gpa, data, seg);
> + len -= seg;
> + ga += seg;
> + data += seg;
> }
> if (need_ipte_lock)
> ipte_unlock(vcpu);
> @@ -875,19 +887,17 @@ int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
> int access_guest_real(struct kvm_vcpu *vcpu, unsigned long gra,
> void *data, unsigned long len, enum gacc_mode mode)
> {
> - unsigned long _len, gpa;
> + unsigned long gpa;
> + unsigned int seg;
> int rc = 0;
>
> while (len && !rc) {
> gpa = kvm_s390_real_to_abs(vcpu, gra);
> - _len = min(PAGE_SIZE - (gpa & ~PAGE_MASK), len);
> - if (mode)
> - rc = write_guest_abs(vcpu, gpa, data, _len);
> - else
> - rc = read_guest_abs(vcpu, gpa, data, _len);
> - len -= _len;
> - gra += _len;
> - data += _len;
> + seg = min(PAGE_SIZE - offset_in_page(gpa), len);
> + rc = access_guest_frame(vcpu->kvm, mode, gpa, data, seg);
> + len -= seg;
> + gra += seg;
> + data += seg;
> }
> return rc;
> }
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 1/2] KVM: s390: gaccess: Cleanup access to guest frames
2021-08-16 15:07 ` [PATCH 1/2] KVM: s390: gaccess: Cleanup access to guest frames Janis Schoetterl-Glausch
2021-08-18 7:46 ` Janosch Frank
@ 2021-08-18 7:54 ` David Hildenbrand
2021-08-18 8:06 ` Janosch Frank
2021-08-18 9:00 ` Janis Schoetterl-Glausch
1 sibling, 2 replies; 12+ messages in thread
From: David Hildenbrand @ 2021-08-18 7:54 UTC (permalink / raw)
To: Janis Schoetterl-Glausch, kvm, borntraeger, frankja, imbrenda,
Heiko Carstens, Vasily Gorbik
Cc: cohuck, linux-s390, linux-kernel
On 16.08.21 17:07, Janis Schoetterl-Glausch wrote:
> Introduce a helper function for guest frame access.
> Rewrite the calculation of the gpa and the length of the segment
> to be more readable.
>
> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
> ---
> arch/s390/kvm/gaccess.c | 48 +++++++++++++++++++++++++----------------
> 1 file changed, 29 insertions(+), 19 deletions(-)
>
> diff --git a/arch/s390/kvm/gaccess.c b/arch/s390/kvm/gaccess.c
> index b9f85b2dc053..df83de0843de 100644
> --- a/arch/s390/kvm/gaccess.c
> +++ b/arch/s390/kvm/gaccess.c
> @@ -827,11 +827,26 @@ static int guest_page_range(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar,
> return 0;
> }
>
> +static int access_guest_frame(struct kvm *kvm, enum gacc_mode mode, gpa_t gpa,
> + void *data, unsigned int len)
I know, "frame" is a beautiful term for "page" -- can we just avoid
using it because we're not using it anywhere else here? :)
What's wrong with "access_guest_page()" ?
> +{
> + gfn_t gfn = gpa_to_gfn(gpa);
> + unsigned int offset = offset_in_page(gpa);
> + int rc;
You could turn both const. You might want to consider
reverse-christmas-treeing this.
> +
> + if (mode == GACC_STORE)
> + rc = kvm_write_guest_page(kvm, gfn, data, offset, len);
> + else
> + rc = kvm_read_guest_page(kvm, gfn, data, offset, len);
Personally, I prefer passing in pfn + offset instead of a gpa. Also
avoids having to convert back and forth.
> + return rc;
> +}
> +
> int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
> unsigned long len, enum gacc_mode mode)
> {
> psw_t *psw = &vcpu->arch.sie_block->gpsw;
> - unsigned long _len, nr_pages, gpa, idx;
> + unsigned long nr_pages, gpa, idx;
> + unsigned int seg;
Dito, reverse christmas tree might be worth keeping.
> unsigned long pages_array[2];
> unsigned long *pages;
> int need_ipte_lock;
> @@ -855,15 +870,12 @@ int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
> ipte_lock(vcpu);
> rc = guest_page_range(vcpu, ga, ar, pages, nr_pages, asce, mode);
> for (idx = 0; idx < nr_pages && !rc; idx++) {
> - gpa = *(pages + idx) + (ga & ~PAGE_MASK);
> - _len = min(PAGE_SIZE - (gpa & ~PAGE_MASK), len);
> - if (mode == GACC_STORE)
> - rc = kvm_write_guest(vcpu->kvm, gpa, data, _len);
> - else
> - rc = kvm_read_guest(vcpu->kvm, gpa, data, _len);
> - len -= _len;
> - ga += _len;
> - data += _len;
> + gpa = pages[idx] + offset_in_page(ga);
> + seg = min(PAGE_SIZE - offset_in_page(gpa), len);
> + rc = access_guest_frame(vcpu->kvm, mode, gpa, data, seg);
> + len -= seg;
> + ga += seg;
> + data += seg;
> }
> if (need_ipte_lock)
> ipte_unlock(vcpu);
> @@ -875,19 +887,17 @@ int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
> int access_guest_real(struct kvm_vcpu *vcpu, unsigned long gra,
> void *data, unsigned long len, enum gacc_mode mode)
> {
> - unsigned long _len, gpa;
> + unsigned long gpa;
> + unsigned int seg;
> int rc = 0;
>
> while (len && !rc) {
> gpa = kvm_s390_real_to_abs(vcpu, gra);
> - _len = min(PAGE_SIZE - (gpa & ~PAGE_MASK), len);
> - if (mode)
> - rc = write_guest_abs(vcpu, gpa, data, _len);
> - else
> - rc = read_guest_abs(vcpu, gpa, data, _len);
> - len -= _len;
> - gra += _len;
> - data += _len;
> + seg = min(PAGE_SIZE - offset_in_page(gpa), len);
What does "seg" mean? I certainly know when "len" means -- which is also
what the function eats.
> + rc = access_guest_frame(vcpu->kvm, mode, gpa, data, seg);
> + len -= seg;
> + gra += seg;
> + data += seg;
> }
> return rc;
> }
>
--
Thanks,
David / dhildenb
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 1/2] KVM: s390: gaccess: Cleanup access to guest frames
2021-08-18 7:54 ` David Hildenbrand
@ 2021-08-18 8:06 ` Janosch Frank
2021-08-18 8:44 ` David Hildenbrand
2021-08-19 13:53 ` Janis Schoetterl-Glausch
2021-08-18 9:00 ` Janis Schoetterl-Glausch
1 sibling, 2 replies; 12+ messages in thread
From: Janosch Frank @ 2021-08-18 8:06 UTC (permalink / raw)
To: David Hildenbrand, Janis Schoetterl-Glausch, kvm, borntraeger,
imbrenda, Heiko Carstens, Vasily Gorbik
Cc: cohuck, linux-s390, linux-kernel
On 8/18/21 9:54 AM, David Hildenbrand wrote:
> On 16.08.21 17:07, Janis Schoetterl-Glausch wrote:
>> Introduce a helper function for guest frame access.
>> Rewrite the calculation of the gpa and the length of the segment
>> to be more readable.
>>
>> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
[...]
>> - unsigned long _len, gpa;
>> + unsigned long gpa;
>> + unsigned int seg;
>> int rc = 0;
>>
>> while (len && !rc) {
>> gpa = kvm_s390_real_to_abs(vcpu, gra);
>> - _len = min(PAGE_SIZE - (gpa & ~PAGE_MASK), len);
>> - if (mode)
>> - rc = write_guest_abs(vcpu, gpa, data, _len);
>> - else
>> - rc = read_guest_abs(vcpu, gpa, data, _len);
>> - len -= _len;
>> - gra += _len;
>> - data += _len;
>> + seg = min(PAGE_SIZE - offset_in_page(gpa), len);
>
> What does "seg" mean? I certainly know when "len" means -- which is also
> what the function eats.
What does "_len" mean especially in contrast to "len"?
"seg" is used in the common kvm guest access functions so it's at least
consistent although I share the sentiment that it's not a great name for
the length we access inside the page.
Originally I suggested "len_in_page" if you have a better name I'd
expect we'll both be happy to discuss it :-)
>
>> + rc = access_guest_frame(vcpu->kvm, mode, gpa, data, seg);
>> + len -= seg;
>> + gra += seg;
>> + data += seg;
>> }
>> return rc;
>> }
>>
>
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 1/2] KVM: s390: gaccess: Cleanup access to guest frames
2021-08-18 8:06 ` Janosch Frank
@ 2021-08-18 8:44 ` David Hildenbrand
2021-08-18 8:48 ` Janis Schoetterl-Glausch
2021-08-19 13:53 ` Janis Schoetterl-Glausch
1 sibling, 1 reply; 12+ messages in thread
From: David Hildenbrand @ 2021-08-18 8:44 UTC (permalink / raw)
To: Janosch Frank, Janis Schoetterl-Glausch, kvm, borntraeger,
imbrenda, Heiko Carstens, Vasily Gorbik
Cc: cohuck, linux-s390, linux-kernel
On 18.08.21 10:06, Janosch Frank wrote:
> On 8/18/21 9:54 AM, David Hildenbrand wrote:
>> On 16.08.21 17:07, Janis Schoetterl-Glausch wrote:
>>> Introduce a helper function for guest frame access.
>>> Rewrite the calculation of the gpa and the length of the segment
>>> to be more readable.
>>>
>>> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
> [...]
>>> - unsigned long _len, gpa;
>>> + unsigned long gpa;
>>> + unsigned int seg;
>>> int rc = 0;
>>>
>>> while (len && !rc) {
>>> gpa = kvm_s390_real_to_abs(vcpu, gra);
>>> - _len = min(PAGE_SIZE - (gpa & ~PAGE_MASK), len);
>>> - if (mode)
>>> - rc = write_guest_abs(vcpu, gpa, data, _len);
>>> - else
>>> - rc = read_guest_abs(vcpu, gpa, data, _len);
>>> - len -= _len;
>>> - gra += _len;
>>> - data += _len;
>>> + seg = min(PAGE_SIZE - offset_in_page(gpa), len);
>>
>> What does "seg" mean? I certainly know when "len" means -- which is also
>> what the function eats.
>
> What does "_len" mean especially in contrast to "len"?
>
> "seg" is used in the common kvm guest access functions so it's at least
> consistent although I share the sentiment that it's not a great name for
> the length we access inside the page.
>
> Originally I suggested "len_in_page" if you have a better name I'd
> expect we'll both be happy to discuss it :-)
Similar code I encountered in other places uses "len" vs "cur_len" or
"total_len" vs. "cur_len". I agree that everything is better than "len"
vs. "_len".
I just cannot come up with a proper word for "seg" that would make
sense. "Segment" ? Maybe my uneducated mind is missing some important
English words that just fit perfectly here.
Anyhow, just my 2 cents, you maintain this code :)
--
Thanks,
David / dhildenb
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 1/2] KVM: s390: gaccess: Cleanup access to guest frames
2021-08-18 8:44 ` David Hildenbrand
@ 2021-08-18 8:48 ` Janis Schoetterl-Glausch
0 siblings, 0 replies; 12+ messages in thread
From: Janis Schoetterl-Glausch @ 2021-08-18 8:48 UTC (permalink / raw)
To: David Hildenbrand, Janosch Frank, Janis Schoetterl-Glausch, kvm,
borntraeger, imbrenda, Heiko Carstens, Vasily Gorbik
Cc: cohuck, linux-s390, linux-kernel
On 8/18/21 10:44 AM, David Hildenbrand wrote:
> On 18.08.21 10:06, Janosch Frank wrote:
>> On 8/18/21 9:54 AM, David Hildenbrand wrote:
>>> On 16.08.21 17:07, Janis Schoetterl-Glausch wrote:
>>>> Introduce a helper function for guest frame access.
>>>> Rewrite the calculation of the gpa and the length of the segment
>>>> to be more readable.
>>>>
>>>> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
>> [...]
>>>> - unsigned long _len, gpa;
>>>> + unsigned long gpa;
>>>> + unsigned int seg;
>>>> int rc = 0;
>>>> while (len && !rc) {
>>>> gpa = kvm_s390_real_to_abs(vcpu, gra);
>>>> - _len = min(PAGE_SIZE - (gpa & ~PAGE_MASK), len);
>>>> - if (mode)
>>>> - rc = write_guest_abs(vcpu, gpa, data, _len);
>>>> - else
>>>> - rc = read_guest_abs(vcpu, gpa, data, _len);
>>>> - len -= _len;
>>>> - gra += _len;
>>>> - data += _len;
>>>> + seg = min(PAGE_SIZE - offset_in_page(gpa), len);
>>>
>>> What does "seg" mean? I certainly know when "len" means -- which is also
>>> what the function eats.
>>
>> What does "_len" mean especially in contrast to "len"?
>>
>> "seg" is used in the common kvm guest access functions so it's at least
>> consistent although I share the sentiment that it's not a great name for
>> the length we access inside the page.
>>
>> Originally I suggested "len_in_page" if you have a better name I'd
>> expect we'll both be happy to discuss it :-)
>
> Similar code I encountered in other places uses "len" vs "cur_len" or "total_len" vs. "cur_len". I agree that everything is better than "len" vs. "_len".
>
> I just cannot come up with a proper word for "seg" that would make sense. "Segment" ? Maybe my uneducated mind is missing some important English words that just fit perfectly here.
Yes, it's short for segment, kvm_main has a function next_segment to calculate it.
I don't like the naming scheme much either.
>
> Anyhow, just my 2 cents, you maintain this code :)
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 1/2] KVM: s390: gaccess: Cleanup access to guest frames
2021-08-18 7:54 ` David Hildenbrand
2021-08-18 8:06 ` Janosch Frank
@ 2021-08-18 9:00 ` Janis Schoetterl-Glausch
1 sibling, 0 replies; 12+ messages in thread
From: Janis Schoetterl-Glausch @ 2021-08-18 9:00 UTC (permalink / raw)
To: David Hildenbrand, Janis Schoetterl-Glausch, kvm, borntraeger,
frankja, imbrenda, Heiko Carstens, Vasily Gorbik
Cc: cohuck, linux-s390, linux-kernel
On 8/18/21 9:54 AM, David Hildenbrand wrote:
> On 16.08.21 17:07, Janis Schoetterl-Glausch wrote:
>> Introduce a helper function for guest frame access.
>> Rewrite the calculation of the gpa and the length of the segment
>> to be more readable.
>>
>> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
>> ---
>> arch/s390/kvm/gaccess.c | 48 +++++++++++++++++++++++++----------------
>> 1 file changed, 29 insertions(+), 19 deletions(-)
>>
>> diff --git a/arch/s390/kvm/gaccess.c b/arch/s390/kvm/gaccess.c
>> index b9f85b2dc053..df83de0843de 100644
>> --- a/arch/s390/kvm/gaccess.c
>> +++ b/arch/s390/kvm/gaccess.c
>> @@ -827,11 +827,26 @@ static int guest_page_range(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar,
>> return 0;
>> }
>> +static int access_guest_frame(struct kvm *kvm, enum gacc_mode mode, gpa_t gpa,
>> + void *data, unsigned int len)
>
> I know, "frame" is a beautiful term for "page" -- can we just avoid using it because we're not using it anywhere else here? :)
>
> What's wrong with "access_guest_page()" ?
Ok, I'll use page for consistency's sake.
>
>
>> +{
>> + gfn_t gfn = gpa_to_gfn(gpa);
>> + unsigned int offset = offset_in_page(gpa);
>> + int rc;
>
> You could turn both const. You might want to consider reverse-christmas-treeing this.
Ok
>
>> +
>> + if (mode == GACC_STORE)
>> + rc = kvm_write_guest_page(kvm, gfn, data, offset, len);
>> + else
>> + rc = kvm_read_guest_page(kvm, gfn, data, offset, len);
>
> Personally, I prefer passing in pfn + offset instead of a gpa. Also avoids having to convert back and forth.
In access_guest_real we get back the gpa directly from the translation function.
After the next patch the same is true for access_guest.
So using gpas everywhere is nicer.
And if we were to introduce a len_in_page function the offset would not even show up as an intermediary.
>
>> + return rc;
>> +}
>> +
>> int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
>> unsigned long len, enum gacc_mode mode)
>> {
>> psw_t *psw = &vcpu->arch.sie_block->gpsw;
>> - unsigned long _len, nr_pages, gpa, idx;
>> + unsigned long nr_pages, gpa, idx;
>> + unsigned int seg;
>
> Dito, reverse christmas tree might be worth keeping.
>
>> unsigned long pages_array[2];
>> unsigned long *pages;
>> int need_ipte_lock;
>> @@ -855,15 +870,12 @@ int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
>> ipte_lock(vcpu);
>> rc = guest_page_range(vcpu, ga, ar, pages, nr_pages, asce, mode);
>> for (idx = 0; idx < nr_pages && !rc; idx++) {
>> - gpa = *(pages + idx) + (ga & ~PAGE_MASK);
>> - _len = min(PAGE_SIZE - (gpa & ~PAGE_MASK), len);
>> - if (mode == GACC_STORE)
>> - rc = kvm_write_guest(vcpu->kvm, gpa, data, _len);
>> - else
>> - rc = kvm_read_guest(vcpu->kvm, gpa, data, _len);
>> - len -= _len;
>> - ga += _len;
>> - data += _len;
>> + gpa = pages[idx] + offset_in_page(ga);
>> + seg = min(PAGE_SIZE - offset_in_page(gpa), len);
>> + rc = access_guest_frame(vcpu->kvm, mode, gpa, data, seg);
>> + len -= seg;
>> + ga += seg;
>> + data += seg;
>> }
>> if (need_ipte_lock)
>> ipte_unlock(vcpu);
>> @@ -875,19 +887,17 @@ int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
>> int access_guest_real(struct kvm_vcpu *vcpu, unsigned long gra,
>> void *data, unsigned long len, enum gacc_mode mode)
>> {
>> - unsigned long _len, gpa;
>> + unsigned long gpa;
>> + unsigned int seg;
>> int rc = 0;
>> while (len && !rc) {
>> gpa = kvm_s390_real_to_abs(vcpu, gra);
>> - _len = min(PAGE_SIZE - (gpa & ~PAGE_MASK), len);
>> - if (mode)
>> - rc = write_guest_abs(vcpu, gpa, data, _len);
>> - else
>> - rc = read_guest_abs(vcpu, gpa, data, _len);
>> - len -= _len;
>> - gra += _len;
>> - data += _len;
>> + seg = min(PAGE_SIZE - offset_in_page(gpa), len);
>
> What does "seg" mean? I certainly know when "len" means -- which is also what the function eats.
>
>> + rc = access_guest_frame(vcpu->kvm, mode, gpa, data, seg);
>> + len -= seg;
>> + gra += seg;
>> + data += seg;
>> }
>> return rc;
>> }
>>
>
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 2/2] KVM: s390: gaccess: Refactor access address range check
2021-08-16 15:07 ` [PATCH 2/2] KVM: s390: gaccess: Refactor access address range check Janis Schoetterl-Glausch
@ 2021-08-18 10:08 ` Claudio Imbrenda
2021-08-19 12:39 ` Janis Schoetterl-Glausch
0 siblings, 1 reply; 12+ messages in thread
From: Claudio Imbrenda @ 2021-08-18 10:08 UTC (permalink / raw)
To: Janis Schoetterl-Glausch
Cc: kvm, borntraeger, frankja, Heiko Carstens, Vasily Gorbik, david,
cohuck, linux-s390, linux-kernel
On Mon, 16 Aug 2021 17:07:17 +0200
Janis Schoetterl-Glausch <scgl@linux.ibm.com> wrote:
> Do not round down the first address to the page boundary, just translate
> it normally, which gives the value we care about in the first place.
> Given this, translating a single address is just the special case of
> translating a range spanning a single page.
>
> Make the output optional, so the function can be used to just check a
> range.
I like the idea, but see a few nits below
>
> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
> ---
> arch/s390/kvm/gaccess.c | 91 ++++++++++++++++++-----------------------
> 1 file changed, 39 insertions(+), 52 deletions(-)
>
> diff --git a/arch/s390/kvm/gaccess.c b/arch/s390/kvm/gaccess.c
> index df83de0843de..e5a19d8b30e2 100644
> --- a/arch/s390/kvm/gaccess.c
> +++ b/arch/s390/kvm/gaccess.c
> @@ -794,35 +794,45 @@ static int low_address_protection_enabled(struct kvm_vcpu *vcpu,
> return 1;
> }
>
> -static int guest_page_range(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar,
> - unsigned long *pages, unsigned long nr_pages,
> - const union asce asce, enum gacc_mode mode)
> +/* Stores the gpas for each page in a real/virtual range into @gpas
> + * Modifies the 'struct kvm_s390_pgm_info pgm' member of @vcpu in the same
> + * way read_guest/write_guest do, the meaning of the return value is likewise
this comment is a bit confusing; why telling us to look what a
different function is doing?
either don't mention this at all (since it's more or less the expected
behaviour), or explain in full what's going on
> + * the same.
> + * If @gpas is NULL only the checks are performed.
> + */
> +static int guest_range_to_gpas(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar,
> + unsigned long *gpas, unsigned long len,
> + const union asce asce, enum gacc_mode mode)
> {
> psw_t *psw = &vcpu->arch.sie_block->gpsw;
> + unsigned long gpa;
> + unsigned int seg;
> + unsigned int offset = offset_in_page(ga);
> int lap_enabled, rc = 0;
> enum prot_type prot;
>
> lap_enabled = low_address_protection_enabled(vcpu, asce);
> - while (nr_pages) {
> + while ((seg = min(PAGE_SIZE - offset, len)) != 0) {
I'm not terribly fond of assignments-as-values; moreover offset is used
only once.
why not something like:
seg = min(PAGE_SIZE - offset, len);
while (seg) {
...
seg = min(PAGE_SIZE, len);
}
or maybe even:
seg = min(PAGE_SIZE - offset, len);
for (; seg; seg = min(PAGE_SIZE, len)) {
(although the one with the while is perhaps more readable)
> ga = kvm_s390_logical_to_effective(vcpu, ga);
> if (mode == GACC_STORE && lap_enabled && is_low_address(ga))
> return trans_exc(vcpu, PGM_PROTECTION, ga, ar, mode,
> PROT_TYPE_LA);
> - ga &= PAGE_MASK;
> if (psw_bits(*psw).dat) {
> - rc = guest_translate(vcpu, ga, pages, asce, mode, &prot);
> + rc = guest_translate(vcpu, ga, &gpa, asce, mode, &prot);
> if (rc < 0)
> return rc;
> } else {
> - *pages = kvm_s390_real_to_abs(vcpu, ga);
> - if (kvm_is_error_gpa(vcpu->kvm, *pages))
> + gpa = kvm_s390_real_to_abs(vcpu, ga);
> + if (kvm_is_error_gpa(vcpu->kvm, gpa))
> rc = PGM_ADDRESSING;
> }
> if (rc)
> return trans_exc(vcpu, rc, ga, ar, mode, prot);
> - ga += PAGE_SIZE;
> - pages++;
> - nr_pages--;
> + if (gpas)
> + *gpas++ = gpa;
> + offset = 0;
> + ga += seg;
> + len -= seg;
> }
> return 0;
> }
> @@ -845,10 +855,10 @@ int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
> unsigned long len, enum gacc_mode mode)
> {
> psw_t *psw = &vcpu->arch.sie_block->gpsw;
> - unsigned long nr_pages, gpa, idx;
> + unsigned long nr_pages, idx;
> unsigned int seg;
> - unsigned long pages_array[2];
> - unsigned long *pages;
> + unsigned long gpa_array[2];
> + unsigned long *gpas;
reverse Christmas tree?
also, since you're touching this: have you checked if a different size
for the array would bring any benefit?
2 seems a little too small, but I have no idea if anything bigger would
bring any advantages.
> int need_ipte_lock;
> union asce asce;
> int rc;
> @@ -860,27 +870,25 @@ int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
> if (rc)
> return rc;
> nr_pages = (((ga & ~PAGE_MASK) + len - 1) >> PAGE_SHIFT) + 1;
> - pages = pages_array;
> - if (nr_pages > ARRAY_SIZE(pages_array))
> - pages = vmalloc(array_size(nr_pages, sizeof(unsigned long)));
> - if (!pages)
> + gpas = gpa_array;
> + if (nr_pages > ARRAY_SIZE(gpa_array))
> + gpas = vmalloc(array_size(nr_pages, sizeof(unsigned long)));
> + if (!gpas)
> return -ENOMEM;
> need_ipte_lock = psw_bits(*psw).dat && !asce.r;
> if (need_ipte_lock)
> ipte_lock(vcpu);
> - rc = guest_page_range(vcpu, ga, ar, pages, nr_pages, asce, mode);
> + rc = guest_range_to_gpas(vcpu, ga, ar, gpas, len, asce, mode);
> for (idx = 0; idx < nr_pages && !rc; idx++) {
> - gpa = pages[idx] + offset_in_page(ga);
> - seg = min(PAGE_SIZE - offset_in_page(gpa), len);
> - rc = access_guest_frame(vcpu->kvm, mode, gpa, data, seg);
> + seg = min(PAGE_SIZE - offset_in_page(gpas[idx]), len);
> + rc = access_guest_frame(vcpu->kvm, mode, gpas[idx], data, seg);
> len -= seg;
> - ga += seg;
> data += seg;
> }
> if (need_ipte_lock)
> ipte_unlock(vcpu);
> - if (nr_pages > ARRAY_SIZE(pages_array))
> - vfree(pages);
> + if (nr_pages > ARRAY_SIZE(gpa_array))
> + vfree(gpas);
> return rc;
> }
>
> @@ -914,8 +922,6 @@ int access_guest_real(struct kvm_vcpu *vcpu, unsigned long gra,
> int guest_translate_address(struct kvm_vcpu *vcpu, unsigned long gva, u8 ar,
> unsigned long *gpa, enum gacc_mode mode)
> {
> - psw_t *psw = &vcpu->arch.sie_block->gpsw;
> - enum prot_type prot;
> union asce asce;
> int rc;
>
> @@ -923,23 +929,7 @@ int guest_translate_address(struct kvm_vcpu *vcpu, unsigned long gva, u8 ar,
> rc = get_vcpu_asce(vcpu, &asce, gva, ar, mode);
> if (rc)
> return rc;
> - if (is_low_address(gva) && low_address_protection_enabled(vcpu, asce)) {
> - if (mode == GACC_STORE)
> - return trans_exc(vcpu, PGM_PROTECTION, gva, 0,
> - mode, PROT_TYPE_LA);
> - }
> -
> - if (psw_bits(*psw).dat && !asce.r) { /* Use DAT? */
> - rc = guest_translate(vcpu, gva, gpa, asce, mode, &prot);
> - if (rc > 0)
> - return trans_exc(vcpu, rc, gva, 0, mode, prot);
> - } else {
> - *gpa = kvm_s390_real_to_abs(vcpu, gva);
> - if (kvm_is_error_gpa(vcpu->kvm, *gpa))
> - return trans_exc(vcpu, rc, gva, PGM_ADDRESSING, mode, 0);
> - }
> -
> - return rc;
> + return guest_range_to_gpas(vcpu, gva, ar, gpa, 1, asce, mode);
> }
>
> /**
> @@ -948,17 +938,14 @@ int guest_translate_address(struct kvm_vcpu *vcpu, unsigned long gva, u8 ar,
> int check_gva_range(struct kvm_vcpu *vcpu, unsigned long gva, u8 ar,
> unsigned long length, enum gacc_mode mode)
> {
> - unsigned long gpa;
> - unsigned long currlen;
> + union asce asce;
> int rc = 0;
>
> + rc = get_vcpu_asce(vcpu, &asce, gva, ar, mode);
> + if (rc)
> + return rc;
> ipte_lock(vcpu);
> - while (length > 0 && !rc) {
> - currlen = min(length, PAGE_SIZE - (gva % PAGE_SIZE));
> - rc = guest_translate_address(vcpu, gva, ar, &gpa, mode);
> - gva += currlen;
> - length -= currlen;
> - }
> + rc = guest_range_to_gpas(vcpu, gva, ar, NULL, length, asce, mode);
> ipte_unlock(vcpu);
>
> return rc;
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 2/2] KVM: s390: gaccess: Refactor access address range check
2021-08-18 10:08 ` Claudio Imbrenda
@ 2021-08-19 12:39 ` Janis Schoetterl-Glausch
0 siblings, 0 replies; 12+ messages in thread
From: Janis Schoetterl-Glausch @ 2021-08-19 12:39 UTC (permalink / raw)
To: Claudio Imbrenda, Janis Schoetterl-Glausch
Cc: kvm, borntraeger, frankja, Heiko Carstens, Vasily Gorbik, david,
cohuck, linux-s390, linux-kernel
On 8/18/21 12:08 PM, Claudio Imbrenda wrote:
> On Mon, 16 Aug 2021 17:07:17 +0200
> Janis Schoetterl-Glausch <scgl@linux.ibm.com> wrote:
>
>> Do not round down the first address to the page boundary, just translate
>> it normally, which gives the value we care about in the first place.
>> Given this, translating a single address is just the special case of
>> translating a range spanning a single page.
>>
>> Make the output optional, so the function can be used to just check a
>> range.
>
> I like the idea, but see a few nits below
>
>>
>> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
>> ---
>> arch/s390/kvm/gaccess.c | 91 ++++++++++++++++++-----------------------
>> 1 file changed, 39 insertions(+), 52 deletions(-)
>>
>> diff --git a/arch/s390/kvm/gaccess.c b/arch/s390/kvm/gaccess.c
>> index df83de0843de..e5a19d8b30e2 100644
>> --- a/arch/s390/kvm/gaccess.c
>> +++ b/arch/s390/kvm/gaccess.c
>> @@ -794,35 +794,45 @@ static int low_address_protection_enabled(struct kvm_vcpu *vcpu,
>> return 1;
>> }
>>
>> -static int guest_page_range(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar,
>> - unsigned long *pages, unsigned long nr_pages,
>> - const union asce asce, enum gacc_mode mode)
>> +/* Stores the gpas for each page in a real/virtual range into @gpas
>> + * Modifies the 'struct kvm_s390_pgm_info pgm' member of @vcpu in the same
>> + * way read_guest/write_guest do, the meaning of the return value is likewise
>
> this comment is a bit confusing; why telling us to look what a
> different function is doing?
>
> either don't mention this at all (since it's more or less the expected
> behaviour), or explain in full what's going on
Yeah, it's not ideal. I haven't decided yet what I'll do.
I think a comment would be helpful, and it may be expected behavior only if one has
looked at the code for long enough :).
>
>> + * the same.
>> + * If @gpas is NULL only the checks are performed.
>> + */
>> +static int guest_range_to_gpas(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar,
>> + unsigned long *gpas, unsigned long len,
>> + const union asce asce, enum gacc_mode mode)
>> {
>> psw_t *psw = &vcpu->arch.sie_block->gpsw;
>> + unsigned long gpa;
>> + unsigned int seg;
>> + unsigned int offset = offset_in_page(ga);
>> int lap_enabled, rc = 0;
>> enum prot_type prot;
>>
>> lap_enabled = low_address_protection_enabled(vcpu, asce);
>> - while (nr_pages) {
>> + while ((seg = min(PAGE_SIZE - offset, len)) != 0) {
>
> I'm not terribly fond of assignments-as-values; moreover offset is used
> only once.
>
> why not something like:
>
> seg = min(PAGE_SIZE - offset, len);
> while (seg) {
>
> ...
>
> seg = min(PAGE_SIZE, len);
> }
>
> or maybe even:
>
> seg = min(PAGE_SIZE - offset, len);
> for (; seg; seg = min(PAGE_SIZE, len)) {
>
> (although the one with the while is perhaps more readable)
That code pattern is not entirely uncommon, but I'll change it to:
while(min(PAGE_SIZE - offset, len) > 0) {
seg = min(PAGE_SIZE - offset, len);
...
}
which I think reads better than having the assignment at the end.
I assume the compiler gets rid of the redundancy.
>
[...]
>> @@ -845,10 +855,10 @@ int access_guest(struct kvm_vcpu *vcpu, unsigned long ga, u8 ar, void *data,
>> unsigned long len, enum gacc_mode mode)
>> {
>> psw_t *psw = &vcpu->arch.sie_block->gpsw;
>> - unsigned long nr_pages, gpa, idx;
>> + unsigned long nr_pages, idx;
>> unsigned int seg;
>> - unsigned long pages_array[2];
>> - unsigned long *pages;
>> + unsigned long gpa_array[2];
>> + unsigned long *gpas;
>
> reverse Christmas tree?
>
> also, since you're touching this: have you checked if a different size
> for the array would bring any benefit?
> 2 seems a little too small, but I have no idea if anything bigger would
> bring any advantages.
I have not checked it, no. When emulating instructions, you would only need >2
entries if an operand is >8k or >4k and weirdly aligned, hardly seems like a common occurrence.
On the other hand, bumping it up should not have any negative consequences.
I'll leave it as is.
[...]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 1/2] KVM: s390: gaccess: Cleanup access to guest frames
2021-08-18 8:06 ` Janosch Frank
2021-08-18 8:44 ` David Hildenbrand
@ 2021-08-19 13:53 ` Janis Schoetterl-Glausch
2021-08-19 14:11 ` Janosch Frank
1 sibling, 1 reply; 12+ messages in thread
From: Janis Schoetterl-Glausch @ 2021-08-19 13:53 UTC (permalink / raw)
To: Janosch Frank, David Hildenbrand, Janis Schoetterl-Glausch, kvm,
borntraeger, imbrenda, Heiko Carstens, Vasily Gorbik
Cc: cohuck, linux-s390, linux-kernel
On 8/18/21 10:06 AM, Janosch Frank wrote:
> On 8/18/21 9:54 AM, David Hildenbrand wrote:
>> On 16.08.21 17:07, Janis Schoetterl-Glausch wrote:
>>> Introduce a helper function for guest frame access.
>>> Rewrite the calculation of the gpa and the length of the segment
>>> to be more readable.
>>>
>>> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
> [...]
>>> - unsigned long _len, gpa;
>>> + unsigned long gpa;
>>> + unsigned int seg;
>>> int rc = 0;
>>>
>>> while (len && !rc) {
>>> gpa = kvm_s390_real_to_abs(vcpu, gra);
>>> - _len = min(PAGE_SIZE - (gpa & ~PAGE_MASK), len);
>>> - if (mode)
>>> - rc = write_guest_abs(vcpu, gpa, data, _len);
>>> - else
>>> - rc = read_guest_abs(vcpu, gpa, data, _len);
>>> - len -= _len;
>>> - gra += _len;
>>> - data += _len;
>>> + seg = min(PAGE_SIZE - offset_in_page(gpa), len);
>>
>> What does "seg" mean? I certainly know when "len" means -- which is also
>> what the function eats.
>
> What does "_len" mean especially in contrast to "len"?
>
> "seg" is used in the common kvm guest access functions so it's at least
> consistent although I share the sentiment that it's not a great name for
> the length we access inside the page.
>
> Originally I suggested "len_in_page" if you have a better name I'd
> expect we'll both be happy to discuss it :-)
fragment_len ?
>
>>
>>> + rc = access_guest_frame(vcpu->kvm, mode, gpa, data, seg);
>>> + len -= seg;
>>> + gra += seg;
>>> + data += seg;
>>> }
>>> return rc;
>>> }
>>>
>>
>>
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: [PATCH 1/2] KVM: s390: gaccess: Cleanup access to guest frames
2021-08-19 13:53 ` Janis Schoetterl-Glausch
@ 2021-08-19 14:11 ` Janosch Frank
0 siblings, 0 replies; 12+ messages in thread
From: Janosch Frank @ 2021-08-19 14:11 UTC (permalink / raw)
To: Janis Schoetterl-Glausch, David Hildenbrand,
Janis Schoetterl-Glausch, kvm, borntraeger, imbrenda,
Heiko Carstens, Vasily Gorbik
Cc: cohuck, linux-s390, linux-kernel
On 8/19/21 3:53 PM, Janis Schoetterl-Glausch wrote:
> On 8/18/21 10:06 AM, Janosch Frank wrote:
>> On 8/18/21 9:54 AM, David Hildenbrand wrote:
>>> On 16.08.21 17:07, Janis Schoetterl-Glausch wrote:
>>>> Introduce a helper function for guest frame access.
>>>> Rewrite the calculation of the gpa and the length of the segment
>>>> to be more readable.
>>>>
>>>> Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
>> [...]
>>>> - unsigned long _len, gpa;
>>>> + unsigned long gpa;
>>>> + unsigned int seg;
>>>> int rc = 0;
>>>>
>>>> while (len && !rc) {
>>>> gpa = kvm_s390_real_to_abs(vcpu, gra);
>>>> - _len = min(PAGE_SIZE - (gpa & ~PAGE_MASK), len);
>>>> - if (mode)
>>>> - rc = write_guest_abs(vcpu, gpa, data, _len);
>>>> - else
>>>> - rc = read_guest_abs(vcpu, gpa, data, _len);
>>>> - len -= _len;
>>>> - gra += _len;
>>>> - data += _len;
>>>> + seg = min(PAGE_SIZE - offset_in_page(gpa), len);
>>>
>>> What does "seg" mean? I certainly know when "len" means -- which is also
>>> what the function eats.
>>
>> What does "_len" mean especially in contrast to "len"?
>>
>> "seg" is used in the common kvm guest access functions so it's at least
>> consistent although I share the sentiment that it's not a great name for
>> the length we access inside the page.
>>
>> Originally I suggested "len_in_page" if you have a better name I'd
>> expect we'll both be happy to discuss it :-)
>
> fragment_len ?
Sounds good to me
>>
>>>
>>>> + rc = access_guest_frame(vcpu->kvm, mode, gpa, data, seg);
>>>> + len -= seg;
>>>> + gra += seg;
>>>> + data += seg;
>>>> }
>>>> return rc;
>>>> }
>>>>
>>>
>>>
>>
>
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2021-08-19 14:12 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20210816150718.3063877-1-scgl@linux.ibm.com>
2021-08-16 15:07 ` [PATCH 1/2] KVM: s390: gaccess: Cleanup access to guest frames Janis Schoetterl-Glausch
2021-08-18 7:46 ` Janosch Frank
2021-08-18 7:54 ` David Hildenbrand
2021-08-18 8:06 ` Janosch Frank
2021-08-18 8:44 ` David Hildenbrand
2021-08-18 8:48 ` Janis Schoetterl-Glausch
2021-08-19 13:53 ` Janis Schoetterl-Glausch
2021-08-19 14:11 ` Janosch Frank
2021-08-18 9:00 ` Janis Schoetterl-Glausch
2021-08-16 15:07 ` [PATCH 2/2] KVM: s390: gaccess: Refactor access address range check Janis Schoetterl-Glausch
2021-08-18 10:08 ` Claudio Imbrenda
2021-08-19 12:39 ` Janis Schoetterl-Glausch
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).