Hi Steve,
On Wed, 2017-10-04 at 13:14 -0400, Steven Rostedt wrote:
> On Fri, 22 Sep 2017 14:59:43 -0500
> Tom Zanussi wrote:
>
> > + /*
> > +* New timestamps may not be consistent with the previous setting.
> > +* Reset the buffer so that it doesn't have incomparable timestamps.
>
> I
hv_do_hypercall() does virt_to_phys() translation and with some configs
(CONFIG_SLAB) this doesn't work for percpu areas, we pass wrong memory to
hypervisor and get #GP. We could use working slow_virt_to_phys() instead
but doing so kills the performance.
Move pcpu_flush/pcpu_flush_ex structures ou
On Wed 04-10-17 16:46:35, Roman Gushchin wrote:
> Traditionally, the OOM killer is operating on a process level.
> Under oom conditions, it finds a process with the highest oom score
> and kills it.
>
> This behavior doesn't suit well the system with many running
> containers:
>
> 1) There is no
On Thu, 2017-10-05 at 12:21 +0530, Viresh Kumar wrote:
> Hi Joe,
Hi Viresh.
> Recently I was Cc'd for some of the patches from Manu, as
> get_maintainers incorrectly mentioned me.
>
> Apart from the fact that I never contributed to the mentioned
> file (drivers/phy/qualcomm/phy-qcom-qmp.c), the
On Wed, Sep 20, 2017 at 3:39 PM, Jerome Brunet wrote:
> pin_base was used with the manually set pin offset in meson pinctrl. This
> is no longer the case, pin_base is 0 on every meson pinctrl controllers
> and should go away.
>
> Tested-by: Martin Blumenstingl
> Signed-off-by: Jerome Brunet
Pa
On Wed, Sep 20, 2017 at 3:39 PM, Jerome Brunet wrote:
> On meson-gx platforms, TEST_N has been incorrectly declared in the EE
> controller while it belongs to AO controller.
>
> Move the pin to the appropriate controller
>
> Signed-off-by: Jerome Brunet
Patch applied.
Yours,
Linus Walleij
Since commit 83a0a96a5f26 ("sched/fair: Leverage the idle state info
when choosing the "idlest" cpu") find_idlest_grou_cpu (formerly
find_idlest_cpu) no longer returns -1.
Signed-off-by: Brendan Jackman
Cc: Dietmar Eggemann
Cc: Vincent Guittot
Cc: Josef Bacik
Cc: Ingo Molnar
Cc: Morten Rasmus
When the local group is not allowed we do not modify this_*_load from
their initial value of 0. That means that the load checks at the end
of find_idlest_group cause us to incorrectly return NULL. Fixing the
initial values to ULONG_MAX means we will instead return the idlest
remote group in that ca
This patchset optimises away an unused comparison, and fixes some corner cases
in
the find_idlest_group path of select_task_rq_fair.
Changes v2 -> v3:
- 1/5 through 4/5 unchanged.
- 5/5: Essentially undid [1]. Vincent pointed out that this isn't really a
bugfix but more of a change in poli
In preparation for changes that would otherwise require adding a new
level of indentation to the while(sd) loop, create a new function
find_idlest_cpu which contains this loop, and rename the existing
find_idlest_cpu to find_idlest_group_cpu.
Code inside the while(sd) loop is unchanged. @new_cpu i
When p is allowed on none of the CPUs in the sched_domain, we
currently return NULL from find_idlest_group, and pointlessly
continue the search on lower sched_domain levels (where p is also not
allowed) before returning prev_cpu regardless (as we have not updated
new_cpu).
Add an explicit check fo
find_idlest_group returns NULL when the local group is idlest. The
caller then continues the find_idlest_group search at a lower level
of the current CPU's sched_domain hierarchy. find_idlest_group_cpu is
not consulted and, crucially, @new_cpu is not updated. This means the
search is pointless and
On Thu, Oct 05, 2017 at 01:12:30PM +0200, Michal Hocko wrote:
> On Thu 05-10-17 11:27:07, Roman Gushchin wrote:
> > On Wed, Oct 04, 2017 at 02:24:26PM -0700, Shakeel Butt wrote:
> [...]
> > > Sorry about the confusion. There are two things. First, should we do a
> > > css_get on the newly selected
On Wed, Sep 20, 2017 at 3:39 PM, Jerome Brunet wrote:
> GPIOX_22 is declared as a gpio but the id is no present in the pin
> table. This hole trigger an error while reading the pingroup debugfs entry
>
> GPIOX_22 is no routed externally. For all we know, it could an internal
> pin of SoC
>
> Sign
On Thu, 2017-10-05 at 13:22 +0200, Linus Walleij wrote:
> On Wed, Sep 20, 2017 at 3:39 PM, Jerome Brunet wrote:
>
> > Offset on meson pinctrl and gpios is something that was carried from the
> > vendor driver, where there is a weird link between the 2
> > controllers. Since these 2 controllers ar
Intel vendor ID is defined globally, thus we may use PCI_VDEVICE().
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_ips.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/platform/x86/intel_ips.c b/drivers/platform/x86/intel_ips.c
index 6f6900065bc2..48
This makes code cleaner.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_ips.c | 18 +-
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/drivers/platform/x86/intel_ips.c b/drivers/platform/x86/intel_ips.c
index 063d9a1624b4..6f6900065bc2 100644
--- a/d
Use devm_ and pcim_ functions to make error handling
simpler and code smaller and tidier.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_ips.c | 62 ++--
1 file changed, 15 insertions(+), 47 deletions(-)
diff --git a/drivers/platform/x86/intel_
This patch removes the FSF address from the GPL notice to fix a
checkpatch.pl CHECK message.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_ips.c | 4
drivers/platform/x86/intel_ips.h | 4
2 files changed, 8 deletions(-)
diff --git a/drivers/platform/x86/intel_ips.c b/d
The routine is named incorrectly since the first attempt as there is
nothing like a put_opp() helper. We wanted to unregister the set_opp()
helper here and so it should rather be named as
dev_pm_opp_unregister_set_opp_helper().
Signed-off-by: Viresh Kumar
---
drivers/opp/core.c | 6 +++---
i
On Wed, Oct 4, 2017 at 4:47 PM, Sudeep Holla wrote:
> On 04/10/17 15:17, Arnd Bergmann wrote:
>> On Wed, Oct 4, 2017 at 3:53 PM, Sudeep Holla wrote:
>>> On 04/10/17 13:35, Arnd Bergmann wrote:
On Wed, Oct 4, 2017 at 1:07 PM, Sudeep Holla wrote:
>> There are probably several ways of doing t
There are fields in the struct ips_mcp_limits which are not used
anywhere and a label which we may get rid of.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_ips.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/platform/x86/intel_ips.c b/drivers
Hi,
On Wednesday, October 04, 2017 07:23:07 PM Hunter, Adrian wrote:
> > -Original Message-
> > From: Bartlomiej Zolnierkiewicz [mailto:b.zolnier...@samsung.com]
> > Sent: Wednesday, October 4, 2017 12:40 PM
> > To: Linus Walleij
> > Cc: Hunter, Adrian ; Ulf Hansson
> > ; linux-mmc ; lin
...instead of keeping pointer to struct pci_dev.
Signed-off-by: Andy Shevchenko
---
drivers/platform/x86/intel_ips.c | 51
1 file changed, 25 insertions(+), 26 deletions(-)
diff --git a/drivers/platform/x86/intel_ips.c b/drivers/platform/x86/intel_ips.c
From: Colin Ian King
Functions ahc_devlimited_syncrate and ahc_linux_initialize_scsi_bus
are declared static in their prototypes but are missing in their
definitions, so add the missing static.
Cleans up sparse warnings:
symbol 'ahc_devlimited_syncrate' was not declared. Should it be static?
sym
More directly describes the only thing it does.
Signed-off-by: Ulf Magnusson
---
scripts/kconfig/menu.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/scripts/kconfig/menu.c b/scripts/kconfig/menu.c
index e935793..8354dfa 100644
--- a/scripts/kconfig/menu.c
Hello,
This patchset fixes a segfault that occurs if 'm' appears in certain
expressions before the modules symbol is defined. The problem is that m is
rewritten to m && already during parsing. Doing it in
menu_finalize(), which runs after parsing, fixes the problem.
To aid the review and people
menu_finalize() is one of the more opaque parts of Kconfig, and I need
to make some changes to it to fix an issue related to modules. Add some
comments related to expression rewriting and dependency propagation as a
review aid. They will also help other people trying to understand the
code.
Signed
Kconfig currently doesn't handle 'm' appearing in a Kconfig file before
the modules symbol is defined (the symbol with 'option modules'). The
problem is the following code, which runs during parsing:
/* change 'm' into 'm' && MODULES */
if (e->left.sym == &symbol_mod)
gcc produces a harmless warning about a recently introduced
signed integer overflow:
drivers/net/wireless/rsi/rsi_91x_hal.c: In function 'rsi_prepare_mgmt_desc':
include/uapi/linux/swab.h:13:15: error: integer overflow in expression
[-Werror=overflow]
(((__u16)(x) & (__u16)0x00ffU) << 8) | \
On Wed 04-10-17 16:46:36, Roman Gushchin wrote:
> The cgroup-aware OOM killer treats leaf memory cgroups as memory
> consumption entities and performs the victim selection by comparing
> them based on their memory footprint. Then it kills the biggest task
> inside the selected memory cgroup.
>
> B
The new backlight code causes a link failure when backlight
support itself is disabled:
drivers/gpu/drm/omapdrm/displays/panel-dpi.o: In function `panel_dpi_probe_of':
panel-dpi.c:(.text+0x35c): undefined reference to `of_find_backlight_by_node'
This adds a Kconfig dependency like we have for the
> Anything with bytes 1-31,127 will get -EACCES.
You're making a mistake of catering to Unix shells which are pure garbage
as programming languages instead of fixing them or switching to saner
alternatives and then "fixing" kernel to sort-of workaround Unix shells
deficiencies.
Formally, you patc
An earlier bugfix tried to work around this build failure:
drivers/gpu/drm/i915/selftests/mock_gem_device.c: In function 'mock_gem_device':
drivers/gpu/drm/i915/selftests/mock_gem_device.c:151:20: error: 'struct
dev_archdata' has no member named 'iommu'
Checking for CONFIG_IOMMU_API is not suffi
One of the recent changes introduced a warning about
undefined behavior in the sanity checking:
drivers/gpu/drm/i915/intel_ddi.c: In function 'intel_ddi_hdmi_level':
drivers/gpu/drm/i915/intel_ddi.c:654:6: error: 'n_hdmi_entries' may be used
uninitialized in this function [-Werror=maybe-uninitial
A bugfix for the SMP case broke the build for the UP case:
arch/arm/mach-shmobile/headsmp-apmu.o: In function `shmobile_boot_apmu':
(.text+0x34): undefined reference to `secondary_startup'
The assembler file mixes code that is used for SMP with code
that we also need on a single-CPU build, so I'm
The new driver fails to build when CONFIG_PINCTRL is disabled:
drivers/gpu/drm/rockchip/rockchip_lvds.c: In function
'rockchip_lvds_grf_config':
drivers/gpu/drm/rockchip/rockchip_lvds.c:229:39: error: dereferencing pointer
to incomplete type 'struct dev_pin_info'
if (lvds->pins && !IS_ERR(lvd
With CONFIG_HWSPINLOCK=m, the new driver fails to link as a built-in driver:
drivers/spi/spi-sprd-adi.o: In function `sprd_adi_remove':
spi-sprd-adi.c:(.text+0x18): undefined reference to `hwspin_lock_free'
drivers/spi/spi-sprd-adi.o: In function `sprd_adi_probe':
spi-sprd-adi.c:(.text+0xfc): unde
The ARM allmodconfig build fails in linux-next, since one
clk interface was accidentally never exported but is now
used by an mmc driver:
ERROR: "clk_bulk_prepare" [drivers/mmc/host/sdhci-msm.ko] undefined!
This exports it as well.
Fixes: d8034e3379a8 ("mmc: sdhci-msm: Utilize bulk clock API")
F
On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrote:
> diff --git a/arch/powerpc/kernel/membarrier.c
> b/arch/powerpc/kernel/membarrier.c
> new file mode 100644
> index ..b0d79a5f5981
> --- /dev/null
> +++ b/arch/powerpc/kernel/membarrier.c
> @@ -0,0 +1,45 @@
> +void memb
Use vma_pages function on vma object instead of explicit computation.
This is a clean up patch.
Signed-off-by: Allen Pais
---
arch/arm64/mm/dma-mapping.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/arch/arm64/mm/dma-mapping.c b/arch/arm64/mm/dma-mapping.c
index 614a
Quoting Arnd Bergmann (2017-10-05 13:07:22)
> An earlier bugfix tried to work around this build failure:
>
> drivers/gpu/drm/i915/selftests/mock_gem_device.c: In function
> 'mock_gem_device':
> drivers/gpu/drm/i915/selftests/mock_gem_device.c:151:20: error: 'struct
> dev_archdata' has no member
Looks good,
Reviewed-by: Johannes Thumshirn
--
Johannes Thumshirn Storage
jthumsh...@suse.de+49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG
Looks good,
Reviewed-by: Johannes Thumshirn
--
Johannes Thumshirn Storage
jthumsh...@suse.de+49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG N
On Thu, 2017-10-05 at 14:05 +0200, Arnd Bergmann wrote:
> gcc produces a harmless warning about a recently introduced
> signed integer overflow:
>
> drivers/net/wireless/rsi/rsi_91x_hal.c: In function 'rsi_prepare_mgmt_desc':
> include/uapi/linux/swab.h:13:15: error: integer overflow in expression
On 05/10/17 13:16, Allen Pais wrote:
> Use vma_pages function on vma object instead of explicit computation.
> This is a clean up patch.
A version of this is already queued for -next here:
https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/commit/?h=for-next/core&id=b4f4a2755665b
On 10/05/2017 07:23 AM, Nicholas Piggin wrote:
On Wed, 4 Oct 2017 14:37:53 -0700
"Paul E. McKenney" wrote:
From: Mathieu Desnoyers
Provide a new command allowing processes to register their intent to use
the private expedited command.
This allows PowerPC to skip the full memory barrier i
On Thu, Oct 05, 2017 at 02:11:17PM +0200, Arnd Bergmann wrote:
> This adds a hard Kconfig dependency on HWSPINLOCK, which is the
> simplest solution since we don't care about building for the case
> without HWSPINLOCK.
Given that there are stubs for HWSPINLOCK it'd be good to also have an
|| COMP
Use vma_pages function on vma object instead of explicit computation.
This is a clean up patch.
A version of this is already queued for -next here:
https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git/commit/?h=for-next/core&id=b4f4a2755665bf847231050b569f587ce0945482
Ah.
On Thu, Oct 05, 2017 at 02:12:50PM +0200, Peter Zijlstra wrote:
> On Wed, Oct 04, 2017 at 02:37:53PM -0700, Paul E. McKenney wrote:
> > diff --git a/arch/powerpc/kernel/membarrier.c
> > b/arch/powerpc/kernel/membarrier.c
> > new file mode 100644
> > index ..b0d79a5f5981
> > --- /dev/nu
Hi Arnd,
On Thu, Oct 5, 2017 at 2:09 PM, Arnd Bergmann wrote:
> A bugfix for the SMP case broke the build for the UP case:
>
> arch/arm/mach-shmobile/headsmp-apmu.o: In function `shmobile_boot_apmu':
> (.text+0x34): undefined reference to `secondary_startup'
>
> The assembler file mixes code that
Em Thu, 5 Oct 2017 11:21:07 +0300
Sakari Ailus escreveu:
> Hi Mauro,
>
> My apologies for the late reply.
>
> On Tue, Aug 29, 2017 at 10:07:50AM -0300, Mauro Carvalho Chehab wrote:
> > Em Tue, 29 Aug 2017 10:47:48 +0300
> > Sakari Ailus escreveu:
> >
> > > Hi Mauro,
> > >
> > > Thanks for
Commit-ID: 69a330007091ea8a801dd9fcd897ec52f9529586
Gitweb: https://git.kernel.org/tip/69a330007091ea8a801dd9fcd897ec52f9529586
Author: Nicolas Iooss
AuthorDate: Mon, 2 Oct 2017 11:28:35 +0200
Committer: Thomas Gleixner
CommitDate: Thu, 5 Oct 2017 14:23:06 +0200
RAS/CEC: Use the right
Commit-ID: 262e681183ddcdb24d64a2f993e41a226adcec29
Gitweb: https://git.kernel.org/tip/262e681183ddcdb24d64a2f993e41a226adcec29
Author: Borislav Petkov
AuthorDate: Mon, 2 Oct 2017 11:28:36 +0200
Committer: Thomas Gleixner
CommitDate: Thu, 5 Oct 2017 14:23:06 +0200
x86/mce: Hide mca_cfg
On Thu, Oct 05, 2017 at 02:06:49PM +0200, Michal Hocko wrote:
> On Wed 04-10-17 16:46:36, Roman Gushchin wrote:
> > The cgroup-aware OOM killer treats leaf memory cgroups as memory
> > consumption entities and performs the victim selection by comparing
> > them based on their memory footprint. Then
On Wed, Oct 04, 2017 at 03:34:55PM +0200, Arnd Bergmann wrote:
> Replaces upstream commit 0b2e9e7947e7 ("media: staging/imx: remove
> confusing IS_ERR_OR_NULL usage")
>
> We get a harmless warning about a potential uninitialized variable
> use in the driver:
>
> drivers/staging/media/imx/imx-medi
On 10/05/2017 01:00 PM, David Howells wrote:
Lockdown is typically enabled during boot and may be terminated, if configured,
by typing a special key combination on a directly attached physical keyboard.
Does this include a Bluetooth keyboard (which might not actually exist
and might in reality
On Wed, Oct 04, 2017 at 10:46:56PM +0530, Srishti Sharma wrote:
> drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 8 +++-
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
> b/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
> index
On 5 October 2017 at 09:58, Mathias Krause wrote:
> On 5 October 2017 at 09:38, Borislav Petkov wrote:
>> On Wed, Oct 04, 2017 at 08:08:12PM +0200, Mathias Krause wrote:
>>> diff --git a/arch/x86/include/asm/alternative.h
>>> b/arch/x86/include/asm/alternative.h
>>> index c096624137ae..7c553f48f
On Wed, 4 Oct 2017, Thiago Jung Bauermann wrote:
> It turns out that not all paths calling arch_update_cpu_topology hold
> cpu_hotplug_lock, but that's ok because those paths aren't supposed to race
> with any concurrent hotplug events.
>
> Callers of arch_update_cpu_topology are expected to know
On Thu, Oct 05, 2017 at 02:35:33PM +0200, Mathias Krause wrote:
> Note the "<"! ...comment is wrong, though the implementation works!
I know, I realized that when I looked at alternative-asm.h. Wanted to
double-check it with Micha first.
Testing your patch now...
--
Regards/Gruss,
Boris.
G
2017-10-05 03:53-0700, Wanpeng Li:
> From: Wanpeng Li
>
> If we take TSC-deadline mode timer out of the picture, the Intel SDM
> does not say that the timer is disable when the timer mode is change,
> either from one-shot to periodic or vice versa.
>
> After this patch, the timer is no longer di
On Mon, Oct 02, 2017 at 02:45:19PM +0200, Pontus Andersson wrote:
> Commit b6c159a9cb69 ("i2c: ismt: Don't duplicate the receive length for
> block reads") broke I2C block reads. It aimed to fix normal SMBus block
> read, but changed the correct behavior of I2C block read in the process.
>
> Accor
Commit-ID: 92bb6cb1403015b1b9520332c8f2ad983c220f67
Gitweb: https://git.kernel.org/tip/92bb6cb1403015b1b9520332c8f2ad983c220f67
Author: Kees Cook
AuthorDate: Wed, 4 Oct 2017 17:54:25 -0700
Committer: Thomas Gleixner
CommitDate: Thu, 5 Oct 2017 14:34:55 +0200
x86/mce: Convert timers to
On Wed, Oct 04, 2017 at 10:34:02PM +0200, Srinivasan Shanmugam wrote:
> Removed all the unnecessary extern from rtl8723bs
>
The patch is good but doesn't match the description.
regards,
dan carpenter
I initially submitted patch 2/3 as a standalone, but it turned out
during some development for iio that some additional functionalities
would be useful as well.
The first patch pulls in slab.h directly instead of relying on the
include from irq.h.
The second exposes an interface for accessing the
Some users need to access the base of the allocated interrupt range.
Although this can be calculated manually, it's more elegant to expose
an interface for that.
Signed-off-by: Bartosz Golaszewski
---
include/linux/irq_sim.h | 1 +
kernel/irq/irq_sim.c| 11 +++
2 files changed, 12 i
Add a routine allowing to retrieve the offset corresponding with an
allocated interrupt number from an irq_sim object.
Signed-off-by: Bartosz Golaszewski
---
include/linux/irq_sim.h | 1 +
kernel/irq/irq_sim.c| 15 +++
2 files changed, 16 insertions(+)
diff --git a/include/linu
We're calling kfree() in the irq_sim code but slab.h is pulled in
indirectly via irq.h. Include it explicitly.
Signed-off-by: Bartosz Golaszewski
---
kernel/irq/irq_sim.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/irq/irq_sim.c b/kernel/irq/irq_sim.c
index 24caabf1a0f7..bd7dc1db6
2017-09-26 19:06 GMT+02:00 Bartosz Golaszewski :
> Some users need to access the base of the allocated interrupt range.
> Although this can be calculated manually, it's more elegant to expose
> an interface for that.
>
> Signed-off-by: Bartosz Golaszewski
> ---
> When porting the iio_dummy_evgen t
On Wed, 04 Oct 2017 15:24:23 -0500
Scott Wood wrote:
> On Wed, 2017-10-04 at 15:18 -0400, Steven Rostedt wrote:
> > On Sun, 16 Jul 2017 19:16:30 -0500
> > Scott Wood wrote:
> >
> > > Reduce code duplication and take advantage of bisection logic
> > > improvements by calling config-bisect.pl.
Hi,
On Thu, 5 Oct 2017, Borislav Petkov wrote:
> On Thu, Oct 05, 2017 at 02:35:33PM +0200, Mathias Krause wrote:
> > Note the "<"! ...comment is wrong, though the implementation works!
>
> I know, I realized that when I looked at alternative-asm.h. Wanted to
> double-check it with Micha first.
2017-10-05 20:40 GMT+08:00 Radim Krčmář :
> 2017-10-05 03:53-0700, Wanpeng Li:
>> From: Wanpeng Li
>>
>> If we take TSC-deadline mode timer out of the picture, the Intel SDM
>> does not say that the timer is disable when the timer mode is change,
>> either from one-shot to periodic or vice versa.
There's no good reason to keep the internal structure of struct qrwlock
hidden from qrwlock.h, particularly as it's actually needed for unlock
and ends up being abstracted independently behind the __qrwlock_write_byte
function.
Stop pretending we can hide this stuff, and move the __qrwlock definit
Hi all,
This patch series reworks bits of the qrwlock code that it can be used
to replace the asm rwlocks currently implemented for arm64. The structure
of the series is:
Patches 1-3 : Work WFE into qrwlock using atomic_cond_read_acquire so
we can avoid busy-waiting.
Patc
Now that the qrwlock can make use of WFE, remove our homebrew rwlock
code in favour of the generic queued implementation.
Signed-off-by: Will Deacon
---
arch/arm64/Kconfig | 17
arch/arm64/include/asm/Kbuild | 1 +
arch/arm64/include/asm/spinlock.h |
Move the check for a stuck SCL before the check for a high SDA.
This prevent false positives in the specific case that SDA is fine
and SCL is stuck, which previously returned 0.
Also check SDA again after the loop, if we can.
Together, these changes should lead to a lot more failed
recoveries bein
When a prospective writer takes the qrwlock locking slowpath due to the
lock being held, it attempts to cmpxchg the wmode field from 0 to
_QW_WAITING so that concurrent lockers also take the slowpath and queue
on the spinlock accordingly, allowing the lockers to drain.
Unfortunately, this isn't fa
Now that all atomic operations are performed on the full lock word of
the qrwlock, there's no need to define a union type exposing the reader
and writer subcomponents. Remove them.
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Waiman Long
Cc: Boqun Feng
Cc: "Paul E. McKenney"
Signed-off-by: Will Dea
The qrwlock slowpaths involve spinning when either a prospective reader
is waiting for a concurrent writer to drain, or a prospective writer is
waiting for concurrent readers to drain. In both of these situations,
atomic_cond_read_acquire can be used to avoid busy-waiting and make use
of any backof
smp_cond_load_acquire provides a way to spin on a variable with acquire
semantics until some conditional expression involing the variable is
satisfied. Architectures such as arm64 can potentially enter a low-power
state, waking up only when the value of the variable changes, which
reduces the syste
On 05/10/17 12:56, Arnd Bergmann wrote:
> On Wed, Oct 4, 2017 at 4:47 PM, Sudeep Holla wrote:
>> On 04/10/17 15:17, Arnd Bergmann wrote:
>>> On Wed, Oct 4, 2017 at 3:53 PM, Sudeep Holla wrote:
On 04/10/17 13:35, Arnd Bergmann wrote:
> On Wed, Oct 4, 2017 at 1:07 PM, Sudeep Holla wrote
rwlock.h should not be included directly. Instead linux/splinlock.h
should be included. One thing it does is to break the RT build.
Cc: Stefano Stabellini
Cc: xen-de...@lists.xenproject.org
Cc: linux-arm-ker...@lists.infradead.org
Signed-off-by: Sebastian Andrzej Siewior
---
arch/arm/xen/p2m.c
rwlock.h should not be included directly. Instead linux/splinlock.h
should be included. One thing it does is to break the RT build.
Cc: Vaibhav Agarwal
Cc: Mark Greer
Cc: Johan Hovold
Cc: Alex Elder
Cc: Greg Kroah-Hartman
Cc: greybus-...@lists.linaro.org
Cc: de...@driverdev.osuosl.org
Signed-
rwlock.h should not be included directly. Instead linux/splinlock.h
should be included. One thing it does is to break the RT build.
Cc: Eric Van Hensbergen
Cc: Ron Minnich
Cc: Latchesar Ionkov
Cc: "David S. Miller"
Cc: v9fs-develo...@lists.sourceforge.net
Cc: net...@vger.kernel.org
Signed-off-
On Thu 05-10-17 13:32:14, Roman Gushchin wrote:
> On Thu, Oct 05, 2017 at 02:06:49PM +0200, Michal Hocko wrote:
> > On Wed 04-10-17 16:46:36, Roman Gushchin wrote:
> > > The cgroup-aware OOM killer treats leaf memory cgroups as memory
> > > consumption entities and performs the victim selection by
On 05/10/17 11:52, Philipp Zabel wrote:
Do we expect this to grow more different cases in the future?
Grow - I'm not so sure. Change definitely there's at least one other
type of MX7 (which I don't have) that doesn't require a clock setup here
at all.
Maybe it would be better to just stor
On 5 October 2017 at 14:52, Michael Matz wrote:
> On Thu, 5 Oct 2017, Borislav Petkov wrote:
>> On Thu, Oct 05, 2017 at 02:35:33PM +0200, Mathias Krause wrote:
>> > Note the "<"! ...comment is wrong, though the implementation works!
>>
>> I know, I realized that when I looked at alternative-asm.h.
On Tue, Oct 03, 2017 at 09:54:31AM -0700, Linus Torvalds wrote:
> On Tue, Oct 3, 2017 at 7:06 AM, Fengguang Wu wrote:
> >
> > This patch triggers a NULL-dereference bug at update_stack_state().
> > Although its parent commit also has a NULL-dereference bug, however
> > the call stack looks rather
On Thursday, October 5, 2017 3:27:14 AM CEST Srinivas Pandruvada wrote:
> On Thu, 2017-10-05 at 02:51 +0200, Rafael J. Wysocki wrote:
> > On Thu, Oct 5, 2017 at 2:39 AM, Srinivas Pandruvada
> > wrote:
> > >
> > > On Thu, 2017-10-05 at 02:10 +0200, Rafael J. Wysocki wrote:
> > > >
> > > > On Thu,
On Thu, 2017-10-05 at 13:28 +0200, Srinivasan Shanmugam wrote:
> Fix checkpatch issues: "CHECK: Alignment should match open parenthesis"
Subject and commit message don't match
> diff --git a/drivers/staging/rtl8723bs/core/rtw_recv.c
> b/drivers/staging/rtl8723bs/core/rtw_recv.c
[]
> @@ -1227,7 +
On Wed, 4 Oct 2017, Andi Kleen wrote:
> From: Andi Kleen
>
> Move the XSAVE initialization code to be after parsing early parameters.
> I don't see any reason why the FPU code needs to be initialized that
> early, nothing else in the initialization phase uses XSAVE.
> This is useful to be able t
Hi Eugeniy,
On 09/22/2017 09:49 AM, Eugeniy Paltsev wrote:
DW ethernet controller on HSDK hangs sometimes after SW reset, so
add reset node to make possible to reset DW ethernet controller HW.
Signed-off-by: Eugeniy Paltsev
---
Changes v2 -> v3:
* Remove v1 suffix as we finaly got rid of v1
This patchset makes the OOM killer cgroup-aware.
v11:
- Fixed an issue with skipping the root mem cgroup
(discovered by Shakeel Butt)
- Moved a check in __oom_kill_process() to the memmory.oom_group
patch, added corresponding comments
- Added a note about ignoring tasks with oom_scor
The cgroup-aware OOM killer treats leaf memory cgroups as memory
consumption entities and performs the victim selection by comparing
them based on their memory footprint. Then it kills the biggest task
inside the selected memory cgroup.
But there are workloads, which are not tolerant to a such beh
Document the cgroup-aware OOM killer.
Signed-off-by: Roman Gushchin
Cc: Michal Hocko
Cc: Vladimir Davydov
Cc: Johannes Weiner
Cc: Tetsuo Handa
Cc: Andrew Morton
Cc: David Rientjes
Cc: Tejun Heo
Cc: kernel-t...@fb.com
Cc: cgro...@vger.kernel.org
Cc: linux-...@vger.kernel.org
Cc: linux-kerne
2017-10-04 12:17 GMT+02:00 Mark Brown :
> On Tue, Oct 03, 2017 at 04:08:30PM -0700, Sandeep Patil wrote:
>
>> It is entirely possible and easy in android/ueventd to create those nodes
>> under "/dev/ion/". (assuming the heap 'subsystem' for these new devices will
>> point to 'ion').
I think it is
The oom_kill_process() function consists of two logical parts:
the first one is responsible for considering task's children as
a potential victim and printing the debug information.
The second half is responsible for sending SIGKILL to all
tasks sharing the mm struct with the given victim.
This co
Implement mem_cgroup_scan_tasks() functionality for the root
memory cgroup to use this function for looking for a OOM victim
task in the root memory cgroup by the cgroup-ware OOM killer.
The root memory cgroup is treated as a leaf cgroup, so only tasks
which are directly belonging to the root cgro
Traditionally, the OOM killer is operating on a process level.
Under oom conditions, it finds a process with the highest oom score
and kills it.
This behavior doesn't suit well the system with many running
containers:
1) There is no fairness between containers. A small container with
few large pr
201 - 300 of 958 matches
Mail list logo
