public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Janosch Frank <frankja@linux.ibm.com>
To: Pierre Morel <pmorel@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, david@redhat.com, thuth@redhat.com,
	cohuck@redhat.com, imbrenda@linux.ibm.com, drjones@redhat.com,
	pbonzini@redhat.com
Subject: Re: [kvm-unit-tests PATCH v4 1/3] s390x: pv: implement routine to share/unshare memory
Date: Thu, 21 Jan 2021 10:20:04 +0100	[thread overview]
Message-ID: <a4ad5c0f-2e77-4ea9-9efd-f4d000f17b72@linux.ibm.com> (raw)
In-Reply-To: <1611220392-22628-2-git-send-email-pmorel@linux.ibm.com>

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@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 | 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/


> +		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'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.

> +	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
> 

  reply	other threads:[~2021-01-21  9:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21  9:13 [kvm-unit-tests PATCH v4 0/3] s390x: css: pv: css test adaptation for PV Pierre Morel
2021-01-21  9:13 ` [kvm-unit-tests PATCH v4 1/3] s390x: pv: implement routine to share/unshare memory Pierre Morel
2021-01-21  9:20   ` Janosch Frank [this message]
2021-01-21  9:49     ` Janosch Frank
2021-01-21  9:52     ` Pierre Morel
2021-01-21  9:13 ` [kvm-unit-tests PATCH v4 2/3] s390x: define UV compatible I/O allocation Pierre Morel
2021-01-21  9:32   ` Thomas Huth
2021-01-22  7:55     ` Pierre Morel
2021-01-21  9:46   ` Janosch Frank
2021-01-21  9:57     ` Pierre Morel
2021-01-21 13:02     ` Pierre Morel
2021-01-21 13:43       ` Thomas Huth
2021-01-21 13:47         ` Pierre Morel
2021-01-21 13:56           ` Thomas Huth
2021-01-21 15:47             ` Pierre Morel
2021-01-21 13:48       ` Janosch Frank
2021-01-21 15:48         ` Pierre Morel
2021-01-21 13:33     ` Pierre Morel
2021-01-21  9:13 ` [kvm-unit-tests PATCH v4 3/3] s390x: css: pv: css test adaptation for PV Pierre Morel
2021-01-21  9:35   ` Thomas Huth
2021-01-21 13:25     ` Pierre Morel
2021-01-21  9:57   ` Janosch Frank
2021-01-21 13:25     ` Pierre Morel
2021-01-21 12:48   ` Cornelia Huck
2021-01-21 13:25     ` 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=a4ad5c0f-2e77-4ea9-9efd-f4d000f17b72@linux.ibm.com \
    --to=frankja@linux.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=drjones@redhat.com \
    --cc=imbrenda@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=pmorel@linux.ibm.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