randconfig-a004-20200920
i386 randconfig-a005-20200920
i386 randconfig-a001-20200920
i386 randconfig-a002-20200921
i386 randconfig-a006-20200921
i386 randconfig-a003-20200921
i386 randconfig-a004
On Tue, Sep 22, 2020 at 11:31:46AM +0800, Qiang Zhao wrote:
> From: Zhao Qiang
>
> On LS1088A, watchdog clk are divided by 16, correct it in dts.
>
> Signed-off-by: Zhao Qiang
Applied, thanks.
On Mon, 2020-09-21 at 13:41 +0200, Pavel Machek wrote:
> The last return statement is unreachable code. I'm not sure if it
> will
> provoke any warnings, but it looks ugly.
>
> Signed-off-by: Pavel Machek (CIP)
>
>
Applied to net-next-mlx5.
Thanks,
Saeed.
On Mon, 24 Aug 2020, Alex Shi wrote:
> Now pgdat.lru_lock was replaced by lruvec lock. It's not used anymore.
>
> Signed-off-by: Alex Shi
> Reviewed-by: Alexander Duyck
I don't take pleasure in spoiling your celebrations and ceremonies,
but I strongly agree with AlexD that this should simply
On Mon, 2020-09-21 at 21:10 +0800, Qinglang Miao wrote:
> Simplify the return expression.
>
> Signed-off-by: Qinglang Miao
> ---
> drivers/net/ethernet/mellanox/mlx5/core/ecpf.c | 6 +-
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
>
Applied to net-next-mlx5.
Thanks.
Clang warns:
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_mst_types.c:637:8:
warning: logical not is only applied to the left hand side of this
comparison [-Wlogical-not-parentheses]
&& !params[i].clock_force_enable ==
DSC_CLK_FORCE_DEFAULT) {
On Mon, 24 Aug 2020, Alex Shi wrote:
> From: Hugh Dickins
>
> Since we changed the pgdat->lru_lock to lruvec->lru_lock, it's time to
> fix the incorrect comments in code. Also fixed some zone->lru_lock comment
> error from ancient time. etc.
>
> Signed-off-by: Hugh Dickins
> Signed-off-by:
On Mon, 24 Aug 2020, Alex Shi wrote:
> From: Hugh Dickins
>
> Use the relock function to replace relocking action. And try to save few
> lock times.
>
> Signed-off-by: Hugh Dickins
> Signed-off-by: Alex Shi
> Reviewed-by: Alexander Duyck
NAK. Who wrote this rubbish? Oh, did I? Maybe
On Mon, 24 Aug 2020, Alex Shi wrote:
> From: Alexander Duyck
>
> Use this new function to replace repeated same code, no func change.
>
> When testing for relock we can avoid the need for RCU locking if we simply
> compare the page pgdat and memcg pointers versus those that the lruvec is
>
In current task abort routine, if task abort happens to the device W-LU,
the code directly jumps to ufshcd_eh_host_reset_handler() to perform a
full reset and restore then returns FAIL or SUCCESS. Commands sent to the
device W-LU are most likely the SSU cmds sent during UFS PM operations. If
such
Hi Sean,
Any comments?
Best Regards,
Joakim Zhang
> -Original Message-
> From: Joakim Zhang
> Sent: 2020年9月19日 2:17
> To: mche...@kernel.org; robh...@kernel.org; s...@mess.org
> Cc: linux-me...@vger.kernel.org; devicet...@vger.kernel.org;
> linux-kernel@vger.kernel.org; dl-linux-imx
Serialize eh_work with system PM events and async scan to make sure eh_work
does not run in parallel with them.
Change-Id: I33012c68e2ea443950313c59a4a46ad88cf3c82d
Signed-off-by: Can Guo
---
drivers/scsi/ufs/ufshcd.c | 64 +--
On Mon, Sep 21, 2020 at 04:46:43PM +0200, poesc...@lemonage.de wrote:
> From: Lars Poeschel
>
> Skip printing characters at the end of a display line. This fits to the
> behaviour we already had, that the cursor is nailed to last position of
> a line.
Just very old memories, but wasn't this
Hi Lars,
On Mon, Sep 21, 2020 at 04:46:40PM +0200, poesc...@lemonage.de wrote:
> From: Lars Poeschel
>
> We remove the hd44780_clear_fast (display) clear implementation. charlcd
> will fall back to use hd44780_common_clear_display then, which is much
> much faster.
I might have got confused,
On Tue, Sep 22, 2020 at 08:30:06AM +0300, Jarkko Sakkinen wrote:
> On Mon, Sep 21, 2020 at 02:18:49PM -0700, Sean Christopherson wrote:
> > On Tue, Sep 22, 2020 at 12:07:36AM +0300, Jarkko Sakkinen wrote:
> > > On Mon, Sep 21, 2020 at 09:57:58AM -0700, Sean Christopherson wrote:
> > > > On Mon,
Hi Lars,
On Mon, Sep 21, 2020 at 04:46:12PM +0200, poesc...@lemonage.de wrote:
> This tries to make charlcd device independent. At the moment hd44780
> device specific code is contained deep in charlcd. This moves this out
> into a hd44780_common module, where the two hd44780 drivers we have at
>
On 2020-09-18 12:13, Jaegeuk Kim wrote:
On 09/17, Can Guo wrote:
On 2020-09-17 00:05, Jaegeuk Kim wrote:
> On 09/16, Bean Huo wrote:
> > On Tue, 2020-09-15 at 13:45 -0700, Jaegeuk Kim wrote:
> > > Cc: Avri Altman
> > > Signed-off-by: Jaegeuk Kim
> > > ---
> > > drivers/scsi/ufs/ufshcd.c | 8
On Mon, Sep 21, 2020 at 02:18:49PM -0700, Sean Christopherson wrote:
> On Tue, Sep 22, 2020 at 12:07:36AM +0300, Jarkko Sakkinen wrote:
> > On Mon, Sep 21, 2020 at 09:57:58AM -0700, Sean Christopherson wrote:
> > > On Mon, Sep 21, 2020 at 03:49:46PM +0300, Jarkko Sakkinen wrote:
> > > > On Fri,
End users frequently want to know what features their processor
supports, independent of what the kernel supports.
/proc/cpuinfo is great. It is omnipresent and since it is provided by
the kernel it is always as up to date as the kernel. But, it could be
ambiguous about processor features which
On Mon, 24 Aug 2020, Alex Shi wrote:
> This patch moves per node lru_lock into lruvec, thus bring a lru_lock for
> each of memcg per node. So on a large machine, each of memcg don't
> have to suffer from per node pgdat->lru_lock competition. They could go
> fast with their self lru_lock.
>
>
On Mon, Sep 21, 2020 at 09:25:04PM -0500, Russ Anderson wrote:
> On Thu, Sep 17, 2020 at 09:54:29AM +0200, Greg Kroah-Hartman wrote:
> > On Wed, Sep 16, 2020 at 02:20:39PM -0500, Mike Travis wrote:
> > > Add Copyrights to those files that have been updated for UV5 changes.
> > >
> > >
On 9/21/20 2:49 AM, Hugh Dickins wrote:
On Mon, 21 Sep 2020, Tianjia Zhang wrote:
In function __shmem_file_setup(), shmem_unacct_size() is forgotten
on the failed path, so add it.
Fixes: 93dec2da7b234 ("... and switch shmem_file_setup() to
alloc_file_pseudo()")
Cc: Al Viro
Signed-off-by:
From: Yadong Qi
Background: We have a lightweight HV, it needs INIT-VMExit and
SIPI-VMExit to wake-up APs for guests since it do not monitor
the Local APIC. But currently virtual wait-for-SIPI(WFS) state
is not supported in nVMX, so when running on top of KVM, the L1
HV cannot receive the
On Mon, 2020-09-21 at 19:23 +0300, Denis Efremov wrote:
> Memory ft->g in accel_fs_tcp_create_groups() is allocaed with
> kcalloc().
> It's excessive to free ft->g with kvfree(). Use kfree() instead.
>
> Signed-off-by: Denis Efremov
> ---
>
series applied to net-next-mlx5
> + fh->buffers.buffer[i].v4l.fbuffer = mem;
> + fh->buffers.buffer[i].v4l.fbuffer_phys = virt_to_phys(mem);
> + fh->buffers.buffer[i].v4l.fbuffer_bus = virt_to_bus(mem);
> + for (off = 0; off < fh->buffers.buffer_size;
> + off +=
On Mon, Sep 21, 2020 at 10:59 PM 'Nick Desaulniers' via syzkaller-bugs
wrote:
>
> On Mon, Sep 21, 2020 at 1:09 AM 'Dmitry Vyukov' via Clang Built Linux
> wrote:
> >
> > On Mon, Sep 21, 2020 at 7:54 AM Dmitry Vyukov wrote:
> > >
> > > On Sat, Sep 19, 2020 at 1:08 PM Borislav Petkov wrote:
> > >
Add "ply" entry for Plymovent Group BV: https://www.plymovent.com/
Signed-off-by: Oleksij Rempel
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
changes v3:
- use old style copyright text
changes v2:
- fsl.yaml: reorder ply,plym2m
- imx6dl-plym2m.dts: use hyphen instead of underscore in phy-clock
Oleksij Rempel (3):
dt-bindings: vendor-prefixes: Add an entry for Plymovent
dt-bindings: arm: fsl: add Plymovent M2M board
ARM: dts: add
Plymovent M2M is a control interface produced for the Plymovent filter
systems.
Signed-off-by: David Jander
Signed-off-by: Oleksij Rempel
---
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/imx6dl-plym2m.dts | 396
2 files changed, 397 insertions(+)
On Mon, Sep 21, 2020 at 10:59 PM 'Nick Desaulniers' via syzkaller-bugs
wrote:
>
> On Mon, Sep 21, 2020 at 1:09 AM 'Dmitry Vyukov' via Clang Built Linux
> wrote:
> >
> > On Mon, Sep 21, 2020 at 7:54 AM Dmitry Vyukov wrote:
> > >
> > > On Sat, Sep 19, 2020 at 1:08 PM Borislav Petkov wrote:
> > >
Add Plymovent Group BV M2M iMX6dl based board
Signed-off-by: Oleksij Rempel
---
Documentation/devicetree/bindings/arm/fsl.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/arm/fsl.yaml
b/Documentation/devicetree/bindings/arm/fsl.yaml
index
On Mon, Sep 21, 2020 at 10:19:41AM +, Corentin Labbe wrote:
> This patch un-split some lines.
> Signed-off-by: Corentin Labbe
Just don't do this. This is a purious change going over 80 chars for
absolutely no reason, and you'd still need a very good reason for that.
On Mon, Sep 21, 2020 at 10:19:59AM +, Corentin Labbe wrote:
> Instead of using a fragile virt_to_bus, let's use proper DMA coherent
> for the stat_com entry.
>
> Signed-off-by: Corentin Labbe
> ---
> drivers/staging/media/zoran/zoran.h| 2 ++
>
Hi Mikulas,
I'll say up front that I think you're barking up the wrong tree
trying to knock down XFS and ext4 to justify NVFS. NVFS will stand
or fall on it's own merits, not on how you think it's better than
other filesystems...
I have some fundamental concerns about the NVFS integrity model,
在 2020/9/22 上午8:42, Hugh Dickins 写道:
> On Mon, 24 Aug 2020, Alex Shi wrote:
>
>> Hugh Dickins' found a memcg change bug on original version:
>> If we want to change the pgdat->lru_lock to memcg's lruvec lock, we have
>> to serialize mem_cgroup_move_account during pagevec_lru_move_fn. The
>>
On Mon, 21 Sep 2020 at 22:14, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 5.8.11 release.
> There are 118 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.
>
>
在 2020/9/22 上午7:49, Hugh Dickins 写道:
> On Mon, 24 Aug 2020, Alex Shi wrote:
>
>> Currently, compaction would get the lru_lock and then do page isolation
>> which works fine with pgdat->lru_lock, since any page isoltion would
>> compete for the lru_lock. If we want to change to memcg lru_lock,
On 2020-09-22 01:26, Stephen Boyd wrote:
Quoting Rafael J. Wysocki (2020-09-21 09:18:17)
On Fri, Aug 21, 2020 at 10:49 PM Sibi Sankar
wrote:
>
> Add GENPD_FLAG_NO_SUSPEND/RESUME flags to instruct genpd to keep the
> status of the PM domain unaltered during suspend/resume respectively.
> The
On 9/22/2020 2:57 AM, Douglas Anderson wrote:
As talked about in the patch ("arm64: dts: qcom: sc7180: Provide
pinconf for SPI to use GPIO for CS"), on some boards it makes much
more sense (and is much more efficient) to think of the SPI Chip
Select as a GPIO. Trogdor is one such board where
Include the linux/idle_inject.h header to fix W=1 build warning:
drivers/powercap/idle_inject.c:152:6: warning: no previous prototype for
‘idle_inject_set_duration’ [-Wmissing-prototypes]
drivers/powercap/idle_inject.c:167:6: warning: no previous prototype for
‘idle_inject_get_duration’
On 9/22/2020 2:57 AM, Douglas Anderson wrote:
When the chip select line is controlled by the QUP, changing CS is a
time consuming operation. We have to send a command over to the geni
and wait for it to Ack us every time we want to change (both making it
high and low). To send this command
Given tht we've not made much progress with the common branch,
are you fine just picking this up through the riscv tree for 5.10?
I'll defer other architectures that depend on the common changes to
5.11 then.
On Wed, Sep 09, 2020 at 08:55:15AM +0200, Christoph Hellwig wrote:
> now that we've
The included armada-37xx.dtsi already defines these two aliases.
Signed-off-by: Andre Heider
Reviewed-by: Pali Rohár
---
v3: really fix filename, sorry for the spam... too early, not enough coffee
v2: fix filename in commit message
This goes on top of Pali's patch:
"arm64: dts: marvell:
The included armada-3xxx.dtsi already defines these two aliases.
Signed-off-by: Andre Heider
Reviewed-by: Pali Rohár
---
v2: fix filename in commit message
This goes on top of Pali's patch:
"arm64: dts: marvell: espressobin: Add ethernet switch aliases"
The resulting .dtb files are the same.
On Mon, Sep 21, 2020 at 7:36 PM Michal Hocko wrote:
>
> On Mon 21-09-20 19:23:01, Yafang Shao wrote:
> > On Mon, Sep 21, 2020 at 7:05 PM Michal Hocko wrote:
> > >
> > > On Mon 21-09-20 18:55:40, Yafang Shao wrote:
> > > > On Mon, Sep 21, 2020 at 4:12 PM Michal Hocko wrote:
> > > > >
> > > > >
Hi Randy,
Thank you for the report, surely will fix it.
Regards
Vadivel
On 21/9/2020 11:45 pm, Randy Dunlap wrote:
Ping. Still seeing this in linux-next.
On 9/17/20 10:51 AM, Randy Dunlap wrote:
From: Randy Dunlap
Fix a Kconfig warning that is causing lots of build errors
when
syzbot has bisected this issue to:
commit 4b2bd5fec007a4fd3fc82474b9199af25013de4c
Author: John Stultz
Date: Sat Oct 8 00:02:33 2016 +
proc: fix timerslack_ns CAP_SYS_NICE check when adjusting self
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1697348d90
start
On Tue, Sep 22, 2020 at 12:53 AM Axel Rasmussen
wrote:
>
> On Sun, Sep 20, 2020 at 9:58 PM Yafang Shao wrote:
> >
> > On Fri, Sep 18, 2020 at 2:13 AM Axel Rasmussen
> > wrote:
> > >
> > > The goal of these tracepoints is to be able to debug lock contention
> > > issues. This lock is acquired
On Fri, Sep 18, 2020 at 02:10:42PM +0200, Nicolas Rybowski wrote:
> +
> +BPF_CALL_1(bpf_mptcp_sock, struct sock *, sk)
> +{
> + if (sk_fullsock(sk) && sk->sk_protocol == IPPROTO_TCP &&
> sk_is_mptcp(sk)) {
> + struct mptcp_subflow_context *mptcp_sfc = mptcp_subflow_ctx(sk);
Could
On Mon, 14 Sep 2020 10:32:07 +0800, Jing Xiangfeng wrote:
> The variable ret has been initialized with a value '0'. The assignment
> in switch-case is redundant. So remove it.
Applied to 5.10/scsi-queue, thanks!
[1/1] scsi: target: Remove redundant assignment to variable 'ret'
On 9/21/20 2:51 PM, kernel test robot wrote:
Greeting,
FYI, we noticed the following commit (built with gcc-9):
commit: e2aad6f1d232b457ea6a3194992dd4c0a83534a5 ("mm/debug_vm_pgtable/locks: take
correct page table lock")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
On Wed, 9 Sep 2020 21:54:32 +0800, YueHaibing wrote:
> drivers/scsi/libfc/fc_disc.c:304
> fc_disc_error() warn: passing zero to 'PTR_ERR'
>
> fp maybe NULL in fc_disc_error(), use PTR_ERR_OR_ZERO to handle this.
Applied to 5.10/scsi-queue, thanks!
[1/1] scsi: libfc: Fix passing zero to
On Mon, Sep 21, 2020 at 1:29 PM Joe Perches wrote:
>
> On Mon, 2020-09-21 at 13:04 -0600, Jim Cromie wrote:
> > This BUG_ON, from 2009, caught the impossible case of a word-char both
> > starting and ending a string (loosely speaking). A bad (reverted)
> > patch finally hit this case, but even
On Wed, 9 Sep 2020 21:57:11 +0800, YueHaibing wrote:
> There is no caller in tree, so can remove it.
Applied to 5.10/scsi-queue, thanks!
[1/1] scsi: aic94xx: Remove unused inline function
https://git.kernel.org/mkp/scsi/c/3f4fee002b00
--
Martin K. Petersen Oracle Linux Engineering
On Thu, 3 Sep 2020 19:29:33 +0800, Xiongfeng Wang wrote:
> When I cat module paramter 'global_max_data_area_mb' by sysfs, it
> displays as follows. It's better to add a newline for easy reading.
>
> root@(none):/# cat
> /sys/module/target_core_user/parameters/global_max_data_area_mb
>
On Wed, 02 Sep 2020 11:58:52 +0900, Daejun Park wrote:
> In some Samsung UFS devices, there is some booting fail issue with
> low-power UFS device. The reason of this issue is the UFS device has a
> little bit longer latency for NOP OUT response. It causes booting fail
> because NOP OUT command
On Fri, 28 Aug 2020 12:21:35 +, Matej Genci wrote:
> VirtIO 1.0 spec says
> The removed and rescan events ... when sent for LUN 0, they MAY
> apply to the entire target so the driver can ask the initiator
> to rescan the target to detect this.
>
> This change introduces the
On Wed, 9 Sep 2020 19:58:55 +0100, Alex Dewar wrote:
> kmemdup can be used instead of kmalloc+memcpy. Replace two occurrences
> of this pattern.
>
> Issue identified with Coccinelle.
Applied to 5.10/scsi-queue, thanks!
[1/1] scsi: aic7xxx: Use kmemdup() in two places
On Thu, 27 Aug 2020 10:20:30 +0300, Adrian Hunter wrote:
> Intel host controllers support the setting of latency tolerance.
> Accordingly, implement the PM QoS ->set_latency_tolerance() callback. The
> raw register values are also exposed via debugfs.
Applied to 5.10/scsi-queue, thanks!
[1/1]
在 2020/9/22 上午7:16, Hugh Dickins 写道:
> On Mon, 24 Aug 2020, Alex Shi wrote:
>
>> Currently lru_lock still guards both lru list and page's lru bit, that's
>> ok. but if we want to use specific lruvec lock on the page, we need to
>> pin down the page's lruvec/memcg during locking. Just taking
On Thu, Sep 17, 2020 at 09:54:29AM +0200, Greg Kroah-Hartman wrote:
> On Wed, Sep 16, 2020 at 02:20:39PM -0500, Mike Travis wrote:
> > Add Copyrights to those files that have been updated for UV5 changes.
> >
> > Signed-off-by: Mike Travis
> > ---
> > arch/x86/include/asm/uv/bios.h | 1 +
>
On Mon, Sep 14, 2020 at 03:52:02PM +0800, Qiang Zhao wrote:
> -Original Message-
> From: Shawn Guo
> Sent: 2020年9月22日 10:18
> To: Qiang Zhao
> Cc: robh...@kernel.org; linux-kernel@vger.kernel.org;
> devicet...@vger.kernel.org
> Subject: Re: [PATCH] arm64: dts: layerscape: correct
在 2020/9/22 上午6:03, Hugh Dickins 写道:
>> Acked-by: Hugh Dickins
>>
>> In your lruv19 github tree, you have merged 14/32 into this one: thanks.
> Grr, I've only just started, and already missed some of my notes.
>
> I wanted to point out that this patch does introduce an extra unlock+lock
> in
From: Zhao Qiang
On LS1088A, watchdog clk are divided by 16, correct it in dts.
Signed-off-by: Zhao Qiang
---
Changes for v2:
- rebase
arch/arm64/boot/dts/freescale/fsl-ls1088a.dtsi | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git
在 2020/9/22 上午5:36, Hugh Dickins 写道:
>
>> We have to move lru_lock into lru_note_cost, since it cycle up on memcg
>> tree, for future per lruvec lru_lock replace. It's a bit ugly and may
>> cost a bit more locking, but benefit from multiple memcg locking could
>> cover the lost.
>>
>>
On Mon, Sep 21, 2020 at 06:03:18PM +0200, Michal Hocko wrote:
> On Mon 21-09-20 08:45:58, Paul E. McKenney wrote:
> > On Mon, Sep 21, 2020 at 09:47:16AM +0200, Michal Hocko wrote:
> > > On Fri 18-09-20 21:48:15, Uladzislau Rezki (Sony) wrote:
> > > [...]
> > > > Proposal
> > > >
> > > >
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/i915/selftests/mock_gem_device.c
between commit:
9f9f4101fc98 ("drm/i915/selftests: Push the fake iommu device from the stack
to data")
from the drm-intel tree and commit:
cd01269d11a3
>
>
>
> > -Original Message-
> > From: Biwen Li
> > Sent: Monday, September 21, 2020 10:13 PM
> > To: Shawn Guo ; Biwen Li (OSS)
> >
> > Cc: alexandre.bell...@bootlin.com; Leo Li ;
> > robh...@kernel.org; mark.rutl...@arm.com; devicet...@vger.kernel.org;
> >
> -Original Message-
> From: Biwen Li
> Sent: Monday, September 21, 2020 10:13 PM
> To: Shawn Guo ; Biwen Li (OSS)
>
> Cc: alexandre.bell...@bootlin.com; Leo Li ;
> robh...@kernel.org; mark.rutl...@arm.com; devicet...@vger.kernel.org;
> linux-kernel@vger.kernel.org; Jiafei Pan ;
On Thu, Sep 10, 2020 at 08:32:04AM -0700, Guenter Roeck wrote:
> Since v5.8, powerpc:allmodconfig often fails to build with the following
> error message.
>
> Inconsistent kallsyms data
> Try make KALLSYMS_EXTRA_PASS=1 as a workaround
>
> Setting KALLSYMS_EXTRA_PASS=1 does not help.
On Tue, Sep 15, 2020 at 12:31:58PM +0200, Peter Zijlstra wrote:
> Make acpi_processor_idle use the common broadcast code, there's no
> reason not to. This also removes some RCU usage after
> rcu_idle_enter().
>
> Signed-off-by: Peter Zijlstra (Intel)
> Acked-by: Rafael J. Wysocki
> Reported-by:
On 9/21/20 8:18 PM, Naresh Kamboju wrote:
> On Fri, 14 Aug 2020 at 14:26, Guenter Roeck wrote:
>>
>> On Mon, Jun 15, 2020 at 11:17:40AM +0200, Álvaro Fernández Rojas wrote:
>>> Instead of trying to parse CFE version string, which is customized by some
>>> vendors, let's just check that "CFE1" was
On Mon, Sep 21, 2020 at 12:32:16PM -0700, Tom Rix wrote:
>
> On 9/21/20 1:55 AM, Xu Yilun wrote:
> > On Sat, Sep 19, 2020 at 09:51:13AM -0700, t...@redhat.com wrote:
> >> From: Tom Rix
> >>
> >> I following up on Moritz asking for early RFC's by showing how this
> >> could be done with the
This patchset updates CascadelakeX events to v1.08 and
updates SkylakeX events to v1.21.
The events have been tested on CascadelakeX and SkylakeX
servers with latest perf/core branch.
The first version was posted a few months ago and now just
resend the patchset with minor update.
v2:
-
On Fri, 14 Aug 2020 at 14:26, Guenter Roeck wrote:
>
> On Mon, Jun 15, 2020 at 11:17:40AM +0200, Álvaro Fernández Rojas wrote:
> > Instead of trying to parse CFE version string, which is customized by some
> > vendors, let's just check that "CFE1" was passed on argument 3.
> >
> > Signed-off-by:
Hi Krzysztof,
On Mon, Sep 21, 2020 at 10:46:45PM +0200, Krzysztof Kozlowski wrote:
> WhOn Mon, 21 Sep 2020 at 22:31, Moritz Fischer wrote:
> >
> > Hi Krzysztof,
> >
> > On Mon, Sep 21, 2020 at 09:23:11AM +0200, Krzysztof Kozlowski wrote:
> > > On Mon, Sep 21, 2020 at 01:31:20PM +0800, Xu Yilun
On 9/21/20 7:40 PM, Frederic Weisbecker wrote:
> On Wed, Sep 09, 2020 at 11:08:16AM -0400, Nitesh Narayan Lal wrote:
>> +/*
>> + * num_housekeeping_cpus() - Read the number of housekeeping CPUs.
>> + *
>> + * This function returns the number of available housekeeping CPUs
>> + * based on
Currently, perf-stat with armv8_pmu events with a workload is broken.
This patch set just fixes that.
Before the patch set:
[root@localhost hulk]# tools/perf/perf stat -e
armv8_pmuv3_0/ll_cache_rd/,armv8_pmuv3_0/ll_cache_miss_rd/ ls > /dev/null
Segmentation fault
After the patch set:
When executing perf stat with armv8_pmu events with a workload, it will
report a segfault as result.
(gdb) bt
#0 0x00603fc8 in perf_evsel__close_fd_cpu (evsel=,
cpu=) at evsel.c:122
#1 perf_evsel__close_cpu (evsel=evsel@entry=0x716e950, cpu=7) at evsel.c:156
#2 0x004d4718
After the segfault is fixed, perf-stat with armv8_pmu events with a
workload is still broken:
[root@localhost hulk]# tools/perf/perf stat -e
armv8_pmuv3_0/ll_cache_rd/,armv8_pmuv3_0/ll_cache_miss_rd/ ls > /dev/null
Performance counter stats for 'ls':
armv8_pmuv3_0/ll_cache_rd/
On Tue, Sep 22, 2020 at 10:02 AM Rik van Riel wrote:
>
> Check whether a swap page was obtained instantaneously, for example
> because it is in zswap, or on a very fast IO device which uses busy
> waiting, and we did not wait on IO to swap in this page.
> If no IO was needed to get the swap page
>
> Caution: EXT Email
>
> On Tue, Sep 15, 2020 at 03:32:10PM +0800, Biwen Li wrote:
> > From: Biwen Li
> >
> > Remove useless property interrupts of rtc
> >
> > Signed-off-by: Biwen Li
> > ---
> > arch/arm64/boot/dts/freescale/fsl-lx2160a-rdb.dts | 2 --
> > 1 file changed, 2 deletions(-)
>
On 9/21/20 6:58 PM, Frederic Weisbecker wrote:
> On Thu, Sep 17, 2020 at 11:23:59AM -0700, Jesse Brandeburg wrote:
>> Nitesh Narayan Lal wrote:
>>
>>> In a realtime environment, it is essential to isolate unwanted IRQs from
>>> isolated CPUs to prevent latency overheads. Creating MSIX vectors
The Caninos Loucos Program develops Single Board Computers with an open
structure. The Program wants to form a community of developers to use
IoT technologies and disseminate the learning of embedded systems in
Brazil.
It is an initiative of the Technological Integrated Systems Laboratory
Add Device Trees for Caninos Loucos Labrador CoM Core v3 and base board
M v2. Based on the work of Andreas Färber on Cubieboard 7 device tree.
Signed-off-by: Matheus Castello
---
arch/arm64/boot/dts/actions/Makefile | 2 +
.../dts/actions/s700-labrador-base-m2.dts | 34 +
Update the documentation to add the Caninos Loucos Labrador. Labrador
project consists of the computer on module Core v2 based on the Actions
Semi S500, computer on module Core v3 based on the Actions Semi S700
and the Labrador base boards.
Signed-off-by: Matheus Castello
Acked-by: Rob Herring
Add Device Trees for Caninos Loucos Labrador CoM Core v2 and base board
M v1. Based on the work of Andreas Färber on Lemaker Guitar device tree.
Signed-off-by: Matheus Castello
Reviewed-by: Manivannan Sadhasivam
Reviewed-by: Andreas Färber
---
arch/arm/boot/dts/Makefile|
I'm adding to the series the new Labrador v3, since it uses the same vendor
prefix. Thanks Andreas, Mani and Rob for your time reviewing it.
Changes since v6:
- Add new caninos,labrador-v3 CoM and caninos,labrador-base-m2 base board
- Improve Model description
Changes since v5:
(Suggested by
On Tue, Sep 15, 2020 at 03:32:10PM +0800, Biwen Li wrote:
> From: Biwen Li
>
> Remove useless property interrupts of rtc
>
> Signed-off-by: Biwen Li
> ---
> arch/arm64/boot/dts/freescale/fsl-lx2160a-rdb.dts | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git
On Mon, Sep 14, 2020 at 11:43:39PM +0200, Michael Walle wrote:
> Now that we have support for GPIO lines of the SMARC connector, enable
> LED support on the KBox A-230-LS. There are two LEDs without fixed
> functions, one is yellow and one is green. Unfortunately, it is just one
> multi-color LED,
Hi,
On Tue, Sep 22, 2020 at 1:07 AM Matthias Brugger wrote:
>
> Hi Nicolas,
>
> Thanks for the patch.
>
> On 30/07/2020 06:01, Nicolas Boichat wrote:
> > In the error case, where a power domain cannot be powered on
> > successfully at boot time (in mtk_register_power_domains),
> > pm_genpd_init
On Mon, Sep 21, 2020 at 10:30:57PM +0100, Will Deacon wrote:
> On Sat, Sep 05, 2020 at 01:04:06PM -0700, Rob Clark wrote:
> > From: Rob Clark
> >
> > NOTE: I have re-ordered the series, and propose that we could merge this
> > series in the following order:
> >
> >1) 01-11 - merge
Rename nlines to num_lines to be consistent with other usage for fields
describing the number of entries in an array.
Signed-off-by: Kent Gibson
---
tools/gpio/gpio-hammer.c | 26 +-
tools/gpio/gpio-utils.c | 20 ++--
tools/gpio/gpio-utils.h | 6 +++---
Port the gpio-watch tool to the latest GPIO uAPI.
Signed-off-by: Kent Gibson
---
tools/gpio/gpio-watch.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/tools/gpio/gpio-watch.c b/tools/gpio/gpio-watch.c
index 5cea24fddfa7..f229ec62301b 100644
---
Port the gpio-hammer tool to the latest GPIO uAPI.
Signed-off-by: Kent Gibson
---
tools/gpio/gpio-hammer.c | 32 +---
tools/gpio/gpio-utils.c | 164 ---
tools/gpio/gpio-utils.h | 46 ++-
3 files changed, 197 insertions(+), 45 deletions(-)
Add support for debouncing monitored lines to gpio-event-mon.
Signed-off-by: Kent Gibson
---
tools/gpio/gpio-event-mon.c | 20 +---
1 file changed, 17 insertions(+), 3 deletions(-)
diff --git a/tools/gpio/gpio-event-mon.c b/tools/gpio/gpio-event-mon.c
index
Extend gpio-event-mon to support monitoring multiple lines.
This would require multiple lineevent requests to implement using uAPI v1,
but can be performed with a single line request using uAPI v2.
Signed-off-by: Kent Gibson
---
tools/gpio/gpio-event-mon.c | 45
Port the gpio-event-mon tool to the latest GPIO uAPI.
Signed-off-by: Kent Gibson
---
tools/gpio/gpio-event-mon.c | 91 +++--
1 file changed, 47 insertions(+), 44 deletions(-)
diff --git a/tools/gpio/gpio-event-mon.c b/tools/gpio/gpio-event-mon.c
index
Add support for edge detection to lines requested using
GPIO_V2_GET_LINE_IOCTL.
The edge detector implementation is based on the v1 lineevent
implementation.
Unlike the v1 implementation, an overflow of the event buffer results
in discarding older events, rather than the most recent, so the
Add support for GPIO_V2_LINE_SET_CONFIG_IOCTL, the uAPI v2
line set config ioctl.
Signed-off-by: Kent Gibson
---
drivers/gpio/gpiolib-cdev.c | 88 +
1 file changed, 88 insertions(+)
diff --git a/drivers/gpio/gpiolib-cdev.c b/drivers/gpio/gpiolib-cdev.c
index
1 - 100 of 2299 matches
Mail list logo