On Sun, 22 Jun 2025 03:45:49 +0200 Achill Gilgenast wrote:
> Some libc's like musl libc don't provide execinfo.h since it's not part
> of POSIX. In order to fix compilation on musl, only include execinfo.h
> if available (HAVE_BACKTRACE_SUPPORT)
>
> This was discovered with c104c16073b7 ("Kunit
Some libc's like musl libc don't provide execinfo.h since it's not part
of POSIX. In order to fix compilation on musl, only include execinfo.h
if available (HAVE_BACKTRACE_SUPPORT)
This was discovered with c104c16073b7 ("Kunit to check the longest symbol
length")
which starts to include linux/kal
On 6/18/25 11:45 PM, Luca Weiss wrote:
> From: Adam Honse
>
> Add support for the touchkeys on the Samsung Galaxy Note 3 (hlte).
>
> Signed-off-by: Adam Honse
> Signed-off-by: Luca Weiss
> ---
> Changes in v2:
> - Fix schema validation failure, adjust i2c-gpio node name
> - Fix misplaced S-o-b
On Fri, Jun 20, 2025 at 10:46 PM Muhammad Usama Anjum
wrote:
>
> On 6/20/25 8:50 AM, Chen Linxuan wrote:
> > When running `make kselftest`, the following compilation warning was
> > encountered:
> >
> > mount-notify_test.c: In function ‘fanotify_rmdir’:
> > mount-notify_test.c:490:17: warning: ig
On 6/20/25 8:50 AM, Chen Linxuan wrote:
> When running `make kselftest`, the following compilation warning was
> encountered:
>
> mount-notify_test.c: In function ‘fanotify_rmdir’:
> mount-notify_test.c:490:17: warning: ignoring return value of ‘chdir’
> declared with attribute ‘warn_unused_resu
el/git/rcu/linux.git rcu/dev
patch link:
https://lore.kernel.org/r/20250619175335.2905836-1-joelagnelf%40nvidia.com
patch subject: [PATCH v2] refscale: Add tests for local_irq_disable() vs
local_interrupt_disable()
config: x86_64-buildonly-randconfig-004-20250620
(https://download.01.org/0day-
When running `make kselftest`, the following compilation warning was
encountered:
mount-notify_test.c: In function ‘fanotify_rmdir’:
mount-notify_test.c:490:17: warning: ignoring return value of ‘chdir’ declared
with attribute ‘warn_unused_result’ [-Wunused-result]
490 | chdir(
On Thu, Jun 19, 2025 at 5:55 PM Eduard Zingerman wrote:
>
> On Thu, 2025-06-19 at 17:13 -0400, Harishankar Vishwanathan wrote:
> > On Wed, Jun 18, 2025 at 5:22 PM Eduard Zingerman wrote:
> > >
> > > On Tue, 2025-06-17 at 19:17 -0400, Harishankar Vishwanathan wrote:
[...]
> Hm, I see, that's an in
On Thu, 2025-06-19 at 17:13 -0400, Harishankar Vishwanathan wrote:
> On Wed, Jun 18, 2025 at 5:22 PM Eduard Zingerman wrote:
> >
> > On Tue, 2025-06-17 at 19:17 -0400, Harishankar Vishwanathan wrote:
> > > The previous commit improves the precision in scalar(32)_min_max_add,
> > > and scalar(32)_
On Wed, Jun 18, 2025 at 5:22 PM Eduard Zingerman wrote:
>
> On Tue, 2025-06-17 at 19:17 -0400, Harishankar Vishwanathan wrote:
> > The previous commit improves the precision in scalar(32)_min_max_add,
> > and scalar(32)_min_max_sub. The improvement in precision occurs in
> > cases when all outcome
Module aliases are used by userspace to identify the correct module to
load for a detected hardware. The currently supported RPMSG device IDs for
this module include "rpmsg-raw", but the module alias is "rpmsg_chrdev".
Use the helper macro MODULE_DEVICE_TABLE(rpmsg) to export the correct
supported
Add two new refscale test cases to compare the performance of
traditional local_irq_disable()/local_irq_enable() with the newer
local_interrupt_disable()/local_interrupt_enable() APIs.
The local_interrupt_disable()/local_interrupt_enable() APIs are
introduced to provide a Rust-compatible interface
On Fri, 20 Jun 2025 01:13:28 +0900 Masahiro Yamada wrote:
> > IIUC you made the kernel spew nearly 5000 warnings on every W=1 build
> > to "encourage" others to help fix a fairly innocuous problem.
> > I appreciate the work that goes into separating the headers but it's
> > hardly urgent enough to
On Fri, Jun 20, 2025 at 1:01 AM Jakub Kicinski wrote:
>
> On Sun, 1 Jun 2025 22:31:29 +0900 Masahiro Yamada wrote:
> > The problem was described in commit 5b20755b7780 ("init: move THIS_MODULE
> > from to ").
> >
> > To summarize it again here: is included by most C files,
> > even though only
On Sun, 1 Jun 2025 22:31:29 +0900 Masahiro Yamada wrote:
> The problem was described in commit 5b20755b7780 ("init: move THIS_MODULE
> from to ").
>
> To summarize it again here: is included by most C files,
> even though only some of them actually export symbols. This is because
> some headers
On Thu, 19 Jun 2025 10:40:15 +0100,
Ganapatrao Kulkarni wrote:
>
>
> [Sorry for late reply]
>
> On 5/29/2025 5:18 PM, Marc Zyngier wrote:
> > On Thu, 29 May 2025 11:29:58 +0100,
> > Ganapatrao Kulkarni wrote:
> >>
> >>
> >> Hi Eric,
> >>
> >> On 5/28/2025 6:58 PM, Eric Auger wrote:
> >>> Hi
[Sorry for late reply]
On 5/29/2025 5:18 PM, Marc Zyngier wrote:
On Thu, 29 May 2025 11:29:58 +0100,
Ganapatrao Kulkarni wrote:
Hi Eric,
On 5/28/2025 6:58 PM, Eric Auger wrote:
Hi Ganapatrao,
On 5/12/25 12:52 PM, Ganapatrao Kulkarni wrote:
This patch series makes the selftest work with
On Fri, Jun 06, 2025 at 09:55:11AM +0800, Peng Fan (OSS) wrote:
>i.MX95 features a Cortex-M33 core, six Cortex-A55 cores, and
>one Cortex-M7 core. The System Control Management Interface(SCMI)
>firmware runs on the M33 core. The i.MX95 SCMI firmware named System
>Manager(SM) includes vendor extensi
On Fri, May 9, 2025 at 1:30 PM Josh Poimboeuf wrote:
>
> +
> +# Make sure git re-stats the changed files
> +git_refresh() {
> + local patch="$1"
> + local files=()
> +
> + [[ ! -d "$SRC/.git" ]] && return
As a user of git worktrees, my $SRC/.git is a file containing a key:
value
From: Adam Honse
Add support for the touchkeys on the Samsung Galaxy Note 3 (hlte).
Signed-off-by: Adam Honse
Signed-off-by: Luca Weiss
---
Changes in v2:
- Fix schema validation failure, adjust i2c-gpio node name
- Fix misplaced S-o-b (hopefully)
- Link to v1:
https://lore.kernel.org/r/20250
On Tue, 2025-06-17 at 19:17 -0400, Harishankar Vishwanathan wrote:
> The previous commit improves the precision in scalar(32)_min_max_add,
> and scalar(32)_min_max_sub. The improvement in precision occurs in
> cases when all outcomes overflow or underflow, respectively. This
> commit adds selftests
On Sun, 15 Jun 2025 22:35:02 +0200, André Apitzsch wrote:
> This dts adds support for BQ Aquaris X5 Plus (Longcheer L9360) released
> in 2016.
>
> Add a device tree with initial support for:
>
> - GPIO keys
> - NFC
> - SDHCI
> - Status LED
> - Touchscreen
>
> [...]
Applied, thanks!
[1/4] arm
On 18/06/2025 14.26, Petr Pavlu wrote:
> The function move_module() uses the variable t to track how many memory
> types it has allocated and consequently how many should be freed if an
> error occurs.
>
> The variable is initially set to 0 and is updated when a call to
> module_memory_alloc() fai
On 18/06/2025 14.26, Petr Pavlu wrote:
> All error conditions in move_module() set the return value by updating the
> ret variable. Therefore, it is not necessary to the initialize the variable
> when declaring it.
>
> Remove the unnecessary initialization.
>
> Signed-off-by: Petr Pavlu
> Review
With CONFIG_MEM_ALLOC_PROFILING=n, vmlinux and all modules unnecessarily
contain the symbols __start_alloc_tags and __stop_alloc_tags, which define
an empty range. In the case of modules, the presence of these symbols also
forces the linker to create an empty .codetag.alloc_tags section.
Update co
All error conditions in move_module() set the return value by updating the
ret variable. Therefore, it is not necessary to the initialize the variable
when declaring it.
Remove the unnecessary initialization.
Signed-off-by: Petr Pavlu
Reviewed-by: Sami Tolvanen
---
kernel/module/main.c | 3 +--
The function move_module() uses the variable t to track how many memory
types it has allocated and consequently how many should be freed if an
error occurs.
The variable is initially set to 0 and is updated when a call to
module_memory_alloc() fails. However, move_module() can fail for other
reaso
The first patch is an actual fix. The second patch is a minor related
cleanup.
Changes since v1 [1]:
- Initialize t to MOD_MEM_NUM_TYPES in move_module(), instead of assigning
the value later.
- Merge the definitions of the variables i and ret in move_module().
[1]
https://lore.kernel.org/linu
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski :
On Sun, 15 Jun 2025 01:48:12 -0700 you wrote:
> This patch corrects several logging and error message in nettest.c:
> - Corrects function name in log messages "setsockopt" -> "getsockopt".
> - Closes missing parenthes
The previous commit improves the precision in scalar(32)_min_max_add,
and scalar(32)_min_max_sub. The improvement in precision occurs in
cases when all outcomes overflow or underflow, respectively. This
commit adds selftests that exercise those cases.
Co-developed-by: Matan Shachnai
Signed-off-by
On Tue, 10 Jun 2025 21:58:27 -0500, Bjorn Andersson wrote:
>
Applied, thanks!
[1/3] soc: qcom: mdt_loader: Ensure we don't read past the ELF header
commit: 9f9967fed9d066ed3dae9372b45ffa4f6fccfeef
[2/3] soc: qcom: mdt_loader: Rename mdt_phdr_valid()
commit: cd840362b0a7b3da59740c1
On 6/15/25 10:35 PM, André Apitzsch via B4 Relay wrote:
> From: André Apitzsch
>
> Downstream vendor code for reference:
>
> https://git.codelinaro.org/clo/la/kernel/msm-3.10/-/blob/LA.BR.1.3.7.c26/arch/arm/boot/dts/qcom/msm8976-pinctrl.dtsi#L223-263
>
> Signed-off-by: André Apitzsch
> ---
>
On Tue, Jun 17, 2025 at 2:18 AM wrote:
>
> From: "Dr. David Alan Gilbert"
>
> Hi,
> The following pair of patches remove a bunch of small functions
> that have been unused for a long time.
>
Acked-by: Eugenio Pérez
Thanks!
On Tue, Jun 17, 2025 at 01:18:37AM +0100, li...@treblig.org wrote:
> From: "Dr. David Alan Gilbert"
>
> The functions:
> vringh_abandon_kern()
> vringh_abandon_user()
> vringh_iov_pull_kern() and
> vringh_iov_push_kern()
> were all added in 2013 by
> commit f87d0fbb5798 ("vringh: host-sid
Hi Daniel,
On Mon, Jun 16, 2025 at 04:07:02PM +0300, Daniel Baluta wrote:
>On Fri, Jun 6, 2025 at 4:57???AM Peng Fan (OSS) wrote:
>>
>> From: Peng Fan
>>
>> i.MX95 has a System Manager(SM) core runs the System Control Management
>> Interface(SCMI) firmware. Vendor extenions are implemented in th
From: "Dr. David Alan Gilbert"
The functions:
vringh_abandon_iotlb()
vringh_notify_disable_iotlb() and
vringh_notify_enable_iotlb()
were added in 2020 by
commit 9ad9c49cfe97 ("vringh: IOTLB support")
but have remained unused.
Remove them.
Signed-off-by: Dr. David Alan Gilbert
Reviewed-b
From: "Dr. David Alan Gilbert"
The functions:
vringh_abandon_kern()
vringh_abandon_user()
vringh_iov_pull_kern() and
vringh_iov_push_kern()
were all added in 2013 by
commit f87d0fbb5798 ("vringh: host-side implementation of virtio rings.")
but have remained unused.
Remove them and the tw
From: "Dr. David Alan Gilbert"
Hi,
The following pair of patches remove a bunch of small functions
that have been unused for a long time.
Dave
v2
Remove the xfer_kern() and kern_xfer() helpers that are now
unused. (As spotted by Simon's review)
Dr. David Alan Gilbert (2):
vhost: vringh
On Sun, 15 Jun 2025 22:35:02 +0200, André Apitzsch wrote:
> This dts adds support for BQ Aquaris X5 Plus (Longcheer L9360) released
> in 2016.
>
> Add a device tree with initial support for:
>
> - GPIO keys
> - NFC
> - SDHCI
> - Status LED
> - Touchscreen
>
> Signed-off-by: André Apitzsch
> -
Am Montag, dem 16.06.2025 um 13:46 +0200 schrieb Konrad Dybcio:
> On 6/15/25 10:35 PM, André Apitzsch via B4 Relay wrote:
> > This dts adds support for BQ Aquaris X5 Plus (Longcheer L9360)
> > released
> > in 2016.
> >
> > Add a device tree with initial support for:
> >
> > - GPIO keys
> > - NFC
On Sun, Jun 15, 2025 at 01:48:12AM -0700, Alok Tiwari wrote:
> This patch corrects several logging and error message in nettest.c:
> - Corrects function name in log messages "setsockopt" -> "getsockopt".
> - Closes missing parentheses in "setsockopt(IPV6_FREEBIND)".
> - Replaces misleading error te
On Tue, Jun 10, 2025 at 09:58:28PM -0500, Bjorn Andersson wrote:
> When the MDT loader is used in remoteproc, the ELF header is sanitized
> beforehand, but that's not necessary the case for other clients.
>
> Validate the size of the firmware buffer to ensure that we don't read
> past the end as w
On Fri, Jun 6, 2025 at 4:57 AM Peng Fan (OSS) wrote:
>
> From: Peng Fan
>
> i.MX95 features a Cortex-M33 core, six Cortex-A55 cores, and
> one Cortex-M7 core. The System Control Management Interface(SCMI)
> firmware runs on the M33 core. The i.MX95 SCMI firmware named System
> Manager(SM) include
On Fri, Jun 6, 2025 at 4:57 AM Peng Fan (OSS) wrote:
>
> From: Peng Fan
>
> i.MX95 has a System Manager(SM) core runs the System Control Management
> Interface(SCMI) firmware. Vendor extenions are implemented in the
> firmware, Logical Machine Management(LMM) protocol to manage
> Logical Machines
On 6/15/25 10:35 PM, André Apitzsch via B4 Relay wrote:
> This dts adds support for BQ Aquaris X5 Plus (Longcheer L9360) released
> in 2016.
>
> Add a device tree with initial support for:
>
> - GPIO keys
> - NFC
> - SDHCI
> - Status LED
> - Touchscreen
>
> Signed-off-by: André Apitzsch
> ---
>
On 15/06/2025 22:35, André Apitzsch via B4 Relay wrote:
> From: André Apitzsch
>
> BQ Aquaris X5 Plus (Longcheer L9360) is a smartphone based on MSM8976
> SoC.
>
> Signed-off-by: André Apitzsch
> ---
Reviewed-by: Krzysztof Kozlowski
Best regards,
Krzysztof
From: André Apitzsch
BQ Aquaris X5 Plus (Longcheer L9360) is a smartphone based on MSM8976
SoC.
Signed-off-by: André Apitzsch
---
Documentation/devicetree/bindings/arm/qcom.yaml | 5 +
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml
b/Document
From: André Apitzsch
Downstream vendor code for reference:
https://git.codelinaro.org/clo/la/kernel/msm-3.10/-/blob/LA.BR.1.3.7.c26/arch/arm/boot/dts/qcom/msm8976-pinctrl.dtsi#L223-263
Signed-off-by: André Apitzsch
---
arch/arm64/boot/dts/qcom/msm8976.dtsi | 36 +++
This dts adds support for BQ Aquaris X5 Plus (Longcheer L9360) released
in 2016.
Add a device tree with initial support for:
- GPIO keys
- NFC
- SDHCI
- Status LED
- Touchscreen
Signed-off-by: André Apitzsch
---
Changes in v2:
- Add Fixes and R-b tag
- Move sdc2 GPIO definitions into msm8976.dt
From: André Apitzsch
This dts adds support for BQ Aquaris X5 Plus (Longcheer L9360) released
in 2016.
Add a device tree with initial support for:
- GPIO keys
- NFC
- SDHCI
- Status LED
- Touchscreen
Signed-off-by: André Apitzsch
---
arch/arm64/boot/dts/qcom/Makefile | 1 +
From: André Apitzsch
The blsp_dma controller is shared between the different subsystems,
which is why it is already initialized by the firmware. We should not
reinitialize it from Linux to avoid potential other users of the DMA
engine to misbehave.
In mainline this can be described using the "qc
On Sun, Jun 15, 2025 at 9:21 AM lirongqing wrote:
>
> From: Li RongQing
>
> Since clear_bit is an atomic operation, the spinlock is redundant and
> can be removed, reducing lock contention is good for performance.
>
> Signed-off-by: Li RongQing
> ---
> Diff with v1: remove unused variable "fpq"
From: Li RongQing
Since clear_bit is an atomic operation, the spinlock is redundant and
can be removed, reducing lock contention is good for performance.
Signed-off-by: Li RongQing
---
Diff with v1: remove unused variable "fpq"
fs/fuse/virtio_fs.c | 3 ---
1 file changed, 3 deletions(-)
diff
This patch corrects several logging and error message in nettest.c:
- Corrects function name in log messages "setsockopt" -> "getsockopt".
- Closes missing parentheses in "setsockopt(IPV6_FREEBIND)".
- Replaces misleading error text ("Invalid port") with the correct
description ("Invalid prefix l
As we always iterate through the entire die_map when expanding
type strings, recursively processing referenced types in
type_expand_child() is not actually necessary. Furthermore,
the type_string kABI rule added in commit c9083467f7b9
("gendwarfksyms: Add a kABI rule to override type strings") can
On 6/13/25 12:18 PM, Mathieu Poirier wrote:
Good day,
On Tue, Jun 10, 2025 at 12:27:38PM -0700, Tanmay Shah wrote:
It's a valid use case to have only one core enabled in cluster in split
mode. Remove exact core count expecatation from the driver.
I suggest:
"When operating in split mode,
Good day,
On Tue, Jun 10, 2025 at 12:27:38PM -0700, Tanmay Shah wrote:
> It's a valid use case to have only one core enabled in cluster in split
> mode. Remove exact core count expecatation from the driver.
I suggest:
"When operating in split mode, it is a valid usecase to have only one core
ena
On 12.06.25 18:10, Lorenzo Stoakes wrote:
On Wed, Jun 11, 2025 at 02:06:53PM +0200, David Hildenbrand wrote:
Marking PMDs that map a "normal" refcounted folios as special is
against our rules documented for vm_normal_page().
Fortunately, there are not that many pmd_special() check that can be
m
On 13.06.25 03:49, Baolin Wang wrote:
When running the khugepaged selftest for shmem (./khugepaged all:shmem),
I encountered the following test failures:
"
Run test: collapse_full (khugepaged:shmem)
Collapse multiple fully populated PTE table Fail
...
Run test: collapse_single_pte_entry (khug
On 13/06/25 7:19 am, Baolin Wang wrote:
When running the khugepaged selftest for shmem (./khugepaged all:shmem),
I encountered the following test failures:
"
Run test: collapse_full (khugepaged:shmem)
Collapse multiple fully populated PTE table Fail
...
Run test: collapse_single_pte_entry (
When running the khugepaged selftest for shmem (./khugepaged all:shmem),
I encountered the following test failures:
"
Run test: collapse_full (khugepaged:shmem)
Collapse multiple fully populated PTE table Fail
...
Run test: collapse_single_pte_entry (khugepaged:shmem)
Collapse PTE table with si
Currently, we only test anonymous memory collapse by default. We should also
add shmem collapse as a default test item to catch issues that could break
the test cases.
Reviewed-by: Dev Jain
Tested-by: Dev Jain
Acked-by: David Hildenbrand
Acked-by: Zi Yan
Signed-off-by: Baolin Wang
---
Changes
On Thu, 29 May 2025 01:42:39 -0700, Alok Tiwari
wrote:
> Corrected "suceess" to "success" in the function documentation
> for clarity.
>
> Signed-off-by: Alok Tiwari
> Acked-by: Jason Wang
Reviewed-by: Xuan Zhuo
> ---
> v1 -> v2
> No changes; only added Acked-by: Jason Wang.
> ---
> drivers
On Fri, May 09, 2025 at 01:16:24PM -0700, Josh Poimboeuf wrote:
> I've tested with a variety of patches on defconfig and Fedora-config
> kernels with both GCC and Clang.
>
> These patches can also be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git
> klp-build-v2
On 6/11/25 7:12 PM, Josh Poimboeuf wrote:
>
> Hm, revert_patch() already has a call to git_refresh(), so there doesn't
> appear to be any point to that extra refresh in revert_patches().
>
> Does this fix?
>
> diff --git a/scripts/livepatch/klp-build b/scripts/livepatch/klp-build
> index 7ec07c4
On Wed, Jun 11, 2025 at 02:06:54PM +0200, David Hildenbrand wrote:
> Marking PUDs that map a "normal" refcounted folios as special is
> against our rules documented for vm_normal_page().
>
> Fortunately, there are not that many pud_special() check that can be
> mislead and are right now rather har
On Wed, Jun 11, 2025 at 02:06:53PM +0200, David Hildenbrand wrote:
> Marking PMDs that map a "normal" refcounted folios as special is
> against our rules documented for vm_normal_page().
>
> Fortunately, there are not that many pmd_special() check that can be
> mislead, and most vm_normal_page_pmd
On Wed, Jun 11, 2025 at 02:06:52PM +0200, David Hildenbrand wrote:
> We setup the cache mode but ... don't forward the updated pgprot to
> insert_pfn_pud().
>
> Only a problem on x86-64 PAT when mapping PFNs using PUDs that
> require a special cachemode.
>
> Fix it by using the proper pgprot wher
On 12.06.25 19:08, Lorenzo Stoakes wrote:
On Thu, Jun 12, 2025 at 07:00:01PM +0200, David Hildenbrand wrote:
On 12.06.25 18:49, Lorenzo Stoakes wrote:
On Wed, Jun 11, 2025 at 02:06:54PM +0200, David Hildenbrand wrote:
Marking PUDs that map a "normal" refcounted folios as special is
against our
On Thu, Jun 12, 2025 at 07:00:01PM +0200, David Hildenbrand wrote:
> On 12.06.25 18:49, Lorenzo Stoakes wrote:
> > On Wed, Jun 11, 2025 at 02:06:54PM +0200, David Hildenbrand wrote:
> > > Marking PUDs that map a "normal" refcounted folios as special is
> > > against our rules documented for vm_norm
On 12.06.25 18:49, Lorenzo Stoakes wrote:
On Wed, Jun 11, 2025 at 02:06:54PM +0200, David Hildenbrand wrote:
Marking PUDs that map a "normal" refcounted folios as special is
against our rules documented for vm_normal_page().
Might be worth referring to specifically which rule. I'm guessing it'
> I spent too much time trying to get the ndctl tests mentioned by Dan
> running (.config tweaks, memmap= setup, ... ), without getting them to
> pass even without these patches. Some SKIP, some FAIL, some sometimes
> suddenly SKIP on first invocation, ... instructions unclear or
On Wed, Jun 11, 2025 at 02:06:54PM +0200, David Hildenbrand wrote:
> Marking PUDs that map a "normal" refcounted folios as special is
> against our rules documented for vm_normal_page().
Might be worth referring to specifically which rule. I'm guessing it's the
general one of special == don't touc
On Thu, Jun 12, 2025 at 06:22:32PM +0200, David Hildenbrand wrote:
> On 12.06.25 18:19, Lorenzo Stoakes wrote:
> > FWIW I did a basic build/mm self tests run locally and all looking good!
>
> Thanks! I have another series based on this series coming up ... but
> struggling to get !CONFIG_ARCH_HAS_P
On 12.06.25 18:19, Lorenzo Stoakes wrote:
FWIW I did a basic build/mm self tests run locally and all looking good!
Thanks! I have another series based on this series coming up ... but
struggling to get !CONFIG_ARCH_HAS_PTE_SPECIAL tested "easily" :)
--
Cheers,
David / dhildenb
FWIW I did a basic build/mm self tests run locally and all looking good!
On Wed, Jun 11, 2025 at 02:06:51PM +0200, David Hildenbrand wrote:
> This is v2 of
> "[PATCH v1 0/2] mm/huge_memory: don't mark refcounted pages special
>in vmf_insert_folio_*()"
> Now with one additional fix, b
On Wed, Jun 11, 2025 at 02:06:53PM +0200, David Hildenbrand wrote:
> Marking PMDs that map a "normal" refcounted folios as special is
> against our rules documented for vm_normal_page().
>
> Fortunately, there are not that many pmd_special() check that can be
> mislead, and most vm_normal_page_pmd(
On Thu, Jun 12, 2025 at 05:36:35PM +0200, David Hildenbrand wrote:
> On 12.06.25 17:28, Lorenzo Stoakes wrote:
> > On Wed, Jun 11, 2025 at 02:06:52PM +0200, David Hildenbrand wrote:
> > > We setup the cache mode but ... don't forward the updated pgprot to
> > > insert_pfn_pud().
> > >
> > > Only a
On 12.06.25 17:59, Lorenzo Stoakes wrote:
On Thu, Jun 12, 2025 at 05:36:35PM +0200, David Hildenbrand wrote:
On 12.06.25 17:28, Lorenzo Stoakes wrote:
On Wed, Jun 11, 2025 at 02:06:52PM +0200, David Hildenbrand wrote:
We setup the cache mode but ... don't forward the updated pgprot to
insert_p
On Wed, Jun 11, 2025 at 02:06:52PM +0200, David Hildenbrand wrote:
> We setup the cache mode but ... don't forward the updated pgprot to
> insert_pfn_pud().
>
> Only a problem on x86-64 PAT when mapping PFNs using PUDs that
> require a special cachemode.
>
> Fix it by using the proper pgprot where
On 12.06.25 17:28, Lorenzo Stoakes wrote:
On Wed, Jun 11, 2025 at 02:06:52PM +0200, David Hildenbrand wrote:
We setup the cache mode but ... don't forward the updated pgprot to
insert_pfn_pud().
Only a problem on x86-64 PAT when mapping PFNs using PUDs that
require a special cachemode.
Fix it
On Wed, Jun 11, 2025 at 05:49:14PM -0400, Joel Fernandes wrote:
>
>
> On 6/11/2025 1:56 PM, Uladzislau Rezki (Sony) wrote:
> > Update the documentation about rcu_normal_wake_from_gp parameter.
> >
> > Signed-off-by: Uladzislau Rezki (Sony)
>
> Reviewed-by: Joel Fernandes
>
Thanks!
--
Uladzi
On Wed, Jun 11, 2025 at 05:48:57PM -0400, Joel Fernandes wrote:
>
>
> On 6/11/2025 1:56 PM, Uladzislau Rezki (Sony) wrote:
> > Automatically enable the rcu_normal_wake_from_gp parameter on
> > systems with a small number of CPUs. The activation threshold
> > is set to 16 CPUs.
> >
> > This helps
On 12.06.25 09:18, David Hildenbrand wrote:
On 12.06.25 06:20, Dan Williams wrote:
Alistair Popple wrote:
On Wed, Jun 11, 2025 at 02:06:51PM +0200, David Hildenbrand wrote:
This is v2 of
"[PATCH v1 0/2] mm/huge_memory: don't mark refcounted pages special
in vmf_insert_folio_*(
On 12.06.25 01:08, Andrew Morton wrote:
On Wed, 11 Jun 2025 14:06:51 +0200 David Hildenbrand wrote:
While working on improving vm_normal_page() and friends, I stumbled
over this issues: refcounted "normal" pages must not be marked
using pmd_special() / pud_special().
Why is this?
The two p
On 12.06.25 06:20, Dan Williams wrote:
Alistair Popple wrote:
On Wed, Jun 11, 2025 at 02:06:51PM +0200, David Hildenbrand wrote:
This is v2 of
"[PATCH v1 0/2] mm/huge_memory: don't mark refcounted pages special
in vmf_insert_folio_*()"
Now with one additional fix, based on mm/m
On 12.06.25 04:17, Alistair Popple wrote:
On Wed, Jun 11, 2025 at 02:06:53PM +0200, David Hildenbrand wrote:
Marking PMDs that map a "normal" refcounted folios as special is
against our rules documented for vm_normal_page().
Fortunately, there are not that many pmd_special() check that can be
m
On 12.06.25 03:56, Alistair Popple wrote:
On Wed, Jun 11, 2025 at 02:06:52PM +0200, David Hildenbrand wrote:
We setup the cache mode but ... don't forward the updated pgprot to
insert_pfn_pud().
Only a problem on x86-64 PAT when mapping PFNs using PUDs that
require a special cachemode.
Fix it
On 12.06.25 06:34, Dan Williams wrote:
David Hildenbrand wrote:
We setup the cache mode but ... don't forward the updated pgprot to
insert_pfn_pud().
Only a problem on x86-64 PAT when mapping PFNs using PUDs that
require a special cachemode.
This is only a problem if the kernel mapped the pud
David Hildenbrand wrote:
> Marking PUDs that map a "normal" refcounted folios as special is
> against our rules documented for vm_normal_page().
>
> Fortunately, there are not that many pud_special() check that can be
> mislead and are right now rather harmless: e.g., none so far
> bases decisions
David Hildenbrand wrote:
> Marking PMDs that map a "normal" refcounted folios as special is
> against our rules documented for vm_normal_page().
>
> Fortunately, there are not that many pmd_special() check that can be
> mislead, and most vm_normal_page_pmd()/vm_normal_folio_pmd() users that
> woul
David Hildenbrand wrote:
> We setup the cache mode but ... don't forward the updated pgprot to
> insert_pfn_pud().
>
> Only a problem on x86-64 PAT when mapping PFNs using PUDs that
> require a special cachemode.
This is only a problem if the kernel mapped the pud in advance of userspace
mapping
Alistair Popple wrote:
> On Wed, Jun 11, 2025 at 02:06:51PM +0200, David Hildenbrand wrote:
> > This is v2 of
> > "[PATCH v1 0/2] mm/huge_memory: don't mark refcounted pages special
> > in vmf_insert_folio_*()"
> > Now with one additional fix, based on mm/mm-unstable.
> >
> > While workin
On Mon, 24 Mar 2025 09:41:00 +0100, Luca Weiss wrote:
> The driver for the SM6350 videocc has been lying around in some branches
> of my git tree for a long time, let's upstream it. It doesn't get any
> better by letting it age!
>
>
Applied, thanks!
[4/4] arm64: dts: qcom: sm6350: Add video c
On Tue, 10 Jun 2025 20:34:51 +0200, Luca Weiss wrote:
> Do some tweaks to the common file for the devices in the 'rhine' family
> of Sony devices, and add a dts for togari.
>
>
Applied, thanks!
[1/4] ARM: dts: qcom: msm8974-sony-xperia-rhine: Enable USB charging
commit: 702639bc50515c97
On Tue, 10 Jun 2025 19:03:48 +0200, Luca Weiss wrote:
> Add an alias for the internal storage so it always becomes mmcblk0 and
> - where applicable - SD card becomes mmcblk1.
>
> This avoids issues with internal storage becoming mmcblk1 unexpectedly
> and aligns this board with other boards that
On Wed, Jun 11, 2025 at 02:06:53PM +0200, David Hildenbrand wrote:
> Marking PMDs that map a "normal" refcounted folios as special is
> against our rules documented for vm_normal_page().
>
> Fortunately, there are not that many pmd_special() check that can be
> mislead, and most vm_normal_page_pmd
On Wed, Jun 11, 2025 at 02:06:51PM +0200, David Hildenbrand wrote:
> This is v2 of
> "[PATCH v1 0/2] mm/huge_memory: don't mark refcounted pages special
>in vmf_insert_folio_*()"
> Now with one additional fix, based on mm/mm-unstable.
>
> While working on improving vm_normal_page() a
On Wed, Jun 11, 2025 at 02:06:52PM +0200, David Hildenbrand wrote:
> We setup the cache mode but ... don't forward the updated pgprot to
> insert_pfn_pud().
>
> Only a problem on x86-64 PAT when mapping PFNs using PUDs that
> require a special cachemode.
>
> Fix it by using the proper pgprot wher
On Wed, Jun 11, 2025 at 05:44:23PM -0400, Joe Lawrence wrote:
> On 5/9/25 4:17 PM, Josh Poimboeuf wrote:
> > +revert_patches() {
> > + local extra_args=("$@")
> > + local patches=("${APPLIED_PATCHES[@]}")
> > +
> > + for (( i=${#patches[@]}-1 ; i>=0 ; i-- )) ; do
> > + revert_patch
1 - 100 of 49904 matches
Mail list logo
