Hi Erwan,
Sorry for the late answer.
On Wed, 18 Sep 2019 11:43:19 +0200, Erwan Velu wrote:
> In DMI type 0, there is several fields that encodes a release.
is -> are
encodes -> encode
> The dmi_save_release() function have the logic to check if the field is valid.
> If so, it reports the
* Stephen Kitt [191019 14:07]:
> The buffer allocated in ti_adpll_clk_get_name doesn't account for the
> terminating null. This patch switches to devm_kasprintf to avoid
> overflowing.
>
> Signed-off-by: Stephen Kitt
> ---
> Changes since v2:
> - Move "adpll" into the format string and drop
This fixes the following DT schemas check errors:
meson-gxbb-nanopi-k2.dt.yaml: i2c@8500: compatible: Additional items are not
allowed ('amlogic,meson-gxbb-i2c' was unexpected)
meson-gxbb-nanopi-k2.dt.yaml: i2c@8500: compatible:0: 'amlogic,meson-gx-i2c' is
not one of ['amlogic,meson6-i2c',
* H. Nikolaus Schaller [191019 18:43]:
> --- a/arch/arm/mach-omap2/Makefile
> +++ b/arch/arm/mach-omap2/Makefile
> @@ -216,7 +216,6 @@ obj-$(CONFIG_MACH_NOKIA_N8X0) += board-n8x0.o
>
> # Platform specific device init code
>
> -omap-hsmmc-$(CONFIG_MMC_OMAP_HS) := hsmmc.o
>
This fixes the following DT schemas check errors:
meson-g12b-odroid-n2.dt.yaml: /: compatible: ['hardkernel,odroid-n2',
'amlogic,g12b'] is not valid under any of the given schemas
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-g12b-odroid-n2.dts | 2 +-
1 file changed, 1
This fixes the following DT schemas check errors:
meson-gxl-s905x-hwacom-amazetv.dt.yaml: cec@100: 'hdmi-phandle' is a required
property
meson-gxm-rbox-pro.dt.yaml: cec@100: 'hdmi-phandle' is a required property
because CEC is not enabled on these boards.
Signed-off-by: Neil Armstrong
---
This is the first set of DT fixes following the first YAML bindings conversion
at [1], [2], [3] and [4] and v5.4-rc1 bindings changes.
These are only cosmetic changes, and should not break drivers implementation
following the bindings.
[1] https://patchwork.kernel.org/patch/11202077/
[2]
This fixes the following DT schemas check errors:
meson-gxm-khadas-vim2.dt.yaml: gpu@c: interrupt-names:0: 'job' was expected
meson-gxm-khadas-vim2.dt.yaml: gpu@c: interrupt-names:2: 'gpu' was expected
Signed-off-by: Neil Armstrong
---
arch/arm64/boot/dts/amlogic/meson-gxm.dtsi | 6
This fixes the following DT schemas check errors:
meson-g12b-s922x-khadas-vim3.dt.yaml: gpu@ffe4: interrupt-names:0: 'job'
was expected
meson-g12b-s922x-khadas-vim3.dt.yaml: gpu@ffe4: interrupt-names:2: 'gpu'
was expected
Signed-off-by: Neil Armstrong
---
> -Original Message-
> From: Andrew Murray
> Sent: Monday, October 21, 2019 7:47 PM
> To: Pankaj Dubey
> Cc: 'Anvesh Salveru' ; linux-...@vger.kernel.org;
> linux-kernel@vger.kernel.org; bhelg...@google.com;
> gustavo.pimen...@synopsys.com; jingooh...@gmail.com;
>
Hi Anand,
On 21/10/2019 16:11, Anand Moon wrote:
> Hi Martin,
>
> On Fri, 18 Oct 2019 at 23:40, Martin Blumenstingl
> wrote:
>>
>> Hi Anand,
>>
>> On Fri, Oct 18, 2019 at 4:04 PM Anand Moon wrote:
>> [...]
Next step it to try narrow down the clock causing the issue.
Remove
iso_buffer should be set to NULL after use and free in the while loop.
In the case of isochronous URB in the while loop, iso_buffer is
allocated and after sending it to server, buffer is deallocated. And
then, if the next URB in the while loop is not a isochronous pipe,
iso_buffer still holds the
On Mon, Oct 21, 2019 at 10:01:24AM -0400, Qian Cai wrote:
> Warnings from linux-next,
>
> [ 14.265911][ T659] BUG: sleeping function called from invalid context at
> kernel/locking/mutex.c:935
> [ 14.265992][ T659] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid:
> 659, name:
"powerpc_security_features" is "unsigned long", i.e. 32-bit or 64-bit,
depending on the platform (PPC_FSL_BOOK3E or PPC_BOOK3S_64). Hence
casting its address to "u64 *", and calling debugfs_create_x64() is
wrong, and leaks 32-bit of nearby data to userspace on 32-bit platforms.
While all
On Tue, Oct 15, 2019 at 10:00 PM Minchan Kim wrote:
>
> On Tue, Oct 15, 2019 at 09:39:35AM +0200, Vitaly Wool wrote:
> > Hi Minchan,
> >
> > On Mon, Oct 14, 2019 at 6:41 PM Minchan Kim wrote:
> > >
> > > On Thu, Oct 10, 2019 at 11:04:14PM +0300, Vitaly Wool wrote:
> > > > The coming patchset is
Chris von Recklinghausen wrote:
> The put_user call from keyring_read_iterator caused a page fault which
> attempts to lock mm->mmap_sem and type->lock_class (key->sem) in the reverse
> order that keyring_read_iterator did, thus causing the circular locking
> dependency.
>
> Remedy this by
Commit fea3409112a9 ("USB: add direction bit to urb->transfer_flags") has
added a usb_urb_dir_in() helper function that can be used to determine
the direction of the URB. With that patch USB_DIR_IN control requests with
wLength == 0 are considered out requests by real USB HCDs. This patch
changes
When fuzzing the USB subsystem with syzkaller, we currently use 8 testing
processes within one VM. To isolate testing processes from one another it
is desirable to assign a dedicated USB bus to each of those, which means
we need at least 8 Dummy UDC/HCD devices.
This patch increases the maximum
could you explain the usage of siglock/PF_EXITING in
cgroup_enable_task_cg_lists() ?
PF_EXITING is protected by cgroup_threadgroup_rwsem, not by
sighand->siglock.
Oleg.
Changes in v2:
- Added missing Signed-off-by.
- Added better explanation as to why we need more Dummy devices.
Andrey Konovalov (2):
USB: dummy-hcd: increase max number of devices to 32
USB: dummy-hcd: use usb_urb_dir_in instead of usb_pipein
drivers/usb/gadget/udc/dummy_hcd.c | 10
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/scsi/cxgbi/cxgb4i/cxgb4i.c:2076:15:
warning: variable ppmax set but not used [-Wunused-but-set-variable]
drivers/target/iscsi/cxgbit/cxgbit_ddp.c:300:15:
warning: variable ppmax set but not used [-Wunused-but-set-variable]
It is not used
We have two types of users of page isolation:
1. Memory offlining: Offline memory so it can be unplugged. Memory won't
be touched.
2. Memory allocation: Allocate memory (e.g., alloc_contig_range()) to
become the owner of the memory and make use of it.
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/scsi/cxlflash/main.c:47:22: warning:
variable ioarcb set but not used [-Wunused-but-set-variable]
It is never used, so can be removed.
Signed-off-by: YueHaibing
---
drivers/scsi/cxlflash/main.c | 2 --
1 file changed, 2 deletions(-)
Two cleanups that popped up while working on (and discussing) virtio-mem:
https://lkml.org/lkml/2019/9/19/463
Tested with DIMMs on x86.
David Hildenbrand (2):
mm/page_alloc.c: Don't set pages PageReserved() when offlining
mm/page_isolation.c: Convert SKIP_HWPOISON to MEMORY_OFFLINE
On 21/10/2019 16:18, Arnd Bergmann wrote:
> After many randconfig builds, one configuration caused a link
> error with dwc3-meson-g12a lacking the regmap-mmio code:
>
> drivers/usb/dwc3/dwc3-meson-g12a.o: In function `dwc3_meson_g12a_probe':
> dwc3-meson-g12a.c:(.text+0x9f): undefined reference
We call __offline_isolated_pages() from __offline_pages() after all
pages were isolated and are either free (PageBuddy()) or PageHWPoison.
Nothing can stop us from offlining memory at this point.
In __offline_isolated_pages() we first set all affected memory sections
offline
After many randconfig builds, one configuration caused a link
error with dwc3-meson-g12a lacking the regmap-mmio code:
drivers/usb/dwc3/dwc3-meson-g12a.o: In function `dwc3_meson_g12a_probe':
dwc3-meson-g12a.c:(.text+0x9f): undefined reference to
`__devm_regmap_init_mmio_clk'
Add the select
This reverts commit cde9dde6e11a5ab54b6462cd46d82878926783bc.
The frame reassembly errors were root caused to a transient gpio issue.
The missing response was root caused to an issue with properly managing
RFR in the uart driver. Addressing those root causes occurs outside of
hci_qca and
On 21/10/2019 10:58, claudiu.bez...@microchip.com wrote:
> Hi Daniel,
>
> On 18.10.2019 23:24, Daniel Lezcano wrote:
>> Hi Claudiu,
>>
>> On 15/10/2019 11:23, claudiu.bez...@microchip.com wrote:
>>
>> [ ... ]
>>
>>> The timer clock source could be divided by MR.PRES + 1.
>>>
>>> So, I used the
On Mon, Oct 21, 2019 at 07:44:25PM +0530, Pankaj Dubey wrote:
>
>
> > -Original Message-
> > From: Andrew Murray
> > Sent: Monday, October 21, 2019 7:34 PM
> > To: Anvesh Salveru
> > Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
> > bhelg...@google.com;
On Sun, Oct 20, 2019 at 08:03:34PM -0700, Florian Fainelli wrote:
>
>
> On 10/19/2019 8:19 PM, Vivien Didelot wrote:
> > Now that we have a potential list of CPU ports, make use of it instead
> > of only configuring the master device of an unique CPU port.
>
> Out of your series, this is the
> On Sep 11, 2019, at 2:25 PM, Nicolas Saenz Julienne
> wrote:
>
> So far all arm64 devices have supported 32 bit DMA masks for their
> peripherals. This is not true anymore for the Raspberry Pi 4 as most of
> it's peripherals can only address the first GB of memory on a total of
> up to 4
On 21. 10. 19 12:18, Radhey Shyam Pandey wrote:
> xilinx axi_emac driver is supported on ZynqMP UltraScale platform.
> So enable ARCH64 in kconfig. It also removes redundant ARCH_ZYNQ
> dependency. Basic sanity testing is done on zu+ mpsoc zcu102
> evaluation board.
>
> Signed-off-by: Radhey
On Mon, Oct 21, 2019 at 05:55:55PM +0530, Anvesh Salveru wrote:
> Add support for ZRX-DC compliant PHYs. If PHY is not compliant to ZRX-DC
> specification, then after every 100ms link should transition to recovery
> state during the low power states which increases power consumption.
>
>
The SDC_QDSD_PINGROUP/UFS_RESET macros are missing the .tile info needed to
calculate the right register offsets. Adding them here and also
adjusting the offsets accordingly.
Fixes: f2ae04c45b1a ("pinctrl: qcom: Add SC7180 pinctrl driver")
Reported-by: Veerabhadrarao Badiganti
Signed-off-by:
On Thu, 17 Oct 2019 at 08:22, Manish Narani wrote:
>
> This patch series does the following:
> - Reorganize the Clock Handling in Arasan SD driver
> - Adds new sampling clock in Arasan SD driver
> - Adds support to set Clock Delays in SD Arasan Driver
> - Add SDIO Tap Delay handling in ZynqMP
> -Original Message-
> From: Andrew Murray
> Sent: Monday, October 21, 2019 7:34 PM
> To: Anvesh Salveru
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
> bhelg...@google.com; gustavo.pimen...@synopsys.com;
> jingooh...@gmail.com; lorenzo.pieral...@arm.com; Pankaj Dubey
+++ Petr Mladek [18/10/19 15:40 +0200]:
On Fri 2019-10-18 15:03:42, Jessica Yu wrote:
+++ Miroslav Benes [16/10/19 15:29 +0200]:
> On Wed, 16 Oct 2019, Miroslav Benes wrote:
> Thinking about it more... crazy idea. I think we could leverage these new
> ELF .text per vmlinux/module sections for
On Mon, Oct 21, 2019 at 08:53:12AM -0500, Josh Poimboeuf wrote:
> On Fri, Oct 18, 2019 at 09:35:40AM +0200, Peter Zijlstra wrote:
> > Now that set_all_modules_text_*() is gone, nothing depends on the
> > relation between ->state = COMING and the protection state anymore.
> > This enables moving
4.266299][ T659] softirqs last enabled at (0): []
> copy_process+0x720/0x19b0
> [ 14.266339][ T659] softirqs last disabled at (0): [<>] 0x0
> [ 14.266400][ T659] CPU: 64 PID: 659 Comm: pgdatinit8 Not tainted
> 5.4.0-rc4-next-20191021 #1
> [ 14.266462][
Hi Martin,
On Fri, 18 Oct 2019 at 23:40, Martin Blumenstingl
wrote:
>
> Hi Anand,
>
> On Fri, Oct 18, 2019 at 4:04 PM Anand Moon wrote:
> [...]
> > > Next step it to try narrow down the clock causing the issue.
> > > Remove clk_ignore_unused from the command line and add CLK_INGORE_UNUSED
> > >
From: Borislav Petkov
function_hook is used as a better name than the default __fentry__
which is the profiling counter which gcc adds before every function's
prologue. Thus, it is not called from C and cannot have the same
semantics as a pure C function - it saves/restores regs so that a C
On Mon, Oct 21, 2019 at 03:40:38PM +0200, Petr Mladek wrote:
> On Mon 2019-10-21 14:43:39, Peter Zijlstra wrote:
> > On Mon, Aug 19, 2019 at 12:47:31PM +0200, Petr Mladek wrote:
> > > Softlockup report means that there is no progress on the given CPU. It
> > > might be a "short" affair where the
From: Paul Cercueil
The scale can now be obtained with the "in_voltage_scale" file.
By default, the scale returned corresponds to the internal VREF of 2.5V.
It is possible to use an external VREF (through the REFIN/REFOUT pin of
the chip), by passing a regulator to the driver. The scale will
Documentation for AD7091R5 ADC was added.
Signed-off-by: Beniamin Bia
---
.../bindings/iio/adc/adi,ad7091r5.yaml| 53 +++
1 file changed, 53 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/adc/adi,ad7091r5.yaml
diff --git
From: Paul Cercueil
AD7091 is 4-Channel, I2C, Ultra Low Power,12-Bit ADC.
Datasheet:
Link:
https://www.analog.com/media/en/technical-documentation/data-sheets/ad7091r-5.pdf
Signed-off-by: Paul Cercueil
Co-developed-by: Beniamin Bia
Signed-off-by: Beniamin Bia
---
drivers/iio/adc/Kconfig
Add Beniamin Bia as a maintainer for AD7091R5 ADC.
Signed-off-by: Beniamin Bia
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2e01d0f0b0e5..7f1e4b88688f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -893,6 +893,14 @@ S: Supported
F:
On Mon 21-10-19 15:48:48, Oscar Salvador wrote:
> On Fri, Oct 18, 2019 at 02:39:01PM +0200, Michal Hocko wrote:
> >
> > I am sorry but I got lost in the above description and I cannot really
> > make much sense from the code either. Let me try to outline the way how
> > I think about this.
> >
>
On Mon, Oct 07, 2019 at 07:53:21AM +, eugen.hris...@microchip.com wrote:
>
>
> On 11.09.2019 11:24, Eugen Hristev - M18282 wrote:
> > From: Eugen Hristev
> >
> > Hello,
> >
> > This series adds support for analog and digital filters for i2c controllers
> >
> > This series is based on the
On Mon, Oct 21, 2019 at 05:59:53PM +0530, Anvesh Salveru wrote:
> Many platforms use DesignWare controller but the PHY can be different in
> different platforms. If the PHY is compliant is to ZRX-DC specification
s/is to/to the/
> it helps in low power consumption during power states.
s/in
On Mon, Oct 21, 2019 at 02:56:57PM +0800, Jin, Yao wrote:
SNIP
> > > Does it seem like what the c2c does?
> >
> > well c2c has its own data output with multiline column titles,
> > hence it has its own separate dimension stuff, but your code
> > output is within the standard perf report right?
Hi Paolo,
On 2019/10/21 16:45, Paolo Bonzini wrote:
On 13/10/19 11:15, Like Xu wrote:
Currently, a host perf_event is created for a vPMC functionality emulation.
It’s unpredictable to determine if a disabled perf_event will be reused.
If they are disabled and are not reused for a considerable
Em Mon, Oct 21, 2019 at 03:42:39PM +0300, Adrian Hunter escreveu:
> On 7/10/19 3:06 PM, Adrian Hunter wrote:
> > On 7/10/19 2:20 PM, Jiri Olsa wrote:
> >> On Fri, Oct 04, 2019 at 11:31:20AM +0300, Adrian Hunter wrote:
> >>
> >> SNIP
> >>
> >>> u8 pad[8] = {0};
> >>>
> >>> - if
at: deferred_init_memmap+0xc4/0x26c
[ 14.266160][ T659] irq event stamp: 26
[ 14.266194][ T659] hardirqs last enabled at (25): []
_raw_spin_unlock_irq+0x44/0x80
[ 14.266246][ T659] hardirqs last disabled at (26): []
_raw_spin_lock_irqsave+0x3c/0xa0
[ 14.266299][ T659] softirqs l
Now that we have the DT validation in place, let's convert the device tree
bindings for the Amlogic I2C Controller over to YAML schemas.
Cc: Beniamino Galvani
Signed-off-by: Neil Armstrong
---
.../bindings/i2c/amlogic,meson6-i2c.yaml | 53 +++
On Mon, Sep 30, 2019 at 05:28:01PM +0200, Fabrice Gasnier wrote:
> The slave-interface documentation [1] states "the bus driver should
> transmit the first byte" upon I2C_SLAVE_READ_REQUESTED slave event:
> - 'val': backend returns first byte to be sent
> The driver currently ignores the 1st byte
On Tue, Oct 01, 2019 at 10:51:09AM +0200, Fabrice Gasnier wrote:
> When in slave mode, an arbitration loss (ARLO) may be detected before the
> slave had a chance to detect the stop condition (STOPF in ISR).
> This is seen when two master + slave adapters switch their roles. It
> provokes the i2c
Save a few bytes by removing some registers from the driver that are not
currently used and not intended to be used at any point in the future.
Signed-off-by: Charles Keepax
---
drivers/mfd/wm8998-tables.c | 12
include/linux/mfd/arizona/registers.h | 7 ---
2 files
Add the 3 input clock sources for the chip into the device tree binding
document.
Reviewed-by: Rob Herring
Signed-off-by: Charles Keepax
---
Documentation/devicetree/bindings/mfd/madera.txt | 8
1 file changed, 8 insertions(+)
diff --git
Add the ability to get the clock for each clock input pin of the chip
and enable MCLK2 since that is expected to be a permanently enabled
32kHz clock.
Signed-off-by: Charles Keepax
---
drivers/mfd/madera-core.c | 27 ++-
include/linux/mfd/madera/core.h | 11
On 18.10.2019 21.59, Greg Kroah-Hartman wrote:
On Thu, Oct 17, 2019 at 02:33:00PM +0800, Kai-Heng Feng wrote:
On Oct 4, 2019, at 03:04, Alan Stern wrote:
On Fri, 4 Oct 2019, Kai-Heng Feng wrote:
Dell WD15 dock has a topology like this:
/: Bus 04.Port 1: Dev 1, Class=root_hub,
Hi Randy,
On 10/21/19 3:44 AM, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix Sphinx warning when building Documentation:
>
> Documentation/admin-guide/sysctl/kernel.rst:397: WARNING: Title underline too
> short.
>
> hung_task_interval_warnings:
> ===
Thanks for the patch!
On Fri, Oct 18, 2019 at 09:35:40AM +0200, Peter Zijlstra wrote:
> Now that set_all_modules_text_*() is gone, nothing depends on the
> relation between ->state = COMING and the protection state anymore.
> This enables moving the protection changes later, such that the COMING
> notifier callbacks
On Thu, Oct 17, 2019 at 7:44 PM Andrey Konovalov wrote:
>
> Currently kcov can only collect coverage for syscalls that are issued
> from the current process. This patch adds support for KCOV_REMOTE_ENABLE,
> that makes it possible to collect coverage for arbitrary parts of the
> kernel code,
On Mon, Oct 21, 2019 at 10:46:11AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Oct 21, 2019 at 03:42:39PM +0300, Adrian Hunter escreveu:
> > On 7/10/19 3:06 PM, Adrian Hunter wrote:
> > > On 7/10/19 2:20 PM, Jiri Olsa wrote:
> > >> On Fri, Oct 04, 2019 at 11:31:20AM +0300, Adrian Hunter
On Mon, Oct 21, 2019 at 11:10:55AM +0200, Christian Brauner wrote:
> The ifndef for SECCOMP_USER_NOTIF_FLAG_CONTINUE was placed under the
> ifndef for the SECCOMP_FILTER_FLAG_NEW_LISTENER feature. This will not
> work on systems that do support SECCOMP_FILTER_FLAG_NEW_LISTENER but do not
> support
On 21/10/2019 15:19:09+0200, Stefan Agner wrote:
> On 2019-10-21 07:41, Andreas Kemnade wrote:
> > Add an RTC driver for the RTC device on Ricoh MFD rc5t619,
> > which is implemented as a variant of rn5t618
> >
> > Signed-off-by: Andreas Kemnade
> > ---
> > drivers/rtc/Kconfig | 10 +
> >
Greetings
My name is Barrister Hans Erich.
I have a client who is interested to invest in your country, she is a well
known politician in her country and deserve a lucrative investment partnership
with you outside her country without any delay Please can you manage such
investment please
On Mon, Oct 21, 2019 at 10:56:27AM +0200, Johan Hovold wrote:
> On Fri, Oct 18, 2019 at 11:54:58AM -0700, Greg Kroah-Hartman wrote:
> > On Fri, Oct 18, 2019 at 05:19:55PM +0200, Johan Hovold wrote:
> > > The custom ring-buffer implementation was merged without any locking
> > > whatsoever, but a
On Fri, Oct 18, 2019 at 02:39:01PM +0200, Michal Hocko wrote:
>
> I am sorry but I got lost in the above description and I cannot really
> make much sense from the code either. Let me try to outline the way how
> I think about this.
>
> Say we have a pfn to hwpoison. We have effectivelly three
On Mon, Oct 21, 2019 at 03:19:48PM +0200, Christian Brauner wrote:
> On Mon, Oct 21, 2019 at 03:11:49PM +0200, Peter Zijlstra wrote:
> > By popular request; here's that alternative. Completely untested :-)
>
> Am I not getting some mails? :)
You're not on the 'right' IRC channels :-)
> I
On Thu, Oct 17, 2019 at 03:32:56PM -0400, Stuart Hayes wrote:
> Some systems have in-band presence detection disabled for hot-plug PCI
> slots, but do not report this in the slot capabilities 2 (SLTCAP2) register.
> On these systems, presence detect can become active well after the link is
>
This cures a panic on restart after a kexec -p operation on 5.3 and 5.4 kernels.
Fixes: 8af46c784ecfe ("iommu/vt-d: Implement is_attach_deferred iommu ops
entry")
The underlying state of the iommu registers (iommu->flags &
VTD_FLAG_TRANS_PRE_ENABLED) on a restart results in a domain being
On 10/21, Marco Elver wrote:
>
> On Mon, 21 Oct 2019 at 14:00, Oleg Nesterov wrote:
> >
> > I think this is WONTFIX.
>
> If taking the spinlock is unnecessary (which AFAIK it probably is) and
> there are no other writers to this flag, you will still need a
> WRITE_ONCE(tsk->flags, tsk->flags |
Em Mon, Oct 21, 2019 at 03:42:39PM +0300, Adrian Hunter escreveu:
> On 7/10/19 3:06 PM, Adrian Hunter wrote:
> > On 7/10/19 2:20 PM, Jiri Olsa wrote:
> >> On Fri, Oct 04, 2019 at 11:31:20AM +0300, Adrian Hunter wrote:
> >>
> >> SNIP
> >>
> >>> u8 pad[8] = {0};
> >>>
> >>> - if
On Wednesday, 16 October 2019 09:17:39 BST james qian wang (Arm Technology
China) wrote:
> On Tue, Oct 15, 2019 at 11:00:01AM +, Mihail Atanassov wrote:
> > Signed-off-by: Mihail Atanassov
> > ---
> > .../gpu/drm/arm/display/komeda/d71/d71_component.c | 14 +-
> > 1 file
From: John Garry
Add some more missing events.
Signed-off-by: John Garry
Reviewed-by: Shaokun Zhang
Cc: Alexander Shishkin
Cc: Jiri Olsa
Cc: Mark Rutland
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Will Deacon
Cc: linux...@huawei.com
Link:
From: John Garry
Add some more missing events.
A trivial typo is also fixed.
Signed-off-by: John Garry
Reviewed-by: Shaokun Zhang
Cc: Alexander Shishkin
Cc: Jiri Olsa
Cc: Mark Rutland
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc: Will Deacon
Cc: linux...@huawei.com
Link:
From: Thomas Richter
The build of file libperf-jvmti.so succeeds but the resulting
object fails to load:
# ~/linux/tools/perf/perf record -k mono -- java \
-XX:+PreserveFramePointer \
-agentpath:/root/linux/tools/perf/libperf-jvmti.so \
hog 10 123450
Error occurred
From: Arnaldo Carvalho de Melo
Just like strace has:
# trace -s sleep 1
Summary of events:
sleep (32370), 80 events, 93.0%
syscallcalls errors total min avg max
stddev
(msec)(msec)(msec)(msec)
From: Arnaldo Carvalho de Melo
To go from strarrays strings to its indexes.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jiri Olsa
Cc: Luis Cláudio Gonçalves
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-wta0qvo207z27huib2c4i...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
From: Jiri Olsa
Add the perf_evlist__for_each_mmap() function and export it in the
perf/evlist.h header, so that the user can iterate through 'struct
perf_mmap' objects.
Add a internal perf_mmap__link() function to do the actual linking.
Signed-off-by: Jiri Olsa
Cc: Alexander Shishkin
Cc:
From: Arnaldo Carvalho de Melo
We were doing this only at the sys_exit syscall tracepoint, as for
strace-like we count the pair of sys_enter and sys_exit as one event,
but when asking specifically for a the syscalls:sys_enter_NAME
tracepoint we need to count each of those as an event.
I.e.
From: Jiri Olsa
And missing include for "perf/core.h" header, which provides LIBPERF_*
debug levels and add missing pr_err() support.
Signed-off-by: Jiri Olsa
Cc: Alexander Shishkin
Cc: Alexey Budankov
Cc: Andi Kleen
Cc: Jin Yao
Cc: Michael Petlan
Cc: Namhyung Kim
Cc: Peter Zijlstra
Cc:
From: Jiri Olsa
Move allocation of the mmap array into perf_evlist__mmap_ops::get, to
centralize the mmap allocation.
Also move nr_mmap setup to perf_evlist__mmap_ops so it's centralized and
shared by both perf and libperf mmap code.
Signed-off-by: Jiri Olsa
Cc: Alexander Shishkin
Cc: Alexey
From: Jiri Olsa
Add mmaping tests that generates prctl call on every cpu validates it
gets all the related events in ring buffer.
Committer testing:
# make -C tools/perf/lib tests
make: Entering directory '/home/acme/git/perf/tools/perf/lib'
LINK test-cpumap-a
LINK
From: Jiri Olsa
Both static and dynamic tests needs to link with libapi.a, because it's
using its functions. Also include path for libapi includes.
Signed-off-by: Jiri Olsa
Cc: Alexander Shishkin
Cc: Alexey Budankov
Cc: Andi Kleen
Cc: Jin Yao
Cc: Michael Petlan
Cc: Namhyung Kim
Cc: Peter
On 18/10/2019 18:10, Mark Rutland wrote:
> On Tue, Oct 15, 2019 at 06:56:51PM +0100, Mark Rutland wrote:
[...]
>>> +PV_TIME_ST
>>> += ==
>>> +Function ID: (uint32)0xC521
>>> +Return value: (int64) IPA of the stolen time data structure for
From: Arnaldo Carvalho de Melo
The 'mmap' syscall has special needs so it doesn't use
SCA_STRARRAY_FLAGS, see its implementation in
syscall_arg__scnprintf_mmap_flags(), related to special handling of
MAP_ANONYMOUS, so set ->parm to the strarray__mmap_flags and hook up
with
From: Jin Yao
There are some deprecated events listed by perf list. But we can't
remove them from perf list with ease because some old scripts may use
them.
Deprecated events are old names of renamed events. When an event gets
renamed the old name is kept around for some time and marked with
From: Arnaldo Carvalho de Melo
With just what we need for the STUL_STRARRAY, i.e. the 'struct strarray'
pointer to be used, just like with syscall_arg_fmt->scnprintf() for the
other direction (number -> string).
With this all the strarrays that are associated with syscalls can be
used with '-e
From: Arnaldo Carvalho de Melo
Since its values are in two ranges of values we ended up codifying it
using a 'struct strarrays', so now hook it up with STUL_STRARRAYS so
that we can do:
# perf trace -e syscalls:*enter_fcntl --filter=cmd==SETLK||cmd==SETLKW
0.000 sssd_kcm/19021
On Mon 2019-10-21 14:43:39, Peter Zijlstra wrote:
> On Mon, Aug 19, 2019 at 12:47:31PM +0200, Petr Mladek wrote:
> > Softlockup report means that there is no progress on the given CPU. It
> > might be a "short" affair where the system gets recovered. But often
> > the system stops being responsive
From: Leo Yan
A few headers are not needed and were introduced by copying from other
test file. This patch removes the needless headers for the breakpoint
accounting testing.
Signed-off-by: Leo Yan
Cc: Adrian Hunter
Cc: Alexander Shishkin
Cc: Brajeswar Ghosh
Cc: Florian Fainelli
Cc: Jiri
From: Leo Yan
The arm architecture supports breakpoint accounting but it doesn't
support breakpoint overflow signal handling. The current code uses the
same checking helper, thus it disables both testings (bp_account and
bp_signal) for arm platform.
For handling two testings separately, this
From: Arnaldo Carvalho de Melo
Counterpart of strarray__scnprintf_flags(), i.e. from a expression like:
# perf trace -e syscalls:sys_enter_mmap
--filter="flags==PRIVATE|FIXED|DENYWRITE"
I.e. that "flags==PRIVATE|FIXED|DENYWRITE", turn that into
# perf trace -e syscalls:sys_enter_mmap
On Wed, Sep 25, 2019 at 03:06:37PM +0800, Jiwei Sun wrote:
SNIP
> SEE ALSO
>
> linkperf:perf-stat[1], linkperf:perf-list[1]
> diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
> index 48600c90cc7e..30904d2a3407 100644
> --- a/tools/perf/builtin-record.c
> +++
From: Jiri Olsa
Add mmaping tests that generates 100 prctl calls in monitored child
process and validates it gets 100 events in ring buffer.
Committer tests:
# make -C tools/perf/lib tests
make: Entering directory '/home/acme/git/perf/tools/perf/lib'
LINK test-cpumap-a
LINK
From: Arnaldo Carvalho de Melo
Now anything that uses STRARRAY_FLAGS, like the 'fsmount' syscall will
support mapping or-ed strings back to a value that can be used in a
filter.
In some cases, where STRARRAY_FLAGS isn't used but instead the scnprintf
is a special one because of specific needs,
From: Arnaldo Carvalho de Melo
So that we can later use it with the strarray__strtoul_flags() routine
that will be soon introduced.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Luis Cláudio Gonçalves
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-vldj3ch8su6i20to5eq31...@git.kernel.org
601 - 700 of 1220 matches
Mail list logo
