User-space normally keeps the node alive when creating a transaction
since it has a reference to the target. The local strong ref keeps it
alive if the sending process dies before the target process processes
the transaction. If the source process is malicious or has a reference
counting bug, this
On 09/29/2017 07:19 AM, Borislav Petkov wrote:
...
This one was in the Part1 set, right? It landed here for whatever
reason...
Part1 is based on tip/master and Part2 is based on kvm/master.
With the current division, we should be able to compile and run part1
and part2 independently. This
Use the device properties (that can be provided by ACPI systems
as well as non ACPI systems) instead of device tree properties
(that are not provided ACPI systems). This required some minor
code restructuring.
Signed-off-by: Rajat Jain
---
I don't think its a big deal, but just FYI, this changes
On 09/26, Dong Aisheng wrote:
> 'clock-names' property is optinal in DT, so of_clk_bulk_get() is introduced
s/optinal/optional/
> here to handle this for DT users without 'clock-names' specified.
>
> Cc: Stephen Boyd
> Cc: Michael Turquette
> Cc: Russell King
> Reported-by: Shawn Guo
> Signe
Noticed these don't seem to be in 4.14/scsi-queue
On Tue, Aug 29, 2017 at 6:45 PM, Martin K. Petersen
wrote:
>
> Chris,
>
>> Looks good to me, fixes up the code given that the comment there about
>> calling iscsi_remove_session wasn't being followed.
>
> Applied these two to 4.14/scsi-queue.
>
>
On Thu, Sep 28, 2017 at 09:36:37PM +0200, Martin Wilck wrote:
> By using device_add_disk_with_groups(), we can avoid the race
> condition with udev rule processing, because no udev event will
> be triggered before all attributes are available.
>
> Signed-off-by: Martin Wilck
Looks good.
Reviewe
On Thu, Sep 28, 2017 at 09:36:36PM +0200, Martin Wilck wrote:
> In the NVME subsystem, we're seeing a race condition with udev where
> device_add_disk() is called (which triggers an "add" uevent), and a
> sysfs attribute group is added to the disk device afterwards.
> If udev rules access these att
On Fri, Sep 22, 2017 at 11:43 AM, Dawid Ciezarkiewicz
wrote:
> On Thu, Sep 21, 2017 at 12:14 PM, Ram Pai wrote:
>> Here is a patch that accomplishes the job. tested to work with
>> some simple use cases. check if this works for you. If it does
>> than we will have to think through all the edge c
The mem_encrypt=on activates both SME and SEV. Add a new argument to disable
the SEV and allow SME. The argument can be useful when SEV has issues and
we want to disable it.
early_detect_mem_encrypt() [cpu/amd.com] will need to know the state of
the mem_encrypt= argument. Since early_detect_mem_en
On 09/29/2017 01:58 PM, Josh Poimboeuf wrote:
On Fri, Sep 29, 2017 at 01:38:43PM -0700, Guenter Roeck wrote:
On Fri, Sep 29, 2017 at 01:00:56PM -0700, Guenter Roeck wrote:
Hi Josh,
when trying to compile an image with KCFLAGS="-frecord-gcc-switches",
I get the folllowing build warning/error.
From: Mahesh Bandewar
Add a sysctl variable kernel.controlled_userns_caps_whitelist. This
takes input as capability mask expressed as two comma separated hex
u32 words. The mask, however, is stored in kernel as kernel_cap_t type.
Any capabilities that are not part of this mask will be controlled
From: Mahesh Bandewar
[Same as the previous RFC series sent on 9/21]
TL;DR version
-
Creating a sandbox environment with namespaces is challenging
considering what these sandboxed processes can engage into. e.g.
CVE-2017-6074, CVE-2017-7184, CVE-2017-7308 etc. just to name few.
Curre
From: Mahesh Bandewar
With this new notion of "controlled" user-namespaces, the controlled
user-namespaces are marked at the time of their creation while the
capabilities of processes that belong to them are controlled using the
global mask.
Init-user-ns is always uncontrolled and a process that
On 09/28/2017 08:09 PM, Jens Axboe wrote:
> On 09/25/2017 11:35 AM, Jan Kara wrote:
>> On Thu 21-09-17 10:00:25, Jens Axboe wrote:
>>> On 09/21/2017 09:36 AM, Jens Axboe wrote:
> But more importantly once we are not guaranteed that we only have
> a single global wb_writeback_work per bdi_wr
nst undefined symbol 'abort'
The function 'abort' was never defined for the m32r architecture.
Create 'abort' as is done in other arch like 'arm' and 'unicore32'.
Signed-off-by: Sudip Mukherjee
---
The build log of next-20170929 is at:
https://tr
On Sat, Sep 30, 2017 at 12:01 AM, Michael S. Tsirkin wrote:
> intel idle driver does not DTRT when running within a VM:
> when going into a deep power state, the right thing to
> do is to exit to hypervisor rather than to keep polling
> within guest using mwait.
>
> Currently the solution is just
On Fri, Sep 29, 2017 at 07:40:15PM +, Ruhl, Michael J wrote:
> > -Original Message-
> > From: dan.j.willi...@gmail.com [mailto:dan.j.willi...@gmail.com] On
> > Behalf Of Dan Williams
> > Sent: Friday, September 29, 2017 3:37 PM
> > To: Dmitry Torokhov
> > Cc: Greg Kroah-Hartman ; Tejun
Hi Andi,
On Sat, Sep 30, 2017 at 05:38:28AM +0900, Andi Shyti wrote:
> Commit 57b8ff070f98 ("driver core: add devm_device_add_group()
> and friends") has added the the managed version for creating
> sysfs group files.
>
> Use devm_device_add_group instead of sysfs_create_group and
> remove the re
On Sat, Sep 30, 2017 at 05:38:33AM +0900, Andi Shyti wrote:
> Commit 57b8ff070f98 ("driver core: add devm_device_add_group()
> and friends") has added the the managed version for creating
> sysfs group files.
>
> Use devm_device_add_group instead of sysfs_create_group and
> remove the action that
On Sat, Sep 30, 2017 at 05:38:35AM +0900, Andi Shyti wrote:
> Commit 57b8ff070f98 ("driver core: add devm_device_add_group()
> and friends") has added the the managed version for creating
> sysfs group files.
>
> Use devm_device_add_group instead of sysfs_create_group and
> remove the action that
On Sat, Sep 30, 2017 at 05:38:36AM +0900, Andi Shyti wrote:
> Commit 57b8ff070f98 ("driver core: add devm_device_add_group()
> and friends") has added the the managed version for creating
> sysfs group files.
>
> Use devm_device_add_group instead of sysfs_create_group and
> remove the action that
On Sat, Sep 30, 2017 at 05:38:37AM +0900, Andi Shyti wrote:
> Commit 57b8ff070f98 ("driver core: add devm_device_add_group()
> and friends") has added the the managed version for creating
> sysfs group files.
>
> Use devm_device_add_group instead of sysfs_create_group and
> remove the action that
From: Rafael J. Wysocki
It sometimes is useful to know what power states the kernel thinks
it puts PCI devices into during system suspend, so add a dev_dbg()
statement for that.
Signed-off-by: Rafael J. Wysocki
---
drivers/pci/pci-driver.c |3 +++
1 file changed, 3 insertions(+)
Index: li
On Sat, Sep 30, 2017 at 05:38:39AM +0900, Andi Shyti wrote:
> Commit 57b8ff070f98 ("driver core: add devm_device_add_group()
> and friends") has added the the managed version for creating
> sysfs group files.
>
> Use devm_device_add_group instead of sysfs_create_group and
> remove the relative sys
On Sat, Sep 30, 2017 at 05:38:32AM +0900, Andi Shyti wrote:
> Commit 57b8ff070f98 ("driver core: add devm_device_add_group()
> and friends") has added the the managed version for creating
> sysfs group files.
>
> Use devm_device_add_group instead of sysfs_create_group and
> remove the relative sys
On Fri, Sep 29, 2017 at 04:43:39PM +, Paul E. McKenney wrote:
> On Fri, Sep 29, 2017 at 04:53:57PM +0200, Paolo Bonzini wrote:
> > On 29/09/2017 13:01, Boqun Feng wrote:
> > > Sasha Levin reported a WARNING:
> > >
> > > | WARNING: CPU: 0 PID: 6974 at kernel/rcu/tree_plugin.h:329
> > > | rcu_pr
On Sat, Sep 30, 2017 at 05:38:38AM +0900, Andi Shyti wrote:
> Commit 57b8ff070f98 ("driver core: add devm_device_add_group()
> and friends") has added the the managed version for creating
> sysfs group files.
>
> Use devm_device_add_group instead of sysfs_create_group and
> remove the relative sys
On Sat, Sep 30, 2017 at 05:38:34AM +0900, Andi Shyti wrote:
> Commit 57b8ff070f98 ("driver core: add devm_device_add_group()
> and friends") has added the the managed version for creating
> sysfs group files.
>
> Use devm_device_add_group instead of sysfs_create_group and
> remove the relative sys
On Sat, Sep 30, 2017 at 05:38:30AM +0900, Andi Shyti wrote:
> Commit 57b8ff070f98 ("driver core: add devm_device_add_group()
> and friends") has added the the managed version for creating
> sysfs group files.
>
> Use devm_device_add_group instead of sysfs_create_group and
> remove the relative sys
On Sat, Sep 30, 2017 at 05:38:31AM +0900, Andi Shyti wrote:
> Commit 57b8ff070f98 ("driver core: add devm_device_add_group()
> and friends") has added the the managed version for creating
> sysfs group files.
>
> Use devm_device_add_group instead of sysfs_create_group.
>
> CC: Nick Dyer
> Signed
On Sat, Sep 30, 2017 at 05:38:29AM +0900, Andi Shyti wrote:
> Commit 57b8ff070f98 ("driver core: add devm_device_add_group()
> and friends") has added the the managed version for creating
> sysfs group files.
>
> Use devm_device_add_group instead of sysfs_create_group and
> remove the action that
Hello,
I have tried to build the latest master and got the following error:
42sh> make O=~/works/linux-build/aarch64-4k -C ~/works/linux
make: Entering directory '/home/julgra01/works/linux'
Mak
The function tcphy_phy_init() could return an error but the callers
weren't checking the return value. They should. In at least one case
while testing I saw the message "wait pma ready timeout" which
indicates that tcphy_phy_init() really could return an error and we
should account for it.
Signe
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 knowledge
>> to find out the answer nor energy to imple
Hi Rajat,
On Fri, Sep 29, 2017 at 03:44:41PM -0700, Rajat Jain wrote:
> Use the device properties (that can be provided by ACPI systems
> as well as non ACPI systems) instead of device tree properties
> (that are not provided ACPI systems). This required some minor
> code restructuring.
>
> Signe
2017-09-30 8:59 GMT+09:00 Julien Grall :
> Hello,
>
> I have tried to build the latest master and got the following error:
>
> 42sh> make O=~/works/linux-build/aarch64-4k -C ~/works/linux
> make: Entering directory '/home/julgra01/works/linux'
> Makefile:135: *** failed to create output directory
Hi, Colin
On 2017/9/30 3:51, Colin King wrote:
> From: Colin Ian King
>
> pointer ndev is being dereferenced with the call to netif_running
> before it is being null checked. Re-order the code to only dereference
> ndev after it has been null checked.
Thanks for fixing it.
>
> Detected by Co
Thanks! This fixes a warning I was seeing with Clang:
drivers/char/tpm/tpm.h:560:15: warning: duplicate 'inline' declaration
specifier [-Wduplicate-decl-specifier]
On Fri, Sep 29, 2017 at 10:17 AM, Jarkko Sakkinen
wrote:
> On Tue, Sep 26, 2017 at 01:58:57PM +, Ruben Roy wrote:
>> This commit
On Wed, Sep 27, 2017 at 11:02:14PM -0500, Mario Limonciello wrote:
> The driver currently uses an SMI interface which grants direct access
> to physical memory to the firmware SMM methods via a pointer.
>
> Now add a WMI-ACPI interface that is detected by WMI probe and preferred
> over the SMI int
For variables that have type struct list_head* use list_entry to
access current list element instead of using container_of.
Done using the following semantic patch by coccinelle.
@r@
identifier e;
struct list_head* l;
@@
<... when != l == NULL
l;
...>
(
e=
-container_of
+list_entry
(
..
On 09/29/2017 01:46 PM, Josh Poimboeuf wrote:
On Fri, Sep 29, 2017 at 01:00:56PM -0700, Guenter Roeck wrote:
Hi Josh,
when trying to compile an image with KCFLAGS="-frecord-gcc-switches",
I get the folllowing build warning/error.
make allmodconfig
KCFLAGS="-frecord-gcc-switches" make arch/x86/
If "make rpm-pkg" or "make binrpm-pkg" is run with -j[jobs] option,
the following warning message is displayed.
warning: jobserver unavailable: using -j1. Add '+' to parent make rule.
Follow the suggestion.
Signed-off-by: Masahiro Yamada
---
scripts/package/Makefile | 4 ++--
1 file change
The sysfs attributes in_intensity0_thresh_period and
in_proximity0_thresh_period are currently directly created by the driver.
This patch migrates the creation of these sysfs attributes from the driver
to using the IIO core via iio_event_spec.
Signed-off-by: Brian Masney
---
drivers/staging/iio/
This patch set converts several sysfs attributes from directly being
created by the driver to be created by iio_chan_spec and iio_event_spec.
There is also a patch to shorten the length of a variable to fix an
issue that I encountered with some lines that were over 80 characters
with this refactori
The length of the 'tsl2x7x_settings' variable within the tsl2X7X_chip
structure makes some of the line lengths greater than 80 characters for
upcoming patches. This patch shortens the name of the 'tsl2x7x_settings'
variable in this structure to just 'settings' to improve code
readability.
Signed-o
The repeat of echo is unreadable. The here-document is a well-known
device for such scripts. One difficulty is we have a bunch of PREBUILT
conditionals that would split the here-document.
My idea is to add "$S" annotatation to lines only for the source package
spec file, then post-process it by
The driver explicitly creates the in_illuminance0_integration_time sysfs
attribute outside the IIO core. This attribute is available in the IIO
core so this patches migrates the attribute to be created by
the iio_chan_spec.
Signed-off-by: Brian Masney
---
Changes since v1 (Jul 9 2017):
- Use MIN_
This conditional was added by commit 1a0f3d422bb9 ("kbuild: fix
make rpm for powerpc"). Its git-log explains the default kernel
image is zImage, but obviously the current arch/powerpc/Makefile
does not set KBUILD_IMAGE, so the image file is actually vmlinux.
Moreover, since commit 09549aa1baa9 ("
The spec file always passes %{?_smp_mflags}, but we have two
problems here.
[1] "make -jN rpm-pkg" emits the following warning message:
make[2]: warning: -jN forced in submake: disabling jobserver mode.
[2] We can not specify the number of jobs that run in parallel.
Whether we give -jN o
$RPM_BUILD_ROOT must be escaped to prevent shell from expanding it
when generating the spec file.
%{build_root} is more readable than \$RPM_BUILD_ROOT.
Signed-off-by: Masahiro Yamada
---
scripts/package/mkspec | 32
1 file changed, 16 insertions(+), 16 deletion
When CONFIG_MODULES is disabled, make rpm-pkg / binrpm-pkg fails
with the following message:
The present kernel configuration has modules disabled.
Type 'make config' and enable loadable module support.
Then build a kernel with module support enabled.
Do not install modules in the case. Al
If build fails during (bin)rpm-pkg, the spec file is not cleaned by
anyone until the next successful build of the package.
We do not have to immediately delete the spec file in case somebody
may want to take a look at it. Instead, make them ignored by git,
and cleaned up by make mrproper.
Signed
Clean up the mkspec without changing the behavior.
- grep CONFIG_DRM=y more simply
- move "EXCLUDE" out of the "%install" section because it can be
computed when the spec file is generated
- remove "BuildRoot:" field, which is now redundant
- do not mkdir $RPM_BUILD_ROOT/lib/modules expl
This conditional was added by commit fc370ecfdb37 ("kbuild: add
vmlinux to kernel rpm"). Its git-log mentioned vmlinux.bz2 was
necessary for debugging, but did not explain why ppc64 was an
exception. I see no problem to copy vmlinux.bz2 all the time.
Signed-off-by: Masahiro Yamada
---
scripts
On 09/29/2017 02:19 PM, Vivien Didelot wrote:
> The DSA tagging code does not need to know about the DSA architecture,
> it only needs to return the slave device corresponding to the source
> port index (and eventually the source device index for cascade-capable
> switches) parsed from the frame
This patch fixes the scope of has_fr and has_fmr variables as they are
needed only in rds_ib_add_one().
Signed-off-by: Avinash Repaka
---
net/rds/ib.c | 11 ++-
net/rds/ib.h | 2 --
2 files changed, 6 insertions(+), 7 deletions(-)
diff --git a/net/rds/ib.c b/net/rds/ib.c
index a0954ac.
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 != l == NULL
l;
...>
(
e =
-container_of
+list_entry
(
On 09/28/2017 04:37 AM, Lorenzo Pieralisi wrote:
Through struct pci_host_bridge->{map/swizzle}_irq() hooks is now
possible to define IRQ mapping functions on a per PCI host bridge basis.
Actual IRQ allocation is carried out by the pci_assign_irq() function in
pci_device_probe() - to make sure a
On Wed, Sep 27, 2017 at 11:02:15PM -0500, Mario Limonciello wrote:
> The Dell WMI descriptor check is used as an indication that WMI
> calls are safe to run both when used with the notification
> ASL/GUID pair as well as the SMBIOS calling ASL/GUID pair.
>
> As some code in dell-wmi-smbios is alre
On 9/29/2017 6:13 PM, Avinash Repaka wrote:
This patch fixes the scope of has_fr and has_fmr variables as they are
needed only in rds_ib_add_one().
Signed-off-by: Avinash Repaka
---
Indeed the final merge version actually didn't need
those across files. Change looks good to me. Thanks !!
Acke
These patches add support drm hdmi in RK3328 and has been tested in RK
development
board. We add dev_type to distinguish different rockchip chips. Hdmi phy or
some regs
configuration can't be switched according to dev_type, that hdmi driver's
compatibility
will be better.
Algea Cao (7):
drm/r
Add rk3328-dw-hdmi to support rk3328.
Signed-off-by: Algea Cao
---
.../devicetree/bindings/display/rockchip/dw_hdmi-rockchip.txt | 1 +
drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 6 ++
2 files changed, 7 insertions(+)
diff --git
a/Documentation/devicetree/b
To determine type of SOC, we add a parameter dev_type.
Signed-off-by: Algea Cao
---
drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 5 +
include/drm/bridge/dw_hdmi.h| 10 ++
2 files changed, 15 insertions(+)
diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
b/
Because some RK chips use inno hdmi phy, such as RK3328, we add
inno hdmi phy ops.
Signed-off-by: Algea Cao
---
drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 110 +++-
1 file changed, 107 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockchi
Writing grf register according to device type.
Signed-off-by: Algea Cao
---
drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
b/drivers/gpu/drm/rockchip/dw_hdmi-rockchip
Change dw_hdmi_phy_read_hpd from static to export.
inno hdmi phy ops will call this interface to get
hpd status.
Signed-off-by: Algea Cao
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 5 +++--
include/drm/bridge/dw_hdmi.h | 3 ++-
2 files changed, 5 insertions(+), 3 deletions(-)
Add clk hclk_vio and enable it when hdmi bind.
Signed-off-by: Algea Cao
---
drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c | 21 +
1 file changed, 21 insertions(+)
diff --git a/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
b/drivers/gpu/drm/rockchip/dw_hdmi-rockchip.c
index 7658
Add device type to distinguish different chips.Different chips
use different phy ops, get them by device type.
Signed-off-by: Algea Cao
---
drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi.c
On Wed, Sep 27, 2017 at 11:02:16PM -0500, Mario Limonciello wrote:
> For WMI operations that are only Set or Query read or write sysfs
> attributes created by WMI vendor drivers make sense.
>
> For other WMI operations that are run on Method, there needs to be a
> way to guarantee to userspace th
Hi!
I'm afraid I see random instant reboots on current -rc, approximately
once per day, only under CPU load. There's nothing on serial/etc -- just
an immediate reboot. 4.13 works perfectly; last kernel I've tried is
v4.14-rc2-165-g770b782f555d. gcc 7.2.0-7 (Debian).
CPU is AMD Phenom II X6 1055
On Wed, Sep 27, 2017 at 11:02:17PM -0500, Mario Limonciello wrote:
> This userspace character device will be used to perform SMBIOS calls
> from any applications.
>
> It provides an ioctl that will allow passing the 32k WMI calling
> interface buffer between userspace and kernel space.
>
> This c
On Wed, Sep 27, 2017 at 11:02:18PM -0500, Mario Limonciello wrote:
> Currently userspace tools can access system tokens via the dcdbas
> kernel module and a SMI call that will cause the platform to execute
> SMM code.
>
> With a goal in mind of deprecating the dcdbas kernel module a different
> me
x-next specific files for 20170929
+---++++---+
| | 96036c4306 |
f34c8585ed | 99637e4268
On Wed, Sep 27, 2017 at 11:02:12PM -0500, Mario Limonciello wrote:
> The existing way that the dell-smbios helper module and associated
> other drivers (dell-laptop, dell-wmi) communicate with the platform
> really isn't secure. It requires creating a buffer in physical
> DMA32 memory space and pa
I am Ms.Ella Golan, I am the Executive Vice President Banking Division with
FIRST INTERNATIONAL BANK OF ISRAEL LTD (FIBI).
I am getting in touch with you regarding an extremely important and urgent
matter. If you would oblige me the opportunity, I shall provide you with
details upon your response.
Hi Linus,
My apologies for the typo in the patch subject... at this point it was
rebase a published branch, or send you a spelling error... tough call!
The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
are available in the
On 28.09.2017 15:50, Mikko Perttunen wrote:
> Since Tegra186 the Host1x hardware allows syncpoints to be assigned to
> specific channels, preventing any other channels from incrementing
> them.
>
> Enable this feature where available and assign syncpoints to channels
> when submitting a job. Syncp
On 28.09.2017 15:50, Mikko Perttunen wrote:
> The disassembler for debug dumps was missing some newer host1x opcodes.
> Add disassembly support for these.
>
> Signed-off-by: Mikko Perttunen
> ---
Reviewed-by: Dmitry Osipenko
And for older Tegra's:
Tested-by: Dmitry Osipenko
> drivers/gpu/
On 28.09.2017 15:50, Mikko Perttunen wrote:
> Use the u64_to_user_ptr helper macro to cast IOCTL argument u64 values
> to user pointers instead of writing out the cast manually. Also do
> some other cleanup with user pointers to make them stand out more
> and look cleaner.
>
> Signed-off-by: Mikko
Hello
Petr, could you please pick up the series?
==
On some arches C function pointers are indirect and point to
a function descriptor, which contains the actual pointer to the code.
This mostly does
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 dereference_kernel_funct
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 func
We are moving towards separate kernel and module function descriptor
dereference callbacks. This patch enables it for IA64.
For pointers that belong to the kernel
- Added __start_opd and __end_opd pointers, to track the kernel
.opd section address range;
- Added dereference_kernel_function_d
Convert dereference_function_descriptor() to accept and return
`unsigned long'. There will be two new ARCH function for kernel
and module function pointer dereference, which will work with
`unsigned long', so the patch unifies interfaces.
Besides, dereference_function_descriptor() mostly work with
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
'%pF/%pf'
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 dereference_kernel_functi
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 Senozhat
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,
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 p
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
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 -> __getblk_g
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 +
arch/
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
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
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
(addr0 && addr1)
Signed-off-by: Luming Yu
0005-early-pt-basic-addr-pair-filter-support-addr0-addr1.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 PSB packet
Signed-off-by: Luming Yu
0007-enable-early-pt-psb-packet.patch
Description: Binary data
enable CYC packet
Signed-off-by: Luming Yu
0008-early-pt-enable-cyc-packet.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
1 - 100 of 625 matches
Mail list logo
