Re: kernfs: can read/write method grow buffer size?

On Fri, Mar 29, 2019 at 07:51:07AM +0100, Marek Behun wrote: > > If this is just for kernfs, and you have your own filesystem, sure, we > > can probably do something here. But if this is for sysfs, no, you all > > need to keep to the "one value per file" rule that we have there > > please. > > Gr

Re: kernfs: can read/write method grow buffer size?

> If this is just for kernfs, and you have your own filesystem, sure, we > can probably do something here. But if this is for sysfs, no, you all > need to keep to the "one value per file" rule that we have there > please. Greg, the file satisfies the "one value per file" rule. That value is the c

Re: [PATCH] RISC-V: Fix FIXMAP_TOP to avoid overlap with VMALLOC area

Hi Palmer, On Fri, Mar 29, 2019 at 11:48 AM Palmer Dabbelt wrote: > > On Fri, 22 Mar 2019 06:25:09 PDT (-0700), Christoph Hellwig wrote: > > Looks good, > > > > Reviewed-by: Christoph Hellwig > > Thanks. I've added this to my fixes list for the next RC. I have another RC fix as well: "[PATCH

[PATCH v3 7/9] ARM: dts: imx53: Specify IMX5_CLK_IPG as "ahb" clock to SDMA

Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX5_CLK_SDMA results in driver incorrectly thinking that ratio is 1:1 which resu

[PATCH v3 8/9] ARM: dts: imx51: Specify IMX5_CLK_IPG as "ahb" clock to SDMA

Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX5_CLK_SDMA results in driver incorrectly thinking that ratio is 1:1 which resu

[PATCH v3 4/9] ARM: dts: imx6ul: Specify IMX6UL_CLK_IPG as "ipg" clock to SDMA

Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX6UL_CLK_SDMA results in driver incorrectly thinking that ratio is 1:1 which re

[PATCH v3 9/9] ARM: dts: imx50: Specify IMX5_CLK_IPG as "ahb" clock to SDMA

Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX5_CLK_SDMA results in driver incorrectly thinking that ratio is 1:1 which resu

[PATCH v3 2/9] ARM: dts: imx6sx: Specify IMX6SX_CLK_IPG as "ipg" clock to SDMA

Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX6SX_CLK_SDMA results in driver incorrectly thinking that ratio is 1:1 which re

[PATCH v3 3/9] ARM: dts: imx7d: Specify IMX7D_CLK_IPG as "ipg" clock to SDMA

Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX7D_CLK_SDMA results in driver incorrectly thinking that ratio is 1:1 which res

[PATCH v3 5/9] ARM: dts: imx6sll: Specify IMX6SLL_CLK_IPG as "ipg" clock to SDMA

Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX6SLL_CLK_SDMA result in driver incorrectly thinking that ratio is 1:1 which re

[PATCH v3 6/9] ARM: dts: imx6sx: Specify IMX6SX_CLK_IPG as "ahb" clock to SDMA

Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX6SL_CLK_SDMA results in driver incorrectly thinking that ratio is 1:1 which re

[PATCH v3 1/9] ARM: dts: imx6qdl: Specify IMX6QDL_CLK_IPG as "ipg" clock to SDMA

Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX6QDL_CLK_SDMA results in driver incorrectly thinking that ratio is 1:1 which r

[tip:efi/core] efi/libstub/arm: Omit unneeded stripping of ksymtab/kcrctab sections

Commit-ID: 02562d0ca1084a688ac5c92e0e92947f62f13093 Gitweb: https://git.kernel.org/tip/02562d0ca1084a688ac5c92e0e92947f62f13093 Author: Ard Biesheuvel AuthorDate: Thu, 28 Mar 2019 20:34:29 +0100 Committer: Ingo Molnar CommitDate: Fri, 29 Mar 2019 07:35:00 +0100 efi/libstub/arm: Omit un

[tip:efi/core] efi: Unify DMI setup code over the arm/arm64, ia64 and x86 architectures

Commit-ID: 0fca08122eaf5c956a2cbe12775245d747f8b1ac Gitweb: https://git.kernel.org/tip/0fca08122eaf5c956a2cbe12775245d747f8b1ac Author: Robert Richter AuthorDate: Thu, 28 Mar 2019 20:34:28 +0100 Committer: Ingo Molnar CommitDate: Fri, 29 Mar 2019 07:35:00 +0100 efi: Unify DMI setup cod

[tip:efi/core] efi/arm: Show SMBIOS bank/device location in CPER and GHES error logs

Commit-ID: 5e83cfe947444c7f201f8c39ce0189922ec9f578 Gitweb: https://git.kernel.org/tip/5e83cfe947444c7f201f8c39ce0189922ec9f578 Author: Marcin Benka AuthorDate: Thu, 28 Mar 2019 20:34:27 +0100 Committer: Ingo Molnar CommitDate: Fri, 29 Mar 2019 07:35:00 +0100 efi/arm: Show SMBIOS bank/

Re: [PATCH v2 0/4] Clean up comments and codes in sparse_add_one_section()

Talked to Michal, the local code refactorying may impact those big feature or improvement patchset, e.g patch 2/4 and patch 3/4 will conflict with Dan's patchset: [PATCH v5 00/10] mm: Sub-section memory hotplug support So I would like to discard them and only repost patch 1/4 and 4/4 after address

[tip:efi/core] efifb: Omit memory map check on legacy boot

Commit-ID: c2999c281ea2d2ebbdfce96cecc7b52e2ae7c406 Gitweb: https://git.kernel.org/tip/c2999c281ea2d2ebbdfce96cecc7b52e2ae7c406 Author: Ard Biesheuvel AuthorDate: Thu, 28 Mar 2019 20:34:26 +0100 Committer: Ingo Molnar CommitDate: Fri, 29 Mar 2019 07:34:59 +0100 efifb: Omit memory map c

[RFC PATCH] drm/komeda: Creates plane alpha and blend mode properties

Creates plane alpha and blend mode properties attached to plane. Signed-off-by: Lowry Li --- drivers/gpu/drm/arm/display/komeda/komeda_plane.c | 11 +++ 1 file changed, 11 insertions(+) diff --git a/drivers/gpu/drm/arm/display/komeda/komeda_plane.c b/drivers/gpu/drm/arm/display/komeda/

[tip:efi/core] efi/libstub: Refactor the cmd_stubcopy Makefile command

Commit-ID: e8d368ad20f514dce86a64931fe4a6f06a0a6703 Gitweb: https://git.kernel.org/tip/e8d368ad20f514dce86a64931fe4a6f06a0a6703 Author: Masahiro Yamada AuthorDate: Thu, 28 Mar 2019 20:34:25 +0100 Committer: Ingo Molnar CommitDate: Fri, 29 Mar 2019 07:34:59 +0100 efi/libstub: Refactor t

Re: [PATCH] ARM: dts: imx6qdl: Specify IMX6QDL_CLK_IPG as "ipg" clock for SDMA

On Wed, Mar 27, 2019 at 4:17 AM Fabio Estevam wrote: > > Hi Andrey, > > On Tue, Mar 26, 2019 at 11:52 PM Andrey Smirnov > wrote: > > > I think it is worth fixing in DT, regardless if we do anything about > > SDMA driver or not. I'll add fixes for 6SX and 7D in v2. > > What about imx25, imx31, imx

Re: [PATCHv2] x86/boot/KASLR: skip the specified crashkernel reserved region

On 03/29/19 at 01:45pm, Pingfan Liu wrote: > On Fri, Mar 22, 2019 at 4:34 PM Baoquan He wrote: > > > > On 03/22/19 at 03:52pm, Baoquan He wrote: > > > On 03/22/19 at 03:43pm, Pingfan Liu wrote: > > > > > > +/* parse crashkernel=x@y option */ > > > > > > +static void mem_avoid_crashkernel_simple(ch

Re: kernfs: can read/write method grow buffer size?

On Fri, Mar 29, 2019 at 04:09:22AM +0100, Marek Behun wrote: > Hello Tejun and Greg, > > kernfs_fop_open/read/write allocates a buffer for the ->read, ->write, > or ->seq_read methods. This buffer is either preallocated or allocated > on the spot, with minimum size being PAGE_SIZE, if ->atomic_wri

[PATCH v2] irqchip/irq-ls1x: Missing error code in ls1x_intc_of_init()

Currently, when irq_domain_add_linear() fails, the error code does not get so it returns zero which is wrong. Fix it by setting appropriate error code. Fixes: 9e543e22e204 ("irqchip: Add driver for Loongson-1 interrupt controller") Signed-off-by: Dan Carpenter Reviewed-by: Mukesh Ojha --- V2: I

Re: [PATCH] RISC-V: Fix FIXMAP_TOP to avoid overlap with VMALLOC area

On Fri, 22 Mar 2019 06:25:09 PDT (-0700), Christoph Hellwig wrote: Looks good, Reviewed-by: Christoph Hellwig Thanks. I've added this to my fixes list for the next RC. Btw, what is the 32-bit test vehicle of choice? qemu with the virt machine?

Re: [PATCH v3 3/5] dt-bindings: phy: ti: Add dt binding documentation for SERDES in AM654x SoC

Hi Rob, On 28/03/19 11:37 PM, Rob Herring wrote: > On Mon, Mar 25, 2019 at 01:38:13PM +0530, Kishon Vijay Abraham I wrote: >> AM654x has two SERDES instances. Each instance has three input clocks >> (left input, externel reference clock and right input) and two output >> clocks (left output and ri

RE: [PATCHv4 16/28] PCI: mobiveil: refactor Mobiveil PCIe Host Bridge IP driver

Hi Lorenzo, Thanks a lot for your comments! > -Original Message- > From: Lorenzo Pieralisi > Sent: 2019年3月29日 0:09 > To: Z.q. Hou > Cc: linux-...@vger.kernel.org; linux-arm-ker...@lists.infradead.org; > devicet...@vger.kernel.org; linux-kernel@vger.kernel.org; > bhelg...@google.com; rob

Re: [PATCH v2] HID: intel-ish-hid: ISH firmware loader client driver

This is so close! There are just one or two tiny things. On Thu, Mar 28, 2019 at 1:20 PM Rushikesh S Kadam wrote: > > This driver adds support for loading Intel Integrated > Sensor Hub (ISH) firmware from host file system to ISH > SRAM and start execution. > > At power-on, the ISH subsystem shall

Re: [PATCH 1/2] kernel.h: use parentheses around argument in u64_to_user_ptr()

On 3/29/2019 2:53 AM, Jann Horn wrote: Use parentheses around uses of the argument in u64_to_user_ptr() to ensure that the cast doesn't apply to part of the argument. There are existing uses of the macro of the form `u64_to_user_ptr(A + B)`, which expands to `(void __user *)(uintptr_t)A + B` (

Re: [PATCHv2] x86/boot/KASLR: skip the specified crashkernel reserved region

On Fri, Mar 22, 2019 at 4:34 PM Baoquan He wrote: > > On 03/22/19 at 03:52pm, Baoquan He wrote: > > On 03/22/19 at 03:43pm, Pingfan Liu wrote: > > > > > +/* parse crashkernel=x@y option */ > > > > > +static void mem_avoid_crashkernel_simple(char *option) > > > > > > > > Chao ever mentioned this, I

Re: Page-allocation-failure

From: Pankaj Suryawanshi Sent: 28 March 2019 13:17 To: linux-kernel@vger.kernel.org; linux...@kvack.org Subject: Re: Page-allocation-failure From: Pankaj Suryawanshi Sent: 28 March 2019 13:12 To: linux-kernel@vger

Re: [PATCH 4/4] leds: lm3532: Introduce the lm3532 LED driver

Hi, On Mon, Mar 25, 2019 at 11:01:18AM -0500, Dan Murphy wrote: > On 3/25/19 9:54 AM, Tony Lindgren wrote: > > * Dan Murphy [190325 12:36]: > >> On 3/22/19 5:16 PM, Tony Lindgren wrote: > >>> I can control the backlight brightness just fine via /sys, and > >>> backlight shows up as the trigger in

Re: [PATCH 2/2] ARM: dts: Add support for ZII i.MX7 RPU2 board

On Tue, Mar 26, 2019 at 11:41 PM Andrey Smirnov wrote: > > Add support for ZII's i.MX7 based Remote Peripheral Unit 2 (RPU2) > board. > > Signed-off-by: Andrey Smirnov > Cc: Shawn Guo > Cc: Chris Healy > Cc: Andrew Lunn > Cc: Fabio Estevam > Cc: Rob Herring > Cc: linux-kernel@vger.kernel.org

Re: [PATCH 1/2] platform/x86: intel_pmc_core: Convert to a platform_driver

Hi Srinivas, On Thu, Mar 28, 2019 at 8:41 PM Srinivas Pandruvada wrote: > > On Mon, 2019-03-25 at 18:41 -0700, Rajat Jain wrote: > > Hi Rajneesh, > > > > > > On Mon, Mar 25, 2019 at 3:23 AM Bhardwaj, Rajneesh > > wrote: > > > > > > Hi Rajat > > > > > > On 23-Mar-19 6:00 AM, Rajat Jain wrote: >

Re: [External] Re: vmscan: Reclaim unevictable pages

From: Michal Hocko Sent: 26 March 2019 15:06 To: Pankaj Suryawanshi Cc: Kirill Tkhai; Vlastimil Babka; aneesh.ku...@linux.ibm.com; linux-kernel@vger.kernel.org; minc...@kernel.org; linux...@kvack.org; khand...@linux.vnet.ibm.com Subject: Re: [External]

Re: [PATCH REBASED] hugetlbfs: fix potential over/underflow setting node specific nr_hugepages

On Thu, Mar 28, 2019 at 03:05:33PM -0700, Mike Kravetz wrote: > The number of node specific huge pages can be set via a file such as: > /sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages > When a node specific value is specified, the global number of huge > pages must also be ad

Re: [External] Re: Print map for total physical and virtual memory

From: Matthew Wilcox Sent: 26 March 2019 18:13 To: Pankaj Suryawanshi Cc: linux-kernel@vger.kernel.org; linux...@kvack.org Subject: Re: [External] Re: Print map for total physical and virtual memory On Tue, Mar 26, 2019 at 12:35:25PM +, Pankaj Suryaw

RE: [LINUX PATCH v13] rawnand: pl353: Add basic driver for arm pl353 smc nand interface

Hi Helmut, > -Original Message- > From: Helmut Grohne > Sent: Thursday, March 28, 2019 5:21 PM > To: Naga Sureshkumar Relli > Cc: bbrezil...@kernel.org; miquel.ray...@bootlin.com; rich...@nod.at; > dw...@infradead.org; computersforpe...@gmail.com; marek.va...@gmail.com; > linux- > m...@

Re: [PATCH v2] RISC-V: Implement ASID allocator

On Fri, Mar 29, 2019 at 10:34 AM Paul Walmsley wrote: > > > On Thu, 28 Mar 2019, Anup Patel wrote: > > > Signed-off-by: Gary Guo > > Signed-off-by: Anup Patel > > --- > > Changes since v1: > > - We adapt good aspects from Gary Guo's ASID allocator implementation > > and provide due credit to h

Re: [PATCH v2] RISC-V: Implement ASID allocator

On Thu, 28 Mar 2019, Anup Patel wrote: > Signed-off-by: Gary Guo > Signed-off-by: Anup Patel > --- > Changes since v1: > - We adapt good aspects from Gary Guo's ASID allocator implementation > and provide due credit to him by adding his SoB. This isn't the right way to use Signed-off-by: li

[PATCH v3] RISC-V: Implement ASID allocator

Currently, we do local TLB flush on every MM switch. This is very harsh on performance because we are forcing page table walks after every MM switch. This patch implements ASID allocator for assigning an ASID to a MM context. The number of ASIDs are limited in HW so we create a logical entity name

Re: [PATCH v2] RISC-V: Implement ASID allocator

On Thu, Mar 28, 2019 at 8:03 PM Gary Guo wrote: > > > > On 28/03/2019 14:13, Anup Patel wrote: > > On Thu, Mar 28, 2019 at 7:07 PM Gary Guo wrote: > >> > >> Hi Anup, > >> > >> The code still does not use ASID in TLB flush routines. Without this > >> added the code does not boot on systems with tr

Re: [PATCH v2] RISC-V: Implement ASID allocator

On Thu, Mar 28, 2019 at 8:00 PM Gary Guo wrote: > > > > On 28/03/2019 14:09, Anup Patel wrote: > > On Thu, Mar 28, 2019 at 7:07 PM Gary Guo wrote: > >> > >> Hi Anup, > >> > >> The code still does not use ASID in TLB flush routines. Without this > >> added the code does not boot on systems with tr

Re: [PATCH v6 1/2] Bluetooth: hci_qca: Added support for WCN3998

Hi Matthias, On 2019-03-29 02:53, Matthias Kaehlcke wrote: On Fri, Mar 29, 2019 at 05:05:49AM +0800, kbuild test robot wrote: Hi Harish, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on bluetooth-next/master] [also build test WARNING on next-20190328

Re: [PATCH v6 1/2] Bluetooth: hci_qca: Added support for WCN3998

Hi Matthias, On 2019-03-27 22:26, Matthias Kaehlcke wrote: On Wed, Mar 27, 2019 at 05:58:42PM +0530, Harish Bandi wrote: Added new compatible for WCN3998 and corresponding voltage and current values to WCN3998 compatible. Changed driver code to support WCN3998 Signed-off-by: Harish Bandi Yo

Re: [PATCH v6 2/2] dt-bindings: net: bluetooth: Add device tree bindings for QTI chip WCN3998

Hi Matthias, On 2019-03-27 22:59, Matthias Kaehlcke wrote: On Wed, Mar 27, 2019 at 05:58:43PM +0530, Harish Bandi wrote: This patch enables regulators for the Qualcomm Bluetooth WCN3998 controller. I commented on this on v3, but you didn't update it: No, it doesn't. The next version sho

Query on how WWAN and Modem interact

Hi All. I am sorry upfront if this might seem like a stupid question. I am wanting to have some insight on how a modem plugs into the linux-kernel at architecture level. First a bit of history. I have prior experience of using an onboard-modem on a ubuntu, via support from modem-manager. There, a

[PATCH 6/5] lib/list_sort: Fix GCC warning

It turns out that GCC 4.9, 7.3, and 8.1 ignore the __pure attribute on function pointers and (with the standard kernel compile flags) emit a warning about it. Even though it accurately describes a comparison function (the compiler need not reload cached pointers across the call), it doesn't actual

Re: [RESEND PATCH v2 4/5] lib/list_sort: Simplify and remove MAX_LIST_LENGTH_BITS

Than you all for the build warning report. The warning produced by gcc versions 4.9, 7.3, 8.1, whatever version Stephen Rothwell is running, is: lib/list_sort.c:17:36: warning: __pure__ attribute ignored [-Wattributes] The relevant code is: 10: /* 11: * By declaring the compare function with the

Re: [RFC PATCH] mm, kvm: account kvm_vcpu_mmap to kmemcg

On Thu, Mar 28, 2019 at 7:36 PM Matthew Wilcox wrote: > > On Thu, Mar 28, 2019 at 06:28:36PM -0700, Shakeel Butt wrote: > > A VCPU of a VM can allocate upto three pages which can be mmap'ed by the > > user space application. At the moment this memory is not charged. On a > > large machine running

(.init.text+0x134): multiple definition of `plat_irq_setup'

Hi Takashi, FYI, the error/warning still remains. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 9936328b41ce4bce8f20269dcac8cb476c8d0820 commit: c97617a81a7616d49bc3700959e08c6c6f447093 ALSA: hda/ca0132 - Fix build error without CONFIG_PCI date: 7 w

Re: [PATCH 1/2] platform/x86: intel_pmc_core: Convert to a platform_driver

On Mon, 2019-03-25 at 18:41 -0700, Rajat Jain wrote: > Hi Rajneesh, > > > On Mon, Mar 25, 2019 at 3:23 AM Bhardwaj, Rajneesh > wrote: > > > > Hi Rajat > > > > On 23-Mar-19 6:00 AM, Rajat Jain wrote: > > > Hi Rajneesh, > > > > > > > > > > > > On Fri, Mar 22, 2019 at 12:56 PM Bhardwaj, Rajnee

Re: [PATCH 4/6] x86, mm: make split_mem_range() more easy to read

On Thu, Mar 28, 2019 at 09:08:43AM +0100, Thomas Gleixner wrote: >On Thu, 28 Mar 2019, Wei Yang wrote: >> On Sun, Mar 24, 2019 at 03:29:04PM +0100, Thomas Gleixner wrote: >> My question is to the for loop. >> >> For example, we have a range >> >>+--+-+---+ >>

Re: [PATCH] ARM: dts: vf610-zii-cfu1: Disable NOR flash/SPI controller

On Mon, Mar 25, 2019 at 11:30:17AM -0700, Andrey Smirnov wrote: > Only a certain number of CFU1's come with NOR flash populated. Disable > it by default to avoid trying to probe NOR flash on devices that don't > have it. Devices that do have it can rely on the bootloader to enable > this node. > >

[RFC][PATCH 2/4 v2] tracing/syscalls: Pass in hardcoded 6 into syscall_get_arguments()

From: "Steven Rostedt (Red Hat)" The only users that calls syscall_get_arguments() with a variable and not a hard coded '6' is ftrace_syscall_enter(). syscall_get_arguments() can be optimized by removing a variable input, and always grabbing 6 arguments regardless of what the system call actually

[RFC][PATCH 0/4 v2] sycalls: Remove args i and n from syscall_get_arguments()

Two and a half years ago I sent out 3 patches and a title letter that had this[1]: At Linux Plumbers, Andy Lutomirski approached me to tell me that the syscall_get_arguments() implementation in x86 was horrible and gcc certainly gets it wrong. He said that since the tracepoints only pass

[RFC][PATCH 4/4 v2] syscalls: Remove start and number from syscall_set_arguments() args

From: "Steven Rostedt (VMware)" After removing the start and count arguments of syscall_get_arguments() it seems reasonable to remove them from syscall_set_arguments(). Note, as of today, there are no users of syscall_set_arguments(). But we are told that there will be soon. But for now, at least

[RFC][PATCH 3/4 v2] syscalls: Remove start and number from syscall_get_arguments() args

From: "Steven Rostedt (Red Hat)" At Linux Plumbers, Andy Lutomirski approached me and pointed out that the function call syscall_get_arguments() implemented in x86 was horribly written and not optimized for the standard case of passing in 0 and 6 for the starting index and the number of system ca

[RFC][PATCH 1/4 v2] ptrace: Remove maxargs from task_current_syscall()

From: "Steven Rostedt (Red Hat)" task_current_syscall() has a single user that passes in 6 for maxargs, which is the maximum arguments that can be used to get system calls from syscall_get_arguments(). Instead of passing in a number of arguments to grab, just get 6 arguments. The args argument ev

linux-next: Tree for Mar 29

Hi all, Changes since 20190328: The pidfd tree lost its build failures. Non-merge commits (relative to Linus' tree): 3597 3205 files changed, 100345 insertions(+), 49777 deletions(-) I have created today&#x

Re: mmotm 2019-03-28-15-50 uploaded (gcov)

On 3/28/19 3:51 PM, a...@linux-foundation.org wrote: > The mm-of-the-moment snapshot 2019-03-28-15-50 has been uploaded to > >http://www.ozlabs.org/~akpm/mmotm/ > > mmotm-readme.txt says > > README for mm-of-the-moment: > > http://www.ozlabs.org/~akpm/mmotm/ > > This is a snapshot of my -m

Re: [PATCH v3 1/3] dt-bindings: arm: fsl: Add supported ZII VF610 boards to DT schema

On Mon, Mar 25, 2019 at 11:22:41AM -0700, Andrey Smirnov wrote: > Add already supported ZII VF610 boards to DT schema. > > Signed-off-by: Andrey Smirnov > Cc: Shawn Guo > Cc: Chris Healy > Cc: Andrew Lunn > Cc: Fabio Estevam > Cc: Rob Herring > Cc: linux-arm-ker...@lists.infradead.org > Cc:

kernfs: can read/write method grow buffer size?

Hello Tejun and Greg, kernfs_fop_open/read/write allocates a buffer for the ->read, ->write, or ->seq_read methods. This buffer is either preallocated or allocated on the spot, with minimum size being PAGE_SIZE, if ->atomic_write_len is not given. There is a question/problem currently in the led-

[PATCH v14 10/11] gpio: 74x164: Utilize the for_each_set_clump8 macro

Replace verbose implementation in set_multiple callback with for_each_set_clump8 macro to simplify code and improve clarity. Suggested-by: Andy Shevchenko Cc: Geert Uytterhoeven Cc: Phil Reid Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-74x164.c | 19 +-- 1 file

[PATCH v14 11/11] thermal: intel: intel_soc_dts_iosf: Utilize for_each_set_clump8 macro

Utilize for_each_set_clump8 macro, and the bitmap_set_value8 and bitmap_get_value8 functions, where appropriate. In addition, remove the now unnecessary temp_mask and temp_shift members of the intel_soc_dts_sensor_entry structure. Suggested-by: Andy Shevchenko Tested-by: Andy Shevchenko Signed-o

[PATCH v14 09/11] gpio: uniphier: Utilize for_each_set_clump8 macro

Replace verbose implementation in set_multiple callback with for_each_set_clump8 macro to simplify code and improve clarity. An improvement in this case is that banks that are not masked will now be skipped. Cc: Masahiro Yamada Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-uniphie

[PATCH v14 08/11] gpio: pcie-idio-24: Utilize for_each_set_clump8 macro

Replace verbose implementation in get_multiple/set_multiple callbacks with for_each_set_clump8 macro to simplify code and improve clarity. Reviewed-by: Linus Walleij Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-pcie-idio-24.c | 109 --- 1 file changed,

[PATCH v14 07/11] gpio: pci-idio-16: Utilize for_each_set_clump8 macro

Replace verbose implementation in get_multiple/set_multiple callbacks with for_each_set_clump8 macro to simplify code and improve clarity. Reviewed-by: Linus Walleij Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-pci-idio-16.c | 75 - 1 file changed,

[PATCH v14 06/11] gpio: ws16c48: Utilize for_each_set_clump8 macro

Replace verbose implementation in get_multiple/set_multiple callbacks with for_each_set_clump8 macro to simplify code and improve clarity. Reviewed-by: Linus Walleij Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-ws16c48.c | 73 ++--- 1 file changed,

[PATCH v14 05/11] gpio: gpio-mm: Utilize for_each_set_clump8 macro

Replace verbose implementation in get_multiple/set_multiple callbacks with for_each_set_clump8 macro to simplify code and improve clarity. Reviewed-by: Linus Walleij Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-gpio-mm.c | 73 +++-- 1 file changed,

[PATCH v14 04/11] gpio: 104-idi-48: Utilize for_each_set_clump8 macro

Replace verbose implementation in get_multiple/set_multiple callbacks with for_each_set_clump8 macro to simplify code and improve clarity. Reviewed-by: Linus Walleij Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-104-idi-48.c | 36 +++--- 1 file changed,

[PATCH v14 03/11] gpio: 104-dio-48e: Utilize for_each_set_clump8 macro

Replace verbose implementation in get_multiple/set_multiple callbacks with for_each_set_clump8 macro to simplify code and improve clarity. Reviewed-by: Linus Walleij Signed-off-by: William Breathitt Gray --- drivers/gpio/gpio-104-dio-48e.c | 73 ++--- 1 file changed,

[PATCH v14 01/11] bitops: Introduce the for_each_set_clump8 macro

This macro iterates for each 8-bit group of bits (clump) with set bits, within a bitmap memory region. For each iteration, "start" is set to the bit offset of the found clump, while the respective clump value is stored to the location pointed by "clump". Additionally, the bitmap_get_value8 and bitm

[PATCH v14 02/11] lib/test_bitmap.c: Add for_each_set_clump8 test cases

The introduction of the for_each_set_clump8 macro warrants test cases to verify the implementation. This patch adds test case checks for whether an out-of-bounds clump index is returned, a zero clump is returned, or the returned clump value differs from the expected clump value. Cc: Rasmus Villemo

[PATCH v14 00/11] Introduce the for_each_set_clump8 macro

Changes in v14: - Redefine bitmap_get_value8, bitmap_set_value8, and find_next_clump8 as static inline functions - Rename 'idx' variable to 'index' in the bitmap_get_value8 and bitmap_set_value8 functions - Remove superfluous parens in gen_74x164_set_multiple While adding GPIO get_mu

[PATCH v2] sched/clock: Prevent generic sched_clock wrap caused by tick_freeze()

tick_freeze() introduced by suspend-to-idle in commit 124cf9117c5f ("PM / sleep: Make it possible to quiesce timers during suspend-to-idle") will use timekeeping_suspend() instead of syscore_suspend() during suspend-to-idle. It means that generic sched_clock will keep going because sched_clock_susp

Re: [PATCH v2 06/11] mm/hmm: improve driver API to work and wait over a range v2

On Thu, Mar 28, 2019 at 08:56:54PM -0400, Jerome Glisse wrote: > On Thu, Mar 28, 2019 at 09:12:21AM -0700, Ira Weiny wrote: > > On Mon, Mar 25, 2019 at 10:40:06AM -0400, Jerome Glisse wrote: > > > From: Jérôme Glisse > > > [snip] > > > +/* > > > + * HMM_RANGE_DEFAULT_TIMEOUT - default timeout (

Re: [PATCH 2/5] ARM: dts: imx50: Add Kobo Aura DTS

On Tue, Mar 26, 2019 at 05:26:53PM +0100, Jonathan Neuschäfer wrote: > Hi, thanks for your comments. I'll address them in v2. > > On Fri, Mar 22, 2019 at 09:31:53AM +0800, Shawn Guo wrote: > > On Tue, Mar 19, 2019 at 04:24:17PM +0100, Jonathan Neuschäfer wrote: > > > The Kobo Aura is an e-book rea

Re: [PATCH v2 10/11] mm/hmm: add helpers for driver to safely take the mmap_sem v2

On Thu, Mar 28, 2019 at 04:34:04PM -0700, John Hubbard wrote: > On 3/28/19 4:24 PM, Jerome Glisse wrote: > > On Thu, Mar 28, 2019 at 04:20:37PM -0700, John Hubbard wrote: > >> On 3/28/19 4:05 PM, Jerome Glisse wrote: > >>> On Thu, Mar 28, 2019 at 03:43:33PM -0700, John Hubbard wrote: > On 3/28

linux-next: build warning after merge of the akpm-current tree

Hi all, After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: lib/list_sort.c:17:36: warning: 'pure' attribute ignored [-Wattributes] struct list_head const *, struct list_head const *); ^ Intr

Re: [PATCH v3 03/12] dt-binding: gce: add binding for gce event property

Hi, Rob, Thanks for your review and comments. On Thu, 2019-03-28 at 13:44 -0500, Rob Herring wrote: > On Thu, Mar 28, 2019 at 10:19:24AM +0800, Bibby Hsieh wrote: > > Client hardware would send event to GCE hardware, > > so #event-cells, mediatek,gce-event-names, mediatek,gce-events. > > present

Re: [RFC PATCH] mm, kvm: account kvm_vcpu_mmap to kmemcg

On Thu, Mar 28, 2019 at 06:28:36PM -0700, Shakeel Butt wrote: > A VCPU of a VM can allocate upto three pages which can be mmap'ed by the > user space application. At the moment this memory is not charged. On a > large machine running large number of VMs (or small number of VMs having > large number

Re: [PATCH] Convert struct pid count to refcount_t

On Thu, Mar 28, 2019 at 10:39:58AM -0400, Joel Fernandes wrote: > On Thu, Mar 28, 2019 at 03:26:19PM +0100, Oleg Nesterov wrote: > > On 03/27, Joel Fernandes wrote: > > > > > > Also, based on Kees comment, I think it appears to me that get_pid and > > > put_pid can race in this way in the original

Re: [PATCH 1/1] sched/clock: Prevent generic sched_clock wrap caused by tick_freeze()

On Mon, 2019-03-25 at 21:54 +0800, Thomas Gleixner wrote: > On Mon, 25 Mar 2019, Chang-An Chen wrote: > > --- a/include/linux/sched_clock.h > > +++ b/include/linux/sched_clock.h > > @@ -13,6 +13,10 @@ > > > > extern void sched_clock_register(u64 (*read)(void), int bits, > >

Re: [PATCH] Convert struct pid count to refcount_t

On Thu, Mar 28, 2019 at 04:00:52PM -0400, Joel Fernandes wrote: > On Thu, Mar 28, 2019 at 04:17:50PM +0100, Jann Horn wrote: > > Since we're just talking about RCU stuff now, adding Paul McKenney to > > the thread. > > > > On Thu, Mar 28, 2019 at 3:37 PM Joel Fernandes > > wrote: > > > On Thu, M

Re: [PATCH v2 02/11] mm/hmm: use reference counting for HMM struct v2

On Thu, Mar 28, 2019 at 11:21:00AM -0700, Ira Weiny wrote: > On Thu, Mar 28, 2019 at 09:50:03PM -0400, Jerome Glisse wrote: > > On Thu, Mar 28, 2019 at 06:18:35PM -0700, John Hubbard wrote: > > > On 3/28/19 6:00 PM, Jerome Glisse wrote: > > > > On Thu, Mar 28, 2019 at 09:57:09AM -0700, Ira Weiny wr

Re: [PATCH v2 02/11] mm/hmm: use reference counting for HMM struct v2

On Thu, Mar 28, 2019 at 09:50:03PM -0400, Jerome Glisse wrote: > On Thu, Mar 28, 2019 at 06:18:35PM -0700, John Hubbard wrote: > > On 3/28/19 6:00 PM, Jerome Glisse wrote: > > > On Thu, Mar 28, 2019 at 09:57:09AM -0700, Ira Weiny wrote: > > >> On Thu, Mar 28, 2019 at 05:39:26PM -0700, John Hubbard

Re: [PATCH v2 02/11] mm/hmm: use reference counting for HMM struct v2

On Thu, Mar 28, 2019 at 07:11:17PM -0700, John Hubbard wrote: > On 3/28/19 6:50 PM, Jerome Glisse wrote: > [...] > >>> > >>> The hmm_put() is just releasing the reference on the hmm struct. > >>> > >>> Here i feel i am getting contradicting requirement from different people. > >>> I don't think the

Re: [PATCH v2 09/11] mm/hmm: allow to mirror vma of a file on a DAX backed filesystem v2

On Thu, Mar 28, 2019 at 11:04:26AM -0700, Ira Weiny wrote: > On Mon, Mar 25, 2019 at 10:40:09AM -0400, Jerome Glisse wrote: > > From: Jérôme Glisse > > > > HMM mirror is a device driver helpers to mirror range of virtual address. > > It means that the process jobs running on the device can access

[PATCH v2 1/2] mtd: maps: physmap: Store gpio_values correctly

When the gpio-addr-flash.c driver was merged with physmap-core.c the code to store the current gpio_values was lost. This meant that once a gpio was asserted it was never de-asserted. Fix this by storing the current offset in gpio_values like the old driver used to. Fixes: commit ba32ce95cbd9 ("mt

[PATCH v2 2/2] dt-binding: mtd: physmap: Add example using addr-gpios property

Add an example showing how to use the addr-gpios property to deal with a system with limited IO space. Cc: devicet...@vger.kernel.org Signed-off-by: Chris Packham --- Changes in v2: - None .../devicetree/bindings/mtd/mtd-physmap.txt | 16 1 file changed, 16 insertions(+)

[PATCH v2 0/2] mtd: physmap: Using gpio-addrs

I have a system with ADDR24 of the flash chip connected to a gpio pin. This series fixes a bug in physmap-core.c and adds an example for using gpio-addrs to the dt-binding based on the system I'm using. Chris Packham (2): mtd: maps: physmap: Store gpio_values correctly dt-binding: mtd: physmap

Re: [PATCH v2 02/11] mm/hmm: use reference counting for HMM struct v2

On 3/28/19 6:50 PM, Jerome Glisse wrote: [...] >>> >>> The hmm_put() is just releasing the reference on the hmm struct. >>> >>> Here i feel i am getting contradicting requirement from different people. >>> I don't think there is a way to please everyone here. >>> >> >> That's not a true conflict: y

Re: [PATCH v2 07/11] mm/hmm: add default fault flags to avoid the need to pre-fill pfns arrays.

On Thu, Mar 28, 2019 at 07:05:21PM -0700, John Hubbard wrote: > On 3/28/19 6:59 PM, Jerome Glisse wrote: > >> [...] > > Indeed I did not realize there is an hmm "pfn" until I saw this > > function: > > > > /* > > * hmm_pfn_from_pfn() - create a valid HMM pfn value from pfn

Re: [PATCH v2 09/11] mm/hmm: allow to mirror vma of a file on a DAX backed filesystem v2

On Mon, Mar 25, 2019 at 10:40:09AM -0400, Jerome Glisse wrote: > From: Jérôme Glisse > > HMM mirror is a device driver helpers to mirror range of virtual address. > It means that the process jobs running on the device can access the same > virtual address as the CPU threads of that process. This

Re: [PATCH v2 07/11] mm/hmm: add default fault flags to avoid the need to pre-fill pfns arrays.

On 3/28/19 6:59 PM, Jerome Glisse wrote: >> [...] > Indeed I did not realize there is an hmm "pfn" until I saw this function: > > /* > * hmm_pfn_from_pfn() - create a valid HMM pfn value from pfn > * @range: range use to encode HMM pfn value > * @pfn: pfn value for wh

[PATCH] max98357a:add dai without triggered by pcm

From: Tony Zou max98357a's enable pin need setting independently when max98357a is shared I2S with other codec. add dai "max98357a-hifi" without pcm trigger, and use "Spk PA Switch" to set the enable pin. Signed-off-by: Tony Zou --- sound/soc/codecs/max98357a.c | 94

Re: [PATCH RFC] KVM: x86: vmx: throttle immediate exit through preemtion timer to assist buggy guests

> On 28 Mar 2019, at 22:31, Vitaly Kuznetsov wrote: > > This is embarassing but we have another Windows/Hyper-V issue to workaround > in KVM (or QEMU). Hope "RFC" makes it less offensive. > > It was noticed that Hyper-V guest on q35 KVM/QEMU VM hangs on boot if e.g. > 'piix4-usb-uhci' device

Re: [PATCH v2 07/11] mm/hmm: add default fault flags to avoid the need to pre-fill pfns arrays.

On Thu, Mar 28, 2019 at 09:42:59PM -0400, Jerome Glisse wrote: > On Thu, Mar 28, 2019 at 06:30:26PM -0700, John Hubbard wrote: > > On 3/28/19 6:17 PM, Jerome Glisse wrote: > > > On Thu, Mar 28, 2019 at 09:42:31AM -0700, Ira Weiny wrote: > > >> On Thu, Mar 28, 2019 at 04:28:47PM -0700, John Hubbard

Re: [PATCH v2 02/11] mm/hmm: use reference counting for HMM struct v2

On Thu, Mar 28, 2019 at 06:18:35PM -0700, John Hubbard wrote: > On 3/28/19 6:00 PM, Jerome Glisse wrote: > > On Thu, Mar 28, 2019 at 09:57:09AM -0700, Ira Weiny wrote: > >> On Thu, Mar 28, 2019 at 05:39:26PM -0700, John Hubbard wrote: > >>> On 3/28/19 2:21 PM, Jerome Glisse wrote: > On Thu, Ma

[PATCH] regulator: vctrl: Remove unneeded continue statement

Signed-off-by: Axel Lin --- drivers/regulator/vctrl-regulator.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/regulator/vctrl-regulator.c b/drivers/regulator/vctrl-regulator.c index 78de002037c7..259864520a06 100644 --- a/drivers/regulator/vctrl-regulator.c +++ b

  1   2   3   4   5   6   7   >