From: Pierre Morel <pmorel@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, frankja@linux.ibm.com,
david@redhat.com, thuth@redhat.com, cohuck@redhat.com,
imbrenda@linux.ibm.com
Subject: [kvm-unit-tests PATCH v2 0/4] s390x: css: pv: css test adaptation for PV
Date: Mon, 28 Sep 2020 16:23:33 +0200 [thread overview]
Message-ID: <1601303017-8176-1-git-send-email-pmorel@linux.ibm.com> (raw)
Hi all,
I send a v2 even I got not a lot of answers for v1 because:
1 I forgot the kvm-unit-test header
2 the patch on uv.h was very bad
3 I saw some stupid errors I can correct myself like
to zero the allocated page before use or free it on error.
That said, here what is done:
To adapt the CSS I/O tests to protected virtualisation we need
utilities to:
1- allocate the I/O buffers in a private page (patch 3)
It must be in a dedicated page to avoid exporting code or
guest private data to the host.
2- share the I/O buffer with the host (patch 2)
3- be sure to allocate memory under 2Gb (patch 1)
The 3 first patches are the implementation of the tools,
patch 4 is the modification of the css.c test for PV.
regards,
Pierre
Pierre Morel (4):
memory: allocation in low memory
s390x: pv: implement routine to share/unshare memory
s390x: define UV compatible I/O allocation
s390x: css: pv: css test adaptation for PV
lib/alloc_dma_page.c | 57 +++++++++++++++++++++++++++++++++++++++++++
lib/alloc_dma_page.h | 24 ++++++++++++++++++
lib/s390x/asm/uv.h | 50 +++++++++++++++++++++++++++++++++++++
lib/s390x/css.h | 3 +--
lib/s390x/css_lib.c | 28 ++++++---------------
lib/s390x/malloc_io.c | 49 +++++++++++++++++++++++++++++++++++++
lib/s390x/malloc_io.h | 18 ++++++++++++++
lib/s390x/sclp.c | 2 ++
s390x/Makefile | 2 ++
s390x/css.c | 35 +++++++++++++++++---------
10 files changed, 235 insertions(+), 33 deletions(-)
create mode 100644 lib/alloc_dma_page.c
create mode 100644 lib/alloc_dma_page.h
create mode 100644 lib/s390x/malloc_io.c
create mode 100644 lib/s390x/malloc_io.h
--
2.25.1
changelog:
from v1:
- add the kvm-unit-test header
- correct checks for errors on Set/Remove Shared Access
- Add report for uv Set/Remove Shared Access
- zero the allocated I/O page before use
- free the page on error.
next reply other threads:[~2020-09-28 14:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 14:23 Pierre Morel [this message]
2020-09-28 14:23 ` [kvm-unit-tests PATCH v2 1/4] memory: allocation in low memory Pierre Morel
2020-09-28 15:31 ` Cornelia Huck
2020-09-29 7:19 ` Janosch Frank
2020-11-05 12:16 ` Pierre Morel
2020-11-05 14:15 ` Janosch Frank
2020-11-06 9:46 ` Andrew Jones
2020-11-06 13:25 ` Paolo Bonzini
2020-11-09 9:13 ` Pierre Morel
2020-09-28 14:23 ` [kvm-unit-tests PATCH v2 2/4] s390x: pv: implement routine to share/unshare memory Pierre Morel
2020-09-29 10:51 ` Cornelia Huck
2020-09-28 14:23 ` [kvm-unit-tests PATCH v2 3/4] s390x: define UV compatible I/O allocation Pierre Morel
2020-09-28 14:23 ` [kvm-unit-tests PATCH v2 4/4] s390x: css: pv: css test adaptation for PV 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=1601303017-8176-1-git-send-email-pmorel@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--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