From: Gautam Menghani <gautam@linux.ibm.com>
To: Jordan Niethe <jpn@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, mikey@neuling.org,
kautuk.consul.1980@gmail.com, kvm@vger.kernel.org,
npiggin@gmail.com, kvm-ppc@vger.kernel.org, sbhat@linux.ibm.com,
vaibhav@linux.ibm.com
Subject: Re: [PATCH RFC v2 6/6] docs: powerpc: Document nested KVM on POWER
Date: Wed, 7 Jun 2023 11:07:40 +0530 [thread overview]
Message-ID: <ZIAXpMpjb3V852rB@li-c6426e4c-27cf-11b2-a85c-95d65bc0de0e.ibm.com> (raw)
In-Reply-To: <20230605064848.12319-7-jpn@linux.vnet.ibm.com>
On Mon, Jun 05, 2023 at 04:48:48PM +1000, Jordan Niethe wrote:
> From: Michael Neuling <mikey@neuling.org>
Hi,
There are some minor typos in the documentation pointed out below
> +H_GUEST_GET_STATE()
> +-------------------
> +
> +This is called to get state associated with an L2 (Guest-wide or vCPU specific).
> +This info is passed via the Guest State Buffer (GSB), a standard format as
> +explained later in this doc, necessary details below:
> +
> +This can set either L2 wide or vcpu specific information. Examples of
We are getting the info about vcpu here : s/set/get
> +H_GUEST_RUN_VCPU()
> +------------------
> +
> +This is called to run an L2 vCPU. The L2 and vCPU IDs are passed in as
> +parameters. The vCPU run with the state set previously using
Minor nit : s/run/runs
> +H_GUEST_SET_STATE(). When the L2 exits, the L1 will resume from this
> +hcall.
> +
> +This hcall also has associated input and output GSBs. Unlike
> +H_GUEST_{S,G}ET_STATE(), these GSB pointers are not passed in as
> +parameters to the hcall (This was done in the interest of
> +performance). The locations of these GSBs must be preregistered using
> +the H_GUEST_SET_STATE() call with ID 0x0c00 and 0x0c01 (see table
> +below).
> +
>
> --
> 2.31.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Gautam Menghani <gautam@linux.ibm.com>
To: Jordan Niethe <jpn@linux.vnet.ibm.com>
Cc: mikey@neuling.org, kautuk.consul.1980@gmail.com,
kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, npiggin@gmail.com,
sbhat@linux.ibm.com, vaibhav@linux.ibm.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH RFC v2 6/6] docs: powerpc: Document nested KVM on POWER
Date: Wed, 7 Jun 2023 11:07:40 +0530 [thread overview]
Message-ID: <ZIAXpMpjb3V852rB@li-c6426e4c-27cf-11b2-a85c-95d65bc0de0e.ibm.com> (raw)
In-Reply-To: <20230605064848.12319-7-jpn@linux.vnet.ibm.com>
On Mon, Jun 05, 2023 at 04:48:48PM +1000, Jordan Niethe wrote:
> From: Michael Neuling <mikey@neuling.org>
Hi,
There are some minor typos in the documentation pointed out below
> +H_GUEST_GET_STATE()
> +-------------------
> +
> +This is called to get state associated with an L2 (Guest-wide or vCPU specific).
> +This info is passed via the Guest State Buffer (GSB), a standard format as
> +explained later in this doc, necessary details below:
> +
> +This can set either L2 wide or vcpu specific information. Examples of
We are getting the info about vcpu here : s/set/get
> +H_GUEST_RUN_VCPU()
> +------------------
> +
> +This is called to run an L2 vCPU. The L2 and vCPU IDs are passed in as
> +parameters. The vCPU run with the state set previously using
Minor nit : s/run/runs
> +H_GUEST_SET_STATE(). When the L2 exits, the L1 will resume from this
> +hcall.
> +
> +This hcall also has associated input and output GSBs. Unlike
> +H_GUEST_{S,G}ET_STATE(), these GSB pointers are not passed in as
> +parameters to the hcall (This was done in the interest of
> +performance). The locations of these GSBs must be preregistered using
> +the H_GUEST_SET_STATE() call with ID 0x0c00 and 0x0c01 (see table
> +below).
> +
>
> --
> 2.31.1
>
WARNING: multiple messages have this Message-ID (diff)
From: Gautam Menghani <gautam@linux.ibm.com>
To: Jordan Niethe <jpn@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, mikey@neuling.org,
kautuk.consul.1980@gmail.com, kvm@vger.kernel.org,
npiggin@gmail.com, kvm-ppc@vger.kernel.org, sbhat@linux.ibm.com,
vaibhav@linux.ibm.com
Subject: Re: [PATCH RFC v2 6/6] docs: powerpc: Document nested KVM on POWER
Date: Wed, 07 Jun 2023 05:49:40 +0000 [thread overview]
Message-ID: <ZIAXpMpjb3V852rB@li-c6426e4c-27cf-11b2-a85c-95d65bc0de0e.ibm.com> (raw)
In-Reply-To: <20230605064848.12319-7-jpn@linux.vnet.ibm.com>
On Mon, Jun 05, 2023 at 04:48:48PM +1000, Jordan Niethe wrote:
> From: Michael Neuling <mikey@neuling.org>
Hi,
There are some minor typos in the documentation pointed out below
> +H_GUEST_GET_STATE()
> +-------------------
> +
> +This is called to get state associated with an L2 (Guest-wide or vCPU specific).
> +This info is passed via the Guest State Buffer (GSB), a standard format as
> +explained later in this doc, necessary details below:
> +
> +This can set either L2 wide or vcpu specific information. Examples of
We are getting the info about vcpu here : s/set/get
> +H_GUEST_RUN_VCPU()
> +------------------
> +
> +This is called to run an L2 vCPU. The L2 and vCPU IDs are passed in as
> +parameters. The vCPU run with the state set previously using
Minor nit : s/run/runs
> +H_GUEST_SET_STATE(). When the L2 exits, the L1 will resume from this
> +hcall.
> +
> +This hcall also has associated input and output GSBs. Unlike
> +H_GUEST_{S,G}ET_STATE(), these GSB pointers are not passed in as
> +parameters to the hcall (This was done in the interest of
> +performance). The locations of these GSBs must be preregistered using
> +the H_GUEST_SET_STATE() call with ID 0x0c00 and 0x0c01 (see table
> +below).
> +
>
> --
> 2.31.1
>
next prev parent reply other threads:[~2023-06-07 5:38 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 6:48 [RFC PATCH v2 0/6] KVM: PPC: Nested PAPR guests Jordan Niethe
2023-06-05 6:48 ` Jordan Niethe
2023-06-05 6:48 ` Jordan Niethe
2023-06-05 6:48 ` [RFC PATCH v2 1/6] KVM: PPC: Use getters and setters for vcpu register state Jordan Niethe
2023-06-05 6:48 ` Jordan Niethe
2023-06-05 6:48 ` Jordan Niethe
2023-06-07 7:51 ` Nicholas Piggin
2023-06-07 7:51 ` Nicholas Piggin
2023-06-07 7:51 ` Nicholas Piggin
2023-06-10 1:52 ` Jordan Niethe
2023-06-10 1:52 ` Jordan Niethe
2023-06-10 1:52 ` Jordan Niethe
2023-06-05 6:48 ` [RFC PATCH v2 2/6] KVM: PPC: Add fpr getters and setters Jordan Niethe
2023-06-05 6:48 ` Jordan Niethe
2023-06-05 6:48 ` Jordan Niethe
2023-06-07 7:55 ` Nicholas Piggin
2023-06-07 7:55 ` Nicholas Piggin
2023-06-07 7:55 ` Nicholas Piggin
2023-06-10 1:54 ` Jordan Niethe
2023-06-10 1:54 ` Jordan Niethe
2023-06-10 1:54 ` Jordan Niethe
2023-06-05 6:48 ` [RFC PATCH v2 3/6] KVM: PPC: Add vr " Jordan Niethe
2023-06-05 6:48 ` Jordan Niethe
2023-06-05 6:48 ` Jordan Niethe
2023-06-05 6:48 ` [RFC PATCH v2 4/6] KVM: PPC: Add helper library for Guest State Buffers Jordan Niethe
2023-06-05 6:48 ` Jordan Niethe
2023-06-05 6:48 ` Jordan Niethe
2023-06-07 8:26 ` Nicholas Piggin
2023-06-07 8:26 ` Nicholas Piggin
2023-06-07 8:26 ` Nicholas Piggin
2023-06-10 2:09 ` Jordan Niethe
2023-06-10 2:09 ` Jordan Niethe
2023-06-10 2:09 ` Jordan Niethe
2023-06-05 6:48 ` [RFC PATCH v2 5/6] KVM: PPC: Add support for nested PAPR guests Jordan Niethe
2023-06-05 6:48 ` Jordan Niethe
2023-06-05 6:48 ` Jordan Niethe
2023-06-07 9:08 ` Nicholas Piggin
2023-06-07 9:08 ` Nicholas Piggin
2023-06-07 9:08 ` Nicholas Piggin
2023-06-10 2:16 ` Jordan Niethe
2023-06-10 2:16 ` Jordan Niethe
2023-06-10 2:16 ` Jordan Niethe
2023-06-05 6:48 ` [RFC PATCH v2 6/6] docs: powerpc: Document nested KVM on POWER Jordan Niethe
2023-06-05 6:48 ` Jordan Niethe
2023-06-05 6:48 ` Jordan Niethe
2023-06-07 5:37 ` Gautam Menghani [this message]
2023-06-07 5:49 ` [PATCH RFC " Gautam Menghani
2023-06-07 5:37 ` Gautam Menghani
2023-06-10 1:39 ` Jordan Niethe
2023-06-10 1:39 ` Jordan Niethe
2023-06-10 1:39 ` Jordan Niethe
2023-06-07 5:53 ` [RFC PATCH v2 0/6] KVM: PPC: Nested PAPR guests Nicholas Piggin
2023-06-07 5:53 ` Nicholas Piggin
2023-06-07 5:53 ` Nicholas Piggin
2023-06-10 1:46 ` Jordan Niethe
2023-06-10 1:46 ` Jordan Niethe
2023-06-10 1:46 ` Jordan Niethe
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=ZIAXpMpjb3V852rB@li-c6426e4c-27cf-11b2-a85c-95d65bc0de0e.ibm.com \
--to=gautam@linux.ibm.com \
--cc=jpn@linux.vnet.ibm.com \
--cc=kautuk.consul.1980@gmail.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=npiggin@gmail.com \
--cc=sbhat@linux.ibm.com \
--cc=vaibhav@linux.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.