From: "Michael S. Tsirkin" <mst@redhat.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
Stefano Garzarella <sgarzare@redhat.com>,
Jason Wang <jasowang@redhat.com>,
virtualization <virtualization@lists.linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tools/virtio: Test virtual address range detection
Date: Sun, 20 Mar 2022 07:03:45 -0400 [thread overview]
Message-ID: <20220320070309-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <YhVvOsI0+xVAKHdr@casper.infradead.org>
On Tue, Feb 22, 2022 at 11:18:18PM +0000, Matthew Wilcox wrote:
> On Tue, Feb 22, 2022 at 07:58:33AM +0000, David Woodhouse wrote:
> > On Tue, 2022-02-22 at 01:31 -0500, Michael S. Tsirkin wrote:
> > > On Mon, Feb 21, 2022 at 05:18:48PM +0000, David Woodhouse wrote:
> > > >
> > > > [dwoodhou@i7 virtio]$ sudo ~/virtio_test
> > > > Detected virtual address range 0x1000-0x7ffffffff000
> > > > spurious wakeups: 0x0 started=0x100000 completed=0x100000
> > > >
> > > > Although in some circumstances I also see a different build failure:
> > > >
> > > > cc -g -O2 -Werror -Wno-maybe-uninitialized -Wall -I. -I../include/ -I ../../usr/include/ -Wno-pointer-sign -fno-strict-overflow -fno-strict-aliasing -fno-common -MMD -U_FORTIFY_SOURCE -include ../../include/linux/kconfig.h -c -o vringh_test.o vringh_test.c
>
> Trying to test this myself ...
>
> $ cd tools/virtio/
> $ make
> ...
> cc -lpthread virtio_test.o virtio_ring.o -o virtio_test
> /usr/bin/ld: virtio_ring.o: in function `spin_lock':
> /home/willy/kernel/folio/tools/virtio/./linux/spinlock.h:16: undefined reference to `pthread_spin_lock'
>
> So this is not the only problem here?
Could you let me know which system and gcc version have this problem, for inclusion
in the commit log?
> > > > In file included from ./linux/uio.h:3,
> > > > from ./linux/../../../include/linux/vringh.h:15,
> > > > from ./linux/vringh.h:1,
> > > > from vringh_test.c:9:
> > > > ./linux/../../../include/linux/uio.h:10:10: fatal error: linux/mm_types.h: No such file or directory
> > > > 10 | #include <linux/mm_types.h>
> > > > | ^~~~~~~~~~~~~~~~~~
> > > > compilation terminated.
> > > > make: *** [<builtin>: vringh_test.o] Error 1
> > >
> > > Which tree has this build failure? In mine linux/uio.h does not
> > > include linux/mm_types.h.
> >
> > Strictly it's
> > https://git.infradead.org/users/dwmw2/linux.git/shortlog/refs/heads/xen-evtchn-kernel
> > but I'm sure my part isn't relevant; it's just v5.17-rc5.
> >
> > $ git blame include/linux/uio.h | grep mm_types.h
> > d9c19d32d86fa (Matthew Wilcox (Oracle) 2021-10-18 10:39:06 -0400 10) #include <linux/mm_types.h>
> > $ git describe --tags d9c19d32d86fa
> > v5.16-rc4-37-gd9c19d32d86f
>
> grr. Originally, I had this doing a typebusting cast, but hch objected,
> so I had to include mm_types.h. This should fix it ...
>
> $ git diff
> diff --git a/tools/virtio/linux/mm_types.h b/tools/virtio/linux/mm_types.h
> new file mode 100644
> index 000000000000..3b0fc9bc5b8f
> --- /dev/null
> +++ b/tools/virtio/linux/mm_types.h
> @@ -0,0 +1,3 @@
> +struct folio {
> + struct page page;
> +};
>
> At least, it makes it compile for me.
next prev parent reply other threads:[~2022-03-20 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 16:15 [PATCH] tools/virtio: Test virtual address range detection David Woodhouse
2022-02-21 17:02 ` Stefano Garzarella
2022-02-21 17:18 ` David Woodhouse
2022-02-22 6:31 ` Michael S. Tsirkin
2022-02-22 7:58 ` David Woodhouse
2022-02-22 23:18 ` Matthew Wilcox
2022-02-25 15:48 ` Matthew Wilcox
2022-02-25 18:25 ` Michael S. Tsirkin
2022-03-16 14:41 ` Matthew Wilcox
2022-03-20 11:01 ` Michael S. Tsirkin
2022-03-20 11:03 ` Michael S. Tsirkin [this message]
2022-02-22 3:25 ` Jason Wang
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=20220320070309-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=dwmw2@infradead.org \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=willy@infradead.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