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, drjones@redhat.com, pbonzini@redhat.com
Subject: [kvm-unit-tests PATCH v5 1/3] s390x: pv: implement routine to share/unshare memory
Date: Fri, 22 Jan 2021 14:27:38 +0100 [thread overview]
Message-ID: <1611322060-1972-2-git-send-email-pmorel@linux.ibm.com> (raw)
In-Reply-To: <1611322060-1972-1-git-send-email-pmorel@linux.ibm.com>
When communicating with the host we need to share part of
the memory.
Let's implement the ultravisor calls for this.
Signed-off-by: Pierre Morel <pmorel@linux.ibm.com>
Suggested-by: Janosch Frank <frankja@linux.ibm.com>
Acked-by: Cornelia Huck <cohuck@redhat.com>
Acked-by: Thomas Huth <thuth@redhat.com>
---
lib/s390x/asm/uv.h | 39 +++++++++++++++++++++++++++++++++++++++
1 file changed, 39 insertions(+)
diff --git a/lib/s390x/asm/uv.h b/lib/s390x/asm/uv.h
index 39d2dc0..9c49184 100644
--- a/lib/s390x/asm/uv.h
+++ b/lib/s390x/asm/uv.h
@@ -79,4 +79,43 @@ static inline int uv_call(unsigned long r1, unsigned long r2)
return cc;
}
+static inline int share(unsigned long addr, u16 cmd)
+{
+ struct uv_cb_share uvcb = {
+ .header.cmd = cmd,
+ .header.len = sizeof(uvcb),
+ .paddr = addr
+ };
+ int cc;
+
+ cc = uv_call(0, (u64)&uvcb);
+ if (!cc && uvcb.header.rc == UVC_RC_EXECUTED)
+ return 0;
+
+ report_info("uv_call: cmd %04x cc %d response code: %04x", cc, cmd,
+ uvcb.header.rc);
+ return -1;
+}
+
+/*
+ * Guest 2 request to the Ultravisor to make a page shared with the
+ * hypervisor for IO.
+ *
+ * @addr: Real or absolute address of the page to be shared
+ */
+static inline int uv_set_shared(unsigned long addr)
+{
+ return share(addr, UVC_CMD_SET_SHARED_ACCESS);
+}
+
+/*
+ * Guest 2 request to the Ultravisor to make a page unshared.
+ *
+ * @addr: Real or absolute address of the page to be unshared
+ */
+static inline int uv_remove_shared(unsigned long addr)
+{
+ return share(addr, UVC_CMD_REMOVE_SHARED_ACCESS);
+}
+
#endif
--
2.17.1
next prev parent reply other threads:[~2021-01-22 13:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 13:27 [kvm-unit-tests PATCH v5 0/3] s390x: css: pv: css test adaptation for PV Pierre Morel
2021-01-22 13:27 ` Pierre Morel [this message]
2021-01-22 13:33 ` [kvm-unit-tests PATCH v5 1/3] s390x: pv: implement routine to share/unshare memory Janosch Frank
2021-01-22 15:44 ` Pierre Morel
2021-01-22 13:27 ` [kvm-unit-tests PATCH v5 2/3] s390x: define UV compatible I/O allocation Pierre Morel
2021-01-22 13:57 ` Janosch Frank
2021-01-22 15:38 ` Pierre Morel
2021-01-22 14:12 ` Thomas Huth
2021-01-22 15:43 ` Pierre Morel
2021-01-27 10:47 ` Cornelia Huck
2021-01-27 12:40 ` Pierre Morel
2021-01-22 13:27 ` [kvm-unit-tests PATCH v5 3/3] s390x: css: pv: css test adaptation for PV Pierre Morel
2021-01-27 12:37 ` [kvm-unit-tests PATCH v5 0/3] " Janosch Frank
2021-01-27 12:40 ` 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=1611322060-1972-2-git-send-email-pmorel@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=drjones@redhat.com \
--cc=frankja@linux.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