Store -k clockid frequency into Perf trace to enable timestamps
derived metrics conversion into wall clock time on reporting stage.
Below is the example of perf report output:
tools/perf/perf record -k raw -- ../../matrix/linux/matrix.gcc
...
[ perf record: Captured and wrote 31.222 MB perf.da
On Mon, Sep 24, 2018 at 8:32 AM Richard Weinberger wrote:
>
> Lars,
>
> Am Sonntag, 23. September 2018, 15:49:42 CEST schrieb Lars Persson:
> > Hi Richard
> >
> > Sorry, I assumed this omission from -stable was a mistake.
> >
> > The timing for our boot increased from 45 seconds to 55 seconds on o
On Fri, 28 Sep 2018, Rob Herring wrote:
> On Fri, Sep 28, 2018 at 12:46 AM Lee Jones wrote:
> >
> > On Wed, 26 Sep 2018, Rob Herring wrote:
> >
> > > On Mon, Sep 17, 2018 at 04:33:22PM +0100, Charles Keepax wrote:
> > > > Signed-off-by: Charles Keepax
> > > > ---
> > > > Documentation/devicetre
Add the following flags to allow various restrictions on path
resolution (these affect the *entire* resolution, rather than just the
final path component -- as is the case with most other AT_* flags).
The primary justification for these flags is to allow for programs to be
far more strict about ho
The need for some sort of control over VFS's path resolution (to avoid
malicious paths resulting in inadvertent breakouts) has been a very
long-standing desire of many userspace applications. This patchset is a
revival of Al Viro's old AT_NO_JUMPS[1,2] patchset (which was a variant
of David Drysdal
The need for some sort of control over VFS's path resolution (to avoid
malicious paths resulting in inadvertent breakouts) has been a very
long-standing desire of many userspace applications. This patchset is a
revival of Al Viro's old AT_NO_JUMPS[1,2] patchset (which was a variant
of David Drysdal
Hi Andrew,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/s390/kernel/setup.c
between commit:
b45248da1a33 ("s390: unify stack size definitions")
ee46f78659ac ("s390: add support for virtually mapped kernel stacks")
from the s390 tree and commit:
ab9c2b8deb1
Resend:
- removed unnecessary new line in patch 3. sorry for resend
Changes in v3:
- Simplify TCS locking - added a new patch
- Add lock check to avoid potential race as suggested by Matthias
- Add functionality to RSC controller to disallow active requests
if solver mode is not set
- Rem
From: Lina Iyer
Allow the controller status be queried. The controller is busy if it is
actively processing request. Also allow the controller state be read by
platform drivers. This is useful for PM drivers which can choose to
disallow idle modes when the controller is busy.
Signed-off-by: Lina
tcs->lock was introduced to serialize access with in TCS group. But
even without tcs->lock, drv->lock is serving the same purpose. So
use single drv->lock.
Other optimizations include -
- Remove locking around clear_bit() in IRQ handler. clear_bit() is
atomic.
- Remove redundant read of TCS r
From: Lina Iyer
Controllers may be in 'solver' state, where they could be in autonomous
mode executing low power modes for their hardware and as such are not
available for sending active votes. Device driver may notify RPMH API
that the controller is in solver mode and when in such mode, disallow
[I have only now noticed that the patch has been reposted]
On Mon 08-10-18 18:27:39, Tetsuo Handa wrote:
> On 2018/10/08 17:38, Yong-Taek Lee wrote:
> >>
> >> On 2018/10/08 15:14, Yong-Taek Lee wrote:
> On 2018/10/08 10:19, Yong-Taek Lee wrote:
> > @@ -1056,6 +1056,7 @@ static int __set_o
Hello,
with linux-next for 20181008 I can reliably crash my system with lot's of
debugging options enabled on s390. List debugging triggers the list
corruption below, which I could bisect down to this commit:
fde06e07750477f049f12d7d471ffa505338a3e7 is the first bad commit
c
On Mon, Oct 08, 2018 at 08:31:34PM +0200, Greg Kroah-Hartman wrote:
> 4.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Stephen Boyd
>
> [ Upstream commit b55326dc969ea2d704a008d9a97583b128f54f4f ]
>
> The interrupt controller hardware
Hi Andrew,
On Friday 05 October 2018 09:28 PM, Andrew F. Davis wrote:
> On 10/04/2018 06:14 AM, Faiz Abbas wrote:
>> Add information to document bindings for the MMC PHY
>> on TI's AM654 devices.
>>
>> Signed-off-by: Faiz Abbas
>> Signed-off-by: Sekhar Nori
>> ---
>> .../devicetree/bindings/phy
* Mel Gorman wrote:
> On Sat, Oct 06, 2018 at 04:53:19PM +0530, Srikar Dronamraju wrote:
> > With Commit efaffc5e40ae ("mm, sched/numa: Remove rate-limiting of automatic
> > NUMA balancing migration"), we no more require migrate lock and its
> > initialization. Its redundant. Hence remove it.
>
Thank you Alex for the prompt response and fix!
it works perfectly now..
Mansour..
On 10/08/2018 10:25 AM, Alexander Shishkin wrote:
> Alexander Shishkin writes:
>
>> "Alharthi, Mansour A" writes:
>>
>>> Hello all,
>> Hi,
>>
>>> Assume this test code:
>>>
>>> thread_start(){
>>> ...
>>> test(
On Fri, 05 Oct 2018, Dmitry Torokhov wrote:
> This adds a "base attached" switch definition to the MKBP protocol that
> is used by Whiskers driver to properly determine device state (clamshell
> vs tablet mode).
>
> Signed-off-by: Dmitry Torokhov
> ---
>
> v2 changes: None
>
> Lee, I was wonde
[Cc Oleg]
On Fri 05-10-18 15:32:08, Yong-Taek Lee wrote:
> It is introduced by commit 44a70adec910 ("mm, oom_adj: make sure
> processes sharing mm have same view of oom_score_adj"). Most of
> user process's mm_users is bigger than 1 but only one thread group.
> In this case, for_each_process loop
On Mon 08 Oct 19:08 PDT 2018, Brian Norris wrote:
> Similar to qcom_q6v5_pas and qcom_wcnss drivers, probe will fail if SCM
> is not up.
>
Thanks Brian, this dependency was introduced with the memory ownership
support.
I applied it with an updated conditional to make it explicit that it
related
On 9 October 2018 07:01:57 BST, Veerabhadrarao Badiganti
wrote:
>Hi
>
>
>On 10/8/2018 12:26 PM, Bjorn Andersson wrote:
>> On Sun 07 Oct 01:07 PDT 2018, Craig wrote:
>>
>>> Any updates on this?
>>>
>> FWIW I used qcom,sdhci-msm-v5 on QCS404 successfully.
>>
>> Regards,
>> Bjorn
>
>The base addr
* Josh Poimboeuf wrote:
> > 4. Would a command line parameter be reasonable `disable_unwind`, so people
> > could decrease their boot time with distribution kernels, and easily turn it
> > back on, when they need a stacktrace without having to rebuild the Linux
> > kernel?
>
> I think a boot
* Josh Poimboeuf wrote:
> On Mon, Oct 08, 2018 at 12:34:17PM -0500, Josh Poimboeuf wrote:
> > > 4. Would a command line parameter be reasonable `disable_unwind`, so
> > > people
> > > could decrease their boot time with distribution kernels, and easily turn
> > > it
> > > back on, when they
On Fri, 28 Sep 2018, Mark Brown wrote:
> On Fri, Sep 28, 2018 at 10:14:37AM +0300, Matti Vaittinen wrote:
>
> > I was just wondering if I could do something to help get this patch
> > series applied? Mark, have you had the time to take a look on pickable
> > ranges addition yet? Should I do some
Hi
On 10/8/2018 12:26 PM, Bjorn Andersson wrote:
On Sun 07 Oct 01:07 PDT 2018, Craig wrote:
Any updates on this?
FWIW I used qcom,sdhci-msm-v5 on QCS404 successfully.
Regards,
Bjorn
The base address and interrupt numbers needs to be updated in your dt.
you can refer the below link to upd
Quoting kbuild test robot (2018-10-08 21:56:25)
> Hi Stephen,
>
> I love your patch! Perhaps something to improve:
[...]
>net/mac80211/sta_info.h:588: warning: Function parameter or member
> 'tx_stats.packets' not described in 'sta_info'
>net/mac80211/sta_info.h:588: warning: Function par
Quoting Matthias Kaehlcke (2018-09-25 14:02:55)
> Add a global binding for the 'aliases' node. This includes an initial list
> of standardized alias names for some hardware components that are commonly
> found in 'aliases'.
>
> Signed-off-by: Matthias Kaehlcke
> ---
> Documentation/devicetree/bi
Commit-ID: b8d62f33b7b225935649ab165d901fe8dd7f95e5
Gitweb: https://git.kernel.org/tip/b8d62f33b7b225935649ab165d901fe8dd7f95e5
Author: Geert Uytterhoeven
AuthorDate: Mon, 8 Oct 2018 13:17:26 +0200
Committer: Ingo Molnar
CommitDate: Tue, 9 Oct 2018 07:50:41 +0200
genirq: Fix grammar s/
From: Pierre Yves MORDRET
Having 0 in item counter register is valid and stands for a "No or Ended
transfer". Therefore valid transfer starts from @+0 to @+0xFFFE leading to
unaligned scatter gather at boundary. Thus it's safer to round down this
value on its FIFO size (16 Bytes).
Signed-off-by:
From: Pierre Yves MORDRET
A single register of the controller holds the information for four dma
channels.
The functions stm32_dma_irq_status() don't mask the relevant bits after
the shift, thus adjacent channel's status is also reported in the returned
value.
Fixed by masking the value before re
From: Pierre Yves MORDRET
This patch improves memory burst capability using best burst size
according to transferred buffer size from/to memory.
>From now on, memory burst is not necessarily same as with peripheral
burst one and fifo threshold is directly managed by this driver in order
to fit w
From: Pierre Yves MORDRET
Fix typo in a comment and solved reported checkpatch warnings.
Signed-off-by: Pierre-Yves MORDRET
Signed-off-by: Vinod Koul
---
drivers/dma/stm32-dma.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/dma/stm32-dma.c b/drivers/d
From: Pierre Yves MORDRET
Update the way Transfer Complete and Half Transfer Complete status are
acknowledge. Even if HTI is not enabled its status is shown when reading
registers, driver has to clear it gently and not raise an error.
Signed-off-by: Pierre-Yves MORDRET
Signed-off-by: Vinod Koul
From: Pierre Yves MORDRET
When in cyclic mode, the configuration is updated after having started the
DMA hardware (STM32_DMA_SCR_EN) leading to incomplete configuration of
SMxAR registers.
Signed-off-by: Pierre-Yves MORDRET
Signed-off-by: Hugues Fruchet
Signed-off-by: Vinod Koul
---
drivers/
Hi Greg,
While looking at android-4.14, I found a NULL pointer deref with
stm32-dma driver using Coccicheck errors. I found that upstream had a
bunch of patches on stm32-dma that have fixed this and other issues, I
applied these patches cleanly onto Android 4.14. I believe these should
goto stable
From: Pierre Yves MORDRET
>From now on, DMA bitfield is to manage DMA FIFO Threshold.
Signed-off-by: Pierre-Yves MORDRET
Signed-off-by: Vinod Koul
---
drivers/dma/stm32-dma.c | 19 ---
1 file changed, 16 insertions(+), 3 deletions(-)
diff --git a/drivers/dma/stm32-dma.c b/dri
Commit-ID: bbbab191c2c474d183e93799d008b412e97f5936
Gitweb: https://git.kernel.org/tip/bbbab191c2c474d183e93799d008b412e97f5936
Author: Steven Rostedt (VMware)
AuthorDate: Fri, 5 Oct 2018 12:18:16 -0400
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 8 Oct 2018 14:30:45 -0300
tool
Commit-ID: bb3dd7e7c4d5e024d607c0ec06c2a2fb9408cc99
Gitweb: https://git.kernel.org/tip/bb3dd7e7c4d5e024d607c0ec06c2a2fb9408cc99
Author: Tzvetomir Stoyanov
AuthorDate: Fri, 5 Oct 2018 12:22:25 -0400
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 8 Oct 2018 15:05:37 -0300
tools lib
Commit-ID: 8b2f245faa6238e28a1d801e8633515251d1acfc
Gitweb: https://git.kernel.org/tip/8b2f245faa6238e28a1d801e8633515251d1acfc
Author: Eduardo Habkost
AuthorDate: Fri, 5 Oct 2018 17:40:58 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 8 Oct 2018 14:30:45 -0300
perf python:
Commit-ID: e13a5d69c31d35538e80176d54d95b6addf4dcbf
Gitweb: https://git.kernel.org/tip/e13a5d69c31d35538e80176d54d95b6addf4dcbf
Author: Eduardo Habkost
AuthorDate: Fri, 5 Oct 2018 17:40:57 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 8 Oct 2018 14:30:44 -0300
perf python:
Commit-ID: 1e44224fb0528b4c0cc176bde2bb31e9127eb14b
Gitweb: https://git.kernel.org/tip/1e44224fb0528b4c0cc176bde2bb31e9127eb14b
Author: Sanskriti Sharma
AuthorDate: Tue, 2 Oct 2018 10:29:14 -0400
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 8 Oct 2018 14:23:46 -0300
perf tools:
Commit-ID: 470c8f7c88de013d266e1b61044efe8937728b7f
Gitweb: https://git.kernel.org/tip/470c8f7c88de013d266e1b61044efe8937728b7f
Author: Sanskriti Sharma
AuthorDate: Tue, 2 Oct 2018 10:29:13 -0400
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 8 Oct 2018 14:23:46 -0300
perf tools:
Commit-ID: 9c8a182e5a73e01afd11742a2ab887bf338fdafd
Gitweb: https://git.kernel.org/tip/9c8a182e5a73e01afd11742a2ab887bf338fdafd
Author: Sanskriti Sharma
AuthorDate: Tue, 2 Oct 2018 10:29:12 -0400
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 8 Oct 2018 14:23:45 -0300
perf tools:
Commit-ID: faedbf3fd19f2511a39397f76359e4cc6ee93072
Gitweb: https://git.kernel.org/tip/faedbf3fd19f2511a39397f76359e4cc6ee93072
Author: Sanskriti Sharma
AuthorDate: Tue, 2 Oct 2018 10:29:11 -0400
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 8 Oct 2018 14:23:45 -0300
perf tools:
Commit-ID: ce49d8436cffa9b7a6a5f110879d53e89dbc6746
Gitweb: https://git.kernel.org/tip/ce49d8436cffa9b7a6a5f110879d53e89dbc6746
Author: Sanskriti Sharma
AuthorDate: Tue, 2 Oct 2018 10:29:10 -0400
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 8 Oct 2018 14:23:44 -0300
perf strbuf
Commit-ID: 0e24147d69c9357b1ccb54a9bc028eb9a9f9ed1a
Gitweb: https://git.kernel.org/tip/0e24147d69c9357b1ccb54a9bc028eb9a9f9ed1a
Author: Thomas Richter
AuthorDate: Fri, 28 Sep 2018 12:53:35 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 8 Oct 2018 14:23:44 -0300
perf test: S
Commit-ID: 291ed51deee49ff35d0824fb7050538b449964d6
Gitweb: https://git.kernel.org/tip/291ed51deee49ff35d0824fb7050538b449964d6
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 25 Sep 2018 11:52:10 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 8 Oct 2018 14:23:43 -0300
pe
Commit-ID: ba4aa02b417f08a0bee5e7b8ed70cac788a7c854
Gitweb: https://git.kernel.org/tip/ba4aa02b417f08a0bee5e7b8ed70cac788a7c854
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 25 Sep 2018 10:55:59 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Mon, 8 Oct 2018 14:23:43 -0300
to
quirk for Goldmont Plus (2018-10-02 10:14:33 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
> tags/perf-core-for-mingo-4.20-20181008
>
> for you to fetch changes up to bb3dd7e7c4d5e024d607c0ec06c2a2fb9
On Tue, Oct 09, 2018 at 10:51:02AM +1100, Stephen Rothwell wrote:
> Hi Ted,
>
> After merging the ext4 tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
Oops, my bad. Thanks for catching this. I failed to a new helper
function inside #ifdef CONFIG_QUOTA .. #endif.
Sho
Hi Uffe,
On Monday 08 October 2018 05:02 PM, Ulf Hansson wrote:
> On 4 October 2018 at 13:14, Faiz Abbas wrote:
>> Add driver support for the MMC physical layer present
>> on TI's AM654 devices.
>>
>> Signed-off-by: Faiz Abbas
>> Signed-off-by: Sekhar Nori
>
> I assume Kishon would like to pic
Hi all,
Today's linux-next merge of the staging tree got a conflict in:
drivers/staging/dgnc/dgnc_tty.c
between commits:
b68166ef8fd9 ("dgnc: leave TIOC[GS]SOFTCAR to ldisc")
e002c6f1ccb9 ("dgnc: don't bother with (empty) stub for TCXONC")
79273fc94ee9 ("dgnc: break-related ioctls won't
Hi Stephen,
I love your patch! Perhaps something to improve:
[auto build test WARNING on gpio/for-next]
[also build test WARNING on v4.19-rc7 next-20181008]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
Hello,
syzbot found the following crash on:
HEAD commit:0854ba5ff5c9 Merge git://git.kernel.org/pub/scm/linux/kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1554ec0640
kernel config: https://syzkaller.appspot.com/x/.config?x=88e9a8a39dc0be2d
da
On Mon, Oct 08, 2018 at 06:50:41AM +, zhouzho...@gmail.com wrote:
> From: Zhouyi Zhou
>
> Because RCU avoids interrupting idle CPUs, rcu_is_watching is used to
> test whether or not it is currently legal to run RCU read-side
> critical sections on this CPU.
>
> First sentence and last sent
On 09/19/2018 07:50 AM, Yogesh Gaur wrote:
> Some MICRON related macros in spi-nor domain were ST.
> Rename entries related to STMicroelectronics under macro SNOR_MFR_ST.
>
> Added entry of MFR Id for Micron flashes, 0x002C.
>
> Signed-off-by: Yogesh Gaur
Reviewed-by: Tudor Ambarus
> ---
>
A normal mapped THP page at PMD level should be correctly differentiated
from a PMD migration entry while walking the page table. A mapped THP would
additionally check positive for pmd_present() along with pmd_trans_huge()
as compared to a PMD migration entry. This just adds a new conditional test
NCSI hardware arbitration allows multiple packages to be enabled at once
and share the same wiring. If the NCSI driver recognises that HWA is
available it unconditionally enables all packages and channels; but that
is a configuration decision rather than something required by HWA.
Additionally the
This patch extends the ncsi-netlink interface with two new commands and
three new attributes to configure multiple packages and/or channels at
once, and configure specific failover modes.
NCSI_CMD_SET_PACKAGE mask and NCSI_CMD_SET_CHANNEL_MASK set a whitelist
of packages or channels allowed to be
On Mon, 8 Oct 2018 21:17:10 -0500
Josh Poimboeuf wrote:
> I'm not really convinced we need objtool for this, maybe I'll try
> whipping up a POC.
Awesome!
I wasn't thinking of actually having objtool itself perform this task,
but instead breaking the internals of objtool up into more of a generi
On Tue, 9 Oct 2018 12:44:01 +0900
Masami Hiramatsu wrote:
> On Fri, 05 Oct 2018 21:51:11 -0400
> Steven Rostedt wrote:
>
> > +typedef long dynfunc_t;
> > +
> > +struct dynfunc_struct;
> > +
> > +#define arch_dynfunc_trampoline(name, def) \
> > + asm volatile ( \
> > +
On Fri, 05 Oct 2018 21:51:11 -0400
Steven Rostedt wrote:
> +typedef long dynfunc_t;
> +
> +struct dynfunc_struct;
> +
> +#define arch_dynfunc_trampoline(name, def) \
> + asm volatile ( \
> + ".globl dynfunc_" #name "; \n\t"\
> + "dynfunc_" #name ": \
On Tue, Oct 09, 2018 at 09:52:05AM +0800, Rong Chen wrote:
>
>
> On 10/01/2018 07:00 AM, Paul E. McKenney wrote:
> >On Sun, Sep 30, 2018 at 11:16:14AM +0800, kernel test robot wrote:
> >>FYI, we noticed the following commit (built with gcc-7):
> >>
> >>commit: 5aa56a54ce92761e974f93592f69b75b8c23
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
arch/s390/Kconfig
between commit:
819eafaa7b58 ("s390/kasan: add initialization code and enable it")
from the s290 tree and commit:
13ddb52c165b ("s390/jump_label: Switch to relative references")
from the tip tree.
I
On 08. okt. 2018 20:29, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.18.13 release.
There are 168 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.
CC [M] net/ipv4/
Hello Rob,
Thanks for the review.
On Mon, Oct 8, 2018 at 9:15 PM Rob Herring wrote:
>
> In the future, please use get_maintainers.pl and send to the right
> lists and people. Perhaps the coresight, i2c, network, nvmem and spi
> maintainers would like to see and be aware of this change.
>
Sure.
Hello Rafael,
On Mon, Oct 8, 2018 at 1:43 PM Rafael J. Wysocki wrote:
>
> On Tue, Sep 25, 2018 at 7:29 AM Silesh C V wrote:
> >
> > Some drivers need to find the device on a bus having a specific firmware
> > node. Currently, such drivers have their own implementations to do this.
> > Provide a
On Mon, 2018-10-08 at 18:23 +0100, Lorenzo Pieralisi wrote:
> On Mon, Oct 08, 2018 at 11:24:41AM +0800, honghui.zh...@mediatek.com wrote:
> > From: Honghui Zhang
> >
> > The PCIe controller of MT7622 has TYPE 1 configuration space type, but
> > the HW default class type values is invalid.
> >
>
在 2018年10月08日 21:43, Borislav Petkov 写道:
> On Mon, Oct 08, 2018 at 10:59:09AM +0200, Borislav Petkov wrote:
>> On Mon, Oct 08, 2018 at 04:47:34PM +0800, lijiang wrote:
>>> It looks like a good way to avoid the 'ifdefined', and it's also good
>>> enough for i386.
>>>
>>> But for other architectures
Hi Marc,
On Mon, Oct 08, 2018 at 05:35:19PM +0100, Marc Zyngier wrote:
> Hi Guo,
>
> On 04/10/18 18:22, Guo Ren wrote:
> > - Irq-csky-mpintc is C-SKY smp system interrupt controller and it
> >could support 16 soft irqs, 16 private irqs, and 992 max common
> >irqs.
> >
> >Changelog:
> >
We move __fstate_save and __fstate_restore to a new source
file, fpu.S.
Signed-off-by: Alan Kao
Cc: Greentime Hu
Cc: Vincent Chen
Cc: Zong Li
Cc: Nick Hu
Reviewed-by: Christoph Hellwig
---
arch/riscv/kernel/Makefile | 1 +
arch/riscv/kernel/entry.S | 87 -
This patch cleanup the MARCH string passing to both compiler and
assembler. Note that the CFLAGS should not contain "fd" before we
have mechnisms like kernel_fpu_begin/end in other architectures.
Signed-off-by: Alan Kao
Cc: Greentime Hu
Cc: Vincent Chen
Cc: Zong Li
Cc: Nick Hu
---
arch/risc
We expect that a kernel with CONFIG_FPU=y can still support no-FPU
machines. To do so, the kernel should first examine the existence of a
FPU, then do nothing if a FPU does exist; otherwise, it should
disable/bypass all FPU-related functions.
In this patch, a new global variable, has_fpu, is creat
Hi All,
If there's no comments, should I submit this patch on RMK's Patch system?
Thanks,
Chunyan
On 27 September 2018 at 11:41, Chunyan Zhang wrote:
> From: Arnd Bergmann
>
> When function tracing for IPIs is enabled, we get a warning for an
> overflow of the ipi_types array with the IPI_CPU_
FPU-related logic is separated from normal signal handling path in
this patch. Kernel can easily be configured to exclude those procedures
for no-FPU systems.
Signed-off-by: Alan Kao
Cc: Greentime Hu
Cc: Vincent Chen
Cc: Zong Li
Cc: Nick Hu
Reviewed-by: Christoph Hellwig
---
arch/riscv/ker
This patchset adds an option, CONFIG_FPU, to enable/disable floating-
point procedures.
Kernel's new behavior will be as follows:
* with CONFIG_FPU=y
All FPU codes are reserved. If no FPU is found during booting, a
global flag will be set, and those functions will be bypassed with
conditio
FPU codes have been separated from common part in previous patches.
This patch add the CONFIG_FPU option and some stubs, so that a no-FPU
configuration is allowed.
Signed-off-by: Alan Kao
Cc: Greentime Hu
Cc: Vincent Chen
Cc: Zong Li
Cc: Nick Hu
Reviewed-by: Christoph Hellwig
---
arch/riscv
On Mon, Oct 08, 2018 at 09:29:56AM -0700, Andy Lutomirski wrote:
>
>
> > On Oct 8, 2018, at 8:57 AM, Peter Zijlstra wrote:
> >
> > On Mon, Oct 08, 2018 at 01:33:14AM -0700, Andy Lutomirski wrote:
> >>> Can't we hijack the relocation records for these functions before they
> >>> get thrown out i
From: Lina Iyer
Controllers may be in 'solver' state, where they could be in autonomous
mode executing low power modes for their hardware and as such are not
available for sending active votes. Device driver may notify RPMH API
that the controller is in solver mode and when in such mode, disallow
From: Lina Iyer
Allow the controller status be queried. The controller is busy if it is
actively processing request. Also allow the controller state be read by
platform drivers. This is useful for PM drivers which can choose to
disallow idle modes when the controller is busy.
Signed-off-by: Lina
tcs->lock was introduced to serialize access with in TCS group. But
even without tcs->lock, drv->lock is serving the same purpose. So
use single drv->lock.
Other optimizations include -
- Remove locking around clear_bit() in IRQ handler. clear_bit() is
atomic.
- Remove redundant read of TCS r
Changes in v3:
- Simplify TCS locking - added a new patch
- Add lock check to avoid potential race as suggested by Matthias
- Add functionality to RSC controller to disallow active requests
if solver mode is not set
- Removed independent patches and posted as separate series[2]
Changes in
Similar to qcom_q6v5_pas and qcom_wcnss drivers, probe will fail if SCM
is not up.
Signed-off-by: Brian Norris
---
drivers/remoteproc/qcom_q6v5_mss.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/remoteproc/qcom_q6v5_mss.c
b/drivers/remoteproc/qcom_q6v5_mss.c
index a839b07a58b1
On Mon, 8 Oct 2018 at 20:04, Liran Alon wrote:
>
>
>
> > On 8 Oct 2018, at 13:59, Wanpeng Li wrote:
> >
> > On Mon, 8 Oct 2018 at 05:02, Liran Alon wrote:
> >>
> >>
> >>
> >>> On 28 Sep 2018, at 9:12, Wanpeng Li wrote:
> >>>
> >>> From: Wanpeng Li
> >>>
> >>> In cloud environment, lapic_timer_
On Mon, 2018-10-08 at 10:56 +0300, Igor Stoppa wrote:
> Hi,
>
> I have the following fragment of code:
>
> +struct my_struct {
> + atomic_long_t l __aligned(sizeof(atomic_long_t));
> +} __aligned(sizeof(atomic_long_t));
>
>
> triggering this warning, when fed to checkpatch.pl:
>
> WARNIN
From: Yue Wang
The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
PCI core. This patch adds the driver support for Meson PCIe controller.
Signed-off-by: Yue Wang
Signed-off-by: Hanjie Lin
---
MAINTAINERS| 7 +
drivers/pci/controller/dwc/Kc
The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
PCI core. This patchset add the driver and dt-bindings of the controller.
Changes since v4: [3]
- fix kbuild test robot and compile warnings
Changes since v3: [2]
- modify subject format
- update Kconfig
- update MAINT
From: Yue Wang
The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
PCI core. This patch adds documentation for the DT bindings in Meson PCIe
controller.
Signed-off-by: Yue Wang
Signed-off-by: Hanjie Lin
Reviewed-by: Rob Herring
---
.../devicetree/bindings/pci/amlogic,m
On Mon, 2018-10-08 at 12:31 -0500, Bjorn Helgaas wrote:
> On Mon, Oct 08, 2018 at 11:24:39AM +0800, honghui.zh...@mediatek.com wrote:
>
> > Honghui Zhang (9):
> > PCI: mediatek: Using slot's devfn for compare to fix
> > mtk_pcie_find_port logic
> > PCI: mediatek: Fixup class ID for MT7622
On Sat, 06 Oct 2018 08:01:25 -0400
Steven Rostedt wrote:
> [ Sending v2 because I updated quilt and it added back that stupid
> "Content-Disposition: inline; filename=$patch" line, messing up
> how the patches look in gmail. This should be better. ]
>
Actually, this wasn't suppose to go out
On Mon, Oct 08, 2018 at 06:29:54PM +0200, Dmitry Vyukov wrote:
>
> The program that triggered it did the following:
>
> 05:23:28 executing program 5:
> r0 = creat(&(0x7f0001c0)='./file0\x00', 0x0)
> socketpair$unix(0x1, 0x1, 0x0, &(0x7f000380)={0x,
> 0x})
>
Fixes gcc '-Wunused-but-set-variable' warning:
drivers/net/wireless/mediatek/mt76/mt76x0/pci.c: In function
'mt76x0e_register_device':
drivers/net/wireless/mediatek/mt76/mt76x0/pci.c:107:8: warning:
variable 'data' set but not used [-Wunused-but-set-variable]
It seems correct value to write is
On Mon, Oct 08, 2018 at 08:31:07PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.132 release.
> There are 59 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
On Mon, Oct 08, 2018 at 08:30:01PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.160 release.
> There are 113 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 kno
On Mon, Oct 08, 2018 at 03:28:01PM +, Leonard Crestez wrote:
> Bindings for "fixed-regulator" only explicitly support "gpio" property,
> not "gpios". Fix by correcting the property name.
>
> The enet PHYs on imx6sx-sdb needs to be explicitly reset after a power
> cycle, this can be handled by
From: Wanpeng Li
In cloud environment, lapic_timer_advance_ns is needed to be tuned for every
CPU
generations, and every host kernel versions(the
kvm-unit-tests/tscdeadline_latency.flat
is 5700 cycles for upstream kernel and 9600 cycles for our 3.10 product kernel,
both preemption_timer=N, S
From: Sanskriti Sharma
The temporary 'buf' buffer allocated in read_event_file() may be freed
twice. Move the free() call to the common function exit point.
Fixes the following coverity complaints:
Error: USE_AFTER_FREE (CWE-825):
tools/perf/util/trace-event-read.c:309: double_free: Callin
From: Tzvetomir Stoyanov
As traceevent is going to be transferred into a proper library,
its local data should be protected from the library users.
This patch encapsulates struct tep_handler into a local header,
not visible outside of the library. It implements also a bunch
of new APIs, which lib
From: Thomas Richter
S390 does not support the perf_event_open system call for
attribute type PERF_TYPE_BREAKPOINT. This results in test
failure for test 22:
[root@s8360046 perf]# ./perf test 22
22: Watchpoint:
22.1: Read Only Watchpoint:
From: Sanskriti Sharma
For each system in a given pevent, read_event_files() reads in a
temporary 'sys' string. Be sure to free this string before moving onto
to the next system and/or leaving read_event_files().
Fixes the following coverity complaints:
Error: RESOURCE_LEAK (CWE-772):
too
1 - 100 of 1265 matches
Mail list logo