From: "Michael S. Tsirkin" <mst@redhat.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
qemu-devel@nongnu.org, David Hildenbrand <david@redhat.com>,
David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: [PATCH] i386/pc: Drop pc_machine_kvm_type()
Date: Wed, 18 Oct 2023 09:27:37 -0400 [thread overview]
Message-ID: <20231018092715-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20231007065819.27498-1-xiaoyao.li@intel.com>
On Sat, Oct 07, 2023 at 02:58:19AM -0400, Xiaoyao Li wrote:
> pc_machine_kvm_type() was introduced by commit e21be724eaf5 ("i386/xen:
> add pc_machine_kvm_type to initialize XEN_EMULATE mode") to do Xen
> specific initialization by utilizing kvm_type method.
>
> commit eeedfe6c6316 ("hw/xen: Simplify emulated Xen platform init")
> moves the Xen specific initialization to pc_basic_device_init().
>
> There is no need to keep the PC specific kvm_type() implementation
> anymore. So we'll fallback to kvm_arch_get_default_type(), which
> simply returns 0.
>
> Signed-off-by: Xiaoyao Li <xiaoyao.li@intel.com>
> Reviewed-by: Isaku Yamahata <isaku.yamahata@intel.com>
> Reviewed-by: David Hildenbrand <david@redhat.com>
> Acked-by: David Woodhouse <dwmw@amazon.co.uk>
Seems ok
Acked-by: Michael S. Tsirkin <mst@redhat.com>
kvm thing so please merge through that tree.
> ---
> hw/i386/pc.c | 5 -----
> include/hw/i386/pc.h | 3 ---
> 2 files changed, 8 deletions(-)
>
> diff --git a/hw/i386/pc.c b/hw/i386/pc.c
> index aad7e8ccd1d7..41783b137b9a 100644
> --- a/hw/i386/pc.c
> +++ b/hw/i386/pc.c
> @@ -1730,11 +1730,6 @@ static void pc_machine_initfn(Object *obj)
> cxl_machine_init(obj, &pcms->cxl_devices_state);
> }
>
> -int pc_machine_kvm_type(MachineState *machine, const char *kvm_type)
> -{
> - return 0;
> -}
> -
> static void pc_machine_reset(MachineState *machine, ShutdownCause reason)
> {
> CPUState *cs;
> diff --git a/include/hw/i386/pc.h b/include/hw/i386/pc.h
> index bec38cb92cf7..ad7149cb10b5 100644
> --- a/include/hw/i386/pc.h
> +++ b/include/hw/i386/pc.h
> @@ -305,15 +305,12 @@ extern const size_t pc_compat_1_5_len;
> extern GlobalProperty pc_compat_1_4[];
> extern const size_t pc_compat_1_4_len;
>
> -int pc_machine_kvm_type(MachineState *machine, const char *vm_type);
> -
> #define DEFINE_PC_MACHINE(suffix, namestr, initfn, optsfn) \
> static void pc_machine_##suffix##_class_init(ObjectClass *oc, void *data) \
> { \
> MachineClass *mc = MACHINE_CLASS(oc); \
> optsfn(mc); \
> mc->init = initfn; \
> - mc->kvm_type = pc_machine_kvm_type; \
> } \
> static const TypeInfo pc_machine_type_##suffix = { \
> .name = namestr TYPE_MACHINE_SUFFIX, \
>
> base-commit: 2f3913f4b2ad74baeb5a6f1d36efbd9ecdf1057d
> --
> 2.34.1
next prev parent reply other threads:[~2023-10-18 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-07 6:58 [PATCH] i386/pc: Drop pc_machine_kvm_type() Xiaoyao Li
2023-10-18 13:27 ` Michael S. Tsirkin [this message]
2023-10-19 1:54 ` Xiaoyao Li
2024-01-25 2:21 ` Xiaoyao Li
2024-01-25 10:35 ` Paolo Bonzini
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=20231018092715-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=david@redhat.com \
--cc=dwmw@amazon.co.uk \
--cc=eduardo@habkost.net \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=xiaoyao.li@intel.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;
as well as URLs for NNTP newsgroup(s).