From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org, "Greg Kurz" <groug@kaod.org>,
"Christian Schoenebeck" <qemu_oss@crudebyte.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Paul Durrant <paul@xen.org>,
Richard Henderson <richard.henderson@linaro.org>,
Anthony Perard <anthony.perard@citrix.com>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2 4/4] hw/xen: Have Xen machines select 9pfs
Date: Mon, 1 Feb 2021 11:23:11 +0100 [thread overview]
Message-ID: <50306fbf-c6f0-e281-248f-de1bc984b113@redhat.com> (raw)
In-Reply-To: <f6e1917a-f9cf-9ae3-50b1-9dc0ee4f65f3@amsat.org>
On 01/02/21 10:18, Philippe Mathieu-Daudé wrote:
> FYI using 'imply FSDEV_9P' instead I get:
>
> /usr/bin/ld: libcommon.fa.p/hw_xen_xen-legacy-backend.c.o: in function
> `xen_be_register_common':
> hw/xen/xen-legacy-backend.c:754: undefined reference to `xen_9pfs_ops'
Ok, so then we have the case of a file (hw/xen/xen-legacy-backend.c)
brought in by CONFIG_XEN. In that case this patch is incorrect...
> The function is:
>
> void xen_be_register_common(void)
> {
> xen_set_dynamic_sysbus();
>
> xen_be_register("console", &xen_console_ops);
> xen_be_register("vkbd", &xen_kbdmouse_ops);
> #ifdef CONFIG_VIRTFS
> xen_be_register("9pfs", &xen_9pfs_ops);
> #endif
> #ifdef CONFIG_USB_LIBUSB
> xen_be_register("qusb", &xen_usb_ops);
> #endif
> }
>
> The object is compiled using:
>
> -- >8 --
> -#ifdef CONFIG_VIRTFS
> +#ifdef CONFIG_FSDEV_9P
> xen_be_register("9pfs", &xen_9pfs_ops);
> #endif
> ---
... and this is the best fix, together with:
- a "#include CONFIG_DEVICES" at the top (to get CONFIG_FSDEV_9P)
- moving xen-legacy-backend.c from softmmu_ss to specific_ss (to get
CONFIG_DEVICES)
- changing "select" to "imply" in accel/Kconfig (otherwise the patch has
no effect)
But really, doing nothing and just dropping this patch is perfectly fine.
Paolo
next prev parent reply other threads:[~2021-02-01 10:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210131141810.293186-1-f4bug@amsat.org>
[not found] ` <20210131141810.293186-2-f4bug@amsat.org>
[not found] ` <6ea50cf0-344d-cf9b-0a20-0444b3764f2d@citrix.com>
2021-01-31 18:54 ` [PATCH v2 1/4] meson: Do not build Xen x86_64-softmmu on Aarch64 Philippe Mathieu-Daudé
[not found] ` <20210131141810.293186-5-f4bug@amsat.org>
2021-02-01 8:34 ` [PATCH v2 4/4] hw/xen: Have Xen machines select 9pfs Paolo Bonzini
2021-02-01 9:18 ` Philippe Mathieu-Daudé
2021-02-01 10:23 ` Paolo Bonzini [this message]
2021-02-01 11:03 ` Philippe Mathieu-Daudé
[not found] ` <20210131141810.293186-4-f4bug@amsat.org>
2021-02-01 10:59 ` [PATCH v2 3/4] hw/xen/Kconfig: Introduce XEN_PV config Philippe Mathieu-Daudé
2021-02-01 11:11 ` 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=50306fbf-c6f0-e281-248f-de1bc984b113@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=anthony.perard@citrix.com \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=groug@kaod.org \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--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).