| Message ID | 20220930210751.225873-9-scgl@linux.ibm.com (mailing list archive) |
|---|---|
| State | Accepted |
| Commit | 76a2ee43ed9a34f163d0331e3ba320c34c66c64e |
| Headers | show |
| Series | KVM: s390: Extend MEM_OP ioctl by storage key checked cmpxchg | expand |
On 10/1/22 04:07, Janis Schoetterl-Glausch wrote: > Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com> > --- > tools/testing/selftests/kvm/s390x/memop.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tools/testing/selftests/kvm/s390x/memop.c b/tools/testing/selftests/kvm/s390x/memop.c > index 3a160ab0415b..1887685b41d2 100644 > --- a/tools/testing/selftests/kvm/s390x/memop.c > +++ b/tools/testing/selftests/kvm/s390x/memop.c > @@ -970,7 +970,7 @@ static void test_errors_key_fetch_prot_override_enabled(void) > > /* > * vcpu, mismatching keys on fetch, > - * fetch protection override does not apply because memory range acceeded > + * fetch protection override does not apply because memory range exceeded > */ > CHECK_N_DO(ERR_PROT_MOP, t.vcpu, LOGICAL, READ, mem2, 2048 + 1, GADDR_V(0), KEY(2)); > CHECK_N_DO(ERR_PROT_MOP, t.vcpu, LOGICAL, READ, mem2, PAGE_SIZE + 2048 + 1, No patch description? Seriously? What about this one?: ``` The word "acceded" isn't the right word to describe too much memory situation. Substitute it with "exceeded". ``` Thanks.
On 30/09/2022 23.07, Janis Schoetterl-Glausch wrote: > Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com> > --- > tools/testing/selftests/kvm/s390x/memop.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/tools/testing/selftests/kvm/s390x/memop.c b/tools/testing/selftests/kvm/s390x/memop.c > index 3a160ab0415b..1887685b41d2 100644 > --- a/tools/testing/selftests/kvm/s390x/memop.c > +++ b/tools/testing/selftests/kvm/s390x/memop.c > @@ -970,7 +970,7 @@ static void test_errors_key_fetch_prot_override_enabled(void) > > /* > * vcpu, mismatching keys on fetch, > - * fetch protection override does not apply because memory range acceeded > + * fetch protection override does not apply because memory range exceeded > */ > CHECK_N_DO(ERR_PROT_MOP, t.vcpu, LOGICAL, READ, mem2, 2048 + 1, GADDR_V(0), KEY(2)); > CHECK_N_DO(ERR_PROT_MOP, t.vcpu, LOGICAL, READ, mem2, PAGE_SIZE + 2048 + 1, Reviewed-by: Thomas Huth <thuth@redhat.com>
diff --git a/tools/testing/selftests/kvm/s390x/memop.c b/tools/testing/selftests/kvm/s390x/memop.c index 3a160ab0415b..1887685b41d2 100644 --- a/tools/testing/selftests/kvm/s390x/memop.c +++ b/tools/testing/selftests/kvm/s390x/memop.c @@ -970,7 +970,7 @@ static void test_errors_key_fetch_prot_override_enabled(void) /* * vcpu, mismatching keys on fetch, - * fetch protection override does not apply because memory range acceeded + * fetch protection override does not apply because memory range exceeded */ CHECK_N_DO(ERR_PROT_MOP, t.vcpu, LOGICAL, READ, mem2, 2048 + 1, GADDR_V(0), KEY(2)); CHECK_N_DO(ERR_PROT_MOP, t.vcpu, LOGICAL, READ, mem2, PAGE_SIZE + 2048 + 1,
Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com> --- tools/testing/selftests/kvm/s390x/memop.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)