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 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": "223707e2-3231-4037-bd1f-490ddf6aeeb6@linux.ibm.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": "223707e2-3231-4037-bd1f-490ddf6aeeb6@linux.ibm.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": "223707e2-3231-4037-bd1f-490ddf6aeeb6@linux.ibm.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": "223707e2-3231-4037-bd1f-490ddf6aeeb6@linux.ibm.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": "223707e2-3231-4037-bd1f-490ddf6aeeb6@linux.ibm.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": "223707e2-3231-4037-bd1f-490ddf6aeeb6@linux.ibm.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": "223707e2-3231-4037-bd1f-490ddf6aeeb6@linux.ibm.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": "223707e2-3231-4037-bd1f-490ddf6aeeb6@linux.ibm.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": "223707e2-3231-4037-bd1f-490ddf6aeeb6@linux.ibm.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": "223707e2-3231-4037-bd1f-490ddf6aeeb6@linux.ibm.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": "223707e2-3231-4037-bd1f-490ddf6aeeb6@linux.ibm.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": "223707e2-3231-4037-bd1f-490ddf6aeeb6@linux.ibm.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": "223707e2-3231-4037-bd1f-490ddf6aeeb6@linux.ibm.com.mbox.gz"
} |
lkml | [PATCH] nvdimm: virtio_pmem: serialize flush requests | Under heavy concurrent flush traffic, virtio-pmem can overflow its request
virtqueue (req_vq): virtqueue_add_sgs() starts returning -ENOSPC and the
driver logs "no free slots in the virtqueue". Shortly after that the
device enters VIRTIO_CONFIG_S_NEEDS_RESET and flush requests fail with
"virtio pmem device needs a rese... | Li Chen wrote:
I don't see this error.
<file>
13:28:50 > cat foo.fio
# test http://lore.kernel.org/20260113034552.62805-1-me@linux.beauty
[global]
filename=/mnt/bench/foo
ioengine=io_uring
size=1G
bs=4K
iodepth=64
numjobs=64
direct=1
fsync=1
runtime=30s
time_based=1
[rand-write]
rw=randwrite
</file>
It's possible... | {
"author": "Ira Weiny <ira.weiny@intel.com>",
"date": "Fri, 30 Jan 2026 14:52:12 -0600",
"thread_id": "6980dc5569d5a_3430210092@iweiny-mobl.notmuch.mbox.gz"
} |
lkml | [PATCH] nvdimm: virtio_pmem: serialize flush requests | Under heavy concurrent flush traffic, virtio-pmem can overflow its request
virtqueue (req_vq): virtqueue_add_sgs() starts returning -ENOSPC and the
driver logs "no free slots in the virtqueue". Shortly after that the
device enters VIRTIO_CONFIG_S_NEEDS_RESET and flush requests fail with
"virtio pmem device needs a rese... | On Fri, Jan 30, 2026 at 02:52:12PM -0600, Ira Weiny wrote:
for that matter might_sleep not really needed near mutex_lock. | {
"author": "\"Michael S. Tsirkin\" <mst@redhat.com>",
"date": "Sat, 31 Jan 2026 12:46:19 -0500",
"thread_id": "6980dc5569d5a_3430210092@iweiny-mobl.notmuch.mbox.gz"
} |
lkml | [PATCH] nvdimm: virtio_pmem: serialize flush requests | Under heavy concurrent flush traffic, virtio-pmem can overflow its request
virtqueue (req_vq): virtqueue_add_sgs() starts returning -ENOSPC and the
driver logs "no free slots in the virtqueue". Shortly after that the
device enters VIRTIO_CONFIG_S_NEEDS_RESET and flush requests fail with
"virtio pmem device needs a rese... | On Fri, Jan 30, 2026 at 02:52:12PM -0600, Ira Weiny wrote:
Do you, from code review, agree with the logic that
it's racy right now?
Whether the bug is reproducible isn't really the question. | {
"author": "\"Michael S. Tsirkin\" <mst@redhat.com>",
"date": "Sat, 31 Jan 2026 12:47:15 -0500",
"thread_id": "6980dc5569d5a_3430210092@iweiny-mobl.notmuch.mbox.gz"
} |
lkml | [PATCH] nvdimm: virtio_pmem: serialize flush requests | Under heavy concurrent flush traffic, virtio-pmem can overflow its request
virtqueue (req_vq): virtqueue_add_sgs() starts returning -ENOSPC and the
driver logs "no free slots in the virtqueue". Shortly after that the
device enters VIRTIO_CONFIG_S_NEEDS_RESET and flush requests fail with
"virtio pmem device needs a rese... | Hi Ira,
On Sat, 31 Jan 2026 04:52:12 +0800,
Ira Weiny wrote:
Thanks for taking a look.
I can reproduce the issue here, but it is timing dependent. A single fio run
does not always hit it, so I suspect that's why you're not seeing the dmesg
messages.
Environment:
QEMU: 10.1.2
virtio-pmem backend: memory-backend-ram ... | {
"author": "Li Chen <me@linux.beauty>",
"date": "Sun, 01 Feb 2026 12:21:42 +0800",
"thread_id": "6980dc5569d5a_3430210092@iweiny-mobl.notmuch.mbox.gz"
} |
lkml | [PATCH] nvdimm: virtio_pmem: serialize flush requests | Under heavy concurrent flush traffic, virtio-pmem can overflow its request
virtqueue (req_vq): virtqueue_add_sgs() starts returning -ENOSPC and the
driver logs "no free slots in the virtqueue". Shortly after that the
device enters VIRTIO_CONFIG_S_NEEDS_RESET and flush requests fail with
"virtio pmem device needs a rese... | Hi Michael,
On Sun, 01 Feb 2026 01:46:19 +0800,
Michael S. Tsirkin wrote:
Good point. mutex_lock() already does might_sleep(), so the explicit
might_sleep() next to the lock is redundant.
I'll drop it in v2 (which also switches to guard(mutex) as Ira suggested).
Regards,
Li | {
"author": "Li Chen <me@linux.beauty>",
"date": "Sun, 01 Feb 2026 12:40:15 +0800",
"thread_id": "6980dc5569d5a_3430210092@iweiny-mobl.notmuch.mbox.gz"
} |
lkml | [PATCH] nvdimm: virtio_pmem: serialize flush requests | Under heavy concurrent flush traffic, virtio-pmem can overflow its request
virtqueue (req_vq): virtqueue_add_sgs() starts returning -ENOSPC and the
driver logs "no free slots in the virtqueue". Shortly after that the
device enters VIRTIO_CONFIG_S_NEEDS_RESET and flush requests fail with
"virtio pmem device needs a rese... | Michael S. Tsirkin wrote:
[snip]
I do now. I was hoping to understand the test being run. The additional
detail that it takes multiple runs helps.
True. But we should still use guard(). I'll look for v2.
Ira | {
"author": "Ira Weiny <ira.weiny@intel.com>",
"date": "Mon, 2 Feb 2026 11:18:13 -0600",
"thread_id": "6980dc5569d5a_3430210092@iweiny-mobl.notmuch.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | Simplify the mcasp_set_clk_pdir caller convention in start/stop stream
function, to make it so that set_clk_pdir gets called regardless when
stream starts and also disables when stream ends.
Functionality-wise, everything remains the same as the previously skipped
calls are now either correctly configured
(when McASP ... | {
"author": "Sen Wang <sen@ti.com>",
"date": "Thu, 29 Jan 2026 23:10:43 -0600",
"thread_id": "20260130051045.1898892-1-sen@ti.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | The current mcasp_is_synchronous() function does more than what it
proclaims, it also checks if McASP is a frame producer.
Therefore split the original function into two separate ones and
replace all occurrences with the new equivalent logic. So the functions
can be re-used when checking async/sync status in light of ... | {
"author": "Sen Wang <sen@ti.com>",
"date": "Thu, 29 Jan 2026 23:10:42 -0600",
"thread_id": "20260130051045.1898892-1-sen@ti.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | McASP supports the independent configuration of TX & RX clk and frame
sync registers. By default, the driver is configured in synchronous mode
where RX clock generator is disabled and it uses transmit clock signals as
bit clock and frame sync. Therefore add optional properties needed for
asynchronous mode.
Add ti,asyn... | {
"author": "Sen Wang <sen@ti.com>",
"date": "Thu, 29 Jan 2026 23:10:41 -0600",
"thread_id": "20260130051045.1898892-1-sen@ti.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | McASP has dedicated clock & frame sync registers for both transmit
and receive. Currently McASP driver only supports synchronous behavior and
couples both TX & RX settings.
Add logic that enables asynchronous mode via ti,async-mode property. In
async mode, playback & record can be done simultaneously with different
au... | {
"author": "Sen Wang <sen@ti.com>",
"date": "Thu, 29 Jan 2026 23:10:44 -0600",
"thread_id": "20260130051045.1898892-1-sen@ti.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | On Thu, Jan 29, 2026 at 11:10:41PM -0600, Sen Wang wrote:
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resembl... | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Mon, 2 Feb 2026 12:44:32 +0000",
"thread_id": "20260130051045.1898892-1-sen@ti.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | On 30/01/2026 07:10, Sen Wang wrote:
True, the naming was not too precise. It is tasked to decide if the TX
clock needs to be enabled for RX operation, which precisely when McASP
is in synchronous mode _and_ it is clock provider.
Acked-by: Peter Ujfalusi <peter.ujfalusi@gmail.com>
davinci_mcasp *mcasp, u32 ctl_reg,... | {
"author": "=?UTF-8?Q?P=C3=A9ter_Ujfalusi?= <peter.ujfalusi@gmail.com>",
"date": "Mon, 2 Feb 2026 18:42:20 +0200",
"thread_id": "20260130051045.1898892-1-sen@ti.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | On 30/01/2026 07:10, Sen Wang wrote:
I'm not sure about this, but the sequence should be preserved, PDIR
change first.
--
Péter | {
"author": "=?UTF-8?Q?P=C3=A9ter_Ujfalusi?= <peter.ujfalusi@gmail.com>",
"date": "Mon, 2 Feb 2026 18:49:40 +0200",
"thread_id": "20260130051045.1898892-1-sen@ti.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | On 30/01/2026 07:10, Sen Wang wrote:
static void mcasp_start_rx(struct davinci_mcasp *mcasp)
In new code - while it might not match with old code - use producer
instead of master.
Otherwise it looks nice, I trust you have tested the sync and DIT mode.
With this nitpick addressed:
Acked-by: Peter Ujfalusi <peter.u... | {
"author": "=?UTF-8?Q?P=C3=A9ter_Ujfalusi?= <peter.ujfalusi@gmail.com>",
"date": "Mon, 2 Feb 2026 19:02:31 +0200",
"thread_id": "20260130051045.1898892-1-sen@ti.com.mbox.gz"
} |
lkml | [PATCH V1] nvme-pci: Fix NULL pointer dereference in nvme_pci_prp_iter_next | Fix a NULL pointer dereference that occurs in nvme_pci_prp_iter_next()
when SWIOTLB bounce buffering becomes active during runtime.
The issue occurs when SWIOTLB activation changes the device's DMA
mapping requirements at runtime, creating a mismatch between
iod->dma_vecs allocation and access logic.
The problem mani... | On Mon, Feb 02, 2026 at 06:27:38PM +0530, Pradeep P V K wrote:
I think this patch just papers over the bug. If dma_need_unmap
can't be trusted before the dma_map_* call, we've not saved
the unmap information and the unmap won't work properly.
So we'll need to extend the core code to tell if a mapping
will set dma_sk... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 2 Feb 2026 15:35:48 +0100",
"thread_id": "5a3f03e8-89bc-4b46-b125-e08f8297647f@arm.com.mbox.gz"
} |
lkml | [PATCH V1] nvme-pci: Fix NULL pointer dereference in nvme_pci_prp_iter_next | Fix a NULL pointer dereference that occurs in nvme_pci_prp_iter_next()
when SWIOTLB bounce buffering becomes active during runtime.
The issue occurs when SWIOTLB activation changes the device's DMA
mapping requirements at runtime, creating a mismatch between
iod->dma_vecs allocation and access logic.
The problem mani... | On 2026-02-02 2:35 pm, Christoph Hellwig wrote:
The dma_need_unmap() kerneldoc says:
"This function must be called after all mappings that might
need to be unmapped have been performed."
Trying to infer anything from it beforehand is definitely a bug in the
caller.
I don't see that being possible - at best we c... | {
"author": "Robin Murphy <robin.murphy@arm.com>",
"date": "Mon, 2 Feb 2026 15:16:50 +0000",
"thread_id": "5a3f03e8-89bc-4b46-b125-e08f8297647f@arm.com.mbox.gz"
} |
lkml | [PATCH V1] nvme-pci: Fix NULL pointer dereference in nvme_pci_prp_iter_next | Fix a NULL pointer dereference that occurs in nvme_pci_prp_iter_next()
when SWIOTLB bounce buffering becomes active during runtime.
The issue occurs when SWIOTLB activation changes the device's DMA
mapping requirements at runtime, creating a mismatch between
iod->dma_vecs allocation and access logic.
The problem mani... | On Mon, Feb 02, 2026 at 03:35:48PM +0100, Christoph Hellwig wrote:
Agree
There are two paths that lead to SWIOTLB in dma_direct_map_phys().
The first is is_swiotlb_force_bounce(dev), which dma_need_unmap() can
easily evaluate. The second is more problematic, as it depends on
dma_addr and size, neither of which... | {
"author": "Leon Romanovsky <leon@kernel.org>",
"date": "Mon, 2 Feb 2026 17:22:52 +0200",
"thread_id": "5a3f03e8-89bc-4b46-b125-e08f8297647f@arm.com.mbox.gz"
} |
lkml | [PATCH V1] nvme-pci: Fix NULL pointer dereference in nvme_pci_prp_iter_next | Fix a NULL pointer dereference that occurs in nvme_pci_prp_iter_next()
when SWIOTLB bounce buffering becomes active during runtime.
The issue occurs when SWIOTLB activation changes the device's DMA
mapping requirements at runtime, creating a mismatch between
iod->dma_vecs allocation and access logic.
The problem mani... | On 2026-02-02 3:22 pm, Leon Romanovsky wrote:
This will always be true if a default SWIOTLB buffer exists at all, and
thus pretty much defeat the point of whatever optimisation the caller is
trying to make.
Thanks,
Robin. | {
"author": "Robin Murphy <robin.murphy@arm.com>",
"date": "Mon, 2 Feb 2026 15:26:25 +0000",
"thread_id": "5a3f03e8-89bc-4b46-b125-e08f8297647f@arm.com.mbox.gz"
} |
lkml | [PATCH V1] nvme-pci: Fix NULL pointer dereference in nvme_pci_prp_iter_next | Fix a NULL pointer dereference that occurs in nvme_pci_prp_iter_next()
when SWIOTLB bounce buffering becomes active during runtime.
The issue occurs when SWIOTLB activation changes the device's DMA
mapping requirements at runtime, creating a mismatch between
iod->dma_vecs allocation and access logic.
The problem mani... | On Mon, Feb 02, 2026 at 03:16:50PM +0000, Robin Murphy wrote:
At least for HMM, dma_need_unmap() works as expected. HMM doesn't work
with SWIOTLB.
Thanks | {
"author": "Leon Romanovsky <leon@kernel.org>",
"date": "Mon, 2 Feb 2026 17:58:04 +0200",
"thread_id": "5a3f03e8-89bc-4b46-b125-e08f8297647f@arm.com.mbox.gz"
} |
lkml | [PATCH V1] nvme-pci: Fix NULL pointer dereference in nvme_pci_prp_iter_next | Fix a NULL pointer dereference that occurs in nvme_pci_prp_iter_next()
when SWIOTLB bounce buffering becomes active during runtime.
The issue occurs when SWIOTLB activation changes the device's DMA
mapping requirements at runtime, creating a mismatch between
iod->dma_vecs allocation and access logic.
The problem mani... | On Mon, Feb 02, 2026 at 03:16:50PM +0000, Robin Murphy wrote:
Well that doesn't really make sense. No matter how many mappings the
driver has done, there will always be more. ? | {
"author": "Keith Busch <kbusch@kernel.org>",
"date": "Mon, 2 Feb 2026 10:13:24 -0700",
"thread_id": "5a3f03e8-89bc-4b46-b125-e08f8297647f@arm.com.mbox.gz"
} |
lkml | [PATCH V1] nvme-pci: Fix NULL pointer dereference in nvme_pci_prp_iter_next | Fix a NULL pointer dereference that occurs in nvme_pci_prp_iter_next()
when SWIOTLB bounce buffering becomes active during runtime.
The issue occurs when SWIOTLB activation changes the device's DMA
mapping requirements at runtime, creating a mismatch between
iod->dma_vecs allocation and access logic.
The problem mani... | On Mon, Feb 02, 2026 at 06:27:38PM +0530, Pradeep P V K wrote:
So the return of dma_need_unmap() may change after any call to
dma_map_*? Does it only go from false -> true, and never back to false?
Since we didn't allocate the dma_vecs here, doesn't that mean the
completion side is leaking the mapping? | {
"author": "Keith Busch <kbusch@kernel.org>",
"date": "Mon, 2 Feb 2026 10:18:12 -0700",
"thread_id": "5a3f03e8-89bc-4b46-b125-e08f8297647f@arm.com.mbox.gz"
} |
lkml | [PATCH V1] nvme-pci: Fix NULL pointer dereference in nvme_pci_prp_iter_next | Fix a NULL pointer dereference that occurs in nvme_pci_prp_iter_next()
when SWIOTLB bounce buffering becomes active during runtime.
The issue occurs when SWIOTLB activation changes the device's DMA
mapping requirements at runtime, creating a mismatch between
iod->dma_vecs allocation and access logic.
The problem mani... | On Mon, Feb 02, 2026 at 10:13:24AM -0700, Keith Busch wrote:
Yeah. It's more like if this returns true, all future calls, plus
the previous one (which might have caused this). For that something
like the patch below should work in nvme. Totally untested as I'm
about to head away from the desk and prepare dinner.
... | {
"author": "Christoph Hellwig <hch@lst.de>",
"date": "Mon, 2 Feb 2026 18:36:24 +0100",
"thread_id": "5a3f03e8-89bc-4b46-b125-e08f8297647f@arm.com.mbox.gz"
} |
lkml | [PATCH V1] nvme-pci: Fix NULL pointer dereference in nvme_pci_prp_iter_next | Fix a NULL pointer dereference that occurs in nvme_pci_prp_iter_next()
when SWIOTLB bounce buffering becomes active during runtime.
The issue occurs when SWIOTLB activation changes the device's DMA
mapping requirements at runtime, creating a mismatch between
iod->dma_vecs allocation and access logic.
The problem mani... | On 2026-02-02 5:13 pm, Keith Busch wrote:
But equally the fact that none of the mappings made so far happened to
not need bouncing still doesn't mean that future ones won't. This is not
guaranteed to be a static property of the device, but nor is it really a
property of the *device* at all; it's a property of a set... | {
"author": "Robin Murphy <robin.murphy@arm.com>",
"date": "Mon, 2 Feb 2026 17:39:14 +0000",
"thread_id": "5a3f03e8-89bc-4b46-b125-e08f8297647f@arm.com.mbox.gz"
} |
lkml | [PATCH] drm/panel: boe-th101mb31ig002: Remove use of deprecated mipi_dsi_dcs_nop() | Replace calls to deprecated mipi_dsi_dcs_nop() with
mipi_dsi_dcs_nop_multi(). No intended functional changes.
Signed-off-by: Caio Ishikawa <caio.ishikawa@proton.me>
---
drivers/gpu/drm/panel/panel-boe-th101mb31ig002-28a.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/panel... | Hi,
On Sat, Jan 24, 2026 at 4:51 AM Caio Ishikawa <caio.ishikawa@proton.me> wrote:
Hmmmm, I guess we missed this one call when we moved the rest of the
driver over to the _multi() functions.
While moving this one last call over to _multi() doesn't actually help
at all with code flow / readability (arguably, it makes... | {
"author": "Doug Anderson <dianders@chromium.org>",
"date": "Sat, 24 Jan 2026 15:44:53 -0800",
"thread_id": "CAD=FV=Vd3PbB9h4=n=8ArkMJ8g1VKxpxSk8pLDJ4gDYn1_=4aw@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH] drm/panel: boe-th101mb31ig002: Remove use of deprecated mipi_dsi_dcs_nop() | Replace calls to deprecated mipi_dsi_dcs_nop() with
mipi_dsi_dcs_nop_multi(). No intended functional changes.
Signed-off-by: Caio Ishikawa <caio.ishikawa@proton.me>
---
drivers/gpu/drm/panel/panel-boe-th101mb31ig002-28a.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/panel... | Hi,
On Sat, Jan 24, 2026 at 4:51 AM Caio Ishikawa <caio.ishikawa@proton.me> wrote:
Pushed to drm-misc-next:
[1/1] drm/panel: boe-th101mb31ig002: Remove use of deprecated mipi_dsi_dcs_nop()
commit: 3c55330aac69150a1a4ff20684b41e7f66ad5fe9 | {
"author": "Doug Anderson <dianders@chromium.org>",
"date": "Mon, 2 Feb 2026 08:23:16 -0800",
"thread_id": "CAD=FV=Vd3PbB9h4=n=8ArkMJ8g1VKxpxSk8pLDJ4gDYn1_=4aw@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Modify online_memory_block() to accept the online type through its arg
parameter rather than calling mhp_get_default_online_type() internally.
This prepares for allowing callers to specify explicit online types.
Update the caller in add_memory_resource() to pass the default online
type via a local variable.
No functi... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:34 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Enable dax kmem driver to select how to online the memory rather than
implicitly depending on the system default. This will allow users of
dax to plumb through a preferred auto-online policy for their region.
Refactor and new interface:
Add __add_memory_driver_managed() which accepts an explicit online_type
and expor... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:35 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | There is no way for drivers leveraging dax_kmem to plumb through a
preferred auto-online policy - the system default policy is forced.
Add online_type field to DAX device creation path to allow drivers
to specify an auto-online policy when using the kmem driver.
Current callers initialize online_type to mhp_get_defau... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:36 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Move the pmem region driver logic from region.c into pmem_region.c.
No functional changes.
Signed-off-by: Gregory Price <gourry@gourry.net>
---
drivers/cxl/core/Makefile | 1 +
drivers/cxl/core/core.h | 1 +
drivers/cxl/core/pmem_region.c | 191 +++++++++++++++++++++++++++++++++
drivers/cxl/core/regi... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:38 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Move the CXL DAX region device infrastructure from region.c into a
new dax_region.c file.
No functional changes.
Signed-off-by: Gregory Price <gourry@gourry.net>
---
drivers/cxl/core/Makefile | 1 +
drivers/cxl/core/core.h | 1 +
drivers/cxl/core/dax_region.c | 113 ++++++++++++++++++++++++++++++++++
d... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:39 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Add a new cxl_devdax_region driver that probes CXL regions in device
dax mode and creates dax_region devices. This allows explicit binding to
the device_dax dax driver instead of the kmem driver.
Exports to_cxl_region() to core.h so it can be used by the driver.
Signed-off-by: Gregory Price <gourry@gourry.net>
---
d... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:40 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | CXL regions may wish not to auto-configure their memory as dax kmem,
but the current plumbing defaults all cxl-created dax devices to the
kmem driver. This exposes them to hotplug policy, even if the user
intends to use the memory as a dax device.
Add plumbing to allow CXL drivers to select whether a DAX region shoul... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:37 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Explain the binding process for sysram and daxdev regions which are
explicit about which dax driver to use during region creation.
Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Gregory Price <gourry@gourry.net>
---
.../driver-api/cxl/linux/cxl-driver.rst | 43 +++++++++++++++++++
.../driver-api/cxl/linux/dax... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:42 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | In the current kmem driver binding process, the only way for users
to define hotplug policy is via a build-time option, or by not
onlining memory by default and setting each individual memory block
online after hotplug occurs. We can solve this with a configuration
step between region-probe and dax-probe.
Add the inf... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:41 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Annoyingly, my email client has been truncating my titles:
cxl: explicit DAX driver selection and hotplug policy for CXL regions
~Gregory | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:17:55 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, Jan 29, 2026 at 04:04:33PM -0500, Gregory Price wrote:
Looks like build regression on configs without hotplug
MMOP_ defines and mhp_get_default_online_type() undefined
Will let this version sit for a bit before spinning a v2
~Gregory | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Fri, 30 Jan 2026 12:34:33 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On 1/29/2026 3:04 PM, Gregory Price wrote:
This technically comes up in the devdax_region driver patch first, but I noticed it here
so this is where I'm putting it:
I like the idea here, but the implementation is all off. Firstly, devm_cxl_add_sysram_region()
is never called outside of sysram_region_driver::probe(), ... | {
"author": "\"Cheatham, Benjamin\" <benjamin.cheatham@amd.com>",
"date": "Fri, 30 Jan 2026 15:27:12 -0600",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Fri, Jan 30, 2026 at 03:27:12PM -0600, Cheatham, Benjamin wrote:
I originally tried doing with region0/region_driver, but that design
pattern is also confusing - and it creates differently bad patterns.
echo region0 > decoder0.0/create_ram_region -> creates region0
# Current pattern
echo region > dr... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Fri, 30 Jan 2026 17:12:50 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On 1/30/2026 4:12 PM, Gregory Price wrote:
Ok, that makes sense. I think I just got lost in the sauce while looking at this last
week and this explanation helped a lot.>
I think this was the source of my misunderstanding. I was trying to understand how it
works for auto regions when it's never meant to apply to them... | {
"author": "\"Cheatham, Benjamin\" <benjamin.cheatham@amd.com>",
"date": "Mon, 2 Feb 2026 11:02:37 -0600",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:34 -0500
Gregory Price <gourry@gourry.net> wrote:
Trivial comment inline. I don't really care either way.
Pushing the policy up to the caller and ensuring it's explicitly constant
for all the memory blocks (as opposed to relying on locks) seems sensible to me
even without anything else.
Rev... | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:10:29 +0000",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:35 -0500
Gregory Price <gourry@gourry.net> wrote:
Hi Gregory,
I think maybe I'd have left the export for the first user outside of
memory_hotplug.c. Not particularly important however.
Maybe talk about why a caller of __add_memory_driver_managed() might want
the default? Feels like that's... | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:25:24 +0000",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Mon, Feb 02, 2026 at 11:02:37AM -0600, Cheatham, Benjamin wrote:
Auto regions explicitly use the dax_kmem path (all existing code,
unchanged)- which auto-plugs into dax/hotplug.
I do get what you're saying that everything binds on a region type,
I will look a little closer at this and see if there's something more... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Mon, 2 Feb 2026 12:41:31 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Mon, Feb 02, 2026 at 05:10:29PM +0000, Jonathan Cameron wrote:
ack. will update for next version w/ Ben's notes and the build fix.
Thanks!
~Gregory | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Mon, 2 Feb 2026 12:46:25 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:37 -0500
Gregory Price <gourry@gourry.net> wrote:
LGTM
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com> | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:54:17 +0000",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:38 -0500
Gregory Price <gourry@gourry.net> wrote:
Needs to answer the question: Why?
Minor stuff inline.
Maybe sneak in dropping that trailing comma whilst you are moving it.
...
Bonus line... | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:56:40 +0000",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:39 -0500
Gregory Price <gourry@gourry.net> wrote:
Likewise. Why? | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:57:11 +0000",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Mon, Feb 02, 2026 at 05:25:24PM +0000, Jonathan Cameron wrote:
Less about why they want the default, more about maintaining backward
compatibility.
In the cxl driver, Ben pointed out something that made me realize we can
change `region/bind()` to actually use the new `sysram/bind` path by
just adding a one line `s... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Mon, 2 Feb 2026 13:02:10 -0500",
"thread_id": "aYDhyxjzKtbqFWdM@gourry-fedora-PF4VCD3F.mbox.gz"
} |
lkml | [PATCH v12 0/4] net: dsa: initial support for MaxLinear MxL862xx
switches | This series adds very basic DSA support for the MaxLinear MxL86252
(5x 2500Base-T PHYs) and MxL86282 (8x 2500Base-T PHYs) switches.
In addition to the 2.5G TP ports both switches also come with two
SerDes interfaces which can be used either to connect external PHYs
or SFP cages, or as CPU port when using the switch wit... | Add documentation and an example for MaxLinear MxL86282 and MxL86252
switches.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
---
v12: no changes
v11: no changes
v10: add microcontroller port 0
v9: no changes
v8: no changes
v7: no changes
v6: no changes
v5: no chan... | {
"author": "Daniel Golle <daniel@makrotopia.org>",
"date": "Sun, 1 Feb 2026 02:24:47 +0000",
"thread_id": "aYDoTSySNt7vXazL@makrotopia.org.mbox.gz"
} |
lkml | [PATCH v12 0/4] net: dsa: initial support for MaxLinear MxL862xx
switches | This series adds very basic DSA support for the MaxLinear MxL86252
(5x 2500Base-T PHYs) and MxL86282 (8x 2500Base-T PHYs) switches.
In addition to the 2.5G TP ports both switches also come with two
SerDes interfaces which can be used either to connect external PHYs
or SFP cages, or as CPU port when using the switch wit... | Add proprietary special tag format for the MaxLinear MXL862xx family of
switches. While using the same Ethertype as MaxLinear's GSW1xx switches,
the actual tag format differs significantly, hence we need a dedicated
tag driver for that.
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
---
v12: no changes
v11:
* ar... | {
"author": "Daniel Golle <daniel@makrotopia.org>",
"date": "Sun, 1 Feb 2026 02:24:56 +0000",
"thread_id": "aYDoTSySNt7vXazL@makrotopia.org.mbox.gz"
} |
lkml | [PATCH v12 0/4] net: dsa: initial support for MaxLinear MxL862xx
switches | This series adds very basic DSA support for the MaxLinear MxL86252
(5x 2500Base-T PHYs) and MxL86282 (8x 2500Base-T PHYs) switches.
In addition to the 2.5G TP ports both switches also come with two
SerDes interfaces which can be used either to connect external PHYs
or SFP cages, or as CPU port when using the switch wit... | Add helper inline functions __mdiodev_c45_read() and
__mdiodev_c45_write(), which are the C45 equivalents of the existing
__mdiodev_read() and __mdiodev_write() added by commit e6a45700e7e1
("net: mdio: add unlocked mdiobus and mdiodev bus accessors")
Signed-off-by: Daniel Golle <daniel@makrotopia.org>
---
v12: no cha... | {
"author": "Daniel Golle <daniel@makrotopia.org>",
"date": "Sun, 1 Feb 2026 02:25:03 +0000",
"thread_id": "aYDoTSySNt7vXazL@makrotopia.org.mbox.gz"
} |
lkml | [PATCH v12 0/4] net: dsa: initial support for MaxLinear MxL862xx
switches | This series adds very basic DSA support for the MaxLinear MxL86252
(5x 2500Base-T PHYs) and MxL86282 (8x 2500Base-T PHYs) switches.
In addition to the 2.5G TP ports both switches also come with two
SerDes interfaces which can be used either to connect external PHYs
or SFP cages, or as CPU port when using the switch wit... | Add very basic DSA driver for MaxLinear's MxL862xx switches.
In contrast to previous MaxLinear switches the MxL862xx has a built-in
processor that runs a sophisticated firmware based on Zephyr RTOS.
Interaction between the host and the switch hence is organized using a
software API of that firmware rather than accessi... | {
"author": "Daniel Golle <daniel@makrotopia.org>",
"date": "Sun, 1 Feb 2026 02:25:13 +0000",
"thread_id": "aYDoTSySNt7vXazL@makrotopia.org.mbox.gz"
} |
lkml | [PATCH v12 0/4] net: dsa: initial support for MaxLinear MxL862xx
switches | This series adds very basic DSA support for the MaxLinear MxL86252
(5x 2500Base-T PHYs) and MxL86282 (8x 2500Base-T PHYs) switches.
In addition to the 2.5G TP ports both switches also come with two
SerDes interfaces which can be used either to connect external PHYs
or SFP cages, or as CPU port when using the switch wit... | On Sun, Feb 01, 2026 at 02:25:13AM +0000, Daniel Golle wrote:
I have nothing else to comment except to request you to undo some of the
changes requested by AI review. Sorry I didn't have time to comment on v11.
I'm sorry, I can't accept code that fears its own shadow. Some people,
when they see a defensive NULL chec... | {
"author": "Vladimir Oltean <olteanv@gmail.com>",
"date": "Mon, 2 Feb 2026 12:23:26 +0200",
"thread_id": "aYDoTSySNt7vXazL@makrotopia.org.mbox.gz"
} |
lkml | [PATCH v12 0/4] net: dsa: initial support for MaxLinear MxL862xx
switches | This series adds very basic DSA support for the MaxLinear MxL86252
(5x 2500Base-T PHYs) and MxL86282 (8x 2500Base-T PHYs) switches.
In addition to the 2.5G TP ports both switches also come with two
SerDes interfaces which can be used either to connect external PHYs
or SFP cages, or as CPU port when using the switch wit... | On Sun, Feb 01, 2026 at 02:25:03AM +0000, Daniel Golle wrote:
Sigh, there's too many versions of this patch series. While netdev has
a 24H period, there is also this - note the last sentence. The reason
this exists is to stop this exact problem, where ongoing discussion is
split across multiple different versions of t... | {
"author": "\"Russell King (Oracle)\" <linux@armlinux.org.uk>",
"date": "Mon, 2 Feb 2026 11:08:39 +0000",
"thread_id": "aYDoTSySNt7vXazL@makrotopia.org.mbox.gz"
} |
lkml | [PATCH v12 0/4] net: dsa: initial support for MaxLinear MxL862xx
switches | This series adds very basic DSA support for the MaxLinear MxL86252
(5x 2500Base-T PHYs) and MxL86282 (8x 2500Base-T PHYs) switches.
In addition to the 2.5G TP ports both switches also come with two
SerDes interfaces which can be used either to connect external PHYs
or SFP cages, or as CPU port when using the switch wit... | On Mon, Feb 02, 2026 at 12:23:26PM +0200, Vladimir Oltean wrote:
Now that ports are counted from 0, and 0 being the microcontroller, the
port number no longer matches the PHY ID, so I suppose I got to change
the dt-bindigns as that kinda makes the mdio node mandatory for anything
to work.
Looking at other drivers I ... | {
"author": "Daniel Golle <daniel@makrotopia.org>",
"date": "Mon, 2 Feb 2026 18:09:17 +0000",
"thread_id": "aYDoTSySNt7vXazL@makrotopia.org.mbox.gz"
} |
lkml | [PATCH] [v2] i3c, iio: fix i3c driver dependencies | From: Arnd Bergmann <arnd@arndb.de>
All combined i2c/i3c drivers appear to suffer from the same link
time problem when CONFIG_I3C is set to 'm':
arm-linux-gnueabi-ld: drivers/iio/magnetometer/mmc5633.o: in function `mmc5633_i3c_driver_init':
mmc5633.c:(.init.text+0x30): undefined reference to `i3c_driver_register_wit... | On Mon, Feb 02, 2026 at 05:04:46PM +0100, Arnd Bergmann wrote:
Reviewed-by: Frank Li <Frank.Li@nxp.com> | {
"author": "Frank Li <Frank.li@nxp.com>",
"date": "Mon, 2 Feb 2026 11:37:25 -0500",
"thread_id": "a8f8ee55-3c87-4e9c-a5a9-12929855b86f@roeck-us.net.mbox.gz"
} |
lkml | [PATCH] [v2] i3c, iio: fix i3c driver dependencies | From: Arnd Bergmann <arnd@arndb.de>
All combined i2c/i3c drivers appear to suffer from the same link
time problem when CONFIG_I3C is set to 'm':
arm-linux-gnueabi-ld: drivers/iio/magnetometer/mmc5633.o: in function `mmc5633_i3c_driver_init':
mmc5633.c:(.init.text+0x30): undefined reference to `i3c_driver_register_wit... | On 2/2/26 08:04, Arnd Bergmann wrote:
For hwmon:
Acked-by: Guenter Roeck <linux@roeck-us.net> | {
"author": "Guenter Roeck <linux@roeck-us.net>",
"date": "Mon, 2 Feb 2026 09:50:58 -0800",
"thread_id": "a8f8ee55-3c87-4e9c-a5a9-12929855b86f@roeck-us.net.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Modify online_memory_block() to accept the online type through its arg
parameter rather than calling mhp_get_default_online_type() internally.
This prepares for allowing callers to specify explicit online types.
Update the caller in add_memory_resource() to pass the default online
type via a local variable.
No functi... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:34 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Enable dax kmem driver to select how to online the memory rather than
implicitly depending on the system default. This will allow users of
dax to plumb through a preferred auto-online policy for their region.
Refactor and new interface:
Add __add_memory_driver_managed() which accepts an explicit online_type
and expor... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:35 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | There is no way for drivers leveraging dax_kmem to plumb through a
preferred auto-online policy - the system default policy is forced.
Add online_type field to DAX device creation path to allow drivers
to specify an auto-online policy when using the kmem driver.
Current callers initialize online_type to mhp_get_defau... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:36 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Move the pmem region driver logic from region.c into pmem_region.c.
No functional changes.
Signed-off-by: Gregory Price <gourry@gourry.net>
---
drivers/cxl/core/Makefile | 1 +
drivers/cxl/core/core.h | 1 +
drivers/cxl/core/pmem_region.c | 191 +++++++++++++++++++++++++++++++++
drivers/cxl/core/regi... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:38 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Move the CXL DAX region device infrastructure from region.c into a
new dax_region.c file.
No functional changes.
Signed-off-by: Gregory Price <gourry@gourry.net>
---
drivers/cxl/core/Makefile | 1 +
drivers/cxl/core/core.h | 1 +
drivers/cxl/core/dax_region.c | 113 ++++++++++++++++++++++++++++++++++
d... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:39 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Add a new cxl_devdax_region driver that probes CXL regions in device
dax mode and creates dax_region devices. This allows explicit binding to
the device_dax dax driver instead of the kmem driver.
Exports to_cxl_region() to core.h so it can be used by the driver.
Signed-off-by: Gregory Price <gourry@gourry.net>
---
d... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:40 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | CXL regions may wish not to auto-configure their memory as dax kmem,
but the current plumbing defaults all cxl-created dax devices to the
kmem driver. This exposes them to hotplug policy, even if the user
intends to use the memory as a dax device.
Add plumbing to allow CXL drivers to select whether a DAX region shoul... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:37 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Explain the binding process for sysram and daxdev regions which are
explicit about which dax driver to use during region creation.
Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Gregory Price <gourry@gourry.net>
---
.../driver-api/cxl/linux/cxl-driver.rst | 43 +++++++++++++++++++
.../driver-api/cxl/linux/dax... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:42 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | In the current kmem driver binding process, the only way for users
to define hotplug policy is via a build-time option, or by not
onlining memory by default and setting each individual memory block
online after hotplug occurs. We can solve this with a configuration
step between region-probe and dax-probe.
Add the inf... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:04:41 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | Annoyingly, my email client has been truncating my titles:
cxl: explicit DAX driver selection and hotplug policy for CXL regions
~Gregory | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Thu, 29 Jan 2026 16:17:55 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, Jan 29, 2026 at 04:04:33PM -0500, Gregory Price wrote:
Looks like build regression on configs without hotplug
MMOP_ defines and mhp_get_default_online_type() undefined
Will let this version sit for a bit before spinning a v2
~Gregory | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Fri, 30 Jan 2026 12:34:33 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On 1/29/2026 3:04 PM, Gregory Price wrote:
This technically comes up in the devdax_region driver patch first, but I noticed it here
so this is where I'm putting it:
I like the idea here, but the implementation is all off. Firstly, devm_cxl_add_sysram_region()
is never called outside of sysram_region_driver::probe(), ... | {
"author": "\"Cheatham, Benjamin\" <benjamin.cheatham@amd.com>",
"date": "Fri, 30 Jan 2026 15:27:12 -0600",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Fri, Jan 30, 2026 at 03:27:12PM -0600, Cheatham, Benjamin wrote:
I originally tried doing with region0/region_driver, but that design
pattern is also confusing - and it creates differently bad patterns.
echo region0 > decoder0.0/create_ram_region -> creates region0
# Current pattern
echo region > dr... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Fri, 30 Jan 2026 17:12:50 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On 1/30/2026 4:12 PM, Gregory Price wrote:
Ok, that makes sense. I think I just got lost in the sauce while looking at this last
week and this explanation helped a lot.>
I think this was the source of my misunderstanding. I was trying to understand how it
works for auto regions when it's never meant to apply to them... | {
"author": "\"Cheatham, Benjamin\" <benjamin.cheatham@amd.com>",
"date": "Mon, 2 Feb 2026 11:02:37 -0600",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:34 -0500
Gregory Price <gourry@gourry.net> wrote:
Trivial comment inline. I don't really care either way.
Pushing the policy up to the caller and ensuring it's explicitly constant
for all the memory blocks (as opposed to relying on locks) seems sensible to me
even without anything else.
Rev... | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:10:29 +0000",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:35 -0500
Gregory Price <gourry@gourry.net> wrote:
Hi Gregory,
I think maybe I'd have left the export for the first user outside of
memory_hotplug.c. Not particularly important however.
Maybe talk about why a caller of __add_memory_driver_managed() might want
the default? Feels like that's... | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:25:24 +0000",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Mon, Feb 02, 2026 at 11:02:37AM -0600, Cheatham, Benjamin wrote:
Auto regions explicitly use the dax_kmem path (all existing code,
unchanged)- which auto-plugs into dax/hotplug.
I do get what you're saying that everything binds on a region type,
I will look a little closer at this and see if there's something more... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Mon, 2 Feb 2026 12:41:31 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Mon, Feb 02, 2026 at 05:10:29PM +0000, Jonathan Cameron wrote:
ack. will update for next version w/ Ben's notes and the build fix.
Thanks!
~Gregory | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Mon, 2 Feb 2026 12:46:25 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:37 -0500
Gregory Price <gourry@gourry.net> wrote:
LGTM
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com> | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:54:17 +0000",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:38 -0500
Gregory Price <gourry@gourry.net> wrote:
Needs to answer the question: Why?
Minor stuff inline.
Maybe sneak in dropping that trailing comma whilst you are moving it.
...
Bonus line... | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:56:40 +0000",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Thu, 29 Jan 2026 16:04:39 -0500
Gregory Price <gourry@gourry.net> wrote:
Likewise. Why? | {
"author": "Jonathan Cameron <jonathan.cameron@huawei.com>",
"date": "Mon, 2 Feb 2026 17:57:11 +0000",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH 0/9] cxl: explicit DAX driver selection and hotplug | Currently, CXL regions that create DAX devices have no mechanism to
control select the hotplug online policy for kmem regions at region
creation time. Users must either rely on a build-time default or
manually configure each memory block after hotplug occurs.
Additionally, there is no explicit way to choose between de... | On Mon, Feb 02, 2026 at 05:25:24PM +0000, Jonathan Cameron wrote:
Less about why they want the default, more about maintaining backward
compatibility.
In the cxl driver, Ben pointed out something that made me realize we can
change `region/bind()` to actually use the new `sysram/bind` path by
just adding a one line `s... | {
"author": "Gregory Price <gourry@gourry.net>",
"date": "Mon, 2 Feb 2026 13:02:10 -0500",
"thread_id": "20260202175417.00000abe@huawei.com.mbox.gz"
} |
lkml | [PATCH v5] dmaengine: dw-edma: fix MSI data programming for multi-IRQ case | From: Shenghui Shi <brody.shi@m2semi.com>
When using MSI (not MSI-X) with multiple IRQs, the MSI data value
must be unique per vector to ensure correct interrupt delivery.
Currently, the driver fails to increment the MSI data per vector,
causing interrupts to be misrouted.
Fix this by caching the base MSI data and ad... | On Mon, Feb 02, 2026 at 01:53:44PM +0800, Shi-Shenghui wrote:
Reviewed-by: Frank Li <Frank.Li@nxp.com> | {
"author": "Frank Li <Frank.li@nxp.com>",
"date": "Mon, 2 Feb 2026 11:42:34 -0500",
"thread_id": "aYDT+meppNfX9bD3@lizhi-Precision-Tower-5810.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | Hi Tim,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.18-rc7]
[cannot apply to akpm-mm/mm-everything next-20251124]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base'... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Tue, 25 Nov 2025 15:52:26 +0800",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | Hi Tim,
I tested this on my i.MX93 FRDM (arm64) board and after a bit of
fiddling with the MULT/SHIFT values I got it working. It can be a very
valuable addition.
Some comments follow.
On Mon, Nov 24, 2025 at 10:30:52PM -0700, Tim Bird wrote:
This is... not going to work, IMO, and might lead to breakages in
userspa... | {
"author": "Francesco Valla <francesco@valla.it>",
"date": "Tue, 25 Nov 2025 14:08:40 +0100",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | Hi all,
On Wed, 26 Nov 2025 at 03:24, Francesco Valla <francesco@valla.it> wrote:
I think they are.
Another approach would be to defer the calibration/conversion to
userspace, and make sure the early part stands out.
I.e. when real timekeeping is available, kernel messages are prefixed by
"[%5lu.%06lu]". Early mess... | {
"author": "Geert Uytterhoeven <geert@linux-m68k.org>",
"date": "Wed, 26 Nov 2025 08:38:08 +0100",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | Adding some people from the time subsystem into Cc.
Please, keep them in the loop in the eventual next version of the
patch.
For the new people, please note the discussion has already started,
see
https://lore.kernel.org/r/39b09edb-8998-4ebd-a564-7d594434a981@bird.org
Best Regards,
Petr
On Mon 2025-11-24 22:30:52, T... | {
"author": "Petr Mladek <pmladek@suse.com>",
"date": "Wed, 26 Nov 2025 12:13:41 +0100",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | On Tue 2025-11-25 14:08:40, Francesco Valla wrote:
Honestly, I am not sure if it would break anything. The fact is
that printk() always used monotonic timers. And it is possible
that some userspace depends on it.
I personally thing that non-monotonic time stamps might be confusing
but they should not cause any seriou... | {
"author": "Petr Mladek <pmladek@suse.com>",
"date": "Wed, 26 Nov 2025 13:55:32 +0100",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | I worried about this, but I'm skeptical it's a big deal. Humans might be
a little confused, but it's not difficult to see what's going on just by looking
at the timestamps. If a tool breaks, especially something that's used
in automation, e.g. it's used to report results, or is in some sort of CI
loop where the ... | {
"author": "\"Bird, Tim\" <Tim.Bird@sony.com>",
"date": "Thu, 27 Nov 2025 00:03:32 +0000",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | I thought about this while I was creating this.
It wouldn't require the extra configuration for MULT and SHIFT (which would be nice),
and it would be, as you say, very obvious that this was not a regular timestamp.
This means it could be enabled on a generic kernel (making more likely it could be
enabled by defaul... | {
"author": "\"Bird, Tim\" <Tim.Bird@sony.com>",
"date": "Thu, 27 Nov 2025 00:16:23 +0000",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | Hi Tim,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on v6.18-rc7]
[cannot apply to akpm-mm/mm-everything next-20251127]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base'... | {
"author": "kernel test robot <lkp@intel.com>",
"date": "Thu, 27 Nov 2025 10:13:23 +0100",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.