From: Dongli Zhang <dongli.zhang@oracle.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xenproject.org, x86@kernel.org
Cc: linux-kernel@vger.kernel.org, jgross@suse.com,
sstabellini@kernel.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, joe.jin@oracle.com
Subject: Re: [PATCH v4 2/2] xen: delay xen_hvm_init_time_ops() if kdump is boot on vcpu>=32
Date: Wed, 2 Mar 2022 16:31:51 -0800 [thread overview]
Message-ID: <0ac50fb6-0aca-e61a-1f38-8badbc8c967a@oracle.com> (raw)
In-Reply-To: <bacae45c-9f8e-456b-1036-7f68e1e4374d@oracle.com>
Hi Boris,
On 3/2/22 4:20 PM, Boris Ostrovsky wrote:
>
> On 3/2/22 11:40 AM, Dongli Zhang wrote:
>> void __init xen_hvm_init_time_ops(void)
>> {
>> + static bool hvm_time_initialized;
>> +
>> + if (hvm_time_initialized)
>> + return;
>> +
>> /*
>> * vector callback is needed otherwise we cannot receive interrupts
>> * on cpu > 0 and at this point we don't know how many cpus are
>> * available.
>> */
>> if (!xen_have_vector_callback)
>> - return;
>> + goto exit;
>
>
> Why not just return? Do we expect the value of xen_have_vector_callback to change?
I just want to keep above sync with ....
>
>
> -boris
>
>
>> if (!xen_feature(XENFEAT_hvm_safe_pvclock)) {
>> pr_info("Xen doesn't support pvclock on HVM, disable pv timer");
>> + goto exit;
>> + }
... here.
That is, I want the main logic of xen_hvm_init_time_ops() to run for at most
once. Both of above two if statements will "go to exit".
Thank you very much!
Dongli Zhang
>> +
>> + /*
>> + * Only MAX_VIRT_CPUS 'vcpu_info' are embedded inside 'shared_info'.
>> + * The __this_cpu_read(xen_vcpu) is still NULL when Xen HVM guest
>> + * boots on vcpu >= MAX_VIRT_CPUS (e.g., kexec), To access
>> + * __this_cpu_read(xen_vcpu) via xen_clocksource_read() will panic.
>> + *
>> + * The xen_hvm_init_time_ops() should be called again later after
>> + * __this_cpu_read(xen_vcpu) is available.
>> + */
>> + if (!__this_cpu_read(xen_vcpu)) {
>> + pr_info("Delay xen_init_time_common() as kernel is running on
>> vcpu=%d\n",
>> + xen_vcpu_nr(0));
>> return;
>> }
>> @@ -577,6 +597,9 @@ void __init xen_hvm_init_time_ops(void)
>> x86_cpuinit.setup_percpu_clockev = xen_hvm_setup_cpu_clockevents;
>> x86_platform.set_wallclock = xen_set_wallclock;
>> +
>> +exit:
>> + hvm_time_initialized = true;
>> }
>> #endif
>>
next prev parent reply other threads:[~2022-03-03 0:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 16:40 [PATCH v4 0/2] xen: fix HVM kexec kernel panic Dongli Zhang
2022-03-02 16:40 ` [PATCH v4 1/2] x86/xen/time: fix indentation issue Dongli Zhang
2022-03-02 16:40 ` [PATCH v4 2/2] xen: delay xen_hvm_init_time_ops() if kdump is boot on vcpu>=32 Dongli Zhang
2022-03-03 0:20 ` Boris Ostrovsky
2022-03-03 0:31 ` Dongli Zhang [this message]
2022-03-03 2:11 ` Boris Ostrovsky
2022-03-03 3:08 ` Dongli Zhang
2022-03-11 14:19 ` Boris Ostrovsky
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=0ac50fb6-0aca-e61a-1f38-8badbc8c967a@oracle.com \
--to=dongli.zhang@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=jgross@suse.com \
--cc=joe.jin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®