From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
KVM <kvm@vger.kernel.org>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
David Hildenbrand <david@redhat.com>,
linux-s390 <linux-s390@vger.kernel.org>,
Thomas Huth <thuth@redhat.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH/RFC] KVM: selftests: introduce P44V64 for z196 and EC12
Date: Mon, 05 Jul 2021 12:34:00 +0200 [thread overview]
Message-ID: <87o8bhhwx3.fsf@redhat.com> (raw)
In-Reply-To: <20210701153853.33063-1-borntraeger@de.ibm.com>
On Thu, Jul 01 2021, Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> Older machines likes z196 and zEC12 do only support 44 bits of physical
s/likes/like/
> addresses. Make this the default and check via IBC if we are on a later
> machine. We then add P47V64 as an additional model.
>
> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> Fixes: 1bc603af73dd ("KVM: selftests: introduce P47V64 for s390x")
> ---
> tools/testing/selftests/kvm/include/kvm_util.h | 3 ++-
> tools/testing/selftests/kvm/lib/guest_modes.c | 16 ++++++++++++++++
> tools/testing/selftests/kvm/lib/kvm_util.c | 5 +++++
> 3 files changed, 23 insertions(+), 1 deletion(-)
>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2021-07-05 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 15:38 [PATCH/RFC] KVM: selftests: introduce P44V64 for z196 and EC12 Christian Borntraeger
2021-07-05 9:53 ` David Hildenbrand
2021-07-05 9:59 ` Christian Borntraeger
2021-07-05 10:05 ` David Hildenbrand
2021-07-05 10:16 ` Thomas Huth
2021-07-05 10:34 ` Cornelia Huck [this message]
2021-07-06 7:40 ` Christian Borntraeger
2021-07-06 7:45 ` Christian Borntraeger
2021-07-06 8:18 ` Christian Borntraeger
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=87o8bhhwx3.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.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