kvm-ppc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@linux.ibm.com>
To: Jordan Niethe <jniethe5@gmail.com>
Cc: mikey@neuling.org, sbhat@linux.ibm.com, kvm@vger.kernel.org,
	amachhiw@linux.vnet.ibm.com, gautam@linux.ibm.com,
	kvm-ppc@vger.kernel.org,
	"David.Laight@aculab.com" <David.Laight@ACULAB.COM>,
	Nicholas Piggin <npiggin@gmail.com>,
	vaibhav@linux.ibm.com,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	kconsul@linux.vnet.ibm.com
Subject: Re: [PATCH v4 00/11] KVM: PPC: Nested APIv2 guest support
Date: Thu, 07 Sep 2023 14:26:18 +0000	[thread overview]
Message-ID: <AE7EB275-86E6-45BB-9B55-701FA316B382@linux.ibm.com> (raw)
In-Reply-To: <20230905034658.82835-1-jniethe5@gmail.com>



> On 05-Sep-2023, at 9:16 AM, Jordan Niethe <jniethe5@gmail.com> wrote:
> 
> A nested-HV API for PAPR has been developed based on the KVM-specific
> nested-HV API that is upstream in Linux/KVM and QEMU. The PAPR API had
> to break compatibility to accommodate implementation in other
> hypervisors and partitioning firmware. The existing KVM-specific API
> will be known as the Nested APIv1 and the PAPR API will be known as the
> Nested APIv2. 
> 

I tested the Nested APIv2 support on a Power server. Was able to
bringup a L2 guest successfully. Additionally also tested the code
with avocado-vt based cpu, guest lifecycle and ras bucket.
The test completed successfully.

Based on this testing for patches 1 to 10

Tested-by: Sachin Sant <sachinp@linux.ibm.com>

- Sachin

      parent reply	other threads:[~2023-09-07 14:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05  3:46 [PATCH v4 00/11] KVM: PPC: Nested APIv2 guest support Jordan Niethe
2023-09-05  3:46 ` [PATCH v4 01/11] KVM: PPC: Always use the GPR accessors Jordan Niethe
2023-09-05  3:46 ` [PATCH v4 02/11] KVM: PPC: Introduce FPR/VR accessor functions Jordan Niethe
2023-09-05  3:46 ` [PATCH v4 03/11] KVM: PPC: Rename accessor generator macros Jordan Niethe
2023-09-05  3:46 ` [PATCH v4 04/11] KVM: PPC: Use accessors for VCPU registers Jordan Niethe
2023-09-05  3:46 ` [PATCH v4 05/11] KVM: PPC: Use accessors VCORE registers Jordan Niethe
2023-09-05  3:46 ` [PATCH v4 06/11] KVM: PPC: Book3S HV: Use accessors for VCPU registers Jordan Niethe
2023-09-05  3:46 ` [PATCH v4 07/11] KVM: PPC: Book3S HV: Introduce low level MSR accessor Jordan Niethe
2023-09-05  3:46 ` [PATCH v4 08/11] KVM: PPC: Add helper library for Guest State Buffers Jordan Niethe
2023-09-05  3:46 ` [PATCH v4 09/11] KVM: PPC: Book3s HV: Hold LPIDs in an unsigned long Jordan Niethe
2023-09-05  3:46 ` [PATCH v4 10/11] KVM: PPC: Add support for nestedv2 guests Jordan Niethe
2023-09-05  3:46 ` [PATCH v4 11/11] docs: powerpc: Document nested KVM on POWER Jordan Niethe
2023-09-07 14:26 ` Sachin Sant [this message]

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=AE7EB275-86E6-45BB-9B55-701FA316B382@linux.ibm.com \
    --to=sachinp@linux.ibm.com \
    --cc=David.Laight@ACULAB.COM \
    --cc=amachhiw@linux.vnet.ibm.com \
    --cc=gautam@linux.ibm.com \
    --cc=jniethe5@gmail.com \
    --cc=kconsul@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).