4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Yegor Yefremov
commit befa60113ce7ea270cb51eada28443ca2756f480 upstream.
In order to make the driver work with the common clock framework, this
patch converts the clk_enable()/clk_disable() to
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Yegor Yefremov
commit befa60113ce7ea270cb51eada28443ca2756f480 upstream.
In order to make the driver work with the common clock framework, this
patch converts the clk_enable()/clk_disable() to
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Vineet Gupta
commit 36425cd67052e3becf325fd4d3ba5691791ef7e4 upstream.
commit 3c7c7a2fc8811bc ("ARC: Don't use "+l" inline asm constraint")
modified the inline assembly to setup LP_COUNT regist
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jack Morgenstein
commit b4cfe3971f6eab542dd7ecc398bfa1aeec889934 upstream.
If IPV6 has not been enabled in the underlying kernel, we must avoid
calling IPV6 procedures in rdma_cm.ko.
This requ
Hi,
On Tue, Jan 31, 2017 at 04:02:41AM +0100, Sebastian Reichel wrote:
> On Wed, Jan 25, 2017 at 02:23:38PM -0600, Rob Herring wrote:
> > Here's V3 of the serdev bus support with all the review feedback so far
> > incorporated. Greg applied the first 4 patches already. I also found a
> > problem i
On Mon 30 Jan 07:03 PST 2017, Avaneesh Kumar Dwivedi wrote:
> This patch add additional clock and regulator resource which are
> initialized based on compatible and has no impact on existing driver
> working. This resourse addition enable the existing driver to handle.
> low pass sensor processor
This is the start of the stable review cycle for the 4.9.7 release.
There are 66 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Thu Feb 2 05:35:45 UTC 2017.
Anything received
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Vineet Gupta
commit 9aed02feae57bf7a40cb04ea0e3017cb7a998db4 upstream.
After emulating an unaligned access in delay slot of a branch, we
pretend as the delay slot never happened - so return bac
+CC Greg, LKML as I don't quite know where this should go.
On 01/18/2017 12:16 AM, Marek Vasut wrote:
> I believe there is a possible race condition when configfs attributes
> trigger filp_open() from the kernel. I initially observed the problem
> on Linux 4.4 when loading DT overlay , which in tu
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jack Morgenstein
commit b4cfe3971f6eab542dd7ecc398bfa1aeec889934 upstream.
If IPV6 has not been enabled in the underlying kernel, we must avoid
calling IPV6 procedures in rdma_cm.ko.
This requ
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Martin Schwidefsky
commit 9dce990d2cf57b5ed4e71a9cdbd7eae4335111ff upstream.
Ensure that if userspace supplies insufficient data to
PTRACE_SETREGSET to fill all the registers, the thread's old
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Rientjes
commit 3674534b775354516e5c148ea48f51d4d1909a78 upstream.
When memory.move_charge_at_immigrate is enabled and precharges are
depleted during move, mem_cgroup_move_charge_pte_rang
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 950eabbd6ddedc1b08350b9169a6a51b130ebaaf upstream.
With some gcc versions, we get a warning about the eicon driver,
and that currently shows up as the only remaining warnin
On Mon 30 Jan 07:03 PST 2017, Avaneesh Kumar Dwivedi wrote:
> This patch initialize certain driver related data based on compatible
> string. This enable driver to handle more than one similar device in
> by differentiating in probe their private data.
>
> Signed-off-by: Avaneesh Kumar Dwivedi
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Vlastimil Babka
commit d51e9894d27492783fc6d1b489070b4ba66ce969 upstream.
Since commit be97a41b291e ("mm/mempolicy.c: merge alloc_hugepage_vma to
alloc_pages_vma") alloc_pages_vma() can potenti
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Francisco Jerez
commit 4fc020d864647ea3ae8cb8f17d63e48e87ebd0bf upstream.
The WaDisableLSQCROPERFforOCL workaround has the side effect of
disabling an L3SQ optimization that has huge performanc
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Helge Deller
commit 2ad5d52d42810bed95100a3d912679d8864421ec upstream.
In swab.h the "#if BITS_PER_LONG > 32" breaks compiling userspace programs if
BITS_PER_LONG is #defined by userspace with
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Israel Rukshin
commit 0a475ef4226e305bdcffe12b401ca1eab06c4913 upstream.
After setting indirect_sg_entries module_param to huge value (e.g 500,000),
srp_alloc_req_data() fails to allocate indir
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Israel Rukshin
commit ad8e66b4a80182174f73487ed25fd2140cf43361 upstream.
If the device support arbitrary sg list mapping (device cap
IB_DEVICE_SG_GAPS_REG set) we allocate the memory regions wi
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Laurent Pinchart
commit aff808e813fc2d311137754165cf53d4ee6ddcc2 upstream.
The tvp5150 doesn't support format setting through the subdev pad API
and thus implements the set format handler as a
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Christian Borntraeger
commit 0d6da872d3e4a60f43c295386d7ff9a4cdcd57e9 upstream.
The last pgtable rework silently disabled the CMMA unused state by
setting a local pte variable (a parameter) ins
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Maor Gottlieb
commit f39f775218a7520e3700de2003c84a042c3b5972 upstream.
The first argument of list_add_tail is the new item and the second
is the head of the list. Fix the code to pass argument
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Wilson
commit e88893fea17996018b2d68a22e677ea04f3baadf upstream.
Missed when rebasing patches, I failed to set ret to zero before
starting the unbind loop (which depends upon ret being ze
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Clint Taylor
commit 27892bbdc9233f33bf0f44e08aab8f12e0dec142 upstream.
The .disable_display parameter was causing a fatal crash when fbdev
was dereferenced during driver init.
V1: protection i
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Steve Wise
commit c12a67fec8d99bb554e8d4e99120d418f1a39c87 upstream.
Commit ad61a4c7a9b7 ("iw_cxgb4: don't block in destroy_qp awaiting
the last deref") introduced a bug where the RDMA QP EQ qu
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Martin Schwidefsky
commit 9dce990d2cf57b5ed4e71a9cdbd7eae4335111ff upstream.
Ensure that if userspace supplies insufficient data to
PTRACE_SETREGSET to fill all the registers, the thread's old
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Mika Westerberg
commit ecc8995363ee6231b32dad61c955b371b79cc4cf upstream.
PADCFGLOCK (and PADCFGLOCK_TX) offset in Broxton actually starts at 0x060
and not 0x090 as used in the driver. Fix it t
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Laurent Pinchart
commit b4b2de386bbb6589d81596999d4a924928dc119b upstream.
The FID/GLCO/VLK/HVLK and INTREQ/GPCL/VBLK pins are muxed differently
depending on whether the input is an S-Video or
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Chuck Lever
commit 059aa734824165507c65fd30a55ff000afd14983 upstream.
Xuan Qi reports that the Linux NFSv4 client failed to lock a file
that was migrated. The steps he observed on the wire:
1.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Kenneth Lee
commit 828f6fa65ce7e80f77f5ab12942e44eb3d9d174e upstream.
1. Release pid before enter odp flow
2. Release pid when fail to allocate memory
Fixes: 87773dd56d54 ("IB: ib_umem_release
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Masahiro Yamada
commit df1539c25cce98e2ac69881958850c6535240707 upstream.
Fix the pin-mux values for the MDC, MDIO, MDIO_INTL, PHYRSTL pins.
Fixes: 1e359ab1285e ("pinctrl: uniphier: add Ethern
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Benjamin Coddington
commit a430607b2ef7c3be090f88c71cfcb1b3988aa7c0 upstream.
Some nfsv4.0 servers may return a mode for the verifier following an open
with EXCLUSIVE4 createmode, but this does
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Vineet Gupta
commit 9aed02feae57bf7a40cb04ea0e3017cb7a998db4 upstream.
After emulating an unaligned access in delay slot of a branch, we
pretend as the delay slot never happened - so return bac
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Helge Deller
commit 2ad5d52d42810bed95100a3d912679d8864421ec upstream.
In swab.h the "#if BITS_PER_LONG > 32" breaks compiling userspace programs if
BITS_PER_LONG is #defined by userspace with
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Anholt
commit 6b8ac63847bc2f958dd93c09edc941a0118992d9 upstream.
By failing to set the errno, we'd continue on to trying to set up the
RCL, and then oops on trying to dereference the tile_
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
commit ff9f8a7cf935468a94d9927c68b00daae701667e upstream.
We perform the conversion between kernel jiffies and ms only when
exporting kernel value to user space.
We need to do the
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Vineet Gupta
commit 36425cd67052e3becf325fd4d3ba5691791ef7e4 upstream.
commit 3c7c7a2fc8811bc ("ARC: Don't use "+l" inline asm constraint")
modified the inline assembly to setup LP_COUNT regist
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Nikolay Borisov
commit 880a38547ff08715ce4f1daf9a4bb30c87676e68 upstream.
The ucounts_lock is being used to protect various ucounts lifecycle
management functionalities. However, those services
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 21ccc32496b2f63228f5232b3ac0e426e8fb3c31 upstream.
We accidentally return success even if vc4_full_res_bounds_check() fails.
Fixes: d5b1a78a772f ("drm/vc4: Add support for
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Martin
commit fd7c99142d77dc4a851879a66715abf12a3193fb upstream.
Ensure that if userspace supplies insufficient data to
PTRACE_SETREGSET to fill all the registers, the thread's old
registe
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Will Deacon
commit c7070619f3408d9a0dffbed9149e6f00479cf43b upstream.
Booting Linux on an ARM fastmodel containing an SMMU emulation results
in an unexpected I/O page fault from the legacy virt
On Sat, Jan 28, 2017 at 10:52 PM, Jonathan Cameron wrote:
> On 27/01/17 08:54, Quentin Schulz wrote:
>> This maps the IIO channels batt_v, batt_chrg_i and batt_dischrg_i
>> (respectively exposing the current charging and discharging currents and
>> current voltage measures of the battery power sup
On Mon, Jan 30, 2017 at 10:00:34PM +0100, Alexandre Belloni wrote:
> Arnd, Olof,
>
> Here are two patches worth taking as fixes for 4.10. They change the
> email addresses for Nicolas and Ludovic in MAINTAINERS so
> get_maintainers can point to the correct ones.
>
> The following changes since co
On Mon, Jan 30, 2017 at 07:57:20PM +0200, Krzysztof Kozlowski wrote:
> On Sun, Jan 29, 2017 at 09:23:29PM -0800, Olof Johansson wrote:
> > Hi Krzysztof,
> >
> > On Sun, Jan 29, 2017 at 10:06:29PM +0200, Krzysztof Kozlowski wrote:
> > > Hi,
> > >
> > > On top of previous pull request.
> > >
> > >
Hi Marc,
On Mon, Jan 30, 2017 at 08:53:09AM +, Marc Zyngier wrote:
> ARM-soc folks,
>
> Please find below the pull request for a DT fix affecting a large
> number of 32bit platforms, which has been acked by a number of
> platform maintainers.
>
> * From v1: Dropped the controvertial cortex-
On Fri, Jan 27, 2017 at 4:54 PM, Quentin Schulz
wrote:
> The CHRG_CTRL1 and CHRG_CTRL2 registers are made for controlling
> different battery charging settings such as the constant current charge
> value.
>
> The AXP22X also have a third register CHRG_CTRL3 which has settings for
> battery chargin
From: Bjorn Andersson
Implement support for initialization of the lm3533 LED driver from
Device Tree.
Signed-off-by: Bjorn Andersson
Signed-off-by: Bjorn Andersson
---
Note that this patch can be merged independently of the other patches in the
series.
Changes since v5:
- None
Changes since
From: Bjorn Andersson
Implement support for initialization of the lm3533 driver core and
probing child devices from Device Tree.
Signed-off-by: Bjorn Andersson
Signed-off-by: Bjorn Andersson
---
drivers/mfd/lm3533-core.c | 82 +++
1 file changed, 82
From: Bjorn Andersson
Implement support for initialization of the lm3533 als driver from
Device Tree.
Signed-off-by: Bjorn Andersson
Signed-off-by: Bjorn Andersson
---
Note that this patch can be merged independently of the other patches in the
series.
Changes since v5:
- None
Changes since
From: Bjorn Andersson
Add the binding for the Texas Instruments LM3533 lighting power
solution.
Acked-by: Jonathan Cameron
Acked-by: Rob Herring
Acked-for-MFD-by: Lee Jones
Signed-off-by: Bjorn Andersson
Signed-off-by: Bjorn Andersson
---
Changes since v5:
- None
Changes since v4:
- Acks
From: Bjorn Andersson
Implement support for initialization of the lm3533 backlight from Device
Tree.
Acked-by: Jingoo Han
Acked-by: Pavel Machek
Signed-off-by: Bjorn Andersson
Signed-off-by: Bjorn Andersson
---
Note that this patch can be merged independently of the other patches in the
ser
> On 31 January 2017 at 01:30 "Darrick J. Wong" wrote:
>
>
> On Mon, Jan 30, 2017 at 07:48:44PM +0100, Fabian Frederick wrote:
> > instead of atomic_add_unless(value, -1, 0)
> >
> > Signed-off-by: Fabian Frederick
> > ---
> > fs/xfs/xfs_buf.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 delet
On 01/30/2017 11:21 PM, Dave Hansen wrote:
> Here's the flag definition:
>
>> +#ifdef CONFIG_COHERENT_DEVICE
>> +#define VM_CDM 0x0080 /* Contains coherent device
>> memory */
>> +#endif
>
> But it doesn't match the implementation:
>
>> +#ifdef CONFIG_COHERENT_DEVICE
>> +s
On Fri, Jan 27, 2017 at 4:54 PM, Quentin Schulz
wrote:
> The NextThing Co. CHIP has an AXP209 PMIC and can be power-supplied by
> ACIN via the CHG-IN pin.
>
> This enables the ACIN power supply subnode in the DT.
>
> Signed-off-by: Quentin Schulz
Acked-by: Chen-Yu Tsai
Clean up the clock calling code by removing numerous IS_ERR() checks by
just assigning the clock NULL; as this turn all used functions in the
clk API to nops.
Also include the word "optional" in the error message when failing to acquire
the optional osr clocks.
Cc: Banajit Goswami
Cc: Patrick La
On Mon, Jan 30, 2017 at 12:35 AM, Sebastian Reichel wrote:
> Hi,
>
> On Fri, Jan 27, 2017 at 09:54:44AM +0100, Quentin Schulz wrote:
>> The X-Powers AXP20X and AXP22X PMICs expose the status of AC power
>> supply.
>>
>> This adds the AC power supply driver to the MFD cells of the AXP22X
>> PMICs.
> -Original Message-
> From: Masanari Iida [mailto:standby2...@gmail.com]
> Sent: Sunday, January 29, 2017 9:33 PM
> To: linux-kernel@vger.kernel.org; gre...@linuxfoundation.org; Kershner,
> David A ; de...@driverdev.osuosl.org
> Cc: Masanari Iida
> Subject: [PATCH] [linux-next]staging: un
On 01/30/2017 11:24 PM, Dave Hansen wrote:
> On 01/29/2017 07:35 PM, Anshuman Khandual wrote:
>> +if ((new_pol->mode == MPOL_BIND)
>> +&& nodemask_has_cdm(new_pol->v.nodes))
>> +set_vm_cdm(vma);
> So, if you did:
>
> mbind(addr, PAGE_SIZE,
On Fri, Jan 27, 2017 at 4:54 PM, Quentin Schulz
wrote:
> The X-Powers AXP22X PMIC exposes the status of AC power supply.
>
> This adds the AC power supply subnode for the AXP22X PMIC.
>
> Signed-off-by: Quentin Schulz
Acked-by: Chen-Yu Tsai
Since the core doesn't deal with cputime_t anymore, most of these APIs
have been left unused. Lets remove these.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc
On 01/31/2017 12:22 AM, Jerome Glisse wrote:
> On Mon, Jan 30, 2017 at 09:05:49AM +0530, Anshuman Khandual wrote:
>> VMA which contains CDM memory pages should be marked with new VM_CDM flag.
>> These VMAs need to be identified in various core kernel paths for special
>> handling and this flag will
On Fri, Jan 27, 2017 at 4:54 PM, Quentin Schulz
wrote:
> The X-Powers AXP20X PMIC exposes the status of AC power supply, the
> current current and voltage supplied to the board by the AC power
> supply.
>
> This adds the AC power supply subnode for AXP20X PMIC.
>
> Signed-off-by: Quentin Schulz
Use the new nsec based cputime accessors as part of the whole cputime
conversion from cputime_t to nsecs.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thoma
On Fri, Jan 27, 2017 at 4:54 PM, Quentin Schulz
wrote:
> X-Powers AXP209 PMIC has multiple ADCs, each one exposing data from the
> different power supplies connected to the PMIC.
>
> This adds the ADC subnode for AXP20X PMIC.
>
> Signed-off-by: Quentin Schulz
Given the device node no longer expo
On Mon, 2017-01-30 at 17:44 +0100, Greg Kroah-Hartman wrote:
> On Mon, Jan 30, 2017 at 11:31:42AM -0500, Maksymilian Piechota wrote:
> > This patch fixes the checkpatch.pl warning:
> >
> > WARNING: Statements should start on a tabstop
> >
> > Signed-off-by: Maksymilian Piechota
> > ---
> > driv
On Mon, Jan 30, 2017 at 7:49 PM, Michael Kerrisk wrote:
> [CC += linux-api@]
>
> Andy, this is an API change!
Indeed. I should be ashamed of myself!
>
> On Sat, Jan 28, 2017 at 3:49 PM, Andy Lutomirski wrote:
>> The kernel has some dangerous behavior involving the creation and
>> modification
[CC += linux-api@]
Andy, this is an API change!
On Sat, Jan 28, 2017 at 3:49 PM, Andy Lutomirski wrote:
> The kernel has some dangerous behavior involving the creation and
> modification of setgid executables. These issues aren't kernel
> security bugs per se, but they have been used to turn va
On Tue, Jan 24, 2017 at 11:07:59AM -0700, Alex Williamson wrote:
> On Tue, 24 Jan 2017 17:50:26 +0100
> Greg Kurz wrote:
>
> > The recently added mediated VFIO driver doesn't know about powerpc iommu.
> > It thus doesn't register a struct iommu_table_group in the iommu group
> > upon device creat
[CC += linux-api@]
On Sat, Jan 28, 2017 at 3:49 PM, Andy Lutomirski wrote:
> If an unprivileged program opens a setgid file for write and passes
> the fd to a privileged program and the privileged program writes to
> it, we currently fail to clear the setgid bit. Fix it by checking
> f_cred in a
On Mon, Jan 30, 2017 at 7:41 PM, Philipp Zabel wrote:
> As of commit bb475230b8e5 ("reset: make optional functions really
> optional"), the reset framework API calls use NULL pointers to describe
> optional, non-present reset controls.
>
> This allows to return errors from devm_reset_control_get_o
On Mon, Jan 30, 2017 at 7:41 PM, Philipp Zabel wrote:
> As of commit bb475230b8e5 ("reset: make optional functions really
> optional"), the reset framework API calls use NULL pointers to describe
> optional, non-present reset controls.
>
> This allows to return errors from devm_reset_control_get_o
On Mon, Jan 30, 2017 at 9:27 PM, Maxime Ripard
wrote:
> We introduced recently a new compatible to deal with the A64 eMMC
> controller, let's document its binding.
>
> Signed-off-by: Maxime Ripard
Acked-by: Chen-Yu Tsai
[CC += linux-api@]
On Sat, Jan 28, 2017 at 3:49 PM, Andy Lutomirski wrote:
> Currently, if you open("foo", O_WRONLY | O_CREAT | ..., 02777) in a
> directory that is setgid and owned by a different gid than current's
> fsgid, you end up with an SGID executable that is owned by the
> directory's GI
Change sequences of 8 spaces to hard-tabs.
Signed-off-by: Chris Packham
---
I think this crept in during review and I didn't notice. The file is new enough
that we shouldn't lose any useful history.
arch/arm/boot/dts/armada-xp-98dx3236.dtsi | 14 +++---
1 file changed, 7 insertions(+),
The irqtime is accounted is nsecs and stored in
cpu_irq_time.hardirq_time and cpu_irq_time.softirq_time. Once the
accumulated amount reaches a new jiffy, this one gets accounted to the
kcpustat.
This was necessary when kcpustat was stored in cputime_t, which could at
worst have a jiffies granulari
This will be needed for the cputime_t to nsec conversion.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Stanislaw Grusz
This is the final step toward tick based cputime conversion. Now that
whole cputime accounting engine accounts in nsecs, we can convert the
very source of the cputime to account into nsec.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidef
Christian Kujau writes:
> On Mon, 16 Jan 2017, Christophe Leroy wrote:
>> Since 2005, powerpc GCC doesn't manage anymore __stack_chk_guard as
>> a global variable but as some value located at -0x7008(r2)
>
> Is this still an "RFC" or is there a chance that this will land in 4.10?
No. I've revert
cputime_t is being obsolete and replaced by nsecs units.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Stanislaw Gruszk
There is no need anymore for this cputime_t midlayer. Let's use nsec
units directly.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo
On Tue, Jan 31, 2017 at 02:23:55AM +0800, Icenowy Zheng wrote:
>
>
> 31.01.2017, 00:41, "Vinod Koul" :
> > On Sun, Jan 29, 2017 at 10:33:29AM +0800, Icenowy Zheng wrote:
> >> As 64-bit Allwinner H5 SoC has the same DMA engine with H3, the DMA
> >> driver should be allowed to be built for ARM64,
This API returns the tasks cputime in cputime_t in order to ease the
conversion of cputime internals to use nsecs units instead. Blindly
converting all cputime readers to use this API now will later let us
convert more smoothly and step by step all these places to use the
new nsec based cputime.
C
On Mon, Jan 30, 2017 at 06:47:21PM +0100, Boris Brezillon wrote:
> Hi Vinod,
>
> On Mon, 30 Jan 2017 22:24:17 +0530
> Vinod Koul wrote:
>
> > On Fri, Jan 27, 2017 at 05:42:01PM +0100, Boris Brezillon wrote:
> > > Almost all ->device_prep_dma_xx() methods have a wrapper defined in
> > > dmaengine
On 01/30/2017 03:29 PM, Russell King - ARM Linux wrote:
On Fri, Jan 06, 2017 at 06:11:40PM -0800, Steve Longerbeam wrote:
+config IMX_OV5640_MIPI
+ tristate "OmniVision OV5640 MIPI CSI-2 camera support"
+ depends on GPIOLIB && VIDEO_IMX_CAMERA
+ select IMX_MIPI_CSI2
+ d
Use the new nsec based cputime accessors as part of the whole cputime
conversion from cputime_t to nsecs.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thoma
Use the new nsec based cputime accessors as part of the whole cputime
conversion from cputime_t to nsecs.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thoma
Turn the full dynticks cputime clock source to return nsec while keeping
its very internals jiffies based for performance reasons.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc
This is one more step toward converting cputime accounting to pure nsecs.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc:
Kernel cpu stats are stored in cputime_t which is an architecture
defined type, and hence a bit opaque and requiring accessors and mutators
for any operation.
Converting them to nsecs simplifies the code and is one step toward
the removal of cputime_t in the core code.
Cc: Benjamin Herrenschmidt
This is one more step toward converting cputime accounting to pure nsecs.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc:
NSEC_PER_JIFFY is an ad-hoc redefinition of TICK_NSEC. Let's rather
use a unique and well maintained version.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: T
Use the new nsec based cputime accessors as part of the whole cputime
conversion from cputime_t to nsecs.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thoma
Use the new nsec based cputime accessors as part of the whole cputime
conversion from cputime_t to nsecs.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thoma
Use the new nsec based cputime accessors as part of the whole cputime
conversion from cputime_t to nsecs.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thoma
This cputime_t implementation is now unused, we can remove it.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Stanislaw
Not sure if MISDN stats are ABI but it displays task cputime in cputime_t
raw value regardless of what type cputime_t wraps which could be either
jiffies, nsecs, usecs, or whatever random time unit. Plus it wrongly
assumes that cputime_t is long.
Given that this dump is broken anyway, lets just di
Now that most cputime readers use the transition API which return the
task cputime in old style cputime_t, we can safely store the cputime in
nsecs. This will eventually make cputime statistics less opaque and more
granular. Back and forth convertions between cputime_t and nsecs in order
to deal wi
Initially, nsec based cputime_t implementation belonged to ia64. It got
exported later for CONFIG_VIRT_CPU_ACCOUNTING_GEN but now it is again
only used by ia64. So let's move it back there.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwide
It's a leftover from removed code.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Ingo Molnar
Cc: Stanislaw Gruszka
Cc: Wanpeng Li
Sig
Use the new nsec based cputime accessors as part of the whole cputime
conversion from cputime_t to nsecs.
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: Michael Ellerman
Cc: Heiko Carstens
Cc: Martin Schwidefsky
Cc: Tony Luck
Cc: Fenghua Yu
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thoma
101 - 200 of 1053 matches
Mail list logo
