Commit-ID: 872523233d640c21ce13ea51269c5c031ebb2f78
Gitweb: https://git.kernel.org/tip/872523233d640c21ce13ea51269c5c031ebb2f78
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 18 Jan 2018 13:07:00 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 18 Jan 2018 13:07:00 -0300
p
Commit-ID: 56271170438df39c1b9a39c7aaf69010e6a4b59a
Gitweb: https://git.kernel.org/tip/56271170438df39c1b9a39c7aaf69010e6a4b59a
Author: Arnaldo Carvalho de Melo
AuthorDate: Thu, 18 Jan 2018 10:28:14 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 18 Jan 2018 10:28:14 -0300
p
Commit-ID: 936f1f30bb7892f010670f1edebc419d47b139b1
Gitweb: https://git.kernel.org/tip/936f1f30bb7892f010670f1edebc419d47b139b1
Author: Adrian Hunter
AuthorDate: Tue, 16 Jan 2018 15:14:52 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 18 Jan 2018 09:01:23 -0300
perf tools:
On Wednesday 24 January 2018 04:49 PM, 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
> ---
> Changes in v9:
>
> * Reorganized the place where of_node_put was called.
>
Commit-ID: 59a87fdad1467d228acc5cb1303b0b568a9e86a8
Gitweb: https://git.kernel.org/tip/59a87fdad1467d228acc5cb1303b0b568a9e86a8
Author: Adrian Hunter
AuthorDate: Tue, 16 Jan 2018 15:14:51 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 18 Jan 2018 09:00:45 -0300
perf evsel:
Commit-ID: a10eb530ae497e2411525fc1f5ec73f39eb11c11
Gitweb: https://git.kernel.org/tip/a10eb530ae497e2411525fc1f5ec73f39eb11c11
Author: Adrian Hunter
AuthorDate: Tue, 16 Jan 2018 15:14:50 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Thu, 18 Jan 2018 09:00:16 -0300
perf intel-p
Adapt driver to utilize dmtimer pdata ops instead of pdata-quirks.
Signed-off-by: Keerthy
Acked-by: Neil Armstrong
Reviewed-by: Claudiu Beznea
---
Changes in v9:
* Reorganized the place where of_node_put was called.
Changes in v8:
* Added of_node_put call in success case of probe.
Boot
Hi Peng,
Am Samstag, den 30.12.2017, 21:53 +0800 schrieb Peng Fan:
> There are two states in i.MX6Q cpuidle driver.
> state[1]: ARM WFI mode
> state[2]: i.MX6Q WAIT mode
>
> Take i.MX6DL as example, think out such a case:
> 1. CPU0/1 both run at normal mode
> 2. On CPU0, `sleep 1` is executed. An
Hi!
On Wed 2018-01-24 09:37:05, 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:
> > > > Add the PR_ISOL
* Arnaldo Carvalho de Melo wrote:
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> Test results at the end of this message, as usual.
>
> The following changes since commit a72594ca5c70ef4a94fab8ad541beda0d0a94139:
>
> Merge tag 'perf-core-for-mingo-4.16-20180117' of
> git
On Wed, 2018-01-24 at 09:03 +0100, Johannes Thumshirn wrote:
> 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 t
On Wed, Jan 24, 2018 at 1:56 AM, Vincent Chen wrote:
> 2018-01-18 18:30 GMT+08:00 Arnd Bergmann :
>> On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu wrote:
>>> From: Greentime Hu
>>>
>>> This patch adds support for signal handling.
>>>
>>> Signed-off-by: Vincent Chen
>>> Signed-off-by: Greentime
2018-01-03 21:00 GMT+01:00 Andrey Smirnov :
> Srinivas, all:
>
> This patchset contains various small changes that I recently made to
> NVMEM, more specifically:
>
> - Patches 1 and 3 are two changes I am hoping are acceptable upstream
>
> - Patches 4 to 15 are a follow up to patch 2
>
> - Patch
On Wed, Jan 24, 2018 at 12:34 PM, Jan Kara wrote:
> On Mon 22-01-18 22:31:20, Amir Goldstein wrote:
>> On Fri, Jan 19, 2018 at 5:02 PM, Shakeel Butt wrote:
>> > On Wed, Nov 15, 2017 at 1:31 AM, Jan Kara wrote:
>> >> On Wed 15-11-17 01:32:16, Yang Shi wrote:
>> >>> On 11/14/17 1:39 AM, Michal Hoc
On Wed, Jan 24, 2018 at 12:09 PM, Arnd Bergmann wrote:
> On Wed, Jan 24, 2018 at 11:53 AM, Vincent Chen wrote:
>> 2018-01-18 18:14 GMT+08:00 Arnd Bergmann :
> Ok. I still wonder about the kernel part of this though: is it a good idea
> for user space to configure whether the kernel does unaligne
On Wed, Jan 24, 2018 at 11:53 AM, Vincent Chen wrote:
> 2018-01-18 18:14 GMT+08:00 Arnd Bergmann :
>> On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu wrote:
>>> From: Greentime Hu
>>>
>>> This patch includes the exception/interrupt entries, pt_reg structure and
>>> related accessors.
>>>
>>> Signe
On Wed, 24 Jan 2018 11:53:11 +0100, Nicolas Dichtel wrote:
> Le 23/01/2018 à 18:08, Jiri Benc a écrit :
> > It would be much better if the whole (ifindex, netnsid) pair was
> > returned. I think it could be added.
> Sure. Do you plan to send a patch?
I can do that but it will take a while. I'll
This patch adds support to walk through the free page blocks in the
system and report them via a callback function. Some page blocks may
leave the free list after zone->lock is released, so it is the caller's
responsibility to either detect or prevent the use of such pages.
One use example of this
This patch series is separated from the previous "Virtio-balloon
Enhancement" series. The new feature, VIRTIO_BALLOON_F_FREE_PAGE_HINT,
implemented by this series enables the virtio-balloon driver to report
hints of guest free pages to the host. It can be used to accelerate live
migration of VMs.
Negotiation of the VIRTIO_BALLOON_F_FREE_PAGE_HINT feature indicates the
support of reporting hints of guest free pages to host via virtio-balloon.
Host requests the guest to report free pages by sending a new cmd
id to the guest via the free_page_report_cmd_id configuration register.
When the gu
On Wed 24-01-18 11:27:15, Michel Dänzer wrote:
> On 2018-01-24 10:28 AM, Michal Hocko wrote:
[...]
> > So how exactly then helps to kill one of those processes? The memory
> > stays pinned behind or do I still misunderstand?
>
> Fundamentally, the memory is only released once all references to the
Hi Paul,
On Tue, Jan 23, 2018 at 04:00:14PM -0800, Paul E. McKenney wrote:
> On Fri, Jan 19, 2018 at 09:12:11AM -0800, Paul E. McKenney wrote:
> > On Thu, Jan 18, 2018 at 07:58:55PM -0800, Paul E. McKenney wrote:
> > > Hello!
> > >
> > > There is some reason to believe that Documentation/memory-b
Khuong,
On 24/01/18 02:13, Khuong Dinh wrote:
> Aliasing attacks against CPU branch predictors can allow an attacker to
> redirect speculative control flow on some CPUs and potentially divulge
> information from one context to another.
>
> This patch only supports for XGene processors.
>
> Signe
On Fri, 2018-01-19 at 15:07 -0800, Khazhismel Kumykov wrote:
> Move the last used path to the end of the list (least preferred) so
> that
> ties are more evenly distributed.
>
> For example, in case with three paths with one that is slower than
> others, the remaining two would be unevenly used if
2018-01-18 18:14 GMT+08:00 Arnd Bergmann :
> On Mon, Jan 15, 2018 at 6:53 AM, Greentime Hu wrote:
>> From: Greentime Hu
>>
>> This patch includes the exception/interrupt entries, pt_reg structure and
>> related accessors.
>>
>> Signed-off-by: Vincent Chen
>> Signed-off-by: Greentime Hu
>
> Here
Le 23/01/2018 à 18:08, Jiri Benc a écrit :
> On Tue, 23 Jan 2018 17:37:11 +0100, Nicolas Dichtel wrote:
>> When a virtual interface moves to another netns, the netlink RTM_DELLINK
>> message
>> contains the attribute IFLA_NEW_NETNSID, which identifies where the interface
>> moves. The nsid may be
From: "leilei.lin"
Do not install cgroup event into the CPU context and schedule it
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 CPU context that causes
another cgroup event can't be installed into
On Wed, 24 Jan 2018, David Woodhouse wrote:
> I'm kind of tempted to turn it into a whitelist just by adding 1 to the
> microcode revision in each table entry. Sure, that N+1 might be another
> microcode build that also has issues but never saw the light of day...
Watch out for the (AFAIK) still n
Commit-ID: a97cb0e7b3f4c6297fd857055ae8e895f402f501
Gitweb: https://git.kernel.org/tip/a97cb0e7b3f4c6297fd857055ae8e895f402f501
Author: Peter Zijlstra
AuthorDate: Mon, 22 Jan 2018 11:39:47 +0100
Committer: Ingo Molnar
CommitDate: Wed, 24 Jan 2018 09:58:18 +0100
futex: Fix OWNER_DEAD fi
Commit-ID: ce48c146495a1a50e48cdbfbfaba3e708be7c07c
Gitweb: https://git.kernel.org/tip/ce48c146495a1a50e48cdbfbfaba3e708be7c07c
Author: Peter Zijlstra
AuthorDate: Mon, 22 Jan 2018 22:53:28 +0100
Committer: Ingo Molnar
CommitDate: Wed, 24 Jan 2018 10:03:44 +0100
sched/core: Fix cpu.max
On 24/01/2018 11:35, Peter Zijlstra wrote:
> On Tue, Jan 23, 2018 at 08:48:13PM +, David Woodhouse wrote:
>> On Tue, 2018-01-23 at 21:28 +0100, Borislav Petkov wrote:
>>>
flags = (flags & EFLAGS_MASK) | X86_EFLAGS_IF;
- asm("push %[flags]; popf; call *%[fastop]"
-
Commit-ID: 88f1c87de11a86d839f4ce5313e552d96709b990
Gitweb: https://git.kernel.org/tip/88f1c87de11a86d839f4ce5313e552d96709b990
Author: Tejun Heo
AuthorDate: Mon, 22 Jan 2018 14:00:55 -0800
Committer: Ingo Molnar
CommitDate: Wed, 24 Jan 2018 10:00:09 +0100
locking/lockdep: Avoid trigge
Hi Dmitry!
I'm observing a problem with internal touchpad (handled by psmouse.ko)
on Dell laptops connected to Dell E docking station. When I connect
external PS/2 keyboard to docking station then internal laptop touchpad
switch from multitouch absolute mode to relative bare PS/2 mode.
And becaus
On Tue, Jan 23, 2018 at 08:48:13PM +, David Woodhouse wrote:
> On Tue, 2018-01-23 at 21:28 +0100, Borislav Petkov wrote:
> >
> > > flags = (flags & EFLAGS_MASK) | X86_EFLAGS_IF;
> > > - asm("push %[flags]; popf; call *%[fastop]"
> > > - : "=a"(rc) : [fastop]"r"(fop), [flags]"
Removal of IOMMUs cannot be done reliably.
This is similar to exynos iommu driver.
Signed-off-by: Jeffy Chen
Reviewed-by: Tomasz Figa
---
Changes in v5: None
Changes in v4:
Rewrite commit message.
Changes in v3:
Also remove remove() and module_exit() as Tomasz suggested.
Changes in v2: None
From: Tomasz Figa
Current code relies on master driver enabling necessary clocks before
IOMMU is accessed, however there are cases when the IOMMU should be
accessed while the master is not running yet, for example allocating
V4L2 videobuf2 buffers, which is done by the VB2 framework using DMA
map
On Tue, Jan 23, 2018 at 08:19:08PM +0300, Kirill A. Shutemov wrote:
> sme_populate_pgd() and sme_populate_pgd_large() operate on the identity
> mapping, which means they want virtual addresses to be equal to physical
> one, without PAGE_OFFSET shift.
>
> We also need to avoid paravirtualizaion cal
Use the first registered IOMMU device for dma mapping operations, and
drop the domain platform device.
This is similar to exynos iommu driver.
Signed-off-by: Jeffy Chen
Reviewed-by: Tomasz Figa
Reviewed-by: Robin Murphy
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes i
When the power domain is powered off, the IOMMU cannot be accessed and
register programming must be deferred until the power domain becomes
enabled.
Add runtime PM support, and use runtime PM device link from IOMMU to
master to startup and shutdown IOMMU.
Signed-off-by: Jeffy Chen
---
Changes i
It's hard to undo bus_set_iommu() in the error path, so move it to the
end of rk_iommu_probe().
Signed-off-by: Jeffy Chen
Reviewed-by: Tomasz Figa
Reviewed-by: Robin Murphy
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2:
Move bus_set_iommu() to rk_iommu_probe().
Converts the rockchip-iommu driver to use the OF_IOMMU infrastructure,
which allows attaching master devices to their IOMMUs automatically
according to DT properties.
Signed-off-by: Jeffy Chen
Reviewed-by: Robin Murphy
---
Changes in v5: None
Changes in v4: None
Changes in v3:
Add struct rk_iom
There would be some masters sharing the same IOMMU device. Put them in
the same iommu group and share the same iommu domain.
Signed-off-by: Jeffy Chen
Reviewed-by: Robin Murphy
---
Changes in v5: None
Changes in v4: None
Changes in v3:
Remove rk_iommudata->domain.
Changes in v2: None
drivers
When hypercall-based TLB flush was enabled for Hyper-V guests PCID feature
was deliberately suppressed as a precaution: back then PCID was never
exposed to Hyper-V guests and it wasn't clear what will happen if some day
it becomes available. The day came and PCID/INVPCID features are already
expose
Add clocks in vop iommu nodes, since we are going to control clocks in
rockchip iommu driver.
Signed-off-by: Jeffy Chen
---
Changes in v5:
Remove clk names.
Changes in v4: None
Changes in v3: None
Changes in v2: None
arch/arm/boot/dts/rk3036.dtsi | 1 +
arch/arm/boot/dts/rk3288.dtsi | 2 ++
2
From: Tomasz Figa
Due to the bug in current code, only first IOMMU has the TLB lines
flushed in rk_iommu_zap_lines. This patch fixes the inner loop to
execute for all IOMMUs and properly flush the TLB.
Signed-off-by: Tomasz Figa
Signed-off-by: Jeffy Chen
---
Changes in v5: None
Changes in v4:
From: Tomasz Figa
This patch converts the rockchip-iommu driver to use the in-kernel
iopoll helpers to wait for certain status bits to change in registers
instead of an open-coded custom macro.
Signed-off-by: Tomasz Figa
Signed-off-by: Jeffy Chen
Reviewed-by: Robin Murphy
---
Changes in v5:
From: Tomasz Figa
Currently if the driver encounters an error while attaching device, it
will leave the IOMMU in an inconsistent state. Even though it shouldn't
really happen in reality, let's just add proper error path to keep
things consistent.
Signed-off-by: Tomasz Figa
Signed-off-by: Jeffy
Move request_irq to the end of rk_iommu_probe().
Suggested-by: Robin Murphy
Signed-off-by: Jeffy Chen
---
Changes in v5: None
Changes in v4: None
Changes in v3:
Loop platform_get_irq() as Robin suggested.
Changes in v2: None
drivers/iommu/rockchip-iommu.c | 38 +--
Add missing iommu_device_sysfs_remove in error path.
Signed-off-by: Jeffy Chen
Reviewed-by: Tomasz Figa
---
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
drivers/iommu/rockchip-iommu.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/d
This series fixes some issues in rockchip iommu driver, and add of_iommu
support in it.
Changes in v5:
Use out labels to save the duplication between the error and success paths.
Use RK_MMU_POLL_PERIOD_US instead of 100.
Remove clk names.
Use clk_bulk APIs.
Avoid race about pm_runtime_get_if_in_u
On Mon 22-01-18 22:31:20, Amir Goldstein wrote:
> On Fri, Jan 19, 2018 at 5:02 PM, Shakeel Butt wrote:
> > On Wed, Nov 15, 2017 at 1:31 AM, Jan Kara wrote:
> >> On Wed 15-11-17 01:32:16, Yang Shi wrote:
> >>> On 11/14/17 1:39 AM, Michal Hocko wrote:
> >>> >On Tue 14-11-17 03:10:22, Yang Shi wrote
On Tue, Jan 23, 2018 at 04:49:29PM +, Ayan Kumar Halder wrote:
> From: Ayan Halder
>
> Mali dp needs to disable pixel alpha blending (use layer alpha blending) to
> display color formats that do not contain alpha bits per pixel
>
> This patch depends on:
>
> "[PATCH v2 01/19] drm/fourcc: Ad
Hi
On Wed, Jan 24, 2018 at 4:25 AM, Peter Xu wrote:
> On Tue, Jan 23, 2018 at 05:40:39PM +0100, Marc-André Lureau wrote:
>> Modify fw_cfg_read_blob() to use DMA if the device supports it.
>> Return errors, because the operation may fail.
>>
>> The DMA operation is expected to run synchronously wi
On Wed, Jan 24, 2018 at 10:05 AM, 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
> description in p
On 2018-01-24 10:28 AM, Michal Hocko wrote:
> 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 G
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
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 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
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
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
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
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
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
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 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
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 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
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
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
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
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,
+
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
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
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, 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
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 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 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
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.
>>>
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 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
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
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
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
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
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
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 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
> > > + 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 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
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 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
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
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
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
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:
> > > >
701 - 800 of 855 matches
Mail list logo
