From: "Richard W.M. Jones" <rjones@redhat.com>
To: Michael Young <m.a.young@durham.ac.uk>
Cc: qemu-devel@nongnu.org,
Stefano Stabellini <sstabellini@kernel.org>,
Anthony Perard <anthony.perard@citrix.com>,
Paul Durrant <paul@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] fix qemu build with xen-4.18.0
Date: Fri, 8 Dec 2023 10:00:23 +0000 [thread overview]
Message-ID: <20231208100023.GC23257@redhat.com> (raw)
In-Reply-To: <20231208084707.GA23257@redhat.com>
On Fri, Dec 08, 2023 at 08:47:07AM +0000, Richard W.M. Jones wrote:
> (Adding Xen maintainers)
>
> On Thu, Dec 07, 2023 at 11:12:48PM +0000, Michael Young wrote:
> > Builds of qemu-8.2.0rc2 with xen-4.18.0 are currently failing
> > with errors like
> > ../hw/arm/xen_arm.c:74:5: error: ‘GUEST_VIRTIO_MMIO_SPI_LAST’ undeclared (first use in this function)
> > 74 | (GUEST_VIRTIO_MMIO_SPI_LAST - GUEST_VIRTIO_MMIO_SPI_FIRST)
> > | ^~~~~~~~~~~~~~~~~~~~~~~~~~
> >
> > as there is an incorrect comparision in include/hw/xen/xen_native.h
> > which means that settings like GUEST_VIRTIO_MMIO_SPI_LAST
> > aren't being defined for xen-4.18.0
> >
> > Signed-off-by: Michael Young <m.a.young@durham.ac.uk>
>
> Reviewed-by: Richard W.M. Jones <rjones@redhat.com>
Actually, see Dan Berrange's answer in this thread.
Rich.
> > ---
> > include/hw/xen/xen_native.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/include/hw/xen/xen_native.h b/include/hw/xen/xen_native.h
> > index 6f09c48823..04b1ef4d34 100644
> > --- a/include/hw/xen/xen_native.h
> > +++ b/include/hw/xen/xen_native.h
> > @@ -532,7 +532,7 @@ static inline int xendevicemodel_set_irq_level(xendevicemodel_handle *dmod,
> > }
> > #endif
> >
> > -#if CONFIG_XEN_CTRL_INTERFACE_VERSION <= 41700
> > +#if CONFIG_XEN_CTRL_INTERFACE_VERSION >= 41700
> > #define GUEST_VIRTIO_MMIO_BASE xen_mk_ullong(0x02000000)
> > #define GUEST_VIRTIO_MMIO_SIZE xen_mk_ullong(0x00100000)
> > #define GUEST_VIRTIO_MMIO_SPI_FIRST 33
> > --
> > 2.43.0
> >
>
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> libguestfs lets you edit virtual machines. Supports shell scripting,
> bindings from many languages. http://libguestfs.org
>
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top
next prev parent reply other threads:[~2023-12-08 10:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 23:12 [PATCH] fix qemu build with xen-4.18.0 Michael Young
2023-12-08 8:47 ` Richard W.M. Jones
2023-12-08 9:59 ` Richard W.M. Jones
2023-12-08 10:00 ` Richard W.M. Jones [this message]
2023-12-08 9:25 ` Daniel P. Berrangé
2023-12-08 10:59 ` Peter Maydell
2023-12-08 11:34 ` Daniel P. Berrangé
2023-12-08 22:49 ` Stefano Stabellini
2023-12-12 14:19 ` Anthony PERARD
2023-12-12 14:36 ` Peter Maydell
2023-12-12 15:35 ` Volodymyr Babchuk
2023-12-12 15:47 ` Stefan Hajnoczi
2023-12-12 16:02 ` Volodymyr Babchuk
2023-12-12 16:29 ` Stefan Hajnoczi
2023-12-12 16:00 ` Anthony PERARD
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=20231208100023.GC23257@redhat.com \
--to=rjones@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=m.a.young@durham.ac.uk \
--cc=paul@xen.org \
--cc=qemu-devel@nongnu.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).