Greetings,
0day kernel testing robot got the below dmesg and the first bad commit is
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
debugfs_cleanup
commit c438cfd46e37a6dd9e370219a6f0d397cc3c1a36
Author: Greg Kroah-Hartman
AuthorDate: Fri Jan 4 14:06:22 2019 +0100
Add an off-by-default configuration option to use a global stack cookie
instead of the default TLS. This configuration option will only be used
with PIE binaries.
For kernel stack cookie, the compiler uses the mcmodel=kernel to switch
between the fs segment to gs segment. A PIE binary does not
When using PIE with function tracing, the compiler generates a
call through the GOT (call *__fentry__@GOTPCREL). This instruction
takes 6-bytes instead of 5-bytes with a relative call.
If PIE is enabled, replace the 6th byte of the GOT call by a 1-byte nop
so ftrace can handle the previous
Add an option so the module section is just after the mapped kernel. It
will ensure position independent modules are always at the right
distance from the kernel and do not require mcmodule=large. It also
optimize the available size for modules by getting rid of the empty
space on kernel
The x86 relocation tool generates a list of 32-bit signed integers. There
was no need to use 64-bit integers because all addresses where above the 2G
top of the memory.
This change add a large-reloc option to generate 64-bit unsigned integers.
It can be used when the kernel plan to go below the
Adapt module loading to support PIE relocations. Generate dynamic GOT if
a symbol requires it but no entry exists in the kernel GOT.
Position Independent Executable (PIE) support will allow to extend the
KASLR randomization range below 0x8000.
Signed-off-by: Thomas Garnier
---
Add a new CONFIG_RANDOMIZE_BASE_LARGE option to benefit from PIE
support. It increases the KASLR range from 1GB to 3GB. The new range
stars at 0x just above the EFI memory region. This
option is off by default.
The boot code is adapted to create the appropriate page table spanning
Change the assembly code to use the new _ASM_MOVABS macro which get a
symbol reference while being PIE compatible. Adapt the relocation tool
to ignore 32-bit Xen code.
Position Independent Executable (PIE) support will allow to extend the
KASLR randomization range below 0x8000.
Provide an option to have a PROVIDE_HIDDEN (linker script) entry for
each weak symbol. This option solves an error in x86_64 where the linker
optimizes PIE generated code to be non-PIE because --emit-relocs was used
instead of -pie (to reduce dynamic relocations).
Signed-off-by: Thomas Garnier
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible. The new __ASM_MOVABS macro is used to
get the address of a symbol on both 32 and 64-bit with PIE support.
Position Independent Executable (PIE) support will allow to extend the
KASLR
Change the assembly options to work with pointers instead of integers.
Position Independent Executable (PIE) support will allow to extend the
KASLR randomization range below 0x8000.
Signed-off-by: Thomas Garnier
---
arch/x86/include/asm/alternative.h | 6 +++---
1 file changed, 3
The __startup_64 function assumes all symbols have relocated addresses
instead of the current boot virtual address. PIE generated code favor
relative addresses making all virtual and physical address math incorrect.
If PIE is enabled, build head64.c as mcmodel large instead to ensure absolute
Perpcu uses a clever design where the .percu ELF section has a virtual
address of zero and the custom linux relocation code avoid relocating
specific symbols. It makes the code simple and easily adaptable with or
without SMP support.
This design is incompatible with PIE. While creating a PIE
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extend the
KASLR randomization range below 0x8000.
Signed-off-by: Thomas Garnier
Acked-by: Pavel Machek
Acked-by:
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Early at boot, the kernel is mapped at a temporary address while preparing
the page table. To know the changes needed for the page table with KASLR,
the boot code calculate the difference
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extend the
KASLR randomization range below 0x8000.
Signed-off-by: Thomas Garnier
---
Since commit c40dd2f76644 ("powerpc: Add System RAM to /proc/iomem")
it is possible to use the generic walk_system_ram_range() and
the generic page_is_ram().
Fixes: c40dd2f76644 ("powerpc: Add System RAM to /proc/iomem")
Signed-off-by: Christophe Leroy
---
arch/powerpc/Kconfig| 3
Change the assembly code to use only absolute references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extend the
KASLR randomization range below 0x8000.
Signed-off-by: Thomas Garnier
---
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible. Use the new _ASM_MOVABS macro instead of
the 'mov $symbol, %dst' construct.
Position Independent Executable (PIE) support will allow to extend the
KASLR randomization range below
Add a new _ASM_MOVABS macro to fetch a symbol address. It will be used
to replace "_ASM_MOV $, %dst" code construct that are not compatible
with PIE.
Signed-off-by: Thomas Garnier
---
arch/x86/include/asm/asm.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/include/asm/asm.h
Change assembly to use the new _ASM_MOVABS macro instead of _ASM_MOV for
the assembly to be PIE compatible.
Position Independent Executable (PIE) support will allow to extend the
KASLR randomization range below 0x8000.
Signed-off-by: Thomas Garnier
---
Change the assembly code to use only relative references of symbols for the
kernel to be PIE compatible.
Position Independent Executable (PIE) support will allow to extend the
KASLR randomization range below 0x8000.
Signed-off-by: Thomas Garnier
Acked-by: Pavel Machek
Acked-by:
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-sitronix-st7789v.c | 10 ++
1 file changed, 6 insertions(+), 4
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-jdi-lt070me05000.c | 64 ++
1 file changed, 34
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-ilitek-ili9322.c | 93 +++
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-innolux-p079zca.c | 12 +++-
1 file changed, 7 insertions(+), 5
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
Cc: Stefan Mavrodiev
---
drivers/gpu/drm/panel/panel-truly-nt35597.c | 2 +-
1 file changed, 1 insertion(+), 1
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Stefan Mavrodiev
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-olimex-lcd-olinuxino.c | 26 +-
1 file
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-lg-lg4573.c | 20 +++-
1 file changed, 11 insertions(+), 9
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-orisetech-otm8009a.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-lvds.c | 38 ++
1 file changed, 22
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-samsung-ld9040.c | 12 +--
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-seiko-43wvf1g.c | 14 --
1 file changed, 8 insertions(+), 6
The num_supplies variable is not used, delete it.
Build tested.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-innolux-p079zca.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/panel/panel-innolux-p079zca.c
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-simple.c | 19 ---
1 file changed, 12 insertions(+), 7
Hi Thierry et al.
While reviewing a number of new panel drivers there was a
certain pattern in the feedback:
- the now deprecated drmP.h file was used
- dev_err() and friends was used
This patch-set address the above items in the panel
drivers in drm/panel/
The hope is that new panel drivers
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
Cc: Stefan Mavrodiev
---
drivers/gpu/drm/panel/panel-arm-versatile.c | 18 ++
1 file changed, 10
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
.../gpu/drm/panel/panel-raspberrypi-touchscreen.c | 22 ++
1 file changed, 14
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-panasonic-vvx10f034n00.c | 16 ++--
1 file changed, 10 insertions(+),
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-sharp-lq101r1sx01.c | 63 -
Introduce use of DRM_DEV* for logging.
This makes logging in the drm subsystem more consistent.
Signed-off-by: Sam Ravnborg
Cc: Thierry Reding
Cc: David Airlie
Cc: Daniel Vetter
---
drivers/gpu/drm/panel/panel-raydium-rm68200.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Require signed kernel modules on systems with secure boot mode enabled.
To coordinate between appended kernel module signatures and IMA
signatures, only define an IMA MODULE_CHECK policy rule if
CONFIG_MODULE_SIG is not enabled.
This patch defines a function named set_module_sig_required() and
This commit adds the bootctl platform driver for Mellanox BlueField
Soc, which controls the eMMC boot partition swapping and sends SMC
calls to ATF running at exception level EL3 to program some system
register. This register is only accessible in secure code and is
used to enable the watchdog
On Wed, Jan 30, 2019 at 10:59 PM Yong Wu wrote:
>
> On Wed, 2019-01-30 at 10:28 -0800, Evan Green wrote:
> > On Mon, Dec 31, 2018 at 7:57 PM Yong Wu wrote:
> > >
> > > MediaTek extend the arm v7s descriptor to support the dram over 4GB.
> > >
> > > In the mt2712 and mt8173, it's called "4GB
v3 has been posted with Changelog added.
Thanks!
Liming
> -Original Message-
> From: Liming Sun
> Sent: Thursday, January 31, 2019 12:18 PM
> To: 'Andy Shevchenko'
> Cc: Andy Shevchenko ; Darren Hart ;
> Vadim Pasternak ; David
> Woods ; Platform Driver
> ; Linux Kernel Mailing List
On 12/6/18 1:28 PM, Steve Sistare wrote:
> Provide struct sparsemask and functions to manipulate it. A sparsemask is
> a sparse bitmap. It reduces cache contention vs the usual bitmap when many
> threads concurrently set, clear, and visit elements, by reducing the number
> of significant bits
The kernel can be configured to verify the appended kernel module
signature, the IMA signature stored as an xattr, both types of
signatures, or none. On systems with secure boot enabled AND the IMA
architecture specific policy enabled, this patch set requires the file
to be signed.
Both methods
On Mon, Jan 28, 2019 at 04:05:34PM -0800, Matthias Kaehlcke wrote:
> Hi,
>
> this series has gone through multiple rounds of review and there are
> no outstanding comments. It seems it should be ready to land, or is
> there anything left that needs to be addressed?
>From the drm side, I think
On 2019-01-31 12:02 p.m., Jason Gunthorpe wrote:
> I still think the right direction is to build on what Logan has done -
> realize that he created a DMA-only SGL - make that a formal type of
> the kernel and provide the right set of APIs to work with this type,
> without being forced to expose
On Thu, Jan 31, 2019 at 4:28 AM Mark Brown wrote:
>
> On Thu, Jan 31, 2019 at 09:15:01AM +0100, Bartosz Golaszewski wrote:
>
> > I'm not sure what the policy is on merging MFD drivers, but I'm seeing
> > that Mark Brown has already picked up the regulator part into his tree
> > (including the
On Thu, 31 Jan 2019 at 19:41, Linus Torvalds
wrote:
> On Wed, Jan 30, 2019 at 12:30 PM Andreas Gruenbacher
> wrote:
> >
> > This reverts commit 2d29f6b96d8f80322ed2dd895bca590491c38d34.
> >
> > It turns out that the fix can lead to a ~20 percent performance regression
> > in initial writes to
On Thu, Jan 31, 2019 at 10:52 AM Linus Torvalds
wrote:
>
> I think what I should do is to just make "memcpy_*io()" do the "align
> naturally" thing.
>
> Let me cook up a patch for you to test.
Does this work for you?
I haven't tested it at all, but I verified that the generated code
seems to
On Tue, 8 Jan 2019 at 10:27, Anders Roxell wrote:
>
> Fixes: 2a31b9db1535 ("kvm: introduce manual dirty log reprotect")
> Fixes: 7edcb7343327 ("KVM: selftests: Add hyperv_cpuid test")
> Signed-off-by: Anders Roxell
> ---
> tools/testing/selftests/kvm/.gitignore | 2 ++
> 1 file changed, 2
From: luciana
Align broken line to match upper line parenthesis. Solves the
checkpatch.pl's message:
CHECK: Alignment should match open parenthesis
Signed-off-by: luciana
---
drivers/iio/accel/adxl345_core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Tue, 8 Jan 2019 at 10:25, Anders Roxell wrote:
>
> Commit cda261f421ba ("selftests: add txtimestamp kselftest") introduced
> a warning:
>
> Makefile:14: warning: overriding recipe for target 'clean'
> ../../lib.mk:137: warning: ignoring old recipe for target 'clean'
>
> Theres no need for
On Wed, Jan 30, 2019 at 1:43 AM Gerd Hoffmann wrote:
>
> There is no need to wait for completion here.
>
> The host will process commands in submit order, so commands can
> reference the new resource just fine even when queued up before
> completion.
Does virtio_gpu_execbuffer_ioctl also wait
On 31/01/2019 18:47, Mathieu Poirier wrote:
CoreSight was the only client of the PMU's set_drv_config() API. Now
that it is no longer needed by CoreSight remove it from the code base.
Signed-off-by: Mathieu Poirier
---
tools/perf/builtin-record.c | 10 -
tools/perf/builtin-stat.c
31.01.2019 19:27, Dmitry Osipenko пишет:
> 31.01.2019 19:01, Thierry Reding пишет:
>> On Thu, Jan 31, 2019 at 06:02:45PM +0300, Dmitry Osipenko wrote:
>>> 31.01.2019 17:43, Thierry Reding пишет:
On Thu, Jan 31, 2019 at 05:06:18PM +0300, Dmitry Osipenko wrote:
> 31.01.2019 15:06, Thierry
On Thu, Jan 31, 2019 at 09:13:55AM +0100, Christoph Hellwig wrote:
> On Wed, Jan 30, 2019 at 03:52:13PM -0700, Logan Gunthorpe wrote:
> > > *shrug* so what if the special GUP called a VMA op instead of
> > > traversing the VMA PTEs today? Why does it really matter? It could
> > > easily change to
Hi Sudeep,
> -Original Message-
> From: Sudeep Holla
> Sent: Wednesday, January 30, 2019 2:13 AM
> To: Jolly Shah
> Cc: matthias@gmail.com; andy.gr...@linaro.org; shawn...@kernel.org;
> geert+rene...@glider.be; bjorn.anders...@linaro.org;
> sean.w...@mediatek.com;
On 31/01/2019 18:47, Mathieu Poirier wrote:
This patch uses the information conveyed by perf_event::attr::config2
to select a sink to use for the session. That way a sink can easily be
selected to be used by more than one source, something that isn't currently
possible with the sysfs
On Thu, Jan 31, 2019 at 10:10:11AM +0100, Michal Hocko wrote:
> On Thu 31-01-19 12:34:03, Dave Chinner wrote:
> > On Wed, Jan 30, 2019 at 12:21:07PM +, Chris Mason wrote:
> > >
> > >
> > > On 29 Jan 2019, at 23:17, Dave Chinner wrote:
> > >
> > > > From: Dave Chinner
> > > >
> > > > This
When using multi-ports each port uses resources (dbs, msgs, mws, etc)
on every other port. Creating a mapping for these resources such that
each port has a corresponding resource on every other port is a bit
tricky.
Introduce the ntb_peer_resource_idx() function for this purpose.
It returns the
When the ntb_msi_test module is available, the test code will trigger
each of the interrupts and ensure the corresponding occurrences files
gets incremented.
Signed-off-by: Logan Gunthorpe
Cc: Jon Mason
Cc: Dave Jiang
Cc: Allen Hubbe
---
tools/testing/selftests/ntb/ntb_test.sh | 54
Hi,
This patch series adds optional support for using MSI interrupts instead
of NTB doorbells in ntb_transport. This is desirable seeing doorbells on
current hardware are quite slow and therefore switching to MSI interrupts
provides a significant performance gain. On switchtec hardware, a simple
When a device has multiple aliases that all are from the same bus,
we program the IRTE to accept requests from any matching device on the
bus.
This is so NTB devices which can have requests from multiple bus-devfns
can pass MSI interrupts through across the bridge.
Signed-off-by: Logan Gunthorpe
Introduce the module parameter 'use_msi' which, when set uses
MSI interrupts instead of doorbells for each queue pair (QP). T
he parameter is only available if NTB MSI support is configured into
the kernel. We also require there to be more than one memory window
(MW) so that an extra one is
The NTB MSI library allows passing MSI interrupts across a memory
window. This offers similar functionality to doorbells or messages
except will often have much better latency and the client can
potentially use significantly more remote interrupts than typical hardware
provides for doorbells.
Introduce a tool to test NTB MSI interrupts similar to the other
NTB test tools. This tool creates a debugfs directory for each
NTB device with the following files:
port
irqX_occurrences
peerX/port
peerX/count
peerX/trigger
The 'port' file tells the user the local port number and the
The kbuild system does not support having multiple source files in
a module if one of those source files has the same name as the module.
Therefore, we must rename ntb.c to core.c, while the module remains
ntb.ko.
This is similar to the way the nvme modules are structured.
Signed-off-by: Logan
Remove the few bashisms in the script and use the complete option name
for clarity.
Signed-off-by: Mimi Zohar
---
tools/testing/selftests/ima/test_kexec_load.sh | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/tools/testing/selftests/ima/test_kexec_load.sh
For NTB devices, we want to be able to trigger MSI interrupts
through a memory window. In these cases we may want to use
more interrupts than the NTB PCI device has available in its MSI-X
table.
We allow for this by creating a new 'virtual' interrupt. These
interrupts are allocated as usual but
Seeing the we want to use more interrupts in the NTB MSI code
we need to be able allocate more (sometimes virtual) interrupts
in the switchtec driver. Therefore add a module parameter to
request to allocate additional interrupts.
This puts virtually no limit on the number of MSI interrupts
The kernel can be configured to verify PE signed kernel images, IMA
kernel image signatures, both types of signatures, or none. This test
verifies only properly signed kernel images are loaded into memory,
based on the kernel configuration and runtime policies.
Signed-off-by: Mimi Zohar
---
The kernel can be configured to verify PE signed kernel images, IMA
kernel image signatures, both types of signatures, or none. Verify
only properly signed kernel images are loaded into memory, based on
the kernel configuration and runtime policies.
Mimi Zohar (3):
selftest/ima: cleanup the
On 31/01/2019 18:47, Mathieu Poirier wrote:
Add a "sinks" directory entry so that users can see all the sinks
available in the system in a single place. Individual sink are added
as they are registered with the coresight bus.
Signed-off-by: Mathieu Poirier
Acked-by: Peter Zijlstra (Intel)
Define and move get_secureboot_mode() to a common file for use by other
tests.
Signed-off-by: Mimi Zohar
---
tools/testing/selftests/ima/common_lib.sh | 20
tools/testing/selftests/ima/test_kexec_load.sh | 17 +++--
2 files changed, 23 insertions(+), 14
On Thu, Jan 31, 2019 at 10:51 AM Linus Torvalds
wrote:
>
> In fact, we have another patch (that isn't applied) that makes even
> the memcpy_erms() just call the sw version of memcpy() for short
> copies (because "rep movsb" is slow for those cases). That would also
> have broken your driver.
I
On Thu, Jan 31, 2019 at 10:35 AM Jarkko Sakkinen
wrote:
>
> OK, so the length of the response is not trashed, but only the error
> code. The attached patch fully fixes the issue.
>
> Here's the header again:
>
> struct tpm_output_header {
> __be16 tag;
> __be32 length;
>
This patch uses the information conveyed by perf_event::attr::config2
to select a sink to use for the session. That way a sink can easily be
selected to be used by more than one source, something that isn't currently
possible with the sysfs implementation.
Signed-off-by: Mathieu Poirier
When pmu::setup_aux() is called the coresight PMU needs to know which
sink to use for the session by looking up the information in the
event's attr::config2 field.
As such simply replace the cpu information by the complete perf_event
structure and change all affected customers.
Signed-off-by:
On Thu, Jan 31, 2019 at 09:43:42AM -0800, Linus Torvalds wrote:
> On Thu, Jan 31, 2019 at 9:06 AM Jarkko Sakkinen
> wrote:
> >
> > Found something that *does* fix the issue. If I replace memcpy_*io()
> > calls with regular memcpy(), the driver works and all my tests pass.
>
> That's not
CoreSight was the only client of the PMU's set_drv_config() API. Now
that it is no longer needed by CoreSight remove it from the code base.
Signed-off-by: Mathieu Poirier
---
tools/perf/builtin-record.c | 10 -
tools/perf/builtin-stat.c | 9
tools/perf/builtin-top.c | 13
The communication of sink information for a trace session doesn't work when
more than on CPU is involved in the scenario due to the static nature of
sysfs. As such communicate the sink information to each event by using the
perf_event::attr:config2 attribute. The information sent to the kernel
Moving definition of EVENT_SOURCE_DEVICE_PATH to pmu.h so that it can be
used by other files than pmu.c
Signed-off-by: Mathieu Poirier
Acked-by: Suzuki K Poulose
---
tools/perf/util/pmu.c | 2 --
tools/perf/util/pmu.h | 1 +
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git
Now that event's config2 attribute is used to communicate sink selection
to the kernel, remove the old set_drv_config() implementation since it
is no longer needed.
Signed-off-by: Mathieu Poirier
---
tools/perf/arch/arm/util/cs-etm.c | 54 ---
Add a "sinks" directory entry so that users can see all the sinks
available in the system in a single place. Individual sink are added
as they are registered with the coresight bus.
Signed-off-by: Mathieu Poirier
Acked-by: Peter Zijlstra (Intel)
---
This is the third revision of a patchset allowing multiple sources to select
the same sink for a session which is a prerequisite for the support of CoreSight
CPU-wide trace scenarios.
The sink ID is communicated to the kernel by way of the event's configuration
attribute (event::attr:config2).
On Fri, Feb 01, 2019 at 07:31:48AM +1300, Kees Cook wrote:
> On Thu, Jan 31, 2019 at 11:51 PM Greg KH wrote:
> > Can you test the patch below?
> >
> > thanks,
> >
> > greg k-h
> >
> > --
> >
> > diff --git a/kernel/relay.c b/kernel/relay.c
> > index 04f248644e06..9e0f52375487 100644
>
On Thu, Jan 31, 2019 at 11:15:48AM +, Li,Rongqing wrote:
>
>
> > -邮件原件-
> > 发件人: linux-kernel-ow...@vger.kernel.org
> > [mailto:linux-kernel-ow...@vger.kernel.org] 代表 Greg Kroah-Hartman
> > 发送时间: 2019年1月31日 18:55
> > 收件人: Li,Rongqing
> > 抄送: linux-ser...@vger.kernel.org;
From: Jérôme Glisse
Using set_pte_at_notify() trigger useless calls to change_pte() so just
use set_pte_at() instead. The reason is that set_pte_at_notify() should
only be use when going from either a read and write pte to read only pte
with same pfn, or from read only to read and write with a
On Thu, Jan 31, 2019 at 7:24 PM Greg Kroah-Hartman
wrote:
>
> On Thu, Jan 31, 2019 at 05:02:05PM +0100, Rafael J. Wysocki wrote:
> > On Thu, Jan 31, 2019 at 2:24 PM Greg Kroah-Hartman
> > wrote:
> > >
> > > On Thu, Jan 31, 2019 at 02:22:47PM +0100, Greg Kroah-Hartman wrote:
> > > > On Thu, Jan
The xavier CPU architecture includes 8 CPU cores organized in
4 clusters. Add cpu-map data for topology initialization, add
cache data for cache node creation in sysfs.
Signed-off-by: Bo Yan
---
arch/arm64/boot/dts/nvidia/tegra194.dtsi | 148 +--
1 file changed, 140
On Wed, Jan 30, 2019 at 12:30 PM Andreas Gruenbacher
wrote:
>
> This reverts commit 2d29f6b96d8f80322ed2dd895bca590491c38d34.
>
> It turns out that the fix can lead to a ~20 percent performance regression
> in initial writes to the page cache according to iozone. Let's revert this
> for now to
On Thu, Jan 31, 2019 at 11:14:03AM +0100, Rafael J. Wysocki wrote:
> On Thu, Jan 31, 2019 at 11:07 AM Viresh Kumar wrote:
> >
> > On 31-01-19, 11:03, Rafael J. Wysocki wrote:
> > > On Thu, Jan 31, 2019 at 9:30 AM Viresh Kumar
> > > wrote:
> > > >
> > > > On 30-01-19, 17:51, Matthias Kaehlcke
From: Jérôme Glisse
When notifying change for a range use MMU_NOTIFIER_USE_CHANGE_PTE flag
for page table update that use set_pte_at_notify() and where the we are
going either from read and write to read only with same pfn or read only
to read and write with new pfn.
Note that
Hi,
Greeting of the day!
Would you be interested in acquiring an email list of "Pool Owners" from USA?
We also have data for Home with Pool Owners List, Real Estate Investors List,
Condominium Owners List, Home Owners List, Real Estate Agents/Brokers List,
Mortgage with Home List and many
On Wed, 2019-01-30 at 13:30 -0800, Stephen Boyd wrote:
> > With this quirk, CCF is making an assumption that might be wrong.
> >
> > The quirk is very easy put in the get_parent() callback of the said
> > driver, or
> > even better, don't provide the callback if it should not be called.
> >
> >
From: Jérôme Glisse
Use unsigned for event field in range struct so that we can also set
flags with the event. This patch change the field and introduce the
helper.
Signed-off-by: Jérôme Glisse
Cc: Andrea Arcangeli
Cc: Peter Xu
Cc: Andrew Morton
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc:
From: Jérôme Glisse
Since changes to mmu notifier the change_pte() optimization was lost
for kvm. This re-enable it, when ever a pte is going from read and
write to read only with same pfn, or from read only to read and write
with different pfn.
It is safe to update the secondary MMUs, because
401 - 500 of 1208 matches
Mail list logo
