Hi Rikard,
On Tue, Aug 6, 2019 at 4:55 AM Rikard Falkeborn
wrote:
>
> On Sun, Aug 04, 2019 at 03:45:16PM +0900, Masahiro Yamada wrote:
> > On Sun, Aug 4, 2019 at 3:36 AM Rikard Falkeborn
> > wrote:
> > >
> > > On Sat, Aug 03, 2019 at 12:12:46PM +0900, Masahiro Yamada wrote:
> > > > On Sat, Aug
+Maxime
On Tue, Aug 6, 2019 at 6:50 AM Neil Armstrong wrote:
>
> The Amlogic Meson DWMAC glue bindings needs a second reg cells for the
> glue registers, thus update the reg minItems/maxItems to allow more
> than a single reg cell.
>
> Signed-off-by: Neil Armstrong
> ---
> Documentation/devicet
On Mon, Jul 29, 2019 at 11:22 PM Nicolin Chen wrote:
>
> On Sun, Jul 28, 2019 at 10:24:25PM +0300, Daniel Baluta wrote:
> > SAI supports up to 8 Rx/Tx data lines which can be enabled
> > using TCE/RCE bits of TCR3/RCR3 registers.
> >
> > Data lines to be enabled are read from DT fsl,dl-mask proper
On 7/30/19 05:46, Viresh Kumar wrote:
> On 29-07-19, 13:16, Saravana Kannan wrote:
>> Sibi might be working on doing that for the SDM845 CPUfreq driver.
>> Georgi could also change his GPU driver use case to use this BW OPP
>> table and required-opps.
>>
>> The problem is that people don't want to
On 2019-08-06 02:55, Pierre-Louis Bossart wrote:
diff --git a/drivers/soundwire/cadence_master.c
b/drivers/soundwire/cadence_master.c
index 5d9729b4d634..89c55e4bb72c 100644
--- a/drivers/soundwire/cadence_master.c
+++ b/drivers/soundwire/cadence_master.c
@@ -48,6 +48,8 @@
#define CDNS_MCP_SSP
On Tue, Aug 06, 2019 at 08:01:46AM +0200, Vitaly Kuznetsov wrote:
> svm->next_rip is only used by skip_emulated_instruction() and in case
> kvm_set_msr() fails we rightfully don't do that. Move svm->next_rip
> advancement to 'else' branch to avoid creating false impression that
> it's always advanc
On 2019-08-06 02:55, Pierre-Louis Bossart wrote:
@@ -1493,6 +1493,11 @@ static int _sdw_prepare_stream(struct sdw_stream_runtime
*stream)
}
}
+ if (!bus) {
+ pr_err("Configuration error in %s\n", __func__);
+ return -EINVAL;
+ }
+
T
On Tue, 6 Aug 2019 18:15:43 +0300
Andy Shevchenko wrote:
> Hex dump as many as 16 bytes at once in trace_print_hex_seq()
> instead of byte-by-byte approach.
>
> Signed-off-by: Andy Shevchenko
> ---
> v2: fix length calculation, so, when buf_len=16 it won't indefinitely loop
> kernel/trace/tra
On Tue, Aug 06, 2019 at 09:59:42AM -0400, Steven Rostedt wrote:
> As Peter stated later in this thread, we only have the IRQ stack frame saved
> here, because we just took an NMI, and this is the logic to determine if it
> was a nested NMI or not (where we have to be *very* careful about touching t
Dear Linux folks,
Trying to decrease the resume time of Linux 5.3-rc3 on the Dell OptiPlex
5040 with the device below
$ lspci -nn -s 00:1f.6
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection
(2) I219-V [8086:15b8] (rev 31)
pm-graph’s script `sleepgraph.py` shows
On 8/6/19 10:27 AM, Cezary Rojewski wrote:
On 2019-08-06 02:55, Pierre-Louis Bossart wrote:
diff --git a/drivers/soundwire/cadence_master.c
b/drivers/soundwire/cadence_master.c
index 5d9729b4d634..89c55e4bb72c 100644
--- a/drivers/soundwire/cadence_master.c
+++ b/drivers/soundwire/cadence_ma
On Tue, Aug 06, 2019 at 06:47:08AM +, Ardelean, Alexandru wrote:
> On Mon, 2019-08-05 at 16:51 +0200, Andrew Lunn wrote:
> > [External]
> >
> > On Mon, Aug 05, 2019 at 07:54:43PM +0300, Alexandru Ardelean wrote:
> > > Sometimes, the connection between a MAC and PHY is done via a
> > > mode/int
On 8/6/19 10:31 AM, Cezary Rojewski wrote:
On 2019-08-06 02:55, Pierre-Louis Bossart wrote:
@@ -1493,6 +1493,11 @@ static int _sdw_prepare_stream(struct
sdw_stream_runtime *stream)
}
}
+ if (!bus) {
+ pr_err("Configuration error in %s\n", __func__);
+ return
On 8/6/19 11:16 AM, Alexander Duyck wrote:
> On Tue, 2019-08-06 at 07:31 -0400, Michael S. Tsirkin wrote:
>> On Mon, Aug 05, 2019 at 09:27:16AM -0700, Alexander Duyck wrote:
>>> On Mon, 2019-08-05 at 12:00 -0400, Nitesh Narayan Lal wrote:
On 8/1/19 6:38 PM, Alexander Duyck wrote:
> From:
On Tue, Aug 06, 2019 at 08:01:48AM +0200, Vitaly Kuznetsov wrote:
> When doing x86_emulate_instruction(EMULTYPE_SKIP) interrupt shadow has to
> be cleared if and only if the skipping is successful.
>
> There are two immediate issues:
> - In SVM skip_emulated_instruction() we are not zapping interr
On Tue, Aug 06, 2019 at 08:01:47AM +0200, Vitaly Kuznetsov wrote:
> When we're unable to skip instruction with kvm_emulate_instruction() we
> will not advance RIP and most likely the guest will get stuck as
> consequitive attempts to execute the same instruction will likely result
> in the same beh
On Tue, Aug 06, 2019 at 07:11:57AM +, Ardelean, Alexandru wrote:
> On Mon, 2019-08-05 at 17:28 +0200, Andrew Lunn wrote:
> > [External]
> >
> > > +struct adin_hw_stat {
> > > + const char *string;
> > > +static void adin_get_strings(struct phy_device *phydev, u8 *data)
> > > +{
> > > + int i;
On Fri, Aug 02, 2019 at 12:11:24PM -0400, Steven Rostedt wrote:
> On Fri, 2 Aug 2019 12:09:20 -0400
> Steven Rostedt wrote:
>
> > On Fri, 2 Aug 2019 11:22:59 -0400
> > Steven Rostedt wrote:
> >
> > > I think you are not explaining the issue correctly. From looking at the
> > > document, I think
On 03/08/2019 20:50, Martin Blumenstingl wrote:
> On Wed, Jul 31, 2019 at 2:44 PM Neil Armstrong
> wrote:
> [...]
>> + memory@0 {
>> + device_type = "memory";
>> + reg = <0x0 0x0 0x0 0x4000>;
> nit-pick: we typically use the memory size used in the board size
On Mon, Aug 05, 2019 at 03:02:37PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.188 release.
> There are 22 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
On Mon, Aug 05, 2019 at 03:02:26PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.188 release.
> There are 42 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
On Mon, Aug 05, 2019 at 03:02:25PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.137 release.
> There are 53 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 kno
On Mon, Aug 05, 2019 at 03:02:13PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.65 release.
> There are 74 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
On Mon, Aug 05, 2019 at 03:01:27PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.2.7 release.
> There are 131 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.
On Mon, Jul 22, 2019 at 04:37:40PM +0100, Lorenzo Pieralisi wrote:
> The generic ARM CPUidle driver includes by mistake.
>
> Remove the topology header include.
>
> Signed-off-by: Lorenzo Pieralisi
> Cc: Ulf Hansson
> Cc: Sudeep Holla
Reviewed-by: Sudeep Holla
--
Regards,
Sudeep
On Mon, Jul 22, 2019 at 04:37:41PM +0100, Lorenzo Pieralisi wrote:
> CPUidle back-end operations are not implemented in some platforms
> but this should not be considered an error serious enough to be
> logged. Check the arm_cpuidle_init() return value to detect whether
> the failure must be report
> -Original Message-
> From: Paul Menzel
> Sent: Tuesday, August 6, 2019 10:36 AM
> To: Jeff Kirsher
> Cc: intel-wired-...@lists.osuosl.org; Linux Kernel Mailing List; Limonciello,
> Mario
> Subject: MDI errors during resume from ACPI S3 (suspend to ram)
>
> Dear Linux folks,
>
>
> Try
>
> What accounting in particular is upset? Is it things like
> select_idle_sibling() that thinks the thread is idle and tries to place
> tasks there?
>
The major issue that we saw was, certain work load causes the idle cpu to never
wakeup and schedule again even when there are runnable threads in
On Mon, Jul 22, 2019 at 04:37:42PM +0100, Lorenzo Pieralisi wrote:
> The PSCI checker currently relies on the generic ARM CPUidle
> infrastructure to enter an idle state, which in turn creates
> a dependency that is not really needed.
>
> The PSCI checker code to test PSCI CPU suspend is built on
On Thu, Aug 01, 2019 at 04:40:20PM +0200, Vincent Guittot wrote:
> The load_balance algorithm contains some heuristics which have becomes
> meaningless since the rework of metrics and the introduction of PELT.
>
> Furthermore, it's sometimes difficult to fix wrong scheduling decisions
> because ev
On Mon, Aug 05, 2019 at 10:57:04AM -0700, Reinette Chatre wrote:
> What do you think?
Actually, I was thinking about something a lot simpler: something
along the lines of adding the CPUID check in a helper function which
rdt_pseudo_lock_init() calls. If the cache is not inclusive - and my
guess is
Any ideas or suggestions?
Best,
Tim
On Fri, Aug 2, 2019 at 1:41 AM Fang Zhou wrote:
>
> Hi all,
>
> I’m currently using Ftrace with tracepoints to trace several events in
> kernel. But I found the tracing overhead is a little high.
>
> I found the major overhead comes from
> “local_dec(&cpu_buff
On Tue, Aug 06, 2019 at 08:50:20AM -0700, Guenter Roeck wrote:
> On Mon, Aug 05, 2019 at 03:01:27PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.2.7 release.
> > There are 131 patches in this series, all will be posted as a response
> > to this one. I
Hello,
there is a serious regression in the 5.2 kernel, already fixed in 5.3-rc2 with
an ongoing request of a stable backport:
https://www.spinics.net/lists/netdev/msg590128.html
bug:
https://github.com/torvalds/linux/commit/5142967ab524eb8e5c1f6122e46e2df81bae178b
fix:
https://github.com/torv
This patch alters the for loop iteration scheme in zpci_map_resources
to make it more usual. Thus, the patch generalizes the style for
PCI_IOV_RESOURCES iteration and improves readability.
Signed-off-by: Denis Efremov
---
arch/s390/pci/pci.c | 8
1 file changed, 4 insertions(+), 4 delet
On Mon, Aug 05, 2019 at 07:06:38PM -0500, Gustavo A. R. Silva wrote:
> One of the more common cases of allocation size calculations is finding
> the size of a structure that has a zero-sized array at the end, along
> with memory for some number of elements for that array. For example:
>
> struct t
On Thu, Aug 01, 2019 at 04:40:22PM +0200, Vincent Guittot wrote:
> runnable load has been introduced to take into account the case
> where blocked load biases the load balance decision which was selecting
> underutilized group with huge blocked load whereas other groups were
> overloaded.
>
> The
> > With patch:
> > ---
> > [ 69.815453] mm/pgtable-generic.c:29: bad p4d
> 84653642(80025ca37467)
> > [ 69.815872] BUG: Bad rss-counter state mm:014a6c03
> type:MM_FILEPAGES val:2
> > [ 69.815962] BUG: Bad rss-counter state mm:014a6c03
> type:MM_ANONPAGES
On Mon, Jul 22, 2019 at 04:37:43PM +0100, Lorenzo Pieralisi wrote:
> PSCI firmware is the standard power management control for
> all ARM64 based platforms and it is also deployed on some
> ARM 32 bit platforms to date.
>
> Idle state entry in PSCI is currently achieved by calling
> arm_cpuidle_ini
On Tue, Aug 06, 2019 at 08:01:50AM +0200, Vitaly Kuznetsov wrote:
> Various intercepts hard-code the respective instruction lengths to optimize
> skip_emulated_instruction(): when next_rip is pre-set we skip
> kvm_emulate_instruction(vcpu, EMULTYPE_SKIP). The optimization is, however,
> incorrect:
> >> Without patch:
> >> --
> >> [ 204.836425] mm/pgtable-generic.c:29: bad p4d
> >> 89eb4e92(80025f941467)
> >> [ 204.836544] BUG: Bad rss-counter state mm:f75895ea idx:0
> >> val:2 [ 204.836615] BUG: Bad rss-counter state mm:f75895ea
> >> idx:1 val:5 [
On Fri, Aug 02, 2019 at 10:08:48AM +0100, Patrick Bellasi
wrote:
> +static ssize_t cpu_uclamp_write(struct kernfs_open_file *of, char *buf,
> + size_t nbytes, loff_t off,
> + enum uclamp_id clamp_id)
> +{
> + struct uclamp_request req;
>
On Fri, Aug 02, 2019 at 10:08:49AM +0100, Patrick Bellasi
wrote:
> @@ -7095,6 +7149,7 @@ static ssize_t cpu_uclamp_write(struct kernfs_open_file
> *of, char *buf,
> if (req.ret)
> return req.ret;
>
> + mutex_lock(&uclamp_mutex);
> rcu_read_lock();
>
> tg =
On Fri, Aug 02, 2019 at 10:08:47AM +0100, Patrick Bellasi
wrote:
> Patrick Bellasi (6):
> sched/core: uclamp: Extend CPU's cgroup controller
> sched/core: uclamp: Propagate parent clamps
> sched/core: uclamp: Propagate system defaults to root group
> sched/core: uclamp: Use TG's clamps to
> I think tenant will have per core weight, similar to sched entity's per
> cpu weight. The tenant's per core weight could derive from its
> corresponding taskgroup's per cpu sched entities' weight(sum them up
> perhaps). Tenant with higher weight will have its core wide vruntime
> advance slower t
On 2019-08-06 17:36, Pierre-Louis Bossart wrote:
On 8/6/19 10:27 AM, Cezary Rojewski wrote:
On 2019-08-06 02:55, Pierre-Louis Bossart wrote:
diff --git a/drivers/soundwire/cadence_master.c
b/drivers/soundwire/cadence_master.c
index 5d9729b4d634..89c55e4bb72c 100644
--- a/drivers/soundwire/ca
On Mon, Aug 5, 2019 at 11:47 PM Michal Hocko wrote:
>
> On Mon 05-08-19 20:27:03, Dan Williams wrote:
> > On Sun, Aug 4, 2019 at 10:31 PM Toshiki Fukasawa
> > wrote:
> > >
> > > On 2019/07/26 16:06, Michal Hocko wrote:
> > > > On Fri 26-07-19 06:25:49, Toshiki Fukasawa wrote:
> > > >>
> > > >>
>
On Mon, Jul 22, 2019 at 04:37:44PM +0100, Lorenzo Pieralisi wrote:
> Allow selection of the PSCI CPUidle in the kernel by adding
> the required Kconfig options.
>
> Remove PSCI callbacks from ARM/ARM64 generic CPU ops
> to prevent the PSCI idle driver from clashing with the generic
> ARM CPUidle d
On 08/05, Peter Zijlstra wrote:
>
> Re-implement percpu_rwsem without relying on rwsem.
looks correct... But,
> +bool __percpu_down_read(struct percpu_rw_semaphore *sem, bool try)
> {
> /*
>* Due to having preemption disabled the decrement happens on
>* the same CPU as the
Ivan Khoronzhuk writes:
> In case off error, all entries should be freed from the sched list
> before deleting it. For simplicity use rcu way.
>
> Fixes: 5a781ccbd19e46 ("tc: Add support for configuring the taprio scheduler")
> Signed-off-by: Ivan Khoronzhuk
> ---
Acked-by: Vinicius Costa Gomes
[trim the CC list please to keep only required maintainers]
On Mon, Jul 29, 2019 at 03:38:38PM +0800, Jianjun Wang wrote:
> On Fri, 2019-06-28 at 15:34 +0800, Jianjun Wang wrote:
> > MT7629 is an ARM platform SoC which has the same PCIe IP with MT7622.
> >
> > The HW default value of its Device I
Since architectures can implement ftrace using a variety of mechanisms,
generic code should always use CC_FLAGS_FTRACE rather than assuming that
ftrace is built using -pg.
Since commit:
2464a609ded09420 ("ftrace: do not trace library functions")
... lib/Makefile has removed CC_FLAGS_FTRACE fro
On Tue, Aug 6, 2019 at 7:36 AM Michal Hocko wrote:
>
> On Tue 06-08-19 10:27:28, Johannes Weiner wrote:
> > On Tue, Aug 06, 2019 at 11:36:48AM +0200, Vlastimil Babka wrote:
> > > On 8/6/19 3:08 AM, Suren Baghdasaryan wrote:
> > > >> @@ -1280,3 +1285,50 @@ static int __init psi_proc_init(void)
> >
On 01/08/2019 19:35, Alexei Starovoitov wrote:
> On Wed, Jul 31, 2019 at 09:11:10PM +0200, Mickaël Salaün wrote:
>>
>>
>> On 31/07/2019 20:58, Alexei Starovoitov wrote:
>>> On Wed, Jul 31, 2019 at 11:46 AM Mickaël Salaün
>>> wrote:
>> +for (i = 0; i < htab->n_buckets; i++) {
>> +
On Fri, Jun 14, 2019 at 12:10:59PM +0200, Remi Pommarel wrote:
> PCI_EXP_RTCTL is used to activate PME interrupt only, so writing into it
> should not modify other interrupts' mask. The ISR mask polarity was also
> inverted, when PCI_EXP_RTCTL_PMEIE is set PCIE_MSG_PM_PME_MASK mask bit
> should act
From: Josef Friedl
add entry for rtc and power-controller to mt6323
Signed-off-by: Josef Friedl
Signed-off-by: Frank Wunderlich
---
changes since v3: none
changes since v2: only splitting, second part of v2 part 4
drivers/mfd/mt6397-core.c | 25 +
1 file changed, 25 i
From: Josef Friedl
move code to separate header-file to reuse definitions later
in poweroff-driver (drivers/power/reset/mt6323-poweroff.c)
Suggested-by: Frank Wunderlich
Signed-off-by: Josef Friedl
Signed-off-by: Frank Wunderlich
---
changes since v3: none
changes since v2: add missing commit
From: Josef Friedl
use mt6397 rtc driver also for mt6323 but with different
base/size see "mfd: mt6323: add mt6323 rtc+pwrc"
Signed-off-by: Josef Friedl
Signed-off-by: Frank Wunderlich
---
changes since v3: moved (was part 5)
changes since v2: splitted this from v2.3 suggested-by Alexandre Bel
From: Josef Friedl
add poweroff driver for mt6323 and make Makefile and Kconfig-Entries
Suggested-by: Frank Wunderlich
Signed-off-by: Josef Friedl
Signed-off-by: Frank Wunderlich
---
changes since v3: none
changes since v2: none (=v2 part 5)
drivers/power/reset/Kconfig | 10 +++
d
From: Josef Friedl
simplyfications (resource definitions my DEFINE_RES_* macros)
Signed-off-by: Josef Friedl
Signed-off-by: Frank Wunderlich
---
changes since v3: moved part 6 forward to let compatible and driver be together
changes since v2: splitted v2 part 4 into 6+7
drivers/mfd/mt6397-co
From: Josef Friedl
add mt6323-rtc and mt6323-pwrc to mt6397 mfd DT bindings
an example is shown in mt6323-poweroff.txt
Suggested-by: Frank Wunderlich
Signed-off-by: Josef Friedl
Signed-off-by: Frank Wunderlich
---
changes since v3: none
changes since v2: separated rtc-mt6397.txt to part 2
.
mainline-driver does not support mt6323
this series makes some cleanup to mt6397-rtc-driver, adds mt6323 and
implement power-controller on it.
tested on bananapi-r2
Original Patch from Josef Friedl
changes since v3:
- moved SOB in 2/10 and 9/10
- moved part 5 to 6 to be near dri
From: Josef Friedl
- use regmap_read_poll_timeout to drop while-loop
- use devm-api to drop remove-callback
Suggested-by: Alexandre Belloni
Signed-off-by: Josef Friedl
Signed-off-by: Frank Wunderlich
---
changes since v3: none
changes since v2:
- fix allocation after irq-request
- compatible
From: Josef Friedl
add missing devicetree-binding document for mt6397 rtc
in later patch driver is extended with mt6323 chip
Suggested-By: Alexandre Belloni
Signed-off-by: Josef Friedl
Signed-off-by: Frank Wunderlich
---
changes since v3: moved SOB
changes since v2: splitted rtc-mt6397.txt fr
The code is supposed to clear several fields in the structure with
memset() and it produces the warning:
In file included from arch/x86/kernel/head64.c:17:
In function ‘memset’,
inlined from ‘sanitize_boot_params’ at
./arch/x86/include/asm/bootparam_utils.h:40:3,
inlined from ‘copy_bootda
On 8/5/19 8:05 PM, Sai Praneeth Prakhya wrote:
> +static const char * const resident_page_types[NR_MM_COUNTERS] = {
> + [MM_FILEPAGES] = "MM_FILEPAGES",
> + [MM_ANONPAGES] = "MM_ANONPAGES",
> + [MM_SWAPENTS] = "MM_SWAPENTS",
> + [MM_SHMEMPAGES] =
On Mon, Aug 5, 2019 at 12:27 PM Konstantin Ryabitsev
wrote:
>
> On Mon, Aug 05, 2019 at 12:17:49PM -0700, Linus Torvalds wrote:
> >> However, I suspect that getting message-ids for all your pull
> >> requests
> >> would significantly complicate your workflow.
> >
> >Yeah, that would be a noticeabl
On Tue, Aug 6, 2019 at 7:35 AM Mark Rutland wrote:
>
> On Tue, Aug 06, 2019 at 07:11:41AM -0700, Rob Clark wrote:
> > On Tue, Aug 6, 2019 at 1:48 AM Christoph Hellwig wrote:
> > >
> > > This goes in the wrong direction. drm_cflush_* are a bad API we need to
> > > get rid of, not add use of it.
On Mon, Jul 29, 2019 at 03:38:38PM +0800, Jianjun Wang wrote:
> On Fri, 2019-06-28 at 15:34 +0800, Jianjun Wang wrote:
> > MT7629 is an ARM platform SoC which has the same PCIe IP with MT7622.
> >
> > The HW default value of its Device ID is invalid, fix its Device ID to
> > match the hardware imp
On Tue, Aug 06, 2019 at 05:10:33PM +0100, Sudeep Holla wrote:
> On Mon, Jul 22, 2019 at 04:37:43PM +0100, Lorenzo Pieralisi wrote:
> > PSCI firmware is the standard power management control for
> > all ARM64 based platforms and it is also deployed on some
> > ARM 32 bit platforms to date.
> >
> > I
On Tue, 6 Aug 2019 11:48:11 -0400
Joel Fernandes wrote:
> > diff --git a/arch/arm64/include/asm/ftrace.h
> > b/arch/arm64/include/asm/ftrace.h
> > index 5ab5200b2bdc..13a4832cfb00 100644
> > --- a/arch/arm64/include/asm/ftrace.h
> > +++ b/arch/arm64/include/asm/ftrace.h
> > @@ -13,6 +13,7 @@
>
From: Josef Friedl
support poweroff and power-related keys on bpi-r2
Suggested-by: Frank Wunderlich
Signed-off-by: Josef Friedl
Signed-off-by: Frank Wunderlich
---
changes since v3: none
changes since v2: none (=v2 part 7)
arch/arm/boot/dts/mt6323.dtsi | 27 +++
1 fi
From: Josef Friedl
add Section in MAINTAINERS file for poweroff driver
Signed-off-by: Josef Friedl
Signed-off-by: Frank Wunderlich
---
changes since v3: moved SOB
changes since v2: none (=v2 part 6)
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAIN
On Tue, Aug 06, 2019 at 17:12:06 +0100, Michal Koutný wrote...
> On Fri, Aug 02, 2019 at 10:08:47AM +0100, Patrick Bellasi
> wrote:
>> Patrick Bellasi (6):
>> sched/core: uclamp: Extend CPU's cgroup controller
>> sched/core: uclamp: Propagate parent clamps
>> sched/core: uclamp: Propagat
On Tue, Aug 06, 2019 at 05:16:24PM +0100, Sudeep Holla wrote:
> On Mon, Jul 22, 2019 at 04:37:44PM +0100, Lorenzo Pieralisi wrote:
> > Allow selection of the PSCI CPUidle in the kernel by adding
> > the required Kconfig options.
> >
> > Remove PSCI callbacks from ARM/ARM64 generic CPU ops
> > to p
Hello Dan,
On 06/08/2019 15.52, Dan Carpenter wrote:
On Fri, Aug 02, 2019 at 10:10:20AM +0200, Oliver Hartkopp wrote:
Btw. what kind of compiler/make switches are you using so that I can see
these warnings myself the next time?
These are Sparse warnings, not from GCC.
I compiled the code
On 05/08/2019 01:55, Andy Lutomirski wrote:
> On Wed, Dec 12, 2018 at 6:43 AM Jan Kara wrote:
>>
>> On Wed 12-12-18 09:17:08, Mickaël Salaün wrote:
>>> When the O_MAYEXEC flag is passed, sys_open() may be subject to
>>> additional restrictions depending on a security policy implemented by an
>>>
Hi Thomas,
On 7/15/19 11:43 AM, Thomas Gleixner wrote:
> On Thu, 11 Jul 2019, Hoan Tran OS wrote:
>
>> Remove CONFIG_NODES_SPAN_OTHER_NODES as it's enabled
>> by default with NUMA.
>
> As I told you before this does not mention that the option is now enabled
> even for x86(32bit) configurations
Hi Andy,
On 8/5/19 11:41 PM, Andy Shevchenko wrote:
On Tue, Aug 6, 2019 at 2:37 AM Steve Longerbeam wrote:
There is nothing v4l2-specific about v4l2_fwnode_{parse|put}_link().
Make these functions more generally available by moving them to driver
base, with the appropriate name changes to the
Hi Borislav,
On 8/6/2019 8:57 AM, Borislav Petkov wrote:
> On Mon, Aug 05, 2019 at 10:57:04AM -0700, Reinette Chatre wrote:
>> What do you think?
>
> Actually, I was thinking about something a lot simpler: something
> along the lines of adding the CPUID check in a helper function which
> rdt_pseu
SCMI v2.0 adds support for "FastChannel", a lightweight unidirectional
channel that is dedicated to a single SCMI message type for controlling
a specific platform resource. They do not use a message header as they
are specialized for a single message.
Only PERFORMANCE_LIMITS_{SET,GET} and PERFORMA
SCMI v2.0[1] released recently adds support for:
1. Performance protocol fast channels
2. Reset Management Protocol
among several other features.
This series adds support for the above 2.
The code is based on the cleanup[2] and Rx/async/delayed response series[3]
and is available @[4]
--
Regard
On some ARM based systems, a separate Cortex-M based System Control
Processor(SCP) provides the overall power, clock, reset and system
control. System Control and Management Interface(SCMI) Message Protocol
is defined for the communication between the Application Cores(AP)
and the SCP.
Adds suppor
SCMIv2.0 adds a new Reset Management Protocol to manage various reset
states a given device or domain can enter. Extend the existing SCMI
bindings to add reset protocol support by re-using the reset bindings
for bothe reset providers and consumers.
Cc: Philipp Zabel
Cc: Rob Herring
Cc: Mark Rutl
SCMI v2.0 adds support for "FastChannel" which do not use a message
header as they are specialized for a single message.
Only PERFORMANCE_LIMITS_{SET,GET} and PERFORMANCE_LEVEL_{SET,GET}
commands are supported over fastchannels. As they are optional, they
need to be discovered by PERFORMANCE_DESCR
SCMIv2.0 adds a new Reset Management Protocol to manage various reset
states a given device or domain can enter. Device(s) that can be
collectively reset through a common reset signal constitute a reset
domain for the firmware.
A reset domain can be reset autonomously or explicitly through asserti
On Tue, 6 Aug 2019 12:34:55 -0400
Steven Rostedt wrote:
> Here's the best way to explain this. The code is using the stack trace
> to figure out which function is the stack hog. Or perhaps a serious of
Why so serious? s/serious/series/
-- Steve
> stack hogs. On x86, a call stores the re
On 8/5/19 8:24 PM, Aaron Lu wrote:
> I've been thinking if we should consider core wide tenent fairness?
>
> Let's say there are 3 tasks on 2 threads' rq of the same core, 2 tasks
> (e.g. A1, A2) belong to tenent A and the 3rd B1 belong to another tenent
> B. Assume A1 and B1 are queued on the sa
Hello Geert,
On 8/6/19 9:22 AM, Geert Uytterhoeven wrote:
> Hi Javier,
>
> On Tue, Aug 6, 2019 at 12:25 AM Javier Martinez Canillas
> wrote:
>> On 7/31/19 9:44 PM, Wolfram Sang wrote:
>>> Hi Javier,
The other option is to remove i2c_of_match_device() and don't make OF match
to fallback
On Tue, Aug 06, 2019 at 10:03:29AM -0700, Tim Chen wrote:
> On 8/5/19 8:24 PM, Aaron Lu wrote:
>
> > I've been thinking if we should consider core wide tenent fairness?
> >
> > Let's say there are 3 tasks on 2 threads' rq of the same core, 2 tasks
> > (e.g. A1, A2) belong to tenent A and the 3rd
Hi Chen-Yu,
On Tue, 6 Aug 2019 15:53:25 +0800, Chen-Yu Tsai wrote:
> From: Chen-Yu Tsai
>
> With the recent addition of commit 75dad2520fc3 ("net: dsa: b53: Disable
> all ports on setup"), users of b53 (BCM53125 on Lamobo R1 in my case)
> are forced to use the dsa subsystem to enable the switc
On Tue, Aug 06, 2019 at 06:17:42PM +0200, Oleg Nesterov wrote:
> but this will also wake all the pending readers up. Every reader will burn
> CPU for no reason and likely delay the writer.
>
> In fact I'm afraid this can lead to live-lock, because every reader in turn
> will call __percpu_up_read
Second batch, get it while it's hot...
On 01/08/2019 15:40, Vincent Guittot wrote:
[...]
> @@ -7438,19 +7453,53 @@ static int detach_tasks(struct lb_env *env)
> if (!can_migrate_task(p, env))
> goto next;
>
> - load = task_h_load(p);
> +
On Tue, Aug 06, 2019 at 12:34:55PM -0400, Steven Rostedt wrote:
> On Tue, 6 Aug 2019 11:48:11 -0400
> Joel Fernandes wrote:
>
>
> > > diff --git a/arch/arm64/include/asm/ftrace.h
> > > b/arch/arm64/include/asm/ftrace.h
> > > index 5ab5200b2bdc..13a4832cfb00 100644
> > > --- a/arch/arm64/include
add_to_kill() expects the first 'tk' to be pre-allocated, it makes
subsequent allocations on need basis, this makes the code a bit
difficult to read. Move all the allocation internal to add_to_kill()
and drop the **tk argument.
Signed-off-by: Jane Chu
---
mm/memory-failure.c | 40 +--
Change in v4:
- remove trailing white space
Changes in v3:
- move **tk cleanup to its own patch
Changes in v2:
- move 'tk' allocations internal to add_to_kill(), suggested by Dan;
- ran checkpatch.pl check, pointed out by Matthew;
- Noaya pointed out that v1 would have missed the SIGKILL
Hi, Naoya,
Thanks a lot! v4 on the way. :)
-jane
On 8/1/2019 2:06 AM, Naoya Horiguchi wrote:
On Thu, Jul 25, 2019 at 04:01:40PM -0600, Jane Chu wrote:
add_to_kill() expects the first 'tk' to be pre-allocated, it makes
subsequent allocations on need basis, this makes the code a bit
difficult
Mmap /dev/dax more than once, then read the poison location using address
from one of the mappings. The other mappings due to not having the page
mapped in will cause SIGKILLs delivered to the process. SIGKILL succeeds
over SIGBUS, so user process looses the opportunity to handle the UE.
Although
On 8/6/19 7:07 AM, Denis Efremov wrote:
It's a general pattern to write loops with 'i < PCI_SRIOV_NUM_BARS'
condition. This patch fixes remaining loops which violates this implicit
agreement.
Looks good to me.
Reviewed-by: Kuppuswamy Sathyanarayanan
Signed-off-by: Denis Efremov
---
On Thu, 1 Aug 2019 20:26:03 +0300
Todor Tomov wrote:
> My @linaro.org email address doesn't exist anymore so add a
> mailmap entry to map it to my @gmail.com address.
>
> Signed-off-by: Todor Tomov
I've applied this, but I'm still not convinced that all of these .mailmap
entries are really ne
401 - 500 of 1002 matches
Mail list logo
