From: Jake Freeland <jfree@FreeBSD.org>
To: Chenbo Xia <chenbox@nvidia.com>,
Nipun Gupta <nipun.gupta@amd.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: Jake Freeland <jfree@FreeBSD.org>, dev@dpdk.org
Subject: [PATCH 0/4] BSD PCI Fixes
Date: Tue, 6 May 2025 12:40:40 -0500 [thread overview]
Message-ID: <20250506174046.1136711-1-jfree@FreeBSD.org> (raw)
Hi there,
The following patchset includes a number of fixes I've made over the
past year relating to the PCI driver. Most of these changes target
the FreeBSD platform.
Let me know if you have any feedback. Thanks.
Jake Freeland (4):
bus/pci: Use force-noreplace flag when mapping PCI resources
bus/pci/bsd: Map resources at EAL baseaddr
bus/pci/bsd: Eliminate potential overflow
bus/pci/bsd: Fix device existence check
drivers/bus/pci/bsd/pci.c | 32 ++++++++++++++++++++++++--------
drivers/bus/pci/pci_common_uio.c | 4 +++-
lib/eal/common/eal_private.h | 7 ++++++-
lib/eal/include/rte_eal_paging.h | 7 ++++++-
lib/eal/unix/eal_unix_memory.c | 8 +++++++-
5 files changed, 46 insertions(+), 12 deletions(-)
--
2.47.2
next reply other threads:[~2025-05-06 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 17:40 Jake Freeland [this message]
2025-05-06 17:40 ` [PATCH 1/4] bus/pci: Use force-noreplace flag when mapping PCI resources Jake Freeland
2025-05-08 11:32 ` Burakov, Anatoly
2025-05-06 17:40 ` [PATCH 2/4] bus/pci/bsd: Map resources at EAL baseaddr Jake Freeland
2025-05-08 11:31 ` Burakov, Anatoly
2025-05-06 17:40 ` [PATCH 3/4] bus/pci/bsd: Eliminate potential overflow Jake Freeland
2025-05-08 11:28 ` Burakov, Anatoly
2025-05-06 17:40 ` [PATCH 4/4] bus/pci/bsd: Fix device existence check Jake Freeland
2025-05-08 11:27 ` Burakov, Anatoly
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=20250506174046.1136711-1-jfree@FreeBSD.org \
--to=jfree@freebsd.org \
--cc=bruce.richardson@intel.com \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=nipun.gupta@amd.com \
--cc=roretzla@linux.microsoft.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;
as well as URLs for NNTP newsgroup(s).