From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Zhenzhong Duan <zhenzhong.duan@oracle.com>, linux-kernel@vger.kernel.org
Cc: xen-devel@lists.xenproject.org, jgross@suse.com,
sstabellini@kernel.org, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de
Subject: Re: [PATCH v6 4/4] x86/xen: Add "nopv" support for HVM guest
Date: Tue, 9 Jul 2019 10:54:32 -0400 [thread overview]
Message-ID: <3d7db7c6-cea3-9dce-0519-a1c600b33273@oracle.com> (raw)
In-Reply-To: <6cbd7b78-3d8d-64ae-fd2e-82244dbe6a1e@oracle.com>
On 7/9/19 12:20 AM, Zhenzhong Duan wrote:
>
> -const __initconst struct hypervisor_x86 x86_hyper_xen_hvm = {
> +static uint32_t __init xen_platform_hvm(void)
> +{
> + uint32_t xen_domain = xen_cpuid_base();
> + struct x86_hyper_init *h = &x86_hyper_xen_hvm.init;
> +
> + if (xen_pv_domain())
> + return 0;
> +
> + if (xen_pvh_domain() && nopv) {
> + /* Guest booting via the Xen-PVH boot entry goes here */
> + pr_info("\"nopv\" parameter is ignored in PVH guest\n");
> + nopv = false;
> + } else if (nopv && xen_domain) {
> + /*
> + * Guest booting via normal boot entry (like via
> grub2) goes
> + * here.
> + *
> + * Use interface functions for bare hardware if nopv,
> + * xen_hvm_guest_late_init is an exception as we need to
> + * detect PVH and panic there.
> + */
> + memcpy(h, (void *)&x86_init.hyper,
> sizeof(x86_init.hyper));
And this worked? I'd think it would fail since h points to RO section.
> + memcpy(&x86_hyper_xen_hvm.runtime, (void
> *)&x86_platform.hyper,
> + sizeof(x86_platform.hyper));
> + h->guest_late_init = xen_hvm_guest_late_init;
To me this still doesn't look right --- you are making assumptions about
x86_platform/x86_init.hyper and I don't think you can assume they have
not been set to point to another hypervisor, for example.
Would modifying all x86_hyper_xen_hvm's ops (except, I guess,
xen_hvm_guest_late_init()) to immediately return if nopv is set work?
Also question for Juergen --- is there anything perhaps in zeropage that
indicates we are booting PVH guest from grub?
-boris
> + }
> + return xen_domain;
> +}
> +
> +struct hypervisor_x86 x86_hyper_xen_hvm __initdata = {
> .name = "Xen HVM",
> .detect = xen_platform_hvm,
> .type = X86_HYPER_XEN_HVM,
> @@ -268,4 +292,5 @@ static __init void xen_hvm_guest_late_init(void)
> .init.init_mem_mapping = xen_hvm_init_mem_mapping,
> .init.guest_late_init = xen_hvm_guest_late_init,
> .runtime.pin_vcpu = xen_pin_vcpu,
> + .ignore_nopv = true,
> };
>
>
> Thanks
>
> Zhenzhong
>
next prev parent reply other threads:[~2019-07-09 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-07 9:15 [PATCH v6 0/4] misc fixes to PV extensions code Zhenzhong Duan
2019-07-07 9:15 ` [PATCH v6 1/4] x86/xen: Mark xen_hvm_need_lapic() and xen_x2apic_para_available() as __init Zhenzhong Duan
2019-07-07 9:15 ` [PATCH v6 2/4] x86: Add "nopv" parameter to disable PV extensions Zhenzhong Duan
2019-07-07 9:15 ` [PATCH v6 3/4] xen: Map "xen_nopv" parameter to "nopv" and mark it obsolete Zhenzhong Duan
2019-07-07 9:15 ` [PATCH v6 4/4] x86/xen: Add "nopv" support for HVM guest Zhenzhong Duan
2019-07-08 13:46 ` Boris Ostrovsky
2019-07-09 4:20 ` Zhenzhong Duan
2019-07-09 14:54 ` Boris Ostrovsky [this message]
2019-07-10 2:07 ` Zhenzhong Duan
2019-07-10 13:21 ` 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=3d7db7c6-cea3-9dce-0519-a1c600b33273@oracle.com \
--to=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 \
--cc=zhenzhong.duan@oracle.com \
/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®