The following commit has been merged into the sched/core branch of tip:
Commit-ID: 45da27732b0b9b7a04696653065d5e6037bc5ac0
Gitweb:
https://git.kernel.org/tip/45da27732b0b9b7a04696653065d5e6037bc5ac0
Author:Valentin Schneider
AuthorDate:Wed, 15 Apr 2020 22:05:04 +01:00
The following commit has been merged into the sched/core branch of tip:
Commit-ID: f080d93e1d419099a99d7473ed532289ca8dc717
Gitweb:
https://git.kernel.org/tip/f080d93e1d419099a99d7473ed532289ca8dc717
Author:Xie XiuQi
AuthorDate:Tue, 14 Apr 2020 20:57:21 +08:00
Committer:
The following commit has been merged into the sched/core branch of tip:
Commit-ID: b1d1779e5ef7a60b192b61fd97201f322e1e9303
Gitweb:
https://git.kernel.org/tip/b1d1779e5ef7a60b192b61fd97201f322e1e9303
Author:Wei Yang
AuthorDate:Thu, 23 Apr 2020 21:44:43
Committer:
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 5a6d6a6ccb5f48ca8cf7c6d64ff83fd9c7999390
Gitweb:
https://git.kernel.org/tip/5a6d6a6ccb5f48ca8cf7c6d64ff83fd9c7999390
Author:Huaixin Chang
AuthorDate:Mon, 20 Apr 2020 10:44:21 +08:00
The following commit has been merged into the sched/core branch of tip:
Commit-ID: e669ac8ab952df2f07dee1e1efbf40647d6de332
Gitweb:
https://git.kernel.org/tip/e669ac8ab952df2f07dee1e1efbf40647d6de332
Author:Valentin Schneider
AuthorDate:Wed, 15 Apr 2020 22:05:06 +01:00
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: b09fb65e863733e192d4825a285b4b4998969ce0
Gitweb:
https://git.kernel.org/tip/b09fb65e863733e192d4825a285b4b4998969ce0
Author:Peter Zijlstra
AuthorDate:Fri, 24 Apr 2020 16:18:58 +02:00
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 586b58cac8b4683eb58a1446fbc399de18974e40
Gitweb:
https://git.kernel.org/tip/586b58cac8b4683eb58a1446fbc399de18974e40
Author:Jann Horn
AuthorDate:Thu, 05 Mar 2020 23:06:57 +01:00
Committer:
The following commit has been merged into the sched/core branch of tip:
Commit-ID: e98fa02c4f2ea4991dae422ac7e34d102d2f0599
Gitweb:
https://git.kernel.org/tip/e98fa02c4f2ea4991dae422ac7e34d102d2f0599
Author:Paul Turner
AuthorDate:Fri, 10 Apr 2020 15:52:07 -07:00
The following commit has been merged into the sched/core branch of tip:
Commit-ID: ab93a4bc955b3980c699430bc0b633f0d8b607be
Gitweb:
https://git.kernel.org/tip/ab93a4bc955b3980c699430bc0b633f0d8b607be
Author:Josh Don
AuthorDate:Fri, 10 Apr 2020 15:52:08 -07:00
Committer:
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: 60041bcd8f5ab560dabf44dc384f58bbeb5a6a30
Gitweb:
https://git.kernel.org/tip/60041bcd8f5ab560dabf44dc384f58bbeb5a6a30
Author:Peter Zijlstra
AuthorDate:Fri, 24 Apr 2020 16:16:41 +02:00
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 3a4ac121c2cacbf97d493fa3bc42ead88657abe4
Gitweb:
https://git.kernel.org/tip/3a4ac121c2cacbf97d493fa3bc42ead88657abe4
Author:CodyYao-oc
AuthorDate:Mon, 13 Apr 2020 11:14:29 +08:00
Committer:
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: fdc63ff0e49c54992b4b2656345a5e878b32
Gitweb:
https://git.kernel.org/tip/fdc63ff0e49c54992b4b2656345a5e878b32
Author:Konstantin Khlebnikov
AuthorDate:Wed, 08 Apr 2020 21:13:10 +03:00
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 2ed6edd33a214bca02bd2b45e3fc3038a059436b
Gitweb:
https://git.kernel.org/tip/2ed6edd33a214bca02bd2b45e3fc3038a059436b
Author:Barret Rhoden
AuthorDate:Tue, 14 Apr 2020 18:29:20 -04:00
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 12ac6782a40ad7636b6ef45680741825b64ab221
Gitweb:
https://git.kernel.org/tip/12ac6782a40ad7636b6ef45680741825b64ab221
Author:Davidlohr Bueso
AuthorDate:Tue, 21 Apr 2020 21:07:39 -07:00
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: c84cb3735fd53c91101ccdb191f2e3331a9262cb
Gitweb:
https://git.kernel.org/tip/c84cb3735fd53c91101ccdb191f2e3331a9262cb
Author:Thomas Gleixner
AuthorDate:Mon, 27 Apr 2020 16:55:57 +02:00
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: c721b3f80faebc7891211fa82de303eebadfed15
Gitweb:
https://git.kernel.org/tip/c721b3f80faebc7891211fa82de303eebadfed15
Author:Alexandre Chartre
AuthorDate:Tue, 07 Apr 2020 09:31:35 +02:00
The following commit has been merged into the sched/core branch of tip:
Commit-ID: f38f12d1e0811c0ee59260b2bdadedf99e16c4af
Gitweb:
https://git.kernel.org/tip/f38f12d1e0811c0ee59260b2bdadedf99e16c4af
Author:Muchun Song
AuthorDate:Mon, 06 Apr 2020 15:47:50 +08:00
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: 089dd8e53126ebaf506e2dc0bf89d652c36bfc12
Gitweb:
https://git.kernel.org/tip/089dd8e53126ebaf506e2dc0bf89d652c36bfc12
Author:Peter Zijlstra
AuthorDate:Tue, 14 Apr 2020 12:36:16 +02:00
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 457d1f465778ccb5f14f7d7a62245e41d12a3804
Gitweb:
https://git.kernel.org/tip/457d1f465778ccb5f14f7d7a62245e41d12a3804
Author:Chen Yu
AuthorDate:Tue, 21 Apr 2020 18:50:43 +08:00
Committer:
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: 34fdce6981b96920ced4e0ee56e9db3fb03a33f0
Gitweb:
https://git.kernel.org/tip/34fdce6981b96920ced4e0ee56e9db3fb03a33f0
Author:Peter Zijlstra
AuthorDate:Wed, 22 Apr 2020 17:16:40 +02:00
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: 9e98d62aa7ea1375052895650f3e6d362336c5c9
Gitweb:
https://git.kernel.org/tip/9e98d62aa7ea1375052895650f3e6d362336c5c9
Author:Julien Thierry
AuthorDate:Fri, 27 Mar 2020 15:28:42
Committer:
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 64297f2b03cc7a6d0184a435f1b296beca1bedd1
Gitweb:
https://git.kernel.org/tip/64297f2b03cc7a6d0184a435f1b296beca1bedd1
Author:Peng Wang
AuthorDate:Sat, 11 Apr 2020 17:20:20 +08:00
Committer:
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: 7d989fcadd6e225a61d6490dd15bdbdfc8a53d5c
Gitweb:
https://git.kernel.org/tip/7d989fcadd6e225a61d6490dd15bdbdfc8a53d5c
Author:Peter Zijlstra
AuthorDate:Thu, 23 Apr 2020 13:22:10 +02:00
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: 13fab06d9a3ad3afdfd51c7f8f87f2ae28444648
Gitweb:
https://git.kernel.org/tip/13fab06d9a3ad3afdfd51c7f8f87f2ae28444648
Author:Alexandre Chartre
AuthorDate:Tue, 14 Apr 2020 12:36:11 +02:00
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: 87cf61fe848ca8ddf091548671e168f52e8a718e
Gitweb:
https://git.kernel.org/tip/87cf61fe848ca8ddf091548671e168f52e8a718e
Author:Alexandre Chartre
AuthorDate:Tue, 14 Apr 2020 12:36:10 +02:00
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: ab5130186d7476dcee0d4e787d19a521ca552ce9
Gitweb:
https://git.kernel.org/tip/ab5130186d7476dcee0d4e787d19a521ca552ce9
Author:Rick Edgecombe
AuthorDate:Wed, 22 Apr 2020 20:13:55 -07:00
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: ca3f0d80dd57c8828bfb5bc0bc79750ea7a1ba26
Gitweb:
https://git.kernel.org/tip/ca3f0d80dd57c8828bfb5bc0bc79750ea7a1ba26
Author:Peter Zijlstra
AuthorDate:Wed, 22 Apr 2020 17:03:22 +02:00
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: b490f45362002fef57996388e395efc974b013f4
Gitweb:
https://git.kernel.org/tip/b490f45362002fef57996388e395efc974b013f4
Author:Miroslav Benes
AuthorDate:Fri, 24 Apr 2020 16:30:42 +02:00
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: 8aa8eb2a8f5b3305a95f39957dd2b715fa668e21
Gitweb:
https://git.kernel.org/tip/8aa8eb2a8f5b3305a95f39957dd2b715fa668e21
Author:Alexandre Chartre
AuthorDate:Tue, 14 Apr 2020 12:36:12 +02:00
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: 7117f16bf460ef8cd132e6e80c989677397b4868
Gitweb:
https://git.kernel.org/tip/7117f16bf460ef8cd132e6e80c989677397b4868
Author:Peter Zijlstra
AuthorDate:Tue, 28 Apr 2020 19:37:01 +02:00
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: cc1ac9c792810b93783a7de344f428922af8d98c
Gitweb:
https://git.kernel.org/tip/cc1ac9c792810b93783a7de344f428922af8d98c
Author:Peter Zijlstra
AuthorDate:Thu, 16 Apr 2020 14:34:26 +02:00
The following commit has been merged into the objtool/core branch of tip:
Commit-ID: 1ff865e343c2b59469d7e41d370a980a3f972c71
Gitweb:
https://git.kernel.org/tip/1ff865e343c2b59469d7e41d370a980a3f972c71
Author:Peter Zijlstra
AuthorDate:Tue, 28 Apr 2020 19:57:59 +02:00
The following commit has been merged into the sched/core branch of tip:
Commit-ID: bf2c59fce4074e55d622089b34be3a6bc95484fb
Gitweb:
https://git.kernel.org/tip/bf2c59fce4074e55d622089b34be3a6bc95484fb
Author:Peter Zijlstra
AuthorDate:Wed, 01 Apr 2020 17:40:33 -04:00
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 36c5bdc4387056af3840adb4478c752faeb9d15e
Gitweb:
https://git.kernel.org/tip/36c5bdc4387056af3840adb4478c752faeb9d15e
Author:Valentin Schneider
AuthorDate:Wed, 15 Apr 2020 22:05:07 +01:00
The following commit has been merged into the sched/core branch of tip:
Commit-ID: d91cecc156620ec75d94c55369509c807c3d07e6
Gitweb:
https://git.kernel.org/tip/d91cecc156620ec75d94c55369509c807c3d07e6
Author:Chen Yu
AuthorDate:Tue, 21 Apr 2020 18:50:34 +08:00
Committer:
On 5/1/20 9:02 PM, Joe Perches wrote:
> On Fri, 2020-05-01 at 16:44 +0300, Denis Efremov wrote:
>> These patches are based on Willy's cleanup patches
>> https://lkml.org/lkml/2020/3/31/609.
>
> Maybe add pr_fmt and clean up a few messages so
> all the logging output is prefixed too.
>
Yes, I'm
The following commit has been merged into the perf/core branch of tip:
Commit-ID: 4bd30106ddb26d2304adc5bb7bd269825300440d
Gitweb:
https://git.kernel.org/tip/4bd30106ddb26d2304adc5bb7bd269825300440d
Author:Paul Gortmaker
AuthorDate:Wed, 08 Apr 2020 19:52:16 -04:00
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 9818427c6270a9ce8c52c8621026fe9cebae0f92
Gitweb:
https://git.kernel.org/tip/9818427c6270a9ce8c52c8621026fe9cebae0f92
Author:Valentin Schneider
AuthorDate:Wed, 15 Apr 2020 22:05:05 +01:00
From: Jason Gunthorpe
Since amdgpu does not use the snapshot mode of hmm_range_fault() a
successful return already proves that all entries in the pfns are
HMM_PFN_VALID, there is no need to check the return result of
hmm_device_entry_to_page().
Acked-by: Felix Kuehling
Signed-off-by: Jason
Hello,
On Fri, May 01, 2020 at 10:59:24AM -0700, Linus Torvalds wrote:
> Which kind of makes me want to point a finger at Tejun. But it's been
> mostly PeterZ touching this file lately..
Looks fine to me too. I don't quite understand the usecase tho. It looks
like all it's being used for is to
From: Jason Gunthorpe
This is just an alias for HMM_PFN_ERROR, nothing cares that the error was
because of a special page vs any other error case.
Acked-by: Felix Kuehling
Reviewed-by: Christoph Hellwig
Signed-off-by: Jason Gunthorpe
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 1 -
From: Jason Gunthorpe
hmm_vma_walk->last is supposed to be updated after every write to the
pfns, so that it can be returned by hmm_range_fault(). However, this is
not done consistently. Fortunately nothing checks the return code of
hmm_range_fault() for anything other than error.
More
From: Jason Gunthorpe
The API is a bit complicated for the uses we actually have, and
disucssions for simplifying have come up a number of times.
This small series removes the customizable pfn format and simplifies the
return code of hmm_range_fault()
All the drivers are adjusted to process in
From: Jason Gunthorpe
Presumably the intent here was that hmm_range_fault() could put the data
into some HW specific format and thus avoid some work. However, nothing
actually does that, and it isn't clear how anything actually could do that
as hmm_range_fault() provides CPU addresses which must
From: Jason Gunthorpe
There is no reason for a user to select this or not directly - it should
be selected by drivers that are going to use the feature, similar to how
CONFIG_HMM_MIRROR works.
Currently all drivers provide a feature kconfig that will disable use of
DEVICE_PRIVATE in that
Introduce a device tree layer for to read and store ima buffer
from the reserved memory section of a device tree.
Signed-off-by: Prakhar Srivastava
---
drivers/of/Kconfig | 6 ++
drivers/of/Makefile | 1 +
drivers/of/of_ima.c | 165
Add support for ima buffer pass using reserved memory for
arm64 kexec. Update the arch sepcific code path in kexec file load to store
the ima buffer in the reserved memory. The same reserved memory is read on
kexec or cold boot.
Signed-off-by: Prakhar Srivastava
---
arch/arm64/Kconfig
IMA during kexec(kexec file load) verifies the kernel signature and measures
the signature of the kernel. The signature in the logs can be used to verfiy
the
authenticity of the kernel. The logs don not get carried over kexec and thus
remote attesation cannot verify the signature of the running
Hi,
On Fri, May 1, 2020 at 9:20 AM Daniel Thompson
wrote:
>
> flush_icache_range() contains a bodge to avoid issuing IPIs when the kgdb
> trap handler is running because issuing IPIs is unsafe (and unnecessary)
> in this exection context. However the current test is flawed: it both
> Currently there is a check if priv is null when calling lbtf_remove_card
> but not in a previous call to if_usb_reset_dev that can also dereference
> priv. Fix this by also only calling lbtf_remove_card if priv is null.
I suggest to recheck this description (and the corresponding patch
Working status: I added fixed_phy support to the Microchip lan743x ethernet
driver and for upstream contribution I need to make it runtime configurable via
the device tree.
Question:
There are, amongst other, the following devices on my target (i.mx6):
/soc/aips-bus@210/ethernet@2188000
On 01.05.20 20:03, Dan Williams wrote:
> On Fri, May 1, 2020 at 10:51 AM David Hildenbrand wrote:
>>
>> On 01.05.20 19:45, David Hildenbrand wrote:
>>> On 01.05.20 19:39, Dan Williams wrote:
On Fri, May 1, 2020 at 10:21 AM David Hildenbrand wrote:
>
> On 01.05.20 18:56, Dan Williams
On 5/1/20 12:55 PM, Dan Murphy wrote:
Sebastian
On 5/1/20 12:24 PM, Sebastian Reichel wrote:
Hi,
I don't see any PATCHv5 (with or without RESEND) for bq25150 and
lore does not see anything either:
https://lore.kernel.org/linux-pm/?q=PATCH+v5+0%2F3%5D+BQ25150%2F155+Charger
I posted them
On Thu, Apr 30, 2020 at 04:10:16PM -0600, Jason A. Donenfeld wrote:
> Sometimes it's not okay to use SIMD registers, the conditions for which
> have changed subtly from kernel release to kernel release. Usually the
> pattern is to check for may_use_simd() and then fallback to using
> something
On Thu, Apr 30, 2020 at 12:25 PM Bjorn Andersson
wrote:
>
> rd_full should be defined outside the CONFIG_DEBUG_FS region, in order
> to be able to link the msm driver even when CONFIG_DEBUG_FS is disabled.
>
> Fixes: e515af8d4a6f ("drm/msm: devcoredump should dump MSM_SUBMIT_BO_DUMP
> buffers")
On Fri, 1 May 2020, Mickaël Salaün wrote:
>
> However, for fully controlled distros such as CLIP OS, it make sense to
> enforce such restrictions at kernel build time. I can add an alternative
> kernel configuration to enforce a particular policy at boot and disable
> this sysctl.
Sounds good.
On Fri, May 1, 2020 at 10:51 AM David Hildenbrand wrote:
>
> On 01.05.20 19:45, David Hildenbrand wrote:
> > On 01.05.20 19:39, Dan Williams wrote:
> >> On Fri, May 1, 2020 at 10:21 AM David Hildenbrand wrote:
> >>>
> >>> On 01.05.20 18:56, Dan Williams wrote:
> On Fri, May 1, 2020 at 2:34
Sebastian
On 5/1/20 12:24 PM, Sebastian Reichel wrote:
Hi,
I don't see any PATCHv5 (with or without RESEND) for bq25150 and
lore does not see anything either:
https://lore.kernel.org/linux-pm/?q=PATCH+v5+0%2F3%5D+BQ25150%2F155+Charger
I posted them for Ricardo. Maybe he need a lore
On Fri, 2020-05-01 at 16:44 +0300, Denis Efremov wrote:
> These patches are based on Willy's cleanup patches
> https://lkml.org/lkml/2020/3/31/609.
Maybe add pr_fmt and clean up a few messages so
all the logging output is prefixed too.
---
drivers/block/floppy.c | 11 ++-
1 file
From: Ricardo Rivera-Matos
Description:
The BQ2515X family of devices are highly integrated battery management
ICs that integrate the most common functions for wearbale devices
namely a charger, an output voltage rail, ADC for battery and system
monitoring, and a push-button controller.
From: Ricardo Rivera-Matos
Introduce the bq2515x family of chargers.
Description:
The BQ2515X family of devices are highly integrated battery management
ICs that integrate the most common functions for wearbale devices
namely a charger, an output voltage rail, ADC for battery and system
IMHO it would be better to use switch case here to improve readability.
switch (bmcr & mask) {
case BMCR_SPEED1000:
speed = SPEED_1000;
break;
case BMCR_SPEED100:
speed = SPEED_100;
On Fri, May 1, 2020 at 9:02 AM J. Bruce Fields wrote:
>
> Anyway, does this multiple kthreadd approach look reasonable?
I don't see anything that looks alarming.
My main reaction was that I don't like the "kthreadd" name, but that's
because for some reason I always read it as "kthre add". That
Hello,
Resending for Ricardo
This v5 series picks up on the development that Dan Murphy
began with the power_supply framework and bq2515x_charger driver.
This series incorporates the changes suggested by
Sebastien Reichel in v4.
Datasheets for these devices can be found at:
On Wed, Apr 29, 2020 at 05:08:32PM +0200, Arnaud POULIQUEN wrote:
> Hi Mathieu,
>
> On 4/24/20 10:24 PM, Mathieu Poirier wrote:
> > This patchset needs to be applied on top of this one [1].
> >
> > It refactors the STM32 platform code in order to introduce support for
> > synchronising with the
Add HEALTH_WARM, HEALTH_COOL and HEALTH_HOT to the health enum.
Tested-by: Guru Das Srinagesh
Signed-off-by: Dan Murphy
---
Documentation/ABI/testing/sysfs-class-power | 2 +-
drivers/power/supply/power_supply_sysfs.c | 2 +-
include/linux/power_supply.h| 3 +++
3 files
On 2020-04-30 22:12, Can Guo wrote:
> diff --git a/drivers/scsi/scsi_pm.c b/drivers/scsi/scsi_pm.c
> index 3717eea..d18271d 100644
> --- a/drivers/scsi/scsi_pm.c
> +++ b/drivers/scsi/scsi_pm.c
> @@ -74,12 +74,15 @@ static int scsi_dev_type_resume(struct device *dev,
> {
> const struct
On 5/1/20 11:53 AM, Jens Axboe wrote:
> eventfd is using ->read() as it's file_operations read handler, but
> this prevents passing in information about whether a given IO operation
> is blocking or not. We can only use the file flags for that. To support
> async (-EAGAIN/poll based) retries for
eventfd is using ->read() as it's file_operations read handler, but
this prevents passing in information about whether a given IO operation
is blocking or not. We can only use the file flags for that. To support
async (-EAGAIN/poll based) retries for io_uring, we need ->read_iter()
support.
On Wed, Apr 29, 2020 at 04:47:19PM +0200, Arnaud POULIQUEN wrote:
>
>
> On 4/24/20 10:25 PM, Mathieu Poirier wrote:
> > Set the flags and operations to use if the M4 has been started
> > by another entity than the remoteproc core.
> >
> > Signed-off-by: Mathieu Poirier
> > ---
> >
eventfd is using ->read() as it's file_operations read handler, but
this prevents passing in information about whether a given IO operation
is blocking or not. We can only use the file flags for that. To support
async (-EAGAIN/poll based) retries for io_uring, we need ->read_iter()
support.
eventfd is using ->read() as it's file_operations read handler, but
this prevents passing in information about whether a given IO operation
is blocking or not. We can only use the file flags for that. To support
async (-EAGAIN/poll based) retries for io_uring, we need ->read_iter()
support.
On 01.05.20 19:45, David Hildenbrand wrote:
> On 01.05.20 19:39, Dan Williams wrote:
>> On Fri, May 1, 2020 at 10:21 AM David Hildenbrand wrote:
>>>
>>> On 01.05.20 18:56, Dan Williams wrote:
On Fri, May 1, 2020 at 2:34 AM David Hildenbrand wrote:
>
> On 01.05.20 00:24, Andrew
On Fri, May 01, 2020 at 07:26:16PM +0200, Peter Zijlstra wrote:
> On Fri, May 01, 2020 at 07:21:31PM +0200, Arnd Bergmann wrote:
> > On Thu, Apr 30, 2020 at 4:05 PM Arnd Bergmann wrote:
> > it gets into undefined behavior and stops emitting code after the call to
>
> > Do we consider this
On Fri, May 1, 2020 at 4:35 AM Jiri Olsa wrote:
>
> From: Jiri Olsa
>
> Ian came with the idea of having support to read the pipe
> data also from file [1]. Currently pipe mode files fails
> like:
>
> $ perf record -o - sleep 1 > /tmp/perf.pipe.data
> $ perf report -i /tmp/perf.pipe.data
>
On 5/1/20 11:43 AM, Al Viro wrote:
> On Fri, May 01, 2020 at 11:18:05AM -0600, Jens Axboe wrote:
>
>> -if (res > 0 && put_user(ucnt, (__u64 __user *)buf))
>> +if (res > 0 && copy_to_iter(, res, iov) < res)
>
> *whoa*
>
> It is correct, but only because here res > 0 <=> res == 8.
> And
On 01.05.20 19:39, Dan Williams wrote:
> On Fri, May 1, 2020 at 10:21 AM David Hildenbrand wrote:
>>
>> On 01.05.20 18:56, Dan Williams wrote:
>>> On Fri, May 1, 2020 at 2:34 AM David Hildenbrand wrote:
On 01.05.20 00:24, Andrew Morton wrote:
> On Thu, 30 Apr 2020 20:43:39 +0200
On Fri, May 01, 2020 at 11:18:05AM -0600, Jens Axboe wrote:
> - if (res > 0 && put_user(ucnt, (__u64 __user *)buf))
> + if (res > 0 && copy_to_iter(, res, iov) < res)
*whoa*
It is correct, but only because here res > 0 <=> res == 8.
And that's not trivial at the first glance.
Please,
On Wed, Apr 29, 2020 at 03:38:24PM +0200, Arnaud POULIQUEN wrote:
>
>
> On 4/24/20 10:24 PM, Mathieu Poirier wrote:
> > Introduce the required mechanic to get the state of the M4 when the
> > remoteproc core is initialising.
> >
> > Mainly based on the work published by Arnaud Pouliquen [1].
>
On Fri, May 1, 2020 at 3:35 AM Jiri Olsa wrote:
>
> On Thu, Apr 30, 2020 at 12:51:32AM -0700, Ian Rogers wrote:
> > Add a test that all perf metrics (for your architecture) are parsable
> > with the simple expression parser. Attempt to parse all events in
> > metrics but only fail if the metric
On Fri, May 1, 2020 at 10:21 AM David Hildenbrand wrote:
>
> On 01.05.20 18:56, Dan Williams wrote:
> > On Fri, May 1, 2020 at 2:34 AM David Hildenbrand wrote:
> >>
> >> On 01.05.20 00:24, Andrew Morton wrote:
> >>> On Thu, 30 Apr 2020 20:43:39 +0200 David Hildenbrand
> >>> wrote:
> >>>
>
From: Colin Ian King
Currently there is a check if priv is null when calling lbtf_remove_card
but not in a previous call to if_usb_reset_dev that can also dereference
priv. Fix this by also only calling lbtf_remove_card if priv is null.
It is noteable that there don't seem to be any bugs
Hi Xia,
On Thu, Apr 16, 2020 at 12:03:15PM +0800, Xia Jiang wrote:
> On Fri, 2020-03-06 at 20:23 +0900, Tomasz Figa wrote:
> > Hi Xia,
> >
> > On Tue, Mar 03, 2020 at 08:34:46PM +0800, Xia Jiang wrote:
> > > Add mtk jpeg encode v4l2 driver based on jpeg decode, because that jpeg
> > > decode and
On Fri, May 1, 2020 at 4:53 PM James Bottomley wrote:
> On Fri, 2020-05-01 at 09:54 +0200, Arnd Bergmann wrote:
> > On Fri, May 1, 2020 at 9:48 AM John Garry
> > wrote:
> > I found one hack that would work, but I think it's too ugly and
> > likely not well-defined either:
> >
> > struct
Convert the power_supply.txt to power-supply.yaml.
This conversion entailed fixing up the binding to being yaml and dt
checker compliant.
Added a note in the power_supply.txt to reference the power-supply.yaml
Signed-off-by: Dan Murphy
---
.../bindings/power/supply/power-supply.yaml | 40
On Wed, Apr 22, 2020 at 05:37:34PM -0700, Bjorn Andersson wrote:
> Rather than carrying a special purpose blocking notifier for glink_ssr
> in remoteproc's qcom_common.c, move it into glink_ssr so allow wider
> reuse of the common one.
After reading the changelog and the cover letter a few times
Hi,
On Fri, May 1, 2020 at 6:32 AM Daniel Thompson
wrote:
>
> On Fri, May 01, 2020 at 12:49:43PM +0100, Daniel Thompson wrote:
> > On Thu, Apr 30, 2020 at 09:59:09AM -0700, Douglas Anderson wrote:
> > > The original implementation of kgdboc_earlycon included a comment
> > > about how it was
Hi,
On Fri, May 1, 2020 at 4:49 AM Daniel Thompson
wrote:
>
> On Thu, Apr 30, 2020 at 09:59:09AM -0700, Douglas Anderson wrote:
> > The original implementation of kgdboc_earlycon included a comment
> > about how it was impossible to get notified about the boot console
> > going away without
On Fri, 2020-05-01 at 12:16 -0500, Bjorn Helgaas wrote:
> On Thu, Apr 30, 2020 at 12:46:07PM -0600, Jon Derrick wrote:
> > Hi Bjorn & Kuppuswamy,
> >
> > I see a problem in the DPC ECN [1] to _OSC in that it doesn't give us a way
> > to
> > determine if firmware supports _OSC DPC negotation, and
Remove over escaping with \\.
Fixes: fd5500989c8f (perf vendor events intel: Update metrics from TMAM 3.5)
Signed-off-by: Ian Rogers
---
tools/perf/pmu-events/arch/x86/skylakex/skx-metrics.json | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Add a basic floating point number test to expr.
Break pmu-events test into 2 and add a test to verify that all pmu metric
expressions simply parse. Try to parse all metric ids/events, failing if
metrics for the current architecture fail to parse.
Tested on skylakex with the patch set in place.
If an expression yields 0 and is then divided-by/modulus-by then the
parsing aborts. Add a debug error message to better enable debugging
when this happens.
Signed-off-by: Ian Rogers
---
tools/perf/util/expr.y | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git
Mismatched parentheses.
Fixes: 7f3cf5ac7743 (perf vendor events power9: Cpi_breakdown &
estimated_dcache_miss_cpi metrics)
Reviewed-by: Paul A. Clarke
Signed-off-by: Ian Rogers
---
tools/perf/pmu-events/arch/powerpc/power9/metrics.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On a CPU like skylakex an uncore_iio_0 PMU may alias with
uncore_iio_free_running_0. The latter PMU doesn't support fc_mask
as a parameter and so pmu_config_term fails. Typically
parse_events_add_pmu is called in a loop where if one alias succeeds
errors are ignored, however, if multiple errors
Mismatched parentheses.
Fixes: dd81eafacc52 (perf vendor events power8: Cpi_breakdown &
estimated_dcache_miss_cpi metrics)
Reviewed-by: Paul A. Clarke
Signed-off-by: Ian Rogers
---
tools/perf/pmu-events/arch/powerpc/power8/metrics.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Only effects parser debugging (disabled by default). Enables displaying
'--accepting rule at line .. ("...").
Signed-off-by: Ian Rogers
---
tools/perf/util/expr.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/util/expr.c b/tools/perf/util/expr.c
index aa631e37ad1e..8b4ce704a68d
Large metrics such as Branch_Misprediction_Cost_SMT on x86 broadwell
need more space.
Signed-off-by: Ian Rogers
---
tools/perf/util/expr.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/expr.h b/tools/perf/util/expr.h
index 87d627bb699b..40fc452b0f2b 100644
Add a test that all perf metrics (for your architecture) are parsable
with the simple expression parser. Attempt to parse all events in
metrics but only fail if the metric is for the current CPU. Fix bugs
in the expr parser, x86 and powerpc metrics. Improve debug messages
around add PMU config
This is expected in expr.y and metrics use floating point values such as
x86 broadwell IFetch_Line_Utilization.
Fixes: 26226a97724d (perf expr: Move expr lexer to flex)
Signed-off-by: Ian Rogers
---
tools/perf/util/expr.l | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
Current expression allows 2 escaped '-,=' characters. However, some
metrics require more, for example Haswell DRAM_BW_Use.
Fixes: 26226a97724d (perf expr: Move expr lexer to flex)
Signed-off-by: Ian Rogers
---
tools/perf/util/expr.l | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
401 - 500 of 1490 matches
Mail list logo