From: Bharata B Rao <bharata@linux.ibm.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: linuxppc-dev@lists.ozlabs.org, kvm-ppc@vger.kernel.org,
linux-mm@kvack.org, paulus@au1.ibm.com,
aneesh.kumar@linux.vnet.ibm.com, jglisse@redhat.com,
linuxram@us.ibm.com, sukadev@linux.vnet.ibm.com,
cclaudio@linux.ibm.com
Subject: Re: [RFC PATCH v4 6/6] kvmppc: Support reset of secure guest
Date: Tue, 09 Jul 2019 10:18:04 +0000 [thread overview]
Message-ID: <20190709100604.GD27933@in.ibm.com> (raw)
In-Reply-To: <20190617040632.jiq73ogxqyccvfjl@oak.ozlabs.ibm.com>
On Mon, Jun 17, 2019 at 02:06:32PM +1000, Paul Mackerras wrote:
> On Tue, May 28, 2019 at 12:19:33PM +0530, Bharata B Rao wrote:
> > Add support for reset of secure guest via a new ioctl KVM_PPC_SVM_OFF.
> > This ioctl will be issued by QEMU during reset and in this ioctl,
> > we ask UV to terminate the guest via UV_SVM_TERMINATE ucall,
> > reinitialize guest's partitioned scoped page tables and release all
> > HMM pages of the secure guest.
> >
> > After these steps, guest is ready to issue UV_ESM call once again
> > to switch to secure mode.
>
> Since you are adding a new KVM ioctl, you need to add a description of
> it to Documentation/virtual/kvm/api.txt.
Adding in the next version.
Regards,
Bharata.
WARNING: multiple messages have this Message-ID (diff)
From: Bharata B Rao <bharata@linux.ibm.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: linuxram@us.ibm.com, cclaudio@linux.ibm.com,
kvm-ppc@vger.kernel.org, linux-mm@kvack.org, jglisse@redhat.com,
aneesh.kumar@linux.vnet.ibm.com, paulus@au1.ibm.com,
sukadev@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH v4 6/6] kvmppc: Support reset of secure guest
Date: Tue, 9 Jul 2019 15:36:04 +0530 [thread overview]
Message-ID: <20190709100604.GD27933@in.ibm.com> (raw)
In-Reply-To: <20190617040632.jiq73ogxqyccvfjl@oak.ozlabs.ibm.com>
On Mon, Jun 17, 2019 at 02:06:32PM +1000, Paul Mackerras wrote:
> On Tue, May 28, 2019 at 12:19:33PM +0530, Bharata B Rao wrote:
> > Add support for reset of secure guest via a new ioctl KVM_PPC_SVM_OFF.
> > This ioctl will be issued by QEMU during reset and in this ioctl,
> > we ask UV to terminate the guest via UV_SVM_TERMINATE ucall,
> > reinitialize guest's partitioned scoped page tables and release all
> > HMM pages of the secure guest.
> >
> > After these steps, guest is ready to issue UV_ESM call once again
> > to switch to secure mode.
>
> Since you are adding a new KVM ioctl, you need to add a description of
> it to Documentation/virtual/kvm/api.txt.
Adding in the next version.
Regards,
Bharata.
WARNING: multiple messages have this Message-ID (diff)
From: Bharata B Rao <bharata@linux.ibm.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: linuxppc-dev@lists.ozlabs.org, kvm-ppc@vger.kernel.org,
linux-mm@kvack.org, paulus@au1.ibm.com,
aneesh.kumar@linux.vnet.ibm.com, jglisse@redhat.com,
linuxram@us.ibm.com, sukadev@linux.vnet.ibm.com,
cclaudio@linux.ibm.com
Subject: Re: [RFC PATCH v4 6/6] kvmppc: Support reset of secure guest
Date: Tue, 9 Jul 2019 15:36:04 +0530 [thread overview]
Message-ID: <20190709100604.GD27933@in.ibm.com> (raw)
In-Reply-To: <20190617040632.jiq73ogxqyccvfjl@oak.ozlabs.ibm.com>
On Mon, Jun 17, 2019 at 02:06:32PM +1000, Paul Mackerras wrote:
> On Tue, May 28, 2019 at 12:19:33PM +0530, Bharata B Rao wrote:
> > Add support for reset of secure guest via a new ioctl KVM_PPC_SVM_OFF.
> > This ioctl will be issued by QEMU during reset and in this ioctl,
> > we ask UV to terminate the guest via UV_SVM_TERMINATE ucall,
> > reinitialize guest's partitioned scoped page tables and release all
> > HMM pages of the secure guest.
> >
> > After these steps, guest is ready to issue UV_ESM call once again
> > to switch to secure mode.
>
> Since you are adding a new KVM ioctl, you need to add a description of
> it to Documentation/virtual/kvm/api.txt.
Adding in the next version.
Regards,
Bharata.
next prev parent reply other threads:[~2019-07-09 10:18 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 6:49 [PATCH v4 0/6] kvmppc: HMM driver to manage pages of secure guest Bharata B Rao
2019-05-28 6:49 ` Bharata B Rao
2019-05-28 6:49 ` Bharata B Rao
2019-05-28 6:49 ` [PATCH v4 1/6] kvmppc: HMM backend " Bharata B Rao
2019-05-28 6:49 ` Bharata B Rao
2019-05-28 6:49 ` Bharata B Rao
2019-06-17 5:31 ` Paul Mackerras
2019-06-17 5:31 ` Paul Mackerras
2019-06-17 5:31 ` Paul Mackerras
2019-07-09 10:03 ` Bharata B Rao
2019-07-09 10:15 ` Bharata B Rao
2019-07-09 10:03 ` Bharata B Rao
2019-05-28 6:49 ` [PATCH v4 2/6] kvmppc: Shared pages support for secure guests Bharata B Rao
2019-05-28 6:49 ` Bharata B Rao
2019-05-28 6:49 ` Bharata B Rao
2019-05-28 6:49 ` [PATCH v4 3/6] kvmppc: H_SVM_INIT_START and H_SVM_INIT_DONE hcalls Bharata B Rao
2019-05-28 6:49 ` Bharata B Rao
2019-05-28 6:49 ` Bharata B Rao
2019-06-17 5:37 ` Paul Mackerras
2019-06-17 5:37 ` Paul Mackerras
2019-06-17 5:37 ` Paul Mackerras
2019-07-09 10:04 ` Bharata B Rao
2019-07-09 10:16 ` Bharata B Rao
2019-07-09 10:04 ` Bharata B Rao
2019-06-18 23:05 ` Thiago Jung Bauermann
2019-06-18 23:05 ` Thiago Jung Bauermann
2019-06-18 23:05 ` Thiago Jung Bauermann
2019-07-09 10:05 ` Bharata B Rao
2019-07-09 10:17 ` Bharata B Rao
2019-07-09 10:05 ` Bharata B Rao
2019-05-28 6:49 ` [PATCH v4 4/6] kvmppc: Handle memory plug/unplug to secure VM Bharata B Rao
2019-05-28 6:49 ` Bharata B Rao
2019-05-28 6:49 ` Bharata B Rao
2019-06-17 5:38 ` Paul Mackerras
2019-06-17 5:38 ` Paul Mackerras
2019-06-17 5:38 ` Paul Mackerras
2019-05-28 6:49 ` [RFC PATCH v4 5/6] kvmppc: Radix changes for secure guest Bharata B Rao
2019-05-28 6:50 ` Bharata B Rao
2019-05-28 6:49 ` Bharata B Rao
2019-05-28 6:49 ` [RFC PATCH v4 6/6] kvmppc: Support reset of " Bharata B Rao
2019-05-28 6:50 ` Bharata B Rao
2019-05-28 6:49 ` Bharata B Rao
2019-06-17 4:06 ` Paul Mackerras
2019-06-17 4:06 ` Paul Mackerras
2019-06-17 4:06 ` Paul Mackerras
2019-07-09 10:06 ` Bharata B Rao [this message]
2019-07-09 10:18 ` Bharata B Rao
2019-07-09 10:06 ` Bharata B Rao
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=20190709100604.GD27933@in.ibm.com \
--to=bharata@linux.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=cclaudio@linux.ibm.com \
--cc=jglisse@redhat.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=linuxram@us.ibm.com \
--cc=paulus@au1.ibm.com \
--cc=paulus@ozlabs.org \
--cc=sukadev@linux.vnet.ibm.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.