Re: [PATCH v2] staging: android: ion: Zero CMA allocated memory

2018-01-24 Thread Liam Mark
On Wed, 24 Jan 2018, Laura Abbott wrote: > On 01/22/2018 09:46 AM, Liam Mark wrote: > > Since commit 204f672255c2 ("staging: android: ion: Use CMA APIs directly") > > the CMA API is now used directly and therefore the allocated memory is no > > longer automatically zeroed. > > > > Explicitly zero

Re: [PATCH] staging: imx-media-vdic: fix inconsistent IS_ERR and PTR_ERR

2018-01-24 Thread Steve Longerbeam
Acked-by: Steve Longerbeam On 01/23/2018 04:43 PM, Gustavo A. R. Silva wrote: Fix inconsistent IS_ERR and PTR_ERR in vdic_get_ipu_resources. The proper pointer to be passed as argument is ch. This issue was detected with the help of Coccinelle. Fixes: 0b2e9e7947e7 ("media: staging/imx: remov

Re: [PATCH v3 6/6] uio_hv_generic: support sub-channels

2018-01-24 Thread Stephen Hemminger
On Wed, 10 Jan 2018 17:42:56 +0100 Greg KH wrote: > On Tue, Jan 09, 2018 at 12:57:33PM -0800, Stephen Hemminger wrote: > > Use sysfs to allow supporting sub-channels. The userspace application > > makes request to host to create sub-channels and the UIO kernel > > driver populates the sysfs per-c

[PATCH 1/1] scsi: storvsc: Increase cmd_per_lun for higher speed devices

2018-01-24 Thread Michael Kelley (EOSG)
Increase cmd_per_lun to allow more I/Os in progress per device, particularly for NVMe's. The Hyper-V host side can handle the higher count with no issues. Signed-off-by: Michael Kelley --- drivers/scsi/storvsc_drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/scs

RE: [PATCH 1/1] scsi: storvsc: Spread interrupts when picking a channel for I/O requests

2018-01-24 Thread Michael Kelley (EOSG)
Updated/corrected two email addresses ... > -Original Message- > From: Michael Kelley (EOSG) > Sent: Wednesday, January 24, 2018 2:14 PM > To: KY Srinivasan ; Stephen Hemminger > ; > martin.peter...@oracle.com; lo...@microsoft.com; jbottom...@odin.com; > de...@linuxdriverproject.org; linu

[PATCH 1/1] scsi: storvsc: Spread interrupts when picking a channel for I/O requests

2018-01-24 Thread Michael Kelley (EOSG)
Update the algorithm in storvsc_do_io to look for a channel starting with the current CPU + 1 and wrap around (within the current NUMA node). This spreads VMbus interrupts more evenly across CPUs. Previous code always started with first CPU in the current NUMA node, skewing the interrupt load to th

[PATCH] staging: ccree: Fix missing blank line after declaration

2018-01-24 Thread Kamal Heib
Fix the following warning found by checkpatch.pl WARNING: Missing a blank line after declarations + struct cc_cipher_handle *blkcipher_handle = drvdata->blkcipher_handle; + if (blkcipher_handle) { Signed-off-by: Kamal Heib --- drivers/staging/ccree/cc_cipher.c | 1 + 1 file changed,

Re: [PATCH] Staging: iio: ade7758: Expand buf_lock to cover both buffer

2018-01-24 Thread kbuild test robot
/linux/commits/Shreeya-Patel/Staging-iio-ade7758-Expand-buf_lock-to-cover-both-buffer/20180124-234049 base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg reproduce: # apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__

[RFC PATCH] Staging: iio: ade7758: __ade7758_spi_write_reg_8() can be static

2018-01-24 Thread kbuild test robot
Fixes: c1960999e575 ("Staging: iio: ade7758: Expand buf_lock to cover both buffer") Signed-off-by: Fengguang Wu --- ade7758_core.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/staging/iio/meter/ade7758_core.c b/drivers/staging/iio/meter/ade7758_core.c inde

possible deadlock in shmem_file_llseek

2018-01-24 Thread syzbot
Hello, syzbot tried to test the proposed patch but build/boot failed: patch is already applied Tested on https://github.com/joelagnel/linux.git/test-ashmem commit 32f813bb0d06c1e189ac336f8c3c7377f85c71f0 (Wed Jan 24 01:45:04 2018 +) ashmem: Fix lockdep issue during llseek compiler: gcc (G

Re: [Patch] vmbus: Simply hv_get_next_write_location() function

2018-01-24 Thread Stephen Hemminger
On Wed, 24 Jan 2018 14:21:30 +0800 lantianyu1...@gmail.com wrote: > From: Tianyu Lan > > The "next" variable is redundant in hv_get_next_write_location(). > This patch is to remove it and return write_index directly. > > Signed-off-by: Tianyu Lan > --- > drivers/hv/ring_buffer.c | 4 +--- > 1

Re: [PATCH v4 5/7] x86/irq: Count Hyper-V reenlightenment interrupts

2018-01-24 Thread Radim Krčmář
2018-01-24 14:23+0100, Vitaly Kuznetsov: > Hyper-V reenlightenment interrupts arrive when the VM is migrated, we're > not supposed to see many of them. However, it may be important to know > that the event has happened in case we have L2 nested guests. > > Signed-off-by: Vitaly Kuznetsov > Review

Re: [PATCH v3] staging: lustre: separate a connection destroy from free struct kib_conn

2018-01-24 Thread Greg Kroah-Hartman
On Wed, Jan 24, 2018 at 05:14:12PM +0300, Dmitry Eremin wrote: > Rewrite the logic of the original commit 4d99b2581eff ("staging: lustre: avoid > intensive reconnecting for ko2iblnd") and move the freeing a struct kib_conn > outside of the function kiblnd_destroy_conn(). The freeing of struct kib_c

[PATCH v3] staging: lustre: separate a connection destroy from free struct kib_conn

2018-01-24 Thread Dmitry Eremin
Rewrite the logic of the original commit 4d99b2581eff ("staging: lustre: avoid intensive reconnecting for ko2iblnd") and move the freeing a struct kib_conn outside of the function kiblnd_destroy_conn(). The freeing of struct kib_conn should be depending on the second argument free_conn of function

[PATCH v4 4/7] x86/hyper-v: redirect reenlightment notifications on CPU offlining

2018-01-24 Thread Vitaly Kuznetsov
It is very unlikely for CPUs to get offlined when we run on Hyper-V as we have a protection in vmbus module which prevents it when we have any VMBus devices assigned. This, however, may change in future if an option to reassign an already active channel will be added. It is also possible to run wi

[PATCH v4 7/7] x86/kvm: support Hyper-V reenlightenment

2018-01-24 Thread Vitaly Kuznetsov
When we run nested KVM on Hyper-V guests we need to update masterclocks for all guests when L1 migrates to a host with different TSC frequency. Implement the procedure in the following way: - Pause all guests. - Tell our host (Hyper-V) to stop emulating TSC accesses. - Update our gtod copy, recompu

[PATCH v4 6/7] x86/kvm: pass stable clocksource to guests when running nested on Hyper-V

2018-01-24 Thread Vitaly Kuznetsov
Currently, KVM is able to work in 'masterclock' mode passing PVCLOCK_TSC_STABLE_BIT to guests when the clocksource we use on the host is TSC. When running nested on Hyper-V we normally use a different one: TSC page which is resistant to TSC frequency changes on event like L1 migration. Add support

[PATCH v4 2/7] x86/hyper-v: add a function to read both TSC and TSC page value simulateneously

2018-01-24 Thread Vitaly Kuznetsov
This is going to be used from KVM code where we need to get both TSC and TSC page value. Nobody is supposed to use the function when Hyper-V code is compiled out, just BUG(). Signed-off-by: Vitaly Kuznetsov --- arch/x86/hyperv/hv_init.c | 1 + arch/x86/include/asm/mshyperv.h | 23 +++

[PATCH v4 3/7] x86/hyper-v: reenlightenment notifications support

2018-01-24 Thread Vitaly Kuznetsov
Hyper-V supports Live Migration notification. This is supposed to be used in conjunction with TSC emulation: when we are migrated to a host with different TSC frequency for some short period host emulates our accesses to TSC and sends us an interrupt to notify about the event. When we're done updat

[PATCH v4 5/7] x86/irq: Count Hyper-V reenlightenment interrupts

2018-01-24 Thread Vitaly Kuznetsov
Hyper-V reenlightenment interrupts arrive when the VM is migrated, we're not supposed to see many of them. However, it may be important to know that the event has happened in case we have L2 nested guests. Signed-off-by: Vitaly Kuznetsov Reviewed-by: Thomas Gleixner --- arch/x86/hyperv/hv_init.

[PATCH v4 0/7] x86/kvm/hyperv: stable clocksource for L2 guests when running nested KVM on Hyper-V

2018-01-24 Thread Vitaly Kuznetsov
Changes since v3: - PATCH3: - drop 'include ' (and __visible/_irq_entry from hyperv_reenlightenment_intr declaration -- but not from implementation) from mshyperv.h [kbuild robot] I'm retaining Thomas' Reviewed-by tag as the change is small, hope that's OK. - PATCH7: - add static to

[PATCH v4 1/7] x86/hyper-v: check for required priviliges in hyperv_init()

2018-01-24 Thread Vitaly Kuznetsov
In hyperv_init() we presume we always have access to VP index and hypercall MSRs while according to the specification we should check if we're allowed to access the corresponding MSRs before accessing them. Signed-off-by: Vitaly Kuznetsov Reviewed-by: Thomas Gleixner --- arch/x86/hyperv/hv_init

[PATCH v2] staging: lustre: Fix avoid intensive reconnecting for ko2iblnd patch

2018-01-24 Thread Dmitry Eremin
From: Dmitry Eremin The logic of the original commit 4d99b2581eff ("staging: lustre: avoid intensive reconnecting for ko2iblnd") was assumed conditional free of struct kib_conn if the second argument free_conn in function kiblnd_destroy_conn(struct kib_conn *conn, bool free_conn) is true. But th

[PATCH] x86/hyper-v: stop suppressing X86_FEATURE_PCID

2018-01-24 Thread Vitaly Kuznetsov
When hypercall-based TLB flush was enabled for Hyper-V guests PCID feature was deliberately suppressed as a precaution: back then PCID was never exposed to Hyper-V guests and it wasn't clear what will happen if some day it becomes available. The day came and PCID/INVPCID features are already expose

Re: [PATCH v2] staging: android: ion: Zero CMA allocated memory

2018-01-24 Thread Laura Abbott
On 01/22/2018 09:46 AM, Liam Mark wrote: Since commit 204f672255c2 ("staging: android: ion: Use CMA APIs directly") the CMA API is now used directly and therefore the allocated memory is no longer automatically zeroed. Explicitly zero CMA allocated memory to ensure that no data is exposed to use

Re: [PATCH] staging: media: remove unused VIDEO_ATOMISP_OV8858 kconfig

2018-01-24 Thread Dan Carpenter
On Tue, Jan 23, 2018 at 07:31:27PM +0200, Andy Shevchenko wrote: > On Tue, Jan 23, 2018 at 4:37 PM, Corentin Labbe wrote: > > Nothing in kernel use VIDEO_ATOMISP_OV8858 since commit 3a81c7660f80 > > ("media: staging: atomisp: Remove IMX sensor support") > > Lets remove this kconfig option. > > F