From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, david.marchand@redhat.com,
stephen@networkplumber.org,
Anatoly Burakov <anatoly.burakov@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>
Subject: [kmods PATCH v3] linux/igb_uio: add build instructions
Date: Sun, 5 Feb 2023 19:23:56 +0100 [thread overview]
Message-ID: <20230205182356.600251-1-thomas@monjalon.net> (raw)
In-Reply-To: <1714118.VLH7GnMWUR@thomas>
From: Anatoly Burakov <anatoly.burakov@intel.com>
Currently, compilation instructions for igb_uio are missing.
Add them, as well as referring users to per-OS subdirectories.
Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
v3: improvements suggested one year ago
No need to wait one more year, this patch is directly applied.
---
README | 3 +++
linux/README.rst | 58 ++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 61 insertions(+)
create mode 100644 linux/README.rst
diff --git a/README b/README
index e71dbba..c514cf0 100644
--- a/README
+++ b/README
@@ -8,3 +8,6 @@ Now the preference is to contribute kernel modules to the upstream project
if possible, otherwise to host kernel code in dpdk-kmods.git.
The license can be BSD-3-Clause or GPL-2.0.
+
+For specific instructions per OS,
+please refer to the README file in the respective sub-directory.
diff --git a/linux/README.rst b/linux/README.rst
new file mode 100644
index 0000000..6c60a3d
--- /dev/null
+++ b/linux/README.rst
@@ -0,0 +1,58 @@
+Building Out-of-Tree Kernel Drivers for Linux
+=============================================
+
+Prerequisites
+-------------
+
+The system must have relevant Linux kernel headers or source code installed.
+
+
+Build
+-----
+
+To build ``igb_uio`` driver, simply run ``make`` command
+inside the ``igb_uio`` directory:
+
+.. code-block:: console
+
+ cd igb_uio
+ make
+
+If compiling against a specific kernel source directory is required,
+it is possible to specify the kernel source directory
+using the ``KSRC`` variable:
+
+.. code-block:: console
+
+ make KSRC=/path/to/custom/kernel/source
+
+
+Load
+----
+
+.. note::
+
+ These commands are to be run as ``root`` user.
+
+The ``igb_uio`` driver requires the UIO driver to be loaded beforehand.
+If ``uio`` is not built-in:
+
+.. code-block:: console
+
+ modprobe uio
+
+Then the out-of-tree driver may be loaded.
+
+.. code-block:: console
+
+ insmod igb_uio.ko
+
+
+Clean
+-----
+
+To clean the build directory, the following command can be run:
+
+.. code-block:: console
+
+ make clean
--
2.39.1
prev parent reply other threads:[~2023-02-05 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 16:54 [dpdk-dev] [PATCH DPDK-KMODS] igb_uio: add compile instructions Anatoly Burakov
2020-11-23 17:08 ` Ferruh Yigit
2020-11-24 13:26 ` [dpdk-dev] [PATCH DPDK-KMODS v2] linux/igb_uio: " Anatoly Burakov
2020-11-24 14:27 ` Ajit Khaparde
2021-02-11 11:04 ` Burakov, Anatoly
2021-02-15 11:40 ` Thomas Monjalon
2021-02-15 12:00 ` Burakov, Anatoly
2022-01-11 13:35 ` Thomas Monjalon
2023-02-05 18:23 ` Thomas Monjalon [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=20230205182356.600251-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=ajit.khaparde@broadcom.com \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).