source large_stringclasses 2
values | subject large_stringclasses 112
values | code large_stringclasses 112
values | critique large_stringlengths 61 3.04M ⌀ | metadata dict |
|---|---|---|---|---|
lkml | [PATCHSET v12 sched_ext/for-6.20] Add a deadline server for sched_ext tasks | sched_ext tasks can be starved by long-running RT tasks, especially since
RT throttling was replaced by deadline servers to boost only SCHED_NORMAL
tasks.
Several users in the community have reported issues with RT stalling
sched_ext tasks. This is fairly common on distributions or environments
where applications like... | From: Joel Fernandes <joelagnelf@nvidia.com>
When a sched_ext server is loaded, tasks in the fair class are
automatically moved to the sched_ext class. Add support to modify the
ext server parameters similar to how the fair server parameters are
modified.
Re-use common code between ext and fair servers as needed.
Te... | {
"author": "Andrea Righi <arighi@nvidia.com>",
"date": "Mon, 26 Jan 2026 10:59:03 +0100",
"thread_id": "aYDUqdQquFcqj7rQ@slm.duckdns.org.mbox.gz"
} |
lkml | [PATCHSET v12 sched_ext/for-6.20] Add a deadline server for sched_ext tasks | sched_ext tasks can be starved by long-running RT tasks, especially since
RT throttling was replaced by deadline servers to boost only SCHED_NORMAL
tasks.
Several users in the community have reported issues with RT stalling
sched_ext tasks. This is fairly common on distributions or environments
where applications like... | Add a selftest to validate the correct behavior of the deadline server
for the ext_sched_class.
Reviewed-by: Emil Tsalapatis <emil@etsalapatis.com>
Tested-by: Christian Loehle <christian.loehle@arm.com>
Co-developed-by: Joel Fernandes <joelagnelf@nvidia.com>
Signed-off-by: Joel Fernandes <joelagnelf@nvidia.com>
Signed... | {
"author": "Andrea Righi <arighi@nvidia.com>",
"date": "Mon, 26 Jan 2026 10:59:04 +0100",
"thread_id": "aYDUqdQquFcqj7rQ@slm.duckdns.org.mbox.gz"
} |
lkml | [PATCHSET v12 sched_ext/for-6.20] Add a deadline server for sched_ext tasks | sched_ext tasks can be starved by long-running RT tasks, especially since
RT throttling was replaced by deadline servers to boost only SCHED_NORMAL
tasks.
Several users in the community have reported issues with RT stalling
sched_ext tasks. This is fairly common on distributions or environments
where applications like... | From: Joel Fernandes <joelagnelf@nvidia.com>
Add a new kselftest to verify that the total_bw value in
/sys/kernel/debug/sched/debug remains consistent across all CPUs
under different sched_ext BPF program states:
1. Before a BPF scheduler is loaded
2. While a BPF scheduler is loaded and active
3. After a BPF schedule... | {
"author": "Andrea Righi <arighi@nvidia.com>",
"date": "Mon, 26 Jan 2026 10:59:05 +0100",
"thread_id": "aYDUqdQquFcqj7rQ@slm.duckdns.org.mbox.gz"
} |
lkml | [PATCHSET v12 sched_ext/for-6.20] Add a deadline server for sched_ext tasks | sched_ext tasks can be starved by long-running RT tasks, especially since
RT throttling was replaced by deadline servers to boost only SCHED_NORMAL
tasks.
Several users in the community have reported issues with RT stalling
sched_ext tasks. This is fairly common on distributions or environments
where applications like... | Hello,
On Mon, Jan 26, 2026 at 10:58:58AM +0100, Andrea Righi wrote:
Peter, Ingo, this patchset has been around the block for a long time and the
remaining deadline and debug patches are reviewed and seem fairly isolated.
Given that the patchset addresses an on-going issue, I'd prefer to land the
series before the me... | {
"author": "Tejun Heo <tj@kernel.org>",
"date": "Mon, 2 Feb 2026 06:45:29 -1000",
"thread_id": "aYDUqdQquFcqj7rQ@slm.duckdns.org.mbox.gz"
} |
lkml | [PATCH] perf/core: Fix refcount bug and potential UAF in perf_mmap | Hello,
I would like to report a reference counting vulnerability in the Linux kernel perf_event subsystem, which I discovered using a modified syzkaller-based kernel fuzzing tool that I developed.
Summary
-------
A local user can trigger a reference count saturation or a use-after-free (UAF) vulnerability in the p... | On Sat, Jan 31, 2026 at 09:21:23PM +0800, 余昊铖 wrote:
Can you turn this into a patch we can apply (properly sent, real name
used, etc.) so that the maintainers can review it and apply it
correctly?
Also, be sure to send this to the correct people, I don't think that
the ext4 developers care that much about perf :)
th... | {
"author": "Greg KH <gregkh@linuxfoundation.org>",
"date": "Sun, 1 Feb 2026 09:18:40 +0100",
"thread_id": "CAAoXzSqHuQd7k9rp878YBG5gbChgOaProPQ6XBzKpy81JF5sKg@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH] perf/core: Fix refcount bug and potential UAF in perf_mmap | Hello,
I would like to report a reference counting vulnerability in the Linux kernel perf_event subsystem, which I discovered using a modified syzkaller-based kernel fuzzing tool that I developed.
Summary
-------
A local user can trigger a reference count saturation or a use-after-free (UAF) vulnerability in the p... | The issue is caused by a race condition between mmap() and event
teardown. In perf_mmap(), the ring_buffer (rb) is accessed via
map_range() after the mmap_mutex is released. If another thread
closes the event or detaches the buffer during this window, the
reference count of rb can drop to zero, leading to a UAF or
refc... | {
"author": "Haocheng Yu <yuhaocheng035@gmail.com>",
"date": "Sun, 1 Feb 2026 19:34:36 +0800",
"thread_id": "CAAoXzSqHuQd7k9rp878YBG5gbChgOaProPQ6XBzKpy81JF5sKg@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH] perf/core: Fix refcount bug and potential UAF in perf_mmap | Hello,
I would like to report a reference counting vulnerability in the Linux kernel perf_event subsystem, which I discovered using a modified syzkaller-based kernel fuzzing tool that I developed.
Summary
-------
A local user can trigger a reference count saturation or a use-after-free (UAF) vulnerability in the p... | > Can you turn this into a patch we can apply (properly sent, real name
Hi Greg,
Sorry for not knowing the rules and sending to the wrong people mistakenly. I have just submitted the formal patch to the perf subsystem maintainers with the correct formatting and real name.
Thanks for the guidance!
Best regards,
Haoc... | {
"author": "=?UTF-8?B?5L2Z5piK6ZOW?= <haochengyu@zju.edu.cn>",
"date": "Sun, 1 Feb 2026 19:35:31 +0800 (GMT+08:00)",
"thread_id": "CAAoXzSqHuQd7k9rp878YBG5gbChgOaProPQ6XBzKpy81JF5sKg@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH] perf/core: Fix refcount bug and potential UAF in perf_mmap | Hello,
I would like to report a reference counting vulnerability in the Linux kernel perf_event subsystem, which I discovered using a modified syzkaller-based kernel fuzzing tool that I developed.
Summary
-------
A local user can trigger a reference count saturation or a use-after-free (UAF) vulnerability in the p... | On Sun, Feb 01, 2026 at 07:34:36PM +0800, Haocheng Yu wrote:
This indentation looks very odd, are you sure it is correct?
thanks,
greg k-h | {
"author": "Greg KH <gregkh@linuxfoundation.org>",
"date": "Sun, 1 Feb 2026 12:49:11 +0100",
"thread_id": "CAAoXzSqHuQd7k9rp878YBG5gbChgOaProPQ6XBzKpy81JF5sKg@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH] perf/core: Fix refcount bug and potential UAF in perf_mmap | Hello,
I would like to report a reference counting vulnerability in the Linux kernel perf_event subsystem, which I discovered using a modified syzkaller-based kernel fuzzing tool that I developed.
Summary
-------
A local user can trigger a reference count saturation or a use-after-free (UAF) vulnerability in the p... | Hi Haocheng,
kernel test robot noticed the following build warnings:
[auto build test WARNING on perf-tools-next/perf-tools-next]
[also build test WARNING on tip/perf/core perf-tools/perf-tools linus/master v6.19-rc7 next-20260130]
[cannot apply to acme/perf/core]
[If your patch is applied to the wrong git tree, kind... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Mon, 2 Feb 2026 02:43:48 +0800",
"thread_id": "CAAoXzSqHuQd7k9rp878YBG5gbChgOaProPQ6XBzKpy81JF5sKg@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH] perf/core: Fix refcount bug and potential UAF in perf_mmap | Hello,
I would like to report a reference counting vulnerability in the Linux kernel perf_event subsystem, which I discovered using a modified syzkaller-based kernel fuzzing tool that I developed.
Summary
-------
A local user can trigger a reference count saturation or a use-after-free (UAF) vulnerability in the p... | Syzkaller reported a refcount_t: addition on 0; use-after-free warning
in perf_mmap.
The issue is caused by a race condition between mmap() and event
teardown. In perf_mmap(), the ring_buffer (rb) is accessed via
map_range() after the mmap_mutex is released. If another thread
closes the event or detaches the buffer du... | {
"author": "Haocheng Yu <yuhaocheng035@gmail.com>",
"date": "Mon, 2 Feb 2026 15:44:35 +0800",
"thread_id": "CAAoXzSqHuQd7k9rp878YBG5gbChgOaProPQ6XBzKpy81JF5sKg@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH] perf/core: Fix refcount bug and potential UAF in perf_mmap | Hello,
I would like to report a reference counting vulnerability in the Linux kernel perf_event subsystem, which I discovered using a modified syzkaller-based kernel fuzzing tool that I developed.
Summary
-------
A local user can trigger a reference count saturation or a use-after-free (UAF) vulnerability in the p... | On Mon, Feb 02, 2026 at 03:44:35PM +0800, Haocheng Yu wrote:
So you're saying this is something like:
Thread-1 Thread-2
mmap(fd)
close(fd) / ioctl(fd, IOC_SET_OUTPUT)
I don't think close() is possible, because mmap() should have a
reference on the struct file from fget(), no?
That leaves the ioctl(), let m... | {
"author": "Peter Zijlstra <peterz@infradead.org>",
"date": "Mon, 2 Feb 2026 14:58:59 +0100",
"thread_id": "CAAoXzSqHuQd7k9rp878YBG5gbChgOaProPQ6XBzKpy81JF5sKg@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH] perf/core: Fix refcount bug and potential UAF in perf_mmap | Hello,
I would like to report a reference counting vulnerability in the Linux kernel perf_event subsystem, which I discovered using a modified syzkaller-based kernel fuzzing tool that I developed.
Summary
-------
A local user can trigger a reference count saturation or a use-after-free (UAF) vulnerability in the p... | On Mon, Feb 02, 2026 at 02:58:59PM +0100, Peter Zijlstra wrote:
I'm not seeing it; once perf_mmap_rb() completes, we should have
event->mmap_count != 0, and this the IOC_SET_OUTPUT will fail.
Please provide a better explanation. | {
"author": "Peter Zijlstra <peterz@infradead.org>",
"date": "Mon, 2 Feb 2026 15:36:15 +0100",
"thread_id": "CAAoXzSqHuQd7k9rp878YBG5gbChgOaProPQ6XBzKpy81JF5sKg@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH] perf/core: Fix refcount bug and potential UAF in perf_mmap | Hello,
I would like to report a reference counting vulnerability in the Linux kernel perf_event subsystem, which I discovered using a modified syzkaller-based kernel fuzzing tool that I developed.
Summary
-------
A local user can trigger a reference count saturation or a use-after-free (UAF) vulnerability in the p... | Hi Peter,
Thanks for the review. You are right, my previous explanation was
inaccurate. The actual race condition occurs between a failing
mmap() on one event and a concurrent mmap() on a second event
that shares the ring buffer (e.g., via output redirection).
Detailed scenario is as follows, for example:
1. Thread A... | {
"author": "=?UTF-8?B?5L2Z5piK6ZOW?= <yuhaocheng035@gmail.com>",
"date": "Mon, 2 Feb 2026 23:51:28 +0800",
"thread_id": "CAAoXzSqHuQd7k9rp878YBG5gbChgOaProPQ6XBzKpy81JF5sKg@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH] perf/core: Fix refcount bug and potential UAF in perf_mmap | Hello,
I would like to report a reference counting vulnerability in the Linux kernel perf_event subsystem, which I discovered using a modified syzkaller-based kernel fuzzing tool that I developed.
Summary
-------
A local user can trigger a reference count saturation or a use-after-free (UAF) vulnerability in the p... | From: Haocheng Yu <yuhaocheng035@gmail.com>
Syzkaller reported a refcount_t: addition on 0; use-after-free warning
in perf_mmap.
The issue is caused by a race condition between a failing mmap() setup
and a concurrent mmap() on a dependent event (e.g., using output
redirection).
In perf_mmap(), the ring_buffer (rb) i... | {
"author": "yuhaocheng035@gmail.com",
"date": "Tue, 3 Feb 2026 00:20:56 +0800",
"thread_id": "CAAoXzSqHuQd7k9rp878YBG5gbChgOaProPQ6XBzKpy81JF5sKg@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The "qup-memory" interconnect path is optional and may not be defined
in all device trees. Unroll the loop-based ICC path initialization to
allow specific error handling for each path type.
The "qup-core" and "qup-config" paths remain mandatory and will fail
probe if missing, while "qup-memory" is now handled as optio... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:10 +0530",
"thread_id": "20260202180922.1692428-8-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Add a new function geni_icc_set_bw_ab() that allows callers to set
average bandwidth values for all ICC (Interconnect) paths in a single
call. This function takes separate parameters for core, config, and DDR
average bandwidth values and applies them to the respective ICC paths.
This provides a more convenient API for... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:11 +0530",
"thread_id": "20260202180922.1692428-8-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI Serial Engine drivers (I2C, SPI, and SERIAL) currently duplicate
code for initializing shared resources such as clocks and interconnect
paths.
Introduce a new helper API, geni_se_resources_init(), to centralize this
initialization logic, improving modularity and simplifying the probe
function.
Signed-off-by:... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:12 +0530",
"thread_id": "20260202180922.1692428-8-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Currently, core clk is handled individually in protocol drivers like
the I2C driver. Move this clock management to the common clock APIs
(geni_se_clks_on/off) that are already present in the common GENI SE
driver to maintain consistency across all protocol drivers.
Core clk is now properly managed alongside the other ... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:13 +0530",
"thread_id": "20260202180922.1692428-8-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI SE protocol drivers (I2C, SPI, UART) implement similar resource
activation/deactivation sequences independently, leading to code
duplication.
Introduce geni_se_resources_activate()/geni_se_resources_deactivate() to
power on/off resources.The activate function enables ICC, clocks, and TLMM
whereas the deactiva... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:14 +0530",
"thread_id": "20260202180922.1692428-8-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI Serial Engine drivers (I2C, SPI, and SERIAL) currently handle
the attachment of power domains. This often leads to duplicated code
logic across different driver probe functions.
Introduce a new helper API, geni_se_domain_attach(), to centralize
the logic for attaching "power" and "perf" domains to the GENI SE... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:15 +0530",
"thread_id": "20260202180922.1692428-8-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI Serial Engine (SE) drivers (I2C, SPI, and SERIAL) currently
manage performance levels and operating points directly. This resulting
in code duplication across drivers. such as configuring a specific level
or find and apply an OPP based on a clock frequency.
Introduce two new helper APIs, geni_se_set_perf_leve... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:16 +0530",
"thread_id": "20260202180922.1692428-8-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Add DT bindings for the QUP GENI I2C controller on sa8255p platforms.
SA8255p platform abstracts resources such as clocks, interconnect and
GPIO pins configuration in Firmware. SCMI power and perf protocol
are utilized to request resource configurations.
SA8255p platform does not require the Serial Engine (SE) common... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:17 +0530",
"thread_id": "20260202180922.1692428-8-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Moving the serial engine setup to geni_i2c_init() API for a cleaner
probe function and utilizes the PM runtime API to control resources
instead of direct clock-related APIs for better resource management.
Enables reusability of the serial engine initialization like
hibernation and deep sleep features where hardware co... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:18 +0530",
"thread_id": "20260202180922.1692428-8-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Refactor the resource initialization in geni_i2c_probe() by introducing
a new geni_i2c_resources_init() function and utilizing the common
geni_se_resources_init() framework and clock frequency mapping, making the
probe function cleaner.
Acked-by: Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>
Signed-off-by: Pravee... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:19 +0530",
"thread_id": "20260202180922.1692428-8-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | To manage GENI serial engine resources during runtime power management,
drivers currently need to call functions for ICC, clock, and
SE resource operations in both suspend and resume paths, resulting in
code duplication across drivers.
The new geni_se_resources_activate() and geni_se_resources_deactivate()
helper APIs... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:20 +0530",
"thread_id": "20260202180922.1692428-8-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | To avoid repeatedly fetching and checking platform data across various
functions, store the struct of_device_id data directly in the i2c
private structure. This change enhances code maintainability and reduces
redundancy.
Acked-by: Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>
Signed-off-by: Praveen Talari <prave... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:21 +0530",
"thread_id": "20260202180922.1692428-8-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:22 +0530",
"thread_id": "20260202180922.1692428-8-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | Currently the vdso doesn't include .note.gnu.property or a GNU noexec
stack annotation (the -z noexecstack in the linker script is
ineffective because we specify PHDRs explicitly.)
The motivation is that the dynamic linker currently do not check
these.
However, this is a weak excuse: the vdso*.so are also supposed to... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 16 Dec 2025 13:26:01 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | A macro SYSCALL_ENTER_KERNEL was defined in sigreturn.S, with the
ability of overriding it. The override capability, however, is not
used anywhere, and the macro name is potentially confusing because it
seems to imply that sysenter/syscall could be used here, which is NOT
true: the sigreturn system calls MUST use int $... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 16 Dec 2025 13:25:59 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | It is generally better to build tools in arch/x86/tools to keep host
cflags proliferation down, and to reduce makefile sequencing issues.
Move the vdso build tool vdso2c into arch/x86/tools in preparation for
refactoring the vdso makefiles.
Signed-off-by: H. Peter Anvin (Intel) <hpa@zytor.com>
---
arch/x86/Makefile ... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 16 Dec 2025 13:25:56 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The vdso32 sigreturn.S contains open-coded DWARF bytecode, which
includes a hack for gdb to not try to step back to a previous call
instruction when backtracing from a signal handler.
Neither of those are necessary anymore: the backtracing issue is
handled by ".cfi_entry simple" and ".cfi_signal_frame", both of which
... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 16 Dec 2025 13:26:00 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The vdso .so files are named vdso*.so. These structures are binary
images and descriptions of these files, so it is more consistent for
them to have a naming that more directly mirrors the filenames.
It is also very slightly more compact (by one character...) and
simplifies the Makefile just a little bit.
Signed-off-... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 16 Dec 2025 13:25:55 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | There is no fundamental reason to use the int80_landing_pad symbol to
adjust ip when moving the vdso. If ip falls within the vdso, and the
vdso is moved, we should change the ip accordingly, regardless of mode
or location within the vdso. This *currently* can only happen on 32
bits, but there isn't any reason not to do... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 16 Dec 2025 13:25:58 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | When neither sysenter32 nor syscall32 is available (on either
FRED-capable 64-bit hardware or old 32-bit hardware), there is no
reason to do a bunch of stack shuffling in __kernel_vsyscall.
Unfortunately, just overwriting the initial "push" instructions will
mess up the CFI annotations, so suffer the 3-byte NOP if not
... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 16 Dec 2025 13:26:04 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | Abstract out the calling of true system calls from the vdso into
macros.
It has been a very long time since gcc did not allow %ebx or %ebp in
inline asm in 32-bit PIC mode; remove the corresponding hacks.
Remove the use of memory output constraints in gettimeofday.h in favor
of "memory" clobbers. The resulting code i... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 16 Dec 2025 13:26:02 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | In most cases, the use of "fast 32-bit system call" depends either on
X86_FEATURE_SEP or X86_FEATURE_SYSENTER32 || X86_FEATURE_SYSCALL32.
However, nearly all the logic for both is identical.
Define X86_FEATURE_SYSFAST32 which indicates that *either* SYSENTER32 or
SYSCALL32 should be used, for either 32- or 64-bit kern... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 16 Dec 2025 13:26:03 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | - Separate out the vdso sources into common, vdso32, and vdso64
directories.
- Build the 32- and 64-bit vdsos in their respective subdirectories;
this greatly simplifies the build flags handling.
- Unify the mangling of Makefile flags between the 32- and 64-bit
vdso code as much as possible; all common rules are ... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 16 Dec 2025 13:25:57 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | On Tue, Dec 16, 2025 at 4:26 PM H. Peter Anvin <hpa@zytor.com> wrote:
Do we even still support the old linkers that need these constants?
Brian Gerst | {
"author": "Brian Gerst <brgerst@gmail.com>",
"date": "Wed, 17 Dec 2025 21:16:08 -0500",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | On Wed, Dec 17, 2025 at 9:16 PM Brian Gerst <brgerst@gmail.com> wrote:
Digging into the binutils source, PT_GNU_EH_FRAME and PT_GNU_STACK
were added to the parser around bintils-2.15. PT_GNU_PROPERTY was
added in binutils-2.38, which is newer than the minimum supported
version of binutils-2.30.
Probably better to ju... | {
"author": "Brian Gerst <brgerst@gmail.com>",
"date": "Thu, 18 Dec 2025 01:56:49 -0500",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | On Tue, Dec 16, 2025 at 10:26 PM H. Peter Anvin <hpa@zytor.com> wrote:
Acked-by: Uros Bizjak <ubizjak@gmail.com> | {
"author": "Uros Bizjak <ubizjak@gmail.com>",
"date": "Tue, 6 Jan 2026 19:09:48 +0100",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | When neither sysenter32 nor syscall32 is available (on either
FRED-capable 64-bit hardware or old 32-bit hardware), there is no
reason to do a bunch of stack shuffling in __kernel_vsyscall.
Unfortunately, just overwriting the initial "push" instructions will
mess up the CFI annotations, so suffer the 3-byte NOP if not
... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 6 Jan 2026 13:18:43 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | Currently the vdso doesn't include .note.gnu.property or a GNU noexec
stack annotation (the -z noexecstack in the linker script is
ineffective because we specify PHDRs explicitly.)
The motivation is that the dynamic linker currently do not check
these.
However, this is a weak excuse: the vdso*.so are also supposed to... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 6 Jan 2026 13:18:40 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | In most cases, the use of "fast 32-bit system call" depends either on
X86_FEATURE_SEP or X86_FEATURE_SYSENTER32 || X86_FEATURE_SYSCALL32.
However, nearly all the logic for both is identical.
Define X86_FEATURE_SYSFAST32 which indicates that *either* SYSENTER32 or
SYSCALL32 should be used, for either 32- or 64-bit kern... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 6 Jan 2026 13:18:42 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | Abstract out the calling of true system calls from the vdso into
macros.
It has been a very long time since gcc did not allow %ebx or %ebp in
inline asm in 32-bit PIC mode; remove the corresponding hacks.
Remove the use of memory output constraints in gettimeofday.h in favor
of "memory" clobbers. The resulting code i... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 6 Jan 2026 13:18:41 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The vdso32 sigreturn.S contains open-coded DWARF bytecode, which
includes a hack for gdb to not try to step back to a previous call
instruction when backtracing from a signal handler.
Neither of those are necessary anymore: the backtracing issue is
handled by ".cfi_entry simple" and ".cfi_signal_frame", both of which
... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 6 Jan 2026 13:18:39 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | There is no fundamental reason to use the int80_landing_pad symbol to
adjust ip when moving the vdso. If ip falls within the vdso, and the
vdso is moved, we should change the ip accordingly, regardless of mode
or location within the vdso. This *currently* can only happen on 32
bits, but there isn't any reason not to do... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 6 Jan 2026 13:18:37 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | It is generally better to build tools in arch/x86/tools to keep host
cflags proliferation down, and to reduce makefile sequencing issues.
Move the vdso build tool vdso2c into arch/x86/tools in preparation for
refactoring the vdso makefiles.
Signed-off-by: H. Peter Anvin (Intel) <hpa@zytor.com>
---
arch/x86/Makefile ... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 6 Jan 2026 13:18:35 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The vdso .so files are named vdso*.so. These structures are binary
images and descriptions of these files, so it is more consistent for
them to have a naming that more directly mirrors the filenames.
It is also very slightly more compact (by one character...) and
simplifies the Makefile just a little bit.
Signed-off-... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 6 Jan 2026 13:18:34 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | This is intended as a ping, since I think the v4 got swallowed by the
holidays. v4.1 IS BASICALLY A REBASE AND RESEND OF v4; THE ONLY CODE
CHANGE IS A SINGLE SPACE CHARACTER.
This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, a... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 6 Jan 2026 13:18:33 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | A macro SYSCALL_ENTER_KERNEL was defined in sigreturn.S, with the
ability of overriding it. The override capability, however, is not
used anywhere, and the macro name is potentially confusing because it
seems to imply that sysenter/syscall could be used here, which is NOT
true: the sigreturn system calls MUST use int $... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 6 Jan 2026 13:18:38 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | - Separate out the vdso sources into common, vdso32, and vdso64
directories.
- Build the 32- and 64-bit vdsos in their respective subdirectories;
this greatly simplifies the build flags handling.
- Unify the mangling of Makefile flags between the 32- and 64-bit
vdso code as much as possible; all common rules are ... | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Tue, 6 Jan 2026 13:18:36 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | On 06/01/2026 9:18 pm, H. Peter Anvin wrote:
The v4/v4.1 notes will presumably want dropping before committing? | {
"author": "Andrew Cooper <andrew.cooper3@citrix.com>",
"date": "Wed, 7 Jan 2026 12:10:52 +0000",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 93d73005bff4f600696ce30e366e742c3373b13d
Gitweb: https://git.kernel.org/tip/93d73005bff4f600696ce30e366e742c3373b13d
Author: H. Peter Anvin <hpa@zytor.com>
AuthorDate: Tue, 16 Dec 2025 13:25:55 -08:00
Committer: ... | {
"author": "\"tip-bot2 for H. Peter Anvin\" <tip-bot2@linutronix.de>",
"date": "Wed, 14 Jan 2026 00:01:26 -0000",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The following commit has been merged into the x86/entry branch of tip:
Commit-ID: a76108d05ee13cddb72b620752a80b2c3e87aee1
Gitweb: https://git.kernel.org/tip/a76108d05ee13cddb72b620752a80b2c3e87aee1
Author: H. Peter Anvin <hpa@zytor.com>
AuthorDate: Tue, 16 Dec 2025 13:25:56 -08:00
Committer: ... | {
"author": "\"tip-bot2 for H. Peter Anvin\" <tip-bot2@linutronix.de>",
"date": "Wed, 14 Jan 2026 00:01:25 -0000",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 693c819fedcdcabfda7488e2d5e355a84c2fd1b0
Gitweb: https://git.kernel.org/tip/693c819fedcdcabfda7488e2d5e355a84c2fd1b0
Author: H. Peter Anvin <hpa@zytor.com>
AuthorDate: Tue, 16 Dec 2025 13:25:57 -08:00
Committer: ... | {
"author": "\"tip-bot2 for H. Peter Anvin\" <tip-bot2@linutronix.de>",
"date": "Wed, 14 Jan 2026 00:01:23 -0000",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 36d83c249e0395a915144eceeb528ddc19b1fbe6
Gitweb: https://git.kernel.org/tip/36d83c249e0395a915144eceeb528ddc19b1fbe6
Author: H. Peter Anvin <hpa@zytor.com>
AuthorDate: Tue, 16 Dec 2025 13:26:04 -08:00
Committer: ... | {
"author": "\"tip-bot2 for H. Peter Anvin\" <tip-bot2@linutronix.de>",
"date": "Wed, 14 Jan 2026 00:44:45 -0000",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The following commit has been merged into the x86/entry branch of tip:
Commit-ID: f49ecf5e110ab0ed255ddea5e321689faf4e50e6
Gitweb: https://git.kernel.org/tip/f49ecf5e110ab0ed255ddea5e321689faf4e50e6
Author: H. Peter Anvin <hpa@zytor.com>
AuthorDate: Tue, 16 Dec 2025 13:26:03 -08:00
Committer: ... | {
"author": "\"tip-bot2 for H. Peter Anvin\" <tip-bot2@linutronix.de>",
"date": "Wed, 14 Jan 2026 00:44:49 -0000",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 98d3e996513ad00b7824ea3bece506fc645547dd
Gitweb: https://git.kernel.org/tip/98d3e996513ad00b7824ea3bece506fc645547dd
Author: H. Peter Anvin <hpa@zytor.com>
AuthorDate: Tue, 16 Dec 2025 13:25:59 -08:00
Committer: ... | {
"author": "\"tip-bot2 for H. Peter Anvin\" <tip-bot2@linutronix.de>",
"date": "Wed, 14 Jan 2026 00:44:54 -0000",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 8717b02b8c030dc0c4b55781b59e88def0a1a92f
Gitweb: https://git.kernel.org/tip/8717b02b8c030dc0c4b55781b59e88def0a1a92f
Author: H. Peter Anvin <hpa@zytor.com>
AuthorDate: Tue, 16 Dec 2025 13:26:01 -08:00
Committer: ... | {
"author": "\"tip-bot2 for H. Peter Anvin\" <tip-bot2@linutronix.de>",
"date": "Wed, 14 Jan 2026 00:44:52 -0000",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The following commit has been merged into the x86/entry branch of tip:
Commit-ID: a0636d4c3ad0da0cd6069eb6fef5d2b7d3449378
Gitweb: https://git.kernel.org/tip/a0636d4c3ad0da0cd6069eb6fef5d2b7d3449378
Author: H. Peter Anvin <hpa@zytor.com>
AuthorDate: Tue, 16 Dec 2025 13:26:02 -08:00
Committer: ... | {
"author": "\"tip-bot2 for H. Peter Anvin\" <tip-bot2@linutronix.de>",
"date": "Wed, 14 Jan 2026 00:44:51 -0000",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 6e150b71019f386a021004fafea9ef7189bc6aea
Gitweb: https://git.kernel.org/tip/6e150b71019f386a021004fafea9ef7189bc6aea
Author: H. Peter Anvin <hpa@zytor.com>
AuthorDate: Tue, 16 Dec 2025 13:25:58 -08:00
Committer: ... | {
"author": "\"tip-bot2 for H. Peter Anvin\" <tip-bot2@linutronix.de>",
"date": "Wed, 14 Jan 2026 00:44:55 -0000",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 884961618ee51307cc63ab620a0bdd710fa0b0af
Gitweb: https://git.kernel.org/tip/884961618ee51307cc63ab620a0bdd710fa0b0af
Author: H. Peter Anvin <hpa@zytor.com>
AuthorDate: Tue, 16 Dec 2025 13:26:00 -08:00
Committer: ... | {
"author": "\"tip-bot2 for H. Peter Anvin\" <tip-bot2@linutronix.de>",
"date": "Wed, 14 Jan 2026 00:44:53 -0000",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | [stripped down the list of recipients quite a bit]
On 1/6/26 22:18, H. Peter Anvin wrote:
Lo! My daily -next builds for Fedora failed on x86_64 (other archs
worked fine). Haven't checked, but from the error message I wonder
if this might be due to the changes from this patch-set that showed
up in -next today:
+ /us... | {
"author": "Thorsten Leemhuis <linux@leemhuis.info>",
"date": "Thu, 15 Jan 2026 08:00:55 +0100",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | On January 14, 2026 11:00:55 PM PST, Thorsten Leemhuis <linux@leemhuis.info> wrote:
Looks like it. Specifically it looks like it needs a tweak to make vdso_install. I'll look at it in a few hours. | {
"author": "\"H. Peter Anvin\" <hpa@zytor.com>",
"date": "Thu, 15 Jan 2026 07:00:47 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | On Tue, 6 Jan 2026 13:18:36 -0800 "H. Peter Anvin" <hpa@zytor.com> wrote:
Hi everyone,
I ran the tip master branch through my AI review prompts and this one was
flagged. These look right to me, apologies if it's noise:
[ ... ]
^^^^^^^
Should this be "-fno-PIE" with the leading ... | {
"author": "Chris Mason <clm@meta.com>",
"date": "Thu, 15 Jan 2026 19:58:02 -0800",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | From: "Borislav Petkov (AMD)" <bp@alien8.de>
Date: Tue, 27 Jan 2026 23:09:13 +0100
The commit
a76108d05ee1 ("x86/entry/vdso: Move vdso2c to arch/x86/tools")
moved vdso2c to arch/x86/tools/ and commit
93d73005bff4 ("x86/entry/vdso: Rename vdso_image_* to vdso*_image")
renamed .so files but also dropped vdso2c f... | {
"author": "Borislav Petkov <bp@alien8.de>",
"date": "Tue, 27 Jan 2026 23:16:33 +0100",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | The following commit has been merged into the x86/entry branch of tip:
Commit-ID: ce9b1c10c3f1c723c3cc7b63aa8331fdb6c57a04
Gitweb: https://git.kernel.org/tip/ce9b1c10c3f1c723c3cc7b63aa8331fdb6c57a04
Author: Borislav Petkov (AMD) <bp@alien8.de>
AuthorDate: Tue, 27 Jan 2026 23:09:13 +01:00
Committer... | {
"author": "\"tip-bot2 for Borislav Petkov (AMD)\" <tip-bot2@linutronix.de>",
"date": "Tue, 27 Jan 2026 22:33:30 -0000",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.mbox.gz"
} |
lkml | [PATCH v4 00/10] x86/entry/vdso: clean up the vdso build, vdso updates | This patchset cleans up the vdso build by building the 32- and 64-bit
vdsos in separate directories, moving the vdso2c tool to
arch/x86/tools, and by merging common code and especially Makefile
rules between the 32- and 64-bit vdsos to the greatest extent
possible.
Be more strict about sanitizing and standardizing the... | Hello Peter!
On 1/6/2026 10:18 PM, H. Peter Anvin wrote:
Hopefully Glibc developers will do something similar for x86-64
__restore_rt() in Glibc sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c.
...
...
Note that the "S" in "zRS" is the signal frame indication.
Your version does no longer have this nop nor do... | {
"author": "Jens Remus <jremus@linux.ibm.com>",
"date": "Mon, 2 Feb 2026 18:02:48 +0100",
"thread_id": "vdso-cleanup-patch-4.1@zytor.com.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... | 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": "willemdebruijn.kernel.16b0979449c84@gmail.com.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": "willemdebruijn.kernel.16b0979449c84@gmail.com.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": "willemdebruijn.kernel.16b0979449c84@gmail.com.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": "willemdebruijn.kernel.16b0979449c84@gmail.com.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": "willemdebruijn.kernel.16b0979449c84@gmail.com.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": "willemdebruijn.kernel.16b0979449c84@gmail.com.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": "willemdebruijn.kernel.16b0979449c84@gmail.com.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": "willemdebruijn.kernel.16b0979449c84@gmail.com.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": "willemdebruijn.kernel.16b0979449c84@gmail.com.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": "willemdebruijn.kernel.16b0979449c84@gmail.com.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": "willemdebruijn.kernel.16b0979449c84@gmail.com.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": "willemdebruijn.kernel.16b0979449c84@gmail.com.mbox.gz"
} |
lkml | [PATCH 1/2] vduse: avoid adding implicit padding | From: Arnd Bergmann <arnd@arndb.de>
The vduse_iova_range_v2 and vduse_iotlb_entry_v2 structures are both
defined in a way that adds implicit padding and is incompatible between
i386 and x86_64 userspace because of the different structure alignment
requirements. Building the header with -Wpadded shows these new warning... | From: Arnd Bergmann <arnd@arndb.de>
These two ioctls are incompatible on 32-bit x86 userspace, because
the data structures are shorter than they are on 64-bit.
Add compad handling to the regular ioctl handler to just handle
them the same way and ignore the extra padding. This could be
done in a separate .compat_ioctl... | {
"author": "Arnd Bergmann <arnd@kernel.org>",
"date": "Mon, 2 Feb 2026 10:59:32 +0100",
"thread_id": "20260202114412-mutt-send-email-mst@kernel.org.mbox.gz"
} |
lkml | [PATCH 1/2] vduse: avoid adding implicit padding | From: Arnd Bergmann <arnd@arndb.de>
The vduse_iova_range_v2 and vduse_iotlb_entry_v2 structures are both
defined in a way that adds implicit padding and is incompatible between
i386 and x86_64 userspace because of the different structure alignment
requirements. Building the header with -Wpadded shows these new warning... | On Mon, Feb 2, 2026 at 11:06 AM Arnd Bergmann <arnd@kernel.org> wrote:
s/indiviudally/individually/ if v2
That's something I didn't take into account, thanks!
I did not know about _IOC_SIZE and I like how it reduces the complexity, thanks!
As a proposal, maybe we can add MIN(_IOC_SIZE, sizeof(entry)) ? Not
sure i... | {
"author": "Eugenio Perez Martin <eperezma@redhat.com>",
"date": "Mon, 2 Feb 2026 12:28:26 +0100",
"thread_id": "20260202114412-mutt-send-email-mst@kernel.org.mbox.gz"
} |
lkml | [PATCH 1/2] vduse: avoid adding implicit padding | From: Arnd Bergmann <arnd@arndb.de>
The vduse_iova_range_v2 and vduse_iotlb_entry_v2 structures are both
defined in a way that adds implicit padding and is incompatible between
i386 and x86_64 userspace because of the different structure alignment
requirements. Building the header with -Wpadded shows these new warning... | On Mon, Feb 2, 2026 at 11:07 AM Arnd Bergmann <arnd@kernel.org> wrote:
I'm just learning about the COMPAT_ stuff but does this mean the
userland app need to call a different ioctl depending if it is
compiled for 32 bits or 64 bits? I guess it is not the case, but how
is that handled? | {
"author": "Eugenio Perez Martin <eperezma@redhat.com>",
"date": "Mon, 2 Feb 2026 12:34:48 +0100",
"thread_id": "20260202114412-mutt-send-email-mst@kernel.org.mbox.gz"
} |
lkml | [PATCH 1/2] vduse: avoid adding implicit padding | From: Arnd Bergmann <arnd@arndb.de>
The vduse_iova_range_v2 and vduse_iotlb_entry_v2 structures are both
defined in a way that adds implicit padding and is incompatible between
i386 and x86_64 userspace because of the different structure alignment
requirements. Building the header with -Wpadded shows these new warning... | On Mon, Feb 2, 2026 at 12:28 PM Eugenio Perez Martin
<eperezma@redhat.com> wrote:
(I hit "Send" too early).
We could make this padding[3] so reserved keeps being [12]. This way
the struct members keep the same alignment between the commits. Not
super important as there should not be a lot of users of this right
now, ... | {
"author": "Eugenio Perez Martin <eperezma@redhat.com>",
"date": "Mon, 2 Feb 2026 12:50:49 +0100",
"thread_id": "20260202114412-mutt-send-email-mst@kernel.org.mbox.gz"
} |
lkml | [PATCH 1/2] vduse: avoid adding implicit padding | From: Arnd Bergmann <arnd@arndb.de>
The vduse_iova_range_v2 and vduse_iotlb_entry_v2 structures are both
defined in a way that adds implicit padding and is incompatible between
i386 and x86_64 userspace because of the different structure alignment
requirements. Building the header with -Wpadded shows these new warning... | On Mon, Feb 2, 2026, at 12:34, Eugenio Perez Martin wrote:
In a definition like
#define VDUSE_IOTLB_GET_FD _IOWR(VDUSE_BASE, 0x10, struct vduse_iotlb_entry)
The resulting integer value encodes sizeof(struct vduse_iotlb_entry)
in some of the bits. Since x86-32 and x86-64 have different
sizes for this particular ... | {
"author": "\"Arnd Bergmann\" <arnd@arndb.de>",
"date": "Mon, 02 Feb 2026 12:59:03 +0100",
"thread_id": "20260202114412-mutt-send-email-mst@kernel.org.mbox.gz"
} |
lkml | [PATCH 1/2] vduse: avoid adding implicit padding | From: Arnd Bergmann <arnd@arndb.de>
The vduse_iova_range_v2 and vduse_iotlb_entry_v2 structures are both
defined in a way that adds implicit padding and is incompatible between
i386 and x86_64 userspace because of the different structure alignment
requirements. Building the header with -Wpadded shows these new warning... | On Mon, Feb 2, 2026, at 12:50, Eugenio Perez Martin wrote:
I think it's more readable without the MIN(), but I don't mind
adding it either.
I think that is too risky, as it would overlay 'asid' on top of
previously uninitialized padding fields coming from userspace
on most architectures. Since there was previously n... | {
"author": "\"Arnd Bergmann\" <arnd@arndb.de>",
"date": "Mon, 02 Feb 2026 13:06:54 +0100",
"thread_id": "20260202114412-mutt-send-email-mst@kernel.org.mbox.gz"
} |
lkml | [PATCH 1/2] vduse: avoid adding implicit padding | From: Arnd Bergmann <arnd@arndb.de>
The vduse_iova_range_v2 and vduse_iotlb_entry_v2 structures are both
defined in a way that adds implicit padding and is incompatible between
i386 and x86_64 userspace because of the different structure alignment
requirements. Building the header with -Wpadded shows these new warning... | On Mon, Feb 02, 2026 at 12:59:03PM +0100, Arnd Bergmann wrote:
I think .compat_ioctl would be cleaner frankly. Just look at
all the ifdefery. And who knows what broken-ness userspace
comes up with with this approach. Better use the standard approach. | {
"author": "\"Michael S. Tsirkin\" <mst@redhat.com>",
"date": "Mon, 2 Feb 2026 11:45:13 -0500",
"thread_id": "20260202114412-mutt-send-email-mst@kernel.org.mbox.gz"
} |
lkml | [PATCH 0/2] Add HPET NMI Watchdog support | The current NMI watchdog relies on performance counters and consistently
occupies one on each CPU. When running virtual machines, we want to pass
performance counters to virtual machines so they can make use of them.
In addition the host system wants to use performance counters to check
the system to identify when anyt... | To implement an HPET based NMI watchdog, the HPET code will need to
reconfigure an IOAPIC pin to NMI mode. Add a function that allows driver
code to configure an IOAPIC pin for NMI delivery mode.
(Disclaimer: Some of this code was written with the help of Kiro, an AI
coding assistant)
Signed-off-by: Alexander Graf <g... | {
"author": "Alexander Graf <graf@amazon.com>",
"date": "Mon, 2 Feb 2026 17:43:15 +0000",
"thread_id": "20260202174316.65044-2-graf@amazon.com.mbox.gz"
} |
lkml | [PATCH 0/2] Add HPET NMI Watchdog support | The current NMI watchdog relies on performance counters and consistently
occupies one on each CPU. When running virtual machines, we want to pass
performance counters to virtual machines so they can make use of them.
In addition the host system wants to use performance counters to check
the system to identify when anyt... | To implement an HPET based NMI watchdog, the HPET code will need to
reconfigure an IOAPIC pin to NMI mode. Add a function that allows driver
code to configure an IOAPIC pin for NMI delivery mode.
The caller can choose whether to invoke NMIs on the BSP or broadcast on
all CPUs in the system.
(Disclaimer: Some of this ... | {
"author": "Alexander Graf <graf@amazon.com>",
"date": "Mon, 2 Feb 2026 17:48:02 +0000",
"thread_id": "20260202174316.65044-2-graf@amazon.com.mbox.gz"
} |
lkml | [PATCH 0/2] Add HPET NMI Watchdog support | The current NMI watchdog relies on performance counters and consistently
occupies one on each CPU. When running virtual machines, we want to pass
performance counters to virtual machines so they can make use of them.
In addition the host system wants to use performance counters to check
the system to identify when anyt... | On 02.02.26 18:43, Alexander Graf wrote:
Sorry for the resend. I caught an issue while sending out the series,
hit ctrl-c before thinking and suddenly had a half sent series. Discard
this one. Happy review on the real, full one :)
Alex
Amazon Web Services Development Center Germany GmbH
Tamara-Danz-Str. 13
10... | {
"author": "Alexander Graf <graf@amazon.com>",
"date": "Mon, 2 Feb 2026 18:49:13 +0100",
"thread_id": "20260202174316.65044-2-graf@amazon.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Change '(x - 1) + x' to '2 * (x - 1) + 1' to avoid expanding the
non-trivial __type_half_max() twice.
Signed-off-by: David Laight <david.laight.linux@gmail.com>
---
include/linux/overflow.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/l... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:18 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Since the type is always unsigned (T)-1 is always the correct value
so there is no need to use type_max().
Signed-off-by: David Laight <david.laight.linux@gmail.com>
---
include/linux/bits.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/includ... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:25 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Compile-time tests being added to BIT() make it an 'integer constant
expression' rather than a pre-processor expression for W=1 builds.
Change the BIT(PLANE_INDEX_BITS) != VIDEO_MAX_PLANES test to use
static_assert() so the code compiles.
Signed-off-by: David Laight ... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:20 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
The check for invalid 'compile time constant' parameters can easily be
changed to return 'failed' rather than generating a compile time error.
Add some tests for negative, swapped and overlarge values.
Signed-off-by: David Laight <david.laight.linux@gmail.com>
---
li... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:31 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Some compile time checks significantly bloat the pre-processor output
(particularly when the get nested).
Since the checks aren't really needed on every compilation enable with
W=c (adds -DKBUILD_EXTRA_WARNc) so the checks can be enabled per-build.
Make W=1 imply W=c s... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:19 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Compile-time tests being added to BIT() make it an 'integer constant
expression' rather than a pre-processor expression for W=1 builds.
Change the FRAC_ACC != BDS_UNIT test to use static_assert() so the code
compiles.
Signed-off-by: David Laight <david.laight.linux@g... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:21 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
asm/tlb.h isn't part of the vdso, use the linux/bits.h header.
Signed-off-by: David Laight <david.laight.linux@gmail.com>
---
arch/x86/include/asm/tlb.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/include/asm/tlb.h b/arch/x86/include/... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:24 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
Casting the value of BIT_U*() and GENMASK_U8() to (u8) is pointless.
Although it changes what typeof(BIT_U8()) returns the value will
always be promoted to 'signed int' before it is used.
Instead force the expression to be an unsigned type.
Avoids unexpected sign exte... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:26 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
thread_info_tif.h isn't part of the vdso, use the linux/bits.h header.
Signed-off-by: David Laight <david.laight.linux@gmail.com>
---
include/asm-generic/thread_info_tif.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/asm-generic/thread_... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:23 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
lkml | [PATCH next 00/14] bits: De-bloat expansion of GENMASK() | From: David Laight <david.laight.linux@gmail.com>
The expansion of GENMASK() is a few hundred bytes, this is often multiplied
when the value is passed to other #defines (eg FIELD_PREP).
Part of the size is due to the compile-type check (for reversed arguments),
the rest from the way the value is defined.
Nothing in t... | From: David Laight <david.laight.linux@gmail.com>
The assembler only supports one type of signed integers, so expressions
using BITS_PER_LONG (etc) cannot be guaranteed to be correct.
Use ((2 << (h)) - (1 << (l))) for all assembler GENMASK() expansions and
add definitions of BIT_Uxx() as (1 << (nr)).
Note that 64bit... | {
"author": "david.laight.linux@gmail.com",
"date": "Wed, 21 Jan 2026 14:57:27 +0000",
"thread_id": "20260121145731.3623-1-david.laight.linux@gmail.com.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.