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
Subject: [PATCH v1 0/3] s390x: css: adapting the I/O tests for PV
Date: Mon, 31 Aug 2020 14:05:30 +0200 [thread overview]
Message-ID: <1598875533-19947-1-git-send-email-pmorel@linux.ibm.com> (raw)
To adapt the test for PV we need to share the I/O memory with the host.
To do so we:
- implement the share/unshare ultravisor code.
- implement dedicated allocation routine which make sure that
- the I/O memory is on dedicated pages
- the I/O memory is shared if the guest is run under PV
- replace the start_single_ccw() by ccw_alloc() and start the
start_ccw1_chain() directly from the test function.
This allows to correctly free the I/O memory after the interruption.
Best regards,
Pierre
Pierre Morel (3):
s390x: pv: implement routine to share/unshare memory
s390: define UV compatible I/O allocation
s390x: css: pv: css test adaptation for PV
lib/s390x/asm/uv.h | 33 +++++++++++++++++++++++++++
lib/s390x/css.h | 3 +--
lib/s390x/css_lib.c | 28 +++++++----------------
lib/s390x/malloc_io.c | 53 +++++++++++++++++++++++++++++++++++++++++++
lib/s390x/malloc_io.h | 14 ++++++++++++
s390x/Makefile | 1 +
s390x/css.c | 35 +++++++++++++++++++---------
7 files changed, 134 insertions(+), 33 deletions(-)
create mode 100644 lib/s390x/malloc_io.c
create mode 100644 lib/s390x/malloc_io.h
--
2.25.1
next reply other threads:[~2020-08-31 12:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 12:05 Pierre Morel [this message]
2020-08-31 12:05 ` [PATCH v1 1/3] s390x: pv: implement routine to share/unshare memory Pierre Morel
2020-08-31 12:05 ` [PATCH v1 2/3] s390: define UV compatible I/O allocation Pierre Morel
2020-09-11 12:40 ` Cornelia Huck
2020-09-14 8:23 ` Pierre Morel
2020-08-31 12:05 ` [PATCH v1 3/3] 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=1598875533-19947-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=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