All of lore.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 v5 0/3] s390x: css: pv: css test adaptation for PV
Date: Wed, 27 Jan 2021 13:37:50 +0100	[thread overview]
Message-ID: <6c141deb-819a-ef03-f44c-bd61561a2087@linux.ibm.com> (raw)
In-Reply-To: <1611322060-1972-1-git-send-email-pmorel@linux.ibm.com>

On 1/22/21 2:27 PM, Pierre Morel wrote:
> Hi all,
>   
> To adapt the CSS I/O tests to protected virtualisation we need
> utilities to: 
> 
> 1- allocate the I/O buffers in a private page using (patch 2)
>    It must be in a dedicated page to avoid exporting code or
>    guest private data to the host.
>    We accept a size in byte and flags and allocate page integral
>    memory to handle the Protected Virtualization.
>  
> 2- share the I/O buffers with the host (patch 1)
>    This patch uses the page allocator reworked by Claudio.
>  
> The 2 first patches are the implementation of the tools,
> patch 3 is the modification of the css.c test for PV.
> 
> The checkpatch always asked me to modify MAINTAINERS,
> so I added me as reviewer to be in copy for CSS at least.
> May be we could create a finer grain MAINTAINERS in the
> future.
> 
> regards,
> Pierre

Thanks, picked.


> 
> 
> Pierre Morel (3):
>   s390x: pv: implement routine to share/unshare memory
>   s390x: define UV compatible I/O allocation
>   s390x: css: pv: css test adaptation for PV
> 
>  lib/s390x/asm/uv.h    | 39 ++++++++++++++++++++++++
>  lib/s390x/css.h       |  3 +-
>  lib/s390x/css_lib.c   | 28 +++++------------
>  lib/s390x/malloc_io.c | 71 +++++++++++++++++++++++++++++++++++++++++++
>  lib/s390x/malloc_io.h | 45 +++++++++++++++++++++++++++
>  s390x/Makefile        |  1 +
>  s390x/css.c           | 43 ++++++++++++++++++--------
>  7 files changed, 196 insertions(+), 34 deletions(-)
>  create mode 100644 lib/s390x/malloc_io.c
>  create mode 100644 lib/s390x/malloc_io.h
> 

  parent reply	other threads:[~2021-01-27 12:38 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 ` [kvm-unit-tests PATCH v5 1/3] s390x: pv: implement routine to share/unshare memory Pierre Morel
2021-01-22 13:33   ` 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 ` Janosch Frank [this message]
2021-01-27 12:40   ` [kvm-unit-tests PATCH v5 0/3] " 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=6c141deb-819a-ef03-f44c-bd61561a2087@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.