From: Jason Gunthorpe <jgg@ziepe.ca>
To: David Gow <davidgow@google.com>
Cc: Jeff Dike <jdike@addtoit.com>,
Richard Weinberger <richard@nod.at>,
Anton Ivanov <anton.ivanov@cambridgegreys.com>,
Shuah Khan <skhan@linuxfoundation.org>,
Brendan Higgins <brendanhiggins@google.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-um@lists.infradead.org, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, kunit-dev@googlegroups.com,
linux-kselftest@vger.kernel.org, linux-rdma@vger.kernel.org,
x86@kernel.org, felix.kuehling@amd.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] kunit: tool: Disable broken options for --alltests
Date: Fri, 18 Feb 2022 11:01:51 -0400 [thread overview]
Message-ID: <20220218150151.GD1037534@ziepe.ca> (raw)
In-Reply-To: <20220218075727.2737623-5-davidgow@google.com>
On Fri, Feb 18, 2022 at 03:57:27PM +0800, David Gow wrote:
> There are a number of Kconfig options which break compilation under UML with
> allyesconfig. As kunit_tool's --alltests option is based on allyesconfig and
> UML, we need to update the list of broken options to make --alltests build
> again.
>
> Note that, while this does build again, it still segfaults on startup,
> so more work remains to be done.
>
> They are:
> - CONFIG_VFIO_PCI: Needs ioport_map/ioport_unmap.
> - CONFIG_INFINIBAND_RDMAVT: Needs cpuinfo_x86 and __copy_user_nocache
It doesn't make sense to patch qib and then turn this option off, it
is required to build qib.
Jason
prev parent reply other threads:[~2022-02-18 15:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 7:57 [PATCH 0/4] kunit,um: Fix kunit.py build --alltests David Gow
2022-02-18 7:57 ` [PATCH 1/4] drm/amdgpu: Fix compilation under UML David Gow
2022-02-18 16:39 ` Felix Kuehling
2022-02-18 16:40 ` Alex Deucher
2022-02-19 8:00 ` David Gow
2022-02-18 7:57 ` [PATCH 2/4] drm/amdgpu: Make smu7_hwmgr build on UML David Gow
2022-02-18 7:57 ` [PATCH 3/4] IB/qib: Compile under User-Mode Linux David Gow
2022-02-18 7:57 ` [PATCH 4/4] kunit: tool: Disable broken options for --alltests David Gow
2022-02-18 12:26 ` Johannes Berg
2022-02-19 8:00 ` David Gow
2022-02-19 15:43 ` Johannes Berg
2022-02-18 15:01 ` Jason Gunthorpe [this message]
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=20220218150151.GD1037534@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=amd-gfx@lists.freedesktop.org \
--cc=anton.ivanov@cambridgegreys.com \
--cc=brendanhiggins@google.com \
--cc=davidgow@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=felix.kuehling@amd.com \
--cc=jdike@addtoit.com \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=rdunlap@infradead.org \
--cc=richard@nod.at \
--cc=skhan@linuxfoundation.org \
--cc=x86@kernel.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