Re: [linux-sunxi] Re: [PATCH v3 04/14] drm/sun4i: tcon: Add support for demuxing TCON output on A31

On Sat, Sep 30, 2017 at 1:35 PM, Julian Calaby wrote: > Hi Chen-Yu, > > On Fri, Sep 29, 2017 at 8:22 PM, Chen-Yu Tsai wrote: >> On Fri, Sep 29, 2017 at 6:20 PM, Maxime Ripard >> wrote: >>> On Fri, Sep 29, 2017 at

Re: [linux-sunxi] Re: [PATCH v3 04/14] drm/sun4i: tcon: Add support for demuxing TCON output on A31

On Sat, Sep 30, 2017 at 1:35 PM, Julian Calaby wrote: > Hi Chen-Yu, > > On Fri, Sep 29, 2017 at 8:22 PM, Chen-Yu Tsai wrote: >> On Fri, Sep 29, 2017 at 6:20 PM, Maxime Ripard >> wrote: >>> On Fri, Sep 29, 2017 at 08:22:56AM +, Chen-Yu Tsai wrote: On systems with 2 TCONs such as the

[PATCH V2] PCI: AER: fix deadlock in do_recovery

CPU0CPU1 - __driver_attach() device_lock(>mutex) <--- device mutex lock here driver_probe_device() pci_enable_sriov() pci_iov_add_virtfn() pci_device_add()

[PATCH V2] PCI: AER: fix deadlock in do_recovery

CPU0CPU1 - __driver_attach() device_lock(>mutex) <--- device mutex lock here driver_probe_device() pci_enable_sriov() pci_iov_add_virtfn() pci_device_add()

[PATCH] net: hns3: Fix an error handling path in 'hclge_rss_init_hw()'

If this sanity check fails, we must free 'rss_indir'. Otherwise there is a memory leak. 'goto err' as done in the other error handling paths to fix it. Fixes: 46a3df9f9718 ("net: hns3: Fix for setting rss_size incorrectly") Signed-off-by: Christophe JAILLET ---

[PATCH] net: hns3: Fix an error handling path in 'hclge_rss_init_hw()'

If this sanity check fails, we must free 'rss_indir'. Otherwise there is a memory leak. 'goto err' as done in the other error handling paths to fix it. Fixes: 46a3df9f9718 ("net: hns3: Fix for setting rss_size incorrectly") Signed-off-by: Christophe JAILLET ---

Re: [linux-sunxi] Re: [PATCH v3 04/14] drm/sun4i: tcon: Add support for demuxing TCON output on A31

Hi Chen-Yu, On Fri, Sep 29, 2017 at 8:22 PM, Chen-Yu Tsai wrote: > On Fri, Sep 29, 2017 at 6:20 PM, Maxime Ripard > wrote: >> On Fri, Sep 29, 2017 at 08:22:56AM +, Chen-Yu Tsai wrote: >>> On systems with 2 TCONs such as the A31, it is

Re: [linux-sunxi] Re: [PATCH v3 04/14] drm/sun4i: tcon: Add support for demuxing TCON output on A31

Hi Chen-Yu, On Fri, Sep 29, 2017 at 8:22 PM, Chen-Yu Tsai wrote: > On Fri, Sep 29, 2017 at 6:20 PM, Maxime Ripard > wrote: >> On Fri, Sep 29, 2017 at 08:22:56AM +, Chen-Yu Tsai wrote: >>> On systems with 2 TCONs such as the A31, it is possible to demux the >>> output of the TCONs to one

Re: [PATCH 0/7] gpio: brcmstb: improved interrupt and wake support

On 09/29/2017 08:40 PM, Doug Berger wrote: > This patch set collects a number of improvements to the GPIO driver > used by Broadcom Set-Top-Box devices. > > Primarily they are aimed at correcting problems with the interrupt > controller implementation, but they also extend the functionality for

Re: [PATCH 0/7] gpio: brcmstb: improved interrupt and wake support

On 09/29/2017 08:40 PM, Doug Berger wrote: > This patch set collects a number of improvements to the GPIO driver > used by Broadcom Set-Top-Box devices. > > Primarily they are aimed at correcting problems with the interrupt > controller implementation, but they also extend the functionality for

Re: How to verify linux-next

On Sat, Sep 30, 2017 at 09:28:09AM +0530, Pintu Kumar wrote: > I need to submit a patch to mainline which should be verified against > linux-next tree with latest API. If you want to verify a patch that you intend to submit upstream, my suggestion is to *not* use linux-next, but rather use the

Re: How to verify linux-next

On Sat, Sep 30, 2017 at 09:28:09AM +0530, Pintu Kumar wrote: > I need to submit a patch to mainline which should be verified against > linux-next tree with latest API. If you want to verify a patch that you intend to submit upstream, my suggestion is to *not* use linux-next, but rather use the

Re: [Outreachy kernel] [PATCH] Staging: rtl8723bs: Remove unnecessary comments.

On Sat, 30 Sep 2017, Shreeya Patel wrote: > On Fri, 2017-09-29 at 23:10 +0200, Julia Lawall wrote: > > > > On Sat, 30 Sep 2017, Shreeya Patel wrote: > > > > > > > > The comments regarding memset are not needed in the > > > files which have been modified since the necessary changes > > > are

Re: [Outreachy kernel] [PATCH] Staging: rtl8723bs: Remove unnecessary comments.

On Sat, 30 Sep 2017, Shreeya Patel wrote: > On Fri, 2017-09-29 at 23:10 +0200, Julia Lawall wrote: > > > > On Sat, 30 Sep 2017, Shreeya Patel wrote: > > > > > > > > The comments regarding memset are not needed in the > > > files which have been modified since the necessary changes > > > are

Re: [PATCH -tip v3 7/7] kprobes: Use synchronize_rcu_tasks() for optprobe with CONFIG_PREEMPT

On Fri, 29 Sep 2017 19:45:28 +0200 Ingo Molnar wrote: > > * Masami Hiramatsu wrote: > > > On Fri, 29 Sep 2017 09:37:55 +0200 > > Ingo Molnar wrote: > > > > > > > > * Masami Hiramatsu wrote: > > > > > > > On

Re: [PATCH -tip v3 7/7] kprobes: Use synchronize_rcu_tasks() for optprobe with CONFIG_PREEMPT

On Fri, 29 Sep 2017 19:45:28 +0200 Ingo Molnar wrote: > > * Masami Hiramatsu wrote: > > > On Fri, 29 Sep 2017 09:37:55 +0200 > > Ingo Molnar wrote: > > > > > > > > * Masami Hiramatsu wrote: > > > > > > > On Thu, 28 Sep 2017 09:22:20 +0200 > > > > Ingo Molnar wrote: > > > > > > > > > >

Re: [Outreachy kernel] [PATCH] Staging: rtl8188eu: core: Use list_entry instead of container_of

On Sat, 30 Sep 2017, Srishti Sharma wrote: > For variables of the type struct list_head* use list_entry to access > the current list element instead of using container_of. > Done using the following semantic patch by coccinelle. > > @r@ > identifier e; > struct list_head* l; > @@ > > <... when

Re: [Outreachy kernel] [PATCH] Staging: rtl8188eu: core: Use list_entry instead of container_of

On Sat, 30 Sep 2017, Srishti Sharma wrote: > For variables of the type struct list_head* use list_entry to access > the current list element instead of using container_of. > Done using the following semantic patch by coccinelle. > > @r@ > identifier e; > struct list_head* l; > @@ > > <... when

Re: [PATCH] mkiss: remove redundant check on len being zero

From: Colin King Date: Wed, 27 Sep 2017 22:45:13 +0100 > From: Colin Ian King > > The check on len is redundant as it is always greater than 1, > so just remove it and make the printk less complex. > > Detected by CoverityScan, CID#1226729

Re: [PATCH] mkiss: remove redundant check on len being zero

From: Colin King Date: Wed, 27 Sep 2017 22:45:13 +0100 > From: Colin Ian King > > The check on len is redundant as it is always greater than 1, > so just remove it and make the printk less complex. > > Detected by CoverityScan, CID#1226729 ("Logically dead code") > > Signed-off-by: Colin Ian

RE: [PATCH v15 2/5] lib/xbitmap: add xb_find_next_bit() and xb_zero()

On Monday, September 11, 2017 9:27 PM, Matthew Wilcox wrote > On Mon, Aug 28, 2017 at 06:08:30PM +0800, Wei Wang wrote: > > +/** > > + * xb_zero - zero a range of bits in the xbitmap > > + * @xb: the xbitmap that the bits reside in > > + * @start: the start of the range, inclusive > > + *

RE: [PATCH v15 2/5] lib/xbitmap: add xb_find_next_bit() and xb_zero()

On Monday, September 11, 2017 9:27 PM, Matthew Wilcox wrote > On Mon, Aug 28, 2017 at 06:08:30PM +0800, Wei Wang wrote: > > +/** > > + * xb_zero - zero a range of bits in the xbitmap > > + * @xb: the xbitmap that the bits reside in > > + * @start: the start of the range, inclusive > > + *

[PATCH v16 2/5] radix tree test suite: add tests for xbitmap

From: Matthew Wilcox Add the following tests for xbitmap: 1) single bit test: single bit set/clear/find; 2) bit range test: set/clear a range of bits and find a 0 or 1 bit in the range. Signed-off-by: Wei Wang Cc: Matthew Wilcox

[PATCH v16 2/5] radix tree test suite: add tests for xbitmap

From: Matthew Wilcox Add the following tests for xbitmap: 1) single bit test: single bit set/clear/find; 2) bit range test: set/clear a range of bits and find a 0 or 1 bit in the range. Signed-off-by: Wei Wang Cc: Matthew Wilcox Cc: Andrew Morton Cc: Michael S. Tsirkin ---

[PATCH v16 4/5] mm: support reporting free page blocks

This patch adds support to walk through the free page blocks in the system and report them via a callback function. Some page blocks may leave the free list after zone->lock is released, so it is the caller's responsibility to either detect or prevent the use of such pages. One use example of

[PATCH v16 3/5] virtio-balloon: VIRTIO_BALLOON_F_SG

Add a new feature, VIRTIO_BALLOON_F_SG, which enables the transfer of balloon (i.e. inflated/deflated) pages using scatter-gather lists to the host. The implementation of the previous virtio-balloon is not very efficient, because the balloon pages are transferred to the host one by one. Here is

[PATCH v16 4/5] mm: support reporting free page blocks

This patch adds support to walk through the free page blocks in the system and report them via a callback function. Some page blocks may leave the free list after zone->lock is released, so it is the caller's responsibility to either detect or prevent the use of such pages. One use example of

[PATCH v16 3/5] virtio-balloon: VIRTIO_BALLOON_F_SG

Add a new feature, VIRTIO_BALLOON_F_SG, which enables the transfer of balloon (i.e. inflated/deflated) pages using scatter-gather lists to the host. The implementation of the previous virtio-balloon is not very efficient, because the balloon pages are transferred to the host one by one. Here is

[PATCH v16 1/5] lib/xbitmap: Introduce xbitmap

From: Matthew Wilcox The eXtensible Bitmap is a sparse bitmap representation which is efficient for set bits which tend to cluster. It supports up to 'unsigned long' worth of bits, and this commit adds the bare bones -- xb_set_bit(), xb_clear_bit() and xb_test_bit().

[PATCH v16 1/5] lib/xbitmap: Introduce xbitmap

From: Matthew Wilcox The eXtensible Bitmap is a sparse bitmap representation which is efficient for set bits which tend to cluster. It supports up to 'unsigned long' worth of bits, and this commit adds the bare bones -- xb_set_bit(), xb_clear_bit() and xb_test_bit(). More possible

[PATCH v16 5/5] virtio-balloon: VIRTIO_BALLOON_F_CTRL_VQ

Add a new vq, ctrl_vq, to handle commands between the host and guest. With this feature, we will be able to have the control plane and data plane separated. In other words, the control related commands of each feature will be sent via the ctrl_vq, meanwhile each feature may have its own vq used as

[PATCH v16 5/5] virtio-balloon: VIRTIO_BALLOON_F_CTRL_VQ

Add a new vq, ctrl_vq, to handle commands between the host and guest. With this feature, we will be able to have the control plane and data plane separated. In other words, the control related commands of each feature will be sent via the ctrl_vq, meanwhile each feature may have its own vq used as

[PATCH v16 0/5] Virtio-balloon Enhancement

This patch series enhances the existing virtio-balloon with the following new features: 1) fast ballooning: transfer ballooned pages between the guest and host in chunks using sgs, instead of one array each time; and 2) free page block reporting: a new virtqueue to report guest free pages to the

[PATCH v16 0/5] Virtio-balloon Enhancement

This patch series enhances the existing virtio-balloon with the following new features: 1) fast ballooning: transfer ballooned pages between the guest and host in chunks using sgs, instead of one array each time; and 2) free page block reporting: a new virtqueue to report guest free pages to the

[PATCH 1/1] Drivers: hv: vmbus: Fix bugs in rescind handling

From: "K. Y. Srinivasan" This patch addresses the following bugs in the current rescind handling code: 1. Fixes a race condition where we may be invoking hv_process_channel_removal() on an already freed channel. 2. Prevents indefinite wait when rescinding sub-channels by

[PATCH 1/1] Drivers: hv: vmbus: Fix bugs in rescind handling

From: "K. Y. Srinivasan" This patch addresses the following bugs in the current rescind handling code: 1. Fixes a race condition where we may be invoking hv_process_channel_removal() on an already freed channel. 2. Prevents indefinite wait when rescinding sub-channels by correctly setting the

[PATCH 1/1] arm64: dts: rockchip: default serial for Firefly-RK3399

The Firefly-RK3399 uses serial2 with 1,500,000 baud by default for communication in U-Boot and in the vendor provided distros. So let us set the same default in the Linux kernel. Signed-off-by: Heinrich Schuchardt --- arch/arm64/boot/dts/rockchip/rk3399-firefly.dts | 4

[PATCH 1/1] arm64: dts: rockchip: default serial for Firefly-RK3399

The Firefly-RK3399 uses serial2 with 1,500,000 baud by default for communication in U-Boot and in the vendor provided distros. So let us set the same default in the Linux kernel. Signed-off-by: Heinrich Schuchardt --- arch/arm64/boot/dts/rockchip/rk3399-firefly.dts | 4 1 file changed, 4

Re: [PATCH 1/1] [tools]: android/ion: userspace test utility for ion buffer sharing

On Thu, Sep 28, 2017 at 11:46 PM, Pintu Kumar wrote: > On Thu, Sep 28, 2017 at 11:41 PM, Pintu Kumar wrote: >> On Wed, Sep 27, 2017 at 7:54 PM, Pintu Kumar wrote: >>> On Wed, Sep 27, 2017 at 12:52 AM, Laura Abbott

Re: [PATCH 1/1] [tools]: android/ion: userspace test utility for ion buffer sharing

On Thu, Sep 28, 2017 at 11:46 PM, Pintu Kumar wrote: > On Thu, Sep 28, 2017 at 11:41 PM, Pintu Kumar wrote: >> On Wed, Sep 27, 2017 at 7:54 PM, Pintu Kumar wrote: >>> On Wed, Sep 27, 2017 at 12:52 AM, Laura Abbott wrote: On 09/26/2017 11:08 AM, Pintu Agarwal wrote: > > This is a

Re: How to verify linux-next

Thanks Mr. Tso for your reply. Please find my reply inline. On Sat, Sep 30, 2017 at 3:20 AM, Theodore Ts'o wrote: > On Fri, Sep 29, 2017 at 07:56:41PM +0530, Pintu Kumar wrote: >> BTW, I am more interested in my another query about QEMU arm. >> This will be much quicker and easy

Re: How to verify linux-next

Thanks Mr. Tso for your reply. Please find my reply inline. On Sat, Sep 30, 2017 at 3:20 AM, Theodore Ts'o wrote: > On Fri, Sep 29, 2017 at 07:56:41PM +0530, Pintu Kumar wrote: >> BTW, I am more interested in my another query about QEMU arm. >> This will be much quicker and easy for me. >> But

Hung Task Linux 4.13-rc7 Reiserfs

Hi, I am fuzzing the kernel 4.13-rc7 with Syzkaller with Reiserfs. I am getting the following crash: INFO: task kworker/0:3:1103 blocked for more than 120 seconds. Here is the full stack trace. I noticed that there are a few tasks holding a sbi->lock. Below are a report and a log of all the

Hung Task Linux 4.13-rc7 Reiserfs

Hi, I am fuzzing the kernel 4.13-rc7 with Syzkaller with Reiserfs. I am getting the following crash: INFO: task kworker/0:3:1103 blocked for more than 120 seconds. Here is the full stack trace. I noticed that there are a few tasks holding a sbi->lock. Below are a report and a log of all the

[PATCH 2/7] gpio: brcmstb: release the bgpio lock during irq handlers

The basic memory-mapped GPIO controller lock must be released before calling the registered GPIO interrupt handlers to allow the interrupt handlers to access the hardware. Otherwise, the hardware accesses will deadlock when they attempt to grab the lock. Since the lock is only needed to protect

[PATCH 0/7] gpio: brcmstb: improved interrupt and wake support

This patch set collects a number of improvements to the GPIO driver used by Broadcom Set-Top-Box devices. Primarily they are aimed at correcting problems with the interrupt controller implementation, but they also extend the functionality for waking on GPIO interrupts. Doug Berger (7): gpio:

[PATCH 2/7] gpio: brcmstb: release the bgpio lock during irq handlers

The basic memory-mapped GPIO controller lock must be released before calling the registered GPIO interrupt handlers to allow the interrupt handlers to access the hardware. Otherwise, the hardware accesses will deadlock when they attempt to grab the lock. Since the lock is only needed to protect

[PATCH 0/7] gpio: brcmstb: improved interrupt and wake support

This patch set collects a number of improvements to the GPIO driver used by Broadcom Set-Top-Box devices. Primarily they are aimed at correcting problems with the interrupt controller implementation, but they also extend the functionality for waking on GPIO interrupts. Doug Berger (7): gpio:

Re: [PATCH] initramfs: Fix initramfs rebuilds w/ compression after disabling

On 09/29/2017 08:39 PM, Florian Fainelli wrote: > This is a follow-up to commit 57ddfdaa9a72 ("initramfs: fix disabling of > initramfs (and its compression)"). This particular commit fixed the use case > where we build the kernel with an initramfs with no compression, and then we > build the

[PATCH 5/7] gpio: brcmstb: enable masking of interrupts when changing type

Mask the GPIO interrupt while its type is being changed, just in case it can prevent a spurious interrupt. Signed-off-by: Doug Berger --- drivers/gpio/gpio-brcmstb.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpio/gpio-brcmstb.c

Re: [PATCH] initramfs: Fix initramfs rebuilds w/ compression after disabling

On 09/29/2017 08:39 PM, Florian Fainelli wrote: > This is a follow-up to commit 57ddfdaa9a72 ("initramfs: fix disabling of > initramfs (and its compression)"). This particular commit fixed the use case > where we build the kernel with an initramfs with no compression, and then we > build the

[PATCH 5/7] gpio: brcmstb: enable masking of interrupts when changing type

Mask the GPIO interrupt while its type is being changed, just in case it can prevent a spurious interrupt. Signed-off-by: Doug Berger --- drivers/gpio/gpio-brcmstb.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpio/gpio-brcmstb.c b/drivers/gpio/gpio-brcmstb.c

[PATCH 6/7] gpio: brcmstb: consolidate interrupt domains

The GPIOLIB IRQ chip helpers were very appealing, but badly broke the 1:1 mapping between a GPIO controller's device_node and its interrupt domain. This commit consolidates the per bank irq domains to a version where we have one larger interrupt domain per GPIO controller instance spanning

[PATCH 1/7] gpio: brcmstb: allow all instances to be wakeup sources

This commit allows a wakeup parent interrupt to be shared between instances. It also removes the redundant can_wake member of the private data structure by using whether the parent_wake_irq has been defined to indicate that the GPIO device can wake. Fixes: 19a7b6940b78 ("gpio: brcmstb: Add

[PATCH 7/7] gpio: brcmstb: implement suspend/resume/shutdown

This commit corrects problems with the previous wake implementation by implementing suspend and resume power management operations and the driver shutdown operation. Wake masks are used to keep track of which GPIO should wake the device. On suspend the GPIO state is saved and the possible wakeup

[PATCH 3/7] gpio: brcmstb: switch to handle_level_irq flow

Reading and writing the gpio bank status register each time a pending interrupt bit is serviced could cause new pending bits to be cleared without servicing the associated interrupts. By using the handle_level_irq flow instead of the handle_simple_irq flow we get proper handling of interrupt

[PATCH 6/7] gpio: brcmstb: consolidate interrupt domains

The GPIOLIB IRQ chip helpers were very appealing, but badly broke the 1:1 mapping between a GPIO controller's device_node and its interrupt domain. This commit consolidates the per bank irq domains to a version where we have one larger interrupt domain per GPIO controller instance spanning

[PATCH 1/7] gpio: brcmstb: allow all instances to be wakeup sources

This commit allows a wakeup parent interrupt to be shared between instances. It also removes the redundant can_wake member of the private data structure by using whether the parent_wake_irq has been defined to indicate that the GPIO device can wake. Fixes: 19a7b6940b78 ("gpio: brcmstb: Add

[PATCH 7/7] gpio: brcmstb: implement suspend/resume/shutdown

This commit corrects problems with the previous wake implementation by implementing suspend and resume power management operations and the driver shutdown operation. Wake masks are used to keep track of which GPIO should wake the device. On suspend the GPIO state is saved and the possible wakeup

[PATCH 3/7] gpio: brcmstb: switch to handle_level_irq flow

Reading and writing the gpio bank status register each time a pending interrupt bit is serviced could cause new pending bits to be cleared without servicing the associated interrupts. By using the handle_level_irq flow instead of the handle_simple_irq flow we get proper handling of interrupt

[PATCH 4/7] gpio: brcmstb: correct the configuration of level interrupts

This commit corrects a bug when configuring the GPIO hardware for IRQ_TYPE_LEVEL_LOW and IRQ_TYPE_LEVEL_HIGH interrupt types. The hardware is now correctly configured to support those types. Fixes: 19a7b6940b78 ("gpio: brcmstb: Add interrupt and wakeup source support") Signed-off-by: Doug Berger

[PATCH 4/7] gpio: brcmstb: correct the configuration of level interrupts

This commit corrects a bug when configuring the GPIO hardware for IRQ_TYPE_LEVEL_LOW and IRQ_TYPE_LEVEL_HIGH interrupt types. The hardware is now correctly configured to support those types. Fixes: 19a7b6940b78 ("gpio: brcmstb: Add interrupt and wakeup source support") Signed-off-by: Doug Berger

Re: KVM PV (was: Re: [PATCH v2 2/2] x86/lguest: remove lguest support)

- Lai Jiangshan ha scritto: > On Sat, Sep 30, 2017 at 12:39 AM, Paolo Bonzini wrote: > > On 29/09/2017 17:47, Lai Jiangshan wrote: > >> Hello, all > >> > >> An interesting (at least to me) thinking came up to me when I found > >> that the

[PATCH] initramfs: Fix initramfs rebuilds w/ compression after disabling

This is a follow-up to commit 57ddfdaa9a72 ("initramfs: fix disabling of initramfs (and its compression)"). This particular commit fixed the use case where we build the kernel with an initramfs with no compression, and then we build the kernel with no initramfs. Now this still left us with the

Re: KVM PV (was: Re: [PATCH v2 2/2] x86/lguest: remove lguest support)

- Lai Jiangshan ha scritto: > On Sat, Sep 30, 2017 at 12:39 AM, Paolo Bonzini wrote: > > On 29/09/2017 17:47, Lai Jiangshan wrote: > >> Hello, all > >> > >> An interesting (at least to me) thinking came up to me when I found > >> that the lguest was removed. But I don't have enough

[PATCH] initramfs: Fix initramfs rebuilds w/ compression after disabling

This is a follow-up to commit 57ddfdaa9a72 ("initramfs: fix disabling of initramfs (and its compression)"). This particular commit fixed the use case where we build the kernel with an initramfs with no compression, and then we build the kernel with no initramfs. Now this still left us with the

[PATCH v1 9/9] early pt: early start intel processor trace in early boot

enable intel PT to trace kernel boot && runtime Signed-off-by: Luming Yu 0009-start-early-intel-processor-trace-in-early-boot.patch Description: Binary data

[PATCH v1 9/9] early pt: early start intel processor trace in early boot

enable intel PT to trace kernel boot && runtime Signed-off-by: Luming Yu 0009-start-early-intel-processor-trace-in-early-boot.patch Description: Binary data

[PATCH v1 8/9] early pt: enable cyc packet

enable CYC packet Signed-off-by: Luming Yu 0008-early-pt-enable-cyc-packet.patch Description: Binary data

[PATCH v1 8/9] early pt: enable cyc packet

enable CYC packet Signed-off-by: Luming Yu 0008-early-pt-enable-cyc-packet.patch Description: Binary data

[PATCH v1 7/9] early pt: enable early pt psb packet

enable PSB packet Signed-off-by: Luming Yu 0007-enable-early-pt-psb-packet.patch Description: Binary data

[PATCH v1 7/9] early pt: enable early pt psb packet

enable PSB packet Signed-off-by: Luming Yu 0007-enable-early-pt-psb-packet.patch Description: Binary data

[PATCH v1 6/9] early pt: enable mtc freq packet

enable mtc freq packet Signed-off-by: Luming Yu 0006-early-pt-enable-mtc-freq-packet.patch Description: Binary data

[PATCH v1 6/9] early pt: enable mtc freq packet

enable mtc freq packet Signed-off-by: Luming Yu 0006-early-pt-enable-mtc-freq-packet.patch Description: Binary data

[PATCH v1 5/9] early pt: basic addr pair filter support

(addr0 && addr1) Signed-off-by: Luming Yu 0005-early-pt-basic-addr-pair-filter-support-addr0-addr1.patch Description: Binary data

[PATCH v1 5/9] early pt: basic addr pair filter support

(addr0 && addr1) Signed-off-by: Luming Yu 0005-early-pt-basic-addr-pair-filter-support-addr0-addr1.patch Description: Binary data

[PATCH v1 4/9] early pt: boot option early_pt_buf_len

for early pt buffer size setup Signed-off-by: Luming Yu 0004-boot-option-early_pt_buf_len-for-early-pt-buffer-siz.patch Description: Binary data

[PATCH v1 4/9] early pt: boot option early_pt_buf_len

for early pt buffer size setup Signed-off-by: Luming Yu 0004-boot-option-early_pt_buf_len-for-early-pt-buffer-siz.patch Description: Binary data

[PATCH v1 3/9] early pt: boot option to enable early pt

boot option "early_pt" to enable early pt Signed-off-by: Luming Yu 0003-boot-option-early_pt-to-enable-early-pt.patch Description: Binary data

[PATCH v1 3/9] early pt: boot option to enable early pt

boot option "early_pt" to enable early pt Signed-off-by: Luming Yu 0003-boot-option-early_pt-to-enable-early-pt.patch Description: Binary data

[PATCH v1 2/9] early pt: kconfig disable ftrace by default

Recommend to disable ftrace for pt by default though pt works perfectly for tracing ftrace code Signed-off-by: Luming Yu 0002-Recommend-to-disable-ftrace-for-pt-by-default.patch Description: Binary data

[PATCH v1 2/9] early pt: kconfig disable ftrace by default

Recommend to disable ftrace for pt by default though pt works perfectly for tracing ftrace code Signed-off-by: Luming Yu 0002-Recommend-to-disable-ftrace-for-pt-by-default.patch Description: Binary data

[PATCH v1 1/9] early pt: Basic support for early intel processor trace

with zero dependencies on other technologies in linux kernel, 1.Per cpu dump for basic block level code analysis 2.I can trace any code including myself right after it's enabled Signed-off-by: Luming Yu --- arch/x86/events/Kconfig | 6 +

[PATCH v1 1/9] early pt: Basic support for early intel processor trace

with zero dependencies on other technologies in linux kernel, 1.Per cpu dump for basic block level code analysis 2.I can trace any code including myself right after it's enabled Signed-off-by: Luming Yu --- arch/x86/events/Kconfig | 6 + arch/x86/events/intel/Makefile | 1 +

[PATCH v1 0/9] early pt: intel processor trace early support

we can use intel processor trace facility since cpu power on so we can try this patch to do early code analysis at basic block level. The basic usage is as below: #./sptdump #./sptdecode --pt ptout.0 -e ../linux-test/vmlinux | less [+ 10] ext4_getblk+159 ->

[PATCH v1 0/9] early pt: intel processor trace early support

we can use intel processor trace facility since cpu power on so we can try this patch to do early code analysis at basic block level. The basic usage is as below: #./sptdump #./sptdecode --pt ptout.0 -e ../linux-test/vmlinux | less [+ 10] ext4_getblk+159 ->

Re: [RFC V2] printk: add warning while drop partial text in msg

On (09/27/17 21:59), pierre kuo wrote: [..] > We use the example in this mail since we try to collect the message at > different places in our driver. > And batch to printk for saving individual output time and group > message together. I see. well, printk batching (buffered mode) is a bit tricky

Re: [RFC V2] printk: add warning while drop partial text in msg

On (09/27/17 21:59), pierre kuo wrote: [..] > We use the example in this mail since we try to collect the message at > different places in our driver. > And batch to printk for saving individual output time and group > message together. I see. well, printk batching (buffered mode) is a bit tricky

Re: [PATCH v1 3/5] dt-bindings: Add DT bindings for NVIDIA Tegra AHB DMA controller

On 29.09.2017 22:30, Stephen Warren wrote: > On 09/27/2017 02:34 AM, Jon Hunter wrote: >> >> On 27/09/17 02:57, Dmitry Osipenko wrote: >>> On 26.09.2017 17:50, Jon Hunter wrote: On 26/09/17 00:22, Dmitry Osipenko wrote: > Document DT bindings for NVIDIA Tegra AHB DMA controller that

Re: [PATCH v1 3/5] dt-bindings: Add DT bindings for NVIDIA Tegra AHB DMA controller

On 29.09.2017 22:30, Stephen Warren wrote: > On 09/27/2017 02:34 AM, Jon Hunter wrote: >> >> On 27/09/17 02:57, Dmitry Osipenko wrote: >>> On 26.09.2017 17:50, Jon Hunter wrote: On 26/09/17 00:22, Dmitry Osipenko wrote: > Document DT bindings for NVIDIA Tegra AHB DMA controller that

Re: [PATCH 0/6] Cache coherent device memory (CDM) with HMM v5

On 2017/9/27 0:16, Jerome Glisse wrote: > On Tue, Sep 26, 2017 at 05:56:26PM +0800, Bob Liu wrote: >> On Tue, Sep 12, 2017 at 7:36 AM, Jerome Glisse wrote: >>> On Sun, Sep 10, 2017 at 07:22:58AM +0800, Bob Liu wrote: On Wed, Sep 6, 2017 at 3:36 AM, Jerome Glisse

Re: [PATCH 0/6] Cache coherent device memory (CDM) with HMM v5

On 2017/9/27 0:16, Jerome Glisse wrote: > On Tue, Sep 26, 2017 at 05:56:26PM +0800, Bob Liu wrote: >> On Tue, Sep 12, 2017 at 7:36 AM, Jerome Glisse wrote: >>> On Sun, Sep 10, 2017 at 07:22:58AM +0800, Bob Liu wrote: On Wed, Sep 6, 2017 at 3:36 AM, Jerome Glisse wrote: > On Thu, Jul 20,

[PATCHv3 7/7] checkpatch: add pF/pf deprecation warning

We deprecated '%pF/%pf' printk specifiers, since '%pS/%ps' is now smart enough to handle function pointer dereference on platforms where such dereference is required. checkpatch warning example: WARNING: Deprecated vsprintf pointer extension '%pF' - use %pS instead Signed-off-by: Sergey

[PATCHv3 7/7] checkpatch: add pF/pf deprecation warning

We deprecated '%pF/%pf' printk specifiers, since '%pS/%ps' is now smart enough to handle function pointer dereference on platforms where such dereference is required. checkpatch warning example: WARNING: Deprecated vsprintf pointer extension '%pF' - use %pS instead Signed-off-by: Sergey

[PATCHv3 6/7] symbol lookup: use new kernel and module dereference functions

Call appropriate function descriptor dereference ARCH callbacks: - dereference_kernel_function_descriptor() if the pointer is a kernel symbol; - dereference_module_function_descriptor() if the pointer is a module symbol. This patch also removes dereference_function_descriptor() from

[PATCHv3 5/7] parisc64: Add .opd based function descriptor dereference

We are moving towards separate kernel and module function descriptor dereference callbacks. This patch enables it for parisc64. For pointers that belong to the kernel - Added __start_opd and __end_opd pointers, to track the kernel .opd section address range; - Added

[PATCHv3 6/7] symbol lookup: use new kernel and module dereference functions

Call appropriate function descriptor dereference ARCH callbacks: - dereference_kernel_function_descriptor() if the pointer is a kernel symbol; - dereference_module_function_descriptor() if the pointer is a module symbol. This patch also removes dereference_function_descriptor() from

[PATCHv3 5/7] parisc64: Add .opd based function descriptor dereference

We are moving towards separate kernel and module function descriptor dereference callbacks. This patch enables it for parisc64. For pointers that belong to the kernel - Added __start_opd and __end_opd pointers, to track the kernel .opd section address range; - Added

[PATCHv3 4/7] powerpc64: Add .opd based function descriptor dereference

We are moving towards separate kernel and module function descriptor dereference callbacks. This patch enables it for powerpc64. For pointers that belong to the kernel - Added __start_opd and __end_opd pointers, to track the kernel .opd section address range; - Added

[PATCHv3 2/7] sections: split dereference_function_descriptor()

There are two format specifiers to print out a pointer in symbolic format: '%pS/%ps' and '%pF/%pf'. On most architectures, the two mean exactly the same thing, but some architectures (ia64, ppc64, parisc64) use an indirect pointer for C function pointers, where the function pointer points to a

  1   2   3   4   5   6   7   8   9   10   >