Not exactly. The plan for these patches is to introduce new vm_fault_t type
in vm_operations_struct fault handlers. It's now available in 4.17-rc1. We will
push all the required drivers/filesystem changes through different maintainers
to linus tree. Once everything is converted into vm_fault_t type
On 17 April 2018 at 03:56, Alexander Shishkin
wrote:
> On Mon, Apr 16, 2018 at 02:51:02PM -0600, Mathieu Poirier wrote:
>> Moving all kernel side CoreSight framework and drivers to SPDX identifier.
>>
>> Signed-off-by: Mathieu Poirier
>
> This reminds me: there's drivers/hwtracing/stm/ftrace.c th
Thanks for explaining,
On 17/04/18 15:54, Alban wrote:
This will not only allow reading the calibration data from nvmem, but
will also create a partition on the MTD device, which is not acceptable.
With my proposed binding this would become:
flash@0 {
#address-cells = <1>;
#size
On Sun, Apr 08, 2018 at 02:06:18PM -0700, Paul E. McKenney wrote:
> On Sat, Apr 07, 2018 at 07:40:42AM +1000, Nicholas Piggin wrote:
> > On Thu, 5 Apr 2018 08:53:20 -0700
> > "Paul E. McKenney" wrote:
[ . . . ]
> > > > Note that rcu doesn't show up consistently at the top, this was
> > > > just
On Tue, Apr 17, 2018 at 03:52:21PM +0100, Matt Redfearn wrote:
> The __clear_user function is defined to return the number of bytes that
> could not be cleared. From the underlying memset / bzero implementation
> this means setting register a2 to that number on return. Currently if a
> page fault i
On Tue, 2018-04-17 at 11:16 -0400, Theodore Y. Ts'o wrote:
> On Tue, Apr 17, 2018 at 12:57:12PM +0100, James Bottomley wrote:
> >
> > You don't have to compromise the bootloader to influence this, you
> > merely have to trick it into providing the random number you
> > wanted. The bigger you make
It is not immediately obvious what the expected inputs to these fault
handlers is and how they calculate the number of unset bytes. Having
stared deeply at this in order to fix some corner cases, add some
comments to addist those who follow.
Signed-off-by: Matt Redfearn
---
Changes in v2:
- Add
Assembly language within the MIPS kernel conventionally indents
instructions which are in a branch delay slot to make them easier to
see. Commit 8483b14aaa81 ("MIPS: lib: memset: Whitespace fixes") rather
inexplicably removed all of these indentations from memset.S. Reinstate
the convention for all
The micromips implementation of bzero additionally clobbers registers t7
& t8. Specify this in the clobbers list when invoking bzero.
Reported-by: James Hogan
Fixes: 26c5e07d1478 ("MIPS: microMIPS: Optimise 'memset' core library
function.")
Cc: sta...@vger.kernel.org
Signed-off-by: Matt Redfearn
On 2018-04-17 11:33 AM, Christian König wrote:
Am 17.04.2018 um 17:07 schrieb Andres Rodriguez:
On 2018-04-17 04:48 AM, Christian König wrote:
Well this is a rather big NAK for this patch.
Only a small fraction of the firmware files amdgpu uses are actually
optional (the ones with the *_2
The label .Llast_fixup\@ is jumped to on page fault within the final
byte set loop of memset (on < MIPSR6 architectures). For some reason, in
this fault handler, the v1 register is randomly set to a2 & STORMASK.
This clobbers v1 for the calling function. This can be observed with the
following test
On Fri, Apr 06, 2018 at 04:36:06PM +0100, Dietmar Eggemann wrote:
> From: Quentin Perret
>
> In case an energy model is available, waking tasks are re-routed into a
> new energy-aware placement algorithm. The eligible CPUs to be used in the
> energy-aware wakeup path are restricted to the highest
On Tue, Apr 17, 2018 at 08:57:32AM -0500, Rob Herring wrote:
> Whack-a-mole some more occurrences of status in examples.
>
> Cc: Vinod Koul
> Cc: Mark Rutland
> Cc: Ralf Baechle
> Cc: James Hogan
> Cc: Ulf Hansson
> Cc: David Woodhouse
> Cc: Brian Norris
> Cc: Boris Brezillon
> Cc: Marek V
On 04/17/2018 08:28 AM, Aaro Koskinen wrote:
>
>> [0.00] Kernel/User page tables isolation: enabled
>> [0.00] [ cut here ]
>> [0.00] CPA: called for zero pte. vaddr = 8d00 cpa->vaddr
>> = 8d00
>> [0.00] WARNING: CPU:
On Tue, Apr 17, 2018 at 04:46:43PM +0300, Peter Ujfalusi wrote:
> @@ -709,6 +709,11 @@ struct dma_filter {
> * be called after period_len bytes have been transferred.
> * @device_prep_interleaved_dma: Transfer expression in a generic way.
> * @device_prep_dma_imm_data: DMA's 8 byte immedia
On Mon 2018-04-16 14:04:25, Josh Poimboeuf wrote:
> On Mon, Apr 16, 2018 at 04:58:11PM +0200, Petr Mladek wrote:
> > On Wed 2018-04-11 10:48:52, Josh Poimboeuf wrote:
> > > On Wed, Apr 11, 2018 at 04:17:11PM +0200, Petr Mladek wrote:
> > > > Second, unrelated patches must never patch the same funct
This should let us associate enum kdoc to these values.
Signed-off-by: Andres Rodriguez
---
drivers/base/firmware_loader/fallback.c | 12 ++--
drivers/base/firmware_loader/fallback.h | 6 --
drivers/base/firmware_loader/firmware.h | 17 +
drivers/base/firmware_loader
Some basic definitions for the FW_OPT_* values
Signed-off-by: Andres Rodriguez
---
drivers/base/firmware_loader/firmware.h | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/base/firmware_loader/firmware.h
b/drivers/base/firmware_loader/firmware.h
index 957396293b92..8ef23
This re-spin includes fixes for the kernel-doc style as pointed
out by Randy Dunlap. Otherwise it should be functionally identical
to the previous iteration.
New changes can be found in patches 4 & 5.
Andres Rodriguez (9):
firmware: some documentation fixes
firmware: wrap FW_OPT_* into an en
The kernel-doc spec dictates a function name ends in ().
Signed-off-by: Andres Rodriguez
---
drivers/base/firmware_loader/fallback.c | 8
drivers/base/firmware_loader/main.c | 22 +++---
2 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/drivers/base/f
Currently the firmware loader only exposes one silent path for querying
optional firmware, and that is firmware_request_direct(). This function
also disables the fallback path, which might not always be the
desired behaviour. [0]
This patch introduces variations of firmware_request() and
firmware_
Am 17.04.2018 um 17:07 schrieb Andres Rodriguez:
On 2018-04-17 04:48 AM, Christian König wrote:
Well this is a rather big NAK for this patch.
Only a small fraction of the firmware files amdgpu uses are actually
optional (the ones with the *_2.bin name). All other files are
mandatory for cor
Currently, during the normal boot process the amdgpu driver will produce
spew like the following in dmesg:
Direct firmware load for amdgpu/polaris10_mec_2.bin failed with error -2
This happens when amdgpu tries to load optional firmware files. So the
error does not affect the startup sequence.
Th
Including:
- Fixup outdated kernel-doc paths
- Slightly too short title underline
- Some typos
Signed-off-by: Andres Rodriguez
---
Documentation/driver-api/firmware/request_firmware.rst | 16
drivers/base/firmware_loader/fallback.c| 4 ++--
drivers/base/firmw
This reduces the unnecessary spew when trying to load optional firmware:
"Direct firmware load for ... failed with error -2"
Signed-off-by: Andres Rodriguez
---
drivers/net/wireless/ath/ath10k/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/wireless/ath/ath
Previously, one could assume the firmware name from the preceding
message: "Direct firmware load for {name} failed with error %d".
However, with the new firmware_request_nowarn() entrypoint, the message
outlined above will not always be printed.
Therefore, we add the firmware name to the fallback
This reduces the unnecessary spew when trying to load optional firmware:
"Direct firmware load for ... failed with error -2"
Signed-off-by: Andres Rodriguez
---
drivers/net/wireless/broadcom/brcm80211/brcmfmac/firmware.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/
Hi Sakari,
Thank you for the review.
On 29.03.2018 14:51, Sakari Ailus wrote:
> Hi Todor,
>
> Thanks for the patch. A few quick comments below...
>
> On Fri, Mar 23, 2018 at 12:14:20PM +0800, Todor Tomov wrote:
>> The ov7251 sensor is a 1/7.5-Inch B&W VGA (640x480) CMOS Digital Image
>> Sensor
On Fri, Jan 26, 2018 at 03:04:54PM +0900, Andi Shyti wrote:
> The mms114 binding [1] specifies that the 'x' and 'y' should be
> called respectively 'touchscreen-size-x' and 'touchscreen-size-y'
> in coherence with the touchscreen [2] binding.
>
> Update the mms114 node for trats2 and trats dts acc
On Tue, Apr 17, 2018 at 05:21:30PM +0200, Jörg Otte wrote:
> finished bisection.
> 39114b7a743e6759bab4d96b7d9651d44d17e3f9 is the first bad commit
> (x86/pti: Never implicitly clear _PAGE_GLOBAL for kernel image).
Looks like you're not the only one:
http://marc.info/?i=20180417150130.ga11...@ak-
Hi,
On Tue, Apr 17, 2018 at 06:01:30PM +0300, Aaro Koskinen wrote:
> I'm getting early crash on x86_64 box with 4.17-rc1 and PTI
> enabled. Bisected to:
>
> commit 39114b7a743e6759bab4d96b7d9651d44d17e3f9
> Author: Dave Hansen
> Date: Fri Apr 6 13:55:17 2018 -0700
>
> x86/pti: Never impli
On Tue, 17 Apr 2018, Souptick Joarder wrote:
> Use new return type vm_fault_t for fault handler. For
> now, this is just documenting that the function returns
> a VM_FAULT value rather than an errno. Once all instances
> are converted, vm_fault_t will become a distinct type.
>
> Reference id -> 1c
Commit-ID: e142aa09ed88be98395dde7acb96fb2263566b68
Gitweb: https://git.kernel.org/tip/e142aa09ed88be98395dde7acb96fb2263566b68
Author: Baolin Wang
AuthorDate: Fri, 13 Apr 2018 13:27:58 +0800
Committer: Thomas Gleixner
CommitDate: Tue, 17 Apr 2018 17:18:05 +0200
timekeeping: Remove __c
On 03/23/2018 09:32 AM, argus@mediatek.com wrote:
> From: Argus Lin
>
> mt6797 is a highly integrated SoCs, it uses mt6351 for power
> management. We need to add pwrap support to access mt6351.
> Pwrap of mt6797 also add new feature include starvation and
> request exception interrupt, dyna
Commit-ID: f0ae6a0321222864ed8675a924cc8ee2cb042c31
Gitweb: https://git.kernel.org/tip/f0ae6a0321222864ed8675a924cc8ee2cb042c31
Author: Liu, Changcheng
AuthorDate: Thu, 12 Apr 2018 15:57:01 +0800
Committer: Thomas Gleixner
CommitDate: Tue, 17 Apr 2018 17:18:04 +0200
timers: Remove stal
Commit-ID: 4450dc0ae2c18a0ac6dce560215c7a1fa12122b5
Gitweb: https://git.kernel.org/tip/4450dc0ae2c18a0ac6dce560215c7a1fa12122b5
Author: Geert Uytterhoeven
AuthorDate: Thu, 5 Apr 2018 17:26:58 +0200
Committer: Thomas Gleixner
CommitDate: Tue, 17 Apr 2018 17:18:04 +0200
clockevents: Fix
On Fri, Apr 06, 2018 at 04:36:05PM +0100, Dietmar Eggemann wrote:
> From: Quentin Perret
>
> In preparation for the definition of an energy-aware wakeup path, a
> helper function is provided to estimate the consequence on system energy
> when a specific task wakes-up on a specific CPU. compute_en
On Tue, 17 Apr 2018 10:26:57 -0400
Tony Krowiak wrote:
> On 04/17/2018 06:10 AM, Cornelia Huck wrote:
> > On Tue, 17 Apr 2018 09:49:58 +0200
> > "Harald Freudenberger" wrote:
> >
> >> Didn't we say that when APXA is not available there is no Crypto support
> >> for KVM ?
> > [Going by the co
2018-04-17 16:27 GMT+02:00 Borislav Petkov :
> On Tue, Apr 17, 2018 at 04:16:34PM +0200, Jörg Otte wrote:
>> Current Linus master tree (4.17.0-rc1-00021-ga27fc14) does'nt fix it.
>
> Then pls continue bisecting. Unless someone has a better idea...
>
finished bisection.
39114b7a743e6759bab4d96b7d96
On Tue, 2018-04-17 at 07:07 -0700, Matthew Wilcox wrote:
> On Tue, Apr 17, 2018 at 12:57:12PM +0100, James Bottomley wrote:
> > On Tue, 2018-04-17 at 04:47 -0700, Matthew Wilcox wrote:
> > > On Tue, Apr 17, 2018 at 10:13:34AM +0100, James Bottomley wrote:
> > > > On Sat, 2018-04-14 at 17:41 -0700,
On Thu, Mar 08, 2018 at 02:19:26PM +0800, Jianchao Wang wrote:
> Firstly, really appreciate Keith and Sagi's precious advice on previous
> versions.
> And this is the version 4.
>
> Some patches of the previous patchset have been submitted and the left is
> this patchset
> which has been refacto
On Tue, Apr 17, 2018 at 12:57:12PM +0100, James Bottomley wrote:
>
> You don't have to compromise the bootloader to influence this, you
> merely have to trick it into providing the random number you wanted.
> The bigger you make the attack surface (the more inputs) the more
> likelihood of findin
On 04/16/2018 07:52 AM, Halil Pasic wrote:
On 04/16/2018 01:13 PM, Pierre Morel wrote:
On 16/04/2018 12:51, Pierre Morel wrote:
On 15/04/2018 23:22, Tony Krowiak wrote:
The VFIO AP device model exploits interpretive execution of AP
instructions (APIE) to provide guests passthrough access to A
On 04/16/2018 07:12 AM, Halil Pasic wrote:
On 04/15/2018 11:22 PM, Tony Krowiak wrote:
The VFIO AP device model exploits interpretive execution of AP
instructions (APIE) to provide guests passthrough access to AP
devices. This patch introduces a new interface to enable and
disable APIE.
Signed
On 17.04.2018 17:07, Kamil Konieczny wrote:
>
>
> On 17.04.2018 15:39, Maciej S. Szmigiero wrote:
>> The signatureValue field of a X.509 certificate is encoded as a BIT STRING.
>> For RSA signatures this BIT STRING is of so-called primitive subtype, which
>> contains a u8 prefix indicating a coun
On 04/17/2018 03:33 AM, Juergen Gross wrote:
> On 15/03/18 04:08, Simon Gaiser wrote:
>> xenbus_command_reply() did not actually copy the response string and
>> leaked stack content instead.
>>
>> Fixes: 9a6161fe73bd ("xen: return xenstore command failures via response
>> instead of rc")
>> Signed
On Tue, 17 Apr 2018 10:55:30 -0400
Tony Krowiak wrote:
> On 04/17/2018 10:29 AM, Halil Pasic wrote:
> >
> >
> > On 04/15/2018 11:22 PM, Tony Krowiak wrote:
> >> Introduces a new function to reset the crypto attributes for all
> >> vcpus whether they are running or not. Each vcpu in KVM will
> >
On 04/16/2018 07:13 AM, Pierre Morel wrote:
On 16/04/2018 12:51, Pierre Morel wrote:
On 15/04/2018 23:22, Tony Krowiak wrote:
The VFIO AP device model exploits interpretive execution of AP
instructions (APIE) to provide guests passthrough access to AP
devices. This patch introduces a new interf
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Reference id -> 1c8f422059ae ("mm: change return type to
vm_fault_t")
Sign
On 04/12/2018 01:26 PM, Oleksandr Andrushchenko wrote:
> This is the sync up with the canonical definition of the sound
> protocol in Xen:
>
> 1. Protocol version was referenced in the protocol description,
>but missed its definition. Fixed by adding a constant
>for current protocol version
2018-04-15 17:08 GMT+09:00 Ulf Magnusson :
> On Fri, Apr 13, 2018 at 7:06 AM, Masahiro Yamada
> wrote:
>> Add a document for the macro language introduced to Kconfig.
>>
>> The motivation of this work is to move the compiler option tests to
>> Kconfig from Makefile. A number of kernel features re
On 17.04.2018 15:39, Maciej S. Szmigiero wrote:
> The signatureValue field of a X.509 certificate is encoded as a BIT STRING.
> For RSA signatures this BIT STRING is of so-called primitive subtype, which
> contains a u8 prefix indicating a count of unused bits in the encoding.
>
> We have to str
On 04/09/2018 11:03 AM, Jia-Ju Bai wrote:
> pcistub_probe() is never called in atomic context.
> This function is only set as ".probe" in struct pci_driver.
>
> Despite never getting called from atomic context,
> pcistub_probe() calls kmalloc() with GFP_ATOMIC,
> which does not sleep for allocation
On 2018-04-17 04:48 AM, Christian König wrote:
Well this is a rather big NAK for this patch.
Only a small fraction of the firmware files amdgpu uses are actually
optional (the ones with the *_2.bin name). All other files are mandatory
for correct driver operation.
There is a fallback when
2018-04-15 8:33 GMT+09:00 Randy Dunlap :
> On 04/12/18 22:06, Masahiro Yamada wrote:
>> Add a document for the macro language introduced to Kconfig.
>>
>> Signed-off-by: Masahiro Yamada
>> ---
>>
>> Changes in v3: None
>> Changes in v2: None
>>
>> Documentation/kbuild/kconfig-macro-language.txt |
On Sun, 2018-04-15 at 18:16 +0200, Pavel Machek wrote:
> On Mon 2018-03-26 10:33:55, Dan Williams wrote:
> > On Sun, 2018-03-25 at 08:19 +0200, Pavel Machek wrote:
> > > > > > Ok, what does 'nmcli dev' and 'nmcli radio' show?
> > > > >
> > > > > Broken state.
> > > > >
> > > > > pavel@amd:~$ nmcl
On 04/16/2018 12:34 PM, Linus Torvalds wrote:
> On Mon, Apr 16, 2018 at 11:15 AM, Linus Torvalds
> wrote:
>>
>> Ingo/Thomas: I will be just taking this directly, since it's so
>> trivial and obvious and I got cc'd on the discussion.
>
> .. and I also verified that it actually fixes the problem Sh
Hi,
I'm getting early crash on x86_64 box with 4.17-rc1 and PTI
enabled. Bisected to:
commit 39114b7a743e6759bab4d96b7d9651d44d17e3f9
Author: Dave Hansen
Date: Fri Apr 6 13:55:17 2018 -0700
x86/pti: Never implicitly clear _PAGE_GLOBAL for kernel image
I can see the crash only with earlyp
On 04/16/2018 06:51 AM, Pierre Morel wrote:
On 15/04/2018 23:22, Tony Krowiak wrote:
The VFIO AP device model exploits interpretive execution of AP
instructions (APIE) to provide guests passthrough access to AP
devices. This patch introduces a new interface to enable and
disable APIE.
Signed-of
On 04/17/2018 12:29 PM, Ravi Bangoria wrote:
>
> This change looks good to me but seems it fixed the issue
> partially.Ex,
>
> # readelf --debug-dump=frames-interp /lib64/libc-2.26.so | less
> ...
> 5778 0024 577c FDE cie=
> pc=00048b30..0
On 04/17/2018 04:36 PM, Andy Lutomirski wrote:
32-bit user code that uses int $80 doesn't care about r8-r11. There is,
however, some 64-bit user code that intentionally uses int $0x80 to
invoke 32-bit system calls. From what I've seen, basically all such
code assumes that r8-r15 are all preserv
On Tue, Apr 17, 2018 at 05:04:59PM +0300, Michael S. Tsirkin wrote:
> On Tue, Apr 17, 2018 at 08:47:16PM +0800, Tiwei Bie wrote:
> > On Tue, Apr 17, 2018 at 03:17:41PM +0300, Michael S. Tsirkin wrote:
> > > On Tue, Apr 17, 2018 at 10:51:33AM +0800, Tiwei Bie wrote:
> > > > On Tue, Apr 17, 2018 at 1
On Tue, Apr 17, 2018 at 04:36:31PM +0200, Michal Hocko wrote:
>On Tue 17-04-18 14:04:36, Sasha Levin wrote:
>> On Tue, Apr 17, 2018 at 01:07:17PM +0200, Michal Hocko wrote:
>> >On Tue 17-04-18 12:39:36, Greg KH wrote:
>> >> On Mon, Apr 16, 2018 at 11:28:44PM +0200, Jiri Kosina wrote:
>> >> > On Mon
On 04/17/2018 10:29 AM, Halil Pasic wrote:
On 04/15/2018 11:22 PM, Tony Krowiak wrote:
Introduces a new function to reset the crypto attributes for all
vcpus whether they are running or not. Each vcpu in KVM will
be removed from SIE prior to resetting the crypto attributes in its
SIE state des
On Tue, 17 Apr 2018 13:54:07 +0100
Srinivas Kandagatla wrote:
> On 24/03/18 23:24, Alban Bedel wrote:
> > Having the cells as subnodes of the provider device without any
> > compatible property might clash with other bindings. To avoid this
> > problem update the binding to have all the cells in
On 2018-04-17 16:58, Lars-Peter Clausen wrote:
>>> There are two options.
>>>
>>> Either you extend the generic interfaces so it can cover your usecase in a
>>> generic way. E.g. the ability to attach meta data to transfer.
>>
>> Fwiw I have this patch as part of a bigger work to achieve similar re
The __clear_user function is defined to return the number of bytes that
could not be cleared. From the underlying memset / bzero implementation
this means setting register a2 to that number on return. Currently if a
page fault is triggered within the memset_partial block, the value
loaded into a2 o
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Reference id -> 1c8f422059ae ("mm: change return type to
vm_fault_t")
prev
[+cc Bartlomiej, who recently changed do_pcie_gen3_transition(), LKML]
On Mon, Apr 16, 2018 at 11:53:43PM -0700, Christoph Hellwig wrote:
> On Mon, Apr 16, 2018 at 07:28:23PM -0500, Frederick Lawler wrote:
> > The IB/hfi1 driver uses custom macros to configure the target link speed.
> > Some
> >
This is a port on kernel 4.16 of the work done by Peter Zijlstra to
handle page fault without holding the mm semaphore [1].
The idea is to try to handle user space page faults without holding the
mmap_sem. This should allow better concurrency for massively threaded
process since the page fault han
Set ARCH_SUPPORTS_SPECULATIVE_PAGE_FAULT for BOOK3S_64. This enables
the Speculative Page Fault handler.
Support is only provide for BOOK3S_64 currently because:
- require CONFIG_PPC_STD_MMU because checks done in
set_access_flags_filter()
- require BOOK3S because we can't support for book3e_hug
This configuration variable will be used to build the code needed to
handle speculative page fault.
By default it is turned off, and activated depending on architecture
support, SMP and MMU.
Suggested-by: Thomas Gleixner
Suggested-by: David Rientjes
Signed-off-by: Laurent Dufour
---
mm/Kconfi
When handling page fault without holding the mmap_sem the fetch of the
pte lock pointer and the locking will have to be done while ensuring
that the VMA is not touched in our back.
So move the fetch and locking operations in a dedicated function.
Signed-off-by: Laurent Dufour
---
mm/memory.c |
From: Peter Zijlstra
When speculating faults (without holding mmap_sem) we need to validate
that the vma against which we loaded pages is still valid when we're
ready to install the new PTE.
Therefore, replace the pte_offset_map_lock() calls that (re)take the
PTL with pte_map_lock() which can fa
On Tue, Apr 17, 2018 at 11:13:14AM +0200, Thomas Gleixner wrote:
> On Mon, 16 Apr 2018, Christoph Hellwig wrote:
>
> > The commit that switches x86 to dma_direct_ops stopped using and building
> > this file, but accidentally left it in the tree. Remove it.
>
> There is also stale documentation i
The speculative page fault handler must be protected against anon_vma
changes. This is because page_add_new_anon_rmap() is called during the
speculative path.
In addition, don't try speculative page fault if the VMA don't have an
anon_vma structure allocated because its allocation should be
protec
On Mon, 16 Apr 2018, Mikulas Patocka wrote:
> This patch introduces a flag SLAB_MINIMIZE_WASTE for slab and slub. This
> flag causes allocation of larger slab caches in order to minimize wasted
> space.
>
> This is needed because we want to use dm-bufio for deduplication index and
> there are exis
The VMA sequence count has been introduced to allow fast detection of
VMA modification when running a page fault handler without holding
the mmap_sem.
This patch provides protection against the VMA modification done in :
- madvise()
- mpol_rebind_policy()
- vma_replace_poli
If a thread is remapping an area while another one is faulting on the
destination area, the SPF handler may fetch the vma from the RB tree before
the pte has been moved by the other thread. This means that the moved ptes
will overwrite those create by the page fault handler leading to page
leaked.
The speculative page fault handler which is run without holding the
mmap_sem is calling lru_cache_add_active_or_unevictable() but the vm_flags
is not guaranteed to remain constant.
Introducing __lru_cache_add_active_or_unevictable() which has the vma flags
value parameter instead of the vma pointer
The patch set was made against the Lorenzo's master branch.
Adds support Designware EP support.
Increases the maximum number of interrupts allowed for Designware IP
controller.
Does a code cleanup on Designware driver:
- Replaces magic numbers without a easy meaning by a well known define
th
When handling speculative page fault, the vma->vm_flags and
vma->vm_page_prot fields are read once the page table lock is released. So
there is no more guarantee that these fields would not change in our back.
They will be saved in the vm_fault structure before the VMA is checked for
changes.
This
Adds a seconds entry on the pci_epf_test_ids structure that disables the
linkup_notifier parameter on driver for the designware EP.
This allows designware EPs that doesn't have linkup notification signal
to work with pcitest.
Updates the binding documentation accordingly.
Signed-off-by: Gustavo
Replaces "ctrlreg" reg-name by "dbi" to be coherent with similar drivers,
however it still be compatible with any previous DT that uses the old
reg-name.
Replaces the PCIe base address example by a real PCIe base address in use.
Signed-off-by: Gustavo Pimentel
---
Changes v1->v2:
- Removed any
Hi Martin
On 04/17/2018 08:10 PM, Martin Steigerwald wrote:
> For testing it I add it to 4.16.2 with the patches I have already?
You could try to only apply this patch to have a test. :)
>
> - '[PATCH] blk-mq_Directly schedule q->timeout_work when aborting a
> request.mbox'
>
> - '[PATCH v2]
Replaces lower into upper case characters in comments and debug printks.
This is an attempt to keep the messages coherent within the designware
driver.
Also fixed code style on dw_pcie_irq_domain_free function.
Signed-off-by: Gustavo Pimentel
Acked-by: Jingoo Han
---
Change v1->v2:
- Added an
The PCIe controller dual mode is capable of operating in host mode as well
as endpoint mode by configuration, therefore this patch aims to add
endpoint mode support to the designware driver.
Signed-off-by: Gustavo Pimentel
Acked-by: Kishon Vijay Abraham I
---
Change v1->v2:
- Removed dw_plat_pc
Replaces a simple division by 2 to a right shift rotation of 1 bit.
Probably any recent and decent compiler does this kind of substitution
in order to improve code performance. Nevertheless it's a coding good
practice whenever there is a division / multiplication by multiple of 2
to replace it by
Add device tree binding documentation for the Endpoint in PCIe Designware
driver.
Signed-off-by: Gustavo Pimentel
Reviewed-by: Rob Herring
---
Change v1->v2:
- Add a missing log description.
- Add "snps,dw-pcie" compatible string following Kishon's suggestion.
Change v2->v3:
- Reverted pcie_e
On Thu, Mar 15, 2018 at 10:51:06AM -0700, Linus Torvalds wrote:
> This version looks ok to me. I'm sure there's room for tweaking here,
> but I'm not seeing anything alarming.
So I'm redoing the series ontop of 17-rc1 and I see a *lot* of output
during testing. For example:
1) is from the userspa
When dealing with speculative page fault handler, we may race with VMA
being split or merged. In this case the vma->vm_start and vm->vm_end
fields may not match the address the page fault is occurring.
This can only happens when the VMA is split but in that case, the
anon_vma pointer of the new VM
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Reference id -> 1c8f422059ae ("mm: change return type to
vm_fault_t")
Sign
Adds the designware EP device ID entry to pci_endpoint_test driver table
to allow this device to be recognize and handle by the pci_endpoint_test
driver.
Signed-off-by: Gustavo Pimentel
Acked-by: Kishon Vijay Abraham I
---
Change v1->v2:
- Changed device id following Kishon's suggestion.
Change
On 2018/4/17 下午9:47, Thomas Gleixner wrote:
On Tue, 10 Apr 2018, zou...@linux.alibaba.com wrote:
From: zoucao
Interesting from ... Please use your real mail address for this.
miss this, i will do it.
Normally every BIOS reserved memory is used for some features, we can't
use them, but in so
On Mon, 16 Apr 2018, Mikulas Patocka wrote:
> dm-bufio deals gracefully with allocation failure, because it preallocates
> some buffers with vmalloc, but other subsystems may not deal with it and
> they cound return ENOMEM randomly or misbehave in other ways. So, the
> "SLAB_MINIMIZE_WASTE" flag i
The PCIe controller dual mode is capable of operating in host mode as well
as endpoint mode by configuration.
Signed-off-by: Gustavo Pimentel
---
Change v1->v2:
- Register new device id following Kishon's suggestion.
Change v2->v3:
- Nothing changed, just to follow the patch set version.
Change
When dealing with the speculative fault path we should use the VMA's field
cached value stored in the vm_fault structure.
Currently vm_normal_page() is using the pointer to the VMA to fetch the
vm_flags value. This patch provides a new __vm_normal_page() which is
receiving the vm_flags flags value
Replace magic numbers by a well known define in order to make the code
human readable and also facilitate the code reusability.
Signed-off-by: Gustavo Pimentel
Acked-by: Jingoo Han
---
Change v1->v2:
- Nothing changed, just to follow the patch set version.
Change v2->v3:
- Nothing changed, jus
From: Peter Zijlstra
Provide infrastructure to do a speculative fault (not holding
mmap_sem).
The not holding of mmap_sem means we can race against VMA
change/removal and page-table destruction. We use the SRCU VMA freeing
to keep the VMA around. We use the VMA seqcount to detect change
(includi
This change is inspired by the Peter's proposal patch [1] which was
protecting the VMA using SRCU. Unfortunately, SRCU is not scaling well in
that particular case, and it is introducing major performance degradation
due to excessive scheduling operations.
To allow access to the mm_rb tree without
701 - 800 of 1264 matches
Mail list logo
