From: Michal Hocko
Andrea has noticed [1] that a THP allocation might be really disruptive
when allocated on NUMA system with the local node full or hard to
reclaim. Stefan has posted an allocation stall report on 4.12 based
SLES kernel which suggests the same issue:
[245513.362669] kvm: page all
On Wed, Aug 29, 2018 at 06:04:12PM +0100, Allan Xavier wrote:
> This commit adds support for processing switch jump tables in objects
> with multiple .rodata sections, such as those created when using
> -ffunction-sections and -fdata-sections. Currently, objtool always
> looks in .rodata for jump
On Fri, 7 Sep 2018 at 14:56, Peter Zijlstra wrote:
>
> On Fri, Sep 07, 2018 at 02:35:51PM +0200, Vincent Guittot wrote:
> > Le Friday 07 Sep 2018 à 13:37:49 (+0200), Peter Zijlstra a écrit :
> > > On Fri, Sep 07, 2018 at 09:51:04AM +0200, Vincent Guittot wrote:
> > > > It can happen that load_bala
Digging up an email thread from 2013...
On Wed, Jul 03, 2013 at 01:29:41PM +1000, Dave Chinner wrote:
> On Tue, Jul 02, 2013 at 06:01:11PM -0700, Greg KH wrote:
> > On Tue, Jul 02, 2013 at 05:58:15PM -0700, Linus Torvalds wrote:
> > > On Tue, Jul 2, 2013 at 5:54 PM, Greg KH wrote:
> > > > On Tue,
From: Allan Xavier
Add support for processing switch jump tables in objects with multiple
.rodata sections, such as those created by '-ffunction-sections' and
'-fdata-sections'. Currently, objtool always looks in .rodata for jump
table information, which results in many "sibling call from callab
When we leak some tty buffer, warn about that. For that we need to
account the memory used also in the tty_buffer_free_all function. On
other locations, the accounting is handled correctly.
Note that we do not account the free list, as that was accounted in
tty_buffer_free before put on the free l
On Fri, Sep 07, 2018 at 06:26:49PM +0530, Srikar Dronamraju wrote:
> Can you please pick
>
>
> 1. 69bb3230297e881c797bbc4b3dbf73514078bc9d sched/numa: Stop multiple tasks
> from moving to the cpu at the same time
> 2. dc62cfdac5e5b7a61cd8a2bd4190e80b9bb408fc sched/numa: Avoid task migration
> fo
Pavel
On 09/06/2018 04:16 PM, Pavel Machek wrote:
> Hi!
>
>> Add the device tree bindings for the lm3697
>> LED driver for backlighting and display.
>>
>> Signed-off-by: Dan Murphy
>> ---
>>
>> v6 - Fix minor issues - https://lore.kernel.org/patchwork/patch/975387/
>>
>> v5 - Fix the comment for
What xtensa has in asm/vga.h is the same as what can be found in
asm-generic/vga.h. So use the latter header.
Signed-off-by: Jiri Slaby
Acked-by: Max Filippov
Cc: Chris Zankel
Cc: linux-xte...@linux-xtensa.org
---
arch/xtensa/include/asm/Kbuild | 1 +
arch/xtensa/include/asm/vga.h | 19 -
Hi!
> >> index ..3256dec21075
> >> --- /dev/null
> >> +++ b/Documentation/devicetree/bindings/leds/leds-lm3697.txt
> >> @@ -0,0 +1,86 @@
> >> +* Texas Instruments - LM3697 Highly Efficient White LED Driver
> >> +
> >> +The LM3697 11-bit LED driver provides high-
> >> +performance backl
This allows the context manager to retrieve information about nodes
that it holds a reference to, such as the current number of
references to those nodes.
Such information can for example be used to determine whether the
servicemanager is the only process holding a reference to a node.
This inform
On Thu, Sep 06, 2018 at 10:32:38AM +0200, Jiri Kosina wrote:
> From: Jiri Kosina
>
> Currently, we are issuing IBPB only in cases when switching into a
> non-dumpable
> process, the rationale being to protect such 'important and security
> sensitive'
> processess (such as GPG) from data leak in
Mouse worked fine in 4.18 however does not work in 4.18.5 Both kernels
were built with exactly the same .config file (copied from the 4.18
build dir to the un-tar'ed 4.18.5 directory to build)
Any input on root cause and fix / workaround is appreciated.
"Doesn't work" means : syslog and kerne
This adds labels to commonly used device-tree nodes so that derivative
boards can avoid ahb/apb hierarchy.
Signed-off-by: Eugen Hristev
---
Hello,
This was already done for SoC sama5d3 and sam9x5, in commit:
"fc37204432d" ("ARM: dts: at91: add labels to soc dtsi for derivative boards")
This co
On Fri, 7 Sep 2018 09:34:48 +0200
Peter Zijlstra wrote:
> On Wed, Sep 05, 2018 at 09:33:34PM -0400, Steven Rostedt wrote:
> > do_idle {
> >
> > [interrupts enabled]
> >
> > [interrupts disabled]
> > TRACE_IRQS_OFF [lockdep says irqs off]
> > [...]
> > TRACE_IRQS_IRET
> >
* Peter Zijlstra [2018-09-07 14:44:32]:
> On Fri, Sep 07, 2018 at 01:37:39PM +0100, Mel Gorman wrote:
> > On Fri, Sep 07, 2018 at 01:33:09PM +0200, Peter Zijlstra wrote:
> > > > ---
> > > > kernel/sched/fair.c | 2 +-
> > > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --
On Thu, Sep 06, 2018 at 04:29:59PM -0400, Rik van Riel wrote:
> On Thu, 2018-08-23 at 18:47 +1000, Nicholas Piggin wrote:
> > There is no need to call this from tlb_flush_mmu_tlbonly, it
> > logically belongs with tlb_flush_mmu_free. This allows some
> > code consolidation with a subsequent fix.
>
* Peter Zijlstra [2018-09-07 15:19:23]:
> On Fri, Sep 07, 2018 at 06:26:49PM +0530, Srikar Dronamraju wrote:
>
> > Can you please pick
> >
> >
> > 1. 69bb3230297e881c797bbc4b3dbf73514078bc9d sched/numa: Stop multiple tasks
> > from moving to the cpu at the same time
> > 2. dc62cfdac5e5b7a61cd8
On Fri, Sep 07, 2018 at 09:41:48AM -0400, Steven Rostedt wrote:
> On Fri, 7 Sep 2018 09:34:48 +0200
> Peter Zijlstra wrote:
>
> > On Wed, Sep 05, 2018 at 09:33:34PM -0400, Steven Rostedt wrote:
> > > do_idle {
> > >
> > > [interrupts enabled]
> > >
> > > [interrupts disabled]
> > >
On Fri, 7 Sep 2018 17:35:38 +0900
Sergey Senozhatsky wrote:
> Should't printk_nmi_enter()/printk_nmi_exit() still be notrace?
> Like you and Steven said - it's still before ftrace_nmi_enter()
> and should be notrace regardless.
Correct. My patch fixes both issues.
The patch that Peter is postin
On 09/07/2018 05:59 AM, Pascal PAILLET-LME wrote:
From: pascal paillet
The stpmic1 PMIC embeds a watchdog which is disabled by default. As soon
as the watchdog is started, it must be refreshed periodically otherwise
the PMIC goes off.
Signed-off-by: pascal paillet
---
changes in v2:
* the har
On Fri, Sep 07, 2018 at 07:14:20PM +0530, Srikar Dronamraju wrote:
> * Peter Zijlstra [2018-09-07 15:19:23]:
>
> > On Fri, Sep 07, 2018 at 06:26:49PM +0530, Srikar Dronamraju wrote:
> >
> > > Can you please pick
> > >
> > >
> > > 1. 69bb3230297e881c797bbc4b3dbf73514078bc9d sched/numa: Stop mul
Pavel
On 09/07/2018 08:32 AM, Pavel Machek wrote:
> Hi!
>
index ..3256dec21075
--- /dev/null
+++ b/Documentation/devicetree/bindings/leds/leds-lm3697.txt
@@ -0,0 +1,86 @@
+* Texas Instruments - LM3697 Highly Efficient White LED Driver
+
+The LM3697 1
On Fri, 7 Sep 2018 11:30:55 +0200
Peter Zijlstra wrote:
> > That said, I am not against this change. Especially the inlining
> > is a good move. Note that lockdep_off()/lockdep_on() must not
> > be traced as well.
>
> Hard to trace an inline funcion; we could make it __always_inline to
> feel
On Fri, 7 Sep 2018 15:45:32 +0200
Peter Zijlstra wrote:
> Yes really, we should not muck with the IRQ state from NMI context.
Right, and we didn't. Your patch didn't change anything, but allow for
printk_nmi_enter/exit() to be traced by ftrace, but that's wrong to
begin with because it ftrace_nm
On Fri, 7 Sep 2018 09:55:33 -0400
Steven Rostedt wrote:
> On Fri, 7 Sep 2018 15:45:32 +0200
> Peter Zijlstra wrote:
>
> > Yes really, we should not muck with the IRQ state from NMI context.
>
> Right, and we didn't. Your patch didn't change anything, but allow for
> printk_nmi_enter/exit() t
On Fri, Sep 07, 2018 at 09:55:33AM -0400, Steven Rostedt wrote:
> On Fri, 7 Sep 2018 15:45:32 +0200
> Peter Zijlstra wrote:
>
> > Yes really, we should not muck with the IRQ state from NMI context.
>
> Right, and we didn't. Your patch didn't change anything, but allow for
It does, it kills lock
On Fri, Sep 07, 2018 at 10:01:28AM -0400, Steven Rostedt wrote:
> On Fri, 7 Sep 2018 09:55:33 -0400
> Steven Rostedt wrote:
>
> > On Fri, 7 Sep 2018 15:45:32 +0200
> > Peter Zijlstra wrote:
> >
> > > Yes really, we should not muck with the IRQ state from NMI context.
> >
> > Right, and we di
From: Chao Yu
For journalled quota mode, let checkpoint to flush dquot dirty data
and quota file data to guarntee persistence of all quota sysfile in
last checkpoint, by this way, we can avoid corrupting quota sysfile
when encountering SPO.
The implementation is as below:
1. add a global state
Hi Masahiro,
On Fri, 7 Sep 2018 19:56:23 +0900
Masahiro Yamada wrote:
> NAND devices need additional data area (OOB) for error correction,
> but it is also used for Bad Block Marker (BBM). In many cases, the
> first byte in OOB is used for BBM, but the location actually depends
> on chip vendo
> This could achieve the above #1, but how would it solve #2 above? That is,
> after the guest uses the lbr feature for a while, the lbr stack has been
> passed through, then the guest doesn't use lbr any more, but the vCPU will
> still save/restore on switching?
If nothing accesses the MSR LBRs a
On 09/06/2018 07:21 PM, Dave Hansen wrote:
> On 09/02/2018 11:14 AM, Nadav Amit wrote:
>> When page-table entries are set, the compiler might optimize their
>> assignment by using multiple instructions to set the PTE. This might
>> turn into a security hazard if the user somehow manages to use the
On Fri, Sep 7, 2018 at 2:55 PM Guo Ren wrote:
>
> On Fri, Sep 07, 2018 at 10:14:38AM +0200, Arnd Bergmann wrote:
> > On Fri, Sep 7, 2018 at 5:04 AM Guo Ren wrote:
> > > On Thu, Sep 06, 2018 at 04:31:16PM +0200, Arnd Bergmann wrote:
> > Similarly, an MMIO read may be used to see if a DMA has compl
On Fri, Sep 07, 2018 at 03:58:17PM +0200, Peter Zijlstra wrote:
> On Fri, Sep 07, 2018 at 01:50:18PM +, Christophe Leroy wrote:
> >
> >
> > On 09/07/2018 01:42 PM, Peter Zijlstra wrote:
> > > On Fri, Sep 07, 2018 at 01:27:19PM +, Christophe Leroy wrote:
> > > > On PPC32, enums are 32 bits
On Fri, Sep 07, 2018 at 06:35:53PM +0530, Srikar Dronamraju wrote:
> * Mel Gorman [2018-09-07 11:11:38]:
>
> > task_numa_migrate is responsible for finding a core on a preferred NUMA
> > node for a task. As part of this, task_numa_find_cpu iterates through
> > the CPUs of a node and evaulates CPU
From: Thierry Reding
The kernel's vsnprintf() implementation discards all alpha-numeric
characters following a %p conversion specifier. This is done in order to
generically skip any of the various modifiers that the kernel supports.
Unfortunately, the OF modalias is generated with a format string
On 9/6/18 2:08 PM, Suman Tripathi wrote:
>> Sorry, but the patch is still coming through mangled. Did you use git
>> send-email ?
>
> [Suman Tripathi] yes. I rechecked before sending twice. Sorry for the
> inconvenience. Will figure the issue out
I can apply it manually while you work out the kink
On Fri, Sep 07, 2018 at 07:12:01PM +0530, Srikar Dronamraju wrote:
> > Yeah, I was afraid it would.. Srikar, can you also evaluate, I suspect
> > we'll have to pick one of these two patches.
>
> I can surely run some benchmarks between the two patches.
> However comparing Mel's patch with
> http:
On Fri, 2018-09-07 at 14:44 +0100, Will Deacon wrote:
> On Thu, Sep 06, 2018 at 04:29:59PM -0400, Rik van Riel wrote:
> > On Thu, 2018-08-23 at 18:47 +1000, Nicholas Piggin wrote:
> > > There is no need to call this from tlb_flush_mmu_tlbonly, it
> > > logically belongs with tlb_flush_mmu_free. Thi
On 7 September 2018 10:57:34 BST, Sricharan R wrote:
>Hi Craig,
>
>
>>> [v12]
>>> * Added my signed-off that was missing in some patches.
>>> * Added Bjorn's acked that i missed earlier.
>>>
>>
>> Can you give this a try on your 8974 device and check if the
>> pvs version reporting, sc
Cc linux-spa...@vger.kernel.org
Le 07/09/2018 à 14:22, Christophe Leroy a écrit :
Since commit cafa0010cd51f ("Raise the minimum required gcc version to
4.6"), sparse check fails as follows:
[root@pc16082vm linux-powerpc]# make C=2 arch/powerpc/kernel/process.o
CALL scripts/checksyscalls
From: Fathi Boudra
This patch cleans up the Makefile by restructuring a couple of
things, namely:
1) change explicit paths in targets for variables
2) substitute a variable (BINARIES) for another, part of the
selftests build system (TEST_PROGS_EXTENDED)
3) proper cleaning up of the EXTRA objec
When simply running `make' from the selftests top dir, this
error shows up:
cc -O2 -g -std=gnu99 -Wall -I../../../../usr/include/ -I/usr/include/libmount
-I/usr/include/blkid -I/usr/include/uuidgpio-mockup-chardev.c
../../../gpio/gpio-utils.o -lmount -o gpio-mockup-chardev
cc: error: ..
On Fri, Sep 7, 2018 at 4:28 PM Wei Wang wrote:
> This patch adds support to KVM to save/restore the lbr stack on vCPU
> context switching.
>
> When the guest sets the ACTIVE bit of MSR_KVM_PV_LBR_CTRL, a perf event
> is created on the host for the related vCPU. This perf event ensures the
> LBR st
Hi Boris,
2018-09-07 23:08 GMT+09:00 Boris Brezillon :
> Hi Masahiro,
>
> On Fri, 7 Sep 2018 19:56:23 +0900
> Masahiro Yamada wrote:
>
>> NAND devices need additional data area (OOB) for error correction,
>> but it is also used for Bad Block Marker (BBM). In many cases, the
>> first byte in OOB
On Fri, Sep 07, 2018 at 12:16:34PM +0200, Peter Zijlstra wrote:
> On Tue, Aug 28, 2018 at 01:22:57PM -0400, Johannes Weiner wrote:
> > +enum psi_states {
> > + PSI_IO_SOME,
> > + PSI_IO_FULL,
> > + PSI_MEM_SOME,
> > + PSI_MEM_FULL,
> > + PSI_CPU_SOME,
> > + /* Only per-CPU, to weigh the
On Thu, Sep 06, 2018 at 01:24:22PM +0200, Ard Biesheuvel wrote:
> On 22 August 2018 at 05:07, Jia He wrote:
> > Commit b92df1de5d28 ("mm: page_alloc: skip over regions of invalid pfns
> > where possible") optimized the loop in memmap_init_zone(). But it causes
> > possible panic bug. So Daniel Vac
On 6 September 2018 at 20:43, Theodore Y. Ts'o wrote:
> On Thu, Sep 06, 2018 at 03:13:23PM +0100, Matt Hart wrote:
>> On 6 September 2018 at 15:04, Theodore Y. Ts'o wrote:
>> > On Thu, Sep 06, 2018 at 06:45:15AM -0700, Guenter Roeck wrote:
>> >> Build results:
>> >> total: 134 pass: 133 fai
On (09/07/18 16:03), Peter Zijlstra wrote:
> >
> > I would even argue that placing printk_nmi_enter() between
> > lockdep_off() and ftrace_nmi_enter() is wrong because if in the future
> > printk_nmi_enter() were to do any ftrace tracing, it wont be caught, as
> > it was by having it before lockde
On 07/09/18 16:49, Borislav Petkov wrote:
> Hi Jürgen,
>
> On Mon, Sep 03, 2018 at 08:01:40AM -0700, tip-bot for Juergen Gross wrote:
>> Commit-ID: 6da63eb241a05b0e676d68975e793c0521387141
>> Gitweb:
>> https://git.kernel.org/tip/6da63eb241a05b0e676d68975e793c0521387141
>> Author: Juerge
On Fri, 7 Sep 2018 23:42:53 +0900
Masahiro Yamada wrote:
> Hi Boris,
>
> 2018-09-07 23:08 GMT+09:00 Boris Brezillon :
> > Hi Masahiro,
> >
> > On Fri, 7 Sep 2018 19:56:23 +0900
> > Masahiro Yamada wrote:
> >
> >> NAND devices need additional data area (OOB) for error correction,
> >> but it
On Fri, Sep 07, 2018 at 12:24:58PM +0200, Peter Zijlstra wrote:
> On Tue, Aug 28, 2018 at 01:22:57PM -0400, Johannes Weiner wrote:
> > +static void psi_clock(struct work_struct *work)
> > +{
> > + struct delayed_work *dwork;
> > + struct psi_group *group;
> > + bool nonidle;
> > +
> > + dwo
On Fri, Sep 07, 2018 at 04:52:20PM +0200, Juergen Gross wrote:
> And the fixing patch is already there:
Yeah, tglx just told me :)
Thx!
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
On Thu, Sep 06, 2018 at 08:05:33PM +0300, Andrey Ryabinin wrote:
> ARM64 has asm implementations of memchr(), memcmp(), str[r]chr(),
> str[n]cmp(), str[n]len(). KASAN don't see memory accesses in asm
> code, thus it can potentially miss many bugs.
>
> Ifdef out __HAVE_ARCH_* defines of these funct
Hi Eugen,
On Fri, Sep 07, 2018 at 04:38:09PM +0300, Eugen Hristev wrote:
> This adds labels to commonly used device-tree nodes so that derivative
> boards can avoid ahb/apb hierarchy.
>
> Signed-off-by: Eugen Hristev
> ---
>
> Hello,
>
> This was already done for SoC sama5d3 and sam9x5, in com
On Fri, Sep 07, 2018 at 10:44:22AM -0400, Johannes Weiner wrote:
> > This does the whole seqcount thing 6x, which is a bit of a waste.
>
> [...]
>
> > It's a bit cumbersome, but that's because of C.
>
> I was actually debating exactly this with Suren before, but since this
> is a super cold pat
On Fri, Sep 07, 2018 at 01:04:07PM +0200, Peter Zijlstra wrote:
> So yeah, grudingly acked. Did you want me to pick this up through the
> scheduler tree since most of this lives there?
Thanks for the ack.
As for routing it, I'll leave that decision to you and Andrew. It
touches stuff all over, so
On Thu, Sep 6, 2018 at 8:05 AM Arnd Bergmann wrote:
>
> On Thu, Sep 6, 2018 at 4:13 AM Guo Ren wrote:
> >
> > On Wed, Sep 05, 2018 at 07:43:10PM -0500, Rob Herring wrote:
> > > On Wed, Sep 5, 2018 at 7:10 AM Guo Ren wrote:
> > > >
> > > > Signed-off-by: Guo Ren
> > > > +
> > > > + intc: i
On Wed, 2018-09-05 at 09:01 +0300, Leon Romanovsky wrote:
> On Fri, Aug 31, 2018 at 10:24:18PM +0300, Igor Stoppa wrote:
> > Typically the assert is expected to not fail.
>
> This whole assert can be removed.
>
> >
> > Signed-off-by: Igor Stoppa
> > Acked-by: Doug Ledford
>
> Most probably th
Hello,
syzbot found the following crash on:
HEAD commit:28619527b8a7 Merge git://git.kernel.org/pub/scm/linux/kern..
git tree: bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=1618ac2140
kernel config: https://syzkaller.appspot.com/x/.config?x=62e9b447c16085cf
dashboa
On Thu, Sep 06, 2018 at 10:33:39AM +0200, Jiri Kosina wrote:
> +/*
> + * The read-modify-write of the MSR doesn't need any race protection here,
> + * as we're running in atomic context.
> + */
> +static void enable_stibp(void *info)
> +{
> + u64 mask;
> + rdmsrl(MSR_IA32_SPEC_CTRL, mask);
The abx804 and abx805 chips have support for a simple watchdog
function that can trigger an external reset.
Signed-off-by: Jeremy Gebben
---
drivers/rtc/Kconfig | 11 +++
drivers/rtc/rtc-abx80x.c | 160 ---
2 files changed, 159 insertions(+), 12 deletion
On Fri, 7 Sep 2018 12:35:21 +0200
Borislav Petkov wrote:
> From: Borislav Petkov
>
> There's no 'allocatote' - use the next best thing: 'allocate' :-)
Nice.
Probably can go through the trivial tree (Cc'd).
Acked-by: Steven Rostedt (VMware)
-- Steve
>
> Signed-off-by: Borislav Petkov
>
On Fri, Sep 7, 2018 at 5:17 PM, syzbot
wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:28619527b8a7 Merge git://git.kernel.org/pub/scm/linux/kern..
> git tree: bpf
> console output: https://syzkaller.appspot.com/x/log.txt?x=1618ac2140
> kernel config: https:
On Friday, September 7, 2018 10:11 PM, Andi Kleen wrote:
> > This could achieve the above #1, but how would it solve #2 above? That
> > is, after the guest uses the lbr feature for a while, the lbr stack
> > has been passed through, then the guest doesn't use lbr any more, but
> > the vCPU will sti
On Friday, September 7, 2018 10:37 PM, Jann Horn wrote:
> On Fri, Sep 7, 2018 at 4:28 PM Wei Wang wrote:
> > This patch adds support to KVM to save/restore the lbr stack on vCPU
> > context switching.
> >
> > When the guest sets the ACTIVE bit of MSR_KVM_PV_LBR_CTRL, a perf
> > event is created on
On 07/09/18 18:13, Doug Ledford wrote:
This patch was part of a larger series on lkml. In that context, I
acked it so that the series could be applied by whomever took it (it
didn't belong on rdma-list as a series since only one patch out of some
large number touched rdma files). Now it is bei
syzbot has found a reproducer for the following crash on:
HEAD commit:28619527b8a7 Merge git://git.kernel.org/pub/scm/linux/kern..
git tree: bpf
console output: https://syzkaller.appspot.com/x/log.txt?x=124e64d140
kernel config: https://syzkaller.appspot.com/x/.config?x=62e9b447c16
On Friday 07 Sep 2018 at 10:52:01 (+0200), Rafael J. Wysocki wrote:
> On Thursday, September 6, 2018 4:38:44 PM CEST Quentin Perret wrote:
> > Hi Rafael,
> >
> > On Thursday 06 Sep 2018 at 11:18:55 (+0200), Rafael J. Wysocki wrote:
> > > I'm not a particular fan of notifiers to be honest and you d
Hello Dear Friend.
Am Mrs.Favour Solomon . i work in one of the prime bank here in Burkina
Faso, i want the bank to transfer the money left by most of the greedy
African Politicians used our bank to launder money overseas through the
help of their Political advisers. Most of the funds which the
Hello Dear Friend.
Am Mrs.Favour Solomon . i work in one of the prime bank here in Burkina
Faso, i want the bank to transfer the money left by most of the greedy
African Politicians used our bank to launder money overseas through the
help of their Political advisers. Most of the funds which the
On 24/07/18 12:45, Shameer Kolothum wrote:
From: Neil Leeder
Add support for the SMMU Performance Monitor Counter Group
information from ACPI. This is in preparation for its use
in the SMMU v3 PMU driver.
Signed-off-by: Neil Leeder
Signed-off-by: Hanjun Guo
Signed-off-by: Shameer Kolothum
-
When CPUs have different capacity because of RT/DL tasks or
micro-architecture or max frequency differences, there are situation where
the imbalance is not correctly set to migrate waiting task on the idle CPU.
The UC uses the force_balance case :
if (env->idle != CPU_NOT_IDLE && group_has
On 24/07/18 12:45, Shameer Kolothum wrote:
This adds an helper to retrieve the smmuv3 dev(if any) associated
with the PMCG node. This will be used in subsequent SMMUv3 PMU
driver patch to name the pmu device.
As before, I think we might as well try to generalise this to the NC/RC
case now, rat
The whole static protection magic is silently fixing up anything which is
handed in. That's just wrong. The offending call sites need to be fixed.
Add a debug mechanism which emits a warning if a requested mapping needs to be
fixed up. The DETECT debug mechanism is really not meant to be enabled e
To avoid excessive 4k wise checks in the common case do a quick check first
whether the requested new page protections conflict with a static
protection area in the large page. If there is no conflict then the
decision whether to preserve or to split the page can be made immediately.
If the reques
The extra loop which tries hard to preserve large pages in case of conflicts
with static protection regions turns out to be not preserving anything, at
least not in the experiments which have been conducted.
There might be corner cases in which the code would be able to preserve a
large page oaccs
static_protections() is pretty unreadable. Split it up into separate checks
for each protection area.
Signed-off-by: Thomas Gleixner
---
arch/x86/mm/pageattr.c | 159 +
1 file changed, 95 insertions(+), 64 deletions(-)
--- a/arch/x86/mm/pageattr.
Checking static protections only page by page is slow especially for huge
pages. To allow quick checks over a complete range, add the ability to do
that.
Make the checks inclusive so the ranges can be directly used for debug output
later.
No functional change.
Signed-off-by: Thomas Gleixner
---
Avoid the extra variable and gotos by splitting the function into the
actual algorithm and a callable function which contains the lock
protection.
Rename it to should_split_large_page() while at it so the return values make
actually sense.
Clean up the code flow, comments and general whitespace d
When the existing mapping is correct and the new requested page protections
are the same as the existing ones, then further checks can be omitted and the
large page can be preserved. The slow path 4k wise check will not come up with
a different result.
Before:
1G pages checked:
The large page preservation mechanism is just magic and provides no
information at all. Add optional statistic output in debugfs so the magic can
be evaluated. Defaults is off.
Output:
1G pages checked:2
1G pages sameprot: 0
1G pages preserved:
With the range check it is possible to do a quick verification that the
current mapping is correct vs. the static protection areas.
In case a incorrect mapping is detected a warning is emitted and the large
page is split up. If the large page is a 2M page, then the split code is
forced to check th
If the new pgprot has the PRESENT bit cleared, then conflicts vs. RW/NX are
completely irrelevant.
Before:
1G pages checked:2
1G pages sameprot: 0
1G pages preserved: 0
2M pages checked: 540
2M pages sameprot:
Bin reported that try_preserve_large_page() in the page attribute code
consumes an large amount of CPU time. His initial attempts of addressing
this made me look deeper into the code.
The logic in this code is not really intelligent. It requires to check a
large page in 4k steps for conflicts. Tha
Hi Linus,
Just one small fix here, preventing a VM_WARN_ON when a !present PMD/PUD
is "freed" as part of a huge ioremap() operation. The correct behaviour
is to skip the free silently in this case, which is a little weird (the
function is a bit of a misnomer), but it follows the x86 implementation
Hey Tyler,
On Thu, Sep 06, 2018 at 10:15:12PM +, Tyler Hicks wrote:
> > +Users can read via ``ioctl(SECCOMP_NOTIF_RECV)`` (or ``poll()``) on a
> > seccomp
> > +notification fd to receive a ``struct seccomp_notif``, which contains five
> > +members: the input length of the structure, a global
On 09/07/2018 05:56 PM, Will Deacon wrote:
> On Thu, Sep 06, 2018 at 08:05:33PM +0300, Andrey Ryabinin wrote:
>> ARM64 has asm implementations of memchr(), memcmp(), str[r]chr(),
>> str[n]cmp(), str[n]len(). KASAN don't see memory accesses in asm
>> code, thus it can potentially miss many bugs.
As you are already in a tasklet, it is unnecessary to call spin_lock_bh.
Signed-off-by: jun qian
Cc: Barry song <21cn...@gmail.com>
---
drivers/s390/char/tty3270.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/s390/char/tty3270.c b/drivers/s390/char/tty3270.c
in
On Fri, Sep 07, 2018 at 12:59:44PM +, Pascal PAILLET-LME wrote:
> @@ -804,6 +804,18 @@ config REGULATOR_TI_ABB
> on TI SoCs may be unstable without enabling this as it provides
> device specific optimized bias to allow/optimize functionality.
>
> +config REGULATOR_STPMIC1
Th
Thanks for the new patchset! Backported to 4.9 and retested on ARMv8 8
code system running Android. Signals behave as expected reacting to
memory pressure, no jumps in "total" counters that would indicate an
overflow/underflow issues. Nicely done!
Tested-by: Suren Baghdasaryan
On Fri, Sep 7, 201
On Fri, Sep 7, 2018 at 8:19 AM, Dmitry Vyukov wrote:
> On Fri, Sep 7, 2018 at 5:17 PM, syzbot
> wrote:
>> Hello,
>>
>> syzbot found the following crash on:
>>
>> HEAD commit:28619527b8a7 Merge git://git.kernel.org/pub/scm/linux/kern..
>> git tree: bpf
>> console output: https://syzkalle
On Thu, 6 Sep 2018, Andrea Parri wrote:
> > Have you noticed any part of the generic code that relies on ordinary
> > acquire-release (rather than atomic RMW acquire-release) in order to
> > implement locking constructs?
>
> There are several places in code where the "lock-acquire" seems to be
The patch
regmap: split up regmap_config.use_single_rw
has been applied to the regmap tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent
The patch
spi: pic32: remove unnecessary of_node_get()
has been applied to the spi tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Lin
The patch
regmap: fix comment for regmap.use_single_write
has been applied to the regmap tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and se
On Fri, Sep 07, 2018 at 12:00:19PM -0400, Alan Stern wrote:
> On Thu, 6 Sep 2018, Andrea Parri wrote:
>
> > > Have you noticed any part of the generic code that relies on ordinary
> > > acquire-release (rather than atomic RMW acquire-release) in order to
> > > implement locking constructs?
> >
WARN_ON() already contains an unlikely(), so it's not necessary to wrap it
into another.
Signed-off-by: Igor Stoppa
Cc: Srivatsa S. Bhat
Cc: "Rafael J. Wysocki"
Cc: linux...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
---
drivers/cpufreq/cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1
* David Howells [180907 08:51]:
> Tony Lindgren wrote:
>
> > Looks like next-20180906 now has a regression where mounting
> > root won't work with commit fd0002870b45 ("vfs: Implement a
> > filesystem superblock creation/configuration context").
>
> Am I right in thinking you're not using any o
Hi Boris,
2018-09-07 23:53 GMT+09:00 Boris Brezillon :
> On Fri, 7 Sep 2018 23:42:53 +0900
> Masahiro Yamada wrote:
>
>> Hi Boris,
>>
>> 2018-09-07 23:08 GMT+09:00 Boris Brezillon :
>> > Hi Masahiro,
>> >
>> > On Fri, 7 Sep 2018 19:56:23 +0900
>> > Masahiro Yamada wrote:
>> >
>> >> NAND devices
201 - 300 of 962 matches
Mail list logo
