On Fri, Feb 16, 2018 at 12:47 PM, Hans de Goede wrote:
> Various Intel SoCs (Cherry Trail, Broxton and others) have an internal USB
> role switch for swiching the OTG USB data lines between the xHCI host
> controller and the dwc3 gadget controller.
>
> Note on some Cherry Trail systems there is AC
It helps to give some examples about how to use in-line
comments also when nested union/structs are present. So add it.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/doc-guide/kernel-doc.rst | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/Documentation
We want to give some examples about how to do in-line comments
for nested structs. So, move it to be after nested structs/unions
chapter.
The section content was not changed on this patch.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/doc-guide/kernel-doc.rst | 56 +
This series fix two bugs at kernel-doc.rst examples and add support
for in-line nested struct comments.
It also converts one documentation at intel_dpio_phy to use it,
in order to give a practical example about how to use it.
Mauro Carvalho Chehab (6):
doc-guide: kernel-doc: fix example for nes
There's a missing */ at the end of Kernel docs example.
Even adding it, it will still produce 3 warnings:
example:33: warning: Function parameter or member 'bar' not described
in 'nested_foobar'
example:33: warning: Function parameter or member 'bar.st1' not
described in 'nested_
Without ending with a ";", kernel-doc doesn't recognize it
as an struct, and it fails to parse the example.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/doc-guide/kernel-doc.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/doc-guide/kernel-doc.rst
The in-lined comments for channel.port doesn't follow the syntax
described at kernel-doc document, causing the following warning:
$ ./scripts/kernel-doc -none drivers/gpu/drm/i915/intel_dpio_phy.c
drivers/gpu/drm/i915/intel_dpio_phy.c:154: warning: Function parameter
or member 'ch
The parser at kernel-doc rejects names with dots in the middle.
Fix it, in order to support nested structs/unions.
Tested-by: Jani Nikula
Signed-off-by: Mauro Carvalho Chehab
---
scripts/kernel-doc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/kernel-doc b/scripts/
Hi Mark,
On Fri, Feb 16, 2018 at 11:39:01AM +, Mark Brown wrote:
> On Wed, Feb 14, 2018 at 11:07:39PM +0100, Sebastian Reichel wrote:
>
> > +config SND_SOC_CPCAP
> > + tristate "Motorola CPCAP codec"
> > + depends on MFD_CPCAP
> > + default MFD_CPCAP
> > +
>
> We don't have default lin
On 14/02/18 15:47, Andy Shevchenko wrote:
> ...instead of open coding file operations followed by custom ->open()
> callbacks per each attribute.
>
> Signed-off-by: Andy Shevchenko
> ---
> kernel/irq/irqdomain.c | 18 --
> 1 file changed, 4 insertions(+), 14 deletions(-)
Applied
On Fri, Feb 16, 2018 at 12:47 PM, Hans de Goede wrote:
> The xHCI controller on various Intel SoCs has an extended cap mmio-range
> which contains registers to control the muxing to the xHCI (host mode)
> or the dwc3 (device mode) and vbus-detection for the otg usb-phy.
>
> Having a role-sw driver
On 16.02.2018 13:59, Chen-Yu Tsai wrote:
On Fri, Feb 16, 2018 at 8:49 PM, Philipp Rossak wrote:
On 16.02.2018 05:10, Chen-Yu Tsai wrote:
On Fri, Feb 16, 2018 at 1:53 AM, Philipp Rossak wrote:
On 15.02.2018 15:11, Maxime Ripard wrote:
On Wed, Feb 14, 2018 at 02:56:12PM +0100, Phili
Hi Rodrigo,
Mostly looking good. Few comments.
Please read:
https://chris.beams.io/posts/git-commit/
1) Capitalize the first letter of commit
2) Use prefix tags to indicate the driver that is changed. Here
iio:pressure:ms5611.
If not sure what prefix tags to use please use git log file.c and
[CC Pavel]
On Fri 16-02-18 14:37:26, Juergen Gross wrote:
> Commit f7f99100d8d95dbcf09e0216a143211e79418b9f ("mm: stop zeroing
> memory during allocation in vmemmap") broke Xen pv domains in some
> configurations, as the "Pinned" information in struct page of early
> page tables could get lost.
C
On Friday 16 February 2018 06:35 PM, Heiko Stübner wrote:
> Hi Kishon,
>
> Am Freitag, 16. Februar 2018, 12:04:42 CET schrieb Kishon Vijay Abraham I:
>> On Friday 10 February 2017 01:14 PM, Chris Zhong wrote:
>>> There are 2 Type-c PHYs in RK3399, but only one DP controller. Hence
>>> only one P
On Fri, Feb 16, 2018 at 12:47 PM, Hans de Goede wrote:
> USB Type-C connectors consist of various muxes and switches
> that route the pins on the connector to the right locations.
> The USB Type-C drivers need to be able to control the muxes,
> as they are the ones that know things like the cable
On 16/02/18 14:59, Michal Hocko wrote:
> [CC Pavel]
>
> On Fri 16-02-18 14:37:26, Juergen Gross wrote:
>> Commit f7f99100d8d95dbcf09e0216a143211e79418b9f ("mm: stop zeroing
>> memory during allocation in vmemmap") broke Xen pv domains in some
>> configurations, as the "Pinned" information in struc
On 30/01/18 20:14, Manish Narani wrote:
> This patch adds support of SD auto tuning for ZynqMP platform. Auto
> tuning sequence sends tuning block to card when operating in UHS-1
> modes. This resets the DLL and sends CMD19/CMD21 as a part of the auto
> tuning process. Once the auto tuning process
On Fri, Feb 16, 2018 at 12:47 PM, Hans de Goede wrote:
> USB role switch is a device that can be used to choose the
> data role for USB connector. With dual-role capable USB
> controllers, the controller itself will be the switch, but
> on some platforms the USB host and device controllers are
>
On Fri, Feb 16, 2018 at 02:49:46PM +0300, Kirill A. Shutemov wrote:
> @@ -38,12 +38,12 @@
> *
> */
>
> +#define l4_index(x) (((x) >> 39) & 511)
> #define pud_index(x) (((x) >> PUD_SHIFT) & (PTRS_PER_PUD-1))
Shouldn't that be
+#define p4d_index(x) (((x) >> P4D_SHIFT) & (PTRS_PER_P4D-1))
On 02/15/2018 07:16 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.18.95 release.
There are 45 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
Thanks for the patch!
On 02/15/2018 03:26 PM, srinivas.kandaga...@linaro.org wrote:
> From: Srinivas Kandagatla
>
> This patch converts existing regulators to use regulator bulk apis,
> to make it consistent with msm8996 changes also cut down some redundant code.
>
> Signed-off-by: Srinivas Kan
Hi,
On Fri, Feb 16, 2018 at 01:44:48PM +, Mark Brown wrote:
> On Fri, Feb 16, 2018 at 02:25:38PM +0100, Sebastian Reichel wrote:
> > On Fri, Feb 16, 2018 at 11:30:08AM +, Mark Brown wrote:
>
> > > Why are we adding a separate DT node with no content for this? This is
> > > a single chip,
On 02/15/2018 07:15 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.4.116 release.
There are 108 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On Thu, Feb 15, 2018 at 6:54 PM, Matthew Whitehead
wrote:
> Several i586-class cpus supporting this instruction are missing from
> the X86_CMPXCHG64 config group.
What about Intel Quark? MinuteIA core which is currently set as M586TSC.
> Using a configuration with either M586TSC or M586MMX curre
On Fri, Feb 16, 2018 at 11:35:20AM +0100, Peter Zijlstra wrote:
> #define BIT_U32_MASK(nr) (1UL << ((nr) % 32))
> #define BIT_U32_WORD(nr) (((nr) / 32) ^ (4 * __BIG_ENDIAN__))
s/4 *//
it's already a 4 byte offset.
On Thu, 15 Feb 2018, Randy Dunlap wrote:
> Hi,
>
> Is this a dead kconfig symbol? I don't see any Kconfig file that
> sets/enables it.
>
> ./kernel/irq/Makefile:4:obj-$(CONFIG_IRQ_TIMINGS) += timings.o
> ./kernel/irq/internals.h:#ifdef CONFIG_IRQ_TIMINGS
> ./kernel/irq/internals.h:#endif /* CON
On 06/02/2018 18:29, David Woodhouse wrote:
> From: KarimAllah Ahmed
>
> Intel processors use MSR_IA32_ARCH_CAPABILITIES MSR to indicate RDCL_NO
> (bit 0) and IBRS_ALL (bit 1). This is a read-only MSR. By default the
> contents will come directly from the hardware, but user-space can still
> over
On Wed, Feb 14, 2018 at 07:17:30AM +1100, NeilBrown wrote:
>
> If a signal-callback (lwi_on_signal) is set without lwi_allow_intr, as
> is the case in ldlm_completion_ast(), the behavior depends on the
> timeout set.
>
> If a timeout is set, then signals are ignored. If the timeout is
> reached,
On Thu, 15 Feb 2018 20:03:14 -0500
Minghui Liu wrote:
> Delete reference to the kernel-mentors mailing list because the mailing list
> no longer exists
>
> Signed-off-by: Minghui Liu
It does indeed seem to have vanished. Applied, thanks.
jon
On 02/15/2018 07:16 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.82 release.
There are 88 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be ma
Replace range expressions with seperate individual cases, i.e. convert case
1...3: to case 1: case 2: case 3
Range expression within case statements are non-standard C code and can create
issues over compiler and platform variety.
While compiling with gcc 4.8 (RHEL) I encountered this error on r
From: Markus Elfring
Date: Fri, 16 Feb 2018 15:03:45 +0100
Two update suggestions were taken into account
from static source code analysis.
Markus Elfring (2):
Delete an error message for a failed memory allocation
Use common error handling code
drivers/ata/pata_it821x.c | 13 +++--
From: Markus Elfring
Date: Fri, 16 Feb 2018 14:04:49 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/ata/pata_it821x.c | 6 +++---
1 file changed, 3 insertions(+),
On Fri, Feb 16, 2018 at 04:07:59PM +0200, Andy Shevchenko wrote:
> On Fri, Feb 16, 2018 at 12:47 PM, Hans de Goede wrote:
>
> > USB role switch is a device that can be used to choose the
> > data role for USB connector. With dual-role capable USB
> > controllers, the controller itself will be the
On Thu, Feb 15, 2018 at 8:59 PM, Colin King wrote:
> From: Colin Ian King
>
> The shifting of buf[5] by 24 bits to the left will be promoted to
> a 32 bit signed int and then sign-extended to an unsigned long. If
> the top bit of buf[5] is set then all then all the upper bits sec
> end up as also
Hi James,
On Thu, Feb 15, 2018 at 03:13:33PM -0800, James A. MacInnes wrote:
> 1 << BIT() causes double shift when the macro is unwrapped
> removed extra "1 <<"
No Signed-off-by... But this is already fixed:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7d54d0d38e
From: Markus Elfring
Date: Fri, 16 Feb 2018 14:40:42 +0100
Add a jump target so that a bit of exception handling can be better reused
at the end of this function.
Reorder three function calls.
Signed-off-by: Markus Elfring
---
drivers/ata/pata_it821x.c | 7 ---
1 file changed, 4 insertion
Live migration software in L0 needs to be able to capture an accurate state of
the L1 guest in order to save it and later restore it. One of the complications
of doing this when you have a nested/L2 guest is that the state from the L0
user space point of view is very indeterminstic. The state can b
Replace range expressions with seperate individual cases, i.e. convert case
1...3: to case 1: case 2: case 3
Range expression within case statements are non-standard C code and can create
issues over compiler and platform variety.
While compiling with gcc 4.8 (RHEL) I encountered this error on r
On 02/15/2018 10:00 PM, Naresh Kamboju wrote:
On 15 February 2018 at 20:44, Greg Kroah-Hartman
wrote:
This is the start of the stable review cycle for the 4.14.20 release.
There are 195 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these be
Hi,
On Fri, Feb 16, 2018 at 08:26:16AM +, Carlo Caione wrote:
> From: Carlo Caione
>
> The ECS EF20EA laptop ships an AXP288 but it is actually using a
> different, separate FG chip for AC and battery monitoring. On this
> laptop we need to keep using the regular ACPI driver and disable the
On Fri, Feb 16, 2018 at 02:51:13PM +0100, Sebastian Reichel wrote:
> On Fri, Feb 16, 2018 at 11:39:01AM +, Mark Brown wrote:
> > We don't have default lines like this for other MFDs...
> Is there a reason not to add them? It looks very useful to me:
Consistency. It's a lot easier to apply a
On Fri 16-02-18 15:02:17, Juergen Gross wrote:
> On 16/02/18 14:59, Michal Hocko wrote:
> > [CC Pavel]
> >
> > On Fri 16-02-18 14:37:26, Juergen Gross wrote:
> >> Commit f7f99100d8d95dbcf09e0216a143211e79418b9f ("mm: stop zeroing
> >> memory during allocation in vmemmap") broke Xen pv domains in s
On 02/15/2018 07:15 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.15.4 release.
There are 202 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
On Wed, Jan 17, 2018 at 02:10:47PM +0530, Naveen Panwar wrote:
> In staging/netlogic/platform.c Refactoring the identical code used
> in several places for calculating the physical address of
> memory-mapped objects on the device.Put that into an inline helper
> function and use it.
>
> Adjust the
On Fri, Feb 16, 2018 at 07:55:13PM +0530, Progyan Bhattacharya wrote:
> Replace range expressions with seperate individual cases, i.e. convert case
> 1...3: to case 1: case 2: case 3
> Range expression within case statements are non-standard C code and can
> create issues over compiler and platfo
base and sysclk_reg should be unsigned int, as that is what
regmap takes as a register address.
sysclk_mask is used to mask unsigned register values so
should be unsigned.
sysclk_shift is a shift value so is not allowed to be negative.
Signed-off-by: Richard Fitzgerald
---
sound/soc/codecs/wm_
Hi Thomas,
Here's the few updates I've collected for the irq department. Nothing
major (always a good thing), the biggest update being GICv2m now being
able to use Multi-MSI, and resulting in a negative diffstat...
Please pull.
M.
The following changes since commit 7928b2cbe55b2a410a0f5
On Fri, Feb 16, 2018 at 12:18:36AM +0530, Yash Omer wrote:
> This is patch fixes up a matching paranthesis alignment issue found by
> checkpatch.pl script.
>
> Signed-off-by: Yash Omer
> ---
> drivers/staging/wlan-ng/prism2mgmt.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>
Replace range expressions with seperate individual cases, i.e. convert case
1...3: to case 1: case 2: case 3
Range expression within case statements are non-standard C code and can create
issues over compiler and platform variety.
While compiling with gcc 4.8 (RHEL) I encountered this error on r
On Thu, Feb 15, 2018 at 9:01 PM, David Daney wrote:
> On 02/15/2018 04:45 AM, Andy Shevchenko wrote:
>> On Wed, Feb 14, 2018 at 2:55 AM, David Daney
>> wrote:
>>>
>>> The ISL12026 is a combination RTC and EEPROM device with I2C
>>> interface. The standard RTC driver interface is provided. The E
On Thu, Feb 15, 2018 at 7:07 PM, John Garry wrote:
> On 14/02/2018 16:16, Andy Shevchenko wrote:
> >>> + list_for_each_entry(rentry, &resource_list, node)
> >>> + resources[count++] = *rentry->res;
>> It has similarities with acpi_create_platform_device().
>>
> On 16 Feb 2018, at 6:34 PM, Hans de Goede wrote:
>
> Hi,
>
> On 15-02-18 20:00, Kai-Heng Feng wrote:
>> After Laptop Mode Tools starts to use min_power for LPM, a user found
>> out Crucial BX100 SSD can't get mounted.
>> Crucial BX100 SSD drives don't work well with min_power. This also
>> h
Hi,
Would you be interested in Storage Application Users contact information in
excel sheet for unlimited marketing usage? We provide Top Decision Makers
information like Name, Email, Title, Phone and company details of companies
using Storage Applications.
EMC
VMware
Veeam
Dell Storage
On Thu, Feb 01, 2018 at 08:14:52PM +0100, Stefano Manni wrote:
> Fixed r8712_get_ie, r8712_get_wpa_ie, r8712_get_wpa2_ie
> to have a length as unsigned int pointer instead of signed.
Can you rebase both of these patches on the staging-testing branch of
the staging.git tree so that I can apply th
On 16/02/2018 14:42, Andy Shevchenko wrote:
On Thu, Feb 15, 2018 at 7:07 PM, John Garry wrote:
On 14/02/2018 16:16, Andy Shevchenko wrote:
+ list_for_each_entry(rentry, &resource_list, node)
+ resources[count++] = *rentry->res;
It has similarities with acpi_create_plat
On Thu, Feb 15, 2018 at 8:06 PM, Steve Presser wrote:
> Hi Andy,
>
> No good news. It looks like the vanilla 4.15 series doesn't boot on this
> system. Still working on tracking down why/when it broke/if this is due to a
> Debian patch.
Just in case: you may cherry-pick necessary patches (4 or 5
On Fri, Feb 16, 2018 at 12:54 PM, Rafael J. Wysocki wrote:
> On Fri, Feb 16, 2018 at 11:39 AM, Andy Shevchenko
> wrote:
>> On Fri, Feb 16, 2018 at 11:14 AM, Rafael J. Wysocki
>> wrote:
>>> On Wed, Feb 14, 2018 at 12:23 PM, Andy Shevchenko
>>> wrote:
>>> IMO it is somewhat excessive to put the
> Am 16.02.2018 um 14:48 schrieb Mauro Carvalho Chehab
> :
>
> The parser at kernel-doc rejects names with dots in the middle.
> Fix it, in order to support nested structs/unions.
>
> Tested-by: Jani Nikula
> Signed-off-by: Mauro Carvalho Chehab
> ---
> scripts/kernel-doc | 2 +-
> 1 file chan
On 16/02/2018 15:16, Thomas Gleixner wrote:
> On Thu, 15 Feb 2018, Randy Dunlap wrote:
>
>> Hi,
>>
>> Is this a dead kconfig symbol? I don't see any Kconfig file that
>> sets/enables it.
>>
>> ./kernel/irq/Makefile:4:obj-$(CONFIG_IRQ_TIMINGS) += timings.o
>> ./kernel/irq/internals.h:#ifdef CONFIG
Adding back all the people that were Cc-ed on the initial email.
On Fri, 16 Feb 2018 15:18:21 +0100
Kamil Konieczny wrote:
> On 16.02.2018 15:00, Boris Brezillon wrote:
> > On Fri, 16 Feb 2018 12:21:53 +0100
> > Kamil Konieczny wrote:
> >
> >> On 16.02.2018 12:16, Boris Brezillon wrote:
>
On Mon, Nov 27, 2017 at 11:57:46AM -0500, Sinan Kaya wrote:
> pci_get_bus_and_slot() is restrictive such that it assumes domain=0 as
> where a PCI device is present. This restricts the device drivers to be
> reused for other domain numbers.
>
> Getting ready to remove pci_get_bus_and_slot() functi
On Tue, Dec 19, 2017 at 12:38:02AM -0500, Sinan Kaya wrote:
> pci_get_bus_and_slot() is restrictive such that it assumes domain=0 as
> where a PCI device is present. This restricts the device drivers to be
> reused for other domain numbers.
>
> Now that all users of pci_get_bus_and_slot() switched
On Tue, 13 Feb 2018 13:31:46 +0200
Mike Rapoport wrote:
> When function description includes brackets after the function name as
> suggested by Documentation/doc-guide/kernel-doc, the kernel-doc script
> omits the function name from "Scanning doc for" report.
> Extending match for identifier name
Em Fri, 16 Feb 2018 15:52:33 +0100
Markus Heiser escreveu:
> > Am 16.02.2018 um 14:48 schrieb Mauro Carvalho Chehab
> > :
> >
> > The parser at kernel-doc rejects names with dots in the middle.
> > Fix it, in order to support nested structs/unions.
> >
> > Tested-by: Jani Nikula
> > Signed-of
On Fri, Feb 16, 2018 at 06:11:10AM -0800, Matthew Wilcox wrote:
> On Fri, Feb 16, 2018 at 02:49:46PM +0300, Kirill A. Shutemov wrote:
> > @@ -38,12 +38,12 @@
> > *
> > */
> >
> > +#define l4_index(x)(((x) >> 39) & 511)
> > #define pud_index(x) (((x) >> PUD_SHIFT) & (PTRS_PER_PU
On Fri, Feb 16, 2018 at 08:09:24PM +0530, Progyan Bhattacharya wrote:
> Replace range expressions with seperate individual cases, i.e. convert case
> 1...3: to case 1: case 2: case 3
> Range expression within case statements are non-standard C code and can
> create issues over compiler and platfo
Andy
On Fri, Feb 16, 2018 at 9:17 AM, Andy Shevchenko
wrote:
> On Thu, Feb 15, 2018 at 6:54 PM, Matthew Whitehead
> wrote:
>> Several i586-class cpus supporting this instruction are missing from
>> the X86_CMPXCHG64 config group.
>
> What about Intel Quark? MinuteIA core which is currently set a
d_delete() holds dentry->d_lock and needs to acquire
dentry->d_inode->i_lock. This cannot be done with a spin_lock()
operation because it's the reverse of the regular lock order. To avoid
the ABBA deadlock it is done with a trylock loop.
Trylock loops are problematic in two scenarios:
1) PREEMP
This patchset removes all trylock loops from within the dcache code.
Both d_delete() and dentry_kill() hold dentry->d_lock while needing
to acquire dentry->d_inode->i_lock. dentry_kill() also needs to
acquire dentry->d_parent->d_lock. This cannot be done directly with
spin_lock() operations becaus
dentry_kill() holds dentry->d_lock and needs to acquire both
dentry->d_inode->i_lock and dentry->d_parent->d_lock. This cannot be
done with spin_lock() operations because it's the reverse of the
regular lock order. To avoid ABBA deadlocks it is done with two
trylock loops.
Trylock loops are proble
A subsequent patch will modify dentry_kill() to call lock_parent().
Move the dentry_kill() implementation "as is" below lock_parent()
first. This will help simplify the review of the subsequent patch
with dentry_kill() changes.
Signed-off-by: John Ogness
---
fs/dcache.c | 62
Commit 0d98439ea3c6 ("vfs: use lockred "dead" flag to mark unrecoverably
dead dentries") removed the `ref' parameter in dentry_kill() but its
documentation remained. Remove it.
Signed-off-by: John Ogness
---
fs/dcache.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/dcache.c b/fs/dcache.c
On Fri, Feb 16, 2018 at 4:41 AM, Kees Cook wrote:
> On Thu, Feb 15, 2018 at 10:06 AM, Kees Cook wrote:
>> On Thu, Feb 15, 2018 at 7:59 AM, Arnd Bergmann wrote:
>>> On Thu, Feb 15, 2018 at 4:25 PM, Josh Poimboeuf wrote:
On Thu, Feb 15, 2018 at 04:01:57PM +0100, Arnd Bergmann wrote:
> On
From: Andy Shevchenko
> Sent: 16 February 2018 14:23
...
> Wouldn't be better to use le32_to_cpu() or get_unaligned()?
Or shoot the members of the ANSI C committee who insisted on
promotion of unsigned char/short to int and sign preserving
promotion of int to unsigned long :-)
David
Hi, David, Eric, Neal et al.
On čtvrtek 15. února 2018 21:42:26 CET Oleksandr Natalenko wrote:
> I've faced an issue with a limited TCP bandwidth between my laptop and a
> server in my 1 Gbps LAN while using BBR as a congestion control mechanism.
> To verify my observations, I've set up 2 KVM VMs
On Fri, Feb 16, 2018 at 03:12:37PM +0100, Sebastian Reichel wrote:
> On Fri, Feb 16, 2018 at 01:44:48PM +, Mark Brown wrote:
> > On Fri, Feb 16, 2018 at 02:25:38PM +0100, Sebastian Reichel wrote:
> > > While it looks empty in the DT binding file, it's actually not empty
> > > once some standar
On Fri, 16 Feb 2018, Akira Yokosawa wrote:
> Hi,
>
> My forward-port patch doesn't apply to the "lkmm" branch.
> It looks like "linux-kernel-hardware.cat" is intentionally omitted there.
> Am I guessing right?
>
> If this is the case, I can prepare a patch to be applied to "lkmm".
> But I can't
>> On Feb 15, 2018, at 4:08 PM, Linus Torvalds
>> wrote:
>>
>> On Thu, Feb 15, 2018 at 3:29 PM, Andy Lutomirski wrote:
>>
>> It's possible we could get away with adding the prctl but making the
>> default be that only the bitness that matches the program being run is
>> allowed. After all,
Commit f7f99100d8d95dbcf09e0216a143211e79418b9f ("mm: stop zeroing
memory during allocation in vmemmap") broke Xen pv domains in some
configurations, as the "Pinned" information in struct page of early
page tables could get lost. This will lead to the kernel trying to
write directly into the page t
On 15/02/2018 at 21:44:53 +0100, Alexandre Belloni wrote:
> On 15/02/2018 at 19:36:14 +, Colin King wrote:
> > From: Colin Ian King
> >
> > The shifting of buf[5] by 24 bits to the left will be promoted to
> > a 32 bit signed int and then sign-extended to an unsigned long. If
> > the top bit
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.
Suggested-by: Thomas Gleixner
Signed-off-by: Laurent Dufour
---
mm/Kconfig | 3 +++
1 file changed, 3 insertions(+)
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
This is a port on kernel 4.15 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
Define CONFIG_SPECULATIVE_PAGE_FAULT for BOOK3S_64 and SMP. 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
From: Peter Zijlstra
Wrap the VMA modifications (vma_adjust/unmap_page_range) with sequence
counts such that we can easily test if a VMA is changed.
The unmap_page_range() one allows us to make assumptions about
page-tables; when we find the seqcount hasn't changed we can assume
page-tables are
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
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
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
From: Peter Zijlstra
Try a speculative fault before acquiring mmap_sem, if it returns with
VM_FAULT_RETRY continue with the mmap_sem acquisition and do the
traditional fault.
Signed-off-by: Peter Zijlstra (Intel)
[Clearing of FAULT_FLAG_ALLOW_RETRY is now done in
handle_speculative_fault()]
[
Add a new software event to count succeeded speculative page faults.
Signed-off-by: Laurent Dufour
---
include/uapi/linux/perf_event.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/uapi/linux/perf_event.h b/include/uapi/linux/perf_event.h
index e0739a1aa4b2..164383273147 100644
---
This patch a set of new trace events to collect the speculative page fault
event failures.
Signed-off-by: Laurent Dufour
---
include/trace/events/pagefault.h | 87
mm/memory.c | 62 ++--
2 files changed, 136 in
When the speculative page fault handler is returning VM_RETRY, there is a
chance that VMA fetched without grabbing the mmap_sem can be reused by the
legacy page fault handler. By reusing it, we avoid calling find_vma()
again. To achieve, that we must ensure that the VMA structure will not be
freed
In randconfig testing, we sometimes get this warning:
drivers/gpu/drm/radeon/radeon_object.c: In function 'radeon_bo_create':
drivers/gpu/drm/radeon/radeon_object.c:242:2: error: #warning Please enable
CONFIG_MTRR and CONFIG_X86_PAT for better performance thanks to write-combining
[-Werror=cpp]
We get a warning about some slow configurations in randconfig kernels:
mm/memory.c:83:2: error: #warning Unfortunate NUMA and NUMA Balancing config,
growing page-frame for last_cpupid. [-Werror=cpp]
The warning is reasonable by itself, but gets in the way of
randconfig build testing, so I'm hidi
This patch enable the speculative page fault on the PowerPC
architecture.
This will try a speculative page fault without holding the mmap_sem,
if it returns with VM_FAULT_RETRY, the mmap_sem is acquired and the
traditional page fault processing is done.
The speculative path is only tried for mult
When we build this driver with on x86-32, gcc produces a false-positive warning:
drivers/clk/renesas/clk-sh73a0.c: In function 'sh73a0_cpg_clocks_init':
drivers/clk/renesas/clk-sh73a0.c:155:10: error: 'parent_name' may be used
uninitialized in this function [-Werror=maybe-uninitialized]
return
Add support for the new speculative faults event.
Signed-off-by: Laurent Dufour
---
tools/include/uapi/linux/perf_event.h | 1 +
tools/perf/util/evsel.c | 1 +
tools/perf/util/parse-events.c| 4
tools/perf/util/parse-events.l| 1 +
tools/perf/util/python.c
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
301 - 400 of 889 matches
Mail list logo
