On Thu, 09 May 2019, Daniel Drake wrote:
> Hi,
>
>
> On Thu, Apr 25, 2019 at 4:27 AM Paulo Zanoni wrote:
>>
>> Em qua, 2019-04-24 às 20:58 +0100, Chris Wilson escreveu:
>> > Quoting Jian-Hong Pan (2019-04-23 10:28:10)
>> > > From: Daniel Drake
>> > >
>> > > On many (all?) the Gemini Lake
From: Cao Van Dong
Document SoC specific bindings for R-Car H3/M3-N/E3 SoCs.
Signed-off-by: Cao Van Dong
Reviewed-by: Rob Herring
Reviewed-by: Geert Uytterhoeven
Signed-off-by: Simon Horman
---
Documentation/devicetree/bindings/timer/renesas,cmt.txt | 6 ++
1 file changed, 6
On Mon, Apr 29, 2019 at 12:59:39PM +0200, Jiri Slaby wrote:
> We have a single node system with node 0 disabled:
> Scanning NUMA topology in Northbridge 24
> Number of physical nodes 2
> Skipping disabled node 0
> Node 1 MemBase Limit fbff
> NODE_DATA(1)
On Tue, May 07, 2019 at 08:37:57PM +0200, David Hildenbrand wrote:
>By converting start and size to page granularity, we actually ignore
>unaligned parts within a page instead of properly bailing out with an
>error.
>
>Cc: Andrew Morton
>Cc: Oscar Salvador
>Cc: Michal Hocko
>Cc: David
After thinking about it for a while, I feel it difficult to image how non
shareable plus normal cacheable works for vpending table. Supposing the
shareability bits are to direct the corresponding GICR to read/write table
memory, if a vPE is first scheduled on pCPU0 with GICR0 and an VLPI is
On Thu, 2019-05-09 at 07:37 -0400, Benjamin Coddington wrote:
> NetApp Security WARNING: This is an external email. Do not click links or open
> attachments unless you recognize the sender and know the content is safe.
>
>
>
>
> I think nfs_get_client and nfs_match_client could use a
at 18:31, Christoph Hellwig wrote:
On Thu, May 09, 2019 at 06:28:32PM +0800, Kai-Heng Feng wrote:
Based on my testing if queues (IRQ) are not disabled, NVMe controller
won’t be quiesced.
Symptoms can be high power drain or system freeze.
I can check with vendors whether this also necessary
Hello Xiang,
This patch has the opposite effect on my platform as DMA allocation is
aligned on 4k page.
For instance i declared:
- in RX 6 buffers (of 512 bytes)
- in TX 4 buffers ( of 512 bytes)
The result is (kernel trace)
[ 41.915896] virtio_rpmsg_bus virtio0: rx buffers: va ebb5f5ca, dma
On Wed, 2019-05-08 at 23:20 -0400, Theodore Ts'o wrote:
> On Wed, May 08, 2019 at 07:13:59PM -0700, Frank Rowand wrote:
> > > If you want to use vice grips as a hammer, screwdriver, monkey wrench,
> > > etc. there's nothing stopping you from doing that. But it's not fair
> > > to object to other
On Thu, May 09, 2019 at 10:10:57AM +0100, Patrick Bellasi wrote:
> On 08-May 21:15, Peter Zijlstra wrote:
> > On Wed, May 08, 2019 at 09:07:33PM +0200, Peter Zijlstra wrote:
> > > On Tue, Apr 02, 2019 at 11:41:40AM +0100, Patrick Bellasi wrote:
> > > > +static inline struct uclamp_se
> > > >
This is no longer a valid option in clang, it was removed in 3.5, which
we don't support.
https://github.com/llvm/llvm-project/commit/cb3f812b6b9fab8f3b41414f24e90222170417b4
Signed-off-by: Nathan Chancellor
---
Let me know if you want this incremental to your patch. I figured it
made more
On Thu, May 09, 2019 at 10:18:07AM +0100, Patrick Bellasi wrote:
> On 08-May 21:21, Peter Zijlstra wrote:
> > On Tue, Apr 02, 2019 at 11:41:41AM +0100, Patrick Bellasi wrote:
> > > diff --git a/include/uapi/linux/sched.h b/include/uapi/linux/sched.h
> > > index 22627f80063e..075c610adf45 100644
>
On Sun, May 5, 2019 at 11:45 PM Mika Westerberg
wrote:
>
> On Fri, May 03, 2019 at 04:35:02PM -0700, Furquan Shaikh wrote:
> > Thanks for reporting the issue and apologize for the breakage. When I
> > pushed the patch, my understanding was that the device drivers do not
> > depend on stale GPE
Hello Xiang,
I tested your patch on stm32 platform, no issue.
No remark on you code.
Acked-by:Arnaud POULIQUEN
Thanks,
Arnaud
On 1/31/19 4:41 PM, Xiang Xiao wrote:
> it's useful if the communication throughput is different from each side
>
> Signed-off-by: Xiang Xiao
> ---
>
I think nfs_get_client and nfs_match_client could use a refactor.. but
the
trivial fix is:
8<-
From 4ef2fc5912c5980890e781f8c0d941330254c100 Mon Sep 17 00:00:00 2001
Message-Id:
<4ef2fc5912c5980890e781f8c0d941330254c100.1557401467.git.bcodd...@redhat.com>
Hi.
On Thu, May 9, 2019 at 8:15 PM Nathan Chancellor
wrote:
>
> On Thu, May 09, 2019 at 03:44:55PM +0900, Masahiro Yamada wrote:
> > We do not support old Clang versions. Upgrade your clang version
> > if any of these flags is unsupported.
> >
> > Let's add flags within ifdef CONFIG_CC_IS_CLANG
Hello,
syzbot found the following crash on:
HEAD commit:43151d6c usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=178c8394a0
kernel config:
On Thu, May 09, 2019 at 08:35:05PM +0900, Masahiro Yamada wrote:
> Hi.
>
> On Thu, May 9, 2019 at 8:15 PM Nathan Chancellor
> wrote:
> >
> > On Thu, May 09, 2019 at 03:44:55PM +0900, Masahiro Yamada wrote:
> > > We do not support old Clang versions. Upgrade your clang version
> > > if any of
hi martin,
thanks for review, i will do a new series to remove err log on
get_drive_strength
and integrate your comment
On 5/7/19 8:18 PM, Martin Blumenstingl wrote:
> On Tue, May 7, 2019 at 1:57 PM Guillaume La Roque
> wrote:
>> drive-strength-microamp is a new feature needed for G12A
hi Martin,
same as previous patch i will do a new serie with your comments.
On 5/7/19 7:53 PM, Martin Blumenstingl wrote:
> Hi Guillaume,
>
> On Tue, May 7, 2019 at 1:57 PM Guillaume La Roque
> wrote:
>> rework bias enable/disable part to prepare drive-strength integration
> if it was my
On Thu, May 9, 2019 at 5:17 PM Chris Chiu wrote:
> I need the vif because there's seems no easy way to get RSSI. Please
> suggest if there's any better idea for this. I believe multiple vifs is for AP
> mode (with more than 1 virtual AP/SSIDs) and the Station+AP coexist
> mode. But the rtl8xxxu
This patch set aims at solving the following use case: appraise files from
the initial ram disk. To do that, IMA checks the signature/hash from the
security.ima xattr. Unfortunately, this use case cannot be implemented
currently, as the CPIO format does not support xattrs.
This proposal consists
From: Wanpeng Li
Extract adaptive tune timer advancement logic to a single function.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Sean Christopherson
Cc: Liran Alon
Signed-off-by: Wanpeng Li
---
arch/x86/kvm/lapic.c | 57 ++--
1 file changed, 33
From: Wanpeng Li
Advance lapic timer tries to hidden the hypervisor overhead between host
timer fires and the guest awares the timer is fired. However, it just hidden
the time between apic_timer_fn/handle_preemption_timer -> wait_lapic_expire,
instead of the real position of vmentry which is
Hi,
On Thu, Apr 25, 2019 at 4:27 AM Paulo Zanoni wrote:
>
> Em qua, 2019-04-24 às 20:58 +0100, Chris Wilson escreveu:
> > Quoting Jian-Hong Pan (2019-04-23 10:28:10)
> > > From: Daniel Drake
> > >
> > > On many (all?) the Gemini Lake systems we work with, there is frequent
> > > momentary
From: Wanpeng Li
After commit c3941d9e0 (KVM: lapic: Allow user to disable adaptive tuning of
timer advancement), '-1' enables adaptive tuning starting from default
advancment of 1000ns. However, we should expose an int instead of an overflow
uint module parameter.
Before patch:
Advance lapic timer tries to hidden the hypervisor overhead between host
timer fires and the guest awares the timer is fired. However, it just hidden
the time between apic_timer_fn/handle_preemption_timer -> wait_lapic_expire,
instead of the real position of vmentry which is mentioned in the
This patch adds support for an alternative method to add xattrs to files in
the rootfs filesystem. Instead of extracting them directly from the ram
disk image, they are extracted from a regular file called .xattr-list, that
can be added by any ram disk generator available today.
.xattr-list can
From: Mimi Zohar
This patch adds xattrs to a file, with name and value taken from a supplied
buffer. The data format is:
\0
[kamensky: fixed restoring of xattrs for symbolic links by using
sys_lsetxattr() instead of sys_setxattr()]
[sassu: removed state management, kept only
Le 08/05/2019 à 02:45, Michael Ellerman a écrit :
Christophe Leroy writes:
Selects HAVE_C_RECORDMCOUNT to use the C version of the recordmcount
intead of the old Perl Version of recordmcount.
This should improve build time. It also seems like the old Perl Version
misses some calls to
Similarly to commit 03450e271a16 ("fs: add ksys_fchmod() and do_fchmodat()
helpers and ksys_chmod() wrapper; remove in-kernel calls to syscall"), this
patch introduces the ksys_lsetxattr() helper to avoid in-kernel calls to
the sys_lsetxattr() syscall.
Signed-off-by: Roberto Sassu
---
These definitions are being moved to raid1-10.c.
Signed-off-by: Marcos Paulo de Souza
---
drivers/md/raid1-10.c | 25 +
drivers/md/raid1.c| 29 ++---
drivers/md/raid10.c | 27 +--
3 files changed, 28 insertions(+), 53
From: kbuild test robot
Statisticize tc_clksrc_suspend and tc_clksrc_resume.
Signed-off-by: kbuild test robot
Signed-off-by: Alexandre Belloni
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-atmel-tcb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Thu, May 9, 2019 at 5:54 AM Justin Piszcz wrote:
>
> Hello,
>
> Kernel: 5.1 (self-compiled, no modules)
> Arch: x86_64
> Distro: Debian Testing
>
> Issue: I was performing a dump of ext3 and ext4 filesystems and then
> restoring them to a separate volume (testing)-- afterwards I noticed that
>
From: Sugaya Taichi
Fix mlb_set_oneshot_state() to enable one-shot timer.
The function should stop and start a timer, but "start" statement was
dropped. Kick the register to start one-shot timer.
Fixes: b58f28f306db ("clocksource/drivers/timer-milbeaut: Introduce timer for
Milbeaut SoCs")
From: Alexandre Belloni
For the sake of consistency, let's rename the file to a name similar
to other file names in this directory.
Signed-off-by: Alexandre Belloni
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/Makefile| 2 +-
On Thu, May 09, 2019 at 03:44:55PM +0900, Masahiro Yamada wrote:
> We do not support old Clang versions. Upgrade your clang version
> if any of these flags is unsupported.
>
> Let's add flags within ifdef CONFIG_CC_IS_CLANG unconditionally,
> except -fcatch-undefined-behavior.
>
> Signed-off-by:
From: Alexandre Belloni
atmel_tclib is probed too late in the boot process to be able to use the
TCB as the boot clocksource. This is an issue for SoCs without the PIT
(sams70, samv70 and samv71 families) as they simply currently can't boot.
Get rid of the atmel_tclib dependency and probe
From: Mesih Kilinc
The suniv (new F-series) chip has a timer with less functionality than
the A10 timer, e.g. it has only 3 channels.
Add a new compatible for it. As we didn't use the extra channels on A10
either now, the code needn't to be changed.
The suniv chip is based on ARM926EJ-S CPU,
On Thu, May 09, 2019 at 03:46:35PM +0900, Masahiro Yamada wrote:
> These flags are documented in the GCC 4.6 manual, and recognized by
> Clang as well. Let's rip off the cc-option / cc-disable-warning switches.
>
> Signed-off-by: Masahiro Yamada
Reviewed-by: Nathan Chancellor
> ---
>
>
From: Joseph Lo
Since the clocksource framework has the support for suspend time
compensation. Re-work the driver to use that, so we can reduce the
duplicate code.
Suggested-by: Daniel Lezcano
Signed-off-by: Joseph Lo
Acked-by: Thierry Reding
Signed-off-by: Daniel Lezcano
---
On Thu, May 09, 2019 at 03:45:49PM +0900, Masahiro Yamada wrote:
> This flag is documented in the GCC 4.6 manual, and recognized by
> Clang as well. Let's rip off the cc-option switch.
>
> Signed-off-by: Masahiro Yamada
Reviewed-by: Nathan Chancellor
> ---
>
> Makefile | 2 +-
> 1 file
From: Alexandre Belloni
Allow selecting and unselecting the PIT clocksource driver so it doesn't
have to be compiled when unused.
Signed-off-by: Alexandre Belloni
Signed-off-by: Daniel Lezcano
---
arch/arm/mach-at91/Kconfig | 23 +++
1 file changed, 23 insertions(+)
diff
From: Sugaya Taichi
Add a shutdown operation to support shutdown timer.
Signed-off-by: Sugaya Taichi
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-milbeaut.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/clocksource/timer-milbeaut.c
From: Sugaya Taichi
Aggregate common register accesses into shared functions for
maintainability.
Signed-off-by: Sugaya Taichi
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/timer-milbeaut.c | 62 +---
1 file changed, 39 insertions(+), 23 deletions(-)
diff
From: Alexandre Belloni
Move linux/atmel_tc.h to the SoC specific folder include/soc/at91.
Signed-off-by: Alexandre Belloni
Acked-by: Thierry Reding
Acked-by: Arnd Bergmann
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/tcb_clksrc.c | 2 +-
From: David Abdurachmanov
This is only used on arm and arm64 platforms. Add COMPILE_TEST option.
Tested with 5.1-rc3+ on Fedora/RISCV. CONFIG_ARM_TIMER_SP804 no more shows
up in riscv config.
Signed-off-by: David Abdurachmanov
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/Kconfig |
From: Alexandre Belloni
Allow building the PIT driver when COMPILE_TEST is enabled. Also remove its
default value so it can be disabled.
Signed-off-by: Alexandre Belloni
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/Kconfig | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
From: Alexandre Belloni
Move the ATMEL_TCB_CLKSRC option to drivers/clocksource and make it silent
if COMPILE_TEST is not selected.
Cc: Arnd Bergmann
Signed-off-by: Alexandre Belloni
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/Kconfig | 7 +++
drivers/misc/Kconfig| 14
From: Alexandre Belloni
The TCBs that have children are using the proper DT bindings and don't need
to be handled by tclib.
Acked-by: Greg Kroah-Hartman
Signed-off-by: Alexandre Belloni
Signed-off-by: Daniel Lezcano
---
drivers/misc/atmel_tclib.c | 3 +++
1 file changed, 3 insertions(+)
From: Alexandre Belloni
Now that the driver is registered early enough, use the TCB as the
sched_clock which is much more accurate than the jiffies implementation.
Signed-off-by: Alexandre Belloni
Signed-off-by: Daniel Lezcano
---
drivers/clocksource/tcb_clksrc.c | 16
1
Hi Thomas,
here a (late) pull request for the changes on 5.2.
- Add compatible string for suniv for sun4i (Mesih Kilinc)
- Add COMPILE_TEST option for sp804 (David Abdurachmanov)
- Replace the compensation time when suspend happens on tegra with the one
provided by the generic framework
Commit-ID: eccd906484d1cd4b5da00f093d678badb6f48f28
Gitweb: https://git.kernel.org/tip/eccd906484d1cd4b5da00f093d678badb6f48f28
Author: Brijesh Singh
AuthorDate: Wed, 17 Apr 2019 15:41:17 +
Committer: Borislav Petkov
CommitDate: Wed, 8 May 2019 19:08:35 +0200
x86/mm: Do not use
We need to return from nfs_match_client() while still holding the
nfs_client_lock, or maybe fixed with ISERR_OR_NULL in nfs_match
client().
Anna, would you like a patch to fix it, or can that commit be pulled out
and fixed up at this point?
Ben
On 8 May 2019, at 20:17, syzbot wrote:
On Thu, May 09, 2019 at 12:38:13PM +0200, Peter Zijlstra wrote:
> That's tlb->cleared_p*, and yes agreed. That is, right until some
> architecture has level dependent TLBI instructions, at which point we'll
> need to have them all set instead of cleared.
> Anyway; am I correct in understanding
On Mon 06-05-19 09:39:03, Chengguang Xu wrote:
> Actually there are four lists for dquot management, so add
> the description of dqui_dirty_list to comment.
>
> Signed-off-by: Chengguang Xu
Thanks applied with small addition:
Note that some filesystems do dirty dquot tracking on their own
Hello Petr,
I just realized that early printks, or more specific vsnprintf invocations,
are broken on s390 due to
3e5903eb9cff ("vsprintf: Prevent crash when dereferencing invalid pointers").
E.g. the early boot output now looks like this where the first
(efault) should be the linux_banner:
[
There are many functions invoke apic_debug(), which is defined
a null function by default, and that's incovenient for debuging
lapic.
This patch allows setting apic debug according to add a apic_dbg
parameter of kvm.
Signed-off-by: Yi Wang
---
v2: change apic_dbg to bool and tag __read_mostly.
On Wed 08-05-19 14:38:22, sunny.s.zhang wrote:
> Hi Chengguang,
>
> 在 2019年05月05日 19:01, Chengguang Xu 写道:
> > When fail from creating cache jbd2_inode_cache, we will
> > destroy previously created cache jbd2_handle_cache twice.
> > This patch fixes it by removing first destroy in error path.
> >
On 2019/05/09 19:18, Sergey Senozhatsky wrote:
> What are these lines right before the kernel panic output?
> TTY writes (user space logging)?
I guess that the user space is calling printf() on stdout
which will be readable as console output.
>
>
> 03:54:05 executing program 5:
>
On Thu, May 09, 2019 at 09:37:26AM +0100, Will Deacon wrote:
> Hi all, [+Peter]
Right, mm/mmu_gather.c has a MAINTAINERS entry; use it.
Also added Nadav and Minchan who've poked at this issue before. And Mel,
because he loves these things :-)
> Apologies for the delay; I'm attending a
On (05/09/19 19:26), Tetsuo Handa wrote:
> >> By the way, recently we are hitting false positives caused by "WARNING:"
> >> string from not WARN() messages but plain printk() messages (e.g.
> >>
> >>
> >> https://syzkaller.appspot.com/bug?id=31bdef63e48688854fde93e6edf390922b70f8a4
> >>
> >>
Commit-ID: 604dc9170f2435d27da5039a3efd757dceadc684
Gitweb: https://git.kernel.org/tip/604dc9170f2435d27da5039a3efd757dceadc684
Author: Daniel Drake
AuthorDate: Thu, 9 May 2019 13:54:15 +0800
Committer: Ingo Molnar
CommitDate: Thu, 9 May 2019 11:06:48 +0200
x86/tsc: Use CPUID.0x16 to
Commit-ID: 52ae346bd26c7a8b17ea82e9a09671e98c5402b7
Gitweb: https://git.kernel.org/tip/52ae346bd26c7a8b17ea82e9a09671e98c5402b7
Author: Daniel Drake
AuthorDate: Thu, 9 May 2019 13:54:16 +0800
Committer: Ingo Molnar
CommitDate: Thu, 9 May 2019 11:06:49 +0200
x86/apic: Rename
Commit-ID: 2420a0b1798d7a78d1f9b395f09f3c80d92cc588
Gitweb: https://git.kernel.org/tip/2420a0b1798d7a78d1f9b395f09f3c80d92cc588
Author: Daniel Drake
AuthorDate: Thu, 9 May 2019 13:54:17 +0800
Committer: Ingo Molnar
CommitDate: Thu, 9 May 2019 11:06:49 +0200
x86/tsc: Set LAPIC timer
On Thu, May 09, 2019 at 06:28:32PM +0800, Kai-Heng Feng wrote:
> Based on my testing if queues (IRQ) are not disabled, NVMe controller
> won’t be quiesced.
> Symptoms can be high power drain or system freeze.
>
> I can check with vendors whether this also necessary under Windows.
System freeze
On 2019/05/09 18:58, Sergey Senozhatsky wrote:
>> +#ifdef CONFIG_DEBUG_AID_FOR_SYZBOT
>> +static int initial_loglevel;
>> +static void check_loglevel(struct timer_list *timer)
>> +{
>> +if (console_loglevel < initial_loglevel)
>> +panic("Console loglevel changed (%d->%d)!",
Hello,
syzbot found the following crash on:
HEAD commit:43151d6c usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=10e18c00a0
kernel config:
> -Original Message-
> From: Jonathan Hunter
> Sent: Thursday, May 9, 2019 3:12 PM
> To: Krishna Yarlagadda ; linus.wall...@linaro.org;
> thierry.red...@gmail.com; linux-kernel@vger.kernel.org; linux-
> g...@vger.kernel.org; linux-te...@vger.kernel.org;
> devicet...@vger.kernel.org
> Cc:
at 17:56, Christoph Hellwig wrote:
On Thu, May 09, 2019 at 05:42:30PM +0800, Kai-Heng Feng wrote:
That would be a set of 6 new suspend and resume callbacks, mind you,
and there's quite a few of them already. And the majority of drivers
would not need to use them anyway.
I think
On Thu, Mar 21, 2019 at 11:20:17PM +0100, Rafael J. Wysocki wrote:
> +static struct attribute *intel_epb_attrs[] = {
> + _attr_energy_perf_bias.attr,
> + NULL
> +};
> +
> +static const struct attribute_group intel_epb_attr_group = {
> + .name = power_group_name,
> + .attrs =
On (05/09/19 18:58), Sergey Senozhatsky wrote:
> On (05/08/19 19:31), Tetsuo Handa wrote:
> [..]
> > We are again getting corrupted reports where message from WARN() is missing.
> > For example,
> > https://syzkaller.appspot.com/text?tag=CrashLog=1720cac8a0 was
> > titled as "WARNING in
> On Tue, May 07, 2019 at 02:50:05AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following crash on:
> >
> > HEAD commit:baf76f0c slip: make slhc_free() silently accept an error p..
> > git tree: upstream
> > console output:
On (05/08/19 19:31), Tetsuo Handa wrote:
[..]
> We are again getting corrupted reports where message from WARN() is missing.
> For example, https://syzkaller.appspot.com/text?tag=CrashLog=1720cac8a0
> was
> titled as "WARNING in cgroup_exit" because the
> "WARNING: CPU: 0 PID: 7870 at
On Tue, May 07, 2019 at 02:50:05AM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit:baf76f0c slip: make slhc_free() silently accept an error p..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=16dbe6cca0
>
On Wed, 8 May 2019 20:46:05 -0600
Alex Williamson wrote:
> On Tue, 30 Apr 2019 17:49:37 -0500
> Parav Pandit wrote:
>
> > In following sequences, child devices created while removing mdev parent
> > device can be left out, or it may lead to race of removing half
> > initialized child mdev
On Thu, May 09, 2019 at 05:42:30PM +0800, Kai-Heng Feng wrote:
>> That would be a set of 6 new suspend and resume callbacks, mind you,
>> and there's quite a few of them already. And the majority of drivers
>> would not need to use them anyway.
>
> I think suspend_to_idle() and resume_from_idle()
Hello,
Kernel: 5.1 (self-compiled, no modules)
Arch: x86_64
Distro: Debian Testing
Issue: I was performing a dump of ext3 and ext4 filesystems and then
restoring them to a separate volume (testing)-- afterwards I noticed that
khugepaged is stuck at 100% CPU. It is currently still stuck at 100%
at 17:07, Rafael J. Wysocki wrote:
On Thu, May 9, 2019 at 8:49 AM Kai-Heng Feng
wrote:
Cc Rafael and linux-pm
I would have been much more useful to CC the patch to linux-pm at
least from the outset.
at 14:12, Christoph Hellwig wrote:
On Wed, May 08, 2019 at 08:28:30PM +,
On Wed, May 08, 2019 at 06:47:12PM -0700, Prasad Sodagudi wrote:
> Some platforms may need warm reboot support when kernel crashed
> for post mortem analysis instead of cold reboot. So use config
> CONFIG_WARM_REBOOT_ON_PANIC and SYSTEM_RESET2 psci command
> support for warm reset.
>
Please drop
On 09/05/2019 09:08, Krishna Yarlagadda wrote:
> Add binding doc for Tegra 194 pinctrl driver
>
> Signed-off-by: Krishna Yarlagadda
> ---
> Changes in V2:
> created new binding doc to handle Tegra194 pinctrl driver
>
> .../bindings/pinctrl/nvidia,tegra194-pinmux.txt| 116
>
Linux kernel coding style requires a size of 8 characters for
both TAB and indentation, and such value is embedded as magic
value allover the checkpatch script.
This makes hard to reuse the script by other projects with
different requirements in their coding style (e.g. OpenOCD [1]
requires TAB
On Thu, 09 May 2019, Amelie Delaunay wrote:
> STMicroelectronics Multi-Function eXpander (STMFX) is a slave controller
> using I2C for communication with the main MCU. Main features are:
> - 16 fast GPIOs individually configurable in input/output
> - 8 alternate GPIOs individually configurable in
On Thu, 09 May 2019, Amelie Delaunay wrote:
> This patch adds documentation of device tree bindings for the
> STMicroelectronics Multi-Function eXpander (STMFX) MFD core.
>
> Signed-off-by: Amelie Delaunay
> Reviewed-by: Linus Walleij
> Reviewed-by: Rob Herring
> Acked-for-MFD-by: Lee Jones
On 5/9/19 9:52 AM, Dariusz Marcinkiewicz wrote:
> Hi Hans.
>
> On Wed, Apr 24, 2019 at 2:09 PM Hans Verkuil wrote:
>>
>> Hi Dariusz,
>>
>> This is getting close, so I think for the next version you can drop
>> the RFC tag.
>>
>> Some comments:
>>
> ...
>>> +++
On Thu, May 09, 2019 at 11:19:37AM +0200, Rafael J. Wysocki wrote:
> Right, the choice of the target system state has already been made
> when their callbacks get invoked (and it has been made by user space,
> not by the platform).
>From a previous discussion I remember the main problem here is
On Thu, May 09, 2019 at 10:14:31AM +0200, Peter Zijlstra wrote:
> struct ftrace_regs_stack {
> ftrace_func_t func;
> unsigned long parent_ip;
> };
>
> void ftrace_regs_handler(struct pr_regs *regs)
> {
> struct ftrace_regs_stack *st = (void *)regs->sp;
> ftrace_func_t func
On Thu, May 9, 2019 at 10:03 AM Joe Perches wrote:
>
> On Thu, 2019-05-09 at 09:21 +0200, Antonio Borneo wrote:
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> []
> > @@ -2224,7 +2229,7 @@ sub string_find_replace {
> > sub tabify {
> > my ($leading) = @_;
> >
> > - my
On Wed, 8 May 2019 at 15:44, Sumit Garg wrote:
>
> Add a mailing list for patch reviews and discussions related to TEE
> subsystem.
>
> Signed-off-by: Sumit Garg
I forgot to include following tag as this change was suggested by Daniel. So:
Suggested-by: Daniel Thompson
-Sumit
> ---
>
On (05/02/19 21:42), Daniel Vetter wrote:
[..]
> @@ -469,6 +469,8 @@ static enum hrtimer_restart watchdog_timer_fn(struct
> hrtimer *hrtimer)
> add_taint(TAINT_SOFTLOCKUP, LOCKDEP_STILL_OK);
> if (softlockup_panic)
> panic("softlockup: hung
On 08-May 21:44, Peter Zijlstra wrote:
> On Tue, May 07, 2019 at 12:13:47PM +0100, Patrick Bellasi wrote:
> > On 17-Apr 15:26, Suren Baghdasaryan wrote:
> > > On Tue, Apr 2, 2019 at 3:42 AM Patrick Bellasi
> > > wrote:
>
> > > > @@ -1056,6 +1100,13 @@ static void __init init_uclamp(void)
> > >
On 08-May 21:41, Peter Zijlstra wrote:
> On Tue, Apr 02, 2019 at 11:41:42AM +0100, Patrick Bellasi wrote:
> > @@ -1056,6 +1100,13 @@ static void __init init_uclamp(void)
> > #else /* CONFIG_UCLAMP_TASK */
> > static inline void uclamp_rq_inc(struct rq *rq, struct task_struct *p) { }
> > static
On Wed, 8 May 2019 22:13:28 +
Parav Pandit wrote:
> > -Original Message-
> > From: Cornelia Huck
> > Sent: Wednesday, May 8, 2019 12:17 PM
> > To: Parav Pandit
> > Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org;
> > kwankh...@nvidia.com; alex.william...@redhat.com;
* Masami Hiramatsu wrote:
> --- a/tools/perf/util/probe-event.h
> +++ b/tools/perf/util/probe-event.h
> @@ -37,6 +37,7 @@ struct probe_trace_point {
> struct probe_trace_arg_ref {
> struct probe_trace_arg_ref *next; /* Next reference */
> long
On 08-May 21:21, Peter Zijlstra wrote:
> On Tue, Apr 02, 2019 at 11:41:41AM +0100, Patrick Bellasi wrote:
> > diff --git a/include/uapi/linux/sched.h b/include/uapi/linux/sched.h
> > index 22627f80063e..075c610adf45 100644
> > --- a/include/uapi/linux/sched.h
> > +++ b/include/uapi/linux/sched.h
>
* Masami Hiramatsu wrote:
> Add "ustring" type for fetching user-space string from kprobe event.
> User can specify ustring type at uprobe event, and it is same as
> "string" for uprobe.
>
> Note that probe-event provides this option but it doesn't choose the
> correct type automatically
On Thu, May 9, 2019 at 8:52 AM Christoph Hellwig wrote:
>
> On Thu, May 09, 2019 at 02:48:59PM +0800, Kai-Heng Feng wrote:
> > Not really, for hibernation pm_suspend_via_s2idle() evaluates to false so
> > the old code path will be taken.
> >
> >>
> >> And more to the points - if these "modern MS
* Masami Hiramatsu wrote:
> +static __always_inline long
> +probe_read_common(void *dst, const void __user *src, size_t size)
> +{
> + long ret;
> +
> + pagefault_disable();
> + ret = __copy_from_user_inatomic(dst, src, size);
> + pagefault_enable();
> +
> + return ret ?
On Mon, May 06, 2019 at 12:04:06PM +0300, Maxim Levitsky wrote:
> On top of that, it is expected that newer hardware will support the PASID
> based
> device subdivision, which will allow us to _directly_ pass through the
> submission queues of the device and _force_ us to use the NVME protocol
On 08-May 21:15, Peter Zijlstra wrote:
> On Wed, May 08, 2019 at 09:07:33PM +0200, Peter Zijlstra wrote:
> > On Tue, Apr 02, 2019 at 11:41:40AM +0100, Patrick Bellasi wrote:
> > > +static inline struct uclamp_se
> > > +uclamp_eff_get(struct task_struct *p, unsigned int clamp_id)
> > > +{
> > > +
801 - 900 of 991 matches
Mail list logo
