On 1/21/21 10:20 AM, Janosch Frank wrote:
On 1/21/21 10:13 AM, Pierre Morel wrote:
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@xxxxxxxxxxxxx>
Suggested-by: Janosch Frank <frankja@xxxxxxxxxxxxx>
Acked-by: Cornelia Huck <cohuck@xxxxxxxxxx>
Acked-by: Thomas Huth <thuth@xxxxxxxxxx>
---
lib/s390x/asm/uv.h | 38 ++++++++++++++++++++++++++++++++++++++
1 file changed, 38 insertions(+)
diff --git a/lib/s390x/asm/uv.h b/lib/s390x/asm/uv.h
index 4c2fc48..8400026 100644
--- a/lib/s390x/asm/uv.h
+++ b/lib/s390x/asm/uv.h
@@ -71,4 +71,42 @@ 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 == 0x0001)
s/0x0001/UVC_RC_EXECUTED/
OK
+ return 0;
+
+ report_info("cc %d response code: %04x", cc, uvcb.header.rc);
Will the print have the string UV in it or will I need to guess that a
UV call failed?
I will change for a more explicit
I'm wondering if an assert would make more sense, if callers are
interested in the uv rc they will need to write an own share function
anyway.
No need (reported OOB by Janosch)
Thanks,
Pierre
--
Pierre Morel
IBM Lab Boeblingen
