On 6/22/2018 6:41 AM, Ezequiel Garcia wrote:
Hey Enric,
On Fri, 2018-06-22 at 00:04 +0200, Enric Balletbo i Serra wrote:
When the devfreq driver and the governor driver are built as modules,
the call to devfreq_add_device() or governor_store() fails because
the
governor driver is not loaded
With gcc 4.1.2 when compiling for 32-bit:
drivers/mtd/devices/mtd_dataflash.c:736: warning: integer constant is too
large for ‘long’ type
drivers/mtd/devices/mtd_dataflash.c:737: warning: integer constant is too
large for ‘long’ type
Add the missing "ULL" suffixes to fix this.
Fixes:
Hi Geert,
On 22/06/18 16:35, Geert Uytterhoeven wrote:
On Fri, Jun 22, 2018 at 2:20 AM Greg Ungerer wrote:
On 22/06/18 06:30, Geert Uytterhoeven wrote:
If DEBUG_DMA is defined:
include/asm/dma.h: In function ‘set_dma_mode’:
include/asm/dma.h:393: error: ‘dmabp’ undeclared (first
We use per-cgroup cpu usage statistics similar to "cgroup rstat",
and encountered a problem that user and sys usages are wrongly
split sometimes.
Run tasks with some random run-sleep pattern for a long time, and
when tick-based time and scheduler sum_exec_runtime hugely drifts
apart(scheduler
On Fri, Jun 22, 2018 at 4:27 AM, Stephen Boyd wrote:
> Use devm here to save some lines and prepare for bulk regulator usage in
> this driver. Otherwise, when we devm bulk get regulators we'll free the
> containing i2c_hid structure and try to put regulator pointers from
> freed memory.
>
> Cc:
Hi Alexei,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 1cfea546b10c8fec218973c3f3c39ff797a3e50c
commit: 819dd92b9c0bc7bce9097d8c1f14240f471bb386 bpfilter: switch to CC from
HOSTCC
date: 2 weeks ago
config:
* Pavel Machek [180621 12:18]:
> Hi!
>
> V4.18 is slower than it should be.
>
> user@devuan:~$ time cat /dev/urandom | head -c 1000 | bzip2 -9 -
> | wc -c
> 10044291
> 52.73user 2.40system 61.53 (1m1.534s) elapsed 89.60%CPU
> user@devuan:~$ uname -a
> Linux devuan
ping ?
On Thu, Mar 8, 2018 at 9:29 PM Mathieu Malaterre wrote:
>
> The inline keyword was not at the beginning of the function declaration.
> Fix the following warning (reported at W=1)
>
> CC kernel/events/ring_buffer.o
> kernel/events/ring_buffer.c:105:1: warning: ‘inline’ is not at
On Thu, Jun 21, 2018 at 11:55 PM, Naoya Horiguchi
wrote:
> On Thu, Jun 21, 2018 at 11:12:01PM -0700, Dan Williams wrote:
>> On Thu, Jun 21, 2018 at 11:08 PM, Naoya Horiguchi
>> wrote:
>> > Reading /proc/kpageflags for pfns allocated by pmem namespace triggers
>> > kernel panic with a message
Hi Piotr,
On Fri, 22 Jun 2018 07:57:10 +0200 (CEST)
Piotr Bugalski wrote:
> Hi Boris,
>
> I'm a bit allergic to personal preferences in coding style,
I'm just pointing things that are common kernel coding style practices.
You might not like coding style rules of a particular project, but when
On 21 June 2018 at 21:09, Paweł Chmiel wrote:
> This DTS file have initial support Samsung Aries based phones.
> Initial version have support for:
> - sdcard
> - internal memory (present only on non 4g variant)
> - max8998 pmic and rtc
> - max17040 fuel gauge
> - gpio keys
> - fimd (no panel
On Wed, Jun 20, 2018 at 11:30:55AM +0200, Emmanuel Vadot wrote:
> The card detect GPIO for Sopine and Pine64-LTS is PF6.
> Add this to the dts.
>
> Signed-off-by: Emmanuel Vadot
Applied, thanks!
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
On Thu 21-06-18 13:50:53, David Rientjes wrote:
> On Thu, 21 Jun 2018, Michal Hocko wrote:
>
> > > > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> > > > index 6bcecc325e7e..ac08f5d711be 100644
> > > > --- a/arch/x86/kvm/x86.c
> > > > +++ b/arch/x86/kvm/x86.c
> > > > @@ -7203,8 +7203,9 @@
Hi Steve,
On Thu, Jun 21, 2018 at 08:35:26PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt (VMware)
>
> One of my tests compiles the kernel with gcc 4.5.3, and I hit the
> following build error:
>
> /work/git/linux-trace.git/include/linux/semaphore.h: In function 'sema_init':
>
* Tony Lindgren [180622 07:22]:
> * Pavel Machek [180621 12:18]:
> > Hi!
> >
> > V4.18 is slower than it should be.
> >
> > user@devuan:~$ time cat /dev/urandom | head -c 1000 | bzip2 -9 -
> > | wc -c
> > 10044291
> > 52.73user 2.40system 61.53 (1m1.534s) elapsed 89.60%CPU
> >
On 21 June 2018 at 21:09, Paweł Chmiel wrote:
> Signed-off-by: Paweł Chmiel
Please add commit message. This can be something as simple as "Add
Samsung Galaxy S DTS which is a commercial phone based on Aries
family." or something more (e.g. describe what is working).
> ---
>
Hi Alan,
inline comments
On Friday, 22 June 2018 04:07:41 CEST Alan Tull wrote:
> On Thu, Jun 21, 2018 at 8:13 AM, Federico Vaga
> wrote:
>
> Hi Federico,
>
> Thanks for the analysis. I'll probably not be able to look into
> this very much until next week. A few notes below.
>
> > Hello,
>
On 21 June 2018 at 21:09, Paweł Chmiel wrote:
> Enable config options required for Samsung Aries based phones..
Two dots.
> While we're here, also enable other useful options like:
Please split it. One set of changes needed for Aries and second set of
other useful changes with short
For the common cases where 1000 is a multiple of HZ, or HZ is a multiple
of 1000, jiffies_to_msecs() never returns zero when passed a non-zero
time period.
However, if HZ > 1000 and not an integer multiple of 1000 (e.g. 1024 or
1200, as used on alpha and DECstation), jiffies_to_msecs() may return
On 21 June 2018 at 21:09, Paweł Chmiel wrote:
> Signed-off-by: Paweł Chmiel
> ---
> Documentation/devicetree/bindings/arm/samsung/samsung-boards.txt | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/samsung/samsung-boards.txt
>
On 22 June 2018 at 09:56, Krzysztof Kozlowski wrote:
> On 21 June 2018 at 21:09, Paweł Chmiel wrote:
>> Signed-off-by: Paweł Chmiel
... and commit msg please.
BR,
Krzysztof
>> ---
>> Documentation/devicetree/bindings/arm/samsung/samsung-boards.txt | 2 ++
>> 1 file changed, 2 insertions(+)
On 21 June 2018 at 21:09, Paweł Chmiel wrote:
> From: Jonathan Bakker
Commit msg needed.
> Signed-off-by: Jonathan Bakker
> Signed-off-by: Paweł Chmiel
> ---
> arch/arm/boot/dts/Makefile| 1 +
> arch/arm/boot/dts/s5pv210-fascinate4g.dts | 40
>
On 21/06/18 20:45, Peter Zijlstra wrote:
> On Fri, Jun 08, 2018 at 02:09:47PM +0200, Vincent Guittot wrote:
> > static unsigned long sugov_aggregate_util(struct sugov_cpu *sg_cpu)
> > {
> > struct rq *rq = cpu_rq(sg_cpu->cpu);
> > + unsigned long util;
> >
> > if
Hi Peter,
On Thursday 21 Jun 2018 at 20:45:24 (+0200), Peter Zijlstra wrote:
> On Fri, Jun 08, 2018 at 02:09:47PM +0200, Vincent Guittot wrote:
> > static unsigned long sugov_aggregate_util(struct sugov_cpu *sg_cpu)
> > {
> > struct rq *rq = cpu_rq(sg_cpu->cpu);
> > + unsigned long util;
On 21 June 2018 at 21:09, Paweł Chmiel wrote:
> From: Jonathan Bakker
>
Commit msg.
Best regards,
Krzysztof
> Signed-off-by: Jonathan Bakker
> Signed-off-by: Paweł Chmiel
> ---
> Documentation/devicetree/bindings/arm/samsung/samsung-boards.txt | 1 +
> 1 file changed, 1 insertion(+)
>
>
On Thu, Jun 21, 2018 at 11:15:48PM +, yang@linux.alibaba.com wrote:
> When merging anonymous page vma, if the size of vma can fit in at least
> one hugepage, the mm will be registered for khugepaged for collapsing
> THP in the future.
>
> But, it skips shmem vma. Doing so for shmem too,
On Thu, Jun 21, 2018 at 11:15:49PM +, yang@linux.alibaba.com wrote:
> /sys/kernel/mm/transparent_hugepage/khugepaged/pages_collapsed is used
> to record the counter of collapsed THP, but it just gets inc'ed in
> anonymous THP collapse path, do this for shmem THP collapse too.
>
>
Hi Hugo,
thank you for all your work on Pi433 driver.
For a better understanding some info about Pi433 and the ideas behind it.
Pi433 was developed by me in order to have a simple to mount
CE-compliant 433MHz shield for the Raspberry Pi. I wanted to put it on
sale on the one side and develop a
SPDX license helps developers and machines to know the license governing
a particular file hence easing work
Signed-off-by: Mawanda Henry
---
drivers/bus/arm-cci.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/drivers/bus/arm-cci.c b/drivers/bus/arm-cci.c
index
perf stat command line flag -T to display transaction counters is
currently supported for x86 only.
Add support for s390. It is based on the metrics flag -M transaction
using the architecture dependend json files This requires a metric
named transaction in the json files for the platform.
As
If there is millions of discard entries cached in rb tree, each
sanity check of it can cause very long latency as held cmd_lock
blocking other lock grabbers.
In other aspect, we have enabled the check very long time, as
we see, there is no such inconsistent condition caused by bugs.
But still we
On Thu, Jun 21, 2018 at 08:34:40PM -0700, Paul E. McKenney wrote:
> (Peter, if you meant to ack both, please let me know.)
I sadly have not had the time to go through all that fancy cat language
stuff, so while I can read and mostly understand the Changelog, I don't
feel qualified to actually say
Hi Alan,
On Thu, Jun 21, 2018 at 01:27:12PM -0400, Alan Stern wrote:
> More than one kernel developer has expressed the opinion that the LKMM
> should enforce ordering of writes by release-acquire chains and by
> locking. In other words, given the following code:
>
> WRITE_ONCE(x, 1);
>
On Thu, Jun 21, 2018 at 10:21:44PM +0200, Thomas Gleixner wrote:
> On Thu, 24 May 2018, Lukas Wunner wrote:
> > static int irq_wait_for_interrupt(struct irqaction *action)
> > {
> > - set_current_state(TASK_INTERRUPTIBLE);
> > + for (;;) {
> > +
The hardware core can not be built as a module, so remove the redundant
CONFIG_HWSPINLOCK_MODULE config.
Signed-off-by: Baolin Wang
---
include/linux/hwspinlock.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/hwspinlock.h b/include/linux/hwspinlock.h
index
The hardware spinlock binding already supplied the 'hwlock-names' property
to match and get a specific hwlock, but did not supply one API for users
to get a specific hwlock by the hwlock name. So this patch introduces one
API to support this requirement.
Signed-off-by: Baolin Wang
---
Use devm_hwspin_lock_register() to register the hwlock controller to
avoid unregistering the device explicitly.
Signed-off-by: Baolin Wang
---
drivers/hwspinlock/sprd_hwspinlock.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/hwspinlock/sprd_hwspinlock.c
On Thu, 21 Jun 2018 at 20:57, Peter Zijlstra wrote:
>
> On Thu, Jun 21, 2018 at 08:45:24PM +0200, Peter Zijlstra wrote:
> > On Fri, Jun 08, 2018 at 02:09:47PM +0200, Vincent Guittot wrote:
> > > static unsigned long sugov_aggregate_util(struct sugov_cpu *sg_cpu)
> > > {
> > > struct rq *rq
Change to use devm_hwspin_lock_request_specific() instead of
freeing the hwlock explicitly when unbound the device.
Signed-off-by: Baolin Wang
---
drivers/spi/spi-sprd-adi.c |9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/spi/spi-sprd-adi.c
Now the hwlock core has supplied new function to get a specific hwlock id
by one hwlock name, which is more clear for users. So change to use
of_hwspin_lock_get_id_byname().
Signed-off-by: Baolin Wang
---
drivers/spi/spi-sprd-adi.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Hi Andrea,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on net-next/master]
[also build test ERROR on v4.18-rc1 next-20180622]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
On Thu, Jun 21, 2018 at 03:42:03PM -0700, Fenghua Yu wrote:
> On Thu, Jun 21, 2018 at 03:18:19PM -0700, Dave Hansen wrote:
> > On 06/21/2018 03:08 PM, Peter Zijlstra wrote:
> > > On Thu, Jun 21, 2018 at 03:00:03PM -0700, Fenghua Yu wrote:
> > >> The control knob for kernel is to choose
On 06/22/2018 04:36 AM, Andi Kleen wrote:
> Thomas Richter writes:
>>
>> +/* Handle -T as -M transaction. Once platform specific metrics
>> + * support has been added to the json files, all archiectures
>> + * will use this approach.
>> + */
>> +
Fix one comment mistake with correct function names.
Signed-off-by: Baolin Wang
---
drivers/hwspinlock/hwspinlock_core.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/hwspinlock/hwspinlock_core.c
b/drivers/hwspinlock/hwspinlock_core.c
index ba27465..e16d648
This patch introduces devm_hwspin_lock_register() and
devm_hwspin_lock_unregister()
interfaces to help to register or unregister one hardware spinlock controller,
that
will help to simplify the cleanup code for hwspinlock drivers.
Signed-off-by: Baolin Wang
---
Hi Heiko,
在 2018年06月22日 15:30, Heiko Stuebner 写道:
Hi David,
Am Mittwoch, 20. Juni 2018, 04:40:35 CEST schrieb David Wu:
在 2018年06月14日 16:30, Heiko Stübner 写道:
Am Donnerstag, 14. Juni 2018, 10:14:31 CEST schrieb David Wu:
Hi Heiko,
在 2018年06月14日 15:54, Heiko Stübner 写道:
I don't see that
This patch introduces some devm_xxx() APIs to help to request or free
the hwlocks, which will help to simplify the cleanup code for drivers
requesting one hwlock, ensuring that the hwlock is automatically freed
whenever the device is unbound.
Signed-off-by: Baolin Wang
---
Hi Ard,
On Thu, Jun 21, 2018 at 07:27:01PM +0200, Ard Biesheuvel wrote:
> On 21 June 2018 at 19:04, James Morse wrote:
> > On 21/06/18 10:29, Ard Biesheuvel wrote:
> >> On 21 June 2018 at 10:59, James Morse wrote:
> >>> On 21/06/18 07:39, Ard Biesheuvel wrote:
> On 21 June 2018 at 04:51,
Hello RT Folks!
I'm pleased to announce the 4.4.138-rt155 stable release.
This release is just an update to the new stable 4.4.137 version
and no RT specific changes have been made.
As turns out, it is not a ghost I am hunting:
On Thu, Jun 21, 2018 at 04:05:02PM -0700, Fenghua Yu wrote:
> But in a real case, when I enable #AC for split lock in kernel, reboot
> hits #AC because of split lock in firmware code and firmware handles #AC
> as fatal error and stops continuing to run.
>
> It will take long time/forever for
On Fri, Jun 22, 2018 at 9:54 AM, Geert Uytterhoeven
wrote:
> For the common cases where 1000 is a multiple of HZ, or HZ is a multiple
> of 1000, jiffies_to_msecs() never returns zero when passed a non-zero
> time period.
>
> However, if HZ > 1000 and not an integer multiple of 1000 (e.g. 1024 or
Hi Morten,
On Wednesday 20 Jun 2018 at 10:05:41 (+0100), Morten Rasmussen wrote:
> +static void update_asym_cpucapacity(int cpu)
> +{
> + int enable = false;
> +
> + rcu_read_lock();
> + if (lowest_flag_domain(cpu, SD_ASYM_CPUCAPACITY))
> + enable = true;
> +
Hi Ezequiel and Akhil,
On 22/06/18 09:03, Akhil P Oommen wrote:
>
> On 6/22/2018 6:41 AM, Ezequiel Garcia wrote:
>> Hey Enric,
>>
>> On Fri, 2018-06-22 at 00:04 +0200, Enric Balletbo i Serra wrote:
>>> When the devfreq driver and the governor driver are built as modules,
>>> the call to
On Thu, 2018-06-21 at 22:08 -0700, Scott Branden wrote:
>
>
> On 18-06-21 09:54 AM, Lorenzo Pieralisi wrote:
> >
> >
> > On Wed, Jun 20, 2018 at 10:07:33AM +0200, Jan Kiszka wrote:
> > >
> > >
> > > On 2018-06-19 13:21, Lorenzo Pieralisi wrote:
> > > >
> > > >
> > > > Commit 51bc085d6454
Hi Will,
On 2018/6/21 11:54, Will Deacon wrote:
> Hi Wei,
>
> On Thu, Jun 21, 2018 at 11:14:28AM +0100, Wei Xu wrote:
>> On 2018/6/21 10:18, Will Deacon wrote:
>>> On Thu, Jun 21, 2018 at 09:38:53AM +0100, James Morse wrote:
On 20/06/18 17:25, Wei Xu wrote:
> [0.042421]
On Fri, 22 Jun 2018 13:28:34 +1200
Chris Packham wrote:
> Micron MT29F1G08ABAFAWP-ITE:F supports an on-die ECC with 8 bits
> per 512 bytes. Add support for this combination.
>
> Signed-off-by: Chris Packham
Reviewed-by: Boris Brezillon
> ---
>
> Notes:
> Changes in v2:
> - New
>
Hi Byungchul,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on rcu/rcu/next]
[also build test WARNING on v4.18-rc1 next-20180622]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com
On Fri, 22 Jun 2018 13:28:35 +1200
Chris Packham wrote:
> Some Micron NAND chips have on-die ECC forceably enabled. The detect
^ Detect ?
> these based on chip ID as there seems to be no other way of
> distinguishing these chips from
On Fri 15-06-18 17:52:21, ufo19890...@gmail.com wrote:
> From: yuzhoujian
>
> Some users complains that system-wide oom report does not print memcg's
> name which contains the task killed by the oom-killer. The current system
> wide oom report prints the task's command, gfp_mask, order
Hi, Marc
Current system only supports (NR_IRQS + 8196) interrupts. It's not
enough on ARM64
server, on D06 we have several pcie devices and each device supports 256
VMs and each
VM uses 64 interrupts. Can we set NR_IRQS to a bigger value to support
more interrupts ?
Thanks,
Yang
On Friday, June 22, 2018 9:49:42 AM CEST Krzysztof Kozlowski wrote:
> On 21 June 2018 at 21:09, Paweł Chmiel wrote:
> > Signed-off-by: Paweł Chmiel
>
> Please add commit message. This can be something as simple as "Add
> Samsung Galaxy S DTS which is a commercial phone based on Aries
> family."
Erase white spaces to ease code readability and review
used: checkpatch.pl
Signed-off-by: Mawanda Henry
---
drivers/bus/arm-cci.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/bus/arm-cci.c b/drivers/bus/arm-cci.c
index 74a2e0a..ab04201 100644
---
On Thu, Jun 21, 2018 at 10:03:45PM -0400, Hugo Lefeuvre wrote:
> I'll prepare a patch addressing both issues. However I don't own test devices
> so it would be really great if you could test it !
I have two pi433 devices now so I should be able to tests things,
just let me know...
--
Valentin
On Thu, Jun 21, 2018 at 1:29 AM, Joel Fernandes wrote:
> Also if you look at the kernel sources, there are dozens of drivers that
> check for correct VMA size in mmap handler and fail if it isn't sized
> correctly.
If that's the case, we should definitely do it this way for ashmem as
well. Since
On Wed 20-06-18 20:35:15, Matthew Wilcox wrote:
> On Thu, Jun 21, 2018 at 11:02:58AM +0800, Jia-Ju Bai wrote:
> > The kernel may sleep with holding a spinlock.
> > The function call path (from bottom to top) in Linux-4.16.7 is:
> >
> > [FUNC] schedule
> > lib/percpu-refcount.c, 222:
> >
On 22 June 2018 at 10:42, Paweł Chmiel wrote:
> On Friday, June 22, 2018 9:49:42 AM CEST Krzysztof Kozlowski wrote:
>> On 21 June 2018 at 21:09, Paweł Chmiel
>> wrote:
>> > Signed-off-by: Paweł Chmiel
>>
>> Please add commit message. This can be something as simple as "Add
>> Samsung Galaxy S
On Thu, Jun 21, 2018 at 01:26:49PM -0400, Alan Stern wrote:
> This patch changes the LKMM rule which says that an acquire which
> reads from an earlier release must be executed after that release (in
> other words, the release cannot be forwarded to the acquire). This is
> not true on PowerPC,
Hi Thierry,
> This commit adds support for KOE's 5.7" display.
>
> Signed-off-by: Lukasz Majewski
> Reviewed-by: Rob Herring
> ---
> Changes for v2:
> - Add Reviewed-by tag
Could you apply this patch to your tree?
Thanks in advance,
Łukasz
>
> ---
>
The commit 5d9f40b56630 ("platform/x86: ideapad-laptop: Add
Y520-15IKBN to no_hw_rfkill") added the entry for Y20-15IKBN, and it
turned out that another variant, Y20-15IKBM, also requires the
no_hw_rfkill.
Trim the last letter from the string so that it matches to both
Y20-15IKBN and Y20-15IKBM
Hi Mathieu,
On 21/06/18 18:13, Mathieu Poirier wrote:
+
+/*
+ * catu_populate_table : Populate the given CATU table.
+ * The table is always populated as a circular table.
+ * i.e, the "prev" link of the "first" table points to the "last"
+ * table and the "next" link of the "last" table
Commit-ID: 52e1cf2d19c2e62e6a81b8de3f7320d033917dd5
Gitweb: https://git.kernel.org/tip/52e1cf2d19c2e62e6a81b8de3f7320d033917dd5
Author: Hans de Goede
AuthorDate: Fri, 22 Jun 2018 08:42:22 +0200
Committer: Ingo Molnar
CommitDate: Fri, 22 Jun 2018 10:58:27 +0200
efi/libstub/tpm:
On 2018/6/20 19:51, Punit Agrawal wrote:
> Xie XiuQi writes:
>
>> Hi Lorenzo, Punit,
>>
>>
>> On 2018/6/20 0:32, Lorenzo Pieralisi wrote:
>>> On Tue, Jun 19, 2018 at 04:35:40PM +0100, Punit Agrawal wrote:
Michal Hocko writes:
> On Tue 19-06-18 15:54:26, Punit Agrawal wrote:
>
On Thu 21-06-18 21:17:24, Mikulas Patocka wrote:
[...]
> > But seriously, isn't the best way around the throttling issue to use
> > PF_LESS_THROTTLE?
>
> Yes - it could be done by setting PF_LESS_THROTTLE. But I think it would
> be better to change it just in one place than to add
On 6/22/2018 1:52 PM, Enric Balletbo i Serra wrote:
Hi Ezequiel and Akhil,
On 22/06/18 09:03, Akhil P Oommen wrote:
On 6/22/2018 6:41 AM, Ezequiel Garcia wrote:
Hey Enric,
On Fri, 2018-06-22 at 00:04 +0200, Enric Balletbo i Serra wrote:
When the devfreq driver and the governor driver are
On Thu, Jun 21, 2018 at 01:27:12PM -0400, Alan Stern wrote:
> More than one kernel developer has expressed the opinion that the LKMM
> should enforce ordering of writes by release-acquire chains and by
> locking. In other words, given the following code:
>
> WRITE_ONCE(x, 1);
>
On Fri 22-06-18 16:58:05, Hanjun Guo wrote:
> On 2018/6/20 19:51, Punit Agrawal wrote:
> > Xie XiuQi writes:
> >
> >> Hi Lorenzo, Punit,
> >>
> >>
> >> On 2018/6/20 0:32, Lorenzo Pieralisi wrote:
> >>> On Tue, Jun 19, 2018 at 04:35:40PM +0100, Punit Agrawal wrote:
> Michal Hocko writes:
>
Hi,
On 22-06-18 09:16, Benjamin Tissoires wrote:
On Fri, Jun 22, 2018 at 4:27 AM, Stephen Boyd wrote:
Use devm here to save some lines and prepare for bulk regulator usage in
this driver. Otherwise, when we devm bulk get regulators we'll free the
containing i2c_hid structure and try to put
Commit-ID: 57d6a7938a8fc6cee8420b40ca244220b41721f5
Gitweb: https://git.kernel.org/tip/57d6a7938a8fc6cee8420b40ca244220b41721f5
Author: Mathieu Malaterre
AuthorDate: Thu, 8 Mar 2018 21:28:56 +0100
Committer: Ingo Molnar
CommitDate: Fri, 22 Jun 2018 11:07:47 +0200
perf/core: Move the
On 06/21/2018 06:53 PM, Guenter Roeck wrote:
On Thu, Jun 21, 2018 at 11:02:15AM +0200, Ludovic Barre wrote:
From: Ludovic Barre
This patch adds compatible data to manage pclk clock by
compatible. Adds stm32mp1 support which requires pclk clock.
Signed-off-by: Ludovic Barre
---
Commit-ID: 01bdee64f9cf8e15f998bf52789ed9d0ebdfa621
Gitweb: https://git.kernel.org/tip/01bdee64f9cf8e15f998bf52789ed9d0ebdfa621
Author: Masami Hiramatsu
AuthorDate: Fri, 22 Jun 2018 15:07:40 +0900
Committer: Ingo Molnar
CommitDate: Fri, 22 Jun 2018 11:10:55 +0200
On Thu, 21 Jun 2018, Fenghua Yu wrote:
> Right. Code won't cover the early boot process. It only covers boot process
> after the feature is enabled.
That's broken. #AC wants to be enabled early as any other exception. The
reason why you cannot enable it is because your exception handler is a
On Thu, 21 Jun 2018, Fenghua Yu wrote:
> The control knobs allow sysadmin to handle #AC for split lock in different
> scenarios and usages.
>
> The control knob for kernel is to choose re-executing the faulting
> instruction (default) or kernel panic. Kernel panic may be useful in hard
> real
Hi Wei,
On Fri, Jun 22, 2018 at 09:33:04AM +0100, Wei Xu wrote:
> On 2018/6/21 11:54, Will Deacon wrote:
> > On Thu, Jun 21, 2018 at 11:14:28AM +0100, Wei Xu wrote:
> >> On 2018/6/21 10:18, Will Deacon wrote:
> >>> Wei -- does the diff below help at all? Make sure you disable
> >>> CONFIG_KASAN,
On Thu, Jun 21, 2018 at 05:59:06PM +0200, Geert Uytterhoeven wrote:
> "ARM multiplatform" has actually two meanings:
> 1. It groups platforms that follow the "ARM multiplatform" software
> framework,
> 2. It allows to build a single kernel that can be booted on multiple
> platforms.
[ Added Al, since this all came in through his trees. The guilty
authors were already added by the robot ]
On Fri, Jun 22, 2018 at 5:31 PM kernel test robot wrote:
>
> FYI, we noticed a -8.8% regression of will-it-scale.per_process_ops due to
> commit:
Guys, this seems pretty big.
What was
On Thu, 21 Jun 2018, Fenghua Yu wrote:
> The control knob for user is to choose killing the process (default) or
> re-executing the faulting instruction without blocking the process.
> Re-executing the instruction maybe be useful in platforms that run
> well controlled apps with less split locks.
Hi,
This patch is already tested and confirmed by our colleagues in Guatemala.
Regards,
Jian-Hong Pan
.
Jian-Hong Pan | +886 2 7712 8713 | Endless
2018-05-25 22:05 GMT+08:00 Jian-Hong Pan :
> Hi Daniel,
>
>
On Thu, 21 Jun 2018, Fenghua Yu wrote:
> The control knob for firmware is to choose continuing firmware execution
> by disabling #AC split lock (default) or stopping firmware execution
> by enabling #AC for split lock. Stopping firmware execution may be useful
> in hard real time system to
There is a special case that the size is "(N << KASAN_SHADOW_SCALE_SHIFT)
Pages plus X", the value of X is [1, KASAN_SHADOW_SCALE_SIZE-1]. The
operation "size >> KASAN_SHADOW_SCALE_SHIFT" will drop X, and the roundup
operation can not retrieve the missed one page. For example: size=0x28006,
On Thu, 21 Jun 2018, Fenghua Yu wrote:
> On Thu, Jun 21, 2018 at 03:18:19PM -0700, Dave Hansen wrote:
> > On 06/21/2018 03:08 PM, Peter Zijlstra wrote:
> > > On Thu, Jun 21, 2018 at 03:00:03PM -0700, Fenghua Yu wrote:
> > >> The control knob for kernel is to choose re-executing the faulting
> > >>
Hi Michal
> diff --git a/include/linux/oom.h b/include/linux/oom.h
> index 6adac113e96d..5bed78d4bfb8 100644
> --- a/include/linux/oom.h
> +++ b/include/linux/oom.h
> @@ -15,6 +15,20 @@ struct notifier_block;
> struct mem_cgroup;
> struct task_struct;
>
> +enum oom_constraint {
> +
Hi,
Mawanda Henry writes:
> SPDX license helps developers and machines to know the license governing
> a particular file hence easing work
>
> Signed-off-by: Mawanda Henry
> ---
> drivers/bus/arm-cci.c | 10 +-
> 1 file changed, 1 insertion(+), 9 deletions(-)
>
> diff --git
On Fri, Jun 22, 2018 at 11:27 AM, Zhen Lei wrote:
> There is a special case that the size is "(N << KASAN_SHADOW_SCALE_SHIFT)
> Pages plus X", the value of X is [1, KASAN_SHADOW_SCALE_SIZE-1]. The
> operation "size >> KASAN_SHADOW_SCALE_SHIFT" will drop X, and the roundup
> operation can not
On Fri, Jun 22, 2018 at 06:25:45PM +0900, Linus Torvalds wrote:
> What was the alleged advantage of the new poll methods again? Because
> it sure isn't obvious - not from the numbers, and not from the commit
> messages.
The primary goal is that we can implement a race-free aio poll,
the primary
And a version with select() also covered:
---
>From 317159003ae28113cf759c632b161fb39192fe3c Mon Sep 17 00:00:00 2001
From: Christoph Hellwig
Date: Fri, 22 Jun 2018 11:36:26 +0200
Subject: fs: optimize away ->_qproc indirection for poll_mask based polling
Signed-off-by: Christoph Hellwig
---
From: Borislav Petkov
The hardware configuration register has some useful bits which can be
used by guests. Implement McStatusWrEn which can be used by guests when
injecting MCEs with the in-kernel mce-inject module.
For that, we need to set bit 18 - McStatusWrEn - first, before writing
the
From: Borislav Petkov
Hi all,
there's this mce-inject.ko module in the kernel which allows for
injecting real MCEs and thus test the MCE handling code.
It is doubly useful to be able to inject same MCEs in a guest so that
testing of the MCE handling code can happen even easier/faster. In order
From: Borislav Petkov
Extend the range of MCA banks which get passed to set/get_msr_mce() to
include all the MSRs of the last bank too.
Signed-off-by: Borislav Petkov
---
arch/x86/kvm/x86.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kvm/x86.c
From: Borislav Petkov
This is an AMD-specific MSR. Put it where it belongs.
Signed-off-by: Borislav Petkov
---
arch/x86/kvm/svm.c | 14 ++
arch/x86/kvm/x86.c | 12
2 files changed, 14 insertions(+), 12 deletions(-)
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
We recently made enabling LPIs a lot stricter, by checking that
they are disabled before we enable them. By doing so, we missed
the CPU hotplug case altogether, where we leave LPIs enabled
on hotplug off (we expect the CPU to eventually come back),
and won't write a different value anyway on
701 - 800 of 1351 matches
Mail list logo
