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
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
CPU0CPU1
-
__driver_attach()
device_lock(>mutex) <--- device mutex lock here
driver_probe_device()
pci_enable_sriov()
pci_iov_add_virtfn()
pci_device_add()
CPU0CPU1
-
__driver_attach()
device_lock(>mutex) <--- device mutex lock here
driver_probe_device()
pci_enable_sriov()
pci_iov_add_virtfn()
pci_device_add()
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
---
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
---
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
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
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
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
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
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
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
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
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
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:
> > > >
> > > > >
>
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
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
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
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
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
> > + *
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
> > + *
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
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
---
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
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
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
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
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().
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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:
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
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:
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
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
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
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
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
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
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
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
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
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
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
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
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
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
- 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
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
- 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
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
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
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
enable CYC packet
Signed-off-by: Luming Yu
0008-early-pt-enable-cyc-packet.patch
Description: Binary data
enable CYC packet
Signed-off-by: Luming Yu
0008-early-pt-enable-cyc-packet.patch
Description: Binary data
enable PSB packet
Signed-off-by: Luming Yu
0007-enable-early-pt-psb-packet.patch
Description: Binary data
enable PSB packet
Signed-off-by: Luming Yu
0007-enable-early-pt-psb-packet.patch
Description: Binary data
enable mtc freq packet
Signed-off-by: Luming Yu
0006-early-pt-enable-mtc-freq-packet.patch
Description: Binary data
enable mtc freq packet
Signed-off-by: Luming Yu
0006-early-pt-enable-mtc-freq-packet.patch
Description: Binary data
(addr0 && addr1)
Signed-off-by: Luming Yu
0005-early-pt-basic-addr-pair-filter-support-addr0-addr1.patch
Description: Binary data
(addr0 && addr1)
Signed-off-by: Luming Yu
0005-early-pt-basic-addr-pair-filter-support-addr0-addr1.patch
Description: Binary data
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
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
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
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
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
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
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 +
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 +
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 ->
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 ->
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
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
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
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
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
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,
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
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
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
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
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
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
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
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 - 100 of 1238 matches
Mail list logo