From: Laurent Vivier <lvivier@redhat.com>
To: Bharata B Rao <bharata@linux.ibm.com>, qemu-devel@nongnu.org
Cc: aneesh.kumar@linux.ibm.com, qemu-ppc@nongnu.org,
david@gibson.dropbear.id.au
Subject: Re: [RFC PATCH v0 2/2] ppc,spapr: Handle KVM_EXIT_ESN
Date: Thu, 5 Aug 2021 09:48:04 +0200 [thread overview]
Message-ID: <a7703577-9c69-cab7-6919-93c95d474a0f@redhat.com> (raw)
In-Reply-To: <20210805073228.502292-3-bharata@linux.ibm.com>
On 05/08/2021 09:32, Bharata B Rao wrote:
> Handle KVM_EXIT_ESN exit by issuing subvention notification
> interrupt to the guest. Guests supporting async-pf feature
> will need this interrupt to wake up tasks that are waiting
> for the expropriated pages to be available.
>
> Note: Updates to linux-headers/linux/kvm.h are temporary
> pending headers update.
>
> Signed-off-by: Bharata B Rao <bharata@linux.ibm.com>
> ---
> linux-headers/linux/kvm.h | 1 +
> target/ppc/kvm.c | 16 ++++++++++++++++
> 2 files changed, 17 insertions(+)
...
> diff --git a/target/ppc/kvm.c b/target/ppc/kvm.c
> index 330985c8a0..6bf3f06b88 100644
> --- a/target/ppc/kvm.c
> +++ b/target/ppc/kvm.c
...
> @@ -1657,6 +1658,16 @@ static int kvm_handle_debug(PowerPCCPU *cpu, struct kvm_run *run)
> return DEBUG_RETURN_GUEST;
> }
>
> +#if defined(TARGET_PPC64)
> +static void kvmppc_handle_esn(PowerPCCPU *cpu)
> +{
> + SpaprMachineState *spapr = SPAPR_MACHINE(qdev_get_machine());
> +
> + fprintf(stderr, "%s: ESN exit\n", __func__);
Do you keep this fprintf() on purpose?
You should use trace framework to add debugging traces.
Thanks,
Laurent
next prev parent reply other threads:[~2021-08-05 7:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 7:32 [RFC PATCH v0 0/2] Support for H_REG_SNS hcall Bharata B Rao
2021-08-05 7:32 ` [RFC PATCH v0 1/2] spapr: Add " Bharata B Rao
2021-08-06 19:25 ` Fabiano Rosas
2021-08-09 3:49 ` David Gibson
2021-08-11 9:26 ` Bharata B Rao
2021-08-12 1:24 ` David Gibson
2021-08-05 7:32 ` [RFC PATCH v0 2/2] ppc,spapr: Handle KVM_EXIT_ESN Bharata B Rao
2021-08-05 7:48 ` Laurent Vivier [this message]
2021-08-05 8:37 ` 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=a7703577-9c69-cab7-6919-93c95d474a0f@redhat.com \
--to=lvivier@redhat.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=bharata@linux.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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 NNTP newsgroup(s).