Swapin a THP as a whole isn't desirable in some situations. For
example, for completely random access pattern, swapin a THP in one
piece will inflate the reading greatly. So a sysfs interface:
/sys/kernel/mm/transparent_hugepage/swapin_enabled is added to
configure it. Three options as follow ar
The help of CONFIG_THP_SWAP is updated to reflect the latest progress
of THP (Tranparent Huge Page) swap optimization.
Signed-off-by: "Huang, Ying"
Reviewed-by: Dan Williams
Cc: "Kirill A. Shutemov"
Cc: Andrea Arcangeli
Cc: Michal Hocko
Cc: Johannes Weiner
Cc: Shaohua Li
Cc: Hugh Dickins
C
Original code is only for PMD migration entry, it is revised to
support PMD swap mapping.
Signed-off-by: "Huang, Ying"
Cc: "Kirill A. Shutemov"
Cc: Andrea Arcangeli
Cc: Michal Hocko
Cc: Johannes Weiner
Cc: Shaohua Li
Cc: Hugh Dickins
Cc: Minchan Kim
Cc: Rik van Riel
Cc: Dave Hansen
Cc: N
On Mon, Nov 19, 2018 at 03:19:04PM -0800, Dan Williams wrote:
> [1]: https://lore.kernel.org/patchwork/patch/1009434/#1193941
> [2]: https://lore.kernel.org/patchwork/patch/1009434/#1194540
FWIW, that is not the canonical form to refer to emails. Please use:
https://lkml.kernel.org/r/$msgid
(
This is the final step of the THP swapin support. When reclaiming a
anonymous THP, after allocating the huge swap cluster and add the THP
into swap cache, the PMD page mapping will be changed to the mapping
to the swap space. Previously, the PMD page mapping will be split
before being changed. I
For a PMD swap mapping, zap_huge_pmd() will clear the PMD and call
free_swap_and_cache() to decrease the swap reference count and maybe
free or split the huge swap cluster and the THP in swap cache.
Signed-off-by: "Huang, Ying"
Cc: "Kirill A. Shutemov"
Cc: Andrea Arcangeli
Cc: Michal Hocko
Cc:
During fork, the page table need to be copied from parent to child. A
PMD swap mapping need to be copied too and the swap reference count
need to be increased.
When the huge swap cluster has been split already, we need to split
the PMD swap mapping and fallback to PTE copying.
When swap count co
Previously the huge swap cluster will be split after the THP is
swapout. Now, to support to swapin the THP in one piece, the huge
swap cluster will not be split after the THP is reclaimed. So in
memcg, we need to move the swap account for PMD swap mappings in the
process's page table.
When the p
During mincore(), for PMD swap mapping, swap cache will be looked up.
If the resulting page isn't compound page, the PMD swap mapping will
be split and fallback to PTE swap mapping processing.
Signed-off-by: "Huang, Ying"
Cc: "Kirill A. Shutemov"
Cc: Andrea Arcangeli
Cc: Michal Hocko
Cc: Johan
During MADV_WILLNEED, for a PMD swap mapping, if THP swapin is enabled
for the VMA, the whole swap cluster will be swapin. Otherwise, the
huge swap cluster and the PMD swap mapping will be split and fallback
to PTE swap mapping.
Signed-off-by: "Huang, Ying"
Cc: "Kirill A. Shutemov"
Cc: Andrea A
On Tue, Nov 20, 2018 at 01:16:16PM +1100, Stephen Rothwell wrote:
> Hi Greg,
>
> Today's linux-next merge of the staging tree got a conflict in:
>
> drivers/staging/vboxvideo/vbox_ttm.c
>
> between commits:
>
> a64f784bb14a ("drm/ttm: initialize globals during device init (v2)")
>
> from t
The part of __swap_duplicate() with lock held is separated into a new
function __swap_duplicate_locked(). Because we will add more logic
about the PMD swap mapping into __swap_duplicate() and keep the most
PTE swap mapping related logic in __swap_duplicate_locked().
Just mechanical code refactori
Hi, Andrew, could you help me to check whether the overall design is
reasonable?
Hi, Hugh, Shaohua, Minchan and Rik, could you help me to review the
swap part of the patchset? Especially [02/21], [03/21], [04/21],
[05/21], [06/21], [07/21], [08/21], [09/21], [10/21], [11/21],
[12/21], [20/21], [2
Currently, "the swap entry" in the page tables is used for a number of
things outside of actual swap, like page migration, etc. We support
the THP/PMD "swap entry" for page migration currently and the
functions behind this are tied to page migration's config
option (CONFIG_ARCH_ENABLE_THP_MIGRATIO
A huge PMD need to be split when zap a part of the PMD mapping etc.
If the PMD mapping is a swap mapping, we need to split it too. This
patch implemented the support for this. This is similar as splitting
the PMD page mapping, except we need to decrease the PMD swap mapping
count for the huge swa
When madvise_free() found a PMD swap mapping, if only part of the huge
swap cluster is operated on, the PMD swap mapping will be split and
fallback to PTE swap mapping processing. Otherwise, if all huge swap
cluster is operated on, free_swap_and_cache() will be called to
decrease the PMD swap mapp
During swapoff, for a huge swap cluster, we need to allocate a THP,
read its contents into the THP and unuse the PMD and PTE swap mappings
to it. If failed to allocate a THP, the huge swap cluster will be
split.
During unuse, if it is found that the swap cluster mapped by a PMD
swap mapping is sp
2 new /proc/vmstat fields are added, "thp_swapin" and
"thp_swapin_fallback" to count swapin a THP from swap device in one
piece and fallback to normal page swapin.
Signed-off-by: "Huang, Ying"
Cc: "Kirill A. Shutemov"
Cc: Andrea Arcangeli
Cc: Michal Hocko
Cc: Johannes Weiner
Cc: Shaohua Li
C
When a PMD swap mapping is removed from a huge swap cluster, for
example, unmap a memory range mapped with PMD swap mapping, etc,
free_swap_and_cache() will be called to decrease the reference count
to the huge swap cluster. free_swap_and_cache() may also free or
split the huge swap cluster, and f
With this patch, when page fault handler find a PMD swap mapping, it
will swap in a THP in one piece. This avoids the overhead of
splitting/collapsing before/after the THP swapping. And improves the
swap performance greatly for reduced page fault count etc.
do_huge_pmd_swap_page() is added in th
To support to swapin the THP in one piece, we need to create PMD swap
mapping during swapout, and maintain PMD swap mapping count. This
patch implements the support to increase the PMD swap mapping
count (for swapout, fork, etc.) and set SWAP_HAS_CACHE flag (for
swapin, etc.) for a huge swap clus
When splitting a THP in swap cache or failing to allocate a THP when
swapin a huge swap cluster, the huge swap cluster will be split. In
addition to clear the huge flag of the swap cluster, the PMD swap
mapping count recorded in cluster_count() will be set to 0. But we
will not touch PMD swap map
To swapin a THP in one piece, we need to read a huge swap cluster from
the swap device. This patch revised the __read_swap_cache_async() and
its callers and callees to support this. If __read_swap_cache_async()
find the swap cluster of the specified swap entry is huge, it will try
to allocate a T
Previously, during swapout, all PMD page mapping will be split and
replaced with PTE swap mapping. And when clearing the SWAP_HAS_CACHE
flag for the huge swap cluster in put_swap_page(), the huge swap
cluster will be split. Now, during swapout, the PMD page mappings to
the THP will be changed to
On 20/11/2018 09:47, Anson Huang wrote:
> Hi, Daniel
>
> Best Regards!
> Anson Huang
>
>> -Original Message-
>> From: Daniel Lezcano [mailto:daniel.lezc...@linaro.org]
>> Sent: 2018年11月20日 16:45
>> To: Anson Huang ; rui.zh...@intel.com;
>> edubez...@gmail.com; linux...@vger.kernel.org;
>>
On Tue, Nov 20, 2018 at 01:35:39PM +0530, Naresh Kamboju wrote:
> On Mon, 19 Nov 2018 at 22:01, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 4.19.3 release.
> > There are 205 patches in this series, all will be posted as a response
> > to this one. If a
On Mon, Nov 19, 2018 at 01:11:54PM -0500, Prarit Bhargava wrote:
>
>
> On 11/19/2018 11:28 AM, Greg Kroah-Hartman wrote:
> > 3.18-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Prarit Bhargava
> >
> > [ Upstream commit f69ffc5d
Hi, Daniel
Best Regards!
Anson Huang
> -Original Message-
> From: Daniel Lezcano [mailto:daniel.lezc...@linaro.org]
> Sent: 2018年11月20日 16:45
> To: Anson Huang ; rui.zh...@intel.com;
> edubez...@gmail.com; linux...@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Cc: dl-linux-imx
> Subj
On Mon, Nov 19, 2018 at 10:09 AM Bartosz Golaszewski wrote:
> pt., 16 lis 2018 o 22:43 Linus Walleij napisał(a):
> > __gpio_*
> > I tend to dislike __underscore_notation because I feel it
> > is semantically ambguous. I prefer a proper name, even
> > to the point that I prefer inner_function_foo
On 24/10/2018 08:39, Anson Huang wrote:
> The thermal driver is a standalone driver for monitoring SoC temperature
> by enabling thermal sensor, so it can be enabled even when CONFIG_CPU_FREQ
> is NOT set. So remove the dependency with CPU_THERMAL.
>
> Add CONFIG_CPU_FREQ check for cpu-freq relate
>From 51ab18abe1ad0f8ef0bc88696d956431f3e01f3f Mon Sep 17 00:00:00 2001
From: Leilk Liu
Date: Tue, 20 Nov 2018 16:34:22 +0800
Subject: [PATCH 0/2] add SPI driver support for mt7629
This series are based on 4.20-rc1 and provide two patches to support mt7629 IC.
Leilk Liu (2):
spi: mediatek: Add
this patch add support for mt7629 IC.
Change-Id: Icb8ced408ebd1340fb0340592b91f24740d07e1e
Signed-off-by: Leilk Liu
---
drivers/spi/spi-mt65xx.c |3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/spi/spi-mt65xx.c b/drivers/spi/spi-mt65xx.c
index 9ee1fe9..0cce6f0 100644
--- a/drive
This patch adds a DT binding documentation for the MT7629 soc.
Signed-off-by: Leilk Liu
---
.../devicetree/bindings/spi/spi-mt65xx.txt |1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/spi/spi-mt65xx.txt
b/Documentation/devicetree/bindings/spi/spi-
On Mon, Nov 19, 2018 at 10:11 AM Bartosz Golaszewski wrote:
> pt., 16 lis 2018 o 22:51 Linus Walleij napisał(a):
> > I have some patches starting to move DaVinci over to using only
> > descriptor tables, but that's not somthing we can pull off overnight
> > so I guess we have to go for this solu
From: Bo Yan
The strlcpy function returns the length of source pointer when the
requested size is 0. This behavior is relied upon for sched tracing.
We can't simply return when buf is 0, but we have to protect against the
scenario when buf is 0 and requested size is non-zero, in which case the
st
Le lun. 19 nov. 2018 à 13:20, Linus Walleij a écrit :
>
> On Tue, Nov 13, 2018 at 10:51 AM Benjamin Gaignard
> wrote:
>
> > If a hwspinlock if defined in device tree use it to protect
> > configuration registers.
> >
> > Signed-off-by: Benjamin Gaignard
>
> Patch applied with Alex' ACK.
Thanks
On Mon, Nov 19, 2018 at 9:32 AM Uwe Kleine-König
wrote:
> To sumarize: When the pwm driver probes it is not yet clear if the idle
> state of the output pin is high or low. Even when the pinctrl device has
> an "init" and a "default" pinctrl, it is not yet fixed when its
> "default" is configured.
On 11/03/2018 07:37 PM, Matias Bjørling wrote:
The numa_slit variable used by node_distance is available to a
module as long as it is linked at compile-time. However, it is
not available to loadable modules. Leading to errors such as:
ERROR: "numa_slit" [drivers/nvme/host/nvme-core.ko] undefi
From: Wanpeng Li
Reported by syzkaller:
BUG: unable to handle kernel NULL pointer dereference at 01c8
PGD 8003ec4da067 P4D 8003ec4da067 PUD 3f7bfa067 PMD 0
Oops: [#1] PREEMPT SMP PTI
CPU: 7 PID: 5059 Comm: debug Tainted: G OE 4.19.0-rc5 #16
RIP: 0010:
Hi Linus,
On Tue, Nov 20, 2018 at 9:10 AM Linus Walleij wrote:
> As with the Amiga, this chip also has an RTC clock that should
> go to the RTC subsystem, naturally.
Please note the Amiga CIA is an 8520, not 6526, hence it has a 24-bit TOD
instead of a BCD TOD, so it's not suitable for use as an
Commit-ID: 1ad33f5aec20f53785dbad44c6fb3b204aefd921
Gitweb: https://git.kernel.org/tip/1ad33f5aec20f53785dbad44c6fb3b204aefd921
Author: Andy Lutomirski
AuthorDate: Mon, 19 Nov 2018 14:45:32 -0800
Committer: Ingo Molnar
CommitDate: Tue, 20 Nov 2018 08:44:30 +0100
x86/fault: Don't set th
Commit-ID: e49d3cbef0176c182b86206185f137a87f16ab91
Gitweb: https://git.kernel.org/tip/e49d3cbef0176c182b86206185f137a87f16ab91
Author: Andy Lutomirski
AuthorDate: Mon, 19 Nov 2018 14:45:31 -0800
Committer: Ingo Molnar
CommitDate: Tue, 20 Nov 2018 08:44:29 +0100
x86/fault: Make error_c
Hi Huijin,
On Thu, Nov 15, 2018 at 6:08 AM Huijin Park wrote:
> From: "huijin.park"
>
> The "params->size" is defined as "u64".
> And "info->sector_size" and "info->n_sectors" are defined as
> unsigned int and u16.
> Thus, u64 data might have strange data(loss data) if the result
> overflows an
Commit-ID: 6ea59b074f15e7ef4b042a108950861b383e7b02
Gitweb: https://git.kernel.org/tip/6ea59b074f15e7ef4b042a108950861b383e7b02
Author: Andy Lutomirski
AuthorDate: Mon, 19 Nov 2018 14:45:30 -0800
Committer: Ingo Molnar
CommitDate: Tue, 20 Nov 2018 08:44:29 +0100
x86/fault: Improve the
On Mon, Nov 19, 2018 at 11:59 PM Richard Guy Briggs wrote:
> The simple answer is that the audit PATH record format expects the four
> cap_f* fields to be there and a best effort is being attempted to fill
> in that information in an expected way with meaningful values. Perhaps
> better to accep
Commit-ID: e50928d7213e72ee95507221a89ed07d2bb6517b
Gitweb: https://git.kernel.org/tip/e50928d7213e72ee95507221a89ed07d2bb6517b
Author: Andy Lutomirski
AuthorDate: Mon, 19 Nov 2018 14:45:29 -0800
Committer: Ingo Molnar
CommitDate: Tue, 20 Nov 2018 08:44:29 +0100
x86/fault: Fix SMAP #PF
On Tue, 20 Nov 2018 05:06:50 +,
Manivannan Sadhasivam wrote:
>
> Hi Marc,
>
> On Mon, Nov 19, 2018 at 05:57:12PM +, Marc Zyngier wrote:
> > On 19/11/2018 17:09, Manivannan Sadhasivam wrote:
> > > Add clock driver for RDA Micro RDA8810PL SoC supporting OSTIMER
> > > and HWTIMER.
> > >
>
Commit-ID: dae0a10593007d049ea71601357ac41d4f247ee9
Gitweb: https://git.kernel.org/tip/dae0a10593007d049ea71601357ac41d4f247ee9
Author: Andy Lutomirski
AuthorDate: Mon, 19 Nov 2018 14:45:27 -0800
Committer: Ingo Molnar
CommitDate: Tue, 20 Nov 2018 08:44:28 +0100
x86/cpufeatures, x86/fa
On Mon, Nov 19, 2018 at 02:45:25PM -0800, Andy Lutomirski wrote:
> The fault-handling code that takes mmap_sem needs to avoid a
> deadlock that could occur if the kernel took a bad (OOPS-worthy)
> page fault on a user address while holding mmap_sem. This can only
> happen if the faulting instructi
Commit-ID: a15781b536293edc32bf374233f3b8ad77c3f72b
Gitweb: https://git.kernel.org/tip/a15781b536293edc32bf374233f3b8ad77c3f72b
Author: Andy Lutomirski
AuthorDate: Mon, 19 Nov 2018 14:45:28 -0800
Committer: Ingo Molnar
CommitDate: Tue, 20 Nov 2018 08:44:28 +0100
x86/fault: Fold smap_vi
Commit-ID: 6344be608c039f3a787f1144c46fcb04c0f76561
Gitweb: https://git.kernel.org/tip/6344be608c039f3a787f1144c46fcb04c0f76561
Author: Andy Lutomirski
AuthorDate: Mon, 19 Nov 2018 14:45:25 -0800
Committer: Ingo Molnar
CommitDate: Tue, 20 Nov 2018 08:44:27 +0100
x86/fault: Check user_m
On Mon, Nov 19, 2018 at 2:22 AM Finn Thain wrote:
> Add a platform clocksource by adapting the existing arch_gettimeoffset
> implementation.
>
> Signed-off-by: Finn Thain
> Acked-by: Linus Walleij
> Tested-by: Stan Johnson
As noted for the Amiga CIA (which is pretty much a sibling to this
MOS
On Mon, 19 Nov 2018 at 22:27, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.4.164 release.
> There are 160 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Re
* Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
> > The fault handling code tries to validate that a page fault from
> > user mode that would extend the stack is within a certain range of
> > the user SP. regs->sp is only equal to the user SP if
> > user_mode(regs). In the extremely un
On Mon, 19 Nov 2018 at 22:23, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.138 release.
> There are 83 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Res
On Mon, Nov 19, 2018 at 2:22 AM Finn Thain wrote:
> Add a platform clocksource by adapting the existing arch_gettimeoffset
> implementation.
>
> Normally the MFP timer C interrupt flag would be used to check for
> timer counter wrap-around. Unfortunately, that flag gets cleared by the
> MFP itsel
On Mon, 19 Nov 2018 at 22:18, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.82 release.
> There are 124 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Re
[dropping the @rdamicro.com addresses, as they bounce...]
On Tue, 20 Nov 2018 03:19:58 +,
Manivannan Sadhasivam wrote:
>
> Hi Marc,
>
> Thanks for the quick review!
>
> On Mon, Nov 19, 2018 at 05:36:49PM +, Marc Zyngier wrote:
> > Manivannan,
> >
> > On 19/11/2018 17:09, Manivannan Sa
On SAMA5D2 SoC the PIOBU pins do not lose their
voltage during Backup/Self-refresh mode. This can
be useful, for example, when the voltage must remain
positive for a peripheral during Backup/Self-refresh
mode (suspend-to ram is the Linux equivalent state).
v2:
- make driver be a subnode of the sys
PIOBU pins do not lose their voltage during Backup/Self-refresh.
This patch adds a simple GPIO controller for them and a
maintainer for the driver.
This driver adds support for using the pins as GPIO
offering the possibility to read/set the voltage.
Signed-off-by: Andrei Stefanescu
---
MAINTAIN
This patch describes the compatible and the device tree
bindings necessary for the SAMA5D2 PIOBU GPIO.
Signed-off-by: Andrei Stefanescu
---
.../bindings/gpio/gpio-sama5d2-piobu.txt | 31 ++
1 file changed, 31 insertions(+)
create mode 100644
Documentation/devicetr
On Mon, 19 Nov 2018 at 22:11, Greg Kroah-Hartman
wrote:
>
> --
> NOTE, this is going to be the last 4.18.y release. After this one it is
> end-of-life, please move to 4.19.y at this point in time.
> --
>
> This is the start of the stable review cycle for the 4.18.2
If read_symbols() fails during second list traversal (the one dealing
with ".cold" subfunctions) it frees the symbol, but never deletes it
from the list/hash_table resulting in symbol being freed again in
elf_close(). Fix by just returning an error leaving cleanup to
elf_close().
Fixes: 13810435b9
Because find_symbol_by_name() traverses the same lists as read_symbols()
changing sym->name in place without copying it affects the result of
find_symbol_by_name() and, in case when ".cold" function precedes it's
parent in sec->symbol_list, can result in function being considered a
parent of itself
The series started with 'parent symbol search' patch, but I found another issue
in read_symbols() while testing the failure-path.
Artem Savkov (2):
objtool: fix failed cold symbol doublefree
objtool: fix .cold functions parent symbols search
tools/objtool/elf.c | 19 +++
1 fi
On Mon, 19 Nov 2018 at 22:01, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.3 release.
> There are 205 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Res
On Mon, Nov 19, 2018 at 2:22 AM Finn Thain wrote:
> Add a platform clocksource by adapting the existing arch_gettimeoffset
> implementation.
>
> Signed-off-by: Finn Thain
> Acked-by: Linus Walleij
> ---
> Changed since v1:
> - Moved clk_total access to within the irq lock.
Came to think of it
On Fri, 2018-11-16 at 14:25:49 UTC, thor.tha...@linux.intel.com wrote:
> From: Thor Thayer
>
> The current Cadence QSPI driver caused a kernel panic sporadically
> when writing to QSPI. The problem was caused by writing more bytes
> than needed because the QSPI operated on 4 bytes at a time.
>
>
801 - 868 of 868 matches
Mail list logo
