[PATCH v2] x86/microcode/intel: Blacklist the specific BDW-EP for late loading

Instead of blacklisting all Broadwell processorsi for running a late loading, only BDW-EP (signature 406f1) with the microcode version less than 0x0b21 needs to be blacklisted. This is documented in the the public documentation #334165 (See the item BDF90 for details). Signed-off-by: Jia

[PATCH v2] x86/microcode/intel: Blacklist the specific BDW-EP for late loading

Instead of blacklisting all Broadwell processorsi for running a late loading, only BDW-EP (signature 406f1) with the microcode version less than 0x0b21 needs to be blacklisted. This is documented in the the public documentation #334165 (See the item BDF90 for details). Signed-off-by: Jia

Re: [PATCH] x86/microcode/intel: Blacklist the specific BDW-EP for late loading

Sorry I should remove UTF-8 characters in comment lines. Plz ignore this patch. Cheers, Jia 在 2017/12/25 下午3:30, Jia Zhang 写道: > Instead of blacklisting all Broadwell processorsi for running a late > loading, only BDW-EP (signature 406f1) with the microcode version > less than 0x0b21 needs

Re: [PATCH] x86/microcode/intel: Blacklist the specific BDW-EP for late loading

Sorry I should remove UTF-8 characters in comment lines. Plz ignore this patch. Cheers, Jia 在 2017/12/25 下午3:30, Jia Zhang 写道: > Instead of blacklisting all Broadwell processorsi for running a late > loading, only BDW-EP (signature 406f1) with the microcode version > less than 0x0b21 needs

[BUG ? ] Each pci bridge only supports hotplugging 16 numbers of virtio-blk/virtio-net devices

Hi, We tried to hot add more than 16 numbers of virtio-blk devices to pci bridge, but found that only 16 of them are available in VM. There are ‘no space’ error messages in dmesg: [4.666106] pci :00:03.0: PCI bridge to [bus 01] [4.666191] pci :00:03.0: bridge window [io

[BUG ? ] Each pci bridge only supports hotplugging 16 numbers of virtio-blk/virtio-net devices

Hi, We tried to hot add more than 16 numbers of virtio-blk devices to pci bridge, but found that only 16 of them are available in VM. There are ‘no space’ error messages in dmesg: [4.666106] pci :00:03.0: PCI bridge to [bus 01] [4.666191] pci :00:03.0: bridge window [io

[PATCH] x86/microcode/intel: Blacklist the specific BDW-EP for late loading

Instead of blacklisting all Broadwell processorsi for running a late loading, only BDW-EP (signature 406f1) with the microcode version less than 0x0b21 needs to be blacklisted. This is documented in the the public documentation #334165 (See the item BDF90 for details). Signed-off-by: Jia

[PATCH] x86/microcode/intel: Blacklist the specific BDW-EP for late loading

Instead of blacklisting all Broadwell processorsi for running a late loading, only BDW-EP (signature 406f1) with the microcode version less than 0x0b21 needs to be blacklisted. This is documented in the the public documentation #334165 (See the item BDF90 for details). Signed-off-by: Jia

Re: [PATCH] KVM: x86: ioapic: Clear IRR for rtc bit when rtc EOI gotten

2017-12-14 20:23 GMT+08:00 Gonglei : > We hit a bug in our test while run PCMark 10 in a windows 7 VM, > The VM got stuck and the wallclock was hang after several minutes running > PCMark 10 in it. > It is quite easily to reproduce the bug with the upstream KVM and Qemu. >

Re: [PATCH] KVM: x86: ioapic: Clear IRR for rtc bit when rtc EOI gotten

2017-12-14 20:23 GMT+08:00 Gonglei : > We hit a bug in our test while run PCMark 10 in a windows 7 VM, > The VM got stuck and the wallclock was hang after several minutes running > PCMark 10 in it. > It is quite easily to reproduce the bug with the upstream KVM and Qemu. > > We found that KVM can

Re: Php-fpm will crash when perf runs with call graph option

Have you tried updating your kernel to a recent version? On 2017/12/25 14:58, ufo19890607 wrote: From: yuzhoujian I use perf to analyze the performance overhead for the server. There are several dockers in the server. The php-fpm in the docker will crash as long

Re: Php-fpm will crash when perf runs with call graph option

Have you tried updating your kernel to a recent version? On 2017/12/25 14:58, ufo19890607 wrote: From: yuzhoujian I use perf to analyze the performance overhead for the server. There are several dockers in the server. The php-fpm in the docker will crash as long as the perf collects samples

Re: [PATCH v5 00/11] FUSE mounts from non-init user namespaces

Dongsu Park writes: > This patchset v5 is based on work by Seth Forshee and Eric Biederman. > The latest patchset was v4: > https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1132206.html > > At the moment, filesystems backed by physical medium can only be mounted >

Re: [PATCH v5 00/11] FUSE mounts from non-init user namespaces

Dongsu Park writes: > This patchset v5 is based on work by Seth Forshee and Eric Biederman. > The latest patchset was v4: > https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1132206.html > > At the moment, filesystems backed by physical medium can only be mounted > by real root in the

Php-fpm will crash when perf runs with call graph option

From: yuzhoujian I use perf to analyze the performance overhead for the server. There are several dockers in the server. The php-fpm in the docker will crash as long as the perf collects samples for all the cpus with call graph option(perf record -ag). Below is the

Php-fpm will crash when perf runs with call graph option

From: yuzhoujian I use perf to analyze the performance overhead for the server. There are several dockers in the server. The php-fpm in the docker will crash as long as the perf collects samples for all the cpus with call graph option(perf record -ag). Below is the stack trace in the coredump.

Php-fpm will crash when perf runs with call graph option

From: yuzhoujian #0 0x7f044ff447bd in re_compile_fastmap_iter (bufp=0x7f044ff447bd , fastmap=0x46 , init_state=, init_state=) at regcomp.c:407 407 if (__wcrtomb (buf, towlower

Php-fpm will crash when perf runs with call graph option

From: yuzhoujian #0 0x7f044ff447bd in re_compile_fastmap_iter (bufp=0x7f044ff447bd , fastmap=0x46 , init_state=, init_state=) at regcomp.c:407 407 if (__wcrtomb (buf, towlower (cset->mbchars[i]), ) (gdb) bt #0

RE: [PATCH] vfio: mdev: make a couple of functions and structure vfio_mdev_driver static

> Sent: Friday, December 22, 2017 7:12 AM > To: kwankh...@nvidia.com; alex.william...@redhat.com > Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: [PATCH] vfio: mdev: make a couple of functions and structure > vfio_mdev_driver static > > The functions vfio_mdev_probe,

RE: [PATCH] vfio: mdev: make a couple of functions and structure vfio_mdev_driver static

> Sent: Friday, December 22, 2017 7:12 AM > To: kwankh...@nvidia.com; alex.william...@redhat.com > Cc: k...@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: [PATCH] vfio: mdev: make a couple of functions and structure > vfio_mdev_driver static > > The functions vfio_mdev_probe,

[PATCH v7 1/2] regmap: Add one flag to indicate if a hwlock should be used

Since the hwlock id 0 is valid for hardware spinlock core, but now id 0 is treated as one invalid value for regmap. Thus we should add one extra flag for regmap config to indicate if a hardware spinlock should be used, then id 0 can be valid for regmap to request. Signed-off-by: Baolin Wang

[PATCH v7 1/2] regmap: Add one flag to indicate if a hwlock should be used

Since the hwlock id 0 is valid for hardware spinlock core, but now id 0 is treated as one invalid value for regmap. Thus we should add one extra flag for regmap config to indicate if a hardware spinlock should be used, then id 0 can be valid for regmap to request. Signed-off-by: Baolin Wang ---

[PATCH v7 2/2] mfd: syscon: Add hardware spinlock support

Some system control registers need hardware spinlock to synchronize between the multiple subsystems, so we should add hardware spinlock support for syscon. Signed-off-by: Baolin Wang Acked-by: Rob Herring --- Changes since v6: - Treat hwlock id 0 as

[PATCH v7 2/2] mfd: syscon: Add hardware spinlock support

Some system control registers need hardware spinlock to synchronize between the multiple subsystems, so we should add hardware spinlock support for syscon. Signed-off-by: Baolin Wang Acked-by: Rob Herring --- Changes since v6: - Treat hwlock id 0 as valid for regmap. Changes since v5: - Fix

Re: [PATCH] f2fs: avoid f2fs_gc dead loop

What if the application starts atomic write but forgets to commit, e.g. bugs in application or the application is a malicious software itself? On 2017/12/25 11:44, Chao Yu wrote: On 2017/12/23 21:09, Yunlong Song wrote: For some corner case, f2fs_gc selects one target victim but cannot free

Re: [PATCH] f2fs: avoid f2fs_gc dead loop

What if the application starts atomic write but forgets to commit, e.g. bugs in application or the application is a malicious software itself? On 2017/12/25 11:44, Chao Yu wrote: On 2017/12/23 21:09, Yunlong Song wrote: For some corner case, f2fs_gc selects one target victim but cannot free

Re: [PATCH] f2fs: return error during fill_super

On 2017/12/21 4:39, Jaegeuk Kim wrote: > Let's avoid BUG_ON during fill_super, when on-disk was totall corrupted. > > Signed-off-by: Jaegeuk Kim Reviewed-by: Chao Yu Thanks,

Re: [PATCH] f2fs: return error during fill_super

On 2017/12/21 4:39, Jaegeuk Kim wrote: > Let's avoid BUG_ON during fill_super, when on-disk was totall corrupted. > > Signed-off-by: Jaegeuk Kim Reviewed-by: Chao Yu Thanks,

Re: [PATCH] vfio: mdev: make a couple of functions and structure vfio_mdev_driver static

On 2017/12/22 07:12, Xiongwei Song wrote: The functions vfio_mdev_probe, vfio_mdev_remove and the structure vfio_mdev_driver are only used in this file, so make them static. Clean up sparse warnings: drivers/vfio/mdev/vfio_mdev.c:114:5: warning: no previous prototype for 'vfio_mdev_probe'

Re: [PATCH] vfio: mdev: make a couple of functions and structure vfio_mdev_driver static

On 2017/12/22 07:12, Xiongwei Song wrote: The functions vfio_mdev_probe, vfio_mdev_remove and the structure vfio_mdev_driver are only used in this file, so make them static. Clean up sparse warnings: drivers/vfio/mdev/vfio_mdev.c:114:5: warning: no previous prototype for 'vfio_mdev_probe'

[PATCH] Staging: vt6656: Fix unnecessary parantheses

This patch fixes a few coding style issues as noted by checkpatch.pl related to unnecessary parantheses. This patch fixes the following checkpatch.pl warnings: WARNING: Unnecessary parentheses around 'priv->eeprom[EEP_OFS_MAJOR_VER] == 0x1' WARNING: Unnecessary parentheses around

[PATCH] Staging: vt6656: Fix unnecessary parantheses

This patch fixes a few coding style issues as noted by checkpatch.pl related to unnecessary parantheses. This patch fixes the following checkpatch.pl warnings: WARNING: Unnecessary parentheses around 'priv->eeprom[EEP_OFS_MAJOR_VER] == 0x1' WARNING: Unnecessary parentheses around

[PATCH] Staging: vt6656: Fix unnecessary 'out of memory' message

This patch fixes one of the warnings as noted by checkpatch.pl related to unnecessary 'out of memory' message. This patch fixes the following checkpatch.pl error: WARNING: Possible unnecessary 'out of memory' message Signed-off-by: Sumit Pundir ---

[PATCH] Staging: vt6656: Fix unnecessary 'out of memory' message

This patch fixes one of the warnings as noted by checkpatch.pl related to unnecessary 'out of memory' message. This patch fixes the following checkpatch.pl error: WARNING: Possible unnecessary 'out of memory' message Signed-off-by: Sumit Pundir --- drivers/staging/vt6656/main_usb.c | 5 +

For Your Urgent Attention, Sir/Madam,

-- For Your Urgent Attention, Sir/Madam, Having reviewed all the obstacles and problems surrounding the transfer of your Funds and your inability to meet up with some charges levied against you due to the past transfer options, We the Board of Directors, United Bank For Africa (UBA Bank) had

For Your Urgent Attention, Sir/Madam,

-- For Your Urgent Attention, Sir/Madam, Having reviewed all the obstacles and problems surrounding the transfer of your Funds and your inability to meet up with some charges levied against you due to the past transfer options, We the Board of Directors, United Bank For Africa (UBA Bank) had

Re: [PATCH] perf report: Fix a no annotate browser displayed issue

Hi, Any comments for this bug fix? Thanks Jin Yao On 12/18/2017 9:26 PM, Jin Yao wrote: When enabling '-b' option in perf record, for example, perf record -b ... perf report and then browsing the annotate browser from perf report, it would be failed (annotate browser can't be displayed).

Re: [PATCH] perf report: Fix a no annotate browser displayed issue

Hi, Any comments for this bug fix? Thanks Jin Yao On 12/18/2017 9:26 PM, Jin Yao wrote: When enabling '-b' option in perf record, for example, perf record -b ... perf report and then browsing the annotate browser from perf report, it would be failed (annotate browser can't be displayed).

Re: [PATCH] f2fs: avoid f2fs_gc dead loop

On 2017/12/23 21:09, Yunlong Song wrote: > For some corner case, f2fs_gc selects one target victim but cannot free > that victim segment due to some reason (e.g. the segment has some blocks > of atomic file which is not commited yet), in this case, the victim File should not be atomic opened for

Re: [PATCH] f2fs: avoid f2fs_gc dead loop

On 2017/12/23 21:09, Yunlong Song wrote: > For some corner case, f2fs_gc selects one target victim but cannot free > that victim segment due to some reason (e.g. the segment has some blocks > of atomic file which is not commited yet), in this case, the victim File should not be atomic opened for

[PATCH] usb: dwc3: gadget: decrease the queued_requests in removal

In removal requests, it is necessary to make the corresponding trb disable state (HWO = 1) and dep->queued_requests a corresponding reduction. It is better to use a alone funtion to disable trb (HWO = 0). Signed-off-by: Pengcheng Li --- drivers/usb/dwc3/gadget.c | 30

[PATCH] usb: dwc3: gadget: decrease the queued_requests in removal

In removal requests, it is necessary to make the corresponding trb disable state (HWO = 1) and dep->queued_requests a corresponding reduction. It is better to use a alone funtion to disable trb (HWO = 0). Signed-off-by: Pengcheng Li --- drivers/usb/dwc3/gadget.c | 30

[PATCH v2 07/12] drm/qxl: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/qxl/qxl_ttm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/qxl/qxl_ttm.c

[PATCH v2 08/12] drm/radeon: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/radeon/radeon_ttm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/radeon/radeon_ttm.c

[PATCH v2 07/12] drm/qxl: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/qxl/qxl_ttm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/qxl/qxl_ttm.c b/drivers/gpu/drm/qxl/qxl_ttm.c index

[PATCH v2 08/12] drm/radeon: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/radeon/radeon_ttm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/radeon/radeon_ttm.c

[PATCH v2 01/12] drm/ttm: add ttm_bo_io_mem_pfn to check io_mem_pfn

The io_mem_pfn field was added in commit ea642c3216cb ("drm/ttm: add io_mem_pfn callback") and is called unconditionally. However, not all drivers were updated to set it. Use the ttm_bo_default_io_mem_pfn function if a driver did not set its own. And add new function ttm_bo_io_mem_pfn() as

[PATCH v2 01/12] drm/ttm: add ttm_bo_io_mem_pfn to check io_mem_pfn

The io_mem_pfn field was added in commit ea642c3216cb ("drm/ttm: add io_mem_pfn callback") and is called unconditionally. However, not all drivers were updated to set it. Use the ttm_bo_default_io_mem_pfn function if a driver did not set its own. And add new function ttm_bo_io_mem_pfn() as

[PATCH v2 09/12] drm/virtio: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/virtio/virtgpu_ttm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_ttm.c

[PATCH v2 09/12] drm/virtio: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/virtio/virtgpu_ttm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_ttm.c

[PATCH v2 12/12] drm/ttm: remove ttm_bo_default_io_mem_pfn

No one will use this function except ttm_bo_io_mem_pfn() now, so move the calculation of ttm_bo_default_io_mem_pfn() into ttm_bo_io_mem_pfn() and do some cleanup. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/ttm/ttm_bo_vm.c | 11 ++- include/drm/ttm/ttm_bo_api.h

[PATCH v2 11/12] staging: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/staging/vboxvideo/vbox_ttm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/vboxvideo/vbox_ttm.c

[PATCH v2 12/12] drm/ttm: remove ttm_bo_default_io_mem_pfn

No one will use this function except ttm_bo_io_mem_pfn() now, so move the calculation of ttm_bo_default_io_mem_pfn() into ttm_bo_io_mem_pfn() and do some cleanup. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/ttm/ttm_bo_vm.c | 11 ++- include/drm/ttm/ttm_bo_api.h| 11 --- 2

[PATCH v2 11/12] staging: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/staging/vboxvideo/vbox_ttm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/staging/vboxvideo/vbox_ttm.c

[PATCH v2 00/12] drm: add check if io_mem_pfn is NULL and cleanup

I found an OOPS when I used the mainline kernel for graphical tests in Hisilicon D05, I do not know how to solve this problem until I saw your discussion on this issue a month ago: https://lists.freedesktop.org/archives/dri-devel/2017-November/159046.html And my problem can be solved perfectly

[PATCH v2 00/12] drm: add check if io_mem_pfn is NULL and cleanup

I found an OOPS when I used the mainline kernel for graphical tests in Hisilicon D05, I do not know how to solve this problem until I saw your discussion on this issue a month ago: https://lists.freedesktop.org/archives/dri-devel/2017-November/159046.html And my problem can be solved perfectly

[PATCH v2 04/12] drm/cirrus: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/cirrus/cirrus_ttm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/cirrus/cirrus_ttm.c

[PATCH v2 04/12] drm/cirrus: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/cirrus/cirrus_ttm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/cirrus/cirrus_ttm.c

[PATCH v2 05/12] drm/mgag200: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/mgag200/mgag200_ttm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/mgag200/mgag200_ttm.c

[PATCH v2 05/12] drm/mgag200: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/mgag200/mgag200_ttm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/mgag200/mgag200_ttm.c

[PATCH v2 03/12] drm/bochs: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/bochs/bochs_mm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/bochs/bochs_mm.c

[PATCH v2 06/12] drm/nouveau: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/nouveau/nouveau_bo.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_bo.c

[PATCH v2 03/12] drm/bochs: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/bochs/bochs_mm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/bochs/bochs_mm.c b/drivers/gpu/drm/bochs/bochs_mm.c

[PATCH v2 06/12] drm/nouveau: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/nouveau/nouveau_bo.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_bo.c

[PATCH v2 10/12] drm/vmwgfx: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c

[PATCH v2 10/12] drm/vmwgfx: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_buffer.c

[PATCH v2 02/12] drm/ast: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/ast/ast_ttm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/ast/ast_ttm.c

[PATCH v2 02/12] drm/ast: remove the default io_mem_pfn set

The default interface situation has been taken into the framework, so remove the default set of each module. Signed-off-by: Tan Xiaojun --- drivers/gpu/drm/ast/ast_ttm.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/ast/ast_ttm.c b/drivers/gpu/drm/ast/ast_ttm.c index

Re: [linux-sunxi] [PATCH v4 0/2] Initial Allwinner V3s CSI Support

Hi, On Fri, 22 Dec 2017 14:46:48 +0100 Ondřej Jirman wrote: > Hello, > > Yong Deng píše v Pá 22. 12. 2017 v 17:32 +0800: > > This patchset add initial support for Allwinner V3s CSI. > > > > Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface > > and CSI1

Re: [linux-sunxi] [PATCH v4 0/2] Initial Allwinner V3s CSI Support

Hi, On Fri, 22 Dec 2017 14:46:48 +0100 Ondřej Jirman wrote: > Hello, > > Yong Deng píše v Pá 22. 12. 2017 v 17:32 +0800: > > This patchset add initial support for Allwinner V3s CSI. > > > > Allwinner V3s SoC have two CSI module. CSI0 is used for MIPI interface > > and CSI1 is used for

Re: [PATCH 4/4] KVM: nVMX: initialize more non-shadowed fields in prepare_vmcs02_full

2017-12-21 20:43 GMT+08:00 Paolo Bonzini : > These fields are also simple copies of the data in the vmcs12 struct. > For some of them, prepare_vmcs02 was skipping the copy when the field > was unused. In prepare_vmcs02_full, we copy them always as long as the > field exists

Re: [PATCH 4/4] KVM: nVMX: initialize more non-shadowed fields in prepare_vmcs02_full

2017-12-21 20:43 GMT+08:00 Paolo Bonzini : > These fields are also simple copies of the data in the vmcs12 struct. > For some of them, prepare_vmcs02 was skipping the copy when the field > was unused. In prepare_vmcs02_full, we copy them always as long as the > field exists on the host, because

Re: [PATCH 2/4] KVM: nVMX: track dirty state of non-shadowed VMCS fields

2017-12-21 20:43 GMT+08:00 Paolo Bonzini : > VMCS12 fields that are not handled through shadow VMCS are rarely > written, and thus they are also almost constant in the vmcs02. We can > thus optimize prepare_vmcs02 by skipping all the work for non-shadowed > fields in the

Re: [PATCH 2/4] KVM: nVMX: track dirty state of non-shadowed VMCS fields

2017-12-21 20:43 GMT+08:00 Paolo Bonzini : > VMCS12 fields that are not handled through shadow VMCS are rarely > written, and thus they are also almost constant in the vmcs02. We can > thus optimize prepare_vmcs02 by skipping all the work for non-shadowed > fields in the common case. > > This

RE: [PATCH] usb: dwc3: gadget:Core consumes a trb software to fill a trb, in ISO

Hi, > -Original Message- > From: Felipe Balbi [mailto:ba...@kernel.org] > Sent: Friday, December 22, 2017 3:54 PM > To: Lipengcheng > Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Lipengcheng > Subject: Re: [PATCH] usb: dwc3: gadget:Core consumes a trb software to fill a >

RE: [PATCH] usb: dwc3: gadget:Core consumes a trb software to fill a trb, in ISO

Hi, > -Original Message- > From: Felipe Balbi [mailto:ba...@kernel.org] > Sent: Friday, December 22, 2017 3:54 PM > To: Lipengcheng > Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Lipengcheng > Subject: Re: [PATCH] usb: dwc3: gadget:Core consumes a trb software to fill a >

[PATCH] x86/kconfig: remove residual cmdline param "no-hlt"

cmdline param "no-hlt" has been removed in commit 27be457000211a6903968dfce06d5f73f051a217. Signed-off-by: zhenwei.pi --- arch/x86/Kconfig | 21 ++--- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig

[PATCH] x86/kconfig: remove residual cmdline param "no-hlt"

cmdline param "no-hlt" has been removed in commit 27be457000211a6903968dfce06d5f73f051a217. Signed-off-by: zhenwei.pi --- arch/x86/Kconfig | 21 ++--- 1 file changed, 10 insertions(+), 11 deletions(-) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index d4fc98c..fa9c33c

Re: [PATCH] perf tool: Return all events as auto-completions after comma

One other thing you may want to look at: $ $ perf record -e cycles/ Should present the modifiers, i.e. these: /* * Update according to parse-events.l */ static const char *config_term_names[__PARSE_EVENTS__TERM_TYPE_NR] = { [PARSE_EVENTS__TERM_TYPE_USER] =

Re: [PATCH] perf tool: Return all events as auto-completions after comma

One other thing you may want to look at: $ $ perf record -e cycles/ Should present the modifiers, i.e. these: /* * Update according to parse-events.l */ static const char *config_term_names[__PARSE_EVENTS__TERM_TYPE_NR] = { [PARSE_EVENTS__TERM_TYPE_USER] =

Re: [f2fs-dev] [PATCH v2] f2fs: add an ioctl to disable GC for specific file

On 2017/12/20 6:52, Jaegeuk Kim wrote: > On 12/18, Chao Yu wrote: >> On 2017/12/15 3:50, Jaegeuk Kim wrote: >>> On 12/12, Chao Yu wrote: Hi Jaegeuk, On 2017/12/9 3:37, Jaegeuk Kim wrote: > Change log from v1: > - fix bug in error handling of ioctl > > >From

Re: [f2fs-dev] [PATCH v2] f2fs: add an ioctl to disable GC for specific file

On 2017/12/20 6:52, Jaegeuk Kim wrote: > On 12/18, Chao Yu wrote: >> On 2017/12/15 3:50, Jaegeuk Kim wrote: >>> On 12/12, Chao Yu wrote: Hi Jaegeuk, On 2017/12/9 3:37, Jaegeuk Kim wrote: > Change log from v1: > - fix bug in error handling of ioctl > > >From

Re: TPM driver breaks S3 suspend

On Mon, Dec 25, 2017 at 4:33 AM, Jarkko Sakkinen wrote: > On Thu, Dec 21, 2017 at 04:04:56PM +0800, Chris Chiu wrote: >> Hi, >> We have a desktop which has S3 suspend (to RAM) problem due to >> error messages as follows. >> [ 198.908282] tpm tpm0: Error (38)

Re: TPM driver breaks S3 suspend

On Mon, Dec 25, 2017 at 4:33 AM, Jarkko Sakkinen wrote: > On Thu, Dec 21, 2017 at 04:04:56PM +0800, Chris Chiu wrote: >> Hi, >> We have a desktop which has S3 suspend (to RAM) problem due to >> error messages as follows. >> [ 198.908282] tpm tpm0: Error (38) sending savestate before suspend

[PATCH v2 1/3] tpm: delete the TPM_TIS_CLK_ENABLE flag

This flag is only used to warn if CLKRUN_EN wasn't disabled on Braswell systems, but the only way this can happen is if the code is not correct. So it's an unnecessary check that just makes the code harder to read. Suggested-by: Jarkko Sakkinen Signed-off-by:

[PATCH v2 1/3] tpm: delete the TPM_TIS_CLK_ENABLE flag

This flag is only used to warn if CLKRUN_EN wasn't disabled on Braswell systems, but the only way this can happen is if the code is not correct. So it's an unnecessary check that just makes the code harder to read. Suggested-by: Jarkko Sakkinen Signed-off-by: Javier Martinez Canillas

[PATCH v2 0/3] tpm: fix PS/2 devices not working on Braswell systems due CLKRUN enabled

Hello, Commit 5e572cab92f0 ("tpm: Enable CLKRUN protocol for Braswell systems") added logic in the TPM TIS driver to disable the Low Pin Count CLKRUN signal during TPM transactions. Unfortunately this breaks other devices that are attached to the LPC bus like for example PS/2 mouse and

[PATCH v2 0/3] tpm: fix PS/2 devices not working on Braswell systems due CLKRUN enabled

Hello, Commit 5e572cab92f0 ("tpm: Enable CLKRUN protocol for Braswell systems") added logic in the TPM TIS driver to disable the Low Pin Count CLKRUN signal during TPM transactions. Unfortunately this breaks other devices that are attached to the LPC bus like for example PS/2 mouse and

[PATCH v2 2/3] tpm: follow coding style for variable declaration in tpm_tis_core_init()

The coding style says "use just one data declaration per line (no commas for multiple data declarations)" so follow this convention. Suggested-by: Jarkko Sakkinen Signed-off-by: Javier Martinez Canillas Reviewed-by: Jarkko Sakkinen

[PATCH v2 2/3] tpm: follow coding style for variable declaration in tpm_tis_core_init()

The coding style says "use just one data declaration per line (no commas for multiple data declarations)" so follow this convention. Suggested-by: Jarkko Sakkinen Signed-off-by: Javier Martinez Canillas Reviewed-by: Jarkko Sakkinen Tested-by: Jarkko Sakkinen ---

[PATCH v2 3/3] tpm: only attempt to disable the LPC CLKRUN if is already enabled

Commit 5e572cab92f0 ("tpm: Enable CLKRUN protocol for Braswell systems") added logic in the TPM TIS driver to disable the Low Pin Count CLKRUN signal during TPM transactions. Unfortunately this breaks other devices that are attached to the LPC bus like for example PS/2 mouse and keyboards. One

[PATCH v2 3/3] tpm: only attempt to disable the LPC CLKRUN if is already enabled

Commit 5e572cab92f0 ("tpm: Enable CLKRUN protocol for Braswell systems") added logic in the TPM TIS driver to disable the Low Pin Count CLKRUN signal during TPM transactions. Unfortunately this breaks other devices that are attached to the LPC bus like for example PS/2 mouse and keyboards. One

Re: [PATCH v2] arm64: dts: Hi3660: Fix up psci state id

Hi Vincent, [ + John, Kevin Wang ] On Fri, Dec 22, 2017 at 03:22:51PM +0100, Vincent Guittot wrote: > Hi Leo, > > Sorry for jumping late in the discussion but should we also remove > the NAP state from the property cpu-idle-states of the CPUs because > this state not supported by the platform

Re: [PATCH v2] arm64: dts: Hi3660: Fix up psci state id

Hi Vincent, [ + John, Kevin Wang ] On Fri, Dec 22, 2017 at 03:22:51PM +0100, Vincent Guittot wrote: > Hi Leo, > > Sorry for jumping late in the discussion but should we also remove > the NAP state from the property cpu-idle-states of the CPUs because > this state not supported by the platform

[RFC] dmaengine: pl330: fix a race condition in case of threaded irqs

I found this problem below, and I now understand why it happens, but I'm not 100% sure what is the best way to fix it. When booting up with "threadirqs" in command line, all irq handlers of the DMA controller pl330 will be threaded forcedly. These threads will race for the same list,

[RFC] dmaengine: pl330: fix a race condition in case of threaded irqs

I found this problem below, and I now understand why it happens, but I'm not 100% sure what is the best way to fix it. When booting up with "threadirqs" in command line, all irq handlers of the DMA controller pl330 will be threaded forcedly. These threads will race for the same list,

Re: [PATCH v3 0/3] create sysfs representation of ACPI HMAT

On 2017/12/23 6:31, Ross Zwisler wrote: > On Fri, Dec 22, 2017 at 08:39:41AM +0530, Anshuman Khandual wrote: >> On 12/14/2017 07:40 AM, Ross Zwisler wrote: > <> >>> We solve this issue by providing userspace with performance information on >>> individual memory ranges. This performance

Re: [PATCH v3 0/3] create sysfs representation of ACPI HMAT

On 2017/12/23 6:31, Ross Zwisler wrote: > On Fri, Dec 22, 2017 at 08:39:41AM +0530, Anshuman Khandual wrote: >> On 12/14/2017 07:40 AM, Ross Zwisler wrote: > <> >>> We solve this issue by providing userspace with performance information on >>> individual memory ranges. This performance

Re: [PATCH v3 27/27] devres: kill devm_ioremap_nocache

On 2017/12/23 21:45, Greg KH wrote: > On Sat, Dec 23, 2017 at 07:02:59PM +0800, Yisheng Xie wrote: >> --- a/lib/devres.c >> +++ b/lib/devres.c >> @@ -44,35 +44,6 @@ void __iomem *devm_ioremap(struct device *dev, >> resource_size_t offset, >> EXPORT_SYMBOL(devm_ioremap); >> >> /** >> - *

Re: [PATCH v3 27/27] devres: kill devm_ioremap_nocache

On 2017/12/23 21:45, Greg KH wrote: > On Sat, Dec 23, 2017 at 07:02:59PM +0800, Yisheng Xie wrote: >> --- a/lib/devres.c >> +++ b/lib/devres.c >> @@ -44,35 +44,6 @@ void __iomem *devm_ioremap(struct device *dev, >> resource_size_t offset, >> EXPORT_SYMBOL(devm_ioremap); >> >> /** >> - *

  1   2   3   >