From: Jason Gunthorpe <jgg@nvidia.com>
To: Steve Sistare <steven.sistare@oracle.com>
Cc: iommu@lists.linux.dev, Kevin Tian <kevin.tian@intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: [PATCH V5 4/4] iommufd: IOMMU_IOAS_CHANGE_PROCESS selftest
Date: Thu, 14 Nov 2024 13:42:23 -0400 [thread overview]
Message-ID: <20241114174223.GT35230@nvidia.com> (raw)
In-Reply-To: <1731527497-16091-5-git-send-email-steven.sistare@oracle.com>
On Wed, Nov 13, 2024 at 11:51:37AM -0800, Steve Sistare wrote:
> Add selftest cases for IOMMU_IOAS_CHANGE_PROCESS.
>
> Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
> ---
> tools/testing/selftests/iommu/Makefile | 1 +
> tools/testing/selftests/iommu/iommufd.c | 141 ++++++++++++++++++++++++++
> tools/testing/selftests/iommu/iommufd_utils.h | 6 ++
> 3 files changed, 148 insertions(+)
>
> diff --git a/tools/testing/selftests/iommu/Makefile b/tools/testing/selftests/iommu/Makefile
> index fd64779..bd23ac9 100644
> --- a/tools/testing/selftests/iommu/Makefile
> +++ b/tools/testing/selftests/iommu/Makefile
> @@ -1,6 +1,7 @@
> # SPDX-License-Identifier: GPL-2.0-only
> CFLAGS += -Wall -O2 -Wno-unused-function
> CFLAGS += $(KHDR_INCLUDES)
> +CFLAGS += -lcap
This should be
LDLIBS += -lcap
Otherwise it doesn't compile:
iommufd.c:(.text+0xe54a): undefined reference to `cap_get_proc'
/usr/bin/ld: iommufd.c:(.text+0xe57a): undefined reference to `cap_set_flag'
/usr/bin/ld: iommufd.c:(.text+0xe596): undefined reference to `cap_set_proc'
/usr/bin/ld: iommufd.c:(.text+0xe5b5): undefined reference to `cap_free'
Because the -l option is in the wrong order
Jason
next prev parent reply other threads:[~2024-11-14 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 19:51 [PATCH V5 0/4] iommufd live update Steve Sistare
2024-11-13 19:51 ` [PATCH V5 1/4] iommufd: Export do_update_pinned Steve Sistare
2024-11-13 19:51 ` [PATCH V5 2/4] iommufd: Lock all IOAS objects Steve Sistare
2024-11-13 19:51 ` [PATCH V5 3/4] iommufd: Add IOMMU_IOAS_CHANGE_PROCESS Steve Sistare
2024-11-13 19:51 ` [PATCH V5 4/4] iommufd: IOMMU_IOAS_CHANGE_PROCESS selftest Steve Sistare
2024-11-14 17:42 ` Jason Gunthorpe [this message]
2024-11-14 18:01 ` Steven Sistare
2024-11-14 17:50 ` [PATCH V5 0/4] iommufd live update Jason Gunthorpe
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=20241114174223.GT35230@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=steven.sistare@oracle.com \
/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