[PATCH v1 07/10] mm/memory_hotplug: print only with DEBUG_VM in online/offline_pages()

Let's try to minimze the noise. Cc: Andrew Morton Cc: Michal Hocko Cc: Vlastimil Babka Cc: Dan Williams Cc: Reza Arbab Cc: Pavel Tatashin Cc: Thomas

[PATCH v1 07/10] mm/memory_hotplug: print only with DEBUG_VM in online/offline_pages()

Let's try to minimze the noise. Cc: Andrew Morton Cc: Michal Hocko Cc: Vlastimil Babka Cc: Dan Williams Cc: Reza Arbab Cc: Pavel Tatashin Cc: Thomas Gleixner Signed-off-by: David Hildenbrand --- mm/memory_hotplug.c | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH v1 10/10] mm/memory_hotplug: allow online/offline memory by a kernel module

Kernel modules that want to control how/when memory is onlined/offlined need a proper interface to these functions. Also, for adding memory properly, memory_block_size_bytes is required. Cc: Greg Kroah-Hartman Cc: Andrew Morton Cc:

[PATCH v1 10/10] mm/memory_hotplug: allow online/offline memory by a kernel module

Kernel modules that want to control how/when memory is onlined/offlined need a proper interface to these functions. Also, for adding memory properly, memory_block_size_bytes is required. Cc: Greg Kroah-Hartman Cc: Andrew Morton Cc: Vlastimil Babka Cc: Michal Hocko Cc: Dan Williams Cc: Pavel

[PATCH v1 08/10] mm/memory_hotplug: allow to control onlining/offlining of memory by a driver

Some devices (esp. paravirtualized) might want to control - when to online/offline a memory block - how to online memory (MOVABLE/NORMAL) - in which granularity to online/offline memory So let's add a new flag "driver_managed" and disallow to change the state by user space. Device

[PATCH v1 08/10] mm/memory_hotplug: allow to control onlining/offlining of memory by a driver

Some devices (esp. paravirtualized) might want to control - when to online/offline a memory block - how to online memory (MOVABLE/NORMAL) - in which granularity to online/offline memory So let's add a new flag "driver_managed" and disallow to change the state by user space. Device

[PATCH v1 09/10] mm/memory_hotplug: teach offline_pages() to not try forever

It can easily happen that we get stuck forever trying to offline pages - e.g. on persistent errors. Let's add a way to change this behavior and fail fast. This is interesting if offline_pages() is called from a driver and we just want to find some block to offline. Cc: Benjamin Herrenschmidt

[PATCH v1 09/10] mm/memory_hotplug: teach offline_pages() to not try forever

It can easily happen that we get stuck forever trying to offline pages - e.g. on persistent errors. Let's add a way to change this behavior and fail fast. This is interesting if offline_pages() is called from a driver and we just want to find some block to offline. Cc: Benjamin Herrenschmidt

Re: [PATCH v2 2/5] gpio: syscon: Add gpio-syscon for rockchip

Hi Rob, Levin, sorry for being late to the party. Am Mittwoch, 23. Mai 2018, 16:43:07 CEST schrieb Rob Herring: > On Tue, May 22, 2018 at 9:02 PM, Levin Du wrote: > > On 2018-05-23 2:02 AM, Rob Herring wrote: > >> On Fri, May 18, 2018 at 11:52:05AM +0800, d...@t-chip.com.cn

Re: [PATCH v2 2/5] gpio: syscon: Add gpio-syscon for rockchip

Hi Rob, Levin, sorry for being late to the party. Am Mittwoch, 23. Mai 2018, 16:43:07 CEST schrieb Rob Herring: > On Tue, May 22, 2018 at 9:02 PM, Levin Du wrote: > > On 2018-05-23 2:02 AM, Rob Herring wrote: > >> On Fri, May 18, 2018 at 11:52:05AM +0800, d...@t-chip.com.cn wrote: > >>> From:

[PATCH v1 00/10] mm: online/offline 4MB chunks controlled by device driver

This is now the !RFC version. I did some additional tests and inspected all memory notifiers. At least page_ext and kasan need fixes. == I am right now working on a paravirtualized memory device ("virtio-mem"). These devices control a memory region and the amount of memory available via

[PATCH v1 00/10] mm: online/offline 4MB chunks controlled by device driver

This is now the !RFC version. I did some additional tests and inspected all memory notifiers. At least page_ext and kasan need fixes. == I am right now working on a paravirtualized memory device ("virtio-mem"). These devices control a memory region and the amount of memory available via

[PATCH v1 03/10] kasan: prepare for online/offline of different start/size

The memory notifier has an important restriction right now: it only works if offline_pages() is called with the same parameters as online_pages(). To overcome this restriction, let's handle it per section. We could do it in smaller granularity, but then we get more vm_area overhead and cannot

[PATCH v1 03/10] kasan: prepare for online/offline of different start/size

The memory notifier has an important restriction right now: it only works if offline_pages() is called with the same parameters as online_pages(). To overcome this restriction, let's handle it per section. We could do it in smaller granularity, but then we get more vm_area overhead and cannot

Re: [PATCH 2/3] drm/scheduler: Don't call wait_event_killable for signaled process.

On 05/01/2018 10:35 AM, Oleg Nesterov wrote: On 04/30, Andrey Grodzovsky wrote: On 04/30/2018 12:00 PM, Oleg Nesterov wrote: On 04/30, Andrey Grodzovsky wrote: What about changing PF_SIGNALED to  PF_EXITING in drm_sched_entity_do_release -   if ((current->flags & PF_SIGNALED) &&

Re: [PATCH 2/3] drm/scheduler: Don't call wait_event_killable for signaled process.

On 05/01/2018 10:35 AM, Oleg Nesterov wrote: On 04/30, Andrey Grodzovsky wrote: On 04/30/2018 12:00 PM, Oleg Nesterov wrote: On 04/30, Andrey Grodzovsky wrote: What about changing PF_SIGNALED to  PF_EXITING in drm_sched_entity_do_release -   if ((current->flags & PF_SIGNALED) &&

Re: [PATCH] kernel: sys: fix potential Spectre v1

On Wed, May 23, 2018 at 11:08:40AM +0200, Peter Zijlstra wrote: > > Sorry for being late to the party.. Likewise! > On Wed, May 23, 2018 at 12:03:57AM -0500, Gustavo A. R. Silva wrote: > > +#define validate_index_nospec(index, size)\ > > +({

Re: [PATCH] kernel: sys: fix potential Spectre v1

On Wed, May 23, 2018 at 11:08:40AM +0200, Peter Zijlstra wrote: > > Sorry for being late to the party.. Likewise! > On Wed, May 23, 2018 at 12:03:57AM -0500, Gustavo A. R. Silva wrote: > > +#define validate_index_nospec(index, size)\ > > +({

Re: [PATCH] nvme: host: core: fix precedence of ternary operator

On 5/23/2018 5:56 PM, Ivan Bornyakov wrote: Ternary operator have lower precedence then bitwise or, so 'cdw10' was calculated wrong. Signed-off-by: Ivan Bornyakov --- drivers/nvme/host/core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

Re: [PATCH] nvme: host: core: fix precedence of ternary operator

On 5/23/2018 5:56 PM, Ivan Bornyakov wrote: Ternary operator have lower precedence then bitwise or, so 'cdw10' was calculated wrong. Signed-off-by: Ivan Bornyakov --- drivers/nvme/host/core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/nvme/host/core.c

Re: [PATCH v3] nvme: fix lockdep warning in nvme_mpath_clear_current_path

Thanks for the ping. I started a new branch, nvme-4.18-2, based off of Jens' for-next with this being the first new commit. I'm certain we're still missing a lot of reviewed commits. I'll try to go through the mail history and apply by the end of the week, but any friendly reminders would not be

Re: [PATCH v3] nvme: fix lockdep warning in nvme_mpath_clear_current_path

Thanks for the ping. I started a new branch, nvme-4.18-2, based off of Jens' for-next with this being the first new commit. I'm certain we're still missing a lot of reviewed commits. I'll try to go through the mail history and apply by the end of the week, but any friendly reminders would not be

Re: [alsa-devel] [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files

On Wed, 23 May 2018 16:49:35 +0200, Guenter Roeck wrote: > > On Wed, May 23, 2018 at 6:56 AM Takashi Iwai wrote: > > > > > > > > My point was a bit different: distributions like Gallium start without > > > the relevant topology files and UCM settings, and we should have a > > >

Re: [alsa-devel] [RFC/RFT PATCH] ASoC: topology: Improve backwards compatibility with v4 topology files

On Wed, 23 May 2018 16:49:35 +0200, Guenter Roeck wrote: > > On Wed, May 23, 2018 at 6:56 AM Takashi Iwai wrote: > > > > > > > > My point was a bit different: distributions like Gallium start without > > > the relevant topology files and UCM settings, and we should have a > > > reference to

Re: [PATCH RT] arm64: fpsimd: use a local_lock() in addition to local_bh_disable()

On Wed, May 23, 2018 at 04:31:56PM +0200, Sebastian Andrzej Siewior wrote: > On 2018-05-17 19:19:43 [+0100], Dave Martin wrote: > > On Thu, May 17, 2018 at 02:40:06PM +0200, Sebastian Andrzej Siewior wrote: > > > In v4.16-RT I noticed a number of warnings from task_fpsimd_load(). The > > > code

Re: [PATCH RT] arm64: fpsimd: use a local_lock() in addition to local_bh_disable()

On Wed, May 23, 2018 at 04:31:56PM +0200, Sebastian Andrzej Siewior wrote: > On 2018-05-17 19:19:43 [+0100], Dave Martin wrote: > > On Thu, May 17, 2018 at 02:40:06PM +0200, Sebastian Andrzej Siewior wrote: > > > In v4.16-RT I noticed a number of warnings from task_fpsimd_load(). The > > > code

Re: [PATCH v3] nvme: fix lockdep warning in nvme_mpath_clear_current_path

Keith, Sagi, Christoph ping? -- Johannes Thumshirn Storage jthumsh...@suse.de+49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Key

Re: [PATCH v3] nvme: fix lockdep warning in nvme_mpath_clear_current_path

Keith, Sagi, Christoph ping? -- Johannes Thumshirn Storage jthumsh...@suse.de+49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Key

[PATCH] nvme: host: core: fix precedence of ternary operator

Ternary operator have lower precedence then bitwise or, so 'cdw10' was calculated wrong. Signed-off-by: Ivan Bornyakov --- drivers/nvme/host/core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c

[PATCH] nvme: host: core: fix precedence of ternary operator

Ternary operator have lower precedence then bitwise or, so 'cdw10' was calculated wrong. Signed-off-by: Ivan Bornyakov --- drivers/nvme/host/core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c index

Re: [RFC PATCH 5/5] remoteproc: qcom: Introduce Hexagon V5 based WCSS driver

Hi Bjorn, On 5/23/2018 1:07 PM, Vinod wrote: > On 22-05-18, 23:58, Bjorn Andersson wrote: >> On Tue 22 May 23:05 PDT 2018, Vinod wrote: >> >>> On 22-05-18, 22:20, Bjorn Andersson wrote: >>> +static int q6v5_wcss_reset(struct q6v5_wcss *wcss) +{ + int ret; + u32 val; +

Re: [RFC PATCH 5/5] remoteproc: qcom: Introduce Hexagon V5 based WCSS driver

Hi Bjorn, On 5/23/2018 1:07 PM, Vinod wrote: > On 22-05-18, 23:58, Bjorn Andersson wrote: >> On Tue 22 May 23:05 PDT 2018, Vinod wrote: >> >>> On 22-05-18, 22:20, Bjorn Andersson wrote: >>> +static int q6v5_wcss_reset(struct q6v5_wcss *wcss) +{ + int ret; + u32 val; +

Re: [PATCH] Use 'imply' with SEV Kconfig CRYPTO dependencies

+ Tom and Brijesh. On Mon, May 21, 2018 at 10:12:53AM -0500, Janakarajan Natarajan wrote: > Use Kconfig imply 'option' when specifying SEV CRYPTO dependencies. > > Example configuration: > . > . > CONFIG_CRYPTO_DEV_CCP=y > CONFIG_CRYPTO_DEV_CCP_DD=m > CONFIG_CRYPTO_DEV_SP_CCP=y >

Re: [PATCH 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On Wed, 23 May 2018 09:33:30 -0500 "Alex G." wrote: > > Well I'll agree to disagree with Linus on this one. It's ugly as fsck > > and allows for ambiguous statements in the code. > > You misspelled "fuck". No, Jes is Danish. That's how they spell it. -- Steve

Re: [PATCH 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On Wed, 23 May 2018 09:33:30 -0500 "Alex G." wrote: > > Well I'll agree to disagree with Linus on this one. It's ugly as fsck > > and allows for ambiguous statements in the code. > > You misspelled "fuck". No, Jes is Danish. That's how they spell it. -- Steve

Re: [PATCH] Use 'imply' with SEV Kconfig CRYPTO dependencies

+ Tom and Brijesh. On Mon, May 21, 2018 at 10:12:53AM -0500, Janakarajan Natarajan wrote: > Use Kconfig imply 'option' when specifying SEV CRYPTO dependencies. > > Example configuration: > . > . > CONFIG_CRYPTO_DEV_CCP=y > CONFIG_CRYPTO_DEV_CCP_DD=m > CONFIG_CRYPTO_DEV_SP_CCP=y >

Re: [PATCH v1] cpufreq: tegra20: Fix imbalanced clock enable count

On 23.05.2018 13:44, Dmitry Osipenko wrote: > On 23.05.2018 08:58, Viresh Kumar wrote: >> On 23-05-18, 00:14, Dmitry Osipenko wrote: >>> Tegra20-cpufreq driver missed enabling the CPU clocks. This results in a >>> clock-enable refcount disbalance on PLL_P <-> PLL_X reparent, causing >>> PLL_X to

Re: [PATCH v1] cpufreq: tegra20: Fix imbalanced clock enable count

On 23.05.2018 13:44, Dmitry Osipenko wrote: > On 23.05.2018 08:58, Viresh Kumar wrote: >> On 23-05-18, 00:14, Dmitry Osipenko wrote: >>> Tegra20-cpufreq driver missed enabling the CPU clocks. This results in a >>> clock-enable refcount disbalance on PLL_P <-> PLL_X reparent, causing >>> PLL_X to

Re: [PATCH v5 11/13] KVM: s390: implement mediated device open callback

On 05/16/2018 04:03 AM, Pierre Morel wrote: On 07/05/2018 17:11, Tony Krowiak wrote: Implements the open callback on the mediated matrix device. The function registers a group notifier to receive notification of the VFIO_GROUP_NOTIFY_SET_KVM event. When notified, the vfio_ap device driver will

Re: [PATCH v5 11/13] KVM: s390: implement mediated device open callback

On 05/16/2018 04:03 AM, Pierre Morel wrote: On 07/05/2018 17:11, Tony Krowiak wrote: Implements the open callback on the mediated matrix device. The function registers a group notifier to receive notification of the VFIO_GROUP_NOTIFY_SET_KVM event. When notified, the vfio_ap device driver will

[PATCH v2] gpu: drm: gma500: Change return type to vm_fault_t

Use new return type vm_fault_t for fault handler. For now, this is just documenting that the function returns a VM_FAULT value rather than an errno. Once all instances are converted, vm_fault_t will become a distinct type. Ref-> commit 1c8f422059ae ("mm: change return type to vm_fault_t")

[PATCH v2] gpu: drm: gma500: Change return type to vm_fault_t

Use new return type vm_fault_t for fault handler. For now, this is just documenting that the function returns a VM_FAULT value rather than an errno. Once all instances are converted, vm_fault_t will become a distinct type. Ref-> commit 1c8f422059ae ("mm: change return type to vm_fault_t")

Re: [PATCH v2 2/5] gpio: syscon: Add gpio-syscon for rockchip

On Tue, May 22, 2018 at 9:02 PM, Levin Du wrote: > On 2018-05-23 2:02 AM, Rob Herring wrote: >> >> On Fri, May 18, 2018 at 11:52:05AM +0800, d...@t-chip.com.cn wrote: >>> >>> From: Levin Du >>> >>> Some GPIOs sit in the GRF_SOC_CON registers of Rockchip

Re: [PATCH v2 2/5] gpio: syscon: Add gpio-syscon for rockchip

On Tue, May 22, 2018 at 9:02 PM, Levin Du wrote: > On 2018-05-23 2:02 AM, Rob Herring wrote: >> >> On Fri, May 18, 2018 at 11:52:05AM +0800, d...@t-chip.com.cn wrote: >>> >>> From: Levin Du >>> >>> Some GPIOs sit in the GRF_SOC_CON registers of Rockchip SoCs, >>> which do not belong to the

Re: [PATCH 25/33] ima: use match_string() helper

On Mon, 2018-05-21 at 19:58 +0800, Yisheng Xie wrote: > match_string() returns the index of an array for a matching string, > which can be used intead of open coded variant. > > Cc: Mimi Zohar > Cc: Dmitry Kasatkin > Cc: James Morris

Re: [PATCH 25/33] ima: use match_string() helper

On Mon, 2018-05-21 at 19:58 +0800, Yisheng Xie wrote: > match_string() returns the index of an array for a matching string, > which can be used intead of open coded variant. > > Cc: Mimi Zohar > Cc: Dmitry Kasatkin > Cc: James Morris > Cc: "Serge E. Hallyn" > Cc:

Re: [PATCH v2] PM / devfreq: Add support for QCOM devfreq firmware

On Tue, May 22, 2018 at 1:30 PM, Saravana Kannan wrote: > On 05/22/2018 11:08 AM, Rob Herring wrote: >> >> On Fri, May 18, 2018 at 12:52:40AM -0700, Saravana Kannan wrote: >>> >>> The firmware present in some QCOM chipsets offloads the steps necessary >>> for >>> changing

Re: [PATCH v2] PM / devfreq: Add support for QCOM devfreq firmware

On Tue, May 22, 2018 at 1:30 PM, Saravana Kannan wrote: > On 05/22/2018 11:08 AM, Rob Herring wrote: >> >> On Fri, May 18, 2018 at 12:52:40AM -0700, Saravana Kannan wrote: >>> >>> The firmware present in some QCOM chipsets offloads the steps necessary >>> for >>> changing the frequency of some

[PATCH v2 1/3] usb: roles: intel_xhci: Always allow user control

Trying to determine the USB port type with this mux is very difficult. To simplify the situation, always allowing user control, even if the port is USB Type-C port. Signed-off-by: Heikki Krogerus --- .../usb/roles/intel-xhci-usb-role-switch.c| 21

[PATCH v2 1/3] usb: roles: intel_xhci: Always allow user control

Trying to determine the USB port type with this mux is very difficult. To simplify the situation, always allowing user control, even if the port is USB Type-C port. Signed-off-by: Heikki Krogerus --- .../usb/roles/intel-xhci-usb-role-switch.c| 21 +-- 1 file changed, 1

[PATCH v2 2/3] platform: x86: intel_cht_int33fe: Fix dependencies

The driver will not probe unless bq24190 is loaded, so making it a dependency. Signed-off-by: Heikki Krogerus Cc: Wolfram Sang Cc: Darren Hart Cc: Andy Shevchenko ---

[PATCH v2 2/3] platform: x86: intel_cht_int33fe: Fix dependencies

The driver will not probe unless bq24190 is loaded, so making it a dependency. Signed-off-by: Heikki Krogerus Cc: Wolfram Sang Cc: Darren Hart Cc: Andy Shevchenko --- drivers/i2c/busses/Kconfig | 3 +-- drivers/platform/x86/Kconfig | 4 ++-- 2 files changed, 3 insertions(+), 4 deletions(-)

Re: [PATCH v5 10/13] s390: vfio-ap: sysfs interface to view matrix mdev matrix

On 05/16/2018 03:55 AM, Pierre Morel wrote: On 07/05/2018 17:11, Tony Krowiak wrote: Provides a sysfs interface to view the AP matrix configured for the mediated matrix device. The relevant sysfs structures are: /sys/devices/vfio_ap ... [matrix] .. [mdev_supported_types] .

Re: [PATCH v5 10/13] s390: vfio-ap: sysfs interface to view matrix mdev matrix

On 05/16/2018 03:55 AM, Pierre Morel wrote: On 07/05/2018 17:11, Tony Krowiak wrote: Provides a sysfs interface to view the AP matrix configured for the mediated matrix device. The relevant sysfs structures are: /sys/devices/vfio_ap ... [matrix] .. [mdev_supported_types] .

[PATCH v2 3/3] usb: typec: fusb302: Fix debugfs issue

Removing the "fusb302" debugfs directory when unloading the driver. That allows the driver to be loaded more then ones. The directory will not get actually removed until it is empty, so only after the last instance has been removed. This fixes an issue where the driver can't be re-loaded if it

[PATCH v2 3/3] usb: typec: fusb302: Fix debugfs issue

Removing the "fusb302" debugfs directory when unloading the driver. That allows the driver to be loaded more then ones. The directory will not get actually removed until it is empty, so only after the last instance has been removed. This fixes an issue where the driver can't be re-loaded if it

[PATCH v2 0/3] [PATCH 0/4] usb: typec: fixes for Cherry Trails

Hi, This is second version of the remaining patches that fix various problems I encountered while testing my USB Type-C Alternate Mode patches with GPD Win board (Intel Cherry Trail based). In this version I've addressed the problems pointed out by Hans and Guenter. Link to the original version:

[PATCH v2 0/3] [PATCH 0/4] usb: typec: fixes for Cherry Trails

Hi, This is second version of the remaining patches that fix various problems I encountered while testing my USB Type-C Alternate Mode patches with GPD Win board (Intel Cherry Trail based). In this version I've addressed the problems pointed out by Hans and Guenter. Link to the original version:

Re: [PATCH RT] arm64: fpsimd: use a local_lock() in addition to local_bh_disable()

On 2018-05-18 13:46:36 [+0100], Dave Martin wrote: > On Thu, May 17, 2018 at 07:19:43PM +0100, Dave Martin wrote: > > [...] > > > kernel_neon_begin() could then do > > > > local_fpsimd_context_lock(); > > > > /* ... */ > > > > preempt_disable(); > >

Re: [PATCH RT] arm64: fpsimd: use a local_lock() in addition to local_bh_disable()

On 2018-05-18 13:46:36 [+0100], Dave Martin wrote: > On Thu, May 17, 2018 at 07:19:43PM +0100, Dave Martin wrote: > > [...] > > > kernel_neon_begin() could then do > > > > local_fpsimd_context_lock(); > > > > /* ... */ > > > > preempt_disable(); > >

Re: [PATCH v9 3/4] arm64: Implement page table free interfaces

On Wed, 2018-05-23 at 15:01 +0100, Will Deacon wrote: > Hi Chintan, > > [as a side note: I'm confused on the status of this patch series, as part > of it was reposted separately by Toshi. Please can you work together?] I do not know the status of my patch series, either... That being said, I

Re: [PATCH v9 3/4] arm64: Implement page table free interfaces

On Wed, 2018-05-23 at 15:01 +0100, Will Deacon wrote: > Hi Chintan, > > [as a side note: I'm confused on the status of this patch series, as part > of it was reposted separately by Toshi. Please can you work together?] I do not know the status of my patch series, either... That being said, I

Re: [PATCH 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On 05/23/2018 10:26 AM, Matthew Wilcox wrote: > On Wed, May 23, 2018 at 10:20:10AM -0400, Jes Sorensen wrote: >>> +++ b/drivers/pci/pcie/aer/aerdrv_stats.c >>> @@ -0,0 +1,64 @@ >>> +// SPDX-License-Identifier: GPL-2.0 >> >> Fix the formatting please - that gross // gibberish doesn't belong there.

Re: [PATCH 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On 05/23/2018 10:26 AM, Matthew Wilcox wrote: > On Wed, May 23, 2018 at 10:20:10AM -0400, Jes Sorensen wrote: >>> +++ b/drivers/pci/pcie/aer/aerdrv_stats.c >>> @@ -0,0 +1,64 @@ >>> +// SPDX-License-Identifier: GPL-2.0 >> >> Fix the formatting please - that gross // gibberish doesn't belong there.

Re: [PATCH 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On 05/23/2018 09:32 AM, Jes Sorensen wrote: > On 05/23/2018 10:26 AM, Matthew Wilcox wrote: >> On Wed, May 23, 2018 at 10:20:10AM -0400, Jes Sorensen wrote: +++ b/drivers/pci/pcie/aer/aerdrv_stats.c @@ -0,0 +1,64 @@ +// SPDX-License-Identifier: GPL-2.0 >>> >>> Fix the formatting

Re: [PATCH 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On 05/23/2018 09:32 AM, Jes Sorensen wrote: > On 05/23/2018 10:26 AM, Matthew Wilcox wrote: >> On Wed, May 23, 2018 at 10:20:10AM -0400, Jes Sorensen wrote: +++ b/drivers/pci/pcie/aer/aerdrv_stats.c @@ -0,0 +1,64 @@ +// SPDX-License-Identifier: GPL-2.0 >>> >>> Fix the formatting

Re: [PATCH RT] arm64: fpsimd: use a local_lock() in addition to local_bh_disable()

On 2018-05-17 19:19:43 [+0100], Dave Martin wrote: > On Thu, May 17, 2018 at 02:40:06PM +0200, Sebastian Andrzej Siewior wrote: > > In v4.16-RT I noticed a number of warnings from task_fpsimd_load(). The > > code disables BH and expects that it is not preemptible. On -RT the > > task remains

Re: [PATCH RT] arm64: fpsimd: use a local_lock() in addition to local_bh_disable()

On 2018-05-17 19:19:43 [+0100], Dave Martin wrote: > On Thu, May 17, 2018 at 02:40:06PM +0200, Sebastian Andrzej Siewior wrote: > > In v4.16-RT I noticed a number of warnings from task_fpsimd_load(). The > > code disables BH and expects that it is not preemptible. On -RT the > > task remains

Re: [PATCH 3/6] block: Create scsi_sense.h for SCSI and ATAPI

On 5/23/18 8:25 AM, Christoph Hellwig wrote: > On Wed, May 23, 2018 at 08:13:56AM -0600, Jens Axboe wrote: >>> Should I move to code to a new drivers/scsi/scsi_sense.c and add it to >>> drivers/scsi/Makefile as: >>> >>> obj-$(CONFIG_BLK_SCSI_REQUEST)+= scsi_sense.o >>> >>> Every place I want

Re: [PATCH 3/6] block: Create scsi_sense.h for SCSI and ATAPI

On 5/23/18 8:25 AM, Christoph Hellwig wrote: > On Wed, May 23, 2018 at 08:13:56AM -0600, Jens Axboe wrote: >>> Should I move to code to a new drivers/scsi/scsi_sense.c and add it to >>> drivers/scsi/Makefile as: >>> >>> obj-$(CONFIG_BLK_SCSI_REQUEST)+= scsi_sense.o >>> >>> Every place I want

Re: [PATCH 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On 05/23/2018 10:26 AM, Alex G. wrote: > On 05/23/2018 09:20 AM, Jes Sorensen wrote: >> On 05/22/2018 06:28 PM, Rajat Jain wrote: >>> new file mode 100644 >>> index ..b9f251992209 >>> --- /dev/null >>> +++ b/drivers/pci/pcie/aer/aerdrv_stats.c >>> @@ -0,0 +1,64 @@ >>> +//

Re: [PATCH 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On 05/23/2018 10:26 AM, Alex G. wrote: > On 05/23/2018 09:20 AM, Jes Sorensen wrote: >> On 05/22/2018 06:28 PM, Rajat Jain wrote: >>> new file mode 100644 >>> index ..b9f251992209 >>> --- /dev/null >>> +++ b/drivers/pci/pcie/aer/aerdrv_stats.c >>> @@ -0,0 +1,64 @@ >>> +//

Re: [PATCH v5 06/13] KVM: s390: interfaces to manage guest's AP matrix

On 05/18/2018 04:55 AM, Pierre Morel wrote: On 16/05/2018 15:48, Tony Krowiak wrote: On 05/16/2018 09:15 AM, Pierre Morel wrote: On 16/05/2018 15:12, Tony Krowiak wrote: On 05/16/2018 03:48 AM, Pierre Morel wrote: On 15/05/2018 18:07, Tony Krowiak wrote: On 05/15/2018 10:55 AM, Pierre Morel

Re: [PATCH v5 06/13] KVM: s390: interfaces to manage guest's AP matrix

On 05/18/2018 04:55 AM, Pierre Morel wrote: On 16/05/2018 15:48, Tony Krowiak wrote: On 05/16/2018 09:15 AM, Pierre Morel wrote: On 16/05/2018 15:12, Tony Krowiak wrote: On 05/16/2018 03:48 AM, Pierre Morel wrote: On 15/05/2018 18:07, Tony Krowiak wrote: On 05/15/2018 10:55 AM, Pierre Morel

[PATCH v5 1/2] xen/PVH: Set up GS segment for stack canary

We are making calls to C code (e.g. xen_prepare_pvh()) which may use stack canary (stored in GS segment). Signed-off-by: Boris Ostrovsky Reviewed-by: Juergen Gross --- arch/x86/xen/xen-pvh.S | 26 +- 1 file changed, 25

[PATCH v5 1/2] xen/PVH: Set up GS segment for stack canary

We are making calls to C code (e.g. xen_prepare_pvh()) which may use stack canary (stored in GS segment). Signed-off-by: Boris Ostrovsky Reviewed-by: Juergen Gross --- arch/x86/xen/xen-pvh.S | 26 +- 1 file changed, 25 insertions(+), 1 deletion(-) diff --git

[PATCH v5 2/2] xen/PVH: Make GDT selectors PVH-specific

We don't need to share PVH GDT layout with other GDTs, especially since we now have a PVH-speciific entry (for stack canary segment). Define PVH's own selectors. (As a side effect of this change we are also fixing improper reference to __KERNEL_CS) Signed-off-by: Boris Ostrovsky

[PATCH v5 2/2] xen/PVH: Make GDT selectors PVH-specific

We don't need to share PVH GDT layout with other GDTs, especially since we now have a PVH-speciific entry (for stack canary segment). Define PVH's own selectors. (As a side effect of this change we are also fixing improper reference to __KERNEL_CS) Signed-off-by: Boris Ostrovsky Reviewed-by:

[PATCH v5 0/2] PVH GDT fixes

Fix stack canary handling (in the first patch) and re-index PVH GDT to make it explicit that the GDT PVH-specific v5: - Load canary's physical address and clear %edx for 64-bit mode Boris Ostrovsky (2): xen/PVH: Set up GS segment for stack canary xen/PVH: Make GDT selectors PVH-specific

[PATCH v5 0/2] PVH GDT fixes

Fix stack canary handling (in the first patch) and re-index PVH GDT to make it explicit that the GDT PVH-specific v5: - Load canary's physical address and clear %edx for 64-bit mode Boris Ostrovsky (2): xen/PVH: Set up GS segment for stack canary xen/PVH: Make GDT selectors PVH-specific

Re: [PATCH 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On Wed, May 23, 2018 at 10:20:10AM -0400, Jes Sorensen wrote: > > +++ b/drivers/pci/pcie/aer/aerdrv_stats.c > > @@ -0,0 +1,64 @@ > > +// SPDX-License-Identifier: GPL-2.0 > > Fix the formatting please - that gross // gibberish doesn't belong there. Sorry, Jes. The Chief Penguin has Spoken, and

Re: [PATCH 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On Wed, May 23, 2018 at 10:20:10AM -0400, Jes Sorensen wrote: > > +++ b/drivers/pci/pcie/aer/aerdrv_stats.c > > @@ -0,0 +1,64 @@ > > +// SPDX-License-Identifier: GPL-2.0 > > Fix the formatting please - that gross // gibberish doesn't belong there. Sorry, Jes. The Chief Penguin has Spoken, and

Re: [PATCH 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On 05/23/2018 09:20 AM, Jes Sorensen wrote: > On 05/22/2018 06:28 PM, Rajat Jain wrote: >> new file mode 100644 >> index ..b9f251992209 >> --- /dev/null >> +++ b/drivers/pci/pcie/aer/aerdrv_stats.c >> @@ -0,0 +1,64 @@ >> +// SPDX-License-Identifier: GPL-2.0 > > Fix the formatting

Re: [PATCH 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On 05/23/2018 09:20 AM, Jes Sorensen wrote: > On 05/22/2018 06:28 PM, Rajat Jain wrote: >> new file mode 100644 >> index ..b9f251992209 >> --- /dev/null >> +++ b/drivers/pci/pcie/aer/aerdrv_stats.c >> @@ -0,0 +1,64 @@ >> +// SPDX-License-Identifier: GPL-2.0 > > Fix the formatting

Re: [PATCH 3/6] block: Create scsi_sense.h for SCSI and ATAPI

On Wed, May 23, 2018 at 08:13:56AM -0600, Jens Axboe wrote: > > Should I move to code to a new drivers/scsi/scsi_sense.c and add it to > > drivers/scsi/Makefile as: > > > > obj-$(CONFIG_BLK_SCSI_REQUEST)+= scsi_sense.o > > > > Every place I want to use the code is already covered by > >

Re: [PATCH 3/6] block: Create scsi_sense.h for SCSI and ATAPI

On Wed, May 23, 2018 at 08:13:56AM -0600, Jens Axboe wrote: > > Should I move to code to a new drivers/scsi/scsi_sense.c and add it to > > drivers/scsi/Makefile as: > > > > obj-$(CONFIG_BLK_SCSI_REQUEST)+= scsi_sense.o > > > > Every place I want to use the code is already covered by > >

[PATCH 2/2] f2fs: detect synchronous writeback more earlier

From: Chao Yu This patch changes to detect synchronous writeback more earlier before, in order to avoid unnecessary page writeback before exiting asynchronous writeback. Signed-off-by: Chao Yu --- fs/f2fs/data.c | 11 --- 1 file changed, 8

[PATCH 2/2] f2fs: detect synchronous writeback more earlier

From: Chao Yu This patch changes to detect synchronous writeback more earlier before, in order to avoid unnecessary page writeback before exiting asynchronous writeback. Signed-off-by: Chao Yu --- fs/f2fs/data.c | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git

[PATCH 1/2] f2fs: clean up with is_valid_blkaddr()

From: Chao Yu - rename is_valid_blkaddr() to is_valid_meta_blkaddr() for readability. - introduce is_valid_blkaddr() for cleanup. No logic change in this patch. Signed-off-by: Chao Yu --- fs/f2fs/checkpoint.c | 4 ++-- fs/f2fs/data.c | 18

[PATCH 1/2] f2fs: clean up with is_valid_blkaddr()

From: Chao Yu - rename is_valid_blkaddr() to is_valid_meta_blkaddr() for readability. - introduce is_valid_blkaddr() for cleanup. No logic change in this patch. Signed-off-by: Chao Yu --- fs/f2fs/checkpoint.c | 4 ++-- fs/f2fs/data.c | 18 +- fs/f2fs/f2fs.h | 9

Re: [PATCH v2 11/16] irqchip/irq-mvebu-icu: add support for System Error Interrupts (SEI)

On 22/05/18 10:40, Miquel Raynal wrote: > An SEI driver provides an MSI domain through which it is possible to > raise SEIs. > > Handle the NSR probe function in a more generic way to support other > type of interrupts (ie. the SEIs). > > For clarity we do not use tree IRQ domains for now but

Re: [PATCH v2 11/16] irqchip/irq-mvebu-icu: add support for System Error Interrupts (SEI)

On 22/05/18 10:40, Miquel Raynal wrote: > An SEI driver provides an MSI domain through which it is possible to > raise SEIs. > > Handle the NSR probe function in a more generic way to support other > type of interrupts (ie. the SEIs). > > For clarity we do not use tree IRQ domains for now but

Re: [PATCH 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On 05/22/2018 06:28 PM, Rajat Jain wrote: > Define a structure to hold the AER statistics. There are 2 groups > of statistics: dev_* counters that are to be collected for all AER > capable devices and rootport_* counters that are collected for all > (AER capable) rootports only. Allocate and free

Re: [PATCH 1/5] PCI/AER: Define and allocate aer_stats structure for AER capable devices

On 05/22/2018 06:28 PM, Rajat Jain wrote: > Define a structure to hold the AER statistics. There are 2 groups > of statistics: dev_* counters that are to be collected for all AER > capable devices and rootport_* counters that are collected for all > (AER capable) rootports only. Allocate and free

Re: [PATCH v8 10/10] drivers: qcom: rpmh-rsc: allow active requests from wake TCS

Hi, On 5/12/2018 1:47 AM, Doug Anderson wrote: Hi, On Wed, May 9, 2018 at 10:01 AM, Lina Iyer wrote: Some RSCs may only have sleep and wake TCS, i.e, there is no dedicated TCS for active mode request, but drivers may still want to make active requests from these RSCs.

Re: [PATCH v8 10/10] drivers: qcom: rpmh-rsc: allow active requests from wake TCS

Hi, On 5/12/2018 1:47 AM, Doug Anderson wrote: Hi, On Wed, May 9, 2018 at 10:01 AM, Lina Iyer wrote: Some RSCs may only have sleep and wake TCS, i.e, there is no dedicated TCS for active mode request, but drivers may still want to make active requests from these RSCs. In such cases

Re: [RESEND PATCH 2/5] mtd: rawnand: add NVIDIA Tegra NAND Flash controller driver

Hi Stefan, On Tue, 22 May 2018 14:07:06 +0200 Stefan Agner wrote: > + > +struct tegra_nand { > + void __iomem *regs; > + struct clk *clk; > + struct gpio_desc *wp_gpio; > + > + struct nand_chip chip; > + struct device *dev; > + > + struct completion

Re: [RESEND PATCH 2/5] mtd: rawnand: add NVIDIA Tegra NAND Flash controller driver

Hi Stefan, On Tue, 22 May 2018 14:07:06 +0200 Stefan Agner wrote: > + > +struct tegra_nand { > + void __iomem *regs; > + struct clk *clk; > + struct gpio_desc *wp_gpio; > + > + struct nand_chip chip; > + struct device *dev; > + > + struct completion command_complete; > +

Re: [PATCH v2 1/2] dt-bindings: cpufreq: Introduce QCOM CPUFREQ FW bindings

On Wed, May 23, 2018 at 12:48 AM, Viresh Kumar wrote: > On 22-05-18, 14:31, Rob Herring wrote: >> On Sat, May 19, 2018 at 11:04:50PM +0530, Taniya Das wrote: >> > + freq-domain-0 { >> > + compatible = "cpufreq"; >> > + reg =

Re: [PATCH v2 1/2] dt-bindings: cpufreq: Introduce QCOM CPUFREQ FW bindings

On Wed, May 23, 2018 at 12:48 AM, Viresh Kumar wrote: > On 22-05-18, 14:31, Rob Herring wrote: >> On Sat, May 19, 2018 at 11:04:50PM +0530, Taniya Das wrote: >> > + freq-domain-0 { >> > + compatible = "cpufreq"; >> > + reg = <0x17d43920 0x4>, >> > +

<    7   8   9   10   11   12   13   14   15   16   >