data_type large_stringclasses 3
values | source large_stringclasses 29
values | code large_stringlengths 98 49.4M | filepath large_stringlengths 5 161 ⌀ | message large_stringclasses 234
values | commit large_stringclasses 234
values | subject large_stringclasses 418
values | critique large_stringlengths 101 1.26M ⌀ | metadata dict |
|---|---|---|---|---|---|---|---|---|
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Move calculations of zone limits to a dedicated arch_zone_limits_init()
function.
Later MM core will use this function as an architecture specific callback
during nodes and zones initialization and thus there won't be a need to
call free_area_init() from every archi... | {
"author": "Mike Rapoport <rppt@kernel.org>",
"date": "Sun, 11 Jan 2026 10:20:54 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Move calculations of zone limits to a dedicated arch_zone_limits_init()
function.
Later MM core will use this function as an architecture specific callback
during nodes and zones initialization and thus there won't be a need to
call free_area_init() from every archi... | {
"author": "Mike Rapoport <rppt@kernel.org>",
"date": "Sun, 11 Jan 2026 10:20:55 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Move calculations of zone limits to a dedicated arch_zone_limits_init()
function.
Later MM core will use this function as an architecture specific callback
during nodes and zones initialization and thus there won't be a need to
call free_area_init() from every archi... | {
"author": "Mike Rapoport <rppt@kernel.org>",
"date": "Sun, 11 Jan 2026 10:20:56 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
To initialize node, zone and memory map data structures every architecture
calls free_area_init() during setup_arch() and passes it an array of zone
limits.
Beside code duplication it creates "interesting" ordering cases between
allocation and initialization of huge... | {
"author": "Mike Rapoport <rppt@kernel.org>",
"date": "Sun, 11 Jan 2026 10:20:57 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Every architecture calls sparse_init() during setup_arch() although the
data structures created by sparse_init() are not used until the
initialization of the core MM.
Beside the code duplication, calling sparse_init() from architecture
specific code causes ordering ... | {
"author": "Mike Rapoport <rppt@kernel.org>",
"date": "Sun, 11 Jan 2026 10:20:58 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
All three variants of paging_init() on MIPS are wrappers for
pagetable_init().
Instead of having three identical wrappers, call pagetable_init() directly
from setup_arch() and remove the unnecessary paging_init() functions.
Signed-off-by: Mike Rapoport (Microsoft) ... | {
"author": "Mike Rapoport <rppt@kernel.org>",
"date": "Sun, 11 Jan 2026 10:20:59 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Commit 665eaf313314 ("x86/setup: call hugetlb_bootmem_alloc early")
added an early call to hugetlb_bootmem_alloc() to setup_arch() to allow
HVO style pre-initialization of vmemmap on x86.
With the ordering of hugetlb reservation vs memory map initialization
sorted o... | {
"author": "Mike Rapoport <rppt@kernel.org>",
"date": "Sun, 11 Jan 2026 10:21:00 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Every architecture that supports hugetlb_cma command line parameter
reserves CMA areas for hugetlb during setup_arch().
This obfuscates the ordering of hugetlb CMA initialization with respect to
the rest initialization of the core MM.
Introduce arch_hugetlb_cma_ord... | {
"author": "Mike Rapoport <rppt@kernel.org>",
"date": "Sun, 11 Jan 2026 10:21:01 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
hugetlb_cma_check() was required when the ordering of hugetlb_cma_reserve()
and hugetlb_bootmem_alloc() was architecture depended.
Since hugetlb_cma_reserve() is always called before hugetlb_bootmem_alloc()
there is no need to check whether hugetlb_cma_reserve() was... | {
"author": "Mike Rapoport <rppt@kernel.org>",
"date": "Sun, 11 Jan 2026 10:21:02 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
This reverts commit d58b2498200724e4f8c12d71a5953da03c8c8bdf.
hugetlb_bootmem_alloc() is called only once, no need to check if it was
called already at its entry.
Other checks performed during HVO initialization are also no longer
necessary because sparse_init() th... | {
"author": "Mike Rapoport <rppt@kernel.org>",
"date": "Sun, 11 Jan 2026 10:21:03 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | On Sun, Jan 11, 2026 at 10:20:51AM +0200, Mike Rapoport wrote:
Hi Mike,
...
You move initialization of max_zone_pfns[] to a function, name the
function arch_zone_limits_init(), but leave the initializatio of
max_zone_pfns[] to zeroes outside. Should not it be brought along?
Thanks!
_______________________________... | {
"author": "Alexander Gordeev <agordeev@linux.ibm.com>",
"date": "Mon, 12 Jan 2026 08:02:48 +0100",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | Hi,
On Mon, Jan 12, 2026 at 08:02:48AM +0100, Alexander Gordeev wrote:
The idea is that is the caller responsibility to initialize max_zone_pfns
to zero. After patch 24: "arch, mm: consolidate initialization of
SPARSE memory model" there is a single caller of arch_zone_limits_init()
and having initialization of max_z... | {
"author": "Mike Rapoport <rppt@kernel.org>",
"date": "Mon, 12 Jan 2026 09:34:40 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | On Sun, 11 Jan 2026 10:20:34 +0200 Mike Rapoport <rppt@kernel.org> wrote:
updated, thanks. I'll suppress the ensuing email flood.
Kalle, can you please retest sometime, see if the BeagleBone Black boot
failure was fixed?
Seems we haven't heard back from rmk regarding
https://lkml.kernel.org/r/aVrUDeSkqqY9ZCtS@shel... | {
"author": "Andrew Morton <akpm@linux-foundation.org>",
"date": "Mon, 12 Jan 2026 14:23:23 -0800",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | On 1/13/26 00:23, Andrew Morton wrote:
Hello!
I will test this v3 patch ASAP and reply results here.
Collective sorry for the delay; I have been busy!
BR
Kalle
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-r... | {
"author": "Kalle Niemi <kaleposti@gmail.com>",
"date": "Tue, 13 Jan 2026 08:50:33 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | On 1/13/26 08:50, Kalle Niemi wrote:
Hello!
I tried this patch by cloning
https://git.kernel.org/pub/scm/linux/kernel/git/rppt/linux.git/log/?h=hugetlb-init/v3
Boots succesfully on BeagleBone Black!
BR
Kalle
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
h... | {
"author": "Kalle Niemi <kaleposti@gmail.com>",
"date": "Tue, 13 Jan 2026 10:40:22 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | On 2026-01-11 09:20, Mike Rapoport wrote:
Hi Mike,
Thanks for this nice cleanup series.
This old initialization of max_zone_pfns[ZONE_NORMAL] should also be
removed, right? With that removed it makes the local end_pfn variable
set but unused, so could you please also remove that one?
I know that this whole code b... | {
"author": "Andreas Larsson <andreas@gaisler.com>",
"date": "Tue, 13 Jan 2026 13:28:09 +0100",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | Mike Rapoport <rppt@kernel.org> writes:
This v2 looks good to me.
I have also done a basic bootup testing using Linux PPC CI.
Please feel free to add:
Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
... | {
"author": "Ritesh Harjani (IBM) <ritesh.list@gmail.com>",
"date": "Tue, 13 Jan 2026 17:59:49 +0530",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | Hello:
This series was applied to riscv/linux.git (fixes)
by Andrew Morton <akpm@linux-foundation.org>:
On Sun, 11 Jan 2026 10:20:34 +0200 you wrote:
Here is the summary with links:
- [v3,01/29] alpha: introduce arch_zone_limits_init()
https://git.kernel.org/riscv/c/ba1c86874e25
- [v3,02/29] arc: introduce a... | {
"author": "patchwork-bot+linux-riscv@kernel.org",
"date": "Fri, 20 Feb 2026 04:10:42 +0000",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | Hi everyone,
On Sun, Jan 11, 2026 at 10:20:58AM +0200, Mike Rapoport wrote:
This broke the boot on RISC-V 32-bit (rv32_defconfig) for me.
Specifically if sparse_init() is *not* called before the following callchain,
the kernel dies at that point.
start_kernel()
setup_arch()
apply_boot_alternatives()
_ap... | {
"author": "Thomas =?utf-8?Q?Wei=C3=9Fschuh?= <thomas.weissschuh@linutronix.de>",
"date": "Mon, 23 Feb 2026 14:52:45 +0100",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | Hi Thomas,
On Mon, Feb 23, 2026 at 02:52:45PM +0100, Thomas Weischuh wrote:
Hm, most architectures do alternatives patching much later in the boot,
when much more subsystems (including mm) is already initialized.
Any particular reason riscv does it that early?
Looking at patch_map it's quite clear why movement o... | {
"author": "Mike Rapoport <rppt@kernel.org>",
"date": "Mon, 23 Feb 2026 21:40:59 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | Mike Rapoport <rppt@kernel.org> writes:
Hello Mike,
[ 0.000000][ T0] ------------[ cut here ]------------
[ 0.000000][ T0] WARNING: arch/powerpc/include/asm/io.h:879 at virt_to_phys+0x44/0x1b8, CPU#0: swapper/0
[ 0.000000][ T0] Modules linked in:
[ 0.000000][ T0] CPU: 0 UID: 0 PID: 0 Comm: sw... | {
"author": "Ritesh Harjani (IBM) <ritesh.list@gmail.com>",
"date": "Wed, 25 Feb 2026 09:00:35 +0530",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | Hello Ritesh,
On Wed, Feb 25, 2026 at 09:00:35AM +0530, Ritesh Harjani wrote:
Yes, I agree.
It surely will work for powerpc :)
I checked the definitions of __pa() on other architectures and it seems the
safest and the easiest way to fix this.
Would you send a formal patch?
--
Sincerely yours,
Mike.
_________... | {
"author": "Mike Rapoport <rppt@kernel.org>",
"date": "Wed, 25 Feb 2026 18:25:24 +0200",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | Mike Rapoport <rppt@kernel.org> writes:
Thanks Mike for taking a look at above and confirming. Sure, let me
prepare the patch and send it by tomorrow.
-ritesh
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-r... | {
"author": "Ritesh Harjani (IBM) <ritesh.list@gmail.com>",
"date": "Wed, 25 Feb 2026 23:08:38 +0530",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
Hi,
Order in which early memory reservation for hugetlb happens depends on
architecture, on configuration options and on command line parameters.
Some architectures rely on the core MM to call hugetlb_bootmem_alloc()
while others call it very early to allow pre-all... | null | null | null | [PATCH v3 00/29] arch, mm: consolidate hugetlb early reservation | On 1/11/26 09:20, Mike Rapoport wrote:
I've bisected a problem with virtme-ng testing a NUMA memoryless
node setup (on x86_64) to this patch (commit d49004c5f0c1).
It's executed like this, where node 0 has memory and node 1 only cpus:
vng -vr . -p 8 -m 4G --numa 4G,cpus=0-3 --numa 0,cpus=4-7
This fails to boot due t... | {
"author": "Vlastimil Babka <vbabka@suse.cz>",
"date": "Fri, 27 Feb 2026 16:14:42 +0100",
"is_openbsd": false,
"thread_id": "87seaohgf5.ritesh.list@gmail.com.mbox.gz"
} |
lkml_critique | linux-riscv | UBSAN reported an out of bounds access during registration of the last
two outputs. This out of bounds access occurs because space is only
allocated in the hws array for two PLLs and the four output dividers
that each has, but the defined IDs contain two DLLS and their two
outputs each, which are not supported by the d... | null | null | null | [PATCH v1] clk: microchip: mpfs-ccc: fix out of bounds access during output registration | Hi Conor,
On Tue, Feb 24, 2026 at 09:35:25AM +0000, Conor Dooley wrote:
What happens when / if the DLLs are supported by this driver in the
future? This seems like a trap for the future.
According to include/dt-bindings/clock/microchip,mpfs-clock.h, there are
only 16 clock IDs. Could hws be initialized to have enoug... | {
"author": "Brian Masney <bmasney@redhat.com>",
"date": "Wed, 25 Feb 2026 17:56:53 -0500",
"is_openbsd": false,
"thread_id": "aaBpBYVtt_VhuJws@redhat.com.mbox.gz"
} |
lkml_critique | linux-riscv | UBSAN reported an out of bounds access during registration of the last
two outputs. This out of bounds access occurs because space is only
allocated in the hws array for two PLLs and the four output dividers
that each has, but the defined IDs contain two DLLS and their two
outputs each, which are not supported by the d... | null | null | null | [PATCH v1] clk: microchip: mpfs-ccc: fix out of bounds access during output registration | _______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv | {
"author": "Conor Dooley <conor@kernel.org>",
"date": "Wed, 25 Feb 2026 23:14:47 +0000",
"is_openbsd": false,
"thread_id": "aaBpBYVtt_VhuJws@redhat.com.mbox.gz"
} |
lkml_critique | linux-riscv | UBSAN reported an out of bounds access during registration of the last
two outputs. This out of bounds access occurs because space is only
allocated in the hws array for two PLLs and the four output dividers
that each has, but the defined IDs contain two DLLS and their two
outputs each, which are not supported by the d... | null | null | null | [PATCH v1] clk: microchip: mpfs-ccc: fix out of bounds access during output registration | On Wed, Feb 25, 2026 at 11:24:59PM +0000, Conor Dooley wrote:
That makes sense.
Reviewed-by: Brian Masney <bmasney@redhat.com>
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv | {
"author": "Brian Masney <bmasney@redhat.com>",
"date": "Thu, 26 Feb 2026 10:38:45 -0500",
"is_openbsd": false,
"thread_id": "aaBpBYVtt_VhuJws@redhat.com.mbox.gz"
} |
lkml_critique | linux-riscv | This series is based on the k230 usbphy series[1].
This patch series adds SDHCI support for the Canaan K230 SoC,
which uses Synopsys DWCMSHC SDHCI controllers, include MMC0 and MMC1.
The hardware designs of these two controllers are different.
The MMC0 supports eMMC, while MMC1 only supports SDIO. Detailed
information... | null | null | null | [PATCH v2 0/3] Add SDHCI support for Canaan K230 SoC | Add MMC nodes to K230, including eMMC and SDIO. Enable HS200 eMMC
on the SoM and SDIO high-speed on the board.
Signed-off-by: Jiayu Du <jiayu.riscv@isrc.iscas.ac.cn>
---
.../boot/dts/canaan/k230-canmv-dshanpi.dts | 56 +++++++++++++++++++
.../dts/canaan/k230-canmv-module-dshanpi.dtsi | 7 +++
arch/riscv/boot/dts/... | {
"author": "Jiayu Du <jiayu.riscv@isrc.iscas.ac.cn>",
"date": "Thu, 26 Feb 2026 19:59:23 +0800",
"is_openbsd": false,
"thread_id": "20260226115923.75670-4-jiayu.riscv@isrc.iscas.ac.cn.mbox.gz"
} |
lkml_critique | linux-riscv | This series is based on the k230 usbphy series[1].
This patch series adds SDHCI support for the Canaan K230 SoC,
which uses Synopsys DWCMSHC SDHCI controllers, include MMC0 and MMC1.
The hardware designs of these two controllers are different.
The MMC0 supports eMMC, while MMC1 only supports SDIO. Detailed
information... | null | null | null | [PATCH v2 0/3] Add SDHCI support for Canaan K230 SoC | Add SDHCI controller driver for Canaan k230 SoC. Implement custom
sdhci_ops for set_clock, phy init, init and reset.
Signed-off-by: Jiayu Du <jiayu.riscv@isrc.iscas.ac.cn>
---
drivers/mmc/host/sdhci-of-dwcmshc.c | 288 ++++++++++++++++++++++++++++
1 file changed, 288 insertions(+)
diff --git a/drivers/mmc/host/sdhci... | {
"author": "Jiayu Du <jiayu.riscv@isrc.iscas.ac.cn>",
"date": "Thu, 26 Feb 2026 19:59:22 +0800",
"is_openbsd": false,
"thread_id": "20260226115923.75670-4-jiayu.riscv@isrc.iscas.ac.cn.mbox.gz"
} |
lkml_critique | linux-riscv | This series is based on the k230 usbphy series[1].
This patch series adds SDHCI support for the Canaan K230 SoC,
which uses Synopsys DWCMSHC SDHCI controllers, include MMC0 and MMC1.
The hardware designs of these two controllers are different.
The MMC0 supports eMMC, while MMC1 only supports SDIO. Detailed
information... | null | null | null | [PATCH v2 0/3] Add SDHCI support for Canaan K230 SoC | The Canaan k230 uses the SDHCI from Synopsys. Add compatible strings
to the k230. The k230 has two controllers. MMC0 supports eMMC, while
MMC1 supports SDIO.
Signed-off-by: Jiayu Du <jiayu.riscv@isrc.iscas.ac.cn>
---
.../bindings/mmc/snps,dwcmshc-sdhci.yaml | 29 +++++++++++++++++++
1 file changed, 29 insertions... | {
"author": "Jiayu Du <jiayu.riscv@isrc.iscas.ac.cn>",
"date": "Thu, 26 Feb 2026 19:59:21 +0800",
"is_openbsd": false,
"thread_id": "20260226115923.75670-4-jiayu.riscv@isrc.iscas.ac.cn.mbox.gz"
} |
lkml_critique | linux-riscv | This series is based on the k230 usbphy series[1].
This patch series adds SDHCI support for the Canaan K230 SoC,
which uses Synopsys DWCMSHC SDHCI controllers, include MMC0 and MMC1.
The hardware designs of these two controllers are different.
The MMC0 supports eMMC, while MMC1 only supports SDIO. Detailed
information... | null | null | null | [PATCH v2 0/3] Add SDHCI support for Canaan K230 SoC | _______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv | {
"author": "Conor Dooley <conor@kernel.org>",
"date": "Thu, 26 Feb 2026 18:30:37 +0000",
"is_openbsd": false,
"thread_id": "20260226115923.75670-4-jiayu.riscv@isrc.iscas.ac.cn.mbox.gz"
} |
lkml_critique | linux-riscv | Currently, kvm_arch_vcpu_load() unconditionally restores guest CSRs and
HGATP. However, when a VCPU is loaded back on the same physical CPU,
and no other KVM VCPU has run on this CPU since it was last put,
the hardware CSRs are still valid.
This patch optimizes the vcpu_load path by skipping the expensive CSR
writes ... | null | null | null | [PATCH v5] KVM: riscv: Skip CSR restore if VCPU is reloaded on the same core | On Wed, Feb 25, 2026 at 11:14:02AM +0800, Jinyu Tang wrote:
The most expensive check condition, __this_cpu_read(), should come last
in order to short-circuit it when either of the cheap checks fail.
This write can be skipped by the fast path since kvm_former_vcpu is
already set to vcpu.
Thanks,
drew
______________... | {
"author": "Andrew Jones <andrew.jones@oss.qualcomm.com>",
"date": "Wed, 25 Feb 2026 14:24:26 -0600",
"is_openbsd": false,
"thread_id": "srfopv36p4yeaok6qhew4md6uzo7mq4u75fr2wvxtjyk45lqvj@vuqap6n2szdo.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | iova_to_phys is a performance path for the DMA API and iommufd, implement
it using an unrolled get_user_pages() like function waterfall scheme.
The implementation itself is fairly trivial.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Kha... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:30:03 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | This is used by x86 CPUs and can be used in AMD/VT-d x86 IOMMUs. When a
x86 IOMMU is running SVA the MM will be using this format.
This implementation follows the AMD v2 io-pgtable version.
There is nothing remarkable here, the format can have 4 or 5 levels and
limited support for different page sizes. No contiguous ... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:30:10 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | [Joerg, can you put this and vtd in linux-next please. The vtd series is still
good at v3 thanks]
Currently each of the iommu page table formats duplicates all of the logic
to maintain the page table and perform map/unmap/etc operations. There are
several different versions of the algorithms between all the different
... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:29:58 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | AMD IOMMU v1 is unique in supporting contiguous pages with a variable size
and it can decode the full 64 bit VA space. Unlike other x86 page tables
this explicitly does not do sign extension as part of allowing the entire
64 bit VA space to be supported.
The general design is quite similar to the x86 PAE format, excep... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:30:02 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | The iommufd self test uses an xarray to store the pfns and their orders to
emulate a page table. Slightly modify the amdv1 page table to create a
real page table that has similar properties:
- 2k base granule to simulate something like a 4k page table on a 64K
PAGE_SIZE ARM system
- Contiguous page support for ev... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:30:08 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | This intends to have high coverage of the page table format functions and
the IOMMU implementation itself, exercising the various corner cases.
The kunit tests can be run in the kunit framework, using commands like:
tools/testing/kunit/kunit.py run --build_dir build_kunit_arm64 --arch arm64 --make_options LLVM=-19 --... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:30:13 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | IOMMU HW now supports updating a dirty bit in an entry when a DMA writes
to the entry's VA range. iommufd has a uAPI to read and clear the dirty
bits from the tables.
This is a trivial recursive descent algorithm to read and optionally clear
the dirty bits. The format needs a function to tell if a contiguous entry
is ... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:30:06 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | The existing IOMMU page table implementations duplicate all of the working
algorithms for each format. By using the generic page table API a single C
version of the IOMMU algorithms can be created and re-used for all of the
different formats used in the drivers. The implementation will provide a
single C version of the... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:30:01 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | This intends to have high coverage of the page table format functions, it
uses the IOMMU implementation to create a tree which it then walks through
and directly calls the generic page table functions to test them.
It is a good starting point to test a new format header as it is often
able to find typos and inconsiste... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:30:07 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | unmap_pages removes mappings and any fully contained interior tables from
the given range. This follows the now-standard iommu_domain API definition
where it does not split up larger page sizes into smaller. The caller must
perform unmap only on ranges created by map or it must have somehow
otherwise determined safe cu... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:30:04 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | From: Alejandro Jimenez <alejandro.j.jimenez@oracle.com>
Replace the io_pgtable versions with pt_iommu versions. The v2 page table
uses the x86 implementation that will be eventually shared with VT-d.
This supports the same special features as the original code:
- increase_top for the v1 format to allow scaling from... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:30:11 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | None of this is used anymore, delete it.
Reviewed-by: Alejandro Jimenez <alejandro.j.jimenez@oracle.com>
Reviewed-by: Vasant Hegde <vasant.hegde@amd.com>
Tested-by: Alejandro Jimenez <alejandro.j.jimenez@oracle.com>
Tested-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
-... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:30:12 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | map is slightly complicated because it has to handle a number of special
edge cases:
- Overmapping a previously shared, but now empty, table level with an OA.
Requries validating and freeing the possibly empty tables
- Doing the above across an entire to-be-created contiguous entry
- Installing a new shared table... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:30:05 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | The iommufd self test uses an xarray to store the pfns and their orders to
emulate a page table. Make it act more like a real iommu driver by
replacing the xarray with an iommupt based page table. The new AMDv1 mock
format behaves similarly to the xarray.
Add set_dirty() as a iommu_pt operation to allow the test suite... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:30:09 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | The generic API is intended to be separated from the implementation of
page table algorithms. It contains only accessors for walking and
manipulating the table and helpers that are useful for building an
implementation. Memory management is not in the generic API, but part of
the implementation.
Using a multi-compilat... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 14:29:59 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 11/4/25 10:30 AM, Jason Gunthorpe wrote:
a full
or
the full
--
~Randy
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv | {
"author": "Randy Dunlap <rdunlap@infradead.org>",
"date": "Tue, 4 Nov 2025 10:51:56 -0800",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 11/4/25 10:30 AM, Jason Gunthorpe wrote:
@domain: (as below)
--
~Randy
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv | {
"author": "Randy Dunlap <rdunlap@infradead.org>",
"date": "Tue, 4 Nov 2025 11:02:06 -0800",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 11/4/25 10:30 AM, Jason Gunthorpe wrote:
Just FYI:
I guess that a function with DOMAIN_NS() is going to confuse
scripts/kernel-doc.py.
+#define DOMAIN_NS(op) CONCATENATE(CONCATENATE(pt_iommu_, PTPFX), op)
--
~Randy
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.in... | {
"author": "Randy Dunlap <rdunlap@infradead.org>",
"date": "Tue, 4 Nov 2025 11:13:06 -0800",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Tue, Nov 04, 2025 at 11:13:06AM -0800, Randy Dunlap wrote:
Yeah, I don't think kdoc is pointed at this file. Still need to
document the function though..
Thanks,
Jason
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listin... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 15:17:23 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 11/4/25 11:17 AM, Jason Gunthorpe wrote:
OK, sounds good.
--
~Randy
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv | {
"author": "Randy Dunlap <rdunlap@infradead.org>",
"date": "Tue, 4 Nov 2025 11:19:29 -0800",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Tue, Nov 04, 2025 at 11:02:06AM -0800, Randy Dunlap wrote:
Thanks,
I got this one and the prior one
Jason
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 4 Nov 2025 15:19:47 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | Hi Jason,
On 11/4/25 10:30 AM, Jason Gunthorpe wrote:
See Documentations/doc-guide/sphinx.rst for the usual order
of heading adornments. Section beginning:
* Please stick to this order of heading adornments:
--
~Randy
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infr... | {
"author": "Randy Dunlap <rdunlap@infradead.org>",
"date": "Tue, 4 Nov 2025 15:49:02 -0800",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Tue, Nov 04, 2025 at 02:29:58PM -0400, Jason Gunthorpe wrote:
Applied, thanks Jason. Please send the kdoc fixes which address Randys review
on-top.
Regards,
Joerg
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo... | {
"author": "Joerg Roedel <joro@8bytes.org>",
"date": "Wed, 5 Nov 2025 09:45:07 +0100",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Wed, Nov 05, 2025 at 09:45:07AM +0100, Joerg Roedel wrote:
Will do. Please take the VTD series this cycle also, though maybe it
is easier to let this one sit in -next for a bit first.
Thanks,
Jason
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://list... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Wed, 5 Nov 2025 08:43:18 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Tue, Nov 04, 2025 at 02:30:11PM -0400, Jason Gunthorpe wrote:
Tested-by: Ankit Soni <Ankit.Soni@amd.com>
I am little late, I had tested this patch series in both v1 and v2 page table
modes using multiple benchmark tools (FIO, netperf, etc). The changes work as
expected, and I observed no regressions.
_________... | {
"author": "Ankit Soni <Ankit.Soni@amd.com>",
"date": "Wed, 5 Nov 2025 16:01:53 +0000",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Wed, Nov 05, 2025 at 04:01:53PM +0000, Ankit Soni wrote:
Thanks alot, your testing gives me great confidence!
Jason
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Wed, 5 Nov 2025 12:57:33 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Tue, Nov 04, 2025 at 03:49:02PM -0800, Randy Dunlap wrote:
Okay, I think I got this, it will come in a fixing patch
Thanks,
Jason
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Wed, 5 Nov 2025 14:51:46 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | Hi Alejandro Jimenez,
Greetings!
I used Syzkaller and found that there is WARNING in iommufd_fops_release in linux-next next-20251203.
After bisection and the first bad commit is:
"
789a5913b29c iommu/amd: Use the generic iommu page table
"
All detailed into can be found at:
https://github.com/laifryiee/syzkaller_l... | {
"author": "\"Lai, Yi\" <yi1.lai@linux.intel.com>",
"date": "Fri, 5 Dec 2025 10:40:49 +0800",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Fri, Dec 05, 2025 at 10:40:49AM +0800, Lai, Yi wrote:
This bisect didn't work out, it is close, but the commit is
e93d5945ed5b ("iommufd: Change the selftest to use iommupt instead of xarray")
It is a refcount leak:
@@ -1215,8 +1215,10 @@ static int iommufd_test_md_check_pa(struct iommufd_ucmd *ucmd,
pag... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Fri, 5 Dec 2025 15:46:30 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 12/5/25 2:46 PM, Jason Gunthorpe wrote:
Thank you Jason for debugging this. I was wondering what could be the
possible relation with the AMD changes, since the commit doesn't touch
iommufd/main.c, and the syskaller logs show Intel HW so the AMD driver
code is not involved.
Thank you,
Alejandro
______________... | {
"author": "Alejandro Jimenez <alejandro.j.jimenez@oracle.com>",
"date": "Fri, 5 Dec 2025 15:07:41 -0500",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | Hello:
This series was applied to riscv/linux.git (fixes)
by Joerg Roedel <joerg.roedel@amd.com>:
On Tue, 4 Nov 2025 14:29:58 -0400 you wrote:
Here is the summary with links:
- [v8,01/15] genpt: Generic Page Table base API
https://git.kernel.org/riscv/c/7c5b184db714
- [v8,02/15] genpt: Add Documentation/ fi... | {
"author": "patchwork-bot+linux-riscv@kernel.org",
"date": "Fri, 19 Dec 2025 08:10:05 +0000",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 5/11/25 05:30, Jason Gunthorpe wrote:
[1]
See the comment below.
I am trying this with TEE-IO on AMD SEV and hitting problems. Say, I run a VM with 2MB pages and a passed through secure device. The IOMMU code calculates 2MB page size above and maps the guest memory. Ideally the RMP table ("Reverse Map Table" fr... | {
"author": "Alexey Kardashevskiy <aik@amd.com>",
"date": "Sat, 17 Jan 2026 15:54:52 +1100",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Sat, Jan 17, 2026 at 03:54:52PM +1100, Alexey Kardashevskiy wrote:
My understanding is that if you want to use SEV today you also have to
use the kernel command line parameter to force 4k IOMMU pages?
So, I think your questions are about trying to enhance this to get
larger pages in the IOMMU when possible?
IMH... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Sat, 17 Jan 2026 11:43:47 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 18/1/26 02:43, Jason Gunthorpe wrote:
No, not only 4K. I do not enforce any page size by default so it is "everything but 512G", only when the device is "accepted" - I unmap everything in QEMU, "accept" the device, then map everything again but this time IOMMU uses the (4K|2M) pagemask and takes RMP entry sizes in... | {
"author": "Alexey Kardashevskiy <aik@amd.com>",
"date": "Mon, 19 Jan 2026 12:00:47 +1100",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Mon, Jan 19, 2026 at 12:00:47PM +1100, Alexey Kardashevskiy wrote:
I mean, I'm telling you how things work in upstream right now. If you
want this to work you set the 4k only cmdline option and it
works. None of what you are describing is upstream. Upstream does not
support > 4K IOPTEs if RMP is used.
I mean that... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Mon, 19 Jan 2026 13:37:34 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 20/1/26 04:37, Jason Gunthorpe wrote:
ah, that. Well, even now if you force swiotlb, then IOMMU should be able to use huge pages. But ok, point taken.
Not sure I follow. IOMMU table matches the QEMU page table, it is two tables already and IOMMU cannot just blindly use 2M PTEs if the guest is backed with 4K pages... | {
"author": "Alexey Kardashevskiy <aik@amd.com>",
"date": "Wed, 21 Jan 2026 12:08:19 +1100",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Wed, Jan 21, 2026 at 12:08:19PM +1100, Alexey Kardashevskiy wrote:
That is just because AMD HW can't handle it.
For example if you look at the CPU when the guest S1 page table has a
1G PTE and the KVM S2 has a 2M PTE the CPU doesn't explode, it walks
the S1, walks the S2 and loads a 2M PTE into the TLB.
This issu... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Wed, 21 Jan 2026 13:09:31 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 22/1/26 04:09, Jason Gunthorpe wrote:
Got it. Interestingly the HW actually does that, almost. Say, for >=2MB IO pages it checks if RMP==2MB and puts a 2MB IO TLB entry if RMP==2MB, and for 4KB..1MB IO pages - a 4K IO TLB entry and RMP==4K check. But it does not cross the 2MB boundary in RMP. Uff :-/
on the othe... | {
"author": "Alexey Kardashevskiy <aik@amd.com>",
"date": "Thu, 22 Jan 2026 21:58:04 +1100",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Thu, Jan 22, 2026 at 09:58:04PM +1100, Alexey Kardashevskiy wrote:
Not sure I understand this limitation, how does any aligned size cross
a 2MB boundary?
Sounds like it was thought about, is it a HW bug some cases don't
work?
ARM is pushing a thing where encrypt/decrypt has to work on certain aligned
granual siz... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Thu, 22 Jan 2026 10:12:40 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 23/1/26 01:12, Jason Gunthorpe wrote:
Sorry, probably wrong wording. SNP allows a guest page to be backed by only a 4K or 2M host page, IOMMU always rounds page size down to the nearest 4K or 2M boundary. 4M IO pages can work with 2M RMP but not 4K RMP.
Nah, this is intentional, I just do not understand all conse... | {
"author": "Alexey Kardashevskiy <aik@amd.com>",
"date": "Fri, 23 Jan 2026 12:07:26 +1100",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Fri, Jan 23, 2026 at 12:07:26PM +1100, Alexey Kardashevskiy wrote:
Oh so it doesn't actually check the RMP, it is just rounding down to
two fixed sizes?
On every swiotlb allocation pool chunk, yeah.
Ok, but you say when RMP has 2M pages then this doesn't work?
Yes, some future nested vIOMMU
If guest can't ha... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Fri, 23 Jan 2026 10:14:13 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 24/1/26 01:14, Jason Gunthorpe wrote:
No, it does check RMP.
If the IOMMU page walk ends at a >=2MB page - it will round down to 2MB (to the nearest supported RMP size) and check for 2MB RMP and if that check fails because of the page size - it won't try 4K (even though it could theoretically).
The expectation is... | {
"author": "Alexey Kardashevskiy <aik@amd.com>",
"date": "Tue, 27 Jan 2026 19:08:39 +1100",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Tue, Jan 27, 2026 at 07:08:39PM +1100, Alexey Kardashevskiy wrote:
Seems dynfunctional to me.
Upstream Linux doesn't support that, only SWIOTLB or special DMA
coherent memory can be DMA mapped in CC systems. You can't take a
random page, make it shared and then DMA map it.
Really? So the HW can fix the 4k/2M mi... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Tue, 27 Jan 2026 10:25:12 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 28/1/26 01:25, Jason Gunthorpe wrote:
Well, my test device driver calls dma_alloc_coherent() which does that - alloc + convert 4K.
S2 is controlled by the HV and RMP protects against wrong mapping of the guest physical memory in that S2, RMP is a HW firewall.
The HW translates a DMA handle to a host pfn, and th... | {
"author": "Alexey Kardashevskiy <aik@amd.com>",
"date": "Wed, 28 Jan 2026 12:42:08 +1100",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Wed, Jan 28, 2026 at 12:42:08PM +1100, Alexey Kardashevskiy wrote:
Yes, and there is no reason that can't come from the same allocator as
SWIOTLB and use 2M aligned blocks.
Your explanation doesn't make alot of sense.
If we have a vIOMMU and the guest has a 4K IOPTE in S1 then it goes
S1[4k] -> S2[2M] -- [4k] ... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Wed, 28 Jan 2026 09:32:58 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 29/1/26 00:32, Jason Gunthorpe wrote:
I am rather surprised that even now, with SWIOTLB_FORCE, dma_alloc_coherent chooses not to use SWIOTLB in confidential VM.
Should be 2MB IOTLB.
The host should have made sure S2 and RMP use the same page size.
Yes, the host OS updates both RMP and S2, and the host uses th... | {
"author": "Alexey Kardashevskiy <aik@amd.com>",
"date": "Thu, 29 Jan 2026 11:33:06 +1100",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Thu, Jan 29, 2026 at 11:33:06AM +1100, Alexey Kardashevskiy wrote:
That would be a catastrophic HW bug to take the VM's 4k IOPTE and
expand it to a 2M IOTLB entry.
The HW could have installed a 4K IOTLB like it does above.
It is obviously possible because the CPU TLB is doing this, the S1
case is doing it...
I... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Wed, 28 Jan 2026 21:17:16 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 18/1/26 02:43, Jason Gunthorpe wrote:
I am about to try this approach now. 5) means splitting bigger pages to smaller and I remember you working on that hitless IO PDEs smashing, do you have something to play with? I could not spot anything on github but do not want to reinvent. Thanks,
--
Alexey
__________... | {
"author": "Alexey Kardashevskiy <aik@amd.com>",
"date": "Thu, 26 Feb 2026 10:11:56 +1100",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Thu, Feb 26, 2026 at 10:11:56AM +1100, Alexey Kardashevskiy wrote:
I thought this thread had concluded you needed to use the HW engines
for this and if so then KVM should maintain the IOMMU S2 where it can
synchronize things and access the HW engines?
My draft for cut is here:
https://github.com/jgunthorpe/linux/... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Thu, 26 Feb 2026 11:04:40 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On 27/2/26 02:04, Jason Gunthorpe wrote:
The HW engine has to be used for smashing while DMAing to 2M page being smashed. It is not needed when the insecure->trusted switch happens and IOMMU now needs to match already configured RMP.
I want to explore the idea of using the gmemfd->iommufd notification mechanism for s... | {
"author": "Alexey Kardashevskiy <aik@amd.com>",
"date": "Fri, 27 Feb 2026 12:39:28 +1100",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | Add some general description and pull in the kdoc comments from the source
file to index most of the useful functions.
Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Pasha Tatashin <pasha.tatashin@soleen.com>
Reviewed-by: Samiullah Khawaja <skhawaja@google.com>
Tested-by: Alejandro Jimenez <alejandro.j.ji... | null | null | null | [PATCH v8 02/15] genpt: Add Documentation/ files | On Fri, Feb 27, 2026 at 12:39:28PM +1100, Alexey Kardashevskiy wrote:
Oh? I'm surprised shared->private is different that private->shared..
Regardless, I think if you go this path you have to stick to 4k IOPTEs
and avoid the HW engine. Maybe that is good enough to start.
Equally hard to imagine IOMMU changing the R... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Fri, 27 Feb 2026 09:48:05 -0400",
"is_openbsd": false,
"thread_id": "20260227134805.GJ5933@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | This driver used to use a lot of page table constants from the architecture
code which prevented COMPILE_TEST on other architectures. Now that iommupt
provides all of the constants internally there are only two small bumps
preventing COMPILE_TEST.
- Use the generic functions for the riscv specific phys_to_pfn() and
... | null | null | null | [PATCH v4 6/6] iommu/riscv: Allow RISC_VIOMMU to COMPILE_TEST | In terms of the iommu subystem the SADE/GADE feature "3.4. IOMMU updating
of PTE accessed (A) and dirty (D) updates" is called dirty tracking.
There is no reason to enable HW support for this, and the HW cost
associated with it, unless dirty tracking is actually enabled through
iommufd. It should be a dynamic feature ... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Fri, 27 Feb 2026 11:25:37 -0400",
"is_openbsd": false,
"thread_id": "1-v4-5a9ca1a9b7a5+5f2-iommu_pt_riscv_jgg@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | This driver used to use a lot of page table constants from the architecture
code which prevented COMPILE_TEST on other architectures. Now that iommupt
provides all of the constants internally there are only two small bumps
preventing COMPILE_TEST.
- Use the generic functions for the riscv specific phys_to_pfn() and
... | null | null | null | [PATCH v4 6/6] iommu/riscv: Allow RISC_VIOMMU to COMPILE_TEST | The commit below added MSI related calls to the driver that depends on
GENERIC_MSI_IRQ. It is possible to build RISC-V without this selected.
This is also necessary to make the driver COMPILE_TEST.
Fixes: d5f88acdd6ff ("iommu/riscv: Add support for platform msi")
Tested-by: Vincent Chen <vincent.chen@sifive.com>
Test... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Fri, 27 Feb 2026 11:25:40 -0400",
"is_openbsd": false,
"thread_id": "1-v4-5a9ca1a9b7a5+5f2-iommu_pt_riscv_jgg@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | This driver used to use a lot of page table constants from the architecture
code which prevented COMPILE_TEST on other architectures. Now that iommupt
provides all of the constants internally there are only two small bumps
preventing COMPILE_TEST.
- Use the generic functions for the riscv specific phys_to_pfn() and
... | null | null | null | [PATCH v4 6/6] iommu/riscv: Allow RISC_VIOMMU to COMPILE_TEST | This is a fairly straightforward conversion of the RISC-V iommu driver to
use the now merged generic iommu page table code.
It brings support for SVNAPOT which is a 64K contiguous page. Otherwise it
should not change the behavior.
The series disables SADE as the dirty tracking support is not implemented
in the driver... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Fri, 27 Feb 2026 11:25:35 -0400",
"is_openbsd": false,
"thread_id": "1-v4-5a9ca1a9b7a5+5f2-iommu_pt_riscv_jgg@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | This driver used to use a lot of page table constants from the architecture
code which prevented COMPILE_TEST on other architectures. Now that iommupt
provides all of the constants internally there are only two small bumps
preventing COMPILE_TEST.
- Use the generic functions for the riscv specific phys_to_pfn() and
... | null | null | null | [PATCH v4 6/6] iommu/riscv: Allow RISC_VIOMMU to COMPILE_TEST | This turns on a 64k page size. The "RISC-V IOMMU Architecture
Specification" states:
6.4 IOMMU capabilities
[..]
IOMMU implementations must support the Svnapot standard extension for
NAPOT Translation Contiguity.
So just switch it on unconditionally.
Cc: Xu Lu <luxu.kernel@bytedance.com>
Tested-by: Vincent C... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Fri, 27 Feb 2026 11:25:39 -0400",
"is_openbsd": false,
"thread_id": "1-v4-5a9ca1a9b7a5+5f2-iommu_pt_riscv_jgg@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | This driver used to use a lot of page table constants from the architecture
code which prevented COMPILE_TEST on other architectures. Now that iommupt
provides all of the constants internally there are only two small bumps
preventing COMPILE_TEST.
- Use the generic functions for the riscv specific phys_to_pfn() and
... | null | null | null | [PATCH v4 6/6] iommu/riscv: Allow RISC_VIOMMU to COMPILE_TEST | This is a fairly straightforward conversion of the RISC-V iommu driver to
use the generic iommu page table code.
Invalidation stays as it is now with the driver pretending to implement
simple range based invalidation even though the HW is more like ARM SMMUv3
than AMD where the HW implements a single-PTE based invalid... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Fri, 27 Feb 2026 11:25:38 -0400",
"is_openbsd": false,
"thread_id": "1-v4-5a9ca1a9b7a5+5f2-iommu_pt_riscv_jgg@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | This driver used to use a lot of page table constants from the architecture
code which prevented COMPILE_TEST on other architectures. Now that iommupt
provides all of the constants internally there are only two small bumps
preventing COMPILE_TEST.
- Use the generic functions for the riscv specific phys_to_pfn() and
... | null | null | null | [PATCH v4 6/6] iommu/riscv: Allow RISC_VIOMMU to COMPILE_TEST | The RISC-V format is a fairly simple 5 level page table not unlike the x86
one. It has optional support for a single contiguous page size of 64k (16
x 4k).
The specification describes a 32-bit format, the general code can support
it via a #define but the iommu side implementation has been left off until
a user comes.
... | {
"author": "Jason Gunthorpe <jgg@nvidia.com>",
"date": "Fri, 27 Feb 2026 11:25:36 -0400",
"is_openbsd": false,
"thread_id": "1-v4-5a9ca1a9b7a5+5f2-iommu_pt_riscv_jgg@nvidia.com.mbox.gz"
} |
lkml_critique | linux-riscv | This patchset adds support of hardware breakpoints and watchpoints in RISC-V
architecture. The framework is built on top of perf subsystem and SBI debug
trigger extension.
Currently following features are not supported and are in works:
- Ptrace support
- Single stepping
- Virtualization of debug triggers
The SBI ... | null | null | null | [PATCH v3 0/2] riscv: Introduce support for hardware break/watchpoints | RISC-V hardware breakpoint framework is built on top of perf subsystem
and uses SBI debug trigger extension to
install/uninstall/update/enable/disable hardware triggers as specified
in Sdtrig ISA extension.
Signed-off-by: Himanshu Chauhan <himanshu.chauhan@oss.qualcomm.com>
---
arch/riscv/Kconfig ... | {
"author": "Himanshu Chauhan <himanshu.chauhan@oss.qualcomm.com>",
"date": "Mon, 23 Feb 2026 10:19:17 +0530",
"is_openbsd": false,
"thread_id": "20260223044918.1359983-1-himanshu.chauhan@oss.qualcomm.com.mbox.gz"
} |
lkml_critique | linux-riscv | This patchset adds support of hardware breakpoints and watchpoints in RISC-V
architecture. The framework is built on top of perf subsystem and SBI debug
trigger extension.
Currently following features are not supported and are in works:
- Ptrace support
- Single stepping
- Virtualization of debug triggers
The SBI ... | null | null | null | [PATCH v3 0/2] riscv: Introduce support for hardware break/watchpoints | Add self test for riscv architecture. It uses ptrace to ptrace framework
to set/unset break/watchpoint and uses signals to check triggers.
Signed-off-by: Himanshu Chauhan <himanshu.chauhan@oss.qualcomm.com>
---
tools/testing/selftests/breakpoints/Makefile | 5 +
.../breakpoints/breakpoint_test_riscv.c | 174 ... | {
"author": "Himanshu Chauhan <himanshu.chauhan@oss.qualcomm.com>",
"date": "Mon, 23 Feb 2026 10:19:18 +0530",
"is_openbsd": false,
"thread_id": "20260223044918.1359983-1-himanshu.chauhan@oss.qualcomm.com.mbox.gz"
} |
lkml_critique | linux-riscv | This patchset adds support of hardware breakpoints and watchpoints in RISC-V
architecture. The framework is built on top of perf subsystem and SBI debug
trigger extension.
Currently following features are not supported and are in works:
- Ptrace support
- Single stepping
- Virtualization of debug triggers
The SBI ... | null | null | null | [PATCH v3 0/2] riscv: Introduce support for hardware break/watchpoints | _______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv | {
"author": "Conor Dooley <conor.dooley@microchip.com>",
"date": "Mon, 23 Feb 2026 10:24:20 +0000",
"is_openbsd": false,
"thread_id": "20260223044918.1359983-1-himanshu.chauhan@oss.qualcomm.com.mbox.gz"
} |
lkml_critique | linux-riscv | This patchset adds support of hardware breakpoints and watchpoints in RISC-V
architecture. The framework is built on top of perf subsystem and SBI debug
trigger extension.
Currently following features are not supported and are in works:
- Ptrace support
- Single stepping
- Virtualization of debug triggers
The SBI ... | null | null | null | [PATCH v3 0/2] riscv: Introduce support for hardware break/watchpoints | Hi,
On Mon, Feb 23, 2026 at 3:55 PM Conor Dooley <conor.dooley@microchip.com> wrote:
It's correct that the absence of the extension is not a problem but an
informational message can be helpful.
So, I can use pr_info or pr_info_once for this with proper error code. Ok?
Regards
Himanshu
_____________________________... | {
"author": "Himanshu Chauhan <himanshu.chauhan@oss.qualcomm.com>",
"date": "Tue, 24 Feb 2026 09:30:24 +0530",
"is_openbsd": false,
"thread_id": "20260223044918.1359983-1-himanshu.chauhan@oss.qualcomm.com.mbox.gz"
} |
lkml_critique | linux-riscv | This patchset adds support of hardware breakpoints and watchpoints in RISC-V
architecture. The framework is built on top of perf subsystem and SBI debug
trigger extension.
Currently following features are not supported and are in works:
- Ptrace support
- Single stepping
- Virtualization of debug triggers
The SBI ... | null | null | null | [PATCH v3 0/2] riscv: Introduce support for hardware break/watchpoints | On Tue, Feb 24, 2026 at 1:33 PM Conor Dooley <conor.dooley@microchip.com> wrote:
Accepted.
No. As I mentioned in the cover letter, the ptrace support is not
implemented here. I am actively working on it and these are
implemented in ptrace work.
The test is done using the perf events directly. The second patch in
thi... | {
"author": "Himanshu Chauhan <himanshu.chauhan@oss.qualcomm.com>",
"date": "Wed, 25 Feb 2026 10:33:27 +0530",
"is_openbsd": false,
"thread_id": "20260223044918.1359983-1-himanshu.chauhan@oss.qualcomm.com.mbox.gz"
} |
lkml_critique | linux-riscv | This patchset adds support of hardware breakpoints and watchpoints in RISC-V
architecture. The framework is built on top of perf subsystem and SBI debug
trigger extension.
Currently following features are not supported and are in works:
- Ptrace support
- Single stepping
- Virtualization of debug triggers
The SBI ... | null | null | null | [PATCH v3 0/2] riscv: Introduce support for hardware break/watchpoints | On Wed, Feb 25, 2026 at 2:30 PM Conor Dooley <conor@kernel.org> wrote:
Why? I disagree.
It enables the debug triggers support with perf. Ptrace will build upon it.
Regards
Himanshu
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mail... | {
"author": "Himanshu Chauhan <himanshu.chauhan@oss.qualcomm.com>",
"date": "Thu, 26 Feb 2026 08:17:47 +0530",
"is_openbsd": false,
"thread_id": "20260223044918.1359983-1-himanshu.chauhan@oss.qualcomm.com.mbox.gz"
} |
lkml_critique | linux-riscv | This patchset adds support of hardware breakpoints and watchpoints in RISC-V
architecture. The framework is built on top of perf subsystem and SBI debug
trigger extension.
Currently following features are not supported and are in works:
- Ptrace support
- Single stepping
- Virtualization of debug triggers
The SBI ... | null | null | null | [PATCH v3 0/2] riscv: Introduce support for hardware break/watchpoints | On Wed, Feb 25, 2026 at 2:31 PM Conor Dooley <conor@kernel.org> wrote:
Wow! let's all of us post only large series (covering multiple features)
which are difficult to review instead of making life easier for reviewers
through incremental series which make gradual progress over-time.
FYI, the v1 of this series was pos... | {
"author": "Anup Patel <anup@brainfault.org>",
"date": "Thu, 26 Feb 2026 11:05:14 +0530",
"is_openbsd": false,
"thread_id": "20260223044918.1359983-1-himanshu.chauhan@oss.qualcomm.com.mbox.gz"
} |
lkml_critique | linux-riscv | This patchset adds support of hardware breakpoints and watchpoints in RISC-V
architecture. The framework is built on top of perf subsystem and SBI debug
trigger extension.
Currently following features are not supported and are in works:
- Ptrace support
- Single stepping
- Virtualization of debug triggers
The SBI ... | null | null | null | [PATCH v3 0/2] riscv: Introduce support for hardware break/watchpoints | On Thu, Feb 26, 2026 at 2:14 PM Conor Dooley <conor@kernel.org> wrote:
Well, I disagree with you suggestion of marking this series as RFC.
This series has well defined scope and is based on ratified spec.
A series need not cover all possible features to be a regular
non-RFC patches.
Don't throw your RFC related opini... | {
"author": "Anup Patel <apatel@ventanamicro.com>",
"date": "Thu, 26 Feb 2026 17:10:51 +0530",
"is_openbsd": false,
"thread_id": "20260223044918.1359983-1-himanshu.chauhan@oss.qualcomm.com.mbox.gz"
} |
lkml_critique | linux-riscv | This patchset adds support of hardware breakpoints and watchpoints in RISC-V
architecture. The framework is built on top of perf subsystem and SBI debug
trigger extension.
Currently following features are not supported and are in works:
- Ptrace support
- Single stepping
- Virtualization of debug triggers
The SBI ... | null | null | null | [PATCH v3 0/2] riscv: Introduce support for hardware break/watchpoints | On 26 February 2026 11:40:51 GMT, Anup Patel <apatel@ventanamicro.com> wrote:
It's clearly not pointless when there are unexplained TODOs.
Seeing to-do items is absolutely sufficient grounds to question them, and when the response doesn't clearly explain why they're okay, my thoughts about RFC are reasonable - even if... | {
"author": "Conor Dooley <conor@kernel.org>",
"date": "Thu, 26 Feb 2026 12:35:33 +0000",
"is_openbsd": false,
"thread_id": "20260223044918.1359983-1-himanshu.chauhan@oss.qualcomm.com.mbox.gz"
} |
lkml_critique | linux-riscv | This patchset adds support of hardware breakpoints and watchpoints in RISC-V
architecture. The framework is built on top of perf subsystem and SBI debug
trigger extension.
Currently following features are not supported and are in works:
- Ptrace support
- Single stepping
- Virtualization of debug triggers
The SBI ... | null | null | null | [PATCH v3 0/2] riscv: Introduce support for hardware break/watchpoints | On Thu, Feb 26, 2026 at 6:05 PM Conor Dooley <conor@kernel.org> wrote:
Treating series RFC just because there is some future work to be done
is clearly a pointless opinion of yours.
People across kernel subsystem develop features incrementally as
multiple series.
You started the agression by asking the series to be ... | {
"author": "Anup Patel <anup@brainfault.org>",
"date": "Thu, 26 Feb 2026 18:33:51 +0530",
"is_openbsd": false,
"thread_id": "20260223044918.1359983-1-himanshu.chauhan@oss.qualcomm.com.mbox.gz"
} |
lkml_critique | linux-riscv | Hi,
arm64, riscv and x86 all implement shadow stack support and use a
similar pattern for mapping the user shadow stack (originally cloned
from x86). Extract this common pattern into a shared helper -
vm_mmap_shadow_stack().
Patch 1 introduces vm_mmap_shadow_stack() in mm/util.c, which wraps
do_mmap() with the flags ... | null | null | null | [PATCH 0/5] mm: arch/shstk: Common shadow stack mapping helper and VM_NOHUGEPAGE | arm64, riscv and x86 use a similar pattern for mapping the user shadow
stack (cloned from x86). Extract this into a helper to facilitate code
reuse.
The call to do_mmap() from the new helper uses PROT_READ|PROT_WRITE prot
bits instead of the PROT_READ with an explicit VM_WRITE vm_flag. The
x86 intent was to avoid PROT... | {
"author": "Catalin Marinas <catalin.marinas@arm.com>",
"date": "Tue, 24 Feb 2026 17:57:53 +0000",
"is_openbsd": false,
"thread_id": "20260224175800.2500729-1-catalin.marinas@arm.com.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.