Re: [PATCH] EFI loader: remove dead code

Applied your notice. Sent v2 patch. -- Eugene

Re: [PATCH] EFI loader: remove dead code

Applied your notice. Sent v2 patch. -- Eugene

[PATCH v2 0/6] inherit dma configuration from parent dev

For xhci-hcd platform device, all the DMA parameters are not configured properly, notably dma ops for dwc3 devices. The idea here is that you pass in the parent of_node along with the child device pointer, so it would behave exactly like the parent already does. The difference is that it also

[PATCH v2 0/6] inherit dma configuration from parent dev

For xhci-hcd platform device, all the DMA parameters are not configured properly, notably dma ops for dwc3 devices. The idea here is that you pass in the parent of_node along with the child device pointer, so it would behave exactly like the parent already does. The difference is that it also

[PATCH v2 6/6] usb: dwc3: Do not set dma coherent mask

From: Arnd Bergmann The dma mask is correctly set up by the DT probe function, no need to override it any more. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash --- Changes in v2: - club the cleanup for dma coherent mask for device

[PATCH v2 6/6] usb: dwc3: Do not set dma coherent mask

From: Arnd Bergmann The dma mask is correctly set up by the DT probe function, no need to override it any more. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash --- Changes in v2: - club the cleanup for dma coherent mask for device drivers/usb/dwc3/dwc3-exynos.c | 10 --

[REVISED DOC on v3] Crossrelease Lockdep

Crossrelease Started by Byungchul Park Contents: (*) Background. - What causes deadlock. - What lockdep detects. - How lockdep works. (*) Limitation. - Limit to typical locks. - Pros from the limitation. - Cons from the

[REVISED DOC on v3] Crossrelease Lockdep

Crossrelease Started by Byungchul Park Contents: (*) Background. - What causes deadlock. - What lockdep detects. - How lockdep works. (*) Limitation. - Limit to typical locks. - Pros from the limitation. - Cons from the limitation. (*)

RE: [PATCH v2] ARM: at91/dt: add dts file for sama5d36ek CMP board

> -Original Message- > From: kbuild test robot [mailto:l...@intel.com] > Sent: 2016年11月2日 13:28 > To: Wenyou Yang - A41535 > Cc: kbuild-...@01.org; Nicolas Ferre ; Alexandre > Belloni ; Russell

Re: [PATCH] base memory: introduce CONFIG_MEMORY_DEVICE

On 2016/10/14 18:53, Yisheng Xie wrote: > ping Could someone help to give some comment? Really thanks for that. Thanks. Yisheng > > On 2016/10/10 19:26, Yisheng Xie wrote: >> MEMORY_FAILURE do not depend on SPARSEMEM_MANUAL, >> nor MEMORY_HOTPLUG_SPARSE. However, when I tried to use

RE: [PATCH v2] ARM: at91/dt: add dts file for sama5d36ek CMP board

> -Original Message- > From: kbuild test robot [mailto:l...@intel.com] > Sent: 2016年11月2日 13:28 > To: Wenyou Yang - A41535 > Cc: kbuild-...@01.org; Nicolas Ferre ; Alexandre > Belloni ; Russell King > ; Rob Herring ; Pawel Moll > ; Mark Rutland ; Ian Campbell > ; Kumar Gala ; linux- >

Re: [PATCH] base memory: introduce CONFIG_MEMORY_DEVICE

On 2016/10/14 18:53, Yisheng Xie wrote: > ping Could someone help to give some comment? Really thanks for that. Thanks. Yisheng > > On 2016/10/10 19:26, Yisheng Xie wrote: >> MEMORY_FAILURE do not depend on SPARSEMEM_MANUAL, >> nor MEMORY_HOTPLUG_SPARSE. However, when I tried to use

[PATCH v2 1/6] usb: separate out sysdev pointer from usb_bus

From: Arnd Bergmann For xhci-hcd platform device, all the DMA parameters are not configured properly, notably dma ops for dwc3 devices. The idea here is that you pass in the parent of_node along with the child device pointer, so it would behave exactly like the parent already

[PATCH v2 1/6] usb: separate out sysdev pointer from usb_bus

From: Arnd Bergmann For xhci-hcd platform device, all the DMA parameters are not configured properly, notably dma ops for dwc3 devices. The idea here is that you pass in the parent of_node along with the child device pointer, so it would behave exactly like the parent already does. The

[PATCH v2 5/6] usb: dwc3: use bus->sysdev for DMA configuration

From: Arnd Bergmann The dma ops for dwc3 devices are not set properly. So, use a physical device sysdev, which will be inherited from parent, to set the hardware / firmware parameters like dma. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash

[PATCH v2 3/6] usb: ehci: fsl: use bus->sysdev for DMA configuration

From: Arnd Bergmann For the dual role ehci fsl driver, sysdev will handle the dma config. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash --- Changes in v2: - fix compile warnings drivers/usb/host/ehci-fsl.c | 4 ++-- 1 file

[PATCH v2 5/6] usb: dwc3: use bus->sysdev for DMA configuration

From: Arnd Bergmann The dma ops for dwc3 devices are not set properly. So, use a physical device sysdev, which will be inherited from parent, to set the hardware / firmware parameters like dma. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash --- Changes in v2: - integrate dwc3

[PATCH v2 3/6] usb: ehci: fsl: use bus->sysdev for DMA configuration

From: Arnd Bergmann For the dual role ehci fsl driver, sysdev will handle the dma config. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash --- Changes in v2: - fix compile warnings drivers/usb/host/ehci-fsl.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH v2 2/6] usb: chipidea: use bus->sysdev for DMA configuration

From: Arnd Bergmann Set the dma for chipidea from sysdev. This is inherited from its parent node. Also, do not set dma mask for child as it is not required now. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash --- Changes in v2: -

[PATCH v2 2/6] usb: chipidea: use bus->sysdev for DMA configuration

From: Arnd Bergmann Set the dma for chipidea from sysdev. This is inherited from its parent node. Also, do not set dma mask for child as it is not required now. Signed-off-by: Arnd Bergmann Signed-off-by: Sriram Dash --- Changes in v2: - integrate chipidea driver changes together.

Re: [PATCH 1/4] block: add scalable completion tracking of requests

On Tue, Nov 01 2016, Johannes Thumshirn wrote: > On Tue, Nov 01, 2016 at 03:05:22PM -0600, Jens Axboe wrote: > > For legacy block, we simply track them in the request queue. For > > blk-mq, we track them on a per-sw queue basis, which we can then > > sum up through the hardware queues and finally

Re: [PATCH 1/4] block: add scalable completion tracking of requests

On Tue, Nov 01 2016, Johannes Thumshirn wrote: > On Tue, Nov 01, 2016 at 03:05:22PM -0600, Jens Axboe wrote: > > For legacy block, we simply track them in the request queue. For > > blk-mq, we track them on a per-sw queue basis, which we can then > > sum up through the hardware queues and finally

[PATCH v1] ARM:dmaengine:sun6i:fix the uninitialized value for v_lli

dma_pool_alloc does not initialize the value of the newly allocated block for the v_lli, and the uninitilize value make the tests failed which is on pine64 with dmatest. we can fix it just change the "|=" to "=" for the v_lli->cfg. Signed-off-by: Hao Zhang ---

[PATCH v1] ARM:dmaengine:sun6i:fix the uninitialized value for v_lli

dma_pool_alloc does not initialize the value of the newly allocated block for the v_lli, and the uninitilize value make the tests failed which is on pine64 with dmatest. we can fix it just change the "|=" to "=" for the v_lli->cfg. Signed-off-by: Hao Zhang --- drivers/dma/sun6i-dma.c | 2 +- 1

Re: [PATCH v2] ARM: at91/dt: add dts file for sama5d36ek CMP board

Hi Wenyou, [auto build test ERROR on at91/at91-next] [also build test ERROR on v4.9-rc3 next-20161028] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH v2] ARM: at91/dt: add dts file for sama5d36ek CMP board

Hi Wenyou, [auto build test ERROR on at91/at91-next] [also build test ERROR on v4.9-rc3 next-20161028] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH v7 08/11] x86, kvm/x86.c: support vcpu preempted check

Support the vcpu_is_preempted() functionality under KVM. This will enhance lock performance on overcommitted hosts (more runnable vcpus than physical cpus in the system) as doing busy waits for preempted vcpus will hurt system performance far worse than early yielding. Use one field of struct

[PATCH v7 10/11] x86, xen: support vcpu preempted check

From: Juergen Gross Support the vcpu_is_preempted() functionality under Xen. This will enhance lock performance on overcommitted hosts (more runnable vcpus than physical cpus in the system) as doing busy waits for preempted vcpus will hurt system performance far worse than early

[PATCH v7 11/11] Documentation: virtual: kvm: Support vcpu preempted check

Commit ("x86, kvm: support vcpu preempted check") add one field "__u8 preempted" into struct kvm_steal_time. This field tells if one vcpu is running or not. It is zero if 1) some old KVM deos not support this filed. 2) the vcpu is not preempted. Other values means the vcpu has been preempted.

[PATCH v7 10/11] x86, xen: support vcpu preempted check

From: Juergen Gross Support the vcpu_is_preempted() functionality under Xen. This will enhance lock performance on overcommitted hosts (more runnable vcpus than physical cpus in the system) as doing busy waits for preempted vcpus will hurt system performance far worse than early yielding. A

[PATCH v7 11/11] Documentation: virtual: kvm: Support vcpu preempted check

Commit ("x86, kvm: support vcpu preempted check") add one field "__u8 preempted" into struct kvm_steal_time. This field tells if one vcpu is running or not. It is zero if 1) some old KVM deos not support this filed. 2) the vcpu is not preempted. Other values means the vcpu has been preempted.

[PATCH v7 08/11] x86, kvm/x86.c: support vcpu preempted check

Support the vcpu_is_preempted() functionality under KVM. This will enhance lock performance on overcommitted hosts (more runnable vcpus than physical cpus in the system) as doing busy waits for preempted vcpus will hurt system performance far worse than early yielding. Use one field of struct

Re: [PATCH V4] pinctrl: qcom: Add msm8994 pinctrl driver

On 11/01/2016 04:53 PM, Stephen Boyd wrote: On 10/31, Michael Scott wrote: + +static const struct msm_pingroup msm8994_groups[] = { + PINGROUP(0, blsp_spi1, blsp_uart1, blsp_uim1, NA, NA, NA, NA, NA, NA, +NA, NA), I see an hdmi_rcv group here after blsp_uim1. Please

[PATCH v7 09/11] x86, kernel/kvm.c: support vcpu preempted check

Support the vcpu_is_preempted() functionality under KVM. This will enhance lock performance on overcommitted hosts (more runnable vcpus than physical cpus in the system) as doing busy waits for preempted vcpus will hurt system performance far worse than early yielding. struct

[PATCH v7 06/11] x86, paravirt: Add interface to support kvm/xen vcpu preempted check

This is to fix some lock holder preemption issues. Some other locks implementation do a spin loop before acquiring the lock itself. Currently kernel has an interface of bool vcpu_is_preempted(int cpu). It takes the cpu as parameter and return true if the cpu is preempted. Then kernel can break the

[PATCH v7 09/11] x86, kernel/kvm.c: support vcpu preempted check

Support the vcpu_is_preempted() functionality under KVM. This will enhance lock performance on overcommitted hosts (more runnable vcpus than physical cpus in the system) as doing busy waits for preempted vcpus will hurt system performance far worse than early yielding. struct

[PATCH v7 06/11] x86, paravirt: Add interface to support kvm/xen vcpu preempted check

This is to fix some lock holder preemption issues. Some other locks implementation do a spin loop before acquiring the lock itself. Currently kernel has an interface of bool vcpu_is_preempted(int cpu). It takes the cpu as parameter and return true if the cpu is preempted. Then kernel can break the

Re: [PATCH V4] pinctrl: qcom: Add msm8994 pinctrl driver

On 11/01/2016 04:53 PM, Stephen Boyd wrote: On 10/31, Michael Scott wrote: + +static const struct msm_pingroup msm8994_groups[] = { + PINGROUP(0, blsp_spi1, blsp_uart1, blsp_uim1, NA, NA, NA, NA, NA, NA, +NA, NA), I see an hdmi_rcv group here after blsp_uim1. Please

[PATCH v7 02/11] locking/osq: Drop the overload of osq_lock()

An over-committed guest with more vCPUs than pCPUs has a heavy overload in osq_lock(). This is because vCPU A hold the osq lock and yield out, vCPU B wait per_cpu node->locked to be set. IOW, vCPU B wait vCPU A to run and unlock the osq lock. Kernel has an interface bool vcpu_is_preempted(int

[PATCH v7 01/11] kernel/sched: introduce vcpu preempted check interface

This patch support to fix lock holder preemption issue. For kernel users, we could use bool vcpu_is_preempted(int cpu) to detect if one vcpu is preempted or not. The default implementation is a macro defined by false. So compiler can wrap it out if arch dose not support such vcpu preempted

[PATCH v7 04/11] powerpc/spinlock: support vcpu preempted check

This is to fix some lock holder preemption issues. Some other locks implementation do a spin loop before acquiring the lock itself. Currently kernel has an interface of bool vcpu_is_preempted(int cpu). It takes the cpu as parameter and return true if the cpu is preempted. Then kernel can break the

[PATCH v7 01/11] kernel/sched: introduce vcpu preempted check interface

This patch support to fix lock holder preemption issue. For kernel users, we could use bool vcpu_is_preempted(int cpu) to detect if one vcpu is preempted or not. The default implementation is a macro defined by false. So compiler can wrap it out if arch dose not support such vcpu preempted

[PATCH v7 04/11] powerpc/spinlock: support vcpu preempted check

This is to fix some lock holder preemption issues. Some other locks implementation do a spin loop before acquiring the lock itself. Currently kernel has an interface of bool vcpu_is_preempted(int cpu). It takes the cpu as parameter and return true if the cpu is preempted. Then kernel can break the

[PATCH v7 02/11] locking/osq: Drop the overload of osq_lock()

An over-committed guest with more vCPUs than pCPUs has a heavy overload in osq_lock(). This is because vCPU A hold the osq lock and yield out, vCPU B wait per_cpu node->locked to be set. IOW, vCPU B wait vCPU A to run and unlock the osq lock. Kernel has an interface bool vcpu_is_preempted(int

[PATCH v7 03/11] kernel/locking: Drop the overload of {mutex,rwsem}_spin_on_owner

An over-committed guest with more vCPUs than pCPUs has a heavy overload in the two spin_on_owner. This blames on the lock holder preemption issue. Kernel has an interface bool vcpu_is_preempted(int cpu) to see if a vCPU is currently running or not. So break the spin loops on true condition.

[PATCH v7 07/11] KVM: Introduce kvm_write_guest_offset_cached

It allows us to update some status or field of one struct partially. We can also save one kvm_read_guest_cached if we just update one filed of the struct regardless of its current value. Signed-off-by: Pan Xinhui Acked-by: Paolo Bonzini ---

[PATCH v7 05/11] s390/spinlock: Provide vcpu_is_preempted

From: Christian Borntraeger this implements the s390 backend for commit "kernel/sched: introduce vcpu preempted check interface" by reworking the existing smp_vcpu_scheduled into arch_vcpu_is_preempted. We can then also get rid of the local cpu_is_preempted function by

[PATCH v7 07/11] KVM: Introduce kvm_write_guest_offset_cached

It allows us to update some status or field of one struct partially. We can also save one kvm_read_guest_cached if we just update one filed of the struct regardless of its current value. Signed-off-by: Pan Xinhui Acked-by: Paolo Bonzini --- include/linux/kvm_host.h | 2 ++

[PATCH v7 05/11] s390/spinlock: Provide vcpu_is_preempted

From: Christian Borntraeger this implements the s390 backend for commit "kernel/sched: introduce vcpu preempted check interface" by reworking the existing smp_vcpu_scheduled into arch_vcpu_is_preempted. We can then also get rid of the local cpu_is_preempted function by moving the

[PATCH v7 03/11] kernel/locking: Drop the overload of {mutex,rwsem}_spin_on_owner

An over-committed guest with more vCPUs than pCPUs has a heavy overload in the two spin_on_owner. This blames on the lock holder preemption issue. Kernel has an interface bool vcpu_is_preempted(int cpu) to see if a vCPU is currently running or not. So break the spin loops on true condition.

[PATCH v7 00/11] implement vcpu preempted check

change from v6: fix typos and remove uncessary comments. change from v5: spilt x86/kvm patch into guest/host part. introduce kvm_write_guest_offset_cached. fix some typos. rebase patch onto 4.9.2 change from v4: spilt x86 kvm vcpu preempted check

[PATCH v7 00/11] implement vcpu preempted check

change from v6: fix typos and remove uncessary comments. change from v5: spilt x86/kvm patch into guest/host part. introduce kvm_write_guest_offset_cached. fix some typos. rebase patch onto 4.9.2 change from v4: spilt x86 kvm vcpu preempted check

Re: [PATCH v2 2/2] PM / sleep: don't suspend parent when async child suspend_{noirq,late} fails

+ more genpd folks On Wed, Nov 02, 2016 at 04:51:08AM +0100, Rafael J. Wysocki wrote: > On Tuesday, November 01, 2016 12:04:28 AM Dmitry Torokhov wrote: > > On Mon, Oct 31, 2016 at 10:25 PM, Rafael J. Wysocki > > wrote: > > > On Thursday, October 27, 2016 09:05:34 AM Brian

Re: [PATCH v2 2/2] PM / sleep: don't suspend parent when async child suspend_{noirq,late} fails

+ more genpd folks On Wed, Nov 02, 2016 at 04:51:08AM +0100, Rafael J. Wysocki wrote: > On Tuesday, November 01, 2016 12:04:28 AM Dmitry Torokhov wrote: > > On Mon, Oct 31, 2016 at 10:25 PM, Rafael J. Wysocki > > wrote: > > > On Thursday, October 27, 2016 09:05:34 AM Brian Norris wrote: > > >>

Re: [PATCH] drm/nouveau/tegra: Fix error handling

On Mon, Oct 31, 2016 at 3:35 PM, Christophe JAILLET wrote: > 'iommu_domain_alloc()' returns NULL in case of error, not an error pointer. > So test it accordingly. > > Signed-off-by: Christophe JAILLET Reviewed-by: Alexandre Courbot

Re: [PATCH] drm/nouveau/tegra: Fix error handling

On Mon, Oct 31, 2016 at 3:35 PM, Christophe JAILLET wrote: > 'iommu_domain_alloc()' returns NULL in case of error, not an error pointer. > So test it accordingly. > > Signed-off-by: Christophe JAILLET Reviewed-by: Alexandre Courbot Indeed. Thanks for the fix!

Re: [PATCH V3 0/9] PM / OPP: Multiple regulator support

On 26-10-16, 12:02, Viresh Kumar wrote: > Hi, > > Some platforms (like TI) have complex DVFS configuration for CPU > devices, where multiple regulators are required to be configured to > change DVFS state of the device. This was explained well by Nishanth > earlier [1]. > > One of the major

Re: [PATCH V3 0/9] PM / OPP: Multiple regulator support

On 26-10-16, 12:02, Viresh Kumar wrote: > Hi, > > Some platforms (like TI) have complex DVFS configuration for CPU > devices, where multiple regulators are required to be configured to > change DVFS state of the device. This was explained well by Nishanth > earlier [1]. > > One of the major

Re: [PATCH v3 0/4] PXA cpufreq conversion to clock API

On 31-10-16, 20:54, Robert Jarzmik wrote: > Hi, > > This serie is a preparation to shift the cpufreq of pxa2xx platforms to clocks > API, next iteration. > > The first 3 patches are review and merge material : > - patch 1/4 for Viresh and Rafael > - patches 2/4 and 3/4 for me > > The 4th on

Re: [PATCH v3 0/4] PXA cpufreq conversion to clock API

On 31-10-16, 20:54, Robert Jarzmik wrote: > Hi, > > This serie is a preparation to shift the cpufreq of pxa2xx platforms to clocks > API, next iteration. > > The first 3 patches are review and merge material : > - patch 1/4 for Viresh and Rafael > - patches 2/4 and 3/4 for me > > The 4th on

Re: [PATCH v2 5/7] [media] ir-lirc-codec: don't wait any transmitting time for tx only devices

Hi Sean, > > > Andi, it would be good to know what the use-case for the original change > > > is. > > > > the use case is the ir-spi itself which doesn't need the lirc to > > perform any waiting on its behalf. > > Here is the crux of the problem: in the ir-spi case no wait will actually >

Re: [PATCH v2 5/7] [media] ir-lirc-codec: don't wait any transmitting time for tx only devices

Hi Sean, > > > Andi, it would be good to know what the use-case for the original change > > > is. > > > > the use case is the ir-spi itself which doesn't need the lirc to > > perform any waiting on its behalf. > > Here is the crux of the problem: in the ir-spi case no wait will actually >

[PATCH v2] EFI loader: remove redundant code

*e820ext is always NULL in 'alloc_e820ext()' (see the code of 'exit_boot()'). Without loss of generality we can replace freeing with returning EFI_INVALID_PARAMETER. So if the caller would ever incorrectly pass non-NULL *e820ext, he will obtain a returned error code. ---

[PATCH v2] EFI loader: remove redundant code

*e820ext is always NULL in 'alloc_e820ext()' (see the code of 'exit_boot()'). Without loss of generality we can replace freeing with returning EFI_INVALID_PARAMETER. So if the caller would ever incorrectly pass non-NULL *e820ext, he will obtain a returned error code. ---

Re: [Qemu-devel] [PATCH v9 04/12] vfio iommu: Add support for mediated devices

On 02/11/16 14:29, Kirti Wankhede wrote: > > > On 11/2/2016 6:54 AM, Alexey Kardashevskiy wrote: >> On 02/11/16 01:01, Kirti Wankhede wrote: >>> >>> >>> On 10/28/2016 7:48 AM, Alexey Kardashevskiy wrote: On 27/10/16 23:31, Kirti Wankhede wrote: > > > On 10/27/2016 12:50 PM,

Re: [Qemu-devel] [PATCH v9 04/12] vfio iommu: Add support for mediated devices

On 02/11/16 14:29, Kirti Wankhede wrote: > > > On 11/2/2016 6:54 AM, Alexey Kardashevskiy wrote: >> On 02/11/16 01:01, Kirti Wankhede wrote: >>> >>> >>> On 10/28/2016 7:48 AM, Alexey Kardashevskiy wrote: On 27/10/16 23:31, Kirti Wankhede wrote: > > > On 10/27/2016 12:50 PM,

Re: tmpfs returns incorrect data on concurrent pread() and truncate()

On Tue, Nov 01, 2016 at 06:38:26PM -0700, Hugh Dickins wrote: > On Wed, 2 Nov 2016, Dave Chinner wrote: > > On Tue, Nov 01, 2016 at 04:51:30PM -0700, Hugh Dickins wrote: > > > On Wed, 26 Oct 2016, Jakob Unterwurzacher wrote: > > > > > > > tmpfs seems to be incorrectly returning 0-bytes when

Re: tmpfs returns incorrect data on concurrent pread() and truncate()

On Tue, Nov 01, 2016 at 06:38:26PM -0700, Hugh Dickins wrote: > On Wed, 2 Nov 2016, Dave Chinner wrote: > > On Tue, Nov 01, 2016 at 04:51:30PM -0700, Hugh Dickins wrote: > > > On Wed, 26 Oct 2016, Jakob Unterwurzacher wrote: > > > > > > > tmpfs seems to be incorrectly returning 0-bytes when

Re: [RFC PATCH 0/6] UART slave devices using serio

On Mon, Oct 31, 2016 at 10:40 PM, Rob Herring wrote: > On Mon, Oct 31, 2016 at 3:00 PM, Peter Hurley > wrote: >> On Tue, Oct 25, 2016 at 4:02 PM, Rob Herring wrote: >>> >>> > Maybe you can try to find some minutes at the Kernel Summit

Re: [RFC PATCH 0/6] UART slave devices using serio

On Mon, Oct 31, 2016 at 10:40 PM, Rob Herring wrote: > On Mon, Oct 31, 2016 at 3:00 PM, Peter Hurley > wrote: >> On Tue, Oct 25, 2016 at 4:02 PM, Rob Herring wrote: >>> >>> > Maybe you can try to find some minutes at the Kernel Summit to talk >>> > about this? >>> >>> Still waiting for my

Re: [PATCH v2 2/2] PM / sleep: don't suspend parent when async child suspend_{noirq,late} fails

On Tuesday, November 01, 2016 12:04:28 AM Dmitry Torokhov wrote: > On Mon, Oct 31, 2016 at 10:25 PM, Rafael J. Wysocki > wrote: > > On Thursday, October 27, 2016 09:05:34 AM Brian Norris wrote: > >> Consider two devices, A and B, where B is a child of A, and B utilizes > >>

Re: [PATCH v2 2/2] PM / sleep: don't suspend parent when async child suspend_{noirq,late} fails

On Tuesday, November 01, 2016 12:04:28 AM Dmitry Torokhov wrote: > On Mon, Oct 31, 2016 at 10:25 PM, Rafael J. Wysocki > wrote: > > On Thursday, October 27, 2016 09:05:34 AM Brian Norris wrote: > >> Consider two devices, A and B, where B is a child of A, and B utilizes > >> asynchronous suspend

Re: [Qemu-devel] [PATCH v9 04/12] vfio iommu: Add support for mediated devices

On 11/2/2016 6:54 AM, Alexey Kardashevskiy wrote: > On 02/11/16 01:01, Kirti Wankhede wrote: >> >> >> On 10/28/2016 7:48 AM, Alexey Kardashevskiy wrote: >>> On 27/10/16 23:31, Kirti Wankhede wrote: On 10/27/2016 12:50 PM, Alexey Kardashevskiy wrote: > On 18/10/16 08:22, Kirti

Re: [Qemu-devel] [PATCH v9 04/12] vfio iommu: Add support for mediated devices

On 11/2/2016 6:54 AM, Alexey Kardashevskiy wrote: > On 02/11/16 01:01, Kirti Wankhede wrote: >> >> >> On 10/28/2016 7:48 AM, Alexey Kardashevskiy wrote: >>> On 27/10/16 23:31, Kirti Wankhede wrote: On 10/27/2016 12:50 PM, Alexey Kardashevskiy wrote: > On 18/10/16 08:22, Kirti

Re: Kernel regression introduced by "e1000e: Do not write lsc to ics in msi-x mode" and/or "e1000e: Do not read ICR in Other interrupt"

On 2016/11/01 19:56, Jack Suter wrote: > Hi there, > > I have some servers with an 82574L based NIC and recently upgraded from > a 4.4 series kernel to 4.7. Upon doing so, servers with this chipset > have begun frequently reporting "Link is Down" and "Link is Up" > messages. No other related

Re: Kernel regression introduced by "e1000e: Do not write lsc to ics in msi-x mode" and/or "e1000e: Do not read ICR in Other interrupt"

On 2016/11/01 19:56, Jack Suter wrote: > Hi there, > > I have some servers with an 82574L based NIC and recently upgraded from > a 4.4 series kernel to 4.7. Upon doing so, servers with this chipset > have begun frequently reporting "Link is Down" and "Link is Up" > messages. No other related

Re: [PATCH 1/1] mm/hugetlb: fix huge page reservation leak in private mapping error paths

On Wednesday, November 02, 2016 12:37 AM Mike Kravetz wrote: > On 10/19/2016 08:11 PM, Mike Kravetz wrote: > > Error paths in hugetlb_cow() and hugetlb_no_page() may free a newly > > allocated huge page. If a reservation was associated with the huge > > page, alloc_huge_page() consumed the

Re: [PATCH 1/1] mm/hugetlb: fix huge page reservation leak in private mapping error paths

On Wednesday, November 02, 2016 12:37 AM Mike Kravetz wrote: > On 10/19/2016 08:11 PM, Mike Kravetz wrote: > > Error paths in hugetlb_cow() and hugetlb_no_page() may free a newly > > allocated huge page. If a reservation was associated with the huge > > page, alloc_huge_page() consumed the

Re: [PATCH 09/60] dm: dm.c: replace 'bio->bi_vcnt == 1' with !bio_multiple_segments

On Mon, Oct 31, 2016 at 08:29:01AM -0700, Christoph Hellwig wrote: > On Sat, Oct 29, 2016 at 04:08:08PM +0800, Ming Lei wrote: > > Avoid to access .bi_vcnt directly, because it may be not what > > the driver expected any more after supporting multipage bvec. > > > > Signed-off-by: Ming Lei

Re: [PATCH 09/60] dm: dm.c: replace 'bio->bi_vcnt == 1' with !bio_multiple_segments

On Mon, Oct 31, 2016 at 08:29:01AM -0700, Christoph Hellwig wrote: > On Sat, Oct 29, 2016 at 04:08:08PM +0800, Ming Lei wrote: > > Avoid to access .bi_vcnt directly, because it may be not what > > the driver expected any more after supporting multipage bvec. > > > > Signed-off-by: Ming Lei > >

Re: [PATCH 28/60] block: introduce QUEUE_FLAG_SPLIT_MP

On Mon, Oct 31, 2016 at 08:39:15AM -0700, Christoph Hellwig wrote: > On Sat, Oct 29, 2016 at 04:08:27PM +0800, Ming Lei wrote: > > Some drivers(such as dm) should be capable of dealing with multipage > > bvec, but the incoming bio may be too big, such as, a new singlepage bvec > > bio can't be

Re: [PATCH 28/60] block: introduce QUEUE_FLAG_SPLIT_MP

On Mon, Oct 31, 2016 at 08:39:15AM -0700, Christoph Hellwig wrote: > On Sat, Oct 29, 2016 at 04:08:27PM +0800, Ming Lei wrote: > > Some drivers(such as dm) should be capable of dealing with multipage > > bvec, but the incoming bio may be too big, such as, a new singlepage bvec > > bio can't be

[PATCH v2] ARM: at91/dt: add dts file for sama5d36ek CMP board

The sama5d36ek CMP board is the variant of sama5d3xek board. It is equipped with the low-power DDR2 SDRAM, PMIC ACT8865 and some power rail. Its main purpose is used to measure the power consumption. The difference of the sama5d36ek CMP dts from sama5d36ek dts is listed as below. 1. The USB host

[PATCH v2] ARM: at91/dt: add dts file for sama5d36ek CMP board

The sama5d36ek CMP board is the variant of sama5d3xek board. It is equipped with the low-power DDR2 SDRAM, PMIC ACT8865 and some power rail. Its main purpose is used to measure the power consumption. The difference of the sama5d36ek CMP dts from sama5d36ek dts is listed as below. 1. The USB host

Re: [PATCH 45/60] block: bio: introduce bio_for_each_segment_all_rd() and its write pair

On Mon, Oct 31, 2016 at 08:11:23AM -0700, Christoph Hellwig wrote: > On Mon, Oct 31, 2016 at 09:59:43AM -0400, Theodore Ts'o wrote: > > What is _rd and _wt supposed to stand for? > > I think it's read and write, but I think the naming is highly > unfortunate. I started dabbling around with the

Re: [PATCH 45/60] block: bio: introduce bio_for_each_segment_all_rd() and its write pair

On Mon, Oct 31, 2016 at 08:11:23AM -0700, Christoph Hellwig wrote: > On Mon, Oct 31, 2016 at 09:59:43AM -0400, Theodore Ts'o wrote: > > What is _rd and _wt supposed to stand for? > > I think it's read and write, but I think the naming is highly > unfortunate. I started dabbling around with the

[PATCH] staging: vt6655: card.c: Fixing multiple assignments

Running checkpath on card.c shows two locations where multiple assignments are used. This patch modifies the assignments into single assignments. Signed-off-by: Nick Rosbrook --- drivers/staging/vt6655/card.c | 7 +-- 1 file changed, 5 insertions(+), 2

[PATCH] staging: vt6655: card.c: Fixing multiple assignments

Running checkpath on card.c shows two locations where multiple assignments are used. This patch modifies the assignments into single assignments. Signed-off-by: Nick Rosbrook --- drivers/staging/vt6655/card.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git

Re: [PATCH] drm/exynos: gsc: fix spelling mistakes

Hello Colin, On 11/01/2016 11:23 PM, Colin King wrote: > From: Colin Ian King > > Trivial fixes to spelling mistakes "precalser" to "prescaler" > in dev_err messages > > Signed-off-by: Colin Ian King > --- Reviewed-by: Javier Martinez

Re: [PATCH] drm/exynos: gsc: fix spelling mistakes

Hello Colin, On 11/01/2016 11:23 PM, Colin King wrote: > From: Colin Ian King > > Trivial fixes to spelling mistakes "precalser" to "prescaler" > in dev_err messages > > Signed-off-by: Colin Ian King > --- Reviewed-by: Javier Martinez Canillas Best regards, -- Javier Martinez Canillas

Re: [RFC v3 2/6] Improve the tracking of active utilisation

On Mon, 24 Oct 2016 16:06:34 +0200 Luca Abeni wrote: [...] > @@ -514,7 +556,20 @@ static void update_dl_entity(struct sched_dl_entity > *dl_se, > struct dl_rq *dl_rq = dl_rq_of_se(dl_se); > struct rq *rq = rq_of_dl_rq(dl_rq); > > - add_running_bw(dl_se,

Re: [RFC v3 2/6] Improve the tracking of active utilisation

On Mon, 24 Oct 2016 16:06:34 +0200 Luca Abeni wrote: [...] > @@ -514,7 +556,20 @@ static void update_dl_entity(struct sched_dl_entity > *dl_se, > struct dl_rq *dl_rq = dl_rq_of_se(dl_se); > struct rq *rq = rq_of_dl_rq(dl_rq); > > - add_running_bw(dl_se, dl_rq); > + if

[PATCH v1] iio: adc: at91: add suspend and resume callback

Add suspend/resume callback, support the pinctrl sleep state when the system suspend as well. Signed-off-by: Wenyou Yang --- drivers/iio/adc/at91_adc.c | 35 +++ 1 file changed, 35 insertions(+) diff --git a/drivers/iio/adc/at91_adc.c

[PATCH v1] iio: adc: at91: add suspend and resume callback

Add suspend/resume callback, support the pinctrl sleep state when the system suspend as well. Signed-off-by: Wenyou Yang --- drivers/iio/adc/at91_adc.c | 35 +++ 1 file changed, 35 insertions(+) diff --git a/drivers/iio/adc/at91_adc.c

Re: [RFC v3 2/6] Improve the tracking of active utilisation

On Tue, 1 Nov 2016 22:46:33 +0100 luca abeni wrote: [...] > > > @@ -1074,6 +1161,14 @@ select_task_rq_dl(struct task_struct *p, int cpu, > > > int sd_flag, int flags) > > > } > > > rcu_read_unlock(); > > > > > > + rq = task_rq(p); > > > + raw_spin_lock(>lock); > > > +

Re: [RFC v3 2/6] Improve the tracking of active utilisation

On Tue, 1 Nov 2016 22:46:33 +0100 luca abeni wrote: [...] > > > @@ -1074,6 +1161,14 @@ select_task_rq_dl(struct task_struct *p, int cpu, > > > int sd_flag, int flags) > > > } > > > rcu_read_unlock(); > > > > > > + rq = task_rq(p); > > > + raw_spin_lock(>lock); > > > + if

[PATCH 1/1] usb: xhci: remove the use of xhci->addr_dev

xhci->addr_dev is used for the completion of both address device and enable slot commands. It's shared by enumerations of all USB devices connected to an xhci host. Hence, it's just a source for possible races. Since we've introduced command structure and the command queue to xhci driver. It is

[PATCH 1/1] usb: xhci: remove the use of xhci->addr_dev

xhci->addr_dev is used for the completion of both address device and enable slot commands. It's shared by enumerations of all USB devices connected to an xhci host. Hence, it's just a source for possible races. Since we've introduced command structure and the command queue to xhci driver. It is

[PATCH RFC 2/4] [media] subdev-formats.rst: we need a pdf picture for bayer

The png picture is not ok on Sphinx 1.4.8. Signed-off-by: Mauro Carvalho Chehab --- Documentation/media/uapi/v4l/subdev-formats.rst | 4 +--- .../media/uapi/v4l/subdev-formats_files/bayer.pdf | Bin 0 -> 11131 bytes 2 files changed, 1 insertion(+), 3

[PATCH RFC 2/4] [media] subdev-formats.rst: we need a pdf picture for bayer

The png picture is not ok on Sphinx 1.4.8. Signed-off-by: Mauro Carvalho Chehab --- Documentation/media/uapi/v4l/subdev-formats.rst | 4 +--- .../media/uapi/v4l/subdev-formats_files/bayer.pdf | Bin 0 -> 11131 bytes 2 files changed, 1 insertion(+), 3 deletions(-) create mode

  1   2   3   4   5   6   7   8   9   10   >