From: Nicholas Piggin <npiggin@gmail.com>
To: "Cédric Le Goater" <clg@kaod.org>,
"Fabiano Rosas" <farosas@linux.ibm.com>,
qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] spapr: prevent hdec timer being set up under virtual hypervisor
Date: Tue, 15 Feb 2022 08:59:30 +1000 [thread overview]
Message-ID: <1644879343.e91wwp3hqb.astroid@bobo.none> (raw)
In-Reply-To: <9494ba98-1d7c-8641-285b-c7fee3ec38d1@kaod.org>
Excerpts from Cédric Le Goater's message of February 15, 2022 4:05 am:
> On 2/14/22 14:32, Fabiano Rosas wrote:
>> Nicholas Piggin <npiggin@gmail.com> writes:
>>
>>> The spapr virtual hypervisor does not require the hdecr timer.
>>
>> Why is that? Is this not needed for an emulated powernv running KVM
>> guests?
Yeah, powernv does not use the virtual hypervisor, that's just for
pseries.
> It is now also running in the QEMU pseries machine (L0) when a
> nested is running. That's part of the implementation Nick did for
> the KVM-on-pseries-in-QEMU-TCG.
>
> But isn't that redundant with the cpu_ppc_hdecr_init() and
> cpu_ppc_hdecr_exit() from the RFC ? and shouldn't that be
> created only once, when the first nested is started or when
> the machine is if cap-nested-hv=on ?
For now I create the timer for a vcpu while it is in H_ENTER_NESTED
and destroy it when the hcall returns.
Thanks,
Nick
>
>>> Remove it.
>>>
>>> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
>>> ---
>>> hw/ppc/ppc.c | 2 +-
>>> hw/ppc/spapr_cpu_core.c | 6 +++---
>>> 2 files changed, 4 insertions(+), 4 deletions(-)
>>>
>>> diff --git a/hw/ppc/ppc.c b/hw/ppc/ppc.c
>>> index 462c87dba8..a7c262db93 100644
>>> --- a/hw/ppc/ppc.c
>>> +++ b/hw/ppc/ppc.c
>>> @@ -1072,7 +1072,7 @@ clk_setup_cb cpu_ppc_tb_init (CPUPPCState *env, uint32_t freq)
>>> }
>>> /* Create new timer */
>>> tb_env->decr_timer = timer_new_ns(QEMU_CLOCK_VIRTUAL, &cpu_ppc_decr_cb, cpu);
>>> - if (env->has_hv_mode) {
>>> + if (env->has_hv_mode && !cpu->vhyp) {
>
> hmm, Can we have (env->has_hv_mode && cpu->vhyp) ? this is confusing :/
>
> Thanks,
>
> C.
>
>
>>> tb_env->hdecr_timer = timer_new_ns(QEMU_CLOCK_VIRTUAL, &cpu_ppc_hdecr_cb,
>>> cpu);
>>> } else {
>>> diff --git a/hw/ppc/spapr_cpu_core.c b/hw/ppc/spapr_cpu_core.c
>>> index a781e97f8d..ed84713960 100644
>>> --- a/hw/ppc/spapr_cpu_core.c
>>> +++ b/hw/ppc/spapr_cpu_core.c
>>> @@ -261,12 +261,12 @@ static bool spapr_realize_vcpu(PowerPCCPU *cpu, SpaprMachineState *spapr,
>>> return false;
>>> }
>>>
>>> - /* Set time-base frequency to 512 MHz */
>>> - cpu_ppc_tb_init(env, SPAPR_TIMEBASE_FREQ);
>>> -
>>> cpu_ppc_set_vhyp(cpu, PPC_VIRTUAL_HYPERVISOR(spapr));
>>> kvmppc_set_papr(cpu);
>>>
>>> + /* Set time-base frequency to 512 MHz. vhyp must be set first. */
>>> + cpu_ppc_tb_init(env, SPAPR_TIMEBASE_FREQ);
>>> +
>>> if (spapr_irq_cpu_intc_create(spapr, cpu, errp) < 0) {
>>> qdev_unrealize(DEVICE(cpu));
>>> return false;
>>
>
>
prev parent reply other threads:[~2022-02-14 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 12:31 [PATCH] spapr: prevent hdec timer being set up under virtual hypervisor Nicholas Piggin
2022-02-14 13:16 ` Daniel Henrique Barboza
2022-02-14 13:32 ` Fabiano Rosas
2022-02-14 18:05 ` Cédric Le Goater
2022-02-14 22:59 ` Nicholas Piggin [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=1644879343.e91wwp3hqb.astroid@bobo.none \
--to=npiggin@gmail.com \
--cc=clg@kaod.org \
--cc=farosas@linux.ibm.com \
--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).