[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <969cacf1-d420-223d-7cc7-5b1b2405ec2a@infradead.org>
Date: Tue, 31 Mar 2020 11:27:54 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: akpm@...ux-foundation.org, broonie@...nel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-next@...r.kernel.org, mhocko@...e.cz,
mm-commits@...r.kernel.org, sfr@...b.auug.org.au,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
virtualization@...ts.linux-foundation.org,
"Michael S. Tsirkin" <mst@...hat.com>,
Jason Wang <jasowang@...hat.com>
Subject: Re: mmotm 2020-03-30-18-46 uploaded (VDPA + vhost)
On 3/30/20 6:47 PM, akpm@...ux-foundation.org wrote:
> The mm-of-the-moment snapshot 2020-03-30-18-46 has been uploaded to
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> mmotm-readme.txt says
>
> README for mm-of-the-moment:
>
> http://www.ozlabs.org/~akpm/mmotm/
>
> This is a snapshot of my -mm patch queue. Uploaded at random hopefully
> more than once a week.
>
> You will need quilt to apply these patches to the latest Linus release (5.x
> or 5.x-rcY). The series file is in broken-out.tar.gz and is duplicated in
> http://ozlabs.org/~akpm/mmotm/series
>
> The file broken-out.tar.gz contains two datestamp files: .DATE and
> .DATE-yyyy-mm-dd-hh-mm-ss. Both contain the string yyyy-mm-dd-hh-mm-ss,
> followed by the base kernel version against which this patch series is to
> be applied.
>
> This tree is partially included in linux-next. To see which patches are
> included in linux-next, consult the `series' file. Only the patches
> within the #NEXT_PATCHES_START/#NEXT_PATCHES_END markers are included in
> linux-next.
>
>
> A full copy of the full kernel tree with the linux-next and mmotm patches
> already applied is available through git within an hour of the mmotm
> release. Individual mmotm releases are tagged. The master branch always
> points to the latest release, so it's constantly rebasing.
>
> https://github.com/hnaz/linux-mm
on i386:
ld: drivers/vhost/vdpa.o: in function `vhost_vdpa_init':
vdpa.c:(.init.text+0x52): undefined reference to `__vdpa_register_driver'
ld: drivers/vhost/vdpa.o: in function `vhost_vdpa_exit':
vdpa.c:(.exit.text+0x14): undefined reference to `vdpa_unregister_driver'
drivers/virtio/vdpa/ is not being built. (confusing!)
CONFIG_VIRTIO=m
# CONFIG_VIRTIO_MENU is not set
CONFIG_VDPA=y
CONFIG_VDPA_MENU=y
# CONFIG_VDPA_SIM is not set
CONFIG_VHOST_IOTLB=y
CONFIG_VHOST_RING=m
CONFIG_VHOST=y
CONFIG_VHOST_SCSI=m
CONFIG_VHOST_VDPA=y
Full randconfig file is attached.
(This same build failure happens with today's linux-next, Mar. 31.)
@Yamada-san: Is this a kbuild problem (or feature)?
--
~Randy
Reported-by: Randy Dunlap <rdunlap@...radead.org>
View attachment "config-r1735" of type "text/plain" (116814 bytes)
Powered by blists - more mailing lists