From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Cc: Anthony PERARD <anthony@xenproject.org>,
Paul Durrant <paul@xen.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 6/7] hw/xen: register legacy backends via xen_backend_init
Date: Fri, 10 May 2024 12:52:42 +0200 [thread overview]
Message-ID: <84c89274-f8a9-4f86-84e9-40a962dc4f77@linaro.org> (raw)
In-Reply-To: <20240510104908.76908-7-philmd@linaro.org>
On 10/5/24 12:49, Philippe Mathieu-Daudé wrote:
> From: Paolo Bonzini <pbonzini@redhat.com>
>
> It is okay to register legacy backends in the middle of xen_bus_init().
> All that the registration does is record the existence of the backend
> in xenstore.
>
> This makes it possible to remove them from the build without introducing
> undefined symbols in xen_be_init(). It also removes the need for the
> backend_register callback, whose only purpose is to avoid registering
> nonfunctional backends.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> Message-ID: <20240509170044.190795-8-pbonzini@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> include/hw/xen/xen-legacy-backend.h | 11 ++---------
> include/hw/xen/xen_pvdev.h | 1 -
> hw/9pfs/xen-9p-backend.c | 8 +++++++-
> hw/display/xenfb.c | 8 +++++++-
> hw/usb/xen-usb.c | 14 ++++----------
> hw/xen/xen-legacy-backend.c | 16 ----------------
> 6 files changed, 20 insertions(+), 38 deletions(-)
next prev parent reply other threads:[~2024-05-10 10:52 UTC|newest]
Thread overview: 10+ 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-10 10:49 ` [PATCH v2 2/7] hw/xen: Constify XenLegacyDevice::XenDevOps Philippe Mathieu-Daudé
2024-05-10 10:49 ` [PATCH v2 3/7] hw/xen: Constify xenstore_be::XenDevOps Philippe Mathieu-Daudé
2024-05-10 10:49 ` [PATCH v2 4/7] hw/xen: Make XenDevOps structures const Philippe Mathieu-Daudé
2024-05-10 10:49 ` [PATCH v2 5/7] hw/xen: initialize legacy backends from xen_bus_init() Philippe Mathieu-Daudé
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é [this message]
2024-05-10 10:49 ` [PATCH v2 7/7] hw/xen: Register framebuffer backend via xen_backend_init() Philippe Mathieu-Daudé
2024-05-29 4:51 ` [PATCH v2 0/7] hw/xen: Simplify legacy backends handling 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=84c89274-f8a9-4f86-84e9-40a962dc4f77@linaro.org \
--to=philmd@linaro.org \
--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=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 read-only IMAP folder(s) and NNTP newsgroup(s).