Hi,
On 05.09.2018 21:51, Arnaldo Carvalho de Melo wrote:
> Em Wed, Sep 05, 2018 at 08:37:32PM +0300, Alexey Budankov escreveu:
>> On 05.09.2018 14:28, Jiri Olsa wrote:
>>> can't apply this version on Arnaldo's perf/core...
>
>> my git remote -v
>
>> origin git://git.kernel.org/pub/scm/li
Tetsuo Handa wrote:
> Michal Hocko wrote:
> > > I assert that we should fix af5679fbc669f31f.
> >
> > If you can come up with reasonable patch which doesn't complicate the
> > code and it is a clear win for both this particular workload as well as
> > others then why not.
>
> Why can't we do "at
On Thu, Sep 6, 2018 at 4:55 AM Kai-Heng Feng
wrote:
>
> Raydium touchscreen triggers interrupt storm after system-wide suspend:
> [ 179.085033] i2c_hid i2c-CUST:00: i2c_hid_get_input: incomplete
> report (58/65535)
>
> According to Raydium, Windows driver does not reset the device after
> syst
Hi Boris,
Currently FlexSPI controller is present in ARM SoC but NXP is coming with
PowerPC SoC with same FlexSPI controller.
We are trying to use same binding as defined in this patch-set(tested on ARM64
processors) for PowerPC.
Unfortunately, It is showing issue when driver tries to parse 'fs
Hi,
On Tue, Sep 4, 2018 at 9:41 PM Wolfram Sang wrote:
>
> On Mon, Sep 03, 2018 at 03:11:11PM +0530, shubhrajyoti.da...@gmail.com wrote:
> > From: Shubhrajyoti Datta
> >
> > Disable interrupts while configuring the transfer and enable them back.
> >
> > We have below as the programming sequence
Hi,
Today's next fails to mount NFS root under my ARM targets and fails to
mount root from file image under QMU.
[ 21.512866] Unable to handle kernel NULL pointer dereference at
virtual address
[ 21.695484] [] (nfs_fs_mount) from []
(legacy_get_tree+0x34/0xec)
[ 21.703225] [] (legacy_get
Yann Droneaud wrote:
> This structure should not have been exposed to userspace in the first
> place: it's unusable by userspace as it is. It was incorrect to have it
> outside of #ifdef __KERNEL__ before commit 607ca46e97a1b ...
> ...
> All CODA_REQ_* defines internals to kernel side and not ex
Le mercredi 05 septembre 2018 à 19:33 +0200, Yann Droneaud a écrit :
> Le mercredi 05 septembre 2018 à 18:55 +0200, Greg KH a écrit :
> > On Wed, Sep 05, 2018 at 04:54:27PM +0100, David Howells wrote:
> > >
> > > Here's a set of patches that inserts a step into the build
> > > process to make
> >
On Wed, Sep 05, 2018 at 02:47:07PM -0700, Andi Kleen wrote:
> On Wed, Sep 05, 2018 at 08:53:17AM -0700, Eduardo Valentin wrote:
> > On Wed, Sep 05, 2018 at 10:52:12AM +0200, Peter Zijlstra wrote:
> > > On Thu, Aug 23, 2018 at 08:07:32AM -0700, Eduardo Valentin wrote:
> > > > On a system with X86_FE
Considering this case in find_free_channels():
bitmap:
+--+-+-+-+-+-+-+-+-+-+-+
| .. |0|0|0|0|0|0|0|1|0|0|
+--+-+-+-+-+-+-+-+-+-+-+
1. Channel #2 has been occupied, so bit #2 is 1, and the others
are all 0.
2. Another thread tr
On Wed, Sep 5, 2018 at 4:09 PM 焦晓冬 wrote:
>
> On Tue, Sep 4, 2018 at 11:44 PM Jeff Layton wrote:
> >
> > On Tue, 2018-09-04 at 22:56 +0800, 焦晓冬 wrote:
> > > On Tue, Sep 4, 2018 at 7:09 PM Jeff Layton wrote:
> > > >
> > > > On Tue, 2018-09-04 at 16:58 +0800, Trol wrote:
> > > > > On Tue, Sep 4, 2
Drivers must set the quirk_addfb_prefer_host_byte_order quirk to make
the drm_mode_addfb() compat code work correctly on bigendian machines.
If they don't they interpret pixel_format values incorrectly for bug
compatibility, which in turn implies the ADDFB2 ioctl does not work
correctly then. So
On (09/05/18 13:02), Petr Mladek wrote:
> Note that the first registered console prints all messages
> even without this flag.
Hmm, OK, interesting point.
I assumed that the first console usually has CON_PRINTBUFFER bit set.
Or even a CON_PRINTBUFFER | CON_ANYTIME combo. E.g. 8250. It sort of
mak
Hi,
On 06-09-18 06:33, Suman Tripathi wrote:
Due to hardware errata, Ampere Computing eMAG SATA can't support
AHCI ALPM feature. This patch disables the AHCI ALPM feature for
eMAG SATA.
Changes for v2:
* Introduce the new ata_port_info object which includes ATA_FLAG_NO_LPM.
* Include this obje
On 2018-09-05 08:28:02 [-0400], Steven Rostedt wrote:
> 4.14.63-rt41-rc1 stable review patch.
> If anyone has any objections, please let me know.
>
> --
>
> From: Sebastian Andrzej Siewior
>
> [ Upstream commit 2a9c45d8f89112458364285cbe2b0729561953f1 ]
>
> Drop the Ultraviolet
On 2018-08-31 14:42:25 [-0500], Grygorii Strashko wrote:
>
>
> On 08/31/2018 02:30 PM, Sebastian Andrzej Siewior wrote:
> > On 2018-08-31 14:19:53 [-0500], Grygorii Strashko wrote:
> >>
> >> I've tried this and do not see warnings. I'm sending 4.14-rt patches i
> >> have as
> >> I could miss smt
On 2018-09-05 08:28:05 [-0400], Steven Rostedt wrote:
> 4.14.63-rt41-rc1 stable review patch.
> If anyone has any objections, please let me know.
could you please take commit d6914631a84f4 ("irqchip/gic-v3-its: Move
pending table allocation to init time")
https://git.kernel.org/pub/scm/linux/ke
/linux/commits/Roman-Gushchin/mm-slowly-shrink-slabs-with-a-relatively-small-number-of-objects/20180906-142351
config: openrisc-or1ksim_defconfig (attached as .config)
compiler: or1k-linux-gcc (GCC) 6.0.0 20160327 (experimental)
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp
On 06/09/2018 01:01, Thomas Gleixner wrote:
> On Wed, 5 Sep 2018, Laurent Dufour wrote:
>> On 05/09/2018 17:10, Christopher Lameter wrote:
>>> Large page sizes also reduce contention there.
>>
>> That's true for the page fault path, but for process's actions manipulating
>> the
>> memory process's
After a couple of months work, I think Nyt Cloud is shaping up, and we
are putting the finishing touches on it.
A universalized international streaming goods paradigm, is indeed what
it is about, and what a good computer OS needs to be about in these days.
Internet is becoming professional, a
On 2018-09-05 08:27:54 [-0400], Steven Rostedt wrote:
> Dear RT Folks,
>
> This is the RT stable review cycle of patch 4.14.63-rt41-rc1.
>
> Please scream at me if I messed something up. Please test the patches too.
>
> The -rc release will be uploaded to kernel.org and will be deleted when
> th
On Wed, 5 Sep 2018, pher...@codeaurora.org wrote:
> On 2018-09-05 11:23, Thomas Gleixner wrote:
> > On Wed, 5 Sep 2018, Prakruthi Deepak Heragu wrote:
> >
> > > One of the cores might have just allocated irq_desc() and other core
> > > might be doing irq migration in the hot plug path. In the hot
In order to fix a page table walk issue, commit 6ea6e84309ca
("KVM: x86: inject exceptions produced by x86_decode_insn") check
if variable ctxt->have_exception true and inject the exception.
Unfortunately, ctxt->have_exception is set to true only in function
x86_emulate_insn(), which won't be calle
From: Palmer Dabbelt
commit f1f1007644ff ("mm: add new mmgrab() helper") added a
helper that we missed out on.
Signed-off-by: Palmer Dabbelt
Reviewed-by: Christoph Hellwig
Signed-off-by: Atish Patra
---
arch/riscv/kernel/smpboot.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
Currently, both linux cpu id and hardware cpu id are same.
This is not recommended as it will lead to discontinuous cpu
indexing in Linux. Moreover, kdump kernel will run from CPU0
which would be absent if we follow existing scheme.
Implement a logical mapping between Linux cpu id and hardware
cpu
Fix trivial use-after-free. This could be last reference to bfqg.
Signed-off-by: Konstantin Khlebnikov
Fixes: 8f9bebc33dd7 ("block, bfq: access and cache blkg data only when safe")
---
block/bfq-cgroup.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/block/bfq-cgroup.
This patch enable support for cpu hotplug in RISC-V.
In absence of generic cpu stop functions, WFI is used
to put the cpu in low power state during offline. An IPI
is sent to bring it out of WFI during online operation.
Tested both on QEMU and HighFive Unleashed board with
4 cpus. Test result fol
Currently, irq is enabled before preemption disabling happens.
If the scheduler fired right here and cpu is scheduled then it
may blow up.
Signed-off-by: Palmer Dabbelt
[Atish: Commit text and code comment formatting update]
Signed-off-by: Atish Patra
---
arch/riscv/kernel/smpboot.c | 6 +-
The secondary harts spin on couple of per cpu variables until both of
these are non-zero so it's not necessary to have any ordering here.
However, WRITE_ONCE should be used to avoid tearing.
Signed-off-by: Atish Patra
---
arch/riscv/kernel/smpboot.c | 5 +++--
1 file changed, 3 insertions(+), 2
Setup the cpu_logical_map during boot. Moreover, every SBI call
and PLIC context are based on the physical hartid. Use the logical
cpu to hartid mapping to pass correct hartid to respective functions.
Signed-off-by: Atish Patra
Reviewed-by : Anup Patel
---
arch/riscv/include/asm/tlbflush.h | 1
From: Palmer Dabbelt
The old name was a bit odd.
Signed-off-by: Palmer Dabbelt
Signed-off-by: Atish Patra
---
arch/riscv/kernel/smpboot.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/arch/riscv/kernel/smpboot.c b/arch/riscv/kernel/smpboot.c
index cfb0b02d..4a23
From: Palmer Dabbelt
It's a bit confusing exactly what this function does: it actually
returns the hartid of an OF processor node, failing with -1 on invalid
nodes. I've changed the name to _hartid() in order to make that a bit
more clear, as well as adding a comment.
Signed-off-by: Palmer Dabb
From: Palmer Dabbelt
I'm not sure how I managed to miss this the first time, but this is much
better.
Signed-off-by: Palmer Dabbelt
[Atish: code comment formatting and other fixes]
Signed-off-by: Atish Patra
---
arch/riscv/include/asm/smp.h | 14 --
1 file changed, 4 insertions(+)
From: Palmer Dabbelt
These are just hard coded in the RISC-V port, which doesn't make any
sense. We should probably be setting these from device tree entries
when they exist, but for now I think it's saner to just leave them all
as their default values.
Signed-off-by: Palmer Dabbelt
Reviewed-b
From: Palmer Dabbelt
This isn't readily apparent from reading the code.
Signed-off-by: Palmer Dabbelt
[Atish: code comment formatting update]
Signed-off-by: Atish Patra
---
arch/riscv/kernel/smpboot.c | 4
1 file changed, 4 insertions(+)
diff --git a/arch/riscv/kernel/smpboot.c b/arch/r
From: Palmer Dabbelt
We shouldn't be directly passing device tree values to userspace, both
because there could be mistakes in device trees and because the kernel
doesn't support arbitrary ISAs.
Signed-off-by: Palmer Dabbelt
[Atish: checkpatch fix and code comment formatting update]
Signed-off-
This patch series has updated the assorted cleanup series by palmer.
The original cleanup patch series can be found here.
http://lists.infradead.org/pipermail/linux-riscv/2018-August/001232.html
It also implemented following smp related features.
Some of the work has been inspired from ARM64.
1.
On Wed, 5 Sep 2018, Prakruthi Deepak Heragu wrote:
> Once the tear down hotplug handler is run, cpu is dead and enters
> into CPUHP_AP_IDLE_DEAD state. Any callbacks that fail in the state
> machine with state < CPUHP_AP_IDLE must be treated as fatal as this
> could result into timer not beig migr
On Wed, Sep 05, 2018 at 12:46:02PM +0300, Mika Westerberg wrote:
> On Wed, Sep 05, 2018 at 10:47:46AM +0200, Lukas Wunner wrote:
> > On Mon, Sep 03, 2018 at 04:20:12PM +0300, Mika Westerberg wrote:
> > > If IOMMU is enabled and Thunderbolt driver is built into the kernel
> > > image, it will be pro
On Thu 06-09-18 00:37:06, Souptick Joarder wrote:
> On Wed, Sep 5, 2018 at 2:25 PM Jan Kara wrote:
> >
> > On Wed 05-09-18 00:13:02, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit:387ac6229ecf Add linux-next specific files for 20180905
> > >
On Wed, Sep 05, 2018 at 07:10:46PM +, Nadav Amit wrote:
> at 12:02 PM, Nadav Amit wrote:
>
> > at 11:56 AM, Peter Zijlstra wrote:
> >
> >> On Sun, Sep 02, 2018 at 10:32:18AM -0700, Nadav Amit wrote:
> >>> This patch-set addresses some issues that were raised in a recent
> >>> correspondence
On Thu, Sep 06, 2018 at 09:03:17AM +0300, Alexey Budankov wrote:
> Hi,
>
> On 05.09.2018 21:51, Arnaldo Carvalho de Melo wrote:
> > Em Wed, Sep 05, 2018 at 08:37:32PM +0300, Alexey Budankov escreveu:
> >> On 05.09.2018 14:28, Jiri Olsa wrote:
> >>> can't apply this version on Arnaldo's perf/core..
On Wed, 5 Sep 2018, Rob Herring wrote:
> Use the for_each_of_cpu_node iterator to iterate over cpu nodes. This
> has the side effect of defaulting to iterating using "cpu" node names in
> preference to the deprecated (for FDT) device_type == "cpu".
>
> Cc: Thomas Gleixner
> Cc: Ingo Molnar
> Cc
Hi Mel,
we have results with 2d4056fafa196e1ab4e7161bae4df76f9602d56d reverted.
* Compared to 4.18, there is still performance regression -
especially with NAS (sp_C_x subtest) and SPECjvm2008. On 4 NUMA
systems, regression is around 10-15%
* Compared to 4.19rc1 there is a clear gain across a
Currently, linux kernel is basically not preventing userspace-userspace
spectrev2 attack, because:
- IBPB is basically unused (issued only for tasks that marked themselves
explicitly non-dumpable, which is absolutely negligible minority of all
software out there), therefore cross-process br
Takashi Sakamoto wrote:
> A similar patch was already proposed[1] and has been applied by Mark to
> his tree[2]. Your issue (3) is going to be solved soon for v4.19
> kernel.
Thanks, I've pulled the branch leading up to that commit into the base of
mine. It seems the changes were identical:-)
On 28/08/18 14:53, Patrick Bellasi wrote:
[...]
> static inline int __setscheduler_uclamp(struct task_struct *p,
> const struct sched_attr *attr)
> {
> - if (attr->sched_util_min > attr->sched_util_max)
> - return -EINVAL;
> - if (attr->
From: Jiri Kosina
Currently, we are issuing IBPB only in cases when switching into a non-dumpable
process, the rationale being to protect such 'important and security sensitive'
processess (such as GPG) from data leak into a different userspace process via
spectre v2.
This is however completely
From: Jiri Kosina
STIBP is a feature provided by certain Intel ucodes / CPUs. This feature
(once enabled) prevents cross-hyperthread control of decisions made by
indirect branch predictors.
Enable this feature if
- the CPU is vulnerable to spectre v2
- the CPU supports SMT and has SMT siblings
On Thu, 6 Sep 2018, Neeraj Upadhyay wrote:
> On 09/05/2018 06:47 PM, Thomas Gleixner wrote:
> > On Wed, 5 Sep 2018, Neeraj Upadhyay wrote:
> > > On 09/05/2018 05:53 PM, Thomas Gleixner wrote:
> > > > And looking closer this is a general issue. Just that the TEARDOWN state
> > > > makes it simple to
Hi,
On 06.09.2018 11:14, Jiri Olsa wrote:
> On Thu, Sep 06, 2018 at 09:03:17AM +0300, Alexey Budankov wrote:
>> Hi,
>>
>> On 05.09.2018 21:51, Arnaldo Carvalho de Melo wrote:
>>> Em Wed, Sep 05, 2018 at 08:37:32PM +0300, Alexey Budankov escreveu:
On 05.09.2018 14:28, Jiri Olsa wrote:
> ca
Hello,
syzbot found the following crash on:
HEAD commit:509d1f0c294a Add linux-next specific files for 20180906
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=157b857a40
kernel config: https://syzkaller.appspot.com/x/.config?x=d1a648893bbc933
Hi Kevin,
If you don't mind, please change the title from "ARM64" to "arm64" if
this gets merged.
Thanks!
Maxime
Hi Yogesh,
On 05.09.2018 12:07, Yogesh Narayan Gaur wrote:
Hi Boris,
-Original Message-
From: Boris Brezillon [mailto:boris.brezil...@bootlin.com]
Sent: Tuesday, September 4, 2018 8:29 PM
To: Yogesh Narayan Gaur
Cc: linux-...@lists.infradead.org; marek.va...@gmail.com; linux-
s...@vge
Hi Kevin,
Please create an immutable tag for this patch, as this is a hard
dependency for the video decoder patches. This will make it easier for
Mauro.
Thanks,
Maxime
From: Jiri Kosina
Currently, we are issuing IBPB only in cases when switching into a non-dumpable
process, the rationale being to protect such 'important and security sensitive'
processess (such as GPG) from data leak into a different userspace process via
spectre v2.
This is however completely
From: Jiri Kosina
STIBP is a feature provided by certain Intel ucodes / CPUs. This feature
(once enabled) prevents cross-hyperthread control of decisions made by
indirect branch predictors.
Enable this feature if
- the CPU is vulnerable to spectre v2
- the CPU supports SMT and has SMT siblings
On Wed, Sep 05, 2018 at 02:37:35PM -0500, Rob Herring wrote:
> Use the for_each_of_cpu_node iterator to iterate over cpu nodes. This
> has the side effect of defaulting to iterating using "cpu" node names in
> preference to the deprecated (for FDT) device_type == "cpu".
>
> Cc: Borislav Petkov
>
On Thu 06-09-18 00:54:50, Souptick Joarder wrote:
> On Wed, Sep 5, 2018 at 7:05 PM Theodore Y. Ts'o wrote:
> >
> > On Wed, Sep 05, 2018 at 03:20:16PM +0530, Souptick Joarder wrote:
> > >
> > > "fs: convert return type int to vm_fault_t" is still under
> > > review/discusson and not yet merge
> > >
On Thu, 2018-09-06 at 09:35 +0200, Sebastian Andrzej Siewior wrote:
> On 2018-09-05 08:28:02 [-0400], Steven Rostedt wrote:
> > 4.14.63-rt41-rc1 stable review patch.
> > If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Sebastian Andrzej Siewior
> >
> >
On Thu, Sep 06, 2018 at 11:52:42AM +0800, Pu Wen wrote:
> In most of the normal use cases MCE is necessary. Rarely in some cases
> such as for test purpose MCE may be unselected.
Test with MCE disabled? Please elaborate.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-pos
Do we know what type of filesystem is on the root device?
Also, is there a way to tell if AppArmor denied something?
David
On Wed, Sep 05, 2018 at 12:54:51PM +0300, Mika Westerberg wrote:
> On Wed, Sep 05, 2018 at 11:05:10AM +0200, Lukas Wunner wrote:
> > On Mon, Sep 03, 2018 at 04:33:02PM +0300, Mika Westerberg wrote:
> > > Currently the driver logs quite a lot to the system message buffer even
> > > when doing normal
On Thu, Sep 06, 2018 at 10:13:00AM +0200, Peter Zijlstra wrote:
> No, you got it the first time. There are in fact more fixmap abusers;
> see drivers/acpi/apei/ghes.c. Also, as long as set_fixmap() allows
> overwriting a _PAGE_PRESENT pte and has that dodgy
> __flush_tlb_one_kernel() in it, the b
On Wed 05-09-18 18:59:33, Mike Rapoport wrote:
> The conversion is done using the following semantic patch:
>
> @@
> expression e;
> @@
> - alloc_bootmem_low_pages(e)
> + memblock_alloc_low(e, PAGE_SIZE)
>
> Signed-off-by: Mike Rapoport
Again, I trust Coccinelle to do the right thing and from a
On 27.8.2018 18:22, Luca Ceresoli wrote:
> Hi,
>
> thanks for your feedback.
>
> [Adding Michal Simek (Xilinx maintainer) in Cc]
>
> On 27/08/2018 14:27, Lars-Peter Clausen wrote:
>> On 08/24/2018 06:04 PM, Luca Ceresoli wrote:
>>> The default value of the PERIOD_LEN register is 0 and results in
On Wed, Sep 5, 2018 at 9:38 PM Rob Herring wrote:
> Iterating thru cpu nodes is a common pattern. Create a common iterator
> which can find child nodes either by node name or device_type == cpu.
> Using the former will allow for eventually dropping device_type
> properties which are deprecated for
On 09/04/2018 03:08 PM, Zhang Xianwei wrote:
> Refer to the commit f1395edbcec8 ("platform/x86: ideapad-laptop: Use
> __func__ instead of write_ec_cmd in pr_err"), prefer using '"%s...",
> __func__' to using 'read_ec_cmd' in read_ec_data.
>
> Signed-off-by: Zhang Xianwei
> ---
> drivers/platform
On 13/08/2018 23:48, Tony Krowiak wrote:
From: Tony Krowiak
Registers the matrix device created by the VFIO AP device
driver with the VFIO mediated device framework.
Registering the matrix device will create the sysfs
structures needed to create mediated matrix devices
each of which will be use
From: Marcel Ziswiler
Reorder NAND manufacturer ids for clarity.
Signed-off-by: Marcel Ziswiler
---
drivers/mtd/nand/raw/nand_ids.c | 20 ++--
include/linux/mtd/rawnand.h | 8
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/drivers/mtd/nand/raw/
From: Marcel Ziswiler
This patch enables support to read the ECC level from the NAND flash
using ESMT SLC NAND ID byte 5 information as documented e.g. in the
following data sheet:
https://www.esmt.com.tw/upload/pdf/ESMT/datasheets/F59L1G81LA(2Y).pdf
Signed-off-by: Marcel Ziswiler
---
drive
put_device will call vme_dev_release to free vdev, kfree is
unnecessary here.
Signed-off-by: Ding Xiang
---
drivers/vme/vme.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/vme/vme.c b/drivers/vme/vme.c
index 92500f6..520a5f9 100644
--- a/drivers/vme/vme.c
+++ b/drivers/vme/vme.c
@@
instructions_to_print var is assigned value 16 and there is no
way to change it.
This patch replaces it by a constant.
Signed-off-by: Christophe Leroy
---
arch/powerpc/kernel/process.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/arch/powerpc/kernel/process.c
On Thu, Sep 6, 2018 at 10:41 AM, David Howells wrote:
> Do we know what type of filesystem is on the root device?
ext4
The image is built with this script (you can find mkfs.ext4 there):
https://github.com/google/syzkaller/blob/master/tools/create-gce-image.sh
> Also, is there a way to tell if
Hi Mathieu,
On 05.09.2018 22:34, Mathieu Poirier wrote:
Hi Tomasz,
On Tue, Sep 04, 2018 at 04:20:34PM +0200, Tomasz Nowicki wrote:
For non-VHE systems host kernel runs at EL1 and jumps to EL2 whenever
hypervisor code should be executed. In this case ETM4x driver must
restrict configuration to
On 09/06/2018 01:48 PM, Thomas Gleixner wrote:
On Thu, 6 Sep 2018, Neeraj Upadhyay wrote:
On 09/05/2018 06:47 PM, Thomas Gleixner wrote:
On Wed, 5 Sep 2018, Neeraj Upadhyay wrote:
On 09/05/2018 05:53 PM, Thomas Gleixner wrote:
And looking closer this is a general issue. Just that the TEARD
On Sun, Sep 02, 2018 at 10:32:22AM -0700, Nadav Amit wrote:
> +void __init poking_init(void)
> +{
> + unsigned long poking_addr;
> +
> + poking_mm = copy_init_mm();
> + if (!poking_mm) {
> + pr_err("x86/mm: error setting a separate poking address space");
> + ret
use PTR_ERR_OR_ZERO for bpf__setup_stdout return code
Signed-off-by: Ding Xiang
---
tools/perf/util/bpf-loader.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/bpf-loader.c b/tools/perf/util/bpf-loader.c
index 47aac41..f9ae1a9 100644
--- a/tools/perf/util/bpf
From: Christophe Priouzeau
With change of syntax for 'simple-audio-card,dai-link' containers,
devicetrees of stih410 must be updated.
This fixes the following error:
[3.839466] asoc-simple-card sound: asoc_simple_card_dai_link_of:
Can't find simple-audio-card,cpu DT node
[3.849150] asoc
Le 21/08/2018 à 08:27, Michael Ellerman a écrit :
Christophe Leroy writes:
When two processes crash at the same time, we sometimes encounter
nesting in the middle of a line:
I think "interleaved" is the right word, rather than "nesting".
They're actually (potentially) completely unrelate
On Thu 2018-09-06 11:31:51, Sergey Senozhatsky wrote:
> Hello,
>
> On (09/05/18 21:33), Steven Rostedt wrote:
> > do_idle {
> >
> > [interrupts enabled]
> >
> > [interrupts disabled]
> > TRACE_IRQS_OFF [lockdep says irqs off]
> > [...]
> > TRACE_IRQS_IRET
> > test
On Wed 05-09-18 18:59:40, Mike Rapoport wrote:
> The conversion is done using
>
> sed -i 's@free_all_bootmem@memblock_free_all@' \
> $(git grep -l free_all_bootmem)
>
> Signed-off-by: Mike Rapoport
Acked-by: Michal Hocko
--
Michal Hocko
SUSE Labs
On Wed, Sep 5, 2018 at 11:20 PM Bjorn Helgaas wrote:
>
> On Fri, Aug 10, 2018 at 04:32:11AM +, Sinan Kaya wrote:
> > If _OSC execution fails today for platforms without an _OSC
> > entry, code is printing a misleading message saying disabling
> > ASPM as follows:
> >
> > acpi PNP0A03:00: _OSC
Add support for handling errors in enabling the component.
The ETM is enabled via cross call to owner CPU. Make
necessary changes to report the error back from the cross
call.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-etm4x.c | 39
Refactor the tmc-etr enable operation to make it easier to
handle errors in enabling the hardware. We need to make
sure that the buffer is compatible with the ETR. This
patch re-arranges to make the error handling easier, by
deferring the hardware enablement until all the errors
are checked. This a
Add support for reporting errors back from the SMP cross
function call for enabling ETM.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
Changes since v1:
- Fix build break, missing ;. (Mathieu Poirier)
---
drivers/hwtracing/coresight/coresight-etm3x.c | 42 ++-
Coresight architecture defines CLAIM tags for a device to negotiate
control of the components (external agent vs self-hosted). Each device
has a pair of registers (CLAIMSET & CLAIMCLR) for managing the CLAIM
tags. However, the protocol for the CLAIM tags is IMPLEMENTATION DEFINED.
PSCI has recommen
Use CLAIM protocol to make sure the device is available for use.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
.../coresight/coresight-dynamic-replicator.c | 23 +-
1 file changed, 18 insertions(+), 5 deletions(-)
diff --git a/drivers/hwtracing/coresight/cor
Use CLAIM tags to make sure the device is available for use.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-tmc-etf.c | 22 +++---
drivers/hwtracing/coresight/coresight-tmc-etr.c | 4
2 files changed, 23 insertions(+), 3 delet
Use the CLAIM protocol to grab the ownership of the component.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-funnel.c | 26 +-
1 file changed, 21 insertions(+), 5 deletions(-)
diff --git a/drivers/hwtracing/coresight/cores
Use the CLAIM protocol to grab the ownership of the component when
in use.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-catu.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/hwtracing/coresight/coresight-catu.c
b/drivers/hwtra
Coresight architecture defines CLAIM tags for a device to negotiate
control of the components (external agent vs self-hosted). Each device
has a pair of registers (CLAIMSET & CLAIMCLR) for managing the CLAIM
tags. However, the protocol for the CLAIM tags is IMPLEMENTATION DEFINED.
PSCI has recommen
Use the CLAIM tags to grab the device for self-hosted usage.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-etm3x.c | 16 +---
drivers/hwtracing/coresight/coresight-etm4x.c | 14 +++---
2 files changed, 24 insertions(+), 6 delet
When a replicator port is enabled, we block the traffic
on the other port and route all traffic to the new enabled
port. If there are two active trace sessions each targeting
the two different paths from the replicator, the second session
will disable the first session and route all the data to the
Prepare the etb10 driver to return errors in enabling
the device.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
Changes since v1:
- Rebased to the coresight/next
---
drivers/hwtracing/coresight/coresight-etb10.c | 18 +-
1 file changed, 13 insertions(+), 5 deletions(-
Make sure we honor the errors in CATU device and abort the operation.
While at it, delay setting the etr_buf for the session until we are
sure that we are indeed enabling the ETR.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
drivers/hwtracing/coresight/coresight-tmc-etr.c | 19 ++
On Thu, Sep 06, 2018 at 05:04:08PM +0800, Ding Xiang wrote:
> use PTR_ERR_OR_ZERO for bpf__setup_stdout return code
>
> Signed-off-by: Ding Xiang
> ---
> tools/perf/util/bpf-loader.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/perf/util/bpf-loader.c b/tools/pe
Prepare to handle errors in enabling the hardware and
report it back to the core driver.
Cc: Mathieu Poirier
Signed-off-by: Suzuki K Poulose
---
Changes since v1:
- Fix return code for tmc_enable_etf_link (Mathieu Poirier)
---
drivers/hwtracing/coresight/coresight-tmc-etf.c | 73 ++
coresight_enable_path() enables the components in a trace
path from a given source to a sink, excluding the source.
The operation is performed in the reverse order; the sink
first and then backwards in the list. However, if we encounter
an error in enabling any of the component, we simply disable
a
On Sun, Sep 02, 2018 at 07:15:07PM -0700, Randy Dunlap wrote:
> Date: Sun, 2 Sep 2018 19:15:07 -0700
> From: Randy Dunlap
> To: Kenneth Lee , Jonathan Corbet ,
> Herbert Xu , "David S . Miller"
> , Joerg Roedel , Alex Williamson
> , Kenneth Lee , Hao
> Fang , Zhou Wang , Zaibo Xu
> , Philippe
1 - 100 of 979 matches
Mail list logo
