Re: [PATCH v4 15/18] x86/intel_rdt: Add tasks files

On Fri, 14 Oct 2016, Fenghua Yu wrote: > +struct task_move_callback { > + struct callback_head work; > + struct rdtgroup *rdtgrp; Please align the struct members as you did everywhere else already. > +}; > + > +static void move_myself(struct callback_head *head) > +{ > + struct

Re: [PATCH] ARM: multi_v7_defconfig: Enable Intel e1000e driver

On Tue, Oct 11, 2016 at 3:38 PM, Scott Branden wrote: > Hi Arnd, > > On 16-10-10 12:47 AM, Arnd Bergmann wrote: >> >> On Saturday, October 8, 2016 1:41:04 PM CEST Scott Branden wrote: >>> >>> Enable support for the Intel e1000e driver >>> >>> Signed-off-by: Ray Jui >>> Signed-off-by: Scott

[PATCH 2/3] f2fs: call f2fs_balance_fs for setattr

If inode becomes dirty, we need to check the # of dirty inodes whether or not further checkpoint would be required. Signed-off-by: Jaegeuk Kim --- fs/f2fs/file.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index

[PATCH 1/3] f2fs: count dirty inodes to flush node pages during checkpoint

If there are a lot of dirty inodes, we need to flush all of them when doing checkpoint. So, we need to count this for enough free space. Signed-off-by: Jaegeuk Kim --- fs/f2fs/segment.h | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git

[PATCH 2/3] f2fs: call f2fs_balance_fs for setattr

If inode becomes dirty, we need to check the # of dirty inodes whether or not further checkpoint would be required. Signed-off-by: Jaegeuk Kim --- fs/f2fs/file.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c index 0907efa..e63d0fd 100644

[PATCH 1/3] f2fs: count dirty inodes to flush node pages during checkpoint

If there are a lot of dirty inodes, we need to flush all of them when doing checkpoint. So, we need to count this for enough free space. Signed-off-by: Jaegeuk Kim --- fs/f2fs/segment.h | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/fs/f2fs/segment.h

Re: [PATCH v2] arm64: defconfig: enable EEPROM_AT25 config option

Hi, On Wed, Oct 12, 2016 at 11:51 AM, Scott Branden wrote: > Enable support for on board SPI EEPROM by turning on > CONFIG_EEPROM_AT25. This needs to be on in order to > boot and test the kernel with a static rootfs image > that is not rebuilt everytime the kernel is

Re: [PATCH v2] arm64: defconfig: enable EEPROM_AT25 config option

Hi, On Wed, Oct 12, 2016 at 11:51 AM, Scott Branden wrote: > Enable support for on board SPI EEPROM by turning on > CONFIG_EEPROM_AT25. This needs to be on in order to > boot and test the kernel with a static rootfs image > that is not rebuilt everytime the kernel is rebuilt. If we did this

Re: hci_ldisc: suspicious/buggy code

On Mon 2016-10-17 23:32:06, Pavel Machek wrote: > Hi! > > hci_uart_set_flow_control() contains some rather suspicious > code. AFAICT: > > set = 0. > > Then we do set &= (magic constant). But as set is 0, it stays zero. It > just does not make sense. [Nor does it make sense to do |= on known >

Re: hci_ldisc: suspicious/buggy code

On Mon 2016-10-17 23:32:06, Pavel Machek wrote: > Hi! > > hci_uart_set_flow_control() contains some rather suspicious > code. AFAICT: > > set = 0. > > Then we do set &= (magic constant). But as set is 0, it stays zero. It > just does not make sense. [Nor does it make sense to do |= on known >

Re: [PATCH v4 13/18] x86/intel_rdt: Add mkdir to resctrl file system

On Mon, Oct 17, 2016 at 11:14:55PM +0200, Thomas Gleixner wrote: > > + /* Compute rdt_max_closid across all resources */ > > + rdt_max_closid = 0; > > + for_each_rdt_resource(r) > > + rdt_max_closid = max(rdt_max_closid, r->num_closid); > > Oh no! This needs to be min(). > >

Re: [PATCH v4 13/18] x86/intel_rdt: Add mkdir to resctrl file system

On Mon, Oct 17, 2016 at 11:14:55PM +0200, Thomas Gleixner wrote: > > + /* Compute rdt_max_closid across all resources */ > > + rdt_max_closid = 0; > > + for_each_rdt_resource(r) > > + rdt_max_closid = max(rdt_max_closid, r->num_closid); > > Oh no! This needs to be min(). > >

[PATCH 2/2] staging: lustre: remove class_devno_max

class_devno_max is an inline function that is not used anymore. Hence, it is removed. Signed-off-by: Aya Mahfouz --- drivers/staging/lustre/lustre/include/obd_class.h | 5 - 1 file changed, 5 deletions(-) diff --git

[PATCH 2/2] staging: lustre: remove class_devno_max

class_devno_max is an inline function that is not used anymore. Hence, it is removed. Signed-off-by: Aya Mahfouz --- drivers/staging/lustre/lustre/include/obd_class.h | 5 - 1 file changed, 5 deletions(-) diff --git a/drivers/staging/lustre/lustre/include/obd_class.h

Re: [PATCH] staging: dgnc: replace DGNC_VERIFY_BOARD macro

On Mon, Oct 17, 2016 at 10:29 AM, Greg KH wrote: > On Fri, Oct 14, 2016 at 07:22:57PM +0200, Fernando Apesteguia wrote: >> The patch replaces the macro with a function (dgnc_get_board) and >> substitutes the macro statement with a call to that function and a >>

Re: [PATCH] staging: dgnc: replace DGNC_VERIFY_BOARD macro

On Mon, Oct 17, 2016 at 10:29 AM, Greg KH wrote: > On Fri, Oct 14, 2016 at 07:22:57PM +0200, Fernando Apesteguia wrote: >> The patch replaces the macro with a function (dgnc_get_board) and >> substitutes the macro statement with a call to that function and a >> comparison on the returned value.

[PATCH 1/2] staging: lustre: replace uses of class_devno_max by MAX_OBD_DEVICES

class_devno_max is an inline function that returns MAX_OBD_DEVICES. Replace all calls to the function by MAX_OBD_DEVICES. Signed-off-by: Aya Mahfouz --- drivers/staging/lustre/lustre/obdclass/class_obd.c | 6 +++---

[PATCH 1/2] staging: lustre: replace uses of class_devno_max by MAX_OBD_DEVICES

class_devno_max is an inline function that returns MAX_OBD_DEVICES. Replace all calls to the function by MAX_OBD_DEVICES. Signed-off-by: Aya Mahfouz --- drivers/staging/lustre/lustre/obdclass/class_obd.c | 6 +++--- drivers/staging/lustre/lustre/obdclass/genops.c| 22 +++---

[PATCH 0/2] staging: lustre: replace and remove class_devno_max

class_devno_max is an inline function that is written with the sole purpose of returning the value of MAX_OBD_DEVICES. Since no computations are made by the class_devno_max, replace it with MAX_OBD_DEVICES. Aya Mahfouz (2): staging: lustre: replace uses of class_devno_max by MAX_OBD_DEVICES

[PATCH 0/2] staging: lustre: replace and remove class_devno_max

class_devno_max is an inline function that is written with the sole purpose of returning the value of MAX_OBD_DEVICES. Since no computations are made by the class_devno_max, replace it with MAX_OBD_DEVICES. Aya Mahfouz (2): staging: lustre: replace uses of class_devno_max by MAX_OBD_DEVICES

Re: [PATCH v9 00/12] Add Mediated device support

On Tue, 18 Oct 2016 02:52:00 +0530 Kirti Wankhede wrote: > This series adds Mediated device support to Linux host kernel. Purpose > of this series is to provide a common interface for mediated device > management that can be used by different devices. This series introduces

Re: [PATCH v9 00/12] Add Mediated device support

On Tue, 18 Oct 2016 02:52:00 +0530 Kirti Wankhede wrote: > This series adds Mediated device support to Linux host kernel. Purpose > of this series is to provide a common interface for mediated device > management that can be used by different devices. This series introduces > Mdev core module

[PATCH] x86/fpu: Finish excising 'eagerfpu'

Now that eagerfpu= is gone, remove it from the docs and some comments. Also sync the changes to tools/. Fixes: ca6938a1cd8a ("x86/fpu: Hard-disable lazy FPU mode") Signed-off-by: Andy Lutomirski Message-Id:

[PATCH] x86/fpu: Finish excising 'eagerfpu'

Now that eagerfpu= is gone, remove it from the docs and some comments. Also sync the changes to tools/. Fixes: ca6938a1cd8a ("x86/fpu: Hard-disable lazy FPU mode") Signed-off-by: Andy Lutomirski Message-Id: <6c6e48fa5b6a51a70bf1ffd149a7125c5fd349be.1475859005.git.l...@kernel.org> ---

Re: drivers/pci/hotplug/ibmphp_ebda.c:409:1: warning: the frame size of 1108 bytes is larger than 1024 bytes

On Sun, 16 Oct 2016 06:52:16 +0800 kbuild test robot wrote: >drivers/pci/hotplug/ibmphp_ebda.c: In function 'ibmphp_access_ebda': > >> drivers/pci/hotplug/ibmphp_ebda.c:409:1: warning: the frame size of 1108 > >> bytes is larger than 1024 bytes [-Wframe-larger-than=]

Re: drivers/pci/hotplug/ibmphp_ebda.c:409:1: warning: the frame size of 1108 bytes is larger than 1024 bytes

On Sun, 16 Oct 2016 06:52:16 +0800 kbuild test robot wrote: >drivers/pci/hotplug/ibmphp_ebda.c: In function 'ibmphp_access_ebda': > >> drivers/pci/hotplug/ibmphp_ebda.c:409:1: warning: the frame size of 1108 > >> bytes is larger than 1024 bytes [-Wframe-larger-than=] Hi, Thanks for the

[PATCH v3 5/5] drm/fsl-dcu: only init fbdev if required

There is no need to request a CMA backed framebuffer if fbdev emulation is not enabled. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c

[PATCH v3 3/5] drm/fsl-dcu: do not transfer registers in mode_set_nofb

Do not schedule a transfer of mode settings early. Modes should get applied on on CRTC enable where we also enable the pixel clock. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 2 -- 1 file changed, 2 deletions(-) diff --git

[PATCH v3 1/5] drm/fsl-dcu: enable TCON bypass mode by default

Do not use encoder disable/enable callbacks to control bypass mode as this seems to mess with the signals not liked by displays. This also makes more sense since the encoder is already defined to be parallel RGB/LVDS at creation time. Signed-off-by: Stefan Agner ---

[PATCH v3 4/5] drm/fsl-dcu: enable pixel clock when enabling CRTC

The pixel clock should not be on if the CRTC is not in use, hence move clock enable/disable calls into CRTC callbacks. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 2 ++ drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 21 + 2

[PATCH v3 5/5] drm/fsl-dcu: only init fbdev if required

There is no need to request a CMA backed framebuffer if fbdev emulation is not enabled. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c

[PATCH v3 3/5] drm/fsl-dcu: do not transfer registers in mode_set_nofb

Do not schedule a transfer of mode settings early. Modes should get applied on on CRTC enable where we also enable the pixel clock. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 2 -- 1 file changed, 2 deletions(-) diff --git

[PATCH v3 1/5] drm/fsl-dcu: enable TCON bypass mode by default

Do not use encoder disable/enable callbacks to control bypass mode as this seems to mess with the signals not liked by displays. This also makes more sense since the encoder is already defined to be parallel RGB/LVDS at creation time. Signed-off-by: Stefan Agner ---

[PATCH v3 4/5] drm/fsl-dcu: enable pixel clock when enabling CRTC

The pixel clock should not be on if the CRTC is not in use, hence move clock enable/disable calls into CRTC callbacks. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 2 ++ drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 21 + 2 files changed, 3

[PATCH v3 2/5] drm/fsl-dcu: do not transfer registers on plane init

There is no need to explicitly initiate a register transfer and turn off the DCU after initializing the plane registers. In fact, this is harmful and leads to unnecessary flickers if the DCU has been left on by the bootloader. Signed-off-by: Stefan Agner ---

[PATCH v3 2/5] drm/fsl-dcu: do not transfer registers on plane init

There is no need to explicitly initiate a register transfer and turn off the DCU after initializing the plane registers. In fact, this is harmful and leads to unnecessary flickers if the DCU has been left on by the bootloader. Signed-off-by: Stefan Agner ---

[PATCH v3 0/5] drm/fsl-dcu: initialization fixes

Hi All, This is an assortment of fixes which solve issues seen using an external RGB converter and makes sure that pixel clock is only on when really required. Meng, could you test that on a LS1021a? -- Stefan Changes since v2: - Don't enable TCON bypass in case TCON is not available Changes

[PATCH v3 0/5] drm/fsl-dcu: initialization fixes

Hi All, This is an assortment of fixes which solve issues seen using an external RGB converter and makes sure that pixel clock is only on when really required. Meng, could you test that on a LS1021a? -- Stefan Changes since v2: - Don't enable TCON bypass in case TCON is not available Changes

Re: [PATCH 11/12] jump_label: declare jump table as external array

On Sun, 16 Oct 2016 18:50:55 +0200 Vegard Nossum wrote: > > > > NAK, -ENOCHANGELOG. Agreed. > > > > Hi Peter, > > It's true I didn't put an RFC tag on this (mostly because git-send-email > doesn't seem to have an option for it?), but the whole point of doing I

Re: [PATCH 11/12] jump_label: declare jump table as external array

On Sun, 16 Oct 2016 18:50:55 +0200 Vegard Nossum wrote: > > > > NAK, -ENOCHANGELOG. Agreed. > > > > Hi Peter, > > It's true I didn't put an RFC tag on this (mostly because git-send-email > doesn't seem to have an option for it?), but the whole point of doing I would think it does, although

hci_ldisc: suspicious/buggy code

Hi! hci_uart_set_flow_control() contains some rather suspicious code. AFAICT: set = 0. Then we do set &= (magic constant). But as set is 0, it stays zero. It just does not make sense. [Nor does it make sense to do |= on known value of zero just after else. But that's probably just some artifact

hci_ldisc: suspicious/buggy code

Hi! hci_uart_set_flow_control() contains some rather suspicious code. AFAICT: set = 0. Then we do set &= (magic constant). But as set is 0, it stays zero. It just does not make sense. [Nor does it make sense to do |= on known value of zero just after else. But that's probably just some artifact

Re: [PATCH v4 14/18] x86/intel_rdt: Add cpus file

On Fri, 14 Oct 2016, Fenghua Yu wrote: > static int intel_rdt_offline_cpu(unsigned int cpu) > { > struct rdt_resource *r; > + struct rdtgroup *rdtgrp; > + struct list_head *l; > > mutex_lock(_mutex); > for_each_rdt_resource(r) > update_domain(cpu, r, 0);

Re: [PATCH v4 14/18] x86/intel_rdt: Add cpus file

On Fri, 14 Oct 2016, Fenghua Yu wrote: > static int intel_rdt_offline_cpu(unsigned int cpu) > { > struct rdt_resource *r; > + struct rdtgroup *rdtgrp; > + struct list_head *l; > > mutex_lock(_mutex); > for_each_rdt_resource(r) > update_domain(cpu, r, 0);

Re: [-next, 1/2] Input: synaptics-rmi4 - add support for F55 sensor tuning

On Fri, Sep 30, 2016 at 08:22:47PM -0700, Guenter Roeck wrote: > Sensor tuning support is needed to determine the number of enabled > tx and rx electrodes for use in F54 functions. > > The number of enabled electrodes is not identical to the total number > of electrodes as reported with

Re: [-next, 1/2] Input: synaptics-rmi4 - add support for F55 sensor tuning

On Fri, Sep 30, 2016 at 08:22:47PM -0700, Guenter Roeck wrote: > Sensor tuning support is needed to determine the number of enabled > tx and rx electrodes for use in F54 functions. > > The number of enabled electrodes is not identical to the total number > of electrodes as reported with

Re: [PATCH] fsl-ifc: set extended addressing for systems whose bootloader doesn't

On Mon, Oct 10, 2016 at 01:56:31PM -0700, David Singleton wrote: > For 32bit systems whose bootloader doesn't set the extended 36-bit > addressing register for flash devices above the 4GB boundary > we can set up in the driver. > > This patch checks the number of address-cells in the dts file >

Re: [PATCH] fsl-ifc: set extended addressing for systems whose bootloader doesn't

On Mon, Oct 10, 2016 at 01:56:31PM -0700, David Singleton wrote: > For 32bit systems whose bootloader doesn't set the extended 36-bit > addressing register for flash devices above the 4GB boundary > we can set up in the driver. > > This patch checks the number of address-cells in the dts file >

Re: [RFC] Vendor events file/dir names

On Mon, Oct 17, 2016 at 04:04:38PM -0300, Arnaldo Carvalho de Melo wrote: > Hi, > > Ingo pointed out to me that in the kernel sources we do not use > file/dir names with uppercase chars (look, for instance, at arch/), so I > mostly scripted a conversion to lowercase and what I got is at: >

Re: [RFC] Vendor events file/dir names

On Mon, Oct 17, 2016 at 04:04:38PM -0300, Arnaldo Carvalho de Melo wrote: > Hi, > > Ingo pointed out to me that in the kernel sources we do not use > file/dir names with uppercase chars (look, for instance, at arch/), so I > mostly scripted a conversion to lowercase and what I got is at: >

[PATCH v9 05/12] vfio: Introduce common function to add capabilities

Vendor driver using mediated device framework should use vfio_info_add_capability() to add capabilities. Introduced this function to reduce code duplication in vendor drivers. Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id:

[PATCH v9 06/12] vfio_pci: Update vfio_pci to use vfio_info_add_capability()

Update msix_sparse_mmap_cap() to use vfio_info_add_capability() Update region type capability to use vfio_info_add_capability() Can't split this commit for MSIx and region_type cap since there is a common code which need to be updated for both the cases. Signed-off-by: Kirti Wankhede

[PATCH v9 05/12] vfio: Introduce common function to add capabilities

Vendor driver using mediated device framework should use vfio_info_add_capability() to add capabilities. Introduced this function to reduce code duplication in vendor drivers. Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id: I6fca329fa2291f37a2c859d0bc97574d9e2ce1a6 ---

[PATCH v9 06/12] vfio_pci: Update vfio_pci to use vfio_info_add_capability()

Update msix_sparse_mmap_cap() to use vfio_info_add_capability() Update region type capability to use vfio_info_add_capability() Can't split this commit for MSIx and region_type cap since there is a common code which need to be updated for both the cases. Signed-off-by: Kirti Wankhede

[PATCH v9 04/12] vfio iommu: Add support for mediated devices

VFIO IOMMU drivers are designed for the devices which are IOMMU capable. Mediated device only uses IOMMU APIs, the underlying hardware can be managed by an IOMMU domain. Aim of this change is: - To use most of the code of TYPE1 IOMMU driver for mediated devices - To support direct assigned device

Re: [PATCH V2] usb: xhci: add support for performing fake doorbell

On 17 October 2016 at 23:10, Hauke Mehrtens wrote: > On 10/17/2016 10:30 PM, Rafał Miłecki wrote: >> From: Rafał Miłecki >> >> Broadcom's Northstar XHCI controllers seem to need a special start >> procedure to work correctly. There isn't any official

[PATCH v9 04/12] vfio iommu: Add support for mediated devices

VFIO IOMMU drivers are designed for the devices which are IOMMU capable. Mediated device only uses IOMMU APIs, the underlying hardware can be managed by an IOMMU domain. Aim of this change is: - To use most of the code of TYPE1 IOMMU driver for mediated devices - To support direct assigned device

Re: [PATCH V2] usb: xhci: add support for performing fake doorbell

On 17 October 2016 at 23:10, Hauke Mehrtens wrote: > On 10/17/2016 10:30 PM, Rafał Miłecki wrote: >> From: Rafał Miłecki >> >> Broadcom's Northstar XHCI controllers seem to need a special start >> procedure to work correctly. There isn't any official documentation of >> this, the problem is that

[PATCH v9 10/12] vfio: Add function to get device_api string from vfio_device_info.flags

Function vfio_device_api_string() returns string based on flag set in vfio_device_info's flag. This should be used by vendor driver to get string based on flag for device_api attribute. Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id:

[PATCH v9 02/12] vfio: VFIO based driver for Mediated devices

vfio_mdev driver registers with mdev core driver. MDEV core driver creates mediated device and calls probe routine of vfio_mdev driver for each device. Probe routine of vfio_mdev driver adds mediated device to VFIO core module This driver forms a shim layer that pass through VFIO devices

[PATCH v9 09/12] vfio_platform: Updated to use vfio_set_irqs_validate_and_prepare()

Updated vfio_platform_common.c file to use vfio_set_irqs_validate_and_prepare() Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id: Id87cd6b78ae901610b39bf957974baa6f40cd7b0 --- drivers/vfio/platform/vfio_platform_common.c | 31

[PATCH v9 12/12] docs: Sample driver to demonstrate how to use Mediated device framework.

The Sample driver creates mdev device that simulates serial port over PCI card. Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id: I857f8f12f8b275f2498dfe8c628a5cdc7193b1b2 --- Documentation/vfio-mdev/Makefile | 13 +

[PATCH v9 01/12] vfio: Mediated device Core driver

Design for Mediated Device Driver: Main purpose of this driver is to provide a common interface for mediated device management that can be used by different drivers of different devices. This module provides a generic interface to create the device, add it to mediated bus, add device to IOMMU

[PATCH v9 02/12] vfio: VFIO based driver for Mediated devices

vfio_mdev driver registers with mdev core driver. MDEV core driver creates mediated device and calls probe routine of vfio_mdev driver for each device. Probe routine of vfio_mdev driver adds mediated device to VFIO core module This driver forms a shim layer that pass through VFIO devices

[PATCH v9 09/12] vfio_platform: Updated to use vfio_set_irqs_validate_and_prepare()

Updated vfio_platform_common.c file to use vfio_set_irqs_validate_and_prepare() Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id: Id87cd6b78ae901610b39bf957974baa6f40cd7b0 --- drivers/vfio/platform/vfio_platform_common.c | 31 +++- 1 file changed, 8

[PATCH v9 12/12] docs: Sample driver to demonstrate how to use Mediated device framework.

The Sample driver creates mdev device that simulates serial port over PCI card. Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id: I857f8f12f8b275f2498dfe8c628a5cdc7193b1b2 --- Documentation/vfio-mdev/Makefile | 13 + Documentation/vfio-mdev/mtty.c

[PATCH v9 01/12] vfio: Mediated device Core driver

Design for Mediated Device Driver: Main purpose of this driver is to provide a common interface for mediated device management that can be used by different drivers of different devices. This module provides a generic interface to create the device, add it to mediated bus, add device to IOMMU

[PATCH v9 10/12] vfio: Add function to get device_api string from vfio_device_info.flags

Function vfio_device_api_string() returns string based on flag set in vfio_device_info's flag. This should be used by vendor driver to get string based on flag for device_api attribute. Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id: I42d29f475f02a7132ce13297fbf2b48f1da10995 ---

[PATCH v9 03/12] vfio: Rearrange functions to get vfio_group from dev

Rearrange functions to have common function to increment container_users. Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id: I1f93262bdbab75094bc24b087b29da35ba70c4c6 --- drivers/vfio/vfio.c | 57

[PATCH v9 08/12] vfio_pci: Updated to use vfio_set_irqs_validate_and_prepare()

Updated vfio_pci.c file to use vfio_set_irqs_validate_and_prepare() Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id: I9f3daba89d8dba5cb5b01a8cff420412f30686c7 --- drivers/vfio/pci/vfio_pci.c | 29 + 1 file

[PATCH v9 11/12] docs: Add Documentation for Mediated devices

Add file Documentation/vfio-mediated-device.txt that include details of mediated device framework. Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id: I137dd646442936090d92008b115908b7b2c7bc5d ---

[PATCH v9 03/12] vfio: Rearrange functions to get vfio_group from dev

Rearrange functions to have common function to increment container_users. Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id: I1f93262bdbab75094bc24b087b29da35ba70c4c6 --- drivers/vfio/vfio.c | 57 ++--- 1 file changed, 37

[PATCH v9 08/12] vfio_pci: Updated to use vfio_set_irqs_validate_and_prepare()

Updated vfio_pci.c file to use vfio_set_irqs_validate_and_prepare() Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id: I9f3daba89d8dba5cb5b01a8cff420412f30686c7 --- drivers/vfio/pci/vfio_pci.c | 29 + 1 file changed, 9 insertions(+), 20 deletions(-)

[PATCH v9 11/12] docs: Add Documentation for Mediated devices

Add file Documentation/vfio-mediated-device.txt that include details of mediated device framework. Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id: I137dd646442936090d92008b115908b7b2c7bc5d --- Documentation/vfio-mdev/vfio-mediated-device.txt | 289 +++ 1

[PATCH v9 07/12] vfio: Introduce vfio_set_irqs_validate_and_prepare()

Vendor driver using mediated device framework would use same mechnism to validate and prepare IRQs. Introducing this function to reduce code replication in multiple drivers. Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id:

[PATCH v9 07/12] vfio: Introduce vfio_set_irqs_validate_and_prepare()

Vendor driver using mediated device framework would use same mechnism to validate and prepare IRQs. Introducing this function to reduce code replication in multiple drivers. Signed-off-by: Kirti Wankhede Signed-off-by: Neo Jia Change-Id: Ie201f269dda0713ca18a07dc4852500bd8b48309 ---

[PATCH v9 00/12] Add Mediated device support

This series adds Mediated device support to Linux host kernel. Purpose of this series is to provide a common interface for mediated device management that can be used by different devices. This series introduces Mdev core module that creates and manages mediated devices, VFIO based driver for

[PATCH v9 00/12] Add Mediated device support

This series adds Mediated device support to Linux host kernel. Purpose of this series is to provide a common interface for mediated device management that can be used by different devices. This series introduces Mdev core module that creates and manages mediated devices, VFIO based driver for

Re: [PATCH v4 13/18] x86/intel_rdt: Add mkdir to resctrl file system

On Fri, 14 Oct 2016, Fenghua Yu wrote: > +/* > + * Trivial allocator for CLOSIDs. Since h/w only supports a small number, > + * we can keep a bitmap of free CLOSIDs in a single integer. > + * > + * Please note: This only supports global CLOSID across multiple > + * resources and multiple sockets.

Re: [PATCH v4 13/18] x86/intel_rdt: Add mkdir to resctrl file system

On Fri, 14 Oct 2016, Fenghua Yu wrote: > +/* > + * Trivial allocator for CLOSIDs. Since h/w only supports a small number, > + * we can keep a bitmap of free CLOSIDs in a single integer. > + * > + * Please note: This only supports global CLOSID across multiple > + * resources and multiple sockets.

Re: [PATCH V4 1/2] ACPI: Add support for ResourceSource/IRQ domain mapping

Just a few nits: Agustin Vega-Frias wrote: +int acpi_irq_domain_register_irq(struct acpi_resource_source *source, u32 hwirq, +int trigger, int polarity) +{ + struct irq_fwspec fwspec; + struct acpi_device *device; + acpi_handle handle; +

Re: [PATCH V4 1/2] ACPI: Add support for ResourceSource/IRQ domain mapping

Just a few nits: Agustin Vega-Frias wrote: +int acpi_irq_domain_register_irq(struct acpi_resource_source *source, u32 hwirq, +int trigger, int polarity) +{ + struct irq_fwspec fwspec; + struct acpi_device *device; + acpi_handle handle; +

Re: [PATCH resend 4.9] hw_random: Don't use a stack buffer in add_early_randomness()

Am Montag, 17. Oktober 2016, 14:03:17 CEST schrieb Andy Lutomirski: Hi Andy, > On Mon, Oct 17, 2016 at 11:36 AM, Stephan Mueller wrote: > > Am Montag, 17. Oktober 2016, 10:30:13 CEST schrieb Andy Lutomirski: > > > > Hi Andy, > > > >> Sure, but shouldn't that be a

Re: [PATCH resend 4.9] hw_random: Don't use a stack buffer in add_early_randomness()

Am Montag, 17. Oktober 2016, 14:03:17 CEST schrieb Andy Lutomirski: Hi Andy, > On Mon, Oct 17, 2016 at 11:36 AM, Stephan Mueller wrote: > > Am Montag, 17. Oktober 2016, 10:30:13 CEST schrieb Andy Lutomirski: > > > > Hi Andy, > > > >> Sure, but shouldn't that be a separate patch covering the

Re: [PATCH v3 0/4] MIPS: Remote processor driver

On 10/11/2016 03:42 PM, Matt Redfearn wrote: > > The MIPS remote processor driver allows non-Linux firmware to take > control of and execute on one of the systems VPEs. The CPU must be > offlined from Linux first. A sysfs interface is created which allows > firmware to be loaded and changed at

Re: [PATCH v3 0/4] MIPS: Remote processor driver

On 10/11/2016 03:42 PM, Matt Redfearn wrote: > > The MIPS remote processor driver allows non-Linux firmware to take > control of and execute on one of the systems VPEs. The CPU must be > offlined from Linux first. A sysfs interface is created which allows > firmware to be loaded and changed at

Re: [PATCH V2] usb: xhci: add support for performing fake doorbell

On 10/17/2016 10:30 PM, Rafał Miłecki wrote: > From: Rafał Miłecki > > Broadcom's Northstar XHCI controllers seem to need a special start > procedure to work correctly. There isn't any official documentation of > this, the problem is that controller doesn't detect any connected

Re: [PATCH V2] usb: xhci: add support for performing fake doorbell

On 10/17/2016 10:30 PM, Rafał Miłecki wrote: > From: Rafał Miłecki > > Broadcom's Northstar XHCI controllers seem to need a special start > procedure to work correctly. There isn't any official documentation of > this, the problem is that controller doesn't detect any connected > devices with

Re: [PATCH v2] iio: light: ltr501: claim direct mode during raw writes

On Sun, 16 Oct 2016, Jonathan Cameron wrote: > On 16/10/16 06:02, Alison Schofield wrote: > > Driver was checking for direct mode but not locking it. Use > > claim/release helper functions to guarantee the device stays > > in direct mode during all raw write operations. > > > > Signed-off-by:

Re: [PATCH v2] iio: light: ltr501: claim direct mode during raw writes

On Sun, 16 Oct 2016, Jonathan Cameron wrote: > On 16/10/16 06:02, Alison Schofield wrote: > > Driver was checking for direct mode but not locking it. Use > > claim/release helper functions to guarantee the device stays > > in direct mode during all raw write operations. > > > > Signed-off-by:

Re: [PATCH] spi: mark device nodes only in case of successful instantiation

> > Thanks for this. This is a very rare case that’s easy to slip through. > > It is good to be consistent :) > > I read this as acked-by for the series? Ah, I mixed up. You acked V2 :) signature.asc Description: PGP signature

Re: [PATCH] spi: mark device nodes only in case of successful instantiation

> > Thanks for this. This is a very rare case that’s easy to slip through. > > It is good to be consistent :) > > I read this as acked-by for the series? Ah, I mixed up. You acked V2 :) signature.asc Description: PGP signature

Re: [PATCH v2] Coccinelle: Add misc/boolconv.cocci

On 10/17/2016 03:54 PM, Julia Lawall wrote: > On Mon, 17 Oct 2016, Andrew F. Davis wrote: > >> Add a script to check for unneeded conversions to bool. > > What changed since the previous version? > Nothing, just a resend, forgot to label it as such. Andrew > julia > > >> >> Signed-off-by:

Re: [PATCH v2] Coccinelle: Add misc/boolconv.cocci

On 10/17/2016 03:54 PM, Julia Lawall wrote: > On Mon, 17 Oct 2016, Andrew F. Davis wrote: > >> Add a script to check for unneeded conversions to bool. > > What changed since the previous version? > Nothing, just a resend, forgot to label it as such. Andrew > julia > > >> >> Signed-off-by:

Re: [PATCH] spi: mark device nodes only in case of successful instantiation

On Mon, Oct 17, 2016 at 10:20:47PM +0300, Pantelis Antoniou wrote: > Hi Ralf, > > > On Oct 16, 2016, at 12:55 , Ralf Ramsauer > > wrote: > > > > Hi Geert, > > > > On 10/16/2016 10:49 AM, Geert Uytterhoeven wrote: > >> Hi Ralf, > >> > >> (Cc i2c) > >> > >> On

Re: [PATCH] spi: mark device nodes only in case of successful instantiation

On Mon, Oct 17, 2016 at 10:20:47PM +0300, Pantelis Antoniou wrote: > Hi Ralf, > > > On Oct 16, 2016, at 12:55 , Ralf Ramsauer > > wrote: > > > > Hi Geert, > > > > On 10/16/2016 10:49 AM, Geert Uytterhoeven wrote: > >> Hi Ralf, > >> > >> (Cc i2c) > >> > >> On Fri, Oct 14, 2016 at 9:31 PM,

[PATCH V4 2/2] irqchip: qcom: Add IRQ combiner driver

Driver for interrupt combiners in the Top-level Control and Status Registers (TCSR) hardware block in Qualcomm Technologies chips. An interrupt combiner in this block combines a set of interrupts by OR'ing the individual interrupt signals into a summary interrupt signal routed to a parent

Re: [PATCH resend 4.9] hw_random: Don't use a stack buffer in add_early_randomness()

On Mon, Oct 17, 2016 at 11:36 AM, Stephan Mueller wrote: > Am Montag, 17. Oktober 2016, 10:30:13 CEST schrieb Andy Lutomirski: > > Hi Andy, >> >> Sure, but shouldn't that be a separate patch covering the whole hw_crypto >> core? > > I think that you are right -- there are

[PATCH V4 2/2] irqchip: qcom: Add IRQ combiner driver

Driver for interrupt combiners in the Top-level Control and Status Registers (TCSR) hardware block in Qualcomm Technologies chips. An interrupt combiner in this block combines a set of interrupts by OR'ing the individual interrupt signals into a summary interrupt signal routed to a parent

Re: [PATCH resend 4.9] hw_random: Don't use a stack buffer in add_early_randomness()

On Mon, Oct 17, 2016 at 11:36 AM, Stephan Mueller wrote: > Am Montag, 17. Oktober 2016, 10:30:13 CEST schrieb Andy Lutomirski: > > Hi Andy, >> >> Sure, but shouldn't that be a separate patch covering the whole hw_crypto >> core? > > I think that you are right -- there are many more cases where a

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