From: Paul Durrant <xadimgnik@gmail.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-devel@nongnu.org, "Paolo Bonzini" <pbonzini@redhat.com>
Cc: Anthony PERARD <anthony@xenproject.org>,
Richard Henderson <richard.henderson@linaro.org>,
xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Eduardo Habkost <eduardo@habkost.net>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [PATCH v2 5/7] hw/xen: initialize legacy backends from xen_bus_init()
Date: Fri, 31 May 2024 10:56:57 +0100 [thread overview]
Message-ID: <cd6fec85-c5da-4b89-9ceb-cb10ef4048e4@xen.org> (raw)
In-Reply-To: <20240510104908.76908-6-philmd@linaro.org>
On 10/05/2024 11:49, Philippe Mathieu-Daudé wrote:
> From: Paolo Bonzini <pbonzini@redhat.com>
>
> Prepare for moving the calls to xen_be_register() under the
> control of xen_bus_init(), using the normal xen_backend_init()
> method that is used by the "modern" backends.
>
> This requires the xenstore global variable to be initialized,
> which is done by xen_be_init(). To ensure that everything is
> ready at the time the xen_backend_init() functions are called,
> remove the xen_be_init() function from all the boards and
> place it directly in xen_bus_init().
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Message-ID: <20240509170044.190795-7-pbonzini@redhat.com>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> hw/i386/pc.c | 1 -
> hw/xen/xen-bus.c | 4 ++++
> hw/xen/xen-hvm-common.c | 2 --
> hw/xenpv/xen_machine_pv.c | 5 +----
> 4 files changed, 5 insertions(+), 7 deletions(-)
>
Reviewed-by: Paul Durrant <paul@xen.org>
next prev parent reply other threads:[~2024-05-31 9:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 10:49 [PATCH v2 0/7] hw/xen: Simplify legacy backends handling Philippe Mathieu-Daudé
2024-05-10 10:49 ` [PATCH v2 1/7] hw/xen: Remove declarations left over in 'xen-legacy-backend.h' Philippe Mathieu-Daudé
2024-05-31 9:08 ` Paul Durrant
2024-05-10 10:49 ` [PATCH v2 2/7] hw/xen: Constify XenLegacyDevice::XenDevOps Philippe Mathieu-Daudé
2024-05-31 9:09 ` Paul Durrant
2024-05-10 10:49 ` [PATCH v2 3/7] hw/xen: Constify xenstore_be::XenDevOps Philippe Mathieu-Daudé
2024-05-31 9:10 ` Paul Durrant
2024-05-10 10:49 ` [PATCH v2 4/7] hw/xen: Make XenDevOps structures const Philippe Mathieu-Daudé
2024-05-31 9:52 ` Paul Durrant
2024-05-10 10:49 ` [PATCH v2 5/7] hw/xen: initialize legacy backends from xen_bus_init() Philippe Mathieu-Daudé
2024-05-31 9:56 ` Paul Durrant [this message]
2024-05-10 10:49 ` [PATCH v2 6/7] hw/xen: register legacy backends via xen_backend_init Philippe Mathieu-Daudé
2024-05-10 10:52 ` Philippe Mathieu-Daudé
2024-05-31 9:57 ` Paul Durrant
2024-05-10 10:49 ` [PATCH v2 7/7] hw/xen: Register framebuffer backend via xen_backend_init() Philippe Mathieu-Daudé
2024-05-31 9:59 ` Paul Durrant
2024-05-29 4:51 ` [PATCH v2 0/7] hw/xen: Simplify legacy backends handling Philippe Mathieu-Daudé
2024-06-03 11:48 ` Philippe Mathieu-Daudé
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=cd6fec85-c5da-4b89-9ceb-cb10ef4048e4@xen.org \
--to=xadimgnik@gmail.com \
--cc=anthony@xenproject.org \
--cc=eduardo@habkost.net \
--cc=kraxel@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=sstabellini@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;
as well as URLs for NNTP newsgroup(s).