From: Zhenzhong Duan <zhenzhong.duan@oracle.com>
To: Juergen Gross <jgross@suse.com>, linux-kernel@vger.kernel.org
Cc: bp@alien8.de, sstabellini@kernel.org, tglx@linutronix.de,
xen-devel@lists.xenproject.org, boris.ostrovsky@oracle.com,
mingo@redhat.com
Subject: Re: [PATCH v7 4/5] x86/paravirt: Remove const mark from x86_hyper_xen_hvm variable
Date: Wed, 17 Jul 2019 10:09:29 +0800 [thread overview]
Message-ID: <67261f6e-5dce-2452-a6d6-aa6ca73dfeec@oracle.com> (raw)
In-Reply-To: <2433589d-a2d2-6b51-cfbd-c1141014ab93@suse.com>
On 2019/7/16 18:57, Juergen Gross wrote:
> On 11.07.19 14:02, Zhenzhong Duan wrote:
>> .. as "nopv" support needs it to be changeable at boot up stage.
>>
>> Checkpatch report warning, so move variable declarations from
>> hypervisor.c to hypervisor.h
>>
>> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@oracle.com>
>> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
>> Cc: Juergen Gross <jgross@suse.com>
>> Cc: Stefano Stabellini <sstabellini@kernel.org>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Cc: Ingo Molnar <mingo@redhat.com>
>> Cc: Borislav Petkov <bp@alien8.de>
>> ---
>> arch/x86/include/asm/hypervisor.h | 8 ++++++++
>> arch/x86/kernel/cpu/hypervisor.c | 8 --------
>> 2 files changed, 8 insertions(+), 8 deletions(-)
>>
>> diff --git a/arch/x86/include/asm/hypervisor.h
>> b/arch/x86/include/asm/hypervisor.h
>> index f7b4c53..e41cbf2 100644
>> --- a/arch/x86/include/asm/hypervisor.h
>> +++ b/arch/x86/include/asm/hypervisor.h
>> @@ -58,6 +58,14 @@ struct hypervisor_x86 {
>> bool ignore_nopv;
>> };
>> +extern const struct hypervisor_x86 x86_hyper_vmware;
>> +extern const struct hypervisor_x86 x86_hyper_ms_hyperv;
>> +extern const struct hypervisor_x86 x86_hyper_xen_pv;
>> +extern const struct hypervisor_x86 x86_hyper_kvm;
>> +extern const struct hypervisor_x86 x86_hyper_jailhouse;
>> +extern const struct hypervisor_x86 x86_hyper_acrn;
>> +extern struct hypervisor_x86 x86_hyper_xen_hvm;
>
> This should either stay const and be changed in patch 5, or you
> should adapt its definition in arch/x86/xen/enlighten_hvm.c in
> this patch.
Ok, thanks for your suggestion.
I'll choose 2nd opinion as I don't need to change descripton with that.
Zhenzhong
next prev parent reply other threads:[~2019-07-17 2:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 12:02 [PATCH v7 0/5] misc fixes to PV extensions code Zhenzhong Duan
2019-07-11 12:02 ` [PATCH v7 1/5] x86/xen: Mark xen_hvm_need_lapic() and xen_x2apic_para_available() as __init Zhenzhong Duan
2019-07-11 12:02 ` [PATCH v7 2/5] x86: Add "nopv" parameter to disable PV extensions Zhenzhong Duan
2019-07-11 12:02 ` [PATCH v7 3/5] xen: Map "xen_nopv" parameter to "nopv" and mark it obsolete Zhenzhong Duan
2019-07-11 12:02 ` [PATCH v7 4/5] x86/paravirt: Remove const mark from x86_hyper_xen_hvm variable Zhenzhong Duan
2019-07-16 10:57 ` Juergen Gross
2019-07-17 2:09 ` Zhenzhong Duan [this message]
2019-07-17 3:34 ` Juergen Gross
2019-07-11 12:02 ` [PATCH v7 5/5] x86/xen: Add "nopv" support for HVM guest Zhenzhong Duan
2019-07-15 15:17 ` 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=67261f6e-5dce-2452-a6d6-aa6ca73dfeec@oracle.com \
--to=zhenzhong.duan@oracle.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sstabellini@kernel.org \
--cc=tglx@linutronix.de \
--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®