Use smaller scan_control fields for order, priority, and reclaim_idx.
Convert fields from int => s8. All easily fit within a byte:
* allocation order range: 0..MAX_ORDER(64?)
* priority range: 0..12(DEF_PRIORITY)
* reclaim_idx range: 0..6(__MAX_NR_ZONES)
Since commit 6538b8ea886e
Matthew Wilcox wrote:
> On Mon, May 28, 2018 at 07:40:25PM -0700, Greg Thelen wrote:
>> Reclaim priorities range from 0..12(DEF_PRIORITY).
>> scan_control.priority is a 4 byte int, which is overkill.
>>
>> Since commit 6538b8ea886e ("x86_64: expand kernel stack to 16K") x86_64
>> stack
On 29/05/18 16:48, Arnaldo Carvalho de Melo wrote:
> Hi Adrian,
>
> We've made tools/perf/check-headers.sh the mechanism to check
> for drift on kernel file copies we have in tools/, and it assumes that
> if we have tools/a/b/c/d, then it came from a/b/c/d in the kernel
> sources, e.g. a
On Tue, May 29, 2018 at 4:51 PM, Sekhar Nori wrote:
> This nukes the following warning that is seen when building without
> OF support:
>
> drivers/gpio/gpio-davinci.c:437:25: warning: ‘keystone_gpio_get_irq_chip’
> defined but not used [-Wunused-function]
> static struct irq_chip
Hi Georgi,
Thanks for testing the patch on 8096 and pointing out this issue.
The issue is coming because, when card is removed, the HOST_CONTROL2
register is retaining the 1.8V Signalling enable bit till SDHCI reset
happens after a new card is inserted.
Adding the change you suggested can
Jerome,
On 15 May 2018 at 11:57, Jerome Brunet wrote:
> Trigger the reset line of the mmc controller while probing, if available.
> The reset should be optional for now, at least until all related DT nodes
> have the reset property.
>
> Reviewed-by: Kevin Hilman
> Signed-off-by: Jerome Brunet
On Tue 29-05-18 15:46:25, Linus Torvalds wrote:
[...]
> The whole and ONLY point of "kvmalloc()" and friends is to make it easy to
> write code and _not_ have those idiotic "let's do kmalloc or kvmalloc
> depending on the phase of the moon" garbage. So the warning has literally
> destroyed the
On Tue, May 29, 2018 at 03:19:47PM +0300, Dmitry Osipenko wrote:
> On 29.05.2018 15:12, Stefan Agner wrote:
> > On 29.05.2018 09:48, Peter De Schrijver wrote:
> >> On Mon, May 28, 2018 at 05:53:08PM +0200, Stefan Agner wrote:
> >>> On 28.05.2018 09:55, Peter De Schrijver wrote:
> On Sun, May
Hi Thierry,
> This patch fixes the following warning during boot:
>
> do not call blocking ops when !TASK_RUNNING; state=1 set at
> [<(ptrval)>] qca_setup+0x194/0x750 [hci_uart]
> WARNING: CPU: 2 PID: 1878 at kernel/sched/core.c:6135
> __might_sleep+0x7c/0x88
>
> In qca_set_baudrate(), the
i.MX6SLL supports cpu idle with ARM power gated,
it can reuse i.MX6SX's cpu idle driver to support
below 3 states of cpu idle:
state0: WFI;
state1: WAIT mode with ARM power on;
state2: WAIT mode with ARM power off.
L2_PGE in GPC_CNTR needs to be cleared to support
state2 cpu idle.
i.MX6SLL supports ARM power off in cpu idle, better to reuse
i.MX6SX cpu idle driver instead of i.MX6SL which does NOT
support ARM power off.
Signed-off-by: Anson Huang
---
arch/arm/mach-imx/cpuidle-imx6sl.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git
Some platforms like i.MX6UL/i.MX6SLL have L2
page power control in GPC, it needs to be
disabled if ARM is power gated and L2 is NOT
flushed, add GPC interface to control it.
Signed-off-by: Anson Huang
---
arch/arm/mach-imx/common.h | 1 +
arch/arm/mach-imx/gpc.c| 14 ++
2 files
On Tue, May 29, 2018 at 4:54 PM, Mark Brown wrote:
> On Mon, May 14, 2018 at 10:06:36AM +0200, Linus Walleij wrote:
>
>> arch/arm/mach-pxa/hx4700.c| 3 +-
>
> This doesn't apply against the above file in my tree, please check and
> resend.
How typical. I say let's defer this
On Tue, May 29, 2018 at 11:52:37PM -0700, John Stultz wrote:
> On Tue, May 29, 2018 at 10:33 PM, Greg KH wrote:
> > On Tue, May 29, 2018 at 10:14:35PM -0700, John Stultz wrote:
> >> On Tue, May 8, 2018 at 7:28 PM, Chanwoo Choi wrote:
> >> > On 2018년 05월 09일 08:17, John Stultz wrote:
> >> >> Hey
> - req->completion_data = cqr;
> + *((struct dasd_ccw_req **) blk_mq_rq_to_pdu(req)) = cqr;
> +
Please don't play such tricks. In general your driver structure
should have struct request embedded. If for some reason
struct dasd_ccw_req has a different life time please create a new
Hi Dan,
On Fri, May 25, 2018 at 10:21:08AM -0700, Dan Williams wrote:
> Mark notes that gcc optimization passes have the potential to elide
> necessary invocations of this instruction sequence, so include an
> optimization barrier.
>
> > I think that either way, we have a potential problem
Hi Sean,
>>
>> [ ... ]
>
> [ ... ]
>
>>> I post it as plain text as below
>>>
>>>
>>> Bluetooth monitor ver 5.37
>>> = Note: Linux version 4.16.0-rc1+ (aarch64)
>>> 0.641494
>>> = Note: Bluetooth subsystem version 2.22
>>>
When doing pmu sampling and then running a script with
perf script -s script.py, the process_event function gets
dictionary with some fields from the perf ring buffer
(like ip, sym, callchain etc).
But we miss quite a few fields we report now, for example,
LBRs,data
On Tue, May 29, 2018 at 10:33 PM, Greg KH wrote:
> On Tue, May 29, 2018 at 10:14:35PM -0700, John Stultz wrote:
>> On Tue, May 8, 2018 at 7:28 PM, Chanwoo Choi wrote:
>> > On 2018년 05월 09일 08:17, John Stultz wrote:
>> >> Hey folks,
>> >> I wanted to bring up an issue we've recently tripped
On Tue, 29 May 2018, Ben Chan wrote:
> According to [1] and also seemingly agreed by [2], the Scan Time usage
> (0x0D 0x56) is a report level usage, not a contact level usage.
>
> However, the hid-multitouch driver currently includes HID_DG_SCANTIME
> when calculating `td->last_slot_field',
On Wed 2018-05-30 16:03:50, Sergey Senozhatsky wrote:
> Drop the in_nmi() check from printk_safe_flush_on_panic()
> and attempt to re-init (IOW unlock) locked logbuf spinlock
> from panic CPU regardless of its context. Otherwise,
> theoretically, we can deadlock on logbuf trying to flush
> per-CPU
I'm announcing the release of the 4.9.104 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 4.4.134 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
> On 29 May 2018, at 18:40, Jason Gunthorpe wrote:
>
> On Tue, May 29, 2018 at 06:16:14PM +0200, Håkon Bugge wrote:
>>
>>> On 29 May 2018, at 17:49, Jason Gunthorpe wrote:
>>>
>>> On Tue, May 29, 2018 at 09:38:08AM +0200, Hans Westgaard Ry wrote:
The agent TID is a 64 bit value split
I'm announcing the release of the 3.18.111 kernel.
All users of the 3.18 kernel series must upgrade.
The updated 3.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.18.y
and can be browsed at the normal kernel.org git web
On Fri, 25 May 2018, Arnd Bergmann wrote:
> Using the power supply APIs requires selecting the appropriate
> Kconfig symbol, otherwise we get this build failure:
>
> drivers/hid/hid-steam.o: In function `steam_unregister':
> hid-steam.c:(.text+0x1cc): undefined reference to
Drop the in_nmi() check from printk_safe_flush_on_panic()
and attempt to re-init (IOW unlock) locked logbuf spinlock
from panic CPU regardless of its context. Otherwise,
theoretically, we can deadlock on logbuf trying to flush
per-CPU buffers:
a) Panic CPU is running in non-NMI context
b) Panic
On 25-05-18, 15:12, Vincent Guittot wrote:
> diff --git a/kernel/sched/cpufreq_schedutil.c
> b/kernel/sched/cpufreq_schedutil.c
> /*
>* Utilization required by DEADLINE must always be granted while, for
> @@ -197,7 +205,7 @@ static unsigned long sugov_aggregate_util(struct
>
Hi Dmitry,
-Original Message-
From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
Sent: Wednesday, May 30, 2018 2:05 AM
To: KT Liao
Cc: linux-kernel@vger.kernel.org; linux-in...@vger.kernel.org;
ulrik.debie...@e2big.org; phoe...@emc.com.tw; aaron...@canonical.com;
On 30 May 2018 at 07:58, Ingo Molnar wrote:
>
> * nixiaoming wrote:
>
>> mark_rodata_ro is only called by the function mark_readonly
>> when CONFIG_STRICT_KERNEL_RWX=y
>>
>> if CONFIG_STRICT_KERNEL_RWX is not set
>> a compile warning may be triggered: unused function
>>
>> Signed-off-by:
On 30 May 2018 at 2:07PM Ard Biesheuvel [mailto:ard.biesheu...@linaro.org]
wrote:
>On 30 May 2018 at 07:58, Ingo Molnar wrote:
>>
>> * nixiaoming wrote:
>>
>>> mark_rodata_ro is only called by the function mark_readonly
>>> when CONFIG_STRICT_KERNEL_RWX=y
>>>
>>> if CONFIG_STRICT_KERNEL_RWX is
On Fri, 25 May 2018, Benjamin Tissoires wrote:
> When we receive a RMI4 report, we should not unconditionally send an
> input_sync event. Instead, we should let the rmi4 transport layer do it
> for us.
>
> This fixes a situation where we might receive X in a report and the rest
> in a subsequent
On Mon, May 28, 2018 at 2:26 PM, Andy Shevchenko
wrote:
> On Mon, May 28, 2018 at 2:29 PM, Bartlomiej Zolnierkiewicz
> wrote:
>
>> - s2mps11->ext_control_gpiod = devm_kmalloc(>dev,
>> + s2mps11->ext_control_gpiod = devm_kzalloc(>dev,
>>
On Wed, May 30, 2018 at 7:07 AM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the regulator tree got a conflict in:
>
> arch/arm/mach-omap1/board-ams-delta.c
>
> between commit:
>
> 0486738928bf ("ARM: OMAP1: ams-delta: add GPIO lookup tables")
>
> from the arm-soc tree
2018-05-30 15:21 GMT+09:00 Abhishek Sahu :
> On 2018-05-30 05:58, Masahiro Yamada wrote:
>>
>> Hi.
>>
>> 2018-05-30 4:30 GMT+09:00 Boris Brezillon :
>>>
>>> On Sat, 26 May 2018 10:42:47 +0200
>>> Miquel Raynal wrote:
>>>
Hi Abhishek,
On Fri, 25 May 2018 17:51:29 +0530, Abhishek
On Tue, 29 May 2018 10:40:32 -0600
Jason Gunthorpe wrote:
> On Tue, May 29, 2018 at 06:16:14PM +0200, Håkon Bugge wrote:
> >
> > > On 29 May 2018, at 17:49, Jason Gunthorpe wrote:
> > >
> > > On Tue, May 29, 2018 at 09:38:08AM +0200, Hans Westgaard Ry
> > > wrote:
> > >> The agent TID is a
On Wed, May 30, 2018 at 03:31:38AM +, Nixiaoming wrote:
> Unable to set CONFIG_STRICT_KERNEL_RWX=n by make menuconfig ARCH=arm64
Indeed. Making this mandatory was a deliberate decision, in part because this
allows simplification of code (e.g. removal of #ifdef guards).
> When reading the
Hi,
On 2018년 05월 30일 05:57, Matthias Kaehlcke wrote:
> On Mon, May 28, 2018 at 04:32:37PM +0900, Chanwoo Choi wrote:
>
>> IMHO, you better to split out the devfreq patches from
>> 'throttler' patch set. Because I'm not sure throttler is either
>> necessary or not.
>>
>> After finishing the
On Tue, 29 May 2018 12:54:45 +0300
Leon Romanovsky wrote:
> On Tue, May 29, 2018 at 11:54:59AM +0300, Leon Romanovsky wrote:
> > On Tue, May 29, 2018 at 09:38:08AM +0200, Hans Westgaard Ry wrote:
> > > The agent TID is a 64 bit value split in two dwords. The least
> > > significant dword is
On Tue, May 29, 2018 at 5:29 PM, Amir Goldstein wrote:
> On Tue, May 29, 2018 at 5:41 PM, Miklos Szeredi wrote:
>> From: Amir Goldstein
>>
>> vfs_mkdir() may succeed and leave the dentry passed to it unhashed and
>> negative. ovl_create_real() is the last caller breaking when that
>> happens.
On Tue, May 29, 2018 at 5:13 PM, Amir Goldstein wrote:
> On Tue, May 29, 2018 at 5:43 PM, Miklos Szeredi wrote:
>> + WARN(1, "overlayfs: \"check_copy_up\" module option is obsolete\n");
>
> I was under the impression that user controlled input should not be generating
> WARNings... did
Hi all,
Today's linux-next merge of the userns tree got a conflict in:
arch/arm/mm/fault.c
between commit:
93a24d7e23e7 ("ARM: spectre-v2: harden user aborts in kernel space")
from the arm tree and commit:
3eb0f5193b49 ("signal: Ensure every siginfo we send has all bits initialized")
On Wed, 2018-05-30 at 10:41 +0200, Arnd Bergmann wrote:
> On Wed, May 30, 2018 at 2:48 AM, Ian Kent wrote:
> > On Tue, 2018-05-29 at 11:46 +0200, Arnd Bergmann wrote:
> > > The autofs4 implementation is just a redirect to autofs now, but that
> > > also means we can't have both built into the
On Tue, May 29, 2018 at 10:30:33PM -0700, Doug Anderson wrote:
> On Wed, May 23, 2018 at 8:56 AM, Mark Brown wrote:
> > Yes, that's definitely not what's expected but it's unfortunately what
> > the firmware chose to implement so we may well be stuck with it
> > unfortunately.
> We're not
On 30-05-18, 14:25, Rajendra Nayak wrote:
> []...
>
> >>> +Required Properties:
> >>> + - compatible: Should be one of the following
> >>> + * qcom,sdm845-rpmhpd: RPMh powerdomain for the sdm845 family of SoC
> >>> + - power-domain-cells: number of cells in power domain specifier
> >>> + must be
On (05/30/18 18:55), Sergey Senozhatsky wrote:
> >
> > I understand why you came with it but I am against this change without
> > a proper research. This would redirect too valuable messages into
> > a buffer of a limited size and postpone flushing them to the consoles.
> >
> > We would need to
On 30 May 2018 at 11:32, Patrick Bellasi wrote:
> On 29-May 15:29, Vincent Guittot wrote:
>> Hi Patrick,
>> >> +static inline bool rt_rq_has_blocked(struct rq *rq)
>> >> +{
>> >> + if (rq->avg_rt.util_avg)
>> >
>> > Should use READ_ONCE?
>>
>> I was expecting that there will be only one read
On 05/30/2018 03:14 PM, Viresh Kumar wrote:
> On 30-05-18, 14:25, Rajendra Nayak wrote:
>> []...
>>
> +Required Properties:
> + - compatible: Should be one of the following
> + * qcom,sdm845-rpmhpd: RPMh powerdomain for the sdm845 family of SoC
> + - power-domain-cells: number
The OPP binding says:
Property: operating-points-v2
...
This can contain more than one phandle for power domain
providers that provide multiple power domains. That is, one
phandle for each power domain. If only one phandle is available,
then the
On 05/30/2018 02:47 PM, Ulf Hansson wrote:
> On 25 May 2018 at 12:01, Rajendra Nayak wrote:
>> The powerdomains for corners just pass the performance state set by the
>> consumers to the RPM (Remote Power manager) which then takes care
>> of setting the appropriate voltage on the corresponding
Hi Marcel,
Sorry about the late reply. I got side-tracked with other things.
On Tue, May 08, 2018 at 10:03:57PM +0200, Marcel Holtmann wrote:
> Hi Johan,
>
> >> I have one concern, though. While providing raw data by
> >> default is fine generally, it is a problem with device
> >>
Hello!
On 5/29/2018 6:00 PM, Eric W. Biederman wrote:
Geert Uytterhoeven reported:
HOSTLD scripts/mod/modpost
CC arch/sh/kernel/traps_32.o
arch/sh/kernel/traps_32.c: In function 'do_divide_error':
arch/sh/kernel/traps_32.c:606:17: error: 'code' may be used uninitialized in
this
On 30.05.2018 04:50, Hugh Dickins wrote:
Swapping load on huge=always tmpfs (with khugepaged tuned up to be very
eager, but I'm not sure that is relevant) soon hung uninterruptibly,
waiting for page lock in shmem_getpage_gfp()'s find_lock_entry(), most
often when "cp -a" was trying to write to a
On Tue 29-05-18 15:21:14, Mike Kravetz wrote:
> Just a quick heads up. I noticed a change in libhugetlbfs testing starting
> with v4.17-rc1.
>
> V4.16 libhugetlbfs test results
> ** TEST SUMMARY
> * 2M
> * 32-bit 64-bit
> * Total
On Tue, May 29, 2018 at 10:48:16AM +0200, Michal Hocko wrote:
> On Mon 28-05-18 16:52:01, Aaron Lu wrote:
> > On Tue, May 08, 2018 at 01:26:40PM -0400, Johannes Weiner wrote:
> > > Hello,
> > >
> > > On Tue, May 08, 2018 at 01:34:51PM +0800, kernel test robot wrote:
> > > > FYI, we noticed a
On Tue, May 29, 2018 at 10:44 PM, Randy Dunlap wrote:
> On 05/29/2018 07:45 AM, Miklos Szeredi wrote:
>> + If this config option is enabled then overlay filesystems will
>> + copy up only metadata where appropriate and data copy up will
>> + happen when a file is opended for
On Tuesday 29 May 2018 at 11:52:03 (+0200), Juri Lelli wrote:
> On 29/05/18 09:40, Quentin Perret wrote:
> > Hi Vincent,
> >
> > On Friday 25 May 2018 at 15:12:26 (+0200), Vincent Guittot wrote:
> > > Now that we have both the dl class bandwidth requirement and the dl class
> > > utilization, we
Patch series adding support for ROHM BD71837 PMIC.
BD71837 is a programmable Power Management IC for powering single-core,
dual-core, and quad-core SoC’s such as NXP-i.MX 8M. It is optimized for
low BOM cost and compact solution footprint. It integrates 8 buck
regulators and 7 LDO’s to provide
On Wed 2018-05-30 16:51:05, Sergey Senozhatsky wrote:
> On (05/30/18 09:24), Petr Mladek wrote:
> > Acked-by: Petr Mladek
>
> Thanks.
>
> > Just to be sure. IMHO, it is not worth nominating this patch for
> > stable. It is not a regression fix. I see it as a continuous
> > improving of the
In load_module(), it's not always clear whether we're handling the
temporary module copy in info->hdr (which is freed at the end of
load_module()) or if we're handling the module already allocated and
copied to it's final place. Adding an info->mod field and using it
whenever we're handling the
We want to be able to log the module name in early error messages, such as
when module signature verification fails. Previously, the module name is
set in layout_and_allocate(), meaning that any error messages that happen
before (such as those in module_sig_check()) won't be logged with a module
It is useful to know which module failed signature verification, so
print the module name along with the error message.
Signed-off-by: Jessica Yu
---
kernel/module.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/module.c b/kernel/module.c
index
Introduce new_swapper_pg_dir to save virtual address of
new swapper_pg_dir.
Signed-off-by: YaoJun
---
arch/arm64/include/asm/mmu_context.h | 2 +-
arch/arm64/include/asm/pgtable.h | 1 +
arch/arm64/mm/kasan_init.c | 2 +-
arch/arm64/mm/mmu.c | 1 +
4 files
Currently, The offset between swapper_pg_dir and _text is
fixed. When attackers know the address of _text(no KASLR or
breaking KASLR), they can caculate the address of
swapper_pg_dir. Then KSMA(Kernel Space Mirroring Attack) can
be applied.
The principle of KSMA is to insert a carefully
On Wed, May 30, 2018 at 4:36 PM, jianchao.wang
wrote:
> Hi ming
>
> Thanks for your kindly response.
>
> On 05/30/2018 04:22 PM, Ming Lei wrote:
you could keep the software queues as-is but add our own version of
flush_busy_ctxs() that only removes requests of the domain that we want.
On Tue, May 29, 2018 at 03:15:01PM -0700, Tony Lindgren wrote:
> I think I bisected this same issue for the second time now
> but for a different merge window. What's up with that?
Last time we just reverted it as Maciej was unable to reproduce your
problem, he's tried again with some
Introduce __pa_swapper_pg_dir to save physical address
of swapper_pg_dir. And pass it as an argument to
__enable_mmu().
Signed-off-by: YaoJun
---
arch/arm64/include/asm/mmu_context.h | 4 +---
arch/arm64/include/asm/pgtable.h | 1 +
arch/arm64/kernel/cpufeature.c | 2 +-
On Wed, May 30, 2018 at 12:48:06PM +0800, YaoJun wrote:
> To protect against KSMA(Kernel Space Mirroring Attack), make
> tramp_pg_dir read-only. The principle of KSMA is to insert a
> carefully constructed PGD entry into the translation table.
> The type of this entry is block, which maps the
Make tramp_pg_dir and swapper_pg_dir adjacent. So we can migrate
them together.
Signed-off-by: YaoJun
---
arch/arm64/kernel/entry.S | 4 ++--
arch/arm64/kernel/vmlinux.lds.S | 10 +-
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/arch/arm64/kernel/entry.S
To show time info in kernel log earlier and help optimizing kernel
boot time, printk adds a debug hook "boot_printk_clock_fn()" for
capable platform which has accurate clock in early boot phase.
This patch will add early param setup option, so that user can
chose to provide a tsc based early
From: Colin Ian King
Trivial fix to spelling mistake in DP_ERR error message
Signed-off-by: Colin Ian King
---
drivers/infiniband/hw/qedr/verbs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/infiniband/hw/qedr/verbs.c
b/drivers/infiniband/hw/qedr/verbs.c
index
On 25-May 15:12, Vincent Guittot wrote:
> Add both cfs and rt utilization when selecting an OPP for cfs tasks as rt
> can preempt and steal cfs's running time.
>
> Signed-off-by: Vincent Guittot
> ---
> kernel/sched/cpufreq_schedutil.c | 14 +++---
> 1 file changed, 11 insertions(+), 3
On Wed, May 30, 2018 at 05:12:56PM +0800, YaoJun wrote:
> Introduce __pa_swapper_pg_dir to save physical address
> of swapper_pg_dir. And pass it as an argument to
> __enable_mmu().
>
> Signed-off-by: YaoJun
This is better, but your subject line is still identical for all 4
patches (which
On Wed, 2018-05-30 at 09:27 +0200, Ulf Hansson wrote:
> Jerome,
>
> On 15 May 2018 at 11:57, Jerome Brunet wrote:
> > Trigger the reset line of the mmc controller while probing, if available.
> > The reset should be optional for now, at least until all related DT nodes
> > have the reset
On (05/30/18 10:48), Petr Mladek wrote:
> > diff --git a/kernel/panic.c b/kernel/panic.c
> > index 42e487488554..98a0493a59d3 100644
> > --- a/kernel/panic.c
> > +++ b/kernel/panic.c
> > @@ -148,6 +148,7 @@ void panic(const char *fmt, ...)
> > * after setting panic_cpu) from invoking panic()
On 29-05-18, 21:13, Robert Jarzmik wrote:
> Vinod writes:
>
> > On 26-05-18, 11:54, Robert Jarzmik wrote:
> >> @@ -762,6 +762,8 @@ static void pxad_free_chan_resources(struct dma_chan
> >> *dchan)
> >>dma_pool_destroy(chan->desc_pool);
> >>chan->desc_pool = NULL;
> >>
> >> +
在 2018/5/29 18:26, Viresh Kumar 写道:
On 26-05-18, 15:16, Kevin Wangtao wrote:
consider such situation, current user_policy.min is 100,
current user_policy.max is 120, in cpufreq_set_policy,
other driver may update policy.min to 120, policy.max to
130. After that, If we input
On 30 May 2018 at 09:03, Viresh Kumar wrote:
> On 25-05-18, 15:12, Vincent Guittot wrote:
>> diff --git a/kernel/sched/cpufreq_schedutil.c
>> b/kernel/sched/cpufreq_schedutil.c
>> /*
>>* Utilization required by DEADLINE must always be granted while, for
>> @@ -197,7 +205,7 @@
The Asus ROG GL702ZC laptop contains a Realtek RTL8822BE device with
an associated BT chip using a USB ID of 13d3:3526. This ID is added
to the driver.
The /sys/kernel/debug/usb/devices portion for this device is:
T: Bus=01 Lev=01 Prnt=01 Port=09 Cnt=04 Dev#= 5 Spd=12 MxCh= 0
D: Ver= 1.10
On Tue 2018-05-29 21:13:15, Sergey Senozhatsky wrote:
> On (05/29/18 11:51), Hoeun Ryu wrote:
> > Make printk_safe_flush() safe in NMI context.
> > nmi_trigger_cpumask_backtrace() can be called in NMI context. For example
> > the
> > function is called in watchdog_overflow_callback() if the flag
Hi David,
The changes here involve cleaning up load_module() (patches 1 and 2) in
preparation for patch 3. The general idea is to do some preliminary module
section parsing and set up load info convenience variables earlier so that
we could log the module name during the module signature
Hi Ulf,
On 29/05/18 11:04, Ulf Hansson wrote:
> The existing dev_pm_domain_attach() function, allows a single PM domain to
> be attached per device. To be able to support devices that are partitioned
> across multiple PM domains, let's introduce a new interface,
> dev_pm_domain_attach_by_id().
>
Currently printk timestamp mostly come from the sched_clock which
depends on the clock setup, so there are many kernel logs started
with "[0.00] " before the clock is calibrated.
This patch will provide an debug option for specific platform to
provide a early boot time clock, so that we
On Tue, May 29, 2018 at 12:04 PM, Ulf Hansson wrote:
> Changes in v2:
> - Addressed comments from Geert around DT doc.
> - Addressed comments from Jon around clarification of how to use this
> and changes to returned error codes.
> - Fixed build error in case
On 29-May 15:29, Vincent Guittot wrote:
> Hi Patrick,
> >> +static inline bool rt_rq_has_blocked(struct rq *rq)
> >> +{
> >> + if (rq->avg_rt.util_avg)
> >
> > Should use READ_ONCE?
>
> I was expecting that there will be only one read by default but I can
> add READ_ONCE
I would say here
--
This is the Hong Kong Key bridge Investment Company Limited Debt/Loan
Funding Platform.
The HKKIC limited is a Financial Strategic Firm specializing in Growth
Financial Loans/Debt Funding Investments. We specialize in investments
in Private sectors in a broad range of areas, Within our
Hi,
> [PATCH v5] Input: add bu21029 touch driver
>
> Add Rohm BU21029 resistive touch panel controller support with I2C
> interface.
Is the patch ready to be pushed upstream? Is there anything I still need to do?
Regards,
Mark
Mark Jonas
Building Technologies, Panel Software Fire
On 30 May 2018 at 11:40, Patrick Bellasi wrote:
> On 25-May 15:12, Vincent Guittot wrote:
>> Add both cfs and rt utilization when selecting an OPP for cfs tasks as rt
>> can preempt and steal cfs's running time.
>>
>> Signed-off-by: Vincent Guittot
>> ---
>> kernel/sched/cpufreq_schedutil.c |
On Wed, May 30, 2018 at 01:50:22AM +, Hugh Dickins wrote:
> Swapping load on huge=always tmpfs (with khugepaged tuned up to be very
> eager, but I'm not sure that is relevant) soon hung uninterruptibly,
> waiting for page lock in shmem_getpage_gfp()'s find_lock_entry(), most
> often when "cp
Hi John,
On 5/30/2018 7:50 AM, John Stultz wrote:
On Tue, May 29, 2018 at 2:49 AM, Mukesh Ojha wrote:
Currently, for both non-stop clocksource and persistent clock
there is a corner case, when a driver failed to go suspend mode
rtc_resume() injects the sleeptime as
FYI, we noticed the following commit (built with gcc-6):
commit: c385a55f521e1649051d7f653bec9aa0ce711c9e ("Print the memcg's name when
system-wide OOM happened")
url:
https://github.com/0day-ci/linux/commits/ufo19890607/Print-the-memcg-s-name-when-system-wide-OOM-happened/20180522-033834
in
Hi,
On 2018년 05월 30일 03:57, Matthias Kaehlcke wrote:
> On Mon, May 28, 2018 at 03:37:47PM +0900, Chanwoo Choi wrote:
>> Hi,
>>
>> On 2018년 05월 26일 05:30, Matthias Kaehlcke wrote:
>>> Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding the
>>> devfreq device") initializes
consider such situation, current user_policy.min is 100,
current user_policy.max is 120, in cpufreq_set_policy,
other driver may update policy.min to 120, policy.max to
130. After that, If we input "echo 130 > scaling_min_freq",
then user_policy.min will be 130, and
On Wed, May 30, 2018 at 12:15 AM, Thomas Garnier wrote:
> Change the assembly code to use only relative references of symbols for the
> kernel to be PIE compatible.
>
> Position Independent Executable (PIE) support will allow to extend the
> KASLR randomization range 0x8000.
>
>
On Wed, May 30, 2018 at 12:15 AM, Thomas Garnier wrote:
> Change the assembly code to use only relative references of symbols for the
> kernel to be PIE compatible.
>
> Position Independent Executable (PIE) support will allow to extend the
> KASLR randomization range 0x8000.
>
>
On 25 May 2018 10:49, Geert wrote:
> Subject: Re: [PATCH v3 2/3] arm: shmobile: Add the R9A06G032 SMP enabler
> driver
>
> Hi Michel,
Hi Geert,
>
> On Thu, May 24, 2018 at 12:30 PM, Michel Pollet
> wrote:
> > The Renesas R9A06G032 second CA7 is parked in a ROM pen at boot time,
> > it requires
Hi,
On 29-05-18 13:50, Hans de Goede wrote:
Add touchscreen info for the Onda V891w 8.9" windows tablet.
Signed-off-by: Hans de Goede
Self-NACK I just learned there are 2 hardware revisions with different
digitizers which need different firmware, so this needs a more
narrow DMI match.
I
On 2018-05-30 13:08, Masahiro Yamada wrote:
2018-05-30 15:21 GMT+09:00 Abhishek Sahu :
On 2018-05-30 05:58, Masahiro Yamada wrote:
Hi.
2018-05-30 4:30 GMT+09:00 Boris Brezillon
:
On Sat, 26 May 2018 10:42:47 +0200
Miquel Raynal wrote:
Hi Abhishek,
On Fri, 25 May 2018 17:51:29 +0530,
Hi Dmitry,
On Tue, May 29, 2018 at 8:21 PM, Dmitry Torokhov
wrote:
> Hi Benjamin,
>
> On Tue, May 29, 2018 at 11:57:52AM +0200, Benjamin Tissoires wrote:
>> Looks like we require users to set a tool but input_mt_init_slots() never
>> set the tool bit for us. Meaning that this is a useless
On 30/05/18 09:37, Quentin Perret wrote:
> On Tuesday 29 May 2018 at 11:52:03 (+0200), Juri Lelli wrote:
> > On 29/05/18 09:40, Quentin Perret wrote:
> > > Hi Vincent,
> > >
> > > On Friday 25 May 2018 at 15:12:26 (+0200), Vincent Guittot wrote:
> > > > Now that we have both the dl class
401 - 500 of 1682 matches
Mail list logo
