Re: [PATCH V5 0/2] nvme-pci: fix the timeout case when reset is ongoing

On Thu, Jan 18, 2018 at 06:10:00PM +0800, Jianchao Wang wrote: > Hello > > Please consider the following scenario. > nvme_reset_ctrl > -> set state to RESETTING > -> queue reset_work > (scheduling) > nvme_reset_work > -> nvme_dev_disable > -> quiesce queues > ->

Re: [PATCH V5 0/2] nvme-pci: fix the timeout case when reset is ongoing

On Thu, Jan 18, 2018 at 06:10:00PM +0800, Jianchao Wang wrote: > Hello > > Please consider the following scenario. > nvme_reset_ctrl > -> set state to RESETTING > -> queue reset_work > (scheduling) > nvme_reset_work > -> nvme_dev_disable > -> quiesce queues > ->

Re: [PATCH 6/6] s390: scrub registers on kernel entry and KVM exit

On 01/19/2018 07:29 AM, QingFeng Hao wrote: > > > 在 2018/1/17 17:48, Martin Schwidefsky 写道: >> Clear all user space registers on entry to the kernel and all KVM guest >> registers on KVM guest exit if the register does not contain either a >> parameter or a result value. > I am not sure if I

Re: [PATCH 6/6] s390: scrub registers on kernel entry and KVM exit

On 01/19/2018 07:29 AM, QingFeng Hao wrote: > > > 在 2018/1/17 17:48, Martin Schwidefsky 写道: >> Clear all user space registers on entry to the kernel and all KVM guest >> registers on KVM guest exit if the register does not contain either a >> parameter or a result value. > I am not sure if I

[PATCH][V2] mtd: nand: marvell: fix spelling mistake: "suceed"-> "succeed"

From: Colin Ian King Trivial fix to spelling mistakes in dev_err error message text. Signed-off-by: Colin Ian King --- drivers/mtd/nand/marvell_nand.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH][V2] mtd: nand: marvell: fix spelling mistake: "suceed"-> "succeed"

From: Colin Ian King Trivial fix to spelling mistakes in dev_err error message text. Signed-off-by: Colin Ian King --- drivers/mtd/nand/marvell_nand.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mtd/nand/marvell_nand.c b/drivers/mtd/nand/marvell_nand.c index

Re: [PATCH 4.4 045/115] sched/deadline: Throttle a constrained deadline task activated after the deadline

On Fri, Jan 19, 2018 at 01:00:45AM +, Ben Hutchings wrote: > On Mon, 2017-12-18 at 16:48 +0100, Greg Kroah-Hartman wrote: > > 4.4-stable review patch.  If anyone has any objections, please let me > > know. > > > > -- > > > > From: Daniel Bristot de Oliveira

Re: [PATCH 4.4 045/115] sched/deadline: Throttle a constrained deadline task activated after the deadline

On Fri, Jan 19, 2018 at 01:00:45AM +, Ben Hutchings wrote: > On Mon, 2017-12-18 at 16:48 +0100, Greg Kroah-Hartman wrote: > > 4.4-stable review patch.  If anyone has any objections, please let me > > know. > > > > -- > > > > From: Daniel Bristot de Oliveira > > > > > > [

Re: [PATCH 4.4 040/115] scsi: hpsa: update check for logical volume status

On Fri, Jan 19, 2018 at 12:29:12AM +, Ben Hutchings wrote: > On Mon, 2017-12-18 at 16:48 +0100, Greg Kroah-Hartman wrote: > > 4.4-stable review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: Don Brace > > > > > >

Re: [PATCH 4.4 040/115] scsi: hpsa: update check for logical volume status

On Fri, Jan 19, 2018 at 12:29:12AM +, Ben Hutchings wrote: > On Mon, 2017-12-18 at 16:48 +0100, Greg Kroah-Hartman wrote: > > 4.4-stable review patch.  If anyone has any objections, please let me know. > > > > -- > > > > From: Don Brace > > > > > > [ Upstream commit

Re: [PATCH] general protection fault in sock_has_perm

On Thu, Jan 18, 2018 at 01:58:45PM -0800, Mark Salyzyn wrote: > general protection fault: [#1] PREEMPT SMP KASAN > CPU: 1 PID: 14233 Comm: syz-executor2 Not tainted 4.4.112-g5f6325b #28 > task: 8801d1095f00 task.stack: 8800b595 > RIP: 0010:[] [] > sock_has_perm+0x1fe/0x3e0

Re: [PATCH] general protection fault in sock_has_perm

On Thu, Jan 18, 2018 at 01:58:45PM -0800, Mark Salyzyn wrote: > general protection fault: [#1] PREEMPT SMP KASAN > CPU: 1 PID: 14233 Comm: syz-executor2 Not tainted 4.4.112-g5f6325b #28 > task: 8801d1095f00 task.stack: 8800b595 > RIP: 0010:[] [] > sock_has_perm+0x1fe/0x3e0

答复: 答复: 答复: [PATCH v6] mfd: Add support for RTS5250S power saving

> On Wed, Dec 27, 2017 at 05:37:50PM -0600, Bjorn Helgaas wrote: > > On Tue, Dec 19, 2017 at 08:15:24AM +, 冯锐 wrote: > > > > On Fri, Dec 15, 2017 at 09:42:45AM +, 冯锐 wrote: > > > > > > [+cc Hans, Dave, linux-pci] > > > > > > > > > > > > On Thu, Sep 07, 2017 at 04:26:39PM +0800, > > > > > >

答复: 答复: 答复: [PATCH v6] mfd: Add support for RTS5250S power saving

> On Wed, Dec 27, 2017 at 05:37:50PM -0600, Bjorn Helgaas wrote: > > On Tue, Dec 19, 2017 at 08:15:24AM +, 冯锐 wrote: > > > > On Fri, Dec 15, 2017 at 09:42:45AM +, 冯锐 wrote: > > > > > > [+cc Hans, Dave, linux-pci] > > > > > > > > > > > > On Thu, Sep 07, 2017 at 04:26:39PM +0800, > > > > > >

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On Fri, Jan 19, 2018 at 05:09:46AM +, Bart Van Assche wrote: > On Fri, 2018-01-19 at 10:32 +0800, Ming Lei wrote: > > Now most of times both NVMe and SCSI won't return BLK_STS_RESOURCE, and > > it should be DM-only which returns STS_RESOURCE so often. > > That's wrong at least for SCSI. See

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On Fri, Jan 19, 2018 at 05:09:46AM +, Bart Van Assche wrote: > On Fri, 2018-01-19 at 10:32 +0800, Ming Lei wrote: > > Now most of times both NVMe and SCSI won't return BLK_STS_RESOURCE, and > > it should be DM-only which returns STS_RESOURCE so often. > > That's wrong at least for SCSI. See

Re: [patch v17 2/4] drivers: jtag: Add Aspeed SoC 24xx and 25xx families JTAG master driver

Hi Oleksandr, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.15-rc8] [cannot apply to next-20180118] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

Re: [patch v17 2/4] drivers: jtag: Add Aspeed SoC 24xx and 25xx families JTAG master driver

Hi Oleksandr, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.15-rc8] [cannot apply to next-20180118] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On Thu, Jan 18, 2018 at 09:02:45PM -0700, Jens Axboe wrote: > On 1/18/18 7:32 PM, Ming Lei wrote: > > On Thu, Jan 18, 2018 at 01:11:01PM -0700, Jens Axboe wrote: > >> On 1/18/18 11:47 AM, Bart Van Assche wrote: > This is all very tiresome. > >>> > >>> Yes, this is tiresome. It is very

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On Thu, Jan 18, 2018 at 09:02:45PM -0700, Jens Axboe wrote: > On 1/18/18 7:32 PM, Ming Lei wrote: > > On Thu, Jan 18, 2018 at 01:11:01PM -0700, Jens Axboe wrote: > >> On 1/18/18 11:47 AM, Bart Van Assche wrote: > This is all very tiresome. > >>> > >>> Yes, this is tiresome. It is very

Re: [RESEND PATCH 3/3] x86/apic: Clean up the names of legacy irq mode setting related functions

On 01/19/18 at 02:42pm, Dou Liyang wrote: > Hi Baoquan, > > At 01/05/2018 12:39 PM, Baoquan He wrote: > [...] > > /* > > - * Not an __init, needed by kexec/kdump code. > > - * For safety IO-APIC and Local APIC need be cleared before this. > > + * In legacy irq mode, full DOS compatibility with

Re: [RESEND PATCH 3/3] x86/apic: Clean up the names of legacy irq mode setting related functions

On 01/19/18 at 02:42pm, Dou Liyang wrote: > Hi Baoquan, > > At 01/05/2018 12:39 PM, Baoquan He wrote: > [...] > > /* > > - * Not an __init, needed by kexec/kdump code. > > - * For safety IO-APIC and Local APIC need be cleared before this. > > + * In legacy irq mode, full DOS compatibility with

Re: [PATCH v4] perf report: Fix regression when decoding intelPT traces

On 18/01/18 18:29, Arnaldo Carvalho de Melo wrote: > Em Wed, Jan 10, 2018 at 01:31:52PM -0700, Mathieu Poirier escreveu: >> Commit (93d10af26bb7 perf tools: Optimize sample parsing for ordered >> events) breaks intelPT trace decoding by invariably returning an error if >> the event type isn't a

Re: [PATCH v4] perf report: Fix regression when decoding intelPT traces

On 18/01/18 18:29, Arnaldo Carvalho de Melo wrote: > Em Wed, Jan 10, 2018 at 01:31:52PM -0700, Mathieu Poirier escreveu: >> Commit (93d10af26bb7 perf tools: Optimize sample parsing for ordered >> events) breaks intelPT trace decoding by invariably returning an error if >> the event type isn't a

[PATCH] Fix explanation of lower bits in the SPARSEMEM mem_map pointer

The comment is confusing. On the one hand, it refers to 32-bit alignment (struct page alignment on 32-bit platforms), but this would only guarantee that the 2 lowest bits must be zero. On the other hand, it claims that at least 3 bits are available, and 3 bits are actually used. This is not

[PATCH] Fix explanation of lower bits in the SPARSEMEM mem_map pointer

The comment is confusing. On the one hand, it refers to 32-bit alignment (struct page alignment on 32-bit platforms), but this would only guarantee that the 2 lowest bits must be zero. On the other hand, it claims that at least 3 bits are available, and 3 bits are actually used. This is not

Re: [PATCH v5 0/2] kprobes: improve error handling when arming/disarming kprobes

Hi Ingo, Could you pick this to tip tree? Thank you, On Wed, 10 Jan 2018 00:51:22 +0100 Jessica Yu wrote: > Hi, > > This patchset attempts to improve error handling when arming or disarming > ftrace-based kprobes. The current behavior is to simply WARN when ftrace >

Re: [PATCH v5 0/2] kprobes: improve error handling when arming/disarming kprobes

Hi Ingo, Could you pick this to tip tree? Thank you, On Wed, 10 Jan 2018 00:51:22 +0100 Jessica Yu wrote: > Hi, > > This patchset attempts to improve error handling when arming or disarming > ftrace-based kprobes. The current behavior is to simply WARN when ftrace > (un-)registration fails,

Re: [PATCH] xhci:Fix NULL pointer in xhci debugfs

On 19.01.2018 04:13, Zhengjun Xing wrote: Commit dde634057da7 ("xhci: Fix use-after-free in xhci debugfs") causes a null pointer dereference while fixing xhci-debugfs usage of ring pointers that were freed during hibernate. The fix passed addresses to ring pointers instead, but forgot to do

Re: [PATCH] xhci:Fix NULL pointer in xhci debugfs

On 19.01.2018 04:13, Zhengjun Xing wrote: Commit dde634057da7 ("xhci: Fix use-after-free in xhci debugfs") causes a null pointer dereference while fixing xhci-debugfs usage of ring pointers that were freed during hibernate. The fix passed addresses to ring pointers instead, but forgot to do

linux-next: Tree for Jan 19

Hi all, News: there will probably be very few, if any, releases next week as LCA is on (unfortunate clash with the merge window). Changes since 20180118: The powerpc tree gained a build failure due to an interaction with Linus' tree, so I applied a merge fix patch. It gained another for which

linux-next: Tree for Jan 19

Hi all, News: there will probably be very few, if any, releases next week as LCA is on (unfortunate clash with the merge window). Changes since 20180118: The powerpc tree gained a build failure due to an interaction with Linus' tree, so I applied a merge fix patch. It gained another for which

Re: [PATCH V5 2/2] nvme-pci: fixup the timeout case when reset is ongoing

Hi Keith Thanks for your kindly reminding. On 01/19/2018 02:05 PM, Keith Busch wrote: >>> The driver may be giving up on the command here, but that doesn't mean >>> the controller has. We can't just end the request like this because that >>> will release the memory the controller still owns. We

Re: [PATCH V5 2/2] nvme-pci: fixup the timeout case when reset is ongoing

Hi Keith Thanks for your kindly reminding. On 01/19/2018 02:05 PM, Keith Busch wrote: >>> The driver may be giving up on the command here, but that doesn't mean >>> the controller has. We can't just end the request like this because that >>> will release the memory the controller still owns. We

[git pull] drm fixes for 4.15 final

Hi Linus, This is a set of drm regression fixes that I'd like to get into 4.15 final, but I understand if it's too much too late, and am happy to drop these into -next and make people chase the stable monkey. The i915 change fixes a display corruption problem introduced in 4.15, the nouveau

[git pull] drm fixes for 4.15 final

Hi Linus, This is a set of drm regression fixes that I'd like to get into 4.15 final, but I understand if it's too much too late, and am happy to drop these into -next and make people chase the stable monkey. The i915 change fixes a display corruption problem introduced in 4.15, the nouveau

Re: [RESEND PATCH 3/3] x86/apic: Clean up the names of legacy irq mode setting related functions

Hi Baoquan, At 01/05/2018 12:39 PM, Baoquan He wrote: [...] /* - * Not an __init, needed by kexec/kdump code. - * For safety IO-APIC and Local APIC need be cleared before this. + * In legacy irq mode, full DOS compatibility with the uniprocessor PC/AT is + * provided by using the APICs in

Re: [RESEND PATCH 3/3] x86/apic: Clean up the names of legacy irq mode setting related functions

Hi Baoquan, At 01/05/2018 12:39 PM, Baoquan He wrote: [...] /* - * Not an __init, needed by kexec/kdump code. - * For safety IO-APIC and Local APIC need be cleared before this. + * In legacy irq mode, full DOS compatibility with the uniprocessor PC/AT is + * provided by using the APICs in

Re: [RESEND] phy: sun4i-usb: add support for R40 USB PHY

于 2018年1月19日 GMT+08:00 下午2:25:09, Chen-Yu Tsai 写到: >Hi Kishon, > >On Mon, Jan 15, 2018 at 11:06 PM, Hermann Lauer > wrote: >> On Wed, Jan 03, 2018 at 04:49:44PM +0800, Icenowy Zheng wrote: >>> Allwinner R40 features a USB PHY like the one in

Re: [RESEND] phy: sun4i-usb: add support for R40 USB PHY

于 2018年1月19日 GMT+08:00 下午2:25:09, Chen-Yu Tsai 写到: >Hi Kishon, > >On Mon, Jan 15, 2018 at 11:06 PM, Hermann Lauer > wrote: >> On Wed, Jan 03, 2018 at 04:49:44PM +0800, Icenowy Zheng wrote: >>> Allwinner R40 features a USB PHY like the one in A64, but with 3 >PHYs. >>> >>> Add support for it.

Re: [PATCH 6/6] s390: scrub registers on kernel entry and KVM exit

在 2018/1/17 17:48, Martin Schwidefsky 写道: Clear all user space registers on entry to the kernel and all KVM guest registers on KVM guest exit if the register does not contain either a parameter or a result value. I am not sure if I understand this but it will be safer? And can we abstract the

Re: [PATCH 6/6] s390: scrub registers on kernel entry and KVM exit

在 2018/1/17 17:48, Martin Schwidefsky 写道: Clear all user space registers on entry to the kernel and all KVM guest registers on KVM guest exit if the register does not contain either a parameter or a result value. I am not sure if I understand this but it will be safer? And can we abstract the

Re: [RESEND] phy: sun4i-usb: add support for R40 USB PHY

Hi Kishon, On Mon, Jan 15, 2018 at 11:06 PM, Hermann Lauer wrote: > On Wed, Jan 03, 2018 at 04:49:44PM +0800, Icenowy Zheng wrote: >> Allwinner R40 features a USB PHY like the one in A64, but with 3 PHYs. >> >> Add support for it. >> >> Signed-off-by: Icenowy

Re: [RESEND] phy: sun4i-usb: add support for R40 USB PHY

Hi Kishon, On Mon, Jan 15, 2018 at 11:06 PM, Hermann Lauer wrote: > On Wed, Jan 03, 2018 at 04:49:44PM +0800, Icenowy Zheng wrote: >> Allwinner R40 features a USB PHY like the one in A64, but with 3 PHYs. >> >> Add support for it. >> >> Signed-off-by: Icenowy Zheng >> Acked-by: Maxime Ripard

Re: [RESEND PATCH 2/3] x86/apic/kexec: Enable legacy irq mode before jump to kexec/kdump kernel

Hi Baoquan, At 01/17/2018 06:08 PM, Baoquan He wrote: On 01/17/18 at 05:47pm, Dou Liyang wrote: Hi Baoquan, At 01/05/2018 12:38 PM, Baoquan He wrote: In commit commit 522e66464467 ("x86/apic: Disable I/O APIC before shutdown of the local APIC"). lapic_shutdown() invocation is moved after

Re: [RESEND PATCH 2/3] x86/apic/kexec: Enable legacy irq mode before jump to kexec/kdump kernel

Hi Baoquan, At 01/17/2018 06:08 PM, Baoquan He wrote: On 01/17/18 at 05:47pm, Dou Liyang wrote: Hi Baoquan, At 01/05/2018 12:38 PM, Baoquan He wrote: In commit commit 522e66464467 ("x86/apic: Disable I/O APIC before shutdown of the local APIC"). lapic_shutdown() invocation is moved after

Re: [PATCH v22 2/3] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_VQ

On 01/18/2018 12:44 AM, Michael S. Tsirkin wrote: On Wed, Jan 17, 2018 at 01:10:11PM +0800, Wei Wang wrote: +static void virtballoon_changed(struct virtio_device *vdev) +{ + struct virtio_balloon *vb = vdev->priv; + unsigned long flags; + __u32 cmd_id; + s64 diff =

Re: [PATCH v22 2/3] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_VQ

On 01/18/2018 12:44 AM, Michael S. Tsirkin wrote: On Wed, Jan 17, 2018 at 01:10:11PM +0800, Wei Wang wrote: +static void virtballoon_changed(struct virtio_device *vdev) +{ + struct virtio_balloon *vb = vdev->priv; + unsigned long flags; + __u32 cmd_id; + s64 diff =

Re: [PATCH v5 20/44] dt-bindings: clock: Add bindings for TI DA8XX USB PHY clocks

On Friday 19 January 2018 12:30 AM, David Lechner wrote: > On 01/18/2018 06:10 AM, Sekhar Nori wrote: >> On Monday 08 January 2018 07:47 AM, David Lechner wrote: >>> This adds a new binding for TI DA8XX USB PHY clocks. These clocks are >>> part >>> of a syscon register called CFGCHIP3. >> >>

Re: [PATCH v5 20/44] dt-bindings: clock: Add bindings for TI DA8XX USB PHY clocks

On Friday 19 January 2018 12:30 AM, David Lechner wrote: > On 01/18/2018 06:10 AM, Sekhar Nori wrote: >> On Monday 08 January 2018 07:47 AM, David Lechner wrote: >>> This adds a new binding for TI DA8XX USB PHY clocks. These clocks are >>> part >>> of a syscon register called CFGCHIP3. >> >>

Re: [PATCH v5 43/44] ARM: da8xx-dt: switch to device tree clocks

On Friday 19 January 2018 12:10 AM, David Lechner wrote: > On 01/18/2018 09:27 AM, Sekhar Nori wrote: >> On Monday 08 January 2018 07:55 AM, David Lechner wrote: >>> This removes all of the clock init code from da8xx-dt.c. This includes >>> all of the OF_DEV_AUXDATA that was just used for looking

Re: [PATCH v5 43/44] ARM: da8xx-dt: switch to device tree clocks

On Friday 19 January 2018 12:10 AM, David Lechner wrote: > On 01/18/2018 09:27 AM, Sekhar Nori wrote: >> On Monday 08 January 2018 07:55 AM, David Lechner wrote: >>> This removes all of the clock init code from da8xx-dt.c. This includes >>> all of the OF_DEV_AUXDATA that was just used for looking

[PATCH V2 net-next 1/4] net: hns3: add support for get_regs

From: Fuyun Liang This patch adds get_regs support for ethtool cmd. Signed-off-by: Fuyun Liang Signed-off-by: Peng Li --- drivers/net/ethernet/hisilicon/hns3/hnae3.h| 3 +-

[PATCH V2 net-next 1/4] net: hns3: add support for get_regs

From: Fuyun Liang This patch adds get_regs support for ethtool cmd. Signed-off-by: Fuyun Liang Signed-off-by: Peng Li --- drivers/net/ethernet/hisilicon/hns3/hnae3.h| 3 +- drivers/net/ethernet/hisilicon/hns3/hns3_ethtool.c | 23 +++

[PATCH V2 net-next 2/4] net: hns3: add manager table initialization for hardware

From: Fuyun Liang The manager table is empty by default. If it is not initialized, the management pkgs like LLDP will be dropped by hardware. Default entries need to be added to manager table. Signed-off-by: Fuyun Liang Signed-off-by: Peng Li

[PATCH V2 net-next 3/4] net: hns3: add ethtool -p support for fiber port

From: Jian Shen Add led location support for fiber port. The led will keep blinking when locating. Signed-off-by: Jian Shen Signed-off-by: Peng Li --- drivers/net/ethernet/hisilicon/hns3/hnae3.h| 2 +

[PATCH V2 net-next 2/4] net: hns3: add manager table initialization for hardware

From: Fuyun Liang The manager table is empty by default. If it is not initialized, the management pkgs like LLDP will be dropped by hardware. Default entries need to be added to manager table. Signed-off-by: Fuyun Liang Signed-off-by: Peng Li ---

[PATCH V2 net-next 3/4] net: hns3: add ethtool -p support for fiber port

From: Jian Shen Add led location support for fiber port. The led will keep blinking when locating. Signed-off-by: Jian Shen Signed-off-by: Peng Li --- drivers/net/ethernet/hisilicon/hns3/hnae3.h| 2 + drivers/net/ethernet/hisilicon/hns3/hns3_ethtool.c | 12

[PATCH V2 net-next 4/4] net: hns3: add net status led support for fiber port

From: Jian Shen Check the net status per second, include port speed, total rx/tx packets and link status. Updating the led status for fiber port. Signed-off-by: Jian Shen Signed-off-by: Peng Li ---

[PATCH V2 net-next 4/4] net: hns3: add net status led support for fiber port

From: Jian Shen Check the net status per second, include port speed, total rx/tx packets and link status. Updating the led status for fiber port. Signed-off-by: Jian Shen Signed-off-by: Peng Li --- .../net/ethernet/hisilicon/hns3/hns3pf/hclge_cmd.h | 1 +

[PATCH V2 net-next 0/4] add some features to hns3 driver

This patchset adds some features to hns3 driver, include the support for ethtool command -d, -p and support for manager table. [Patch 1/4] adds support for ethtool command -d, its ops is get_regs. driver will send command to command queue, and get regs number and regs value from command queue.

[PATCH V2 net-next 0/4] add some features to hns3 driver

This patchset adds some features to hns3 driver, include the support for ethtool command -d, -p and support for manager table. [Patch 1/4] adds support for ethtool command -d, its ops is get_regs. driver will send command to command queue, and get regs number and regs value from command queue.

Re: [PATCH 3/4] drm/gem: adjust per file OOM badness on handling buffers

On 2018年01月19日 00:47, Andrey Grodzovsky wrote: Large amounts of VRAM are usually not CPU accessible, so they are not mapped into the processes address space. But since the device drivers usually support swapping buffers from VRAM to system memory we can still run into an out of memory

Re: [PATCH V5 2/2] nvme-pci: fixup the timeout case when reset is ongoing

On Fri, Jan 19, 2018 at 01:55:29PM +0800, jianchao.wang wrote: > On 01/19/2018 12:59 PM, Keith Busch wrote: > > On Thu, Jan 18, 2018 at 06:10:02PM +0800, Jianchao Wang wrote: > >> + * - When the ctrl.state is NVME_CTRL_RESETTING, the expired > >> + * request should come from the previous

Re: [PATCH 3/4] drm/gem: adjust per file OOM badness on handling buffers

On 2018年01月19日 00:47, Andrey Grodzovsky wrote: Large amounts of VRAM are usually not CPU accessible, so they are not mapped into the processes address space. But since the device drivers usually support swapping buffers from VRAM to system memory we can still run into an out of memory

Re: [PATCH V5 2/2] nvme-pci: fixup the timeout case when reset is ongoing

On Fri, Jan 19, 2018 at 01:55:29PM +0800, jianchao.wang wrote: > On 01/19/2018 12:59 PM, Keith Busch wrote: > > On Thu, Jan 18, 2018 at 06:10:02PM +0800, Jianchao Wang wrote: > >> + * - When the ctrl.state is NVME_CTRL_RESETTING, the expired > >> + * request should come from the previous

RE: [RFC] Per file OOM badness

-Original Message- From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf Of Michal Hocko Sent: Friday, January 19, 2018 1:14 AM To: Grodzovsky, Andrey Cc: linux...@kvack.org; amd-...@lists.freedesktop.org; linux-kernel@vger.kernel.org;

RE: [RFC] Per file OOM badness

-Original Message- From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf Of Michal Hocko Sent: Friday, January 19, 2018 1:14 AM To: Grodzovsky, Andrey Cc: linux...@kvack.org; amd-...@lists.freedesktop.org; linux-kernel@vger.kernel.org; dri-de...@lists.freedesktop.org;

Re: [PATCH V5 2/2] nvme-pci: fixup the timeout case when reset is ongoing

Hi Keith Thanks for your kindly response and directive. On 01/19/2018 12:59 PM, Keith Busch wrote: > On Thu, Jan 18, 2018 at 06:10:02PM +0800, Jianchao Wang wrote: >> + * - When the ctrl.state is NVME_CTRL_RESETTING, the expired >> + * request should come from the previous work and we

Re: [PATCH V5 2/2] nvme-pci: fixup the timeout case when reset is ongoing

Hi Keith Thanks for your kindly response and directive. On 01/19/2018 12:59 PM, Keith Busch wrote: > On Thu, Jan 18, 2018 at 06:10:02PM +0800, Jianchao Wang wrote: >> + * - When the ctrl.state is NVME_CTRL_RESETTING, the expired >> + * request should come from the previous work and we

linux-next: build failure after merge of the powerpc tree

Hi all, After merging the powerpc tree, today's linux-next build (powerpc64 allnoconfig) failed like this: arch/powerpc/kernel/mce_power.o: In function `.mce_handle_error': mce_power.c:(.text+0x5a8): undefined reference to `.hash__tlbiel_all' mce_power.c:(.text+0x6b8): undefined reference to

linux-next: build failure after merge of the powerpc tree

Hi all, After merging the powerpc tree, today's linux-next build (powerpc64 allnoconfig) failed like this: arch/powerpc/kernel/mce_power.o: In function `.mce_handle_error': mce_power.c:(.text+0x5a8): undefined reference to `.hash__tlbiel_all' mce_power.c:(.text+0x6b8): undefined reference to

Re: [PATCH 2/4] dmaengine: qcom: bam_dma: add num-channels binding for remotely controlled

On Tue, Jan 16, 2018 at 07:02:34PM +, srinivas.kandaga...@linaro.org wrote: > From: Srinivas Kandagatla > > When Linux is master of BAM, it can directly read registers to know number > of supported channels, however when its remotely controlled reading these >

Re: [PATCH 2/4] dmaengine: qcom: bam_dma: add num-channels binding for remotely controlled

On Tue, Jan 16, 2018 at 07:02:34PM +, srinivas.kandaga...@linaro.org wrote: > From: Srinivas Kandagatla > > When Linux is master of BAM, it can directly read registers to know number > of supported channels, however when its remotely controlled reading these > registers would trigger a crash

RE: [PATCH] USB TYPEC: RT1711H Type-C Chip Driver

Hi Jun, For now, RT1711H is not fully compatible with TCPCI. So the existing tcpci.c may not work for it. Best Regards, * Shu-Fan Lee Richtek Technology Corporation TEL: +886-3-5526789 #2359 FAX: +886-3-5526612 * -Original

RE: [PATCH] USB TYPEC: RT1711H Type-C Chip Driver

Hi Jun, For now, RT1711H is not fully compatible with TCPCI. So the existing tcpci.c may not work for it. Best Regards, * Shu-Fan Lee Richtek Technology Corporation TEL: +886-3-5526789 #2359 FAX: +886-3-5526612 * -Original

Re: [PATCH 1/4] dmaengine: qcom: bam_dma: make bam clk optional

On Tue, Jan 16, 2018 at 07:02:33PM +, srinivas.kandaga...@linaro.org wrote: > From: Srinivas Kandagatla > > When BAM is remotely controlled it does not sound correct to control > its clk on Linux side. Make it optional, so that its not madatory

Re: [PATCH 1/4] dmaengine: qcom: bam_dma: make bam clk optional

On Tue, Jan 16, 2018 at 07:02:33PM +, srinivas.kandaga...@linaro.org wrote: > From: Srinivas Kandagatla > > When BAM is remotely controlled it does not sound correct to control > its clk on Linux side. Make it optional, so that its not madatory s/madatory/mandatory > for remote controlled

Re: [PATCH] print kdump kernel loaded status in stack dump

On (01/18/18 10:02), Andi Kleen wrote: > Dave Young writes: > > printk("%sHardware name: %s\n", > >log_lvl, dump_stack_arch_desc_str); > > + if (kexec_crash_loaded()) > > + printk("%skdump kernel loaded\n", log_lvl); > >

Re: [PATCH] print kdump kernel loaded status in stack dump

On (01/18/18 10:02), Andi Kleen wrote: > Dave Young writes: > > printk("%sHardware name: %s\n", > >log_lvl, dump_stack_arch_desc_str); > > + if (kexec_crash_loaded()) > > + printk("%skdump kernel loaded\n", log_lvl); > > Oops/warnings are getting

Re: [PATCH] cpufreq: remove at32ap-cpufreq

On 18-01-18, 21:02, Corentin Labbe wrote: > Since AVR32 arch was removed, at32ap-cpufreq is useless. > Remove this driver. > > Signed-off-by: Corentin Labbe > --- > drivers/cpufreq/Kconfig | 10 --- > drivers/cpufreq/Makefile | 1 - >

Re: [PATCH] cpufreq: remove at32ap-cpufreq

On 18-01-18, 21:02, Corentin Labbe wrote: > Since AVR32 arch was removed, at32ap-cpufreq is useless. > Remove this driver. > > Signed-off-by: Corentin Labbe > --- > drivers/cpufreq/Kconfig | 10 --- > drivers/cpufreq/Makefile | 1 - > drivers/cpufreq/at32ap-cpufreq.c | 127

Re: [PATCH 0/7] PM /Domain/OPP: Add support to get performance state from DT

On 18-01-18, 20:24, Rafael J. Wysocki wrote: > On Thursday, January 18, 2018 7:34:04 AM CET Viresh Kumar wrote: > > On 22-12-17, 12:56, Viresh Kumar wrote: > > > Hi, > > > > > > Now that the DT bindings [1] are already Reviewed/Acked by respective > > > maintainers, here is the code to start

Re: [PATCH 0/7] PM /Domain/OPP: Add support to get performance state from DT

On 18-01-18, 20:24, Rafael J. Wysocki wrote: > On Thursday, January 18, 2018 7:34:04 AM CET Viresh Kumar wrote: > > On 22-12-17, 12:56, Viresh Kumar wrote: > > > Hi, > > > > > > Now that the DT bindings [1] are already Reviewed/Acked by respective > > > maintainers, here is the code to start

RE: [RFC] Per file OOM badness

Basically the idea is right to me. 1. But we need smaller granularity to control the contribution to OOM badness. Because when the TTM buffer resides in VRAM rather than evict to system memory, we should not take this account into badness. But I think it is not easy to implement. 2.

RE: [RFC] Per file OOM badness

Basically the idea is right to me. 1. But we need smaller granularity to control the contribution to OOM badness. Because when the TTM buffer resides in VRAM rather than evict to system memory, we should not take this account into badness. But I think it is not easy to implement. 2.

Re: [RFC PATCH] e1000e: Remove Other from EIAC.

On 2018/01/18 18:42, Shrikrishna Khare wrote: > > > On Thu, 18 Jan 2018, Benjamin Poirier wrote: > > > On 2018/01/18 15:50, Benjamin Poirier wrote: > > > It was reported that emulated e1000e devices in vmware esxi 6.5 Build > > > 7526125 do not link up after commit 4aea7a5c5e94 ("e1000e: Avoid

Re: [RFC PATCH] e1000e: Remove Other from EIAC.

On 2018/01/18 18:42, Shrikrishna Khare wrote: > > > On Thu, 18 Jan 2018, Benjamin Poirier wrote: > > > On 2018/01/18 15:50, Benjamin Poirier wrote: > > > It was reported that emulated e1000e devices in vmware esxi 6.5 Build > > > 7526125 do not link up after commit 4aea7a5c5e94 ("e1000e: Avoid

Re: [PATCH v8 5/5] document: add document for kaslr_mem

On Fri, Jan 19, 2018 at 11:53:31AM +0800, Baoquan He wrote: >On 01/19/18 at 11:36am, Chao Fan wrote: >> Signed-off-by: Chao Fan >> --- >> Documentation/admin-guide/kernel-parameters.txt | 10 ++ >> 1 file changed, 10 insertions(+) >> >> diff --git

Re: [PATCH v8 5/5] document: add document for kaslr_mem

On Fri, Jan 19, 2018 at 11:53:31AM +0800, Baoquan He wrote: >On 01/19/18 at 11:36am, Chao Fan wrote: >> Signed-off-by: Chao Fan >> --- >> Documentation/admin-guide/kernel-parameters.txt | 10 ++ >> 1 file changed, 10 insertions(+) >> >> diff --git

[RESEND PATCH v8 5/5] document: add document for kaslr_mem

Cc: linux-...@vger.kernel.org Cc: Jonathan Corbet Cc: Randy Dunlap Signed-off-by: Chao Fan --- Documentation/admin-guide/kernel-parameters.txt | 10 ++ 1 file changed, 10 insertions(+) diff --git

[RESEND PATCH v8 5/5] document: add document for kaslr_mem

Cc: linux-...@vger.kernel.org Cc: Jonathan Corbet Cc: Randy Dunlap Signed-off-by: Chao Fan --- Documentation/admin-guide/kernel-parameters.txt | 10 ++ 1 file changed, 10 insertions(+) diff --git a/Documentation/admin-guide/kernel-parameters.txt

Re: [PATCH v4 07/13] ARM: dts: rockchip: add clocks in vop iommu nodes

On Fri, Jan 19, 2018 at 1:55 PM, JeffyChen wrote: > Hi Tomasz, > > Thanks for your reply. > > > On 01/19/2018 11:23 AM, Tomasz Figa wrote: >> >> On Thu, Jan 18, 2018 at 8:52 PM, Jeffy Chen >> wrote: >>> >>> Add clocks in vop iommu nodes,

Re: [PATCH v4 07/13] ARM: dts: rockchip: add clocks in vop iommu nodes

On Fri, Jan 19, 2018 at 1:55 PM, JeffyChen wrote: > Hi Tomasz, > > Thanks for your reply. > > > On 01/19/2018 11:23 AM, Tomasz Figa wrote: >> >> On Thu, Jan 18, 2018 at 8:52 PM, Jeffy Chen >> wrote: >>> >>> Add clocks in vop iommu nodes, since we are going to control clocks in >>> rockchip iommu

Re: linux-next: build warning after merge of the crypto tree

On Fri, Jan 19, 2018 at 09:51:43AM +0530, Harsh Jain wrote: > Hi Herbert, > > It's an indentation issue. Seems checkpatch and default compile options does > not report this warning. > > How would you like to take the fix. Should I sent whole series again with fix > or only indentation patch.

Re: linux-next: build warning after merge of the crypto tree

On Fri, Jan 19, 2018 at 09:51:43AM +0530, Harsh Jain wrote: > Hi Herbert, > > It's an indentation issue. Seems checkpatch and default compile options does > not report this warning. > > How would you like to take the fix. Should I sent whole series again with fix > or only indentation patch.

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On Fri, 2018-01-19 at 10:32 +0800, Ming Lei wrote: > Now most of times both NVMe and SCSI won't return BLK_STS_RESOURCE, and > it should be DM-only which returns STS_RESOURCE so often. That's wrong at least for SCSI. See also https://marc.info/?l=linux-block=151578329417076. Bart.

Re: [RFC PATCH] blk-mq: fixup RESTART when queue becomes idle

On Fri, 2018-01-19 at 10:32 +0800, Ming Lei wrote: > Now most of times both NVMe and SCSI won't return BLK_STS_RESOURCE, and > it should be DM-only which returns STS_RESOURCE so often. That's wrong at least for SCSI. See also https://marc.info/?l=linux-block=151578329417076. Bart.

Re: [PATCH v5 29/44] ARM: da8xx: add new USB PHY clock init using common clock framework

On Friday 19 January 2018 12:13 AM, David Lechner wrote: > On 01/18/2018 09:14 AM, Sekhar Nori wrote: >> On Monday 08 January 2018 07:47 AM, David Lechner wrote: >>> +int __init da8xx_register_usb20_phy_clk(bool use_usb_refclkin) >>> +{ >>> +    struct regmap *cfgchip; >>> +    struct clk

Re: [PATCH v5 29/44] ARM: da8xx: add new USB PHY clock init using common clock framework

On Friday 19 January 2018 12:13 AM, David Lechner wrote: > On 01/18/2018 09:14 AM, Sekhar Nori wrote: >> On Monday 08 January 2018 07:47 AM, David Lechner wrote: >>> +int __init da8xx_register_usb20_phy_clk(bool use_usb_refclkin) >>> +{ >>> +    struct regmap *cfgchip; >>> +    struct clk

  1   2   3   4   5   6   7   8   9   10   >