Dataset Viewer
Auto-converted to Parquet Duplicate
source
large_stringclasses
2 values
subject
large_stringclasses
112 values
code
large_stringclasses
112 values
critique
large_stringlengths
61
3.04M
metadata
dict
lkml
[PATCH RFC v2 0/2] virtio-net: add flow filter for receive timestamps
This series tries to pick up the work on the virtio-net timestamping feature from Willem de Bruijn. Original series Message-Id: 20210208185558.995292-1-willemdebruijn.kernel@gmail.com Subject: [PATCH RFC v2 0/4] virtio-net: add tx-hash, rx-tstamp, tx-tstamp and tx-time From: Willem de Bruijn <willemb@g...
Demonstrate support for new virtio-net features VIRTIO_NET_HDR_F_TSTAMP This is not intended to be merged. A full feature test also requires a patched qemu binary that knows these features and negotiates correct vnet_hdr_sz in virtio_net_set_mrg_rx_bufs. See https://github.com/strumtrar/qemu/tree/v10.2.0/virtio-rx-s...
{ "author": "Steffen Trumtrar <s.trumtrar@pengutronix.de>", "date": "Thu, 29 Jan 2026 09:06:41 +0100", "thread_id": "20260129-v6-7-topic-virtio-net-ptp-v2-0-30a27dc52760@pengutronix.de.mbox.gz" }
lkml
[PATCH RFC v2 0/2] virtio-net: add flow filter for receive timestamps
This series tries to pick up the work on the virtio-net timestamping feature from Willem de Bruijn. Original series Message-Id: 20210208185558.995292-1-willemdebruijn.kernel@gmail.com Subject: [PATCH RFC v2 0/4] virtio-net: add tx-hash, rx-tstamp, tx-tstamp and tx-time From: Willem de Bruijn <willemb@g...
Add optional hardware rx timestamp offload for virtio-net. Introduce virtio feature VIRTIO_NET_F_TSTAMP. If negotiated, the virtio-net header is expanded with room for a timestamp. To get and set the hwtstamp the functions ndo_hwtstamp_set/get need to be implemented. This allows filtering the packets and only time st...
{ "author": "Steffen Trumtrar <s.trumtrar@pengutronix.de>", "date": "Thu, 29 Jan 2026 09:06:42 +0100", "thread_id": "20260129-v6-7-topic-virtio-net-ptp-v2-0-30a27dc52760@pengutronix.de.mbox.gz" }
lkml
[PATCH RFC v2 0/2] virtio-net: add flow filter for receive timestamps
This series tries to pick up the work on the virtio-net timestamping feature from Willem de Bruijn. Original series Message-Id: 20210208185558.995292-1-willemdebruijn.kernel@gmail.com Subject: [PATCH RFC v2 0/4] virtio-net: add tx-hash, rx-tstamp, tx-tstamp and tx-time From: Willem de Bruijn <willemb@g...
On Thu, 29 Jan 2026 09:06:42 +0100, Steffen Trumtrar <s.trumtrar@pengutronix.de> wrote: Since patch #1 used this struct, this one should be placed first in the series. Also, has the virtio specification process accepted such a draft proposal? Thanks
{ "author": "Xuan Zhuo <xuanzhuo@linux.alibaba.com>", "date": "Thu, 29 Jan 2026 17:48:25 +0800", "thread_id": "20260129-v6-7-topic-virtio-net-ptp-v2-0-30a27dc52760@pengutronix.de.mbox.gz" }
lkml
[PATCH RFC v2 0/2] virtio-net: add flow filter for receive timestamps
This series tries to pick up the work on the virtio-net timestamping feature from Willem de Bruijn. Original series Message-Id: 20210208185558.995292-1-willemdebruijn.kernel@gmail.com Subject: [PATCH RFC v2 0/4] virtio-net: add tx-hash, rx-tstamp, tx-tstamp and tx-time From: Willem de Bruijn <willemb@g...
Hi, On 2026-01-29 at 17:48 +08, Xuan Zhuo <xuanzhuo@linux.alibaba.com> wrote: oh, you are right, the order should be the other way around. I haven't sent the draft yet, because I'm unsure if I understood the way this should be implemented with the flow filter correctly. If the direction is correct, I'd try and get ...
{ "author": "Steffen Trumtrar <s.trumtrar@pengutronix.de>", "date": "Thu, 29 Jan 2026 11:08:27 +0100", "thread_id": "20260129-v6-7-topic-virtio-net-ptp-v2-0-30a27dc52760@pengutronix.de.mbox.gz" }
lkml
[PATCH RFC v2 0/2] virtio-net: add flow filter for receive timestamps
This series tries to pick up the work on the virtio-net timestamping feature from Willem de Bruijn. Original series Message-Id: 20210208185558.995292-1-willemdebruijn.kernel@gmail.com Subject: [PATCH RFC v2 0/4] virtio-net: add tx-hash, rx-tstamp, tx-tstamp and tx-time From: Willem de Bruijn <willemb@g...
On Thu, 29 Jan 2026 11:08:27 +0100, Steffen Trumtrar <s.trumtrar@pengutronix.de> wrote: There have been many historical attempts in this area- you may want to take a look first. Thanks.
{ "author": "Xuan Zhuo <xuanzhuo@linux.alibaba.com>", "date": "Thu, 29 Jan 2026 19:03:15 +0800", "thread_id": "20260129-v6-7-topic-virtio-net-ptp-v2-0-30a27dc52760@pengutronix.de.mbox.gz" }
lkml
[PATCH RFC v2 0/2] virtio-net: add flow filter for receive timestamps
This series tries to pick up the work on the virtio-net timestamping feature from Willem de Bruijn. Original series Message-Id: 20210208185558.995292-1-willemdebruijn.kernel@gmail.com Subject: [PATCH RFC v2 0/4] virtio-net: add tx-hash, rx-tstamp, tx-tstamp and tx-time From: Willem de Bruijn <willemb@g...
syzbot ci has tested the following series [v2] virtio-net: add flow filter for receive timestamps https://lore.kernel.org/all/20260129-v6-7-topic-virtio-net-ptp-v2-0-30a27dc52760@pengutronix.de * [PATCH RFC v2 1/2] tun: support rx-tstamp * [PATCH RFC v2 2/2] virtio-net: support receive timestamp and found the followi...
{ "author": "syzbot ci <syzbot+ci99a227ab2089b0fa@syzkaller.appspotmail.com>", "date": "Thu, 29 Jan 2026 05:27:03 -0800", "thread_id": "20260129-v6-7-topic-virtio-net-ptp-v2-0-30a27dc52760@pengutronix.de.mbox.gz" }
lkml
[PATCH RFC v2 0/2] virtio-net: add flow filter for receive timestamps
This series tries to pick up the work on the virtio-net timestamping feature from Willem de Bruijn. Original series Message-Id: 20210208185558.995292-1-willemdebruijn.kernel@gmail.com Subject: [PATCH RFC v2 0/4] virtio-net: add tx-hash, rx-tstamp, tx-tstamp and tx-time From: Willem de Bruijn <willemb@g...
Steffen Trumtrar wrote: Good to see this picked up. I would also still like to see support in virtio-net for HW timestamps pass-through for virtio-net.
{ "author": "Willem de Bruijn <willemdebruijn.kernel@gmail.com>", "date": "Sun, 01 Feb 2026 16:00:07 -0500", "thread_id": "20260129-v6-7-topic-virtio-net-ptp-v2-0-30a27dc52760@pengutronix.de.mbox.gz" }
lkml
[PATCH RFC v2 0/2] virtio-net: add flow filter for receive timestamps
This series tries to pick up the work on the virtio-net timestamping feature from Willem de Bruijn. Original series Message-Id: 20210208185558.995292-1-willemdebruijn.kernel@gmail.com Subject: [PATCH RFC v2 0/4] virtio-net: add tx-hash, rx-tstamp, tx-tstamp and tx-time From: Willem de Bruijn <willemb@g...
Steffen Trumtrar wrote: This patch refers to a struct that does not exist yet, so this cannot compile?
{ "author": "Willem de Bruijn <willemdebruijn.kernel@gmail.com>", "date": "Sun, 01 Feb 2026 16:00:49 -0500", "thread_id": "20260129-v6-7-topic-virtio-net-ptp-v2-0-30a27dc52760@pengutronix.de.mbox.gz" }
lkml
[PATCH RFC v2 0/2] virtio-net: add flow filter for receive timestamps
This series tries to pick up the work on the virtio-net timestamping feature from Willem de Bruijn. Original series Message-Id: 20210208185558.995292-1-willemdebruijn.kernel@gmail.com Subject: [PATCH RFC v2 0/4] virtio-net: add tx-hash, rx-tstamp, tx-tstamp and tx-time From: Willem de Bruijn <willemb@g...
Steffen Trumtrar wrote: Jason, Michael: creating a new struct for every field is not very elegant. Is it time to find a more forward looking approach to expanding with new fields? Like a TLV, or how netlink structs like tcp_info are extended with support for legacy users that only use a truncated struct? It's fine t...
{ "author": "Willem de Bruijn <willemdebruijn.kernel@gmail.com>", "date": "Sun, 01 Feb 2026 16:05:54 -0500", "thread_id": "20260129-v6-7-topic-virtio-net-ptp-v2-0-30a27dc52760@pengutronix.de.mbox.gz" }
lkml
[PATCH RFC v2 0/2] virtio-net: add flow filter for receive timestamps
This series tries to pick up the work on the virtio-net timestamping feature from Willem de Bruijn. Original series Message-Id: 20210208185558.995292-1-willemdebruijn.kernel@gmail.com Subject: [PATCH RFC v2 0/4] virtio-net: add tx-hash, rx-tstamp, tx-tstamp and tx-time From: Willem de Bruijn <willemb@g...
On 2026-02-01 at 16:05 -05, Willem de Bruijn <willemdebruijn.kernel@gmail.com> wrote: Yes, this gets complicated real fast and leads to really long calls for all the nested fields. If there is a different way, I'd prefer that. Should have added a comment, but this is based on this patch c3838262b824c71c145cd36...
{ "author": "Steffen Trumtrar <s.trumtrar@pengutronix.de>", "date": "Mon, 02 Feb 2026 08:34:58 +0100", "thread_id": "20260129-v6-7-topic-virtio-net-ptp-v2-0-30a27dc52760@pengutronix.de.mbox.gz" }
lkml
[PATCH RFC v2 0/2] virtio-net: add flow filter for receive timestamps
This series tries to pick up the work on the virtio-net timestamping feature from Willem de Bruijn. Original series Message-Id: 20210208185558.995292-1-willemdebruijn.kernel@gmail.com Subject: [PATCH RFC v2 0/4] virtio-net: add tx-hash, rx-tstamp, tx-tstamp and tx-time From: Willem de Bruijn <willemb@g...
On Sun, Feb 01, 2026 at 04:05:54PM -0500, Willem de Bruijn wrote: I certainly wouldn't mind, though I suspect tlv is too complex as hardware implementations can't efficiently follow linked lists. I'll try to ping some hardware designers for what works well for offloads.
{ "author": "\"Michael S. Tsirkin\" <mst@redhat.com>", "date": "Mon, 2 Feb 2026 02:59:31 -0500", "thread_id": "20260129-v6-7-topic-virtio-net-ptp-v2-0-30a27dc52760@pengutronix.de.mbox.gz" }
lkml
[PATCH RFC v2 0/2] virtio-net: add flow filter for receive timestamps
This series tries to pick up the work on the virtio-net timestamping feature from Willem de Bruijn. Original series Message-Id: 20210208185558.995292-1-willemdebruijn.kernel@gmail.com Subject: [PATCH RFC v2 0/4] virtio-net: add tx-hash, rx-tstamp, tx-tstamp and tx-time From: Willem de Bruijn <willemb@g...
Michael S. Tsirkin wrote: Great thanks. Agreed that TLV was probably the wrong suggestion. We can definitely have a required order of fields. My initial thought is as said like many user/kernel structures: where both sides agree on the basic order of the struct, and pass along the length, so that they agree only to...
{ "author": "Willem de Bruijn <willemdebruijn.kernel@gmail.com>", "date": "Mon, 02 Feb 2026 12:40:36 -0500", "thread_id": "20260129-v6-7-topic-virtio-net-ptp-v2-0-30a27dc52760@pengutronix.de.mbox.gz" }
lkml
[PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support
This series introduces Synchronous Ethernet (SyncE) support for the Intel E825-C Ethernet controller. Unlike previous generations where DPLL connections were implicitly assumed, the E825-C architecture relies on the platform firmware (ACPI) to describe the physical connections between the Ethernet controller and extern...
Extend the DPLL core to support associating a DPLL pin with a firmware node. This association is required to allow other subsystems (such as network drivers) to locate and request specific DPLL pins defined in the Device Tree or ACPI. * Add a .fwnode field to the struct dpll_pin * Introduce dpll_pin_fwnode_set() helpe...
{ "author": "Ivan Vecera <ivecera@redhat.com>", "date": "Mon, 2 Feb 2026 18:16:30 +0100", "thread_id": "20260202171638.17427-6-ivecera@redhat.com.mbox.gz" }
lkml
[PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support
This series introduces Synchronous Ethernet (SyncE) support for the Intel E825-C Ethernet controller. Unlike previous generations where DPLL connections were implicitly assumed, the E825-C architecture relies on the platform firmware (ACPI) to describe the physical connections between the Ethernet controller and extern...
Associate the registered DPLL pin with its firmware node by calling dpll_pin_fwnode_set(). This links the created pin object to its corresponding DT/ACPI node in the DPLL core. Consequently, this enables consumer drivers (such as network drivers) to locate and request this specific pin using the fwnode_dpll_pin_find()...
{ "author": "Ivan Vecera <ivecera@redhat.com>", "date": "Mon, 2 Feb 2026 18:16:31 +0100", "thread_id": "20260202171638.17427-6-ivecera@redhat.com.mbox.gz" }
lkml
[PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support
This series introduces Synchronous Ethernet (SyncE) support for the Intel E825-C Ethernet controller. Unlike previous generations where DPLL connections were implicitly assumed, the E825-C architecture relies on the platform firmware (ACPI) to describe the physical connections between the Ethernet controller and extern...
From: Petr Oros <poros@redhat.com> Currently, the DPLL subsystem reports events (creation, deletion, changes) to userspace via Netlink. However, there is no mechanism for other kernel components to be notified of these events directly. Add a raw notifier chain to the DPLL core protected by dpll_lock. This allows othe...
{ "author": "Ivan Vecera <ivecera@redhat.com>", "date": "Mon, 2 Feb 2026 18:16:32 +0100", "thread_id": "20260202171638.17427-6-ivecera@redhat.com.mbox.gz" }
lkml
[PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support
This series introduces Synchronous Ethernet (SyncE) support for the Intel E825-C Ethernet controller. Unlike previous generations where DPLL connections were implicitly assumed, the E825-C architecture relies on the platform firmware (ACPI) to describe the physical connections between the Ethernet controller and extern...
Allow drivers to register DPLL pins without manually specifying a pin index. Currently, drivers must provide a unique pin index when calling dpll_pin_get(). This works well for hardware-mapped pins but creates friction for drivers handling virtual pins or those without a strict hardware indexing scheme. Introduce DPL...
{ "author": "Ivan Vecera <ivecera@redhat.com>", "date": "Mon, 2 Feb 2026 18:16:33 +0100", "thread_id": "20260202171638.17427-6-ivecera@redhat.com.mbox.gz" }
lkml
[PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support
This series introduces Synchronous Ethernet (SyncE) support for the Intel E825-C Ethernet controller. Unlike previous generations where DPLL connections were implicitly assumed, the E825-C architecture relies on the platform firmware (ACPI) to describe the physical connections between the Ethernet controller and extern...
Add parsing for the "mux" string in the 'connection-type' pin property mapping it to DPLL_PIN_TYPE_MUX. Recognizing this type in the driver allows these pins to be taken as parent pins for pin-on-pin pins coming from different modules (e.g. network drivers). Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel...
{ "author": "Ivan Vecera <ivecera@redhat.com>", "date": "Mon, 2 Feb 2026 18:16:34 +0100", "thread_id": "20260202171638.17427-6-ivecera@redhat.com.mbox.gz" }
lkml
[PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support
This series introduces Synchronous Ethernet (SyncE) support for the Intel E825-C Ethernet controller. Unlike previous generations where DPLL connections were implicitly assumed, the E825-C architecture relies on the platform firmware (ACPI) to describe the physical connections between the Ethernet controller and extern...
Refactor the reference counting mechanism for DPLL devices and pins to improve consistency and prevent potential lifetime issues. Introduce internal helpers __dpll_{device,pin}_{hold,put}() to centralize reference management. Update the internal XArray reference helpers (dpll_xa_ref_*) to automatically grab a referen...
{ "author": "Ivan Vecera <ivecera@redhat.com>", "date": "Mon, 2 Feb 2026 18:16:35 +0100", "thread_id": "20260202171638.17427-6-ivecera@redhat.com.mbox.gz" }
lkml
[PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support
This series introduces Synchronous Ethernet (SyncE) support for the Intel E825-C Ethernet controller. Unlike previous generations where DPLL connections were implicitly assumed, the E825-C architecture relies on the platform firmware (ACPI) to describe the physical connections between the Ethernet controller and extern...
Add support for the REF_TRACKER infrastructure to the DPLL subsystem. When enabled, this allows developers to track and debug reference counting leaks or imbalances for dpll_device and dpll_pin objects. It records stack traces for every get/put operation and exposes this information via debugfs at: /sys/kernel/debug...
{ "author": "Ivan Vecera <ivecera@redhat.com>", "date": "Mon, 2 Feb 2026 18:16:36 +0100", "thread_id": "20260202171638.17427-6-ivecera@redhat.com.mbox.gz" }
lkml
[PATCH net-next v4 0/9] dpll: Core improvements and ice E825-C SyncE support
This series introduces Synchronous Ethernet (SyncE) support for the Intel E825-C Ethernet controller. Unlike previous generations where DPLL connections were implicitly assumed, the E825-C architecture relies on the platform firmware (ACPI) to describe the physical connections between the Ethernet controller and extern...
Update existing DPLL drivers to utilize the DPLL reference count tracking infrastructure. Add dpll_tracker fields to the drivers' internal device and pin structures. Pass pointers to these trackers when calling dpll_device_get/put() and dpll_pin_get/put(). This allows developers to inspect the specific references hel...
{ "author": "Ivan Vecera <ivecera@redhat.com>", "date": "Mon, 2 Feb 2026 18:16:37 +0100", "thread_id": "20260202171638.17427-6-ivecera@redhat.com.mbox.gz" }
End of preview. Expand in Data Studio

KernelLLM-1 Dataset

A high-quality raw dataset for training and fine-tuning LLMs on Operating System Development.

Overview

This dataset combines raw source code from a variety of mature and hobbyist operating system kernels with thousands of expert-level technical discussions and critiques from the Linux Kernel Mailing List.

The source code included in this dataset represents the latest stable versions of the respective repositories as of February 2nd 2026.

Dataset Structure

The dataset is provided in Parquet format for optimal compression and integration with the datasets library.

1. kernelllm_source.parquet (~1 GB)

Cleaned & Deduplicated Source Code (~970M Tokens).

  • Files: 180,129
  • Size: ~1 GB (Parquet), ~3.4 GB (Raw Text)
  • Sources: Linux, FreeBSD, OpenBSD, NetBSD, Illumos, ReactOS, seL4, ToaruOS, Redox OS, SerenityOS and DragonFlyBSD.
  • Cleaning:
    • Removed common license headers (GPL, BSD, MIT, etc) to prioritize logic.
    • Exact and "smart" deduplication (normalized whitespace) across repositories.
    • Excluded files < 100 characters to remove boilerplate headers.

Repository Distribution:

Repository File Count
Linux 62,969
FreeBSD 43,956
Illumos 23,411
BSD-Mixed (Open/Net) 22,949
DragonFlyBSD 17,662
SerenityOS 7,307
Redox OS 701
ToaruOS 609
seL4 565

2. kernelllm_critiques.parquet (~3.6 MB) (Tiny bit of the LKML)

LKML Critique Pairs (3,135 pairs).

  • Sources: lore.kernel.org archives.
  • Content: Pairs code snippets (patches) with substantive replies, critiques and NACKs from senior maintainers.
  • Schema:
{
  "source": "lkml",
  "subject": "[PATCH] ...",
  "code": "(The patch content)",
  "critique": "(The maintainer feedback)",
  "metadata": {
    "author": "...",
    "date": "...",
    "thread_id": "..."
  }
}

Dataset Release Strategy

This is the Raw version of the dataset. It is intended for:

  1. Intermediate Training: Pre-training on high-quality systems code.
  2. Fine-Tuning: Instruction-tuning models to act as "Kernel Maintainers". (Or just make them better at Kernel code.)
  3. Research: Analyzing developer communication patterns in low-level systems.

Licensing and Usage

This dataset is a collection of publicly available open-source code and mailing list archives. It contains content governed by multiple licenses. For full details, see the LICENSE file.

  • GNU General Public License (GPL) v2/v3 (e.g., Linux, ReactOS)
  • BSD 2-Clause / 3-Clause (e.g., FreeBSD, OpenBSD, NetBSD)
  • MIT License (e.g. SerenityOS, ToaruOS)
  • Apache License 2.0 (e.g., seL4)

Disclaimer

  1. Original Licenses Apply: The individual source code files and mailing list archives contained in this dataset remain governed by their original respective licenses.
  2. Attribution: The metadata field for each entry in the dataset includes repository and author information to facilitate attribution.
  3. Research & Ethics: This dataset is provided primarily for research and educational purposes in the field of LLM training and systems programming analysis.
  4. License Compliance: Users of this dataset are responsible for ensuring that their use of the data complies with all applicable licenses.w

Opt-out

If you are a maintainer of one of the included repositories and would like your data removed from future versions of this dataset, please open an issue on the Hugging Face dataset page.

Downloads last month
18

Collection including frisk2137/KernelLLM-1