[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v4 2/2] xen: delay xen_hvm_init_time_ops() if kdump is boot on vcpu>=32


  • To: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, x86@xxxxxxxxxx
  • From: Dongli Zhang <dongli.zhang@xxxxxxxxxx>
  • Date: Wed, 2 Mar 2022 16:31:51 -0800
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=oracle.com; dmarc=pass action=none header.from=oracle.com; dkim=pass header.d=oracle.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=bneHbRqEhwaWmn2AAsUC2F8vjj3KwmMr1Ijt7yZsINQ=; b=NqVNdp1gaAotCL86aPA6a2uVfIU3V0G0T2dYVFTePGrFw4gpER+nGzOSNUE682V0pSMzpKYNioLOFX7o+0ASlJXK1MpxktARR968wQk7NMPViBaulUrPxlUflDJIncWueqI3XUL3DxCJy2AbU5ONC48P5weKOu9R/T1Myuh/Eu7fotzD8Iptu4nPXsXDdyChClntHonNmkhnO5K6q5mqYvEdEmtEstS+9ZVjzuZmrKx+CSjcby+2taslybxfoXttauqa5vBdUJi0sr+DPmd5Qg2B+3WjUBBfqsEucSCbvdsX0oXmf7ap5vxJqfTkMLO5moopBXwLSj1BILfZ3PZnmw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HLqG/wDT5iomSPucBdOhILRPILaKr5nrt2vLmSewKISyMXEWV7oBLTKs8F3OZCJ7HdOWzaWyay2JyzfRx8Ny4zneDM/SXKblhV6ZcsLNOJa9CRrGG+/1jww3DaiXk/PqEIO7QsJ7qmtBmtqyqup7EXf1wtcEmhdKBk9qjv20oNaM3u7yAzCQQ/gmIoBbPs22+7QV4Em/TTEtvAmBWvNqMdArocGZhPz8JIUUHEXcjMrBluFnbDnvxVcG9PpGMOQuC7ULTOT9HccutruKtBl16ynaLyPDnafSvpa0hNYdjknooAIxt02RhaZe8H/LZwA/E4hTun8yiBrl3ETbs64f/g==
  • Cc: linux-kernel@xxxxxxxxxxxxxxx, jgross@xxxxxxxx, sstabellini@xxxxxxxxxx, tglx@xxxxxxxxxxxxx, mingo@xxxxxxxxxx, bp@xxxxxxxxx, dave.hansen@xxxxxxxxxxxxxxx, joe.jin@xxxxxxxxxx
  • Delivery-date: Thu, 03 Mar 2022 00:33:34 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

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
>>   



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.