On Tue, Jan 23, 2018 at 11:57 PM, David Lechner wrote:
> This sets the regmap name to the device tree node name. This is useful
> for debugging.
>
> Signed-off-by: David Lechner
Looks reasonable,
Acked-by: Arnd Bergmann
On Tue, Jan 23, 2018 at 06:53:18PM -0800, Joe Perches wrote:
> On Tue, 2018-01-23 at 23:12 +, Bart Van Assche wrote:
> > On Tue, 2018-01-23 at 04:45 -0800, Joe Perches wrote:
> > > Perhaps the email subject could be improved to describe
> > > the new macro and as well, this macro, without a pr_
2018-01-23 21:23 GMT+01:00 David Lechner :
> On 01/23/2018 02:05 PM, David Lechner wrote:
>>
>> On 01/23/2018 02:01 PM, David Lechner wrote:
>>>
>>> On 01/23/2018 01:53 PM, Bartosz Golaszewski wrote:
In the mdio case - the problem is that devm_clk_get() doesn't fail,
but somehow
2018-01-23 21:49 GMT+08:00 Mike Galbraith :
> On Tue, 2018-01-23 at 18:36 +0800, Wanpeng Li wrote:
>>
>> Thanks for having a try, Mike. :) Actually the two context1 tasks
>> don't stack up on one logical cpu at the most of time which is
>> observed by kernelshark. Do you have any idea why there is
On Wed, Jan 24, 2018 at 8:48 AM, Serge Semin wrote:
> Sparse is whining about the u32 and __le32 mixed usage in the driver
>
> drivers/ntb/test/ntb_perf.c:288:21: warning: cast to restricted __le32
> drivers/ntb/test/ntb_perf.c:295:37: warning: incorrect type in argument 4
> (different base types
On 01/23/2018 06:07 PM, Dominik Brodowski wrote:
> On Tue, Jan 23, 2018 at 02:07:01PM +0100, Martin Schwidefsky wrote:
>> Add the PR_ISOLATE_BP operation to prctl. The effect of the process
>> control is to make all branch prediction entries created by the execution
>> of the user space code of t
Thanks Greg, Andy
How about c198b121b1a1d7a7171770c634cd49191bac4477?
Will both patches go to stable kernel?
BR.
Ning.
-Original Message-
From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org]
Sent: Tuesday, January 23, 2018 3:26 PM
To: Andy Lutomirski
Cc: Zhang, Ning A ;
On Tue 23-01-18 14:22:07, David Rientjes wrote:
> On Tue, 23 Jan 2018, Michal Hocko wrote:
>
> > > It can't, because the current patchset locks the system into a single
> > > selection criteria that is unnecessary and the mount option would become
> > > a
> > > no-op after the policy per subtre
On Wed, Jan 24, 2018 at 03:50:10PM +0800, linxiu...@gmail.com wrote:
> From: "leilei.lin"
>
> Do not install cgroup event into the CPU context if the cgroup
> is not running on this CPU
>
> While there is no task of cgroup running specified CPU, current
> kernel still install cgroup event into C
Hi,
Le Thursday 18 Jan 2018 à 10:38:07 (+), Morten Rasmussen a écrit :
> On Mon, Jan 15, 2018 at 09:26:09AM +0100, Vincent Guittot wrote:
> > Le Wednesday 03 Jan 2018 à 10:16:00 (+0100), Vincent Guittot a écrit :
> > > Hi Peter,
> > >
> > > On 22 December 2017 at 21:42, Peter Zijlstra wrote:
Am 23.01.2018 21:10, schrieb Christopher Díaz Riveros:
> Use PTR_ERR_OR_ZERO rather than if(IS_ERR(...)) + PTR_ERR
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Christopher Díaz Riveros
> ---
> drivers/misc/mic/scif/scif_epd.h | 4 +---
> 1 file changed, 1 i
Add tracepoints for nvme command submission and completion. The tracepoints
are modeled after SCSI's trace_scsi_dispatch_cmd_start() and
trace_scsi_dispatch_cmd_done() tracepoints and fulfil a similar purpose,
namely a fast way to check which command is going to be queued into the HW or
Fabric driv
On Tue, Jan 23, 2018 at 11:59:35PM +, James Hogan wrote:
> On Thu, Jan 18, 2018 at 01:23:12AM +0300, Serge Semin wrote:
> > Memblock allocator can be successfully used from now for early
> > memory management
> >
> > Signed-off-by: Serge Semin
>
> Am I correct that intermediate commits in t
Add tracepoints for nvme_setup_cmd() for tracing admin and/or nvm commands.
Examples of the two tracepoints are as follows for trace_nvme_setup_admin_cmd():
kworker/u8:0-5 [003] 2.998792: nvme_setup_admin_cmd: cmdid=14,
flags=0x0, meta=0x0, cmd=(nvme_admin_create_cq cqid=1, qsize=102
On Wednesday 24 January 2018 12:54 PM, Ladislav Michl wrote:
> Keerthy,
>
> On Wed, Jan 24, 2018 at 11:14:40AM +0530, Keerthy wrote:
>> Adapt driver to utilize dmtimer pdata ops instead of pdata-quirks.
>>
>> Signed-off-by: Keerthy
>> Acked-by: Neil Armstrong
>> Reviewed-by: Claudiu Beznea
>>
Add a tracepoint in nvme_complete_rq() for completions of NVMe commands. An
expmale output of the trace-point is as follows:
-0 [001] d.h. 3.505266: nvme_complete_rq: cmdid=989, qid=1,
res=0, retries=0, flags=0x0, status=0
Signed-off-by: Johannes Thumshirn
Reviewed-by: Hannes Reinecke
On Tue, 2018-01-23 at 17:28 -0800, Dave Hansen wrote:
> On 01/23/2018 05:23 PM, Woodhouse, David wrote:
> >
> > On Tue, 2018-01-23 at 10:43 -0800, Dave Hansen wrote:
> ...
> >
> > >
> > > >
> > > > /* Intel-defined CPU features, CPUID level 0x0007:0 (EDX), word
> > > > 18 */
> > > > #d
2018-01-24 16:20 GMT+08:00 Peter Zijlstra :
> On Wed, Jan 24, 2018 at 03:50:10PM +0800, linxiu...@gmail.com wrote:
>> From: "leilei.lin"
>>
>> Do not install cgroup event into the CPU context if the cgroup
>> is not running on this CPU
>>
>> While there is no task of cgroup running specified CPU,
On 2018/01/22 10:01, Alexander Duyck wrote:
[...]
> >
> > If the patch that I submitted for the current vmware issue is merged,
> > the significant commits that are left are:
> >
> > 0a8047ac68e5 e1000e: Fix msi-x interrupt automask (v4.5-rc1)
> > Fixes a problem in the irq disabling of the
From: Eric Biggers
The SHA-512 multibuffer code keeps track of the number of blocks pending
in each lane. The minimum of these values is used to identify the next
lane that will be completed. Unused lanes are set to a large number
(0x) so that they don't affect this calculation.
Howeve
On Wed, Jan 24, 2018 at 07:29:53AM +0100, Martin Schwidefsky wrote:
> On Tue, 23 Jan 2018 18:07:19 +0100
> Dominik Brodowski wrote:
>
> > On Tue, Jan 23, 2018 at 02:07:01PM +0100, Martin Schwidefsky wrote:
> > > Add the PR_ISOLATE_BP operation to prctl. The effect of the process
> > > control is
On Tue, Jan 23, 2018 at 04:52:53PM +, David Woodhouse wrote:
> AMD exposes the PRED_CMD/SPEC_CTRL MSRs slightly differently to Intel.
> Documented at https://lkml.org/lkml/2018/1/21/112
lkml.org is not very stable. Maybe use messageid-based url instead?
http://lkml.kernel.org/r/2b3e25cc-286d-
On 01/23/2018 05:41 PM, Lee Jones wrote:
> On Tue, 23 Jan 2018, Fabrice Gasnier wrote:
>> On 01/23/2018 04:30 PM, Lee Jones wrote:
>>> On Tue, 23 Jan 2018, Fabrice Gasnier wrote:
>>>
On 01/23/2018 02:32 PM, Lee Jones wrote:
> On Tue, 16 Jan 2018, Fabrice Gasnier wrote:
>
>> STM32 T
On Tue, Jan 23, 2018 at 07:31:27PM +0200, Andy Shevchenko wrote:
> On Tue, Jan 23, 2018 at 4:37 PM, Corentin Labbe wrote:
> > Nothing in kernel use VIDEO_ATOMISP_OV8858 since commit 3a81c7660f80
> > ("media: staging: atomisp: Remove IMX sensor support")
> > Lets remove this kconfig option.
>
> F
On Wed, 2018-01-24 at 11:39 +0300, Kirill A. Shutemov wrote:
> On Tue, Jan 23, 2018 at 04:52:53PM +, David Woodhouse wrote:
> >
> > AMD exposes the PRED_CMD/SPEC_CTRL MSRs slightly differently to Intel.
> > Documented at https://lkml.org/lkml/2018/1/21/112
>
> lkml.org is not very stable. Mayb
> So it works, but you are complaining anyway?
How serious do you interpret such information in the SmPL manual?
>> https://github.com/coccinelle/coccinelle/blob/bf1c6a5869dd324f5faeeaa3a12d57270e478b21/docs/manual/cocci_syntax.tex#L50
>>
>> “…
>> Furthermore, @ should not be used in this code.
Mathhew,
Just a minor question.
On Wed, 2018-01-17 at 12:20 -0800, Matthew Wilcox wrote:
> This is a direct replacement for struct radix_tree_root. Some of the
> struct members have changed name; convert those, and use a #define so
> that radix_tree users continue to work without change.
>
> Si
On 2018-01-09 17:37, Andrey Ryabinin wrote:
> strscpy() performs the word-at-a-time optimistic reads. So it may
> may access the memory past the end of the object, which is perfectly fine
> since strscpy() doesn't use that (past-the-end) data and makes sure the
> optimistic read won't cross a page
On Tue, Jan 23, 2018 at 08:58:36PM +, David Woodhouse wrote:
> +static const struct sku_microcode spectre_bad_microcodes[] = {
> + { INTEL_FAM6_KABYLAKE_DESKTOP, 0x0B, 0x80 },
> + { INTEL_FAM6_KABYLAKE_MOBILE, 0x0A, 0x80 },
> + { INTEL_FAM6_KABYLAKE_MOBILE, 0x0A, 0x80 },
> + {
Topic/Subject: Facebook Email Notifications Stopped for Several Months
Before Returning on 21 Jan 2018 Sunday
Singapore Government Linked Company (GLC) Keppel
Corporation bribed Brazilian Government Officials with $55 MILLION
over 14 years
My best guess is that secret Singapore Government agents
On Wed, 24 Jan 2018 08:46:50 +0100
Ingo Molnar wrote:
> No fundamental objections from me, assuming they are well tested.
>
Yeah, I ran it through my ftrace test suite, and they did fine till I
hit test 20 of 34, which tests static ftrace (CONFIG_DYNAMIC_FTRACE not
set), and it crashed. I'm ho
On 2018-01-09 17:47, Andrey Ryabinin wrote:
> Attached user space program I used to see the difference.
> Usage:
> gcc -02 -o strscpy strscpy_test.c
> ./strscpy {b|w} src_str_len count
>
> src_str_len - length of source string in between 1-4096
> count - how many strscpy() to execute.
2018-01-24 0:32 GMT+01:00 Laurent Pinchart :
> Hi Philippe,
>
> On Tuesday, 23 January 2018 12:25:51 EET Philippe CORNU wrote:
>> On 01/23/2018 12:30 AM, Laurent Pinchart wrote:
>> > On Monday, 22 January 2018 12:26:08 EET Philippe Cornu wrote:
>> >> Add SPDX identifiers to the Synopsys DesignWare
On 23.01.2018 20:32, Steven Rostedt wrote:
> With the new ORC unwinder, ftrace stack tracing became disfunctional.
>
> One was that ORC didn't know how to handle the ftrace callbacks in
> general (which Josh fixed). The other was that ORC would just bail
> if it hit a dynamically allocated tramp
On Tue, Jan 23, 2018 at 08:25:33AM +0100, gre...@linuxfoundation.org wrote:
> On Mon, Jan 22, 2018 at 07:06:29PM -0800, Andy Lutomirski wrote:
> > On Mon, Jan 22, 2018 at 6:59 PM, Zhang, Ning A
> > wrote:
> > > hello, Greg, Andy, Thomas
> > >
> > > would you like to backport these two patches to
On Wed, Jan 24, 2018 at 08:19:44AM +, Zhang, Ning A wrote:
> Thanks Greg, Andy
>
> How about c198b121b1a1d7a7171770c634cd49191bac4477?
Why do you think that is needed in the older stable kernels? What
problem does it solve? Do any distros have this patch in their kernels?
thanks,
greg k-h
On Wed, 2018-01-24 at 09:47 +0100, Peter Zijlstra wrote:
> Typically tglx likes to use x86_match_cpu() for these things; see also
> commit: bd9240a18edfb ("x86/apic: Add TSC_DEADLINE quirk due to
> errata").
Thanks, will fix. I think we might also end up in whitelist mode,
adding "known good" micr
An application running with libhugetlbfs fails to allocate
additional pages to HEAP due to the hugemap being done
inconditionally as topdown mapping:
mmap(0x1008, 1572864, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS|0x4, -1, 0) = 0x73e8
[...]
mmap(0x7400, 1048576, PROT_READ|PR
While the implementation of the "slices" address space allows
a significant amount of high slices, it limits the number of
low slices to 16 due to the use of a single u64 low_slices_psize
element in struct mm_context_t
On the 8xx, the minimum slice size is the size of the area
covered by a single
On Tue, Jan 23, 2018 at 07:30:06PM -0700, Shuah Khan wrote:
> commit 2f2d0088eb93 ("usbip: prevent vhci_hcd driver from leaking a
> socket pointer address")
Now queued up for 4.4 and 4.9, thanks.
greg k-h
On Tue, Jan 23, 2018 at 10:22:54AM -0800, Guenter Roeck wrote:
> On Tue, Jan 23, 2018 at 01:18:01PM +0100, Michael Grzeschik wrote:
> > We add support for the ISL1219 chip that got an integrated tamper
> > detection function. This patch implements the feature by using an hwmon
> > interface.
> >
>
bitmap_or() and bitmap_andnot() can work properly with dst identical
to src1 or src2. There is no need of an intermediate result bitmap
that is copied back to dst in a second step.
Signed-off-by: Christophe Leroy
---
v2: New in v2
v3: patch moved up front of the serie to avoid ephemeral slice_b
In preparation for the following patch which will fix an issue on
the 8xx by re-using the 'slices', this patch enhances the
'slices' implementation to support 32 bits CPUs.
On PPC32, the address space is limited to 4Gbytes, hence only the low
slices will be used.
This patch moves "slices" functio
On the 8xx, the page size is set in the PMD entry and applies to
all pages of the page table pointed by the said PMD entry.
When an app has some regular pages allocated (e.g. see below) and tries
to mmap() a huge page at a hint address covered by the same PMD entry,
the kernel accepts the hint all
Hi all,
This series adds API for 128-bit memory IO access and enables it for ARM64.
The original motivation for 128-bit API came from new Cavium network device
driver. The hardware requires 128-bit access to make things work. See
description in patch 3 for details.
Also, starting from ARMv8.4, st
Architectures like arm64 support 128-bit integer types and
operations. This patch introduces corresponding types and
__swab128() operation for be/le conversions.
They are required to implement 128-bit access to the memory,
in following patches.
Signed-off-by: Yury Norov
---
include/linux/byteor
Introduce __raw_writeo(), __raw_reado() and other arch-specific
RW functions for 128-bit memory access, and enable it for arm64.
128-bit I/O is required for example by Octeon TX2 device to access
some registers. According to Hardware Reference Manual:
A 128-bit write to the OP_FREE0/1 registers f
Some architectures, like arm64, support 128-bit memory access. For
ARM64 - using load/store pair instructions. This patch introduces
reado() and writeo() functions family, where suffix 'o' stands for
reading and writing the octet of bytes at once.
Signed-off-by: Yury Norov
---
include/asm-generi
On Wed 24-01-18 10:39:41, Anshuman Khandual wrote:
> On 01/23/2018 09:36 PM, Michal Hocko wrote:
> > On Tue 23-01-18 21:28:28, Anshuman Khandual wrote:
> >> On 01/23/2018 06:15 PM, Michal Hocko wrote:
> >>> On Tue 23-01-18 16:55:18, Anshuman Khandual wrote:
> On 01/17/2018 01:37 PM, Michal Hoc
On Wed, Jan 24, 2018 at 09:02:21AM +, David Woodhouse wrote:
> On Wed, 2018-01-24 at 09:47 +0100, Peter Zijlstra wrote:
> > Typically tglx likes to use x86_match_cpu() for these things; see also
> > commit: bd9240a18edfb ("x86/apic: Add TSC_DEADLINE quirk due to
> > errata").
>
> Thanks, will
On Tue, Jan 23, 2018 at 07:32:11PM -0700, Shuah Khan wrote:
> From: Jonathan Dieter
>
> Upstream commit cfd6ed4537a9 ("usbip: Fix implicit fallthrough warning")
>
> GCC 7 now warns when switch statements fall through implicitly, and with
> -Werror enabled in configure.ac, that makes these tools
On 01/24/2018 02:32 PM, Christophe Leroy wrote:
An application running with libhugetlbfs fails to allocate
additional pages to HEAP due to the hugemap being done
inconditionally as topdown mapping:
mmap(0x1008, 1572864, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS|0x4, -1, 0) = 0x7
On Wed, Jan 24, 2018 at 04:32:38PM +0800, Lin Xiulei wrote:
> >> kernel/events/core.c | 44 +++-
> >> 1 file changed, 31 insertions(+), 13 deletions(-)
> >>
> >> diff --git a/kernel/events/core.c b/kernel/events/core.c
> >> index 4df5b69..f766b60 100644
> >>
Good Day,
Please accept my apologies for writing you a surprise letter.I am
Mr.Ahmed Owain, account Manager with an investment bank here in
Burkina Faso.I have a very important business I want to discuss with
you.There is a draft account opened in my firm by a long-time client
of our bank.I have t
2018-01-24 17:14 GMT+08:00 Peter Zijlstra :
> On Wed, Jan 24, 2018 at 04:32:38PM +0800, Lin Xiulei wrote:
>> >> kernel/events/core.c | 44 +++-
>> >> 1 file changed, 31 insertions(+), 13 deletions(-)
>> >>
>> >> diff --git a/kernel/events/core.c b/kernel/eve
On Wed, 2018-01-24 at 09:37 +0100, Dominik Brodowski wrote:
> On Wed, Jan 24, 2018 at 07:29:53AM +0100, Martin Schwidefsky wrote:
> >
> > On Tue, 23 Jan 2018 18:07:19 +0100
> > Dominik Brodowski wrote:
> >
> > >
> > > On Tue, Jan 23, 2018 at 02:07:01PM +0100, Martin Schwidefsky wrote:
> > > >
Hi Brian,
On 01/23/2018 09:49 PM, Brian Norris wrote:
> Hi,
>
> Philippe asked me to review the last version. I'm not sure I have a lot
> to contribute. Maybe Rockchip folks who wrote this stuff in the first
> place might. I've CC'd some.
>
> On Tue, Jan 23, 2018 at 06:08:06PM +0100, Philippe C
According to latest reference manual (Rev.2, 9/2017),
previous CKO1/2's mux options are incorrect, update
them.
Signed-off-by: Anson Huang
---
drivers/clk/imx/clk-imx6sx.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/clk/imx/clk-imx6sx.c b/drivers/cl
Le 24/01/2018 à 10:15, Aneesh Kumar K.V a écrit :
On 01/24/2018 02:32 PM, Christophe Leroy wrote:
An application running with libhugetlbfs fails to allocate
additional pages to HEAP due to the hugemap being done
inconditionally as topdown mapping:
mmap(0x1008, 1572864, PROT_READ|PROT_WR
On Tue 23-01-18 17:39:19, Michel Dänzer wrote:
> On 2018-01-23 04:36 PM, Michal Hocko wrote:
> > On Tue 23-01-18 15:27:00, Roman Gushchin wrote:
> >> On Thu, Jan 18, 2018 at 06:00:06PM +0100, Michal Hocko wrote:
> >>> On Thu 18-01-18 11:47:48, Andrey Grodzovsky wrote:
> Hi, this series is a re
Hello,
4th round for this series, now based on Hans' 'parm' branch from
git://linuxtv.org/hverkuil/media_tree.git
I addressed Sakari's comments on bindings documentation and driver error path,
and I hope to get both driver and bindings acked to have this included in next
merge window.
Thanks
ov7670 driver supports two optional properties supplied through platform
data, but currently does not support any standard video interface
property.
Add support through OF parsing for 2 generic properties (vsync and hsync
polarities) and for one custom property already supported through
platform d
Describe newly introduced OF properties for ov7670 image sensor.
The driver supports two standard properties to configure synchronism
signals polarities and one custom property already supported as
platform data options to suppress pixel clock during horizontal
blankings.
Re-phrase child nodes des
On Wed, Jan 24, 2018 at 01:58:19PM +0530, Keerthy wrote:
> On Wednesday 24 January 2018 12:54 PM, Ladislav Michl wrote:
> > Keerthy,
> >
> > On Wed, Jan 24, 2018 at 11:14:40AM +0530, Keerthy wrote:
> >> Adapt driver to utilize dmtimer pdata ops instead of pdata-quirks.
> >>
> >> Signed-off-by: Kee
> > > + for (i = 0; i < ARRAY_SIZE(spectre_bad_microcodes); i++) {
> > > + if (c->x86_model == spectre_bad_microcodes[i].model &&
> > > + c->x86_mask == spectre_bad_microcodes[i].stepping)
> > > + return (c->microcode <=
> > > spectre_bad_microcodes[i].microcode
On 01/24/2018 02:57 PM, Christophe LEROY wrote:
Le 24/01/2018 à 10:15, Aneesh Kumar K.V a écrit :
On 01/24/2018 02:32 PM, Christophe Leroy wrote:
An application running with libhugetlbfs fails to allocate
additional pages to HEAP due to the hugemap being done
inconditionally as topdown ma
On Mon, Jan 22, 2018 at 06:16:19PM +0100, Daniel Bristot de Oliveira wrote:
> --- %< ---
> Here it is! the backport for 4.4.y-stable.
>
> The main difference from the original commit is that
> the BW_SHIFT define was not present yet. As BW_SHIFT was
> introduced in a new fe
On Wed, Jan 10, 2018 at 09:02:23AM -0800, Tejun Heo wrote:
> 1. Console is IPMI emulated serial console. Super slow. Also
>netconsole is in use.
So my IPMI SoE typically run at 115200 Baud (or higher) and I've not had
trouble like that (granted I don't typically trigger OOM storms, but
they
Tejun Heo reported that net_console can cause recursive printk()-s
from call_console_drivers() (under OOM/etc.) and this can lockup that
CPU, because CPU calls call_console_drivers() to print pending logbufs,
but recursive printk() issued by one of console drivers adds several
new messages to the l
Le 24/01/2018 à 10:35, Aneesh Kumar K.V a écrit :
On 01/24/2018 02:57 PM, Christophe LEROY wrote:
Le 24/01/2018 à 10:15, Aneesh Kumar K.V a écrit :
On 01/24/2018 02:32 PM, Christophe Leroy wrote:
An application running with libhugetlbfs fails to allocate
additional pages to HEAP due to
On Wed, Jan 24, 2018 at 05:19:34PM +0800, Lin Xiulei wrote:
> Sure, and I consider this "OK" works for "What goes wrong if we leave
> it set?". : )
It would be good if you inspect the code for the case of leaving
cpuctx->cgrp set with no cgroup events left -- AND -- put a blurb about
what you foun
Hi Serge,
On 23/01/18 19:10, Serge Semin wrote:
Hello Matt,
On Tue, Jan 23, 2018 at 03:35:14PM +, Matt Redfearn
wrote:
Hi Serge,
On 19/01/18 14:27, Serge Semin wrote:
On Fri, Jan 19, 2018 at 07:59:43AM +, Matt Redfearn
wrote:
Hello Matt,
Hi Serge,
On 18/01/18 20:18, Serge S
Hi Serge,
On 23/01/18 19:27, Serge Semin wrote:
Hello Matt,
On Tue, Jan 23, 2018 at 11:03:27AM +, Matt Redfearn
wrote:
Hi Serge,
On 22/01/18 21:47, Serge Semin wrote:
Hello Matt,
On Mon, Jan 22, 2018 at 04:35:26PM +, Matt Redfearn
wrote:
Hi Serge,
On 17/01/18 22:23, Serge Semi
On 01/24/2018 03:09 PM, Christophe LEROY wrote:
Le 24/01/2018 à 10:35, Aneesh Kumar K.V a écrit :
Did you try with HUGETLB_MORECORE_HEAPBASE=0x1100 on PPC64 as I
suggested in my last email on this subject (22/01/2018 9:22) ?
yes. The test ran fine for me
You tried with 0x300
There is no problem whatsoever!
I'm beginner on this so every correction or warning is welcolme.
Thank you both for your help!
--
Alberto Ponces
On Tue, Jan 23, 2018 at 05:18:44PM -0800, Dmitry Torokhov wrote:
> On Tue, Jan 23, 2018 at 05:02:59PM -0800, Darren Hart wrote:
> > On Tue, Jan 23, 20
Hi Brian,
On 01/23/2018 10:15 PM, Brian Norris wrote:
> Hi Philippe,
>
> On Thu, Jan 18, 2018 at 11:40:48AM +, Philippe CORNU wrote:
>> On 01/11/2018 12:16 PM, Philippe CORNU wrote:
>>> To be honest, I do not really like the memcpy here too and I agree with
>>> you regarding the BE issue.
>>>
On Mon, Jan 22, 2018 at 1:09 PM, JeffyChen wrote:
> Hi Randy,
>
>
> On 01/22/2018 10:15 AM, JeffyChen wrote:
>>
>> Hi Randy,
>>
>> On 01/22/2018 09:18 AM, Randy Li wrote:
>>> Also the power domain driver could manage the clocks as well, I would
>>> suggest to use pm_runtime_*.
>>
>>
>> a
On Tue, 23 Jan 2018, Matt Turner wrote:
> On Tue, Jan 23, 2018 at 2:23 AM, Mikulas Patocka wrote:
> >
> >
> > On Sat, 20 Jan 2018, Matt Turner wrote:
> >
> >> Hi Linus,
> >>
> >> Please pull my alpha git tree. It contains a build fix and a regression
> >> fix.
> >>
> >> Hopefully still in time
On Tue, Jan 23, 2018 at 06:32:16PM +0100, Borislav Petkov wrote:
> It's probably not even worth doing anything though - I doubt the speedup
> is visible at all.
One more thing I forgot to mention yesterday: I'm working on changing
the CPUID parsing we do now and we'll probably end up simply readin
On Wed, 24 Jan 2018, Greg Kroah-Hartman wrote:
> But will Andi's patch work well for you? Adding a MODULE_INFO() tag to
> every module?
Yes, that would work -- all the modules that get built in tree, or out of
tree but with retpolined compiler, would have that marker that could be
optionall
Use bool in place of int in the function try_wait_for_completion.
Signed-off-by: Gaurav Jindal
---
diff --git a/kernel/sched/completion.c b/kernel/sched/completion.c
index 0926aef..3e15e8d 100644
--- a/kernel/sched/completion.c
+++ b/kernel/sched/completion.c
@@ -283,7 +283,7 @@ int __sched wait
On Wed, Jan 24, 2018 at 11:32:00AM +1100, Kees Cook wrote:
> I've wanted this for a while (especially for the coming detected
> support for stack protector). Having more than just the clfags is, I
> think, important. We'd likely want to record the entire environment
> (compiler version, linker vers
2018-01-24 17:46 GMT+08:00 Peter Zijlstra :
> On Wed, Jan 24, 2018 at 05:19:34PM +0800, Lin Xiulei wrote:
>> Sure, and I consider this "OK" works for "What goes wrong if we leave
>> it set?". : )
>
> It would be good if you inspect the code for the case of leaving
> cpuctx->cgrp set with no cgroup
Alex / Joerg,
On 1/24/18 5:04 AM, Alex Williamson wrote:
@@ -648,12 +685,40 @@ static int vfio_iommu_type1_unpin_pages(void *iommu_data,
return i > npage ? npage : (i > 0 ? i : -EINVAL);
}
+static size_t try_unmap_unpin_fast(struct vfio_domain *domain, dma_addr_t iova,
+
Le 24/01/2018 à 10:51, Aneesh Kumar K.V a écrit :
On 01/24/2018 03:09 PM, Christophe LEROY wrote:
Le 24/01/2018 à 10:35, Aneesh Kumar K.V a écrit :
Did you try with HUGETLB_MORECORE_HEAPBASE=0x1100 on PPC64 as I
suggested in my last email on this subject (22/01/2018 9:22) ?
yes
Hello Matt,
On Wed, Jan 24, 2018 at 09:49:31AM +, Matt Redfearn
wrote:
> Hi Serge,
>
> On 23/01/18 19:27, Serge Semin wrote:
> >Hello Matt,
> >
> >On Tue, Jan 23, 2018 at 11:03:27AM +, Matt Redfearn
> > wrote:
> >>Hi Serge,
> >>
> >>On 22/01/18 21:47, Serge Semin wrote:
> >>>Hello Matt
On Wed, 24 Jan 2018 03:49:04 -0500
Steven Rostedt wrote:
> On Wed, 24 Jan 2018 08:46:50 +0100
> Ingo Molnar wrote:
>
>
> > No fundamental objections from me, assuming they are well tested.
> >
>
> Yeah, I ran it through my ftrace test suite, and they did fine till I
> hit test 20 of 34, wh
On Tue, 2018-01-09 at 22:39 +0100, Daniel Borkmann wrote:
> On 01/09/2018 07:04 PM, Alexei Starovoitov wrote:
> >
> > The BPF interpreter has been used as part of the spectre 2 attack
> > CVE-2017-5715.
> >
> > A quote from goolge project zero blog:
> > "At this point, it would normally be neces
Hello Matt,
On Wed, Jan 24, 2018 at 09:46:07AM +, Matt Redfearn
wrote:
> Hi Serge,
>
> On 23/01/18 19:10, Serge Semin wrote:
> >Hello Matt,
> >
> >On Tue, Jan 23, 2018 at 03:35:14PM +, Matt Redfearn
> > wrote:
> >>Hi Serge,
> >>
> >>On 19/01/18 14:27, Serge Semin wrote:
> >>>On Fri, Ja
On 01/24/2018 03:33 PM, Christophe LEROY wrote:
Le 24/01/2018 à 10:51, Aneesh Kumar K.V a écrit :
On 01/24/2018 03:09 PM, Christophe LEROY wrote:
Le 24/01/2018 à 10:35, Aneesh Kumar K.V a écrit :
Did you try with HUGETLB_MORECORE_HEAPBASE=0x1100 on PPC64 as I
suggested in my la
On 23/01/18 18:44, Lina Iyer wrote:
> On Tue, Jan 23 2018 at 18:15 +, Sudeep Holla wrote:
>> Hi Lina,
>>
>> On Tue, Jan 23, 2018 at 5:56 PM, Lina Iyer wrote:
>>> On newer Qualcomm Techonologies Inc's SoCs like the SDM845, the GIC
>>> is in a
>>> power domain that can be powered off when not
On 01/24/2018 11:07 AM, David Woodhouse wrote:
> On Tue, 2018-01-09 at 22:39 +0100, Daniel Borkmann wrote:
>> On 01/09/2018 07:04 PM, Alexei Starovoitov wrote:
>>>
>>> The BPF interpreter has been used as part of the spectre 2 attack
>>> CVE-2017-5715.
>>>
>>> A quote from goolge project zero blog
Simplify error handling by using devm_ioremap_shared_resource().
Signed-off-by: Ladislav Michl
---
Changes:
- v2: None
drivers/mtd/nand/davinci_nand.c | 24 +++-
1 file changed, 7 insertions(+), 17 deletions(-)
diff --git a/drivers/mtd/nand/davinci_nand.c b/drivers/mtd/na
Move devm_ioremap_resource() out of device.h into io.h to be
consistent with similar APIs.
Signed-off-by: Ladislav Michl
---
Changes:
- v2: new patch
include/linux/device.h | 2 --
include/linux/io.h | 1 +
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/include/linux/device
Implement managed ioremap function for shared resources.
Signed-off-by: Ladislav Michl
---
Changes:
- v2: Rebased on top of PATCH v2 1/3
include/linux/io.h | 8 +++-
lib/devres.c | 22 ++
2 files changed, 21 insertions(+), 9 deletions(-)
diff --git a/include/li
Many drivers can simplified by using devm_ioremap_resource()
instead of open coding its functionality. However, as pointed
by Wei Yongjun, that function cannot be used when memory region
is already taken. See previous discussion here:
https://www.spinics.net/lists/linux-pci/msg68495.html
To ease j
On Tue, Jan 23, 2018 at 10:00:58PM +, Liang, Kan wrote:
> > On Fri, Jan 19, 2018 at 12:24:17PM -0800, Andi Kleen wrote:
> > > > Oh, think a bit more.
> > > > I think we cannot do the same thing as we did for CPU PMU's fixed
> > counters.
> > > >
> > > > The counters here are free running counte
On 01/22/2018 09:46 AM, Liam Mark wrote:
Since commit 204f672255c2 ("staging: android: ion: Use CMA APIs directly")
the CMA API is now used directly and therefore the allocated memory is no
longer automatically zeroed.
Explicitly zero CMA allocated memory to ensure that no data is exposed to
use
Le 24/01/2018 à 11:08, Aneesh Kumar K.V a écrit :
On 01/24/2018 03:33 PM, Christophe LEROY wrote:
Le 24/01/2018 à 10:51, Aneesh Kumar K.V a écrit :
On 01/24/2018 03:09 PM, Christophe LEROY wrote:
Le 24/01/2018 à 10:35, Aneesh Kumar K.V a écrit :
Did you try with HUGETLB_MORECORE_
On Wed, Jan 24, 2018 at 12:05:16PM +0300, Yury Norov wrote:
> This series adds API for 128-bit memory IO access and enables it for ARM64.
> The original motivation for 128-bit API came from new Cavium network device
> driver. The hardware requires 128-bit access to make things work. See
> descripti
1 - 100 of 855 matches
Mail list logo
