Re: [PATCH v5] gpiolib: Bind gpio_device to a driver to enable fw_devlink=on by default

On Sun, Jan 24, 2021 at 3:54 AM Saravana Kannan wrote: > Considering the "Fixes" is only in driver-core-next, should this go > through driver-core? I think Bartosz should pick it up as a GPIO fix for the -rc:s because it touches code that he is managing. Yours, Linus Walleij

Re: [PATCH v2 0/1] AMD EPYC: fix schedutil perf regression (freq-invariance)

From ongoing tests of this patch, it still certainly shows to address most of the Linux 5.11 performance regression previously encountered when using Schedutil. Additionally, for a number of workloads where not seeing a regression from 5.10 to 5.11 Git is still showing even better performance w

Re: [PATCH V3] mm/compaction: correct deferral logic for proactive compaction

On Wed, 20 Jan 2021, Vlastimil Babka wrote: > On 1/19/21 8:26 PM, David Rientjes wrote: > > On Mon, 18 Jan 2021, Charan Teja Reddy wrote: > > > >> should_proactive_compact_node() returns true when sum of the > >> weighted fragmentation score of all the zones in the node is greater > >> than the w

linux-next: build warning after merge of the xfs tree

Hi all, After merging the xfs tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: fs/xfs/xfs_log.c: In function 'xfs_log_cover': fs/xfs/xfs_log.c::16: warning: unused variable 'log' [-Wunused-variable] | struct xlog *log = mp->m_log; |

Re: [PATCH v7 13/14] selftests/vm: test flag is broken

On 1/21/21 7:37 PM, Pavel Tatashin wrote: In gup_test both gup_flags and test_flags use the same flags field. This is broken. Farther, in the actual gup_test.c all the passed gup_flags are erased and unconditionally replaced with FOLL_WRITE. Which means that test_flags are ignored, and code lik

Re: [PATCH v10 11/12] mm/vmalloc: Hugepage vmalloc mappings

Excerpts from Christoph Hellwig's message of January 25, 2021 1:07 am: > On Sun, Jan 24, 2021 at 06:22:29PM +1000, Nicholas Piggin wrote: >> diff --git a/arch/Kconfig b/arch/Kconfig >> index 24862d15f3a3..f87feb616184 100644 >> --- a/arch/Kconfig >> +++ b/arch/Kconfig >> @@ -724,6 +724,16 @@ config

Re: [PATCH v7 14/14] selftests/vm: test faulting in kernel, and verify pinnable pages

On 1/21/21 7:37 PM, Pavel Tatashin wrote: When pages are pinned they can be faulted in userland and migrated, and they can be faulted right in kernel without migration. In either case, the pinned pages must end-up being pinnable (not movable). Add a new test to gup_test, to help verify that the

Re: [PATCH] dsa: vsc73xx: add support for vlan filtering

On Thu, Jan 21, 2021 at 11:45 PM Vladimir Oltean wrote: > On Wed, Jan 20, 2021 at 07:30:18AM +0100, Pawel Dembicki wrote: > > This patch adds support for vlan filtering in vsc73xx driver. > > > > After vlan filtering enable, CPU_PORT is configured as trunk, without > > non-tagged frames. This all

[PATCH 0/8] MUSE: Userspace backed MTD v3

I'm happy to announce the first non-RFC version of this patch set. Over the xmas holidays I found some time to experiment with various userspace implementations of MTDs and gave the kernel side more fine-tuning. Rationale: -- When working with flash devices a common task is emulating them

[PATCH 2/8] fuse: Export IO helpers

MUSE will use this functions in its IO path, so export them. Signed-off-by: Richard Weinberger --- fs/fuse/file.c | 16 +++- fs/fuse/fuse_i.h | 16 2 files changed, 19 insertions(+), 13 deletions(-) diff --git a/fs/fuse/file.c b/fs/fuse/file.c index 8cccecb55fb8..

[PATCH 3/8] fuse: Make cuse_parse_one a common helper

This function will be used by MUSE too, let's share it. Signed-off-by: Richard Weinberger --- fs/fuse/Kconfig | 4 +++ fs/fuse/Makefile | 1 + fs/fuse/cuse.c | 58 +-- fs/fuse/fuse_i.h | 2 ++ fs/fuse/helper.c | 70 +++

[PATCH 4/8] mtd: Add MTD_MUSE flag

This flag will be set if an MTD is implemeted in userspace using MUSE. Signed-off-by: Richard Weinberger --- include/uapi/mtd/mtd-abi.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/uapi/mtd/mtd-abi.h b/include/uapi/mtd/mtd-abi.h index 65b9db936557..2ad2217e3a96 100644 --- a/includ

[PATCH 8/8] MAINTAINERS: Add entry for MUSE

Since MUSE lives in fs/fuse/, make sure that linux-mtd@ is CC'ed on patches such that MTD related aspects of changes can be reviewed. Signed-off-by: Richard Weinberger --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index f79ec98bbb29..dabd9fd

[PATCH 5/8] mtd: Allow passing a custom cmdline to cmdline line parser

The cmdline parser uses usually the mtdparts string from the kernel cmdline. For special purpose MTDs like MUSE it is useful to pass a custom mtdparts string to the parser. This allows the MTD simulator in userspace directly passing a mtdparts string and the new MTD partitioned. To achieve this, s

[PATCH 1/8] fuse: Export fuse_simple_request

MUSE will use this function to issue requests, so export it. Signed-off-by: Richard Weinberger --- fs/fuse/dev.c | 1 + 1 file changed, 1 insertion(+) diff --git a/fs/fuse/dev.c b/fs/fuse/dev.c index 588f8d1240aa..8b7209537683 100644 --- a/fs/fuse/dev.c +++ b/fs/fuse/dev.c @@ -522,6 +522,7 @@ s

[PATCH 6/8] fuse: Add MUSE specific defines FUSE interface

Raise the FUSE API minor version to 34 and add all MUSE specific operations and data structures. MUSE_INIT: Initialize a new connection and installs the MTD MUSE_ERASE: Erases a block MUSE_READ: Reads a page with or without OOB MUSE_WRITE: Writes a page with or without OOB MUSE_MARKBAD: Marks a bl

[PATCH 7/8] fuse: Implement MUSE - MTD in userspace

MUSE allows implementing a MTD in userspace. So far userspace has control over mtd_read, mtd_write, mtd_erase, mtd_block_isbad, mtd_block_markbad, and mtd_sync. It can also set the various MTD parameters such as name, flags, site, writesize and erasesize. That way advanced simulators for many type

Re: [PATCH v7 14/14] selftests/vm: test faulting in kernel, and verify pinnable pages

On 1/24/21 3:18 PM, John Hubbard wrote: On 1/21/21 7:37 PM, Pavel Tatashin wrote: When pages are pinned they can be faulted in userland and migrated, and they can be faulted right in kernel without migration. In either case, the pinned pages must end-up being pinnable (not movable). Add a new

Re: [PATCH] dsa: vsc73xx: add support for vlan filtering

On Mon, Jan 25, 2021 at 12:19:55AM +0100, Linus Walleij wrote: > This is due to the internal architecture of the switch, while it does > have an internal tagging format, this is stripped off before letting > it exit through the CPU port, and tagged on by the hardware > whenever the CPU transmits so

Re: [PATCH v13 04/12] mm: hugetlb: defer freeing of HugeTLB pages

On Sun, 17 Jan 2021, Muchun Song wrote: > In the subsequent patch, we should allocate the vmemmap pages when > freeing HugeTLB pages. But update_and_free_page() is always called > with holding hugetlb_lock, so we cannot use GFP_KERNEL to allocate > vmemmap pages. However, we can defer the actual f

Re: [PATCH v13 02/12] mm: hugetlb: introduce a new config HUGETLB_PAGE_FREE_VMEMMAP

On Sun, 17 Jan 2021, Muchun Song wrote: > The HUGETLB_PAGE_FREE_VMEMMAP option is used to enable the freeing > of unnecessary vmemmap associated with HugeTLB pages. The config > option is introduced early so that supporting code can be written > to depend on the option. The initial version of the

Re: [PATCH v13 05/12] mm: hugetlb: allocate the vmemmap pages associated with each HugeTLB page

On Sun, 17 Jan 2021, Muchun Song wrote: > diff --git a/mm/sparse-vmemmap.c b/mm/sparse-vmemmap.c > index ce4be1fa93c2..3b146d5949f3 100644 > --- a/mm/sparse-vmemmap.c > +++ b/mm/sparse-vmemmap.c > @@ -29,6 +29,7 @@ > #include > #include > #include > +#include > > #include > #include >

Re: [PATCH v13 06/12] mm: hugetlb: set the PageHWPoison to the raw error page

On Sun, 17 Jan 2021, Muchun Song wrote: > Because we reuse the first tail vmemmap page frame and remap it > with read-only, we cannot set the PageHWPosion on a tail page. > So we can use the head[4].private to record the real error page > index and set the raw error page PageHWPoison later. > > S

YOU HAVE WON

LOTTO.NL, 2391 Beds 152 Koningin Julianaplein 21, Den Haag-Netherlands. (Lotto affiliate with Subscriber Agents). From: Susan Console (Lottery Coordinator) Website: www.lotto.nl Sir/Madam, CONGRATULATIONS!!! We are pleased to inform you of the result of the Lotto NL Winners International progr

Re: [PATCH 1/4] ARM: dts: qcom: msm8974: add gpu support

On Sun, Jan 24, 2021 at 03:56:06PM +0100, Konrad Dybcio wrote: > Hi, > > > > + gpu_opp_table: opp_table { > > + status = "disabled"; > > > Is there a good reason to disable this? > > > > + opp-8 { > > + opp-hz = /

linux-next: manual merge of the bpf-next tree with the net-next tree

Hi all, Today's linux-next merge of the bpf-next tree got a conflict in: net/ipv4/tcp.c between commit: 7eeba1706eba ("tcp: Add receive timestamp support for receive zerocopy.") from the net-next tree and commit: 9cacf81f8161 ("bpf: Remove extra lock_sock for TCP_ZEROCOPY_RECEIVE") fro

linux-next: manual merge of the drm-intel tree with the drm tree

Hi all, Today's linux-next merge of the drm-intel tree got a conflict in: drivers/gpu/drm/i915/gem/i915_gem_object.h between commit: 41a9c75d0acf ("drm/i915/gem: Move stolen node into GEM object union") from the drm tree and commit: 5fbc2c2bfa5c ("drm/i915/gem: Add a helper to read data

Re: [PATCH 1/1] clk: aspeed: modify some default clks are critical

On Fri, 22 Jan 2021, at 18:45, Ryan Chen wrote: > Hello, > How about this patch progress? > It does impact a lot of machine that when BMC boot at u-boot. > SUART is work for Host. But after boot into kernel, due to the clk > disabled. > The SUART is not work for Host a

Re: linux-next: manual merge of the openrisc tree with Linus' tree

On Mon, Jan 25, 2021 at 09:05:06AM +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the openrisc tree got a conflict in: > > drivers/soc/litex/litex_soc_ctrl.c > > between commit: > > e6dc077b7dff ("soc: litex: Fix compile warning when device tree is not > configure

Linux 5.11-rc5

So this rc looked fairly calm and small, all the way up until today. In fact, over 40% of the non-merge commits came in today, as people unloaded their work for the week on me. The end result is a slightly larger than usual rc5 (but both 5.10 and 5.8 were bigger, so not some kind of odd outlier).

Re: [PATCH 3/4] ubifs: Update directory size when creating whiteouts

在 2021/1/23 10:45, Zhihao Cheng 写道: @@ -430,6 +433,7 @@ static int do_tmpfile(struct inode *dir, struct dentry *dentry,   return 0;   out_cancel: Still one question: Does this need a judgment? Like this, if (whiteout)     dir->i_size -= sz_change; +    dir->i_size -= sz_change;  

[PATCH] x86/entry/64: De-Xen-ify our NMI code further

From: Lai Jiangshan The commit 929bacec21478("x86/entry/64: De-Xen-ify our NMI code") simplified the NMI code by changing paravirt code into native code and left a comment about "inspecting RIP instead". But until now, "inspecting RIP instead" has not been made happened and this patch tries to c

Re: [PATCH BUGFIX/IMPROVEMENT 0/6] block, bfq: first bath of fixes and improvements

On 1/22/21 11:19 AM, Paolo Valente wrote: > Hi, > > about nine months ago, Jan (Kara, SUSE) reported a throughput > regression with BFQ. That was the beginning of a fruitful dev&testing > collaboration, which led to 18 new commits. Part are fixes, part are > actual performance improvements. Appli

[PATCH RESEND] dma-mapping: benchmark: fix kernel crash when dma_map_single fails

if dma_map_single() fails, kernel will give the below oops since task_struct has been destroyed and we are running into the memory corruption due to use-after-free in kthread_stop(): [ 48.095310] Unable to handle kernel paging request at virtual address 00c473548040 [ 48.095736] Mem abort

Re: linux-next: manual merge of the openrisc tree with Linus' tree

Hi Stafford, On Mon, 25 Jan 2021 10:04:46 +0900 Stafford Horne wrote: > > Thank's I knew about this conflict but I was not sure the best way to handle, > I > was/am going to rebase the openrisc/for-next branch onto 5.11-rc5 once > released. > I will resolve the conflict during the rebase so you

[PATCH v12 02/17] dmaengine: dw-axi-dmac: simplify descriptor management

Simplify and refactor the descriptor management by removing the redundant Linked List Item (LLI) queue control logic from the AxiDMA driver. The descriptor is split into virtual descriptor and hardware LLI so that only hardware LLI memories are allocated from the DMA memory pool. Up to 64 descript

[PATCH v12 00/17] dmaengine: dw-axi-dmac: support Intel KeemBay AxiDMA

The below patch series are to support AxiDMA running on Intel KeemBay SoC. The base driver is dw-axi-dmac. This driver only support DMA memory copy transfers. Code refactoring is needed so that additional features can be supported. The features added in this patch series are: - Replacing Linked Li

[PATCH v12 01/17] dt-bindings: dma: Add YAML schemas for dw-axi-dmac

YAML schemas Device Tree (DT) binding is the new format for DT to replace the old format. Introduce YAML schemas DT binding for dw-axi-dmac and remove the old version. Signed-off-by: Sia Jee Heng Reviewed-by: Eugeniy Paltsev Reviewed-by: Rob Herring --- .../bindings/dma/snps,dw-axi-dmac.txt

[PATCH v12 04/17] dmaengine: dw-axi-dmac: Add device_synchronize() callback

Add support for device_synchronize() callback function to sync with dmaengine_terminate_sync(). Signed-off-by: Sia Jee Heng Reviewed-by: Andy Shevchenko Reviewed-by: Eugeniy Paltsev Tested-by: Eugeniy Paltsev --- drivers/dma/dw-axi-dmac/dw-axi-dmac-platform.c | 8 1 file changed, 8 i

[PATCH v12 05/17] dmaengine: dw-axi-dmac: Add device_config operation

Add device_config() callback function so that the device address can be passed to the dma driver. DMA clients use this interface to pass in the device address to the AxiDMA. Without this interface, data transfer between device to memory and memory to device would failed. Signed-off-by: Sia Jee He

[PATCH v12 08/17] dmaengine: dw-axi-dmac: Support of_dma_controller_register()

Add support for of_dma_controller_register() so that DMA clients can pass in device handshake number to the AxiDMA driver. DMA clients shall code the device handshake number in the Device tree. When DMA activities are needed, DMA clients shall invoke OF helper function to pass in the device handsh

[PATCH v12 06/17] dmaengine: dw-axi-dmac: Support device_prep_slave_sg

Add device_prep_slave_sg() callback function so that DMA_MEM_TO_DEV and DMA_DEV_TO_MEM operations in single mode can be supported. Existing AxiDMA driver only support data transfer between memory to memory. Data transfer between device to memory and memory to device in single mode would failed if

[PATCH v12 11/17] dmaengine: dw-axi-dmac: Add Intel KeemBay DMA register fields

Add support for Intel KeemBay DMA registers. These registers are required to run data transfer between device to memory and memory to device on Intel KeemBay SoC. Signed-off-by: Sia Jee Heng Reviewed-by: Andy Shevchenko Reviewed-by: Eugeniy Paltsev Tested-by: Eugeniy Paltsev --- drivers/dma/d

[PATCH v12 15/17] dmaengine: dw-axi-dmac: Add Intel KeemBay AxiDMA BYTE and HALFWORD registers

Add support for Intel KeemBay AxiDMA BYTE and HALFWORD registers programming. Intel KeemBay AxiDMA supports data transfer between device to memory and memory to device operations. This code is needed by I2C, I3C, I2S, SPI and UART which uses FIFO size of 8bits and 16bits to perform memory to devi

[PATCH v12 16/17] dmaengine: dw-axi-dmac: Set constraint to the Max segment size

Add support for DMA Scatter-Gather (SG) constraint so that DMA clients can handle the AxiDMA limitation. Without supporting DMA constraint the default Max segment size reported by dmaengine is 64KB, which is not supported by Intel KeemBay AxiDMA. Signed-off-by: Sia Jee Heng Reviewed-by: Andy She

Re: [PATCH v2] bio: limit bio max size

> On Thu, Jan 21, 2021 at 09:58:03AM +0900, Changheun Lee wrote: > > bio size can grow up to 4GB when muli-page bvec is enabled. > > but sometimes it would lead to inefficient behaviors. > > in case of large chunk direct I/O, - 32MB chunk read in user space - > > all pages for 32MB would be merged

Re: linux-next: manual merge of the openrisc tree with Linus' tree

On Mon, Jan 25, 2021 at 12:47:46PM +1100, Stephen Rothwell wrote: > Hi Stafford, > > On Mon, 25 Jan 2021 10:04:46 +0900 Stafford Horne wrote: > > > > Thank's I knew about this conflict but I was not sure the best way to > > handle, I > > was/am going to rebase the openrisc/for-next branch onto 5

[PATCH v2 resend] iio: imu: bmi160: add mutex_lock for avoiding race

From: chiguoqing Adding mutex_lock, when read and write reg need to use this lock to avoid race. Signed-off-by: Guoqing Chi Reviewed-by: Tom Rix --- v2:Follow write function to fix read function. Adding mutex init in core probe function. Adding break in switch case at read and write function.

Re: [PATCH] mm: Fix potential pte_unmap_unlock pte error

Hi: On 2021/1/24 10:01, Andrew Morton wrote: > On Fri, 22 Jan 2021 16:27:23 +0800 Miaohe Lin wrote: > >> Hi Andrew: >> On 2021/1/14 10:51, Miaohe Lin wrote: >>> Hi: >>> On 2021/1/11 1:14, Andi Kleen wrote: On Sat, Jan 09, 2021 at 03:01:18AM -0500, Miaohe Lin wrote: > Since commit 42e4089

Re: Anyone have ideas for checkpatch improvements ?

One of the linux-mentees, Dwaipayan Ray, asked me in a private email for ideas for improvements to checkpatch. Though I am not his nominal mentor, my response to him was the below. Does anyone have any more ideas for checkpatch improvements or enhancements? --- On Fri, 2021-01-15 at 21:02 +0530

回复: 回复: [PATCH 3/3] kvfree_rcu: use migrate_disable/enable()

发件人: Uladzislau Rezki 发送时间: 2021年1月25日 5:57 收件人: Zhang, Qiang 抄送: Uladzislau Rezki (Sony); LKML; RCU; Paul E . McKenney; Michael Ellerman; Andrew Morton; Daniel Axtens; Frederic Weisbecker; Neeraj Upadhyay; Joel Fernandes; Peter Zijlstra; Michal Hocko; T

[PATCH v12 03/17] dmaengine: dw-axi-dmac: move dma_pool_create() to alloc_chan_resources()

The DMA memory block is created at driver load time and exist for device lifetime. Move the dma_pool_create() to the ->chan_resource() callback function allowing the DMA memory blocks to be created as needed and destroyed when the channel is freed. Signed-off-by: Sia Jee Heng Reviewed-by: Andy Sh

Anyone have ideas for checkpatch improvements ?

[PATCH v12 17/17] dmaengine: dw-axi-dmac: Virtually split the linked-list

AxiDMA driver exposed the dma_set_max_seg_size() to the DMAENGINE. It shall helps the DMA clients to create size-optimized linked-list for the controller. However, there are certain situations where DMA client might not be abled to benefit from the dma_get_max_seg_size() if the segment size can't

RE: [PATCH 1/1] sched/topology: Make sched_init_numa() use a set for the deduplicating sort

> -Original Message- > From: Valentin Schneider [mailto:valentin.schnei...@arm.com] > Sent: Saturday, January 23, 2021 1:40 AM > To: linux-kernel@vger.kernel.org > Cc: mi...@kernel.org; pet...@infradead.org; vincent.guit...@linaro.org; > dietmar.eggem...@arm.com; morten.rasmus...@arm.com;

Re: [PATCH] x86_64: move cpu_current_top_of_stack out of TSS

On Fri, Jan 22, 2021 at 11:48 PM Lai Jiangshan wrote: > > From: Lai Jiangshan > > When X86_BUG_CPU_MELTDOWN & KPTI, cpu_current_top_of_stack lives in the > TSS which is also in the user CR3 and it becomes a coveted fruit. An > attacker can fetch the kernel stack top from it and continue next ste

[PATCH v12 14/17] dmaengine: dw-axi-dmac: Add Intel KeemBay AxiDMA handshake

Add support for Intel KeemBay AxiDMA device handshake programming. Device handshake number passed in to the AxiDMA shall be written to the Intel KeemBay AxiDMA hardware handshake registers before DMA operations are started. Signed-off-by: Sia Jee Heng Reviewed-by: Andy Shevchenko Reviewed-by: Eu

[PATCH v12 12/17] dmaengine: drivers: Kconfig: add HAS_IOMEM dependency to DW_AXI_DMAC

If HAS_IOMEM is not defined and DW_AXI_DMAC is enabled under COMPILE_TEST, the build fails with the following error: dw-axi-dmac-platform.c:(.text+0xc4): undefined reference to `devm_ioremap_resource' Link: https://www.spinics.net/lists/dmaengine/msg25188.html Reported-by: kernel test robot Signe

[PATCH v12 13/17] dmaengine: dw-axi-dmac: Add Intel KeemBay AxiDMA support

Add support for Intel KeemBay AxiDMA to the .compatible field. The AxiDMA Apb region will be accessible if the compatible string matches the "intel,kmb-axi-dma". Signed-off-by: Sia Jee Heng Reviewed-by: Andy Shevchenko Reviewed-by: Eugeniy Paltsev Tested-by: Eugeniy Paltsev --- drivers/dma/dw

[PATCH v12 10/17] dt-binding: dma: dw-axi-dmac: Add support for Intel KeemBay AxiDMA

Add support for Intel KeemBay AxiDMA to the dw-axi-dmac Schemas DT binding. Signed-off-by: Sia Jee Heng Reviewed-by: Eugeniy Paltsev Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/dma/snps,dw-axi-dmac.yaml | 5 + 1 file changed, 5 insertions(+) diff --git a/Documentation/d

[PATCH v12 09/17] dmaengine: dw-axi-dmac: Support burst residue granularity

Add support for DMA_RESIDUE_GRANULARITY_BURST so that AxiDMA can report DMA residue. Existing AxiDMA driver only support data transfer between memory to memory operation, therefore reporting DMA residue to the DMA clients is not supported. Reporting DMA residue to the DMA clients is important as

回复: 回复: [PATCH 3/3] kvfree_rcu: use migrate_disable/enable()

发件人: Uladzislau Rezki 发送时间: 2021年1月25日 5:57 收件人: Zhang, Qiang 抄送: Uladzislau Rezki (Sony); LKML; RCU; Paul E . McKenney; Michael Ellerman; Andrew Morton; Daniel Axtens; Frederic Weisbecker; Neeraj Upadhyay; Joel Fernandes; Peter Zijlstra; Michal Hocko;

[PATCH v12 07/17] dmaegine: dw-axi-dmac: Support device_prep_dma_cyclic()

Add support for device_prep_dma_cyclic() callback function to benefit DMA cyclic client, for example ALSA. Existing AxiDMA driver only support data transfer between memory to memory. Data transfer between device to memory and memory to device in cyclic mode would failed if this interface is not su

[PATCH] bridge: Use PTR_ERR_OR_ZERO instead if(IS_ERR(...)) + PTR_ERR

coccicheck suggested using PTR_ERR_OR_ZERO() and looking at the code. Fix the following coccicheck warnings: ./net/bridge/br_multicast.c:1295:7-13: WARNING: PTR_ERR_OR_ZERO can be used. Reported-by: Abaci Signed-off-by: Jiapeng Zhong --- net/bridge/br_multicast.c | 2 +- 1 file changed, 1 ins

Re: [PATCH RESEND V11 0/7] fuse: Add support for passthrough read/write

On 1/22/21 7:06 PM, Alessio Balsini wrote: On Tue, Jan 19, 2021 at 12:34:23PM +, Alessio Balsini wrote: On Tue, Jan 19, 2021 at 07:06:54PM +0800, Rokudo Yan wrote: on Mon, Jan 18, 2021 at 5:27 PM Alessio Balsini wrote: This is the 11th version of the series, rebased on top of v5.11-rc4.

Re: [PATCH v3 00/17] KVM: x86/pmu: Add support to enable Guest PEBS via DS

+ k...@vger.kernel.org Hi Liuxiangdong, On 2021/1/22 18:02, Liuxiangdong (Aven, Cloud Infrastructure Service Product Dept.) wrote: Hi Like, Some questions about https://lore.kernel.org/kvm/20210104131542.495413-1-like...@linux.intel.com/

[PATCH] vfio/iommu_type1: Mantainance a counter for non_pinned_groups

With this counter, we never need to traverse all groups to update pinned_scope of vfio_iommu. Suggested-by: Alex Williamson Signed-off-by: Keqian Zhu --- drivers/vfio/vfio_iommu_type1.c | 40 + 1 file changed, 5 insertions(+), 35 deletions(-) diff --git a/driver

Re: [PATCH v13 01/12] mm: memory_hotplug: factor out bootmem core functions to bootmem_info.c

Hi: On 2021/1/17 23:10, Muchun Song wrote: > Move bootmem info registration common API to individual bootmem_info.c. > And we will use {get,put}_page_bootmem() to initialize the page for the > vmemmap pages or free the vmemmap pages to buddy in the later patch. > So move them out of CONFIG_MEMORY_H

[PATCH V4 0/4] mm/memory_hotplug: Pre-validate the address range with platform

This series adds a mechanism allowing platforms to weigh in and prevalidate incoming address range before proceeding further with the memory hotplug. This helps prevent potential platform errors for the given address range, down the hotplug call chain, which inevitably fails the hotplug itself. Th

[PATCH V4 1/4] mm/memory_hotplug: Prevalidate the address range being added with platform

This introduces mhp_range_allowed() which can be called in various memory hotplug paths to prevalidate the address range which is being added, with the platform. Then mhp_range_allowed() calls mhp_get_pluggable_range() which provides applicable address range depending on whether linear mapping is r

[PATCH V4 2/4] arm64/mm: Define arch_get_mappable_range()

This overrides arch_get_mappable_range() on arm64 platform which will be used with recently added generic framework. It drops inside_linear_region() and subsequent check in arch_add_memory() which are no longer required. It also adds a VM_BUG_ON() check that would ensure that mhp_range_allowed() ha

[PATCH V4 4/4] virtio-mem: check against mhp_get_pluggable_range() which memory we can hotplug

From: David Hildenbrand Right now, we only check against MAX_PHYSMEM_BITS - but turns out there are more restrictions of which memory we can actually hotplug, especially om arm64 or s390x once we support them: we might receive something like -E2BIG or -ERANGE from add_memory_driver_managed(), sto

[PATCH V4 3/4] s390/mm: Define arch_get_mappable_range()

This overrides arch_get_mappabble_range() on s390 platform which will be used with recently added generic framework. It modifies the existing range check in vmem_add_mapping() using arch_get_mappable_range(). It also adds a VM_BUG_ON() check that would ensure that mhp_range_allowed() has already be

Re: [PATCH] x86/entry/64: De-Xen-ify our NMI code further

On Sun, Jan 24, 2021 at 5:13 PM Lai Jiangshan wrote: > > From: Lai Jiangshan > > The commit 929bacec21478("x86/entry/64: De-Xen-ify our NMI code") simplified > the NMI code by changing paravirt code into native code and left a comment > about "inspecting RIP instead". But until now, "inspecting

Re: [PATCH v3] soc/tegra: Add devm_tegra_core_dev_init_opp_table()

On 22-01-21, 17:41, Dmitry Osipenko wrote: > 22.01.2021 09:35, Viresh Kumar пишет: > > On 21-01-21, 22:01, Dmitry Osipenko wrote: > >> Add common helper which initializes OPP table for Tegra SoC core devices. > >> > >> Tested-by: Peter Geis # Ouya T30 > >> Tested-by: Dmitry Osipenko # A500 T20 an

Re: [PATCH] memory: tegra: Remove calls to dev_pm_opp_set_clkname()

On 22-01-21, 18:00, Dmitry Osipenko wrote: > 22.01.2021 09:00, Viresh Kumar пишет: > > There is no point calling dev_pm_opp_set_clkname() with the "name" > > parameter set to NULL, this is already done by the OPP core at setup > > time and should work as it is. > > > > Signed-off-by: Viresh Kumar

Re: [PATCH 03/13] opp: Keep track of currently programmed OPP

On 22-01-21, 17:31, Dmitry Osipenko wrote: > This may not be true for all kinds of hardware, a display controller is > one example. If display's pixclock is raised before the memory bandwidth > of the display's memory client, then display controller may get a memory > underflow since it won't be ab

Re: [PATCH v2 1/1] vhost scsi: alloc vhost_scsi with kvzalloc() to avoid delay

On 2021/1/23 下午4:08, Dongli Zhang wrote: The size of 'struct vhost_scsi' is order-10 (~2.3MB). It may take long time delay by kzalloc() to compact memory pages by retrying multiple times when there is a lack of high-order pages. As a result, there is latency to create a VM (with vhost-scsi) or

RE: [RFC PATCH] sched/fair: first try to fix the scheduling impact of NUMA diameter > 2

> > > > > > Hi, > > > > On 18/01/21 11:25, Song Bao Hua wrote: > > >> -Original Message- > > >> From: Vincent Guittot [mailto:vincent.guit...@linaro.org] > > >> Sent: Tuesday, January 19, 2021 12:14 AM > > >> To: Song Bao Hua (Barry Song) > > >> Cc: Ingo Molnar ; Peter Zijlstra > > >> ; >

RE: [PATCH v2] tracing: precise log info for kretprobe addr err

Hi Masami, Thanks for your comments, it is very helpful to me. Hi Steven, Could you give me more detailed suggestions about the UPROBES section? I lack the knowledge of this part. Can't fully understand your previous comments; Thanks all for your patience. Jianlin > -Original Message

Re: [PATCH 11/13] devfreq: tegra30: Migrate to dev_pm_opp_set_opp()

On 22-01-21, 18:28, Dmitry Osipenko wrote: > Either way will work, but maybe keeping the dev_pm_opp_set_bw() is a bit > more straightforward variant for now since it will avoid the code's > changes and it's probably a bit more obvious variant for the OPP users. The problem is it creates unnecessar

[PATCH] pinctrl: mediatek: Fix trigger type setting follow for unexpected interrupt

When flipping the polarity will be generated interrupt under certain circumstances, but GPIO external signal has not changed. Then, mask the interrupt before polarity setting, and clear the unexpected interrupt after trigger type setting completed. Signed-off-by: Hailong Fan --- [V2] --- drivers

Re: [PATCH V6 2/6] scripts: dtc: Build fdtoverlay tool

On 23-01-21, 11:35, David Gibson wrote: > On Fri, Jan 22, 2021 at 04:20:32PM +0530, Viresh Kumar wrote: > > We will start building overlays for platforms soon in the kernel and > > would need fdtoverlay going forward. Lets start building it. > > > > The fdtoverlay program applies (or merges) one o

Re: [PATCH v13 02/12] mm: hugetlb: introduce a new config HUGETLB_PAGE_FREE_VMEMMAP

On 1/24/21 3:58 PM, David Rientjes wrote: > On Sun, 17 Jan 2021, Muchun Song wrote: > >> The HUGETLB_PAGE_FREE_VMEMMAP option is used to enable the freeing >> of unnecessary vmemmap associated with HugeTLB pages. The config >> option is introduced early so that supporting code can be written >> to

Re: [PATCH V6 5/6] of: unittest: Create overlay_common.dtsi and testcases_common.dtsi

On 23-01-21, 14:07, David Gibson wrote: > On Fri, Jan 22, 2021 at 04:20:35PM +0530, Viresh Kumar wrote: > > In order to build-test the same unit-test files using fdtoverlay tool, > > move the device nodes from the existing overlay_base.dts and > > testcases_common.dts files to .dtsi files. The .dts

Re: [PATCH RESEND] pinctrl: mediatek: Fix trigger type setting follow for unexpected interrupt

On Fri, 2021-01-22 at 18:54 +0800, Nicolas Boichat wrote: > On Fri, Jan 22, 2021 at 10:44 AM mtk15103 wrote: > > > > On Thu, 2021-01-21 at 20:13 +0800, Nicolas Boichat wrote: > > > On Thu, Jan 21, 2021 at 8:09 PM mtk15103 wrote: > > > > > > > > On Thu, 2021-01-21 at 16:55 +0800, Nicolas Boichat w

Re: [PATCH 21/21] vdpasim: control virtqueue support

On 2021/1/23 上午3:43, Eugenio Perez Martin wrote: On Tue, Jan 12, 2021 at 4:12 AM Jason Wang wrote: On 2021/1/11 下午8:26, Eli Cohen wrote: On Wed, Dec 16, 2020 at 02:48:18PM +0800, Jason Wang wrote: This patch introduces the control virtqueue support for vDPA simulator. This is a requirement

Re: [PATCH v2 1/2] dt-bindings: drm/bridge: anx7625: add DPI flag and swing setting

On Sat, Jan 23, 2021 at 12:16:02AM +0800, Rob Herring wrote: > On Tue, Jan 12, 2021 at 2:57 AM Xin Ji wrote: > > > > Hi Rob Herring, thanks for the comments. > > > > On Mon, Jan 11, 2021 at 04:14:35PM -0600, Rob Herring wrote: > > > On Thu, Dec 31, 2020 at 10:21:12AM +0800, Xin Ji wrote: > > > > A

[PATCH v2] pinctrl: mediatek: Fix trigger type setting follow for unexpected interrupt

When flipping the polarity will be generated interrupt under certain circumstances, but GPIO external signal has not changed. Then, mask the interrupt before polarity setting, and clear the unexpected interrupt after trigger type setting completed. Signed-off-by: Hailong Fan Reviewed-by: Nicolas

[PATCH] mm/filemap: Remove redundant variable's assignment

We've already set the variable 'i' 's initial value before using it, thus remove redundant previous assignment of variable 'i'. Signed-off-by: Baolin Wang --- mm/filemap.c | 1 - 1 file changed, 1 deletion(-) diff --git a/mm/filemap.c b/mm/filemap.c index e4906f5..07b02f3 100644 --- a/mm/filema

Re: [PATCH] pinctrl: mediatek: Fix trigger type setting follow for unexpected interrupt

On Mon, Jan 25, 2021 at 11:15 AM Hailong Fan wrote: > > When flipping the polarity will be generated interrupt under certain > circumstances, but GPIO external signal has not changed. > Then, mask the interrupt before polarity setting, and clear the > unexpected interrupt after trigger type settin

Re: kernel BUG in split_huge_page_to_list

On 1/24/21 8:01 PM, syzbot wrote: Hello, syzbot found the following issue on: HEAD commit:647060f3 Add linux-next specific files for 20210120 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=16f0353f50 kernel config: https://syzkaller.appspot.com/

arch/mips/pci/ops-loongson2.c:39:6: warning: variable 'dummy' set but not used

Hi Jiaxun, First bad commit (maybe != root cause): tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 6ee1d745b7c9fd573fba142a2efdad76a9f1cb04 commit: b13812ddea615b6507beef24f76540c0c1143c5c MIPS: Loongson2ef: Disable Loongson MMI instructions date: 4 m

Re: [PATCH 05/14] rtc: ds1685: use rtc_lock/rtc_unlock

On 1/19/2021 17:06, Alexandre Belloni wrote: > Avoid accessing directly rtc->ops_lock and use the RTC core helpers. > > Signed-off-by: Alexandre Belloni > --- > drivers/rtc/rtc-ds1685.c | 6 ++ > 1 file changed, 2 insertions(+), 4 deletions(-) > > diff --git a/drivers/rtc/rtc-ds1685.c b/dri

Re: [PATCH] power: supply: axp20x_usb_power: Init work before enabling IRQs

On Sun, Jan 24, 2021 at 11:24 PM Samuel Holland wrote: > > The IRQ handler calls mod_delayed_work() on power->vbus_detect. However, > that work item is not initialized until after the IRQs are enabled. If > an IRQ is already pending when the driver is probed, the driver calls > mod_delayed_work()

Re: [PATCH] nitro_enclaves: set master in the procedure of NE probe

在 2021/1/20 18:27, Paraschiv, Andra-Irina 写道: > > > On 19/01/2021 05:30, Longpeng(Mike) wrote: >> According the PCI spec: >>    Bus Master Enable – Controls the ability of a PCI Express >>    Endpoint to issue Memory and I/O Read/Write Requests, and >>    the ability of a Root or Switch Port t

Re: Linux 5.11-rc5

On Sun, Jan 24, 2021 at 05:06:40PM -0800, Linus Torvalds wrote: > So this rc looked fairly calm and small, all the way up until today. > > In fact, over 40% of the non-merge commits came in today, as people > unloaded their work for the week on me. The end result is a slightly > larger than usual

Re: Linux 5.11-rc5

On 19:48 Sun 24 Jan 2021, Guenter Roeck wrote: On Sun, Jan 24, 2021 at 05:06:40PM -0800, Linus Torvalds wrote: So this rc looked fairly calm and small, all the way up until today. In fact, over 40% of the non-merge commits came in today, as people unloaded their work for the week on me. The end

Re: [External] Re: [PATCH v13 04/12] mm: hugetlb: defer freeing of HugeTLB pages

On Mon, Jan 25, 2021 at 7:55 AM David Rientjes wrote: > > > On Sun, 17 Jan 2021, Muchun Song wrote: > > > In the subsequent patch, we should allocate the vmemmap pages when > > freeing HugeTLB pages. But update_and_free_page() is always called > > with holding hugetlb_lock, so we cannot use GFP_KE

[PATCH] PM: remove PF_WQ_WORKER mask

From: Zqiang Due to kworker also is kernel thread, it's already included PF_KTHREAD mask, so remove PF_WQ_WORKER mask. Signed-off-by: Zqiang --- kernel/power/process.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/power/process.c b/kernel/power/process.c index 45b0

<    1   2   3   4   5   >