Re: [PATCH v7 3/3] dax/kmem: allow kmem to add memory with memmap_on_memory

Vishal Verma writes: > Large amounts of memory managed by the kmem driver may come in via CXL, > and it is often desirable to have the memmap for this memory on the new > memory itself. > > Enroll kmem-managed memory for memmap_on_memory semantics if the dax > region originates via CXL. For non-C

Re: [PATCH v7 2/3] mm/memory_hotplug: split memmap_on_memory requests across memblocks

Vishal Verma writes: > The MHP_MEMMAP_ON_MEMORY flag for hotplugged memory is restricted to > 'memblock_size' chunks of memory being added. Adding a larger span of > memory precludes memmap_on_memory semantics. > > For users of hotplug such as kmem, large amounts of memory might get > added from

Re: [PATCH v1] lib,kprobes: using try_cmpxchg_local in objpool_push

On 2023/10/30 01:05, Guenter Roeck wrote: On Mon, Oct 23, 2023 at 07:24:52PM +0800, wuqiang.matt wrote: The objpool_push can only happen on local cpu node, so only the local cpu can touch slot->tail and slot->last, which ensures the correctness of using cmpxchg without lock prefix (using try_cmp

[PATCH] eventfs: Save ownership and mode

From ae395d53794e7057c9a756e26865549a6b1a0840 Mon Sep 17 00:00:00 2001 From: "Steven Rostedt (Google)" Now that inodes and dentries are created on the fly, they are also reclaimed on memory pressure. Since the ownership and file mode are saved in the inode, if they are freed, any changes to the o

Re: [PATCH v1] lib,kprobes: using try_cmpxchg_local in objpool_push

On Mon, Oct 23, 2023 at 07:24:52PM +0800, wuqiang.matt wrote: > The objpool_push can only happen on local cpu node, so only the local > cpu can touch slot->tail and slot->last, which ensures the correctness > of using cmpxchg without lock prefix (using try_cmpxchg_local instead > of try_cmpxchg_acq

Re: [PATCH v2] eventfs: Test for ei->is_freed when accessing ei->dentry

On Sun, 29 Oct 2023 12:31:54 +0530 Naresh Kamboju wrote: > Following build errors have been noticed. > > fs/tracefs/event_inode.c:348:1: error: return type defaults to 'int' > [-Werror=implicit-int] > 348 | create_dir_dentry(struct eventfs_inode *pei, struct eventfs_inode *ei, > | ^~

[PATCH 0/2] net: mwifiex: add support for the SD8777 chipset

This series introduces simple modifications to the Marvell mwifiex wireless driver to make it support the SD8777 chipset which can be found in mobile devices using the PXA1908 SoC (the support for which is being upstreamed here [1]), among others, such as samsung,coreprimevelte or samsung,xcover3lt

[PATCH 2/2] net: mwifiex: add support for the SD8777 chipset

Marvell SD8777 is a wireless chipset used for instance in the PXA1908 SoC found for example in the samsung,coreprimevelte smartphone, with which this was tested. The driver seems to be compatible with this chipset so enable this support by adding the necessary information based on the downstream co

[PATCH 1/2] dt-bindings: mwifiex: document use with the SD8777 chipset

Document the corresponding compatible string for the use of this driver with the Marvell SD8777 wireless chipset. Signed-off-by: Karel Balej --- .../devicetree/bindings/net/wireless/marvell-8xxx.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Documentation/devi

Re: [PATCH 1/2] dt-bindings: mwifiex: document use with the SD8777 chipset

On 29/10/2023 12:08, Karel Balej wrote: > Document the corresponding compatible string for the use of this driver > with the Marvell SD8777 wireless chipset. > > Signed-off-by: Karel Balej > --- Acked-by: Krzysztof Kozlowski --- This is an automated instruction, just in case, because many r

Re: [PATCH v2] eventfs: Test for ei->is_freed when accessing ei->dentry

On Sun, 29 Oct 2023 at 02:16, Steven Rostedt wrote: > > From: "Steven Rostedt (Google)" > > The eventfs_inode (ei) is protected by SRCU, but the ei->dentry is not. It > is protected by the eventfs_mutex. Anytime the eventfs_mutex is released, > and access to the ei->dentry needs to be done, it sh