[PATCH v4 3/5] usb: xhci: Fix memory leak when xhci_disable_slot() returns error

If xhci_disable_slot() returns success, a disable slot command trb was queued in the command ring. The command completion handler will free the virtual device data structure associated with the slot. On the other hand, when xhci_disable_slot() returns error, the invokers should take the

[PATCH v4 1/5] usb: xhci: Disable slot even virt-dev is null

xhci_disable_slot() is a helper for disabling a slot when a device goes away or recovers from error situations. Currently, it checks the corespoding virt-dev pointer and returns directly (w/o issuing disable slot command) if it's null. This is unnecessary and will cause problems in case where

[PATCH v4 4/5] usb: xhci: Return error when host is dead in xhci_disable_slot()

xhci_disable_slot() is a helper for disabling a slot when a device goes away or recovers from error situations. Currently, it returns success when it sees a dead host. This is not the right way to go. It should return error and let the invoker know that disable slot command was failed due to a

[PATCH v4 4/5] usb: xhci: Return error when host is dead in xhci_disable_slot()

xhci_disable_slot() is a helper for disabling a slot when a device goes away or recovers from error situations. Currently, it returns success when it sees a dead host. This is not the right way to go. It should return error and let the invoker know that disable slot command was failed due to a

[PATCH v4 5/5] usb: xhci: Handle USB transaction error on address command

Xhci driver handles USB transaction errors on transfer events, but transaction errors are possible on address device command completion events as well. The xHCI specification (section 4.6.5) says: A USB Transaction Error Completion Code for an Address Device Command may be due to a Stall response

[PATCH v4 5/5] usb: xhci: Handle USB transaction error on address command

Xhci driver handles USB transaction errors on transfer events, but transaction errors are possible on address device command completion events as well. The xHCI specification (section 4.6.5) says: A USB Transaction Error Completion Code for an Address Device Command may be due to a Stall response

Re: [RFC V2] printk: add warning while drop partial text in msg

Hi, On (08/11/17 00:55), pierre kuo wrote: [..] > And people will be hard to find out some part of message is left behind. > (since the tail of original message is elegantly dropped by "\n") > That is the reason I try to add such warning in msg_print_text. have you ever seen it (the truncation)

Re: [RFC V2] printk: add warning while drop partial text in msg

Hi, On (08/11/17 00:55), pierre kuo wrote: [..] > And people will be hard to find out some part of message is left behind. > (since the tail of original message is elegantly dropped by "\n") > That is the reason I try to add such warning in msg_print_text. have you ever seen it (the truncation)

Re: [PATCH v2 0/2] x86: paravirt related cleanup

Juergen Gross writes: > Cleanup special cases of paravirt patching: > > - Xen doesn't need a custom patching function, it can use > paravirt_patch_default() > > - Remove lguest completely from the tree. A LKML mail asking for any > users 3 months ago did not reveal any need

Re: [PATCH v2 0/2] x86: paravirt related cleanup

Juergen Gross writes: > Cleanup special cases of paravirt patching: > > - Xen doesn't need a custom patching function, it can use > paravirt_patch_default() > > - Remove lguest completely from the tree. A LKML mail asking for any > users 3 months ago did not reveal any need for keeping lguest

Re: [PATCH] scsi: ncr5380: constify pnp_device_id

Arvind, > pnp_device_id are not supposed to change at runtime. All functions > working with pnp_device_id provided by work with > const pnp_device_id. So mark the non-const structs as const. Applied to 4.14/scsi-queue. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] scsi: ncr5380: constify pnp_device_id

Arvind, > pnp_device_id are not supposed to change at runtime. All functions > working with pnp_device_id provided by work with > const pnp_device_id. So mark the non-const structs as const. Applied to 4.14/scsi-queue. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH v3 2/2] Input: axp20x-pek: add support for AXP221 PEK

On Wed, Aug 09, 2017 at 11:45:55AM +0200, Quentin Schulz wrote: > The AXP221 has different values for startup time bits from the AXP20X. > > Signed-off-by: Quentin Schulz > Reviewed-by: Chen-Yu Tsai Applied, thank you. > --- >

Re: [PATCH v3 2/2] Input: axp20x-pek: add support for AXP221 PEK

On Wed, Aug 09, 2017 at 11:45:55AM +0200, Quentin Schulz wrote: > The AXP221 has different values for startup time bits from the AXP20X. > > Signed-off-by: Quentin Schulz > Reviewed-by: Chen-Yu Tsai Applied, thank you. > --- > drivers/input/misc/axp20x-pek.c | 17 + > 1 file

[PATCH v3] x86/build: Fix stack alignment for CLang

Commit: d77698df39a5 ("x86/build: Specify stack alignment for clang") intended to use the same stack alignment for clang as with gcc. The two compilers use different options to configure the stack alignment (gcc: -mpreferred-stack-boundary=n, clang: -mstack-alignment=n). The above commit

[PATCH v3] x86/build: Fix stack alignment for CLang

Commit: d77698df39a5 ("x86/build: Specify stack alignment for clang") intended to use the same stack alignment for clang as with gcc. The two compilers use different options to configure the stack alignment (gcc: -mpreferred-stack-boundary=n, clang: -mstack-alignment=n). The above commit

Re: [PATCH v3 1/2] Input: axp20x-pek: use driver_data of platform_device_id instead of extended attributes

On Mon, Aug 14, 2017 at 06:03:44PM +0800, Chen-Yu Tsai wrote: > On Wed, Aug 9, 2017 at 5:45 PM, Quentin Schulz > wrote: > > To prepare an upcoming patch adding support for another PMIC that has > > different startup and shutdown time, use driver_data of > >

Re: [PATCH v3 1/2] Input: axp20x-pek: use driver_data of platform_device_id instead of extended attributes

On Mon, Aug 14, 2017 at 06:03:44PM +0800, Chen-Yu Tsai wrote: > On Wed, Aug 9, 2017 at 5:45 PM, Quentin Schulz > wrote: > > To prepare an upcoming patch adding support for another PMIC that has > > different startup and shutdown time, use driver_data of > > platform_device_id instead of a fixed

Re: [PATCH] Input: i8042: constify pnp_device_id

On Wed, Aug 16, 2017 at 11:11:42AM +0530, Arvind Yadav wrote: > pnp_device_id are not supposed to change at runtime. All functions > working with pnp_device_id provided by work with > const pnp_device_id. So mark the non-const structs as const. > > Signed-off-by: Arvind Yadav

Re: [PATCH] Input: i8042: constify pnp_device_id

On Wed, Aug 16, 2017 at 11:11:42AM +0530, Arvind Yadav wrote: > pnp_device_id are not supposed to change at runtime. All functions > working with pnp_device_id provided by work with > const pnp_device_id. So mark the non-const structs as const. > > Signed-off-by: Arvind Yadav Applied, thank

Re: [PATCH] iio: accel: mma8452: Bugfix to enbale and allow different events to work parallely.

Hello, fixes are always welcome, some comments regarding the patch Thanks for the review. in subject: typo "enable" Will fix it. This driver supports multiple devices like mma8653, mma8652, mma8452, mma8453 and fxls8471. Almost all these devices have more than one event. Current driver

Re: [PATCH] iio: accel: mma8452: Bugfix to enbale and allow different events to work parallely.

Hello, fixes are always welcome, some comments regarding the patch Thanks for the review. in subject: typo "enable" Will fix it. This driver supports multiple devices like mma8653, mma8652, mma8452, mma8453 and fxls8471. Almost all these devices have more than one event. Current driver

Re: [PATCH] scsi: qla2xxx: fix spelling mistake of variable sfp_additonal_info

Colin, > Trivial fix to variable name, sfp_additonal_info should be > sfp_additional_info (add in missing i). Applied to 4.14/scsi-queue. -- Martin K. Petersen Oracle Linux Engineering

Re: [PATCH] scsi: qla2xxx: fix spelling mistake of variable sfp_additonal_info

Colin, > Trivial fix to variable name, sfp_additonal_info should be > sfp_additional_info (add in missing i). Applied to 4.14/scsi-queue. -- Martin K. Petersen Oracle Linux Engineering

[PATCH v3] net: inet: diag: expose sockets cgroup classid

From: "Levin, Alexander (Sasha Levin)" This is useful for directly looking up a task based on class id rather than having to scan through all open file descriptors. Signed-off-by: Sasha Levin --- include/uapi/linux/inet_diag.h | 1

[PATCH v3] net: inet: diag: expose sockets cgroup classid

From: "Levin, Alexander (Sasha Levin)" This is useful for directly looking up a task based on class id rather than having to scan through all open file descriptors. Signed-off-by: Sasha Levin --- include/uapi/linux/inet_diag.h | 1 + net/ipv4/inet_diag.c | 11 +++ 2 files

[PATCH] dts: Make it easier to enable __symbols__ generation in dtb files

This introduces the variabe DTC_EXTRA_FLAGS to allow for additional flags to be passed to dtc. While this can have many uses (such as easier testing of new warning flags) the use case I wish to spell out here is passing of -@ to enable __symbols__ to be included in the resulting dtb and thus

[PATCH] dts: Make it easier to enable __symbols__ generation in dtb files

This introduces the variabe DTC_EXTRA_FLAGS to allow for additional flags to be passed to dtc. While this can have many uses (such as easier testing of new warning flags) the use case I wish to spell out here is passing of -@ to enable __symbols__ to be included in the resulting dtb and thus

Re: [PATCH] ARM: dts: TI: Enable __symbols__ in dtb files for some platforms

On Wed, Aug 16, 2017 at 03:57:21PM -0700, Frank Rowand wrote: > On 08/16/17 15:33, Frank Rowand wrote: > > On 08/16/17 14:59, Tom Rini wrote: > >> Build the dtb file for these platfroms with __symbol__ information > >> included. This will reduce the size of the dtb (and resident memory > > > >

Re: [PATCH] ARM: dts: TI: Enable __symbols__ in dtb files for some platforms

On Wed, Aug 16, 2017 at 03:57:21PM -0700, Frank Rowand wrote: > On 08/16/17 15:33, Frank Rowand wrote: > > On 08/16/17 14:59, Tom Rini wrote: > >> Build the dtb file for these platfroms with __symbol__ information > >> included. This will reduce the size of the dtb (and resident memory > > > >

Re: [PATCH] scsi: mpt3sas: fix pr_info message continuation

Colin, > An optional discovery status should be printed with a pr_cont and > needs a leading space to make it more readable. The final new line > should also be a pr_cont and the indentation is out by one, so fix > that too. Applied to 4.14/scsi-queue. -- Martin K. Petersen Oracle Linux

Re: [PATCH] scsi: mpt3sas: fix pr_info message continuation

Colin, > An optional discovery status should be printed with a pr_cont and > needs a leading space to make it more readable. The final new line > should also be a pr_cont and the indentation is out by one, so fix > that too. Applied to 4.14/scsi-queue. -- Martin K. Petersen Oracle Linux

Re: [PATCH v2] net: inet: diag: expose sockets cgroup classid

On Wed, Aug 16, 2017 at 01:15:57PM -0700, Cong Wang wrote: >On Wed, Aug 16, 2017 at 1:13 PM, Levin, Alexander (Sasha Levin) > wrote: >> Ping? > >I guess you missed the comment saying you need to check >the return value of nla_put_u32(). Indeed I did. Odd, I don't see

Re: [PATCH v2] net: inet: diag: expose sockets cgroup classid

On Wed, Aug 16, 2017 at 01:15:57PM -0700, Cong Wang wrote: >On Wed, Aug 16, 2017 at 1:13 PM, Levin, Alexander (Sasha Levin) > wrote: >> Ping? > >I guess you missed the comment saying you need to check >the return value of nla_put_u32(). Indeed I did. Odd, I don't see the mail locally, but I can

[PATCH] lockdep: Make LOCKDEP_CROSSRELEASE part of PROVE_LOCKING

I am not sure if I did as Ingo suggested. Is this what you intended? ->8- >From 64c705bfedf45b2c56a0d2f4c65a998a1b730310 Mon Sep 17 00:00:00 2001 From: Byungchul Park Date: Thu, 17 Aug 2017 09:12:18 +0900 Subject: [PATCH] lockdep: Make LOCKDEP_CROSSRELEASE part of

[PATCH] lockdep: Make LOCKDEP_CROSSRELEASE part of PROVE_LOCKING

I am not sure if I did as Ingo suggested. Is this what you intended? ->8- >From 64c705bfedf45b2c56a0d2f4c65a998a1b730310 Mon Sep 17 00:00:00 2001 From: Byungchul Park Date: Thu, 17 Aug 2017 09:12:18 +0900 Subject: [PATCH] lockdep: Make LOCKDEP_CROSSRELEASE part of PROVE_LOCKING

Re: [RFC PATCH 1/3] PCI: rockchip: Add support for pcie wake irq

hi shawn, On 08/16/2017 05:00 PM, Shawn Lin wrote: Hi Jeffy, On 2017/8/16 15:52, Jeffy Chen wrote: Add support for PCIE_WAKE pin in rockchip pcie driver. Signed-off-by: Jeffy Chen --- drivers/pci/host/pcie-rockchip.c | 58

Re: [RFC PATCH 1/3] PCI: rockchip: Add support for pcie wake irq

hi shawn, On 08/16/2017 05:00 PM, Shawn Lin wrote: Hi Jeffy, On 2017/8/16 15:52, Jeffy Chen wrote: Add support for PCIE_WAKE pin in rockchip pcie driver. Signed-off-by: Jeffy Chen --- drivers/pci/host/pcie-rockchip.c | 58 1 file changed, 58

Re: [PATCH v2] i40e/i40evf: use cpumask_copy() for assigning cpumask

On Wed, 2017-08-16 at 19:52 +0200, Juergen Gross wrote: > Using direct assignment for a cpumask is wrong, cpumask_copy() should > be used instead. > > Otherwise crashes like the following might happen: > > [62792.326374] BUG: unable to handle kernel paging request at > 8800049ff000 >

Re: [PATCH v2] i40e/i40evf: use cpumask_copy() for assigning cpumask

On Wed, 2017-08-16 at 19:52 +0200, Juergen Gross wrote: > Using direct assignment for a cpumask is wrong, cpumask_copy() should > be used instead. > > Otherwise crashes like the following might happen: > > [62792.326374] BUG: unable to handle kernel paging request at > 8800049ff000 >

Re: [PATCH] Adding-Agile-SD-TCP-module-and-modifying-Kconfig-and-makefile

Hi mohamedalrshah, [auto build test ERROR on net/master] [also build test ERROR on v4.13-rc5 next-20170816] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/mohamedalrshah/Adding-Agile-SD-TCP

Re: [PATCH] Adding-Agile-SD-TCP-module-and-modifying-Kconfig-and-makefile

Hi mohamedalrshah, [auto build test ERROR on net/master] [also build test ERROR on v4.13-rc5 next-20170816] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/mohamedalrshah/Adding-Agile-SD-TCP

[HMM-v25 01/19] hmm: heterogeneous memory management documentation v3

This add documentation for HMM (Heterogeneous Memory Management). It presents the motivation behind it, the features necessary for it to be useful and and gives an overview of how this is implemented. Changed since v2: - add section about memory accounting cgroup (memcg) Changed since v1: -

[HMM-v25 01/19] hmm: heterogeneous memory management documentation v3

This add documentation for HMM (Heterogeneous Memory Management). It presents the motivation behind it, the features necessary for it to be useful and and gives an overview of how this is implemented. Changed since v2: - add section about memory accounting cgroup (memcg) Changed since v1: -

[HMM-v25 03/19] mm/hmm/mirror: mirror process address space on device with HMM helpers v3

This is a heterogeneous memory management (HMM) process address space mirroring. In a nutshell this provide an API to mirror process address space on a device. This boils down to keeping CPU and device page table synchronize (we assume that both device and CPU are cache coherent like PCIe device

[HMM-v25 04/19] mm/hmm/mirror: helper to snapshot CPU page table v4

This does not use existing page table walker because we want to share same code for our page fault handler. Changed since v3: - fix THP handling Changed since v2: - s/device unaddressable/device private/ Changes since v1: - Use spinlock instead of rcu synchronized list traversal

[HMM-v25 02/19] mm/hmm: heterogeneous memory management (HMM for short) v5

HMM provides 3 separate types of functionality: - Mirroring: synchronize CPU page table and device page table - Device memory: allocating struct page for device memory - Migration: migrating regular memory to device memory This patch introduces some common helpers and definitions to

[HMM-v25 07/19] mm/ZONE_DEVICE: new type of ZONE_DEVICE for unaddressable memory v5

HMM (heterogeneous memory management) need struct page to support migration from system main memory to device memory. Reasons for HMM and migration to device memory is explained with HMM core patch. This patch deals with device memory that is un-addressable memory (ie CPU can not access it).

[HMM-v25 03/19] mm/hmm/mirror: mirror process address space on device with HMM helpers v3

This is a heterogeneous memory management (HMM) process address space mirroring. In a nutshell this provide an API to mirror process address space on a device. This boils down to keeping CPU and device page table synchronize (we assume that both device and CPU are cache coherent like PCIe device

[HMM-v25 04/19] mm/hmm/mirror: helper to snapshot CPU page table v4

This does not use existing page table walker because we want to share same code for our page fault handler. Changed since v3: - fix THP handling Changed since v2: - s/device unaddressable/device private/ Changes since v1: - Use spinlock instead of rcu synchronized list traversal

[HMM-v25 02/19] mm/hmm: heterogeneous memory management (HMM for short) v5

HMM provides 3 separate types of functionality: - Mirroring: synchronize CPU page table and device page table - Device memory: allocating struct page for device memory - Migration: migrating regular memory to device memory This patch introduces some common helpers and definitions to

[HMM-v25 07/19] mm/ZONE_DEVICE: new type of ZONE_DEVICE for unaddressable memory v5

HMM (heterogeneous memory management) need struct page to support migration from system main memory to device memory. Reasons for HMM and migration to device memory is explained with HMM core patch. This patch deals with device memory that is un-addressable memory (ie CPU can not access it).

[HMM-v25 09/19] mm/memcontrol: allow to uncharge page without using page->lru field

HMM pages (private or public device pages) are ZONE_DEVICE page and thus you can not use page->lru fields of those pages. This patch re-arrange the uncharge to allow single page to be uncharge without modifying the lru field of the struct page. There is no change to memcontrol logic, it is the

[HMM-v25 05/19] mm/hmm/mirror: device page fault handler

This handle page fault on behalf of device driver, unlike handle_mm_fault() it does not trigger migration back to system memory for device memory. Signed-off-by: Jérôme Glisse Signed-off-by: Evgeny Baskakov Signed-off-by: John Hubbard

[HMM-v25 09/19] mm/memcontrol: allow to uncharge page without using page->lru field

HMM pages (private or public device pages) are ZONE_DEVICE page and thus you can not use page->lru fields of those pages. This patch re-arrange the uncharge to allow single page to be uncharge without modifying the lru field of the struct page. There is no change to memcontrol logic, it is the

[HMM-v25 05/19] mm/hmm/mirror: device page fault handler

This handle page fault on behalf of device driver, unlike handle_mm_fault() it does not trigger migration back to system memory for device memory. Signed-off-by: Jérôme Glisse Signed-off-by: Evgeny Baskakov Signed-off-by: John Hubbard Signed-off-by: Mark Hairgrove Signed-off-by: Sherry Cheung

[HMM-v25 08/19] mm/ZONE_DEVICE: special case put_page() for device private pages v4

A ZONE_DEVICE page that reach a refcount of 1 is free ie no longer have any user. For device private pages this is important to catch and thus we need to special case put_page() for this. Changed since v3: - clear page mapping field Changed since v2: - clear page active and waiters Changed

Re: [PATCH 0/1] devpts: use dynamic_dname() to generate proc name

On Wed, Aug 16, 2017 at 4:51 PM, Eric W. Biederman wrote: > > *Blink* You are right I missed that. > > In which case I am concerned about failures that make it to err_release. > Unless I am missing something (again) failures that jump to err_release > won't call mntput and

[HMM-v25 08/19] mm/ZONE_DEVICE: special case put_page() for device private pages v4

A ZONE_DEVICE page that reach a refcount of 1 is free ie no longer have any user. For device private pages this is important to catch and thus we need to special case put_page() for this. Changed since v3: - clear page mapping field Changed since v2: - clear page active and waiters Changed

Re: [PATCH 0/1] devpts: use dynamic_dname() to generate proc name

On Wed, Aug 16, 2017 at 4:51 PM, Eric W. Biederman wrote: > > *Blink* You are right I missed that. > > In which case I am concerned about failures that make it to err_release. > Unless I am missing something (again) failures that jump to err_release > won't call mntput and will result in a mnt

Re: [PATCH] nokia n900: update dts with camera support

Hi, On Thu, Aug 17, 2017 at 12:23:44AM +0300, Sakari Ailus wrote: > On Wed, Aug 16, 2017 at 10:59:15PM +0200, Pavel Machek wrote: > > > On Wed, Aug 16, 2017 at 12:03:49AM +0200, Pavel Machek wrote: > > > > diff --git > > > > a/Documentation/devicetree/bindings/media/video-interfaces.txt > > > >

Re: [PATCH] nokia n900: update dts with camera support

Hi, On Thu, Aug 17, 2017 at 12:23:44AM +0300, Sakari Ailus wrote: > On Wed, Aug 16, 2017 at 10:59:15PM +0200, Pavel Machek wrote: > > > On Wed, Aug 16, 2017 at 12:03:49AM +0200, Pavel Machek wrote: > > > > diff --git > > > > a/Documentation/devicetree/bindings/media/video-interfaces.txt > > > >

[HMM-v25 12/19] mm/hmm/devmem: dummy HMM device for ZONE_DEVICE memory v3

This introduce a dummy HMM device class so device driver can use it to create hmm_device for the sole purpose of registering device memory. It is useful to device driver that want to manage multiple physical device memory under same struct device umbrella. Changed since v2: - use

[HMM-v25 12/19] mm/hmm/devmem: dummy HMM device for ZONE_DEVICE memory v3

This introduce a dummy HMM device class so device driver can use it to create hmm_device for the sole purpose of registering device memory. It is useful to device driver that want to manage multiple physical device memory under same struct device umbrella. Changed since v2: - use

[HMM-v25 11/19] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE v7

This introduce a simple struct and associated helpers for device driver to use when hotpluging un-addressable device memory as ZONE_DEVICE. It will find a unuse physical address range and trigger memory hotplug for it which allocates and initialize struct page for the device memory. Device driver

[HMM-v25 11/19] mm/hmm/devmem: device memory hotplug using ZONE_DEVICE v7

This introduce a simple struct and associated helpers for device driver to use when hotpluging un-addressable device memory as ZONE_DEVICE. It will find a unuse physical address range and trigger memory hotplug for it which allocates and initialize struct page for the device memory. Device driver

[HMM-v25 16/19] mm/migrate: support un-addressable ZONE_DEVICE page in migration v3

Allow to unmap and restore special swap entry of un-addressable ZONE_DEVICE memory. Changed since v2: - un-conditionaly allow device private memory to be migrated (it can not be pin to pointless to check reference count). Changed since v1: - s/device unaddressable/device private/

[HMM-v25 16/19] mm/migrate: support un-addressable ZONE_DEVICE page in migration v3

Allow to unmap and restore special swap entry of un-addressable ZONE_DEVICE memory. Changed since v2: - un-conditionaly allow device private memory to be migrated (it can not be pin to pointless to check reference count). Changed since v1: - s/device unaddressable/device private/

[HMM-v25 15/19] mm/migrate: migrate_vma() unmap page from vma while collecting pages

Common case for migration of virtual address range is page are map only once inside the vma in which migration is taking place. Because we already walk the CPU page table for that range we can directly do the unmap there and setup special migration swap entry. Signed-off-by: Jérôme Glisse

[HMM-v25 15/19] mm/migrate: migrate_vma() unmap page from vma while collecting pages

Common case for migration of virtual address range is page are map only once inside the vma in which migration is taking place. Because we already walk the CPU page table for that range we can directly do the unmap there and setup special migration swap entry. Signed-off-by: Jérôme Glisse

[HMM-v25 14/19] mm/migrate: new memory migration helper for use with device memory v5

This patch add a new memory migration helpers, which migrate memory backing a range of virtual address of a process to different memory (which can be allocated through special allocator). It differs from numa migration by working on a range of virtual address and thus by doing migration in chunk

[HMM-v25 14/19] mm/migrate: new memory migration helper for use with device memory v5

This patch add a new memory migration helpers, which migrate memory backing a range of virtual address of a process to different memory (which can be allocated through special allocator). It differs from numa migration by working on a range of virtual address and thus by doing migration in chunk

[HMM-v25 19/19] mm/hmm: add new helper to hotplug CDM memory region v3

Unlike unaddressable memory, coherent device memory has a real resource associated with it on the system (as CPU can address it). Add a new helper to hotplug such memory within the HMM framework. Changed since v2: - s/host/public Changed since v1: - s/public/host Signed-off-by: Jérôme Glisse

[HMM-v25 06/19] mm/memory_hotplug: introduce add_pages

From: Michal Hocko There are new users of memory hotplug emerging. Some of them require different subset of arch_add_memory. There are some which only require allocation of struct pages without mapping those pages to the kernel address space. We currently have __add_pages for

[HMM-v25 19/19] mm/hmm: add new helper to hotplug CDM memory region v3

Unlike unaddressable memory, coherent device memory has a real resource associated with it on the system (as CPU can address it). Add a new helper to hotplug such memory within the HMM framework. Changed since v2: - s/host/public Changed since v1: - s/public/host Signed-off-by: Jérôme Glisse

[HMM-v25 06/19] mm/memory_hotplug: introduce add_pages

From: Michal Hocko There are new users of memory hotplug emerging. Some of them require different subset of arch_add_memory. There are some which only require allocation of struct pages without mapping those pages to the kernel address space. We currently have __add_pages for that purpose. But

[HMM-v25 17/19] mm/migrate: allow migrate_vma() to alloc new page on empty entry v4

This allow caller of migrate_vma() to allocate new page for empty CPU page table entry (pte_none or back by zero page). This is only for anonymous memory and it won't allow new page to be instanced if the userfaultfd is armed. This is useful to device driver that want to migrate a range of

[HMM-v25 18/19] mm/device-public-memory: device memory cache coherent with CPU v5

Platform with advance system bus (like CAPI or CCIX) allow device memory to be accessible from CPU in a cache coherent fashion. Add a new type of ZONE_DEVICE to represent such memory. The use case are the same as for the un-addressable device memory but without all the corners cases. Changed

[HMM-v25 17/19] mm/migrate: allow migrate_vma() to alloc new page on empty entry v4

This allow caller of migrate_vma() to allocate new page for empty CPU page table entry (pte_none or back by zero page). This is only for anonymous memory and it won't allow new page to be instanced if the userfaultfd is armed. This is useful to device driver that want to migrate a range of

[HMM-v25 18/19] mm/device-public-memory: device memory cache coherent with CPU v5

Platform with advance system bus (like CAPI or CCIX) allow device memory to be accessible from CPU in a cache coherent fashion. Add a new type of ZONE_DEVICE to represent such memory. The use case are the same as for the un-addressable device memory but without all the corners cases. Changed

[HMM-v25 00/19] HMM (Heterogeneous Memory Management) v25

Patchset is on top of git://git.cmpxchg.org/linux-mmotm.git so i test same kernel as kbuild system, git branch: https://cgit.freedesktop.org/~glisse/linux/log/?h=hmm-v25 Change since v24 are: - more comments and more documentations - fix dumb mistake when registering device - fix race when

[HMM-v25 13/19] mm/migrate: new migrate mode MIGRATE_SYNC_NO_COPY

Introduce a new migration mode that allow to offload the copy to a device DMA engine. This changes the workflow of migration and not all address_space migratepage callback can support this. So it needs to be tested in those cases. This is intended to be use by migrate_vma() which itself is use

[HMM-v25 00/19] HMM (Heterogeneous Memory Management) v25

Patchset is on top of git://git.cmpxchg.org/linux-mmotm.git so i test same kernel as kbuild system, git branch: https://cgit.freedesktop.org/~glisse/linux/log/?h=hmm-v25 Change since v24 are: - more comments and more documentations - fix dumb mistake when registering device - fix race when

[HMM-v25 13/19] mm/migrate: new migrate mode MIGRATE_SYNC_NO_COPY

Introduce a new migration mode that allow to offload the copy to a device DMA engine. This changes the workflow of migration and not all address_space migratepage callback can support this. So it needs to be tested in those cases. This is intended to be use by migrate_vma() which itself is use

[HMM-v25 10/19] mm/memcontrol: support MEMORY_DEVICE_PRIVATE v4

HMM pages (private or public device pages) are ZONE_DEVICE page and thus need special handling when it comes to lru or refcount. This patch make sure that memcontrol properly handle those when it face them. Those pages are use like regular pages in a process address space either as anonymous page

[HMM-v25 10/19] mm/memcontrol: support MEMORY_DEVICE_PRIVATE v4

HMM pages (private or public device pages) are ZONE_DEVICE page and thus need special handling when it comes to lru or refcount. This patch make sure that memcontrol properly handle those when it face them. Those pages are use like regular pages in a process address space either as anonymous page

Re: [GIT PULL] Audit fixes for v4.13 (#2)

On Wed, Aug 16, 2017 at 12:19 PM, Paul Moore wrote: > > It's also worth mentioning, as you'll soon notice when you get to the > bottom of this email, that I've moved the audit tree over to > kernel.org and I'm now tagging/signing these pull requests; everything > *should* be

Re: [GIT PULL] Audit fixes for v4.13 (#2)

On Wed, Aug 16, 2017 at 12:19 PM, Paul Moore wrote: > > It's also worth mentioning, as you'll soon notice when you get to the > bottom of this email, that I've moved the audit tree over to > kernel.org and I'm now tagging/signing these pull requests; everything > *should* be in order, but if I've

Re: [PATCH 0/1] devpts: use dynamic_dname() to generate proc name

Linus Torvalds writes: > On Wed, Aug 16, 2017 at 3:46 PM, Eric W. Biederman > wrote: >>> tty->link->driver_data = pts_path; >>> >>> retval = ptm_driver->ops->open(tty, filp); >> ^^^ >> >> If this open fails the code

Re: [PATCH 0/1] devpts: use dynamic_dname() to generate proc name

Linus Torvalds writes: > On Wed, Aug 16, 2017 at 3:46 PM, Eric W. Biederman > wrote: >>> tty->link->driver_data = pts_path; >>> >>> retval = ptm_driver->ops->open(tty, filp); >> ^^^ >> >> If this open fails the code jumps to err_put_path which falls >> through into

Re: [PATCH v2 1/3] ASoC: rockchip: Parse dai links from dts

El Thu, Aug 17, 2017 at 06:55:20AM +0800 jeffy ha dit: > hi matthias, > > thanks for your suggestion. > > On 08/17/2017 05:59 AM, Matthias Kaehlcke wrote: > >El Thu, Aug 10, 2017 at 12:54:56PM +0800 Jeffy Chen ha dit: > > > >>>Refactor rockchip_sound_probe, parse dai links from dts instead of >

Re: [PATCH v2 1/3] ASoC: rockchip: Parse dai links from dts

El Thu, Aug 17, 2017 at 06:55:20AM +0800 jeffy ha dit: > hi matthias, > > thanks for your suggestion. > > On 08/17/2017 05:59 AM, Matthias Kaehlcke wrote: > >El Thu, Aug 10, 2017 at 12:54:56PM +0800 Jeffy Chen ha dit: > > > >>>Refactor rockchip_sound_probe, parse dai links from dts instead of >

Re: Do we really need d_weak_revalidate???

On Wed, Aug 16 2017, Jeff Layton wrote: > On Wed, 2017-08-16 at 12:43 +1000, NeilBrown wrote: >> On Mon, Aug 14 2017, Jeff Layton wrote: >> >> > On Mon, 2017-08-14 at 09:36 +1000, NeilBrown wrote: >> > > On Fri, Aug 11 2017, Jeff Layton wrote: >> > > >> > > > On Fri, 2017-08-11 at 05:55 +,

Re: Do we really need d_weak_revalidate???

On Wed, Aug 16 2017, Jeff Layton wrote: > On Wed, 2017-08-16 at 12:43 +1000, NeilBrown wrote: >> On Mon, Aug 14 2017, Jeff Layton wrote: >> >> > On Mon, 2017-08-14 at 09:36 +1000, NeilBrown wrote: >> > > On Fri, Aug 11 2017, Jeff Layton wrote: >> > > >> > > > On Fri, 2017-08-11 at 05:55 +,

Re: [PATCH v5 0/5] MAP_DIRECT and block-map-atomic files

On Wed, Aug 16, 2017 at 12:44 AM, Dan Williams wrote: > Changes since v4 [1]: > * Drop the new vma ->fs_flags field, it can be replaced by just checking > ->vm_ops locally in the filesystem. This approach also allows > non-MAP_DIRECT vmas to be vma_merge() capable

Re: [PATCH v5 0/5] MAP_DIRECT and block-map-atomic files

On Wed, Aug 16, 2017 at 12:44 AM, Dan Williams wrote: > Changes since v4 [1]: > * Drop the new vma ->fs_flags field, it can be replaced by just checking > ->vm_ops locally in the filesystem. This approach also allows > non-MAP_DIRECT vmas to be vma_merge() capable since vmas with >

Re: [PATCH] Adding-Agile-SD-TCP-module-and-modifying-Kconfig-and-makefile

Hi mohamedalrshah, [auto build test ERROR on net/master] [also build test ERROR on v4.13-rc5 next-20170816] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/mohamedalrshah/Adding-Agile-SD-TCP

Re: [PATCH] Adding-Agile-SD-TCP-module-and-modifying-Kconfig-and-makefile

Hi mohamedalrshah, [auto build test ERROR on net/master] [also build test ERROR on v4.13-rc5 next-20170816] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/mohamedalrshah/Adding-Agile-SD-TCP

Re: [PATCH] selftests: futex: convert test to use ksft TAP13 framework

On Fri, Aug 04, 2017 at 06:46:50PM -0600, Shuah Khan wrote: > Convert test to use ksft TAP13 framework. > Please include some information in the commit about why we're doing this and what it is. >From what I can tell this is converting raw printk to a wrapped set of logging functions to produce

Re: [PATCH] selftests: futex: convert test to use ksft TAP13 framework

On Fri, Aug 04, 2017 at 06:46:50PM -0600, Shuah Khan wrote: > Convert test to use ksft TAP13 framework. > Please include some information in the commit about why we're doing this and what it is. >From what I can tell this is converting raw printk to a wrapped set of logging functions to produce

<    1   2   3   4   5   6   7   8   9   10   >