FYI, we noticed the following commit (built with gcc-7):
commit: df95cc69cca894430640237d39453f5d96c40a7d ("rcu: Parallelize expedited
grace-period initialization")
https://git.kernel.org/cgit/linux/kernel/git/paulmck/linux-rcu.git rcu/dev
in testcase: trinity
with following parameters:
> Il giorno 23 feb 2018, alle ore 17:17, Ming Lei ha
> scritto:
>
> Hi Paolo,
>
> On Fri, Feb 23, 2018 at 04:41:36PM +0100, Paolo Valente wrote:
>>
>>
>>> Il giorno 23 feb 2018, alle ore 16:07, Ming Lei ha
>>> scritto:
>>>
>>> Hi Paolo,
>>>
>>> On Wed, Feb 07, 2018 at 10:19:20PM +0100,
On Sat, Feb 10, 2018 at 05:55:15AM +0800, Ken Lin wrote:
> Add support for Advantech DMS-BA16 board, which uses
> the Advantech BA-16 module.
>
> Signed-off-by: Ken Lin
Applied, thanks.
On Thu, 22 Feb 2018 15:27:24 +0100 (CET)
Christophe Leroy wrote:
> In preparation for the following patch which will fix an issue on
> the 8xx by re-using the 'slices', this patch enhances the
> 'slices' implementation to support 32 bits CPUs.
>
> On PPC32, the address space is limited to 4Gbyte
On Mon, Feb 12, 2018 at 01:39:44PM +0100, Sebastian Reichel wrote:
> On i.MX53 it is necessary to set the DBG_EN bit in the
> platform GPC register to enable access to PMU counters
> other than the cycle counter.
>
> Signed-off-by: Sebastian Reichel
> ---
> arch/arm/mach-imx/mach-imx53.c | 39 ++
On Fri, Feb 09, 2018 at 01:43:23PM +0100, Martin Kaiser wrote:
> imx25 contains two registers (LPIMR0 and 1) to define which interrupts
> are enabled in low-power mode. As of today, those two registers are
> configured to enable all interrupts. Before going to low-power mode, the
> AVIC's INTENABLE
On Sat, Feb 24, 2018 at 01:32:50PM +0800, Boqun Feng wrote:
[...]
>
> I also reorder bit number for each kind of dependency, so that we have a
> simple __calc_dep_bit(), see the following:
>
> /*
>* DEP_*_BIT in lock_list::dep
>*
>* For dependency @prev -> @next:
>
On 02/23/18 at 12:42pm, Tyler Baicar wrote:
> The ESRT memory region is being exposed as System RAM in /proc/iomem
> which is wrong because it cannot be overwritten. This memory is needed
> for kexec kernels in order to properly initialize ESRT, so if it is
> overwritten it will cause ESRT failures
On Thu, 22 Feb 2018 15:27:22 +0100 (CET)
Christophe Leroy wrote:
> In preparation for the following patch which will enhance 'slices'
> for supporting PPC32 in order to fix an issue on hugepages on 8xx,
> this patch takes out of page*.h all bits related to 'slices' and put
> them into newly creat
On 02/23/18 at 12:42pm, Tyler Baicar wrote:
> If ESRT initialization fails due to an unsupported version, the
> early_memremap allocation is never unmapped. This will cause an
> early ioremap leak. So, make sure to unmap the memory allocation
> before returning from efi_esrt_init().
>
> Signed-off
On Sat, Feb 24, 2018 at 02:25:16PM +0800, Shawn Guo wrote:
> On Thu, Feb 08, 2018 at 03:54:34PM +0800, Ran Wang wrote:
> > From: Yuantian Tang
> >
> > Signed-off-by: Tang Yuantian
> > ---
> > arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 18 ++
> > 1 files changed, 18 inser
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 9cb9c07d6b0c5fd97d83b8ab14d7e308ba4b612f
commit: 101110f6271ce956a049250c907bc960030577f8 Kbuild: always define
endianess in kconfig.h
date: 2 days ago
config: m32r-allyesconfig (attached as .config)
compi
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On
> Behalf Of Benjamin Poirier
> Sent: Monday, February 19, 2018 10:12 PM
> To: Kirsher, Jeffrey T
> Cc: net...@vger.kernel.org; intel-wired-...@lists.osuosl.org; linux-
> ker...@vger.kernel.org
> Subject: [Intel-wired-lan] [PATC
On Sat, Feb 24, 2018 at 01:32:50PM +0800, Boqun Feng wrote:
> On Fri, Feb 23, 2018 at 08:37:32PM +0800, Boqun Feng wrote:
> > On Fri, Feb 23, 2018 at 12:55:20PM +0100, Peter Zijlstra wrote:
> > > On Thu, Feb 22, 2018 at 03:08:51PM +0800, Boqun Feng wrote:
> > > > @@ -1012,6 +1013,33 @@ static inlin
On Thu, Feb 08, 2018 at 03:54:34PM +0800, Ran Wang wrote:
> From: Yuantian Tang
>
> Signed-off-by: Tang Yuantian
> ---
> arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 18 ++
> 1 files changed, 18 insertions(+), 0 deletions(-)
Applied all, thanks.
TO: Paul E. McKenney
CC: LKML , Paul E. McKenney
, linux-kernel@vger.kernel.org, l...@01.org
FYI, we noticed the following commit (built with gcc-7):
commit: 056becf54ef1ab39db14a66625353899dba6762f ("rcu: Parallelize expedited
grace-period initialization")
https://git.kernel.org/cgit/linux/
A memory block was allocated in intel_svm_bind_mm() but never freed
in a failure path. This patch fixes this by free it to avoid memory
leakage.
Cc: Ashok Raj
Cc: Jacob Pan
Cc: # v4.4+
Signed-off-by: Lu Baolu
---
drivers/iommu/intel-svm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/dr
When using vfio to pass through a PCIe device (e.g. a GPU card) that
has a huge BAR (e.g. 16GB), a lot of cycles are wasted on memory
pinning because PFNs of PCI BAR are not backed by struct page, and
the corresponding VMA has flags VM_IO|VM_PFNMAP.
With this change, memory pinning process will fi
Add a testcase for array type with kprobe event.
This tests good/bad syntax combinations and also
the traced data is correct in several way.
If the kernel doesn't support array type, it skips
the test as UNSUPPORTED.
Signed-off-by: Masami Hiramatsu
---
.../ftrace/test.d/kprobe/kprobe_args_array.
Add a testcase for array type with kprobe event.
This tests whether the traced data is correct or not.
If the kernel doesn't support array type, it skips
the test as UNSUPPORTED.
Signed-off-by: Masami Hiramatsu
---
.../ftrace/test.d/kprobe/kprobe_args_argN.tc | 25
1
Add array type support for probe events.
This allows user to get arraied types from memory address.
The array type syntax is
TYPE[N]
Where TYPE is one of types (u8/16/32/64,s8/16/32/64,
x8/16/32/64, symbol, string) and N is a fixed value less
than 64.
The string array type is a bit diffe
Add a testcase for symbol type with kprobe event.
This tests good/bad syntax combinations and also
the traced data.
If the kernel doesn't support symbol type, it skips
the test as UNSUPPORTED.
Signed-off-by: Masami Hiramatsu
---
Changes in v3:
- Use IP/PC register to test the symbol type
---
Add $argN special fetch variable for accessing function
arguments. This allows user to trace the Nth argument easily
at the function entry.
Note that this returns most probably assignment of registers
and stacks. In some case, it may not work well. If you need
to access correct registers or stacks
Add regs_get_argument() which returns N th argument of the
function call.
Note that this chooses most probably assignment, in some case
it can be incorrect (e.g. passing data structure or floating
point etc.)
This is expected to be called from kprobes or ftrace with regs
where the top of stack is
Unify the fetch_insn bottom process (from stage 2: dereference
indirect data) from kprobe and uprobe events, since those are
mostly same.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_kprobe.c | 47 +
kernel/trace/trace_probe_tmpl.h | 55 +
Add "symbol" type to probeevent, which is an alias of u32 or u64
(depends on BITS_PER_LONG). This shows the result value in
symbol+offset style. This type is only available with kprobe
events.
Signed-off-by: Masami Hiramatsu
---
Changes in v2:
- Add symbol type to README file.
---
Documentati
Append traceprobe_ for exported function set_print_fmt() as
same as other functions.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_kprobe.c |4 ++--
kernel/trace/trace_probe.c |2 +-
kernel/trace/trace_probe.h |2 +-
kernel/trace/trace_uprobe.c |4 ++--
4 files changed
TO: Petr Mladek
CC: Cong Wang , Dave Hansen ,
Johannes Weiner , Mel Gorman , Michal
Hocko , Vlastimil Babka , Peter Zijlstra
, Linus Torvalds , Jan
Kara , Mathieu Desnoyers , Tetsuo
Handa , Byungchul Park
, Tejun Heo , Pavel Machek
, Steven Rostedt (VMware) , Sergey
Senozhatsky , LKML
, l
Cleanup string fetching routine so that returns the consumed
bytes of dynamic area and store the string information as
data_loc format instead of data_rloc.
This simplifies the fetcharg loop.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_kprobe.c | 51 +++--
Replace {k,u}probe event argument fetching framework
with switch-case based. Currently that is implemented
with structures, macros and chain of function-pointers,
which is more complicated than necessary and may get
a performance penalty by retpoline.
This simplify that with an array of "fetch_ins
Unify {k,u}probe_fetch_type_table to probe_fetch_type_table
because the main difference of those type tables (fetcharg
methods) are gone. Now we can consolidate it.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_kprobe.c | 27 +-
kernel/trace/trace_probe.c | 54 +
Remove unneeded NOKPROBE_SYMBOL from print functions since
the print functions are only used when printing out the
trace data, and not from kprobe handler.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_probe.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/ker
Cleanup event argument definition code in one place for
maintenancability.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_kprobe.c | 32
kernel/trace/trace_probe.c | 21 +
kernel/trace/trace_probe.h |2 ++
kernel/trace/trace_
Current print argument functions prints the argument
name too. It is not good for printing out multiple
values for one argument. This change it to just print
out the value.
Signed-off-by: Masami Hiramatsu
---
kernel/trace/trace_kprobe.c | 20 ++--
kernel/trace/trace_probe.c |
Add a testcase for string type with kprobe event.
This tests good/bad syntax combinations and also
the traced data is correct in several way.
Signed-off-by: Masami Hiramatsu
---
.../ftrace/test.d/kprobe/kprobe_args_string.tc | 46
1 file changed, 46 insertions(+)
crea
On Fri, Feb 23, 2018 at 08:37:32PM +0800, Boqun Feng wrote:
> On Fri, Feb 23, 2018 at 12:55:20PM +0100, Peter Zijlstra wrote:
> > On Thu, Feb 22, 2018 at 03:08:51PM +0800, Boqun Feng wrote:
> > > @@ -1012,6 +1013,33 @@ static inline bool bfs_error(enum bfs_result res)
> > > return res < 0;
> > >
In Documentation/trace/kprobetrace.txt, it says
@SYM[+|-offs] : Fetch memory at SYM +|- offs (SYM should be a data symbol)
However, the parser doesn't parse minus offset correctly, since
commit 2fba0c8867af ("tracing/kprobes: Fix probe offset to be
unsigned") drops minus ("-") offset support for
Add a testcase for probe event argument syntax which
ensures the kprobe_events interface correctly parses
given event arguments.
Signed-off-by: Masami Hiramatsu
---
.../ftrace/test.d/kprobe/kprobe_args_syntax.tc | 97
1 file changed, 97 insertions(+)
create mode 10064
Hi,
This is the 3rd version of the fetch-arg improvement series.
This includes variable changes on fetcharg framework like,
- Add fetcharg testcases (syntax, argN, symbol, string and array)
- Rewrite fetcharg framework with fetch_insn, switch-case based
instead of function pointer.
- Add "symbo
Hi Or,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on char-misc/char-misc-testing]
[also build test ERROR on v4.16-rc2 next-20180223]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com
Hi Masahiro,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.16-rc2 next-20180223]
[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 02/23/2018 05:02 AM, Lorenzo Pieralisi wrote:
On Thu, Jan 25, 2018 at 09:56:30AM -0600, Jeremy Linton wrote:
Hi,
On 01/25/2018 06:15 AM, Xiongfeng Wang wrote:
Hi Jeremy,
I have tested the patch with the newest UEFI. It prints the below error:
[4.017371] BUG: arch topology borken
[
Linus, this talk about the memory map bullshit is interesting and all,
with that binary encoding and shit. But I want you to take a moment and
reflect. I want you to reflect on truth.
Ask yourself. "Am I a white man" and then listen to those who...
who see you ALL for what you are and couldn't be
www.liveleak.com/view?i=017_1519418755
This had to be reposted because the youtube people took down the video
describing the truth about white society. Speaking truth to power isn't
something they was fastioning to slide by.
So, dear OpenSource folks, people that run the show on the computing
On Fri, Feb 23, 2018 at 5:49 PM, Dave Hansen
wrote:
> On 02/22/2018 01:52 PM, Linus Torvalds wrote:
>> Side note - and this may be crazy talk - I wonder if it might make
>> sense to have a mode where we allow executable read-only kernel pages
>> to be marked global too (but only in the kernel mapp
On 02/23/2018 01:34 PM, Adam Borowski wrote:
On Fri, Feb 23, 2018 at 02:32:08PM -0500, James Bottomley wrote:
On Fri, 2018-02-23 at 18:19 +, Al Viro wrote:
[...]
IIRC, parisc/qemu stuff had been announced a while ago;
I have, but it didn't work sufficiently for me to either boot a kernel
I missed the Per-VM-BO share the reservation object with root bo. So context is
not NULL here.
So, this patch is:
Reviewed-by: Roger He
Thanks
Roger(Hongbo.He)
-Original Message-
From: Christian König [mailto:ckoenig.leichtzumer...@gmail.com]
Sent: Friday, February 23, 2018 8:06 PM
To:
-Original Message-
From: Christian König [mailto:ckoenig.leichtzumer...@gmail.com]
Sent: Friday, February 23, 2018 8:06 PM
To: He, Roger ; amd-...@lists.freedesktop.org;
dri-de...@lists.freedesktop.org; linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] drm/ttm: handle already locked
We don't flush batched XDP packets through xdp_do_flush_map(), this
will cause packets stall at TX queue. Consider we don't do XDP on NAPI
poll(), the only possible fix is to call xdp_do_flush_map()
immediately after xdp_do_redirect().
Note, this in fact won't try to batch packets through devmap,
This reverts commit 762c330d670e3d4b795cf7a8d761866fdd1eef49. The
reason is we try to batch packets for devmap which causes calling
xdp_do_flush() in the process context. Simply disabling preemption
may not work since process may move among processors which lead
xdp_do_flush() to miss some flushes
Except for tuntap, all other drivers' XDP was implemented at NAPI
poll() routine in a bh. This guarantees all XDP operation were done at
the same CPU which is required by e.g BFP_MAP_TYPE_PERCPU_ARRAY. But
for tuntap, we do it in process context and we try to protect XDP
processing by RCU reader lo
On Sat, Feb 24, 2018 at 12:22:24PM +0900, Akira Yokosawa wrote:
> On 2018/02/22 07:29:02 +0900, Akira Yokosawa wrote:
> > On 2018/02/22 2:15, Alan Stern wrote:
> >> Commit bf28ae562744 ("tools/memory-model: Remove rb-dep,
> >> smp_read_barrier_depends, and lockless_dereference") was accidentally
>
On 2018/02/22 07:29:02 +0900, Akira Yokosawa wrote:
> On 2018/02/22 2:15, Alan Stern wrote:
>> Commit bf28ae562744 ("tools/memory-model: Remove rb-dep,
>> smp_read_barrier_depends, and lockless_dereference") was accidentally
>> merged too early, while it was still in RFC form. This patch adds in
>
Hi Linus,
Please pull some more powerpc fixes for 4.16:
The following changes since commit 91ab883eb21325ad80f3473633f794c78ac87f51:
Linux 4.16-rc2 (2018-02-18 17:29:42 -0800)
are available in the git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git
tags/po
Hi AKASHI,
On 02/22/18 at 08:17pm, AKASHI Takahiro wrote:
> exclude_mem_range() and prepare_elf64_headers() can be re-used on other
> architectures, including arm64, as well. So let them factored out so as to
> move them to generic side in the next patch.
>
> fill_up_crash_elf_data() can potential
Anson Huang
Best Regards!
> -Original Message-
> From: Shawn Guo [mailto:shawn...@kernel.org]
> Sent: Saturday, February 24, 2018 10:52 AM
> To: Anson Huang
> Cc: rui.zh...@intel.com; edubez...@gmail.com; robh...@kernel.org;
> mark.rutl...@arm.com; ker...@pengutronix.de; Fabio Estevam
Hi,
On 2018/2/23 19:02, Lorenzo Pieralisi wrote:
> On Thu, Jan 25, 2018 at 09:56:30AM -0600, Jeremy Linton wrote:
>> Hi,
>>
>> On 01/25/2018 06:15 AM, Xiongfeng Wang wrote:
>>> Hi Jeremy,
>>>
>>> I have tested the patch with the newest UEFI. It prints the below error:
>>>
>>> [4.017371] BUG: a
As reported by Dan the parentheses is in the wrong place, and since
unlikely() call returns either 0 or 1 it's never less than zero.
The second issue is that signed integer overflows like "INT_MAX + 1" are
undefined behavior.
Since num_test_devs represents the number of devices, we want to stop
pr
On Mon, Jan 22, 2018 at 01:27:54PM +0300, Dan Carpenter wrote:
> The main problem is that the parentheses are in the wrong place and the
> unlikely() call returns either 0 or 1 so it's never less than zero.
Doh, thanks, yes. Seems worth considering a grammar rule for it.
> The other problem is th
On Mon, Feb 05, 2018 at 04:12:27PM +0800, Anson Huang wrote:
> This patch adds i.MX7 thermal sensor support, most
> of the i.MX7 thermal sensor functions are same with
> i.MX6 except the registers offset/layout, so we move
> those registers offset/layout definitions to soc data
> structure.
>
> i.
On 2018/2/21 23:29, Daniel Lezcano wrote:
Register the ARM generic cpuidle driver as a cooling device.
Signed-off-by: Daniel Lezcano
---
drivers/cpuidle/cpuidle-arm.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/cpuidle/cpuidle-arm.c b/drivers/cpuidle/cpuidle-arm.c
inde
All CONFIG_FW_LOADER_USER_HELPER_FALLBACK really is, is just a bool,
initailized at build time. Define it as such. This simplifies the
logic even further, removing now all explicit #ifdefs around the code.
Signed-off-by: Luis R. Rodriguez
---
drivers/base/firmware_loader.c | 25 +
Greg,
this v2 series addresses some corner case build issues. One was spotted
late by 0-day after I used Linus' tree for build tests rather than
linux-next, and another I found on my own. 0-day covers more ground
with testing if you use Linus' tree.
The one cought by 0-day was in that in the case
When a kernel is not built with:
CONFIG_HAS_FW_LOADER_USER_HELPER_FALLBACK=y
We don't currently enable testing fw_fallback.sh. For kernels that
still enable the fallback mechanism, its possible to use the async
request firmware API call request_firmware_nowait() using the custom
interface to use
The firmware loader code has grown quite a bit over the years.
The practice of stuffing everything we need into one file makes
the code hard to follow.
In order to split the firmware loader code into different components
we must pick a module name and a first object target file. We must
keep the f
You currently need four different kernel builds to test the firmware
API fully. By adding a proc knob to force disable the fallback mechanism
completely we are able to reduce the amount of kernels you need built
to test the firmware API down to two.
Signed-off-by: Luis R. Rodriguez
---
drivers/b
Both fw_fallback.sh and fw_filesystem.sh share a common set of
boiler plate setup and tests. We can share these in a common place.
While at it, move both test to use /bin/bash.
Signed-off-by: Luis R. Rodriguez
---
tools/testing/selftests/firmware/fw_fallback.sh | 69 ++---
tools/testi
We only use the timeout for the firmware fallback mechanism
except for trying to set the timeout during the cache setup
for resume/suspend. For those cases, setting the timeout should
be a no-op, so just reflect this in code by adding helpers for it.
This change introduces no functional changes.
The firmware fallback code is optional. Split that code out to help
distinguish the fallback functionlity from othere core firmware loader
features. This should make it easier to maintain and review code
changes.
The reason for keeping the configuration onto a table which is built-in
if you enable
Since we now have knobs to twiddle what used to be set on kernel
configurations we can build one base kernel configuration and modify
behaviour to mimic such kernel configurations to test them.
Provided you build a kernel with:
CONFIG_TEST_FIRMWARE=y
CONFIG_FW_LOADER=y
CONFIG_FW_LOADER_USER_HELPE
The timeout is a fallback construct, so we can just stuff the
timeout configuration under struct firmware_fallback_config.
While at it, add a few helpers which vets the use of getting or
setting the timeout as an int. The main use of the timeout is
to set a timeout for completion, and that is used
On 2018/2/9 14:13, jiangyiwen wrote:
> User use some syscall, for example mmap(v9fs_file_mmap), it will not
> update atime even if user's mnt_flags have MNT_NOATIME, because
> v9fs default set SB_NOATIME in v9fs_set_super.
>
> For supporting access time is updated when user mount with relatime,
>
Now that we have a kconfig checker just use that instead of relying
on testing a sysfs directory being present, since our requirements
are spelled out.
Signed-off-by: Luis R. Rodriguez
---
tools/testing/selftests/firmware/fw_fallback.sh | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
Currently one requires to test four kernel configurations to test the
firmware API completely:
0)
CONFIG_FW_LOADER=y
1)
o CONFIG_FW_LOADER=y
o CONFIG_FW_LOADER_USER_HELPER=y
2)
o CONFIG_FW_LOADER=y
o CONFIG_FW_LOADER_USER_HELPER=y
o CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y
3) When CO
On Sat, Feb 24, 2018 at 01:49:35AM +, Chris Mi wrote:
> To verify this patch, the following is a sanity test case:
>
> # tc qdisc delete dev $link ingress > /dev/null 2>&1;
> # tc qdisc add dev $link ingress;
> # tc filter add dev $link prio 1 protocol ip handle 0x8001 parent :
> flow
On Tue, Feb 13, 2018 at 04:41:37PM -0800, Luis R. Rodriguez wrote:
> 0-day has given me its blessings on these builds.
Spoke too soon, 0-day found one build issue later once I used Linus' tree
instead of linux-next, and I found another one on my own. I've fixed these.
Since these patches are not m
Hi all,
Commits
99158246208b ("KVM: nVMX: preserve SECONDARY_EXEC_DESC without UMIP")
103c763c72dd ("KVM/x86: remove WARN_ON() for when vm_munmap() fails")
b28676bb8ae4 ("KVM: mmu: Fix overlap between public and private memslots")
are missing a Signed-off-by from their committer.
--
Chee
The Spreadtrum SC9860 platform GPIO controller contains 16 groups and
each group contains 16 GPIOs. Each GPIO can set input/output and has
the interrupt capability.
Signed-off-by: Baolin Wang
Reviewed-by: Andy Shevchenko
---
Changes since v4:
- Convert handle_simple_irq() to handle_bad_irq().
This patch adds the device tree bindings for the Spreadtrum
GPIO controller. The gpios will be supported by the GPIO
generic library.
Signed-off-by: Baolin Wang
Acked-by: Rob Herring
---
Changes since v4:
- No updates.
Changes since v3:
- Add acked tag from Rob.
Changes since v2:
- No updat
On 02/23/18 at 11:01am, Philipp Rudo wrote:
> Hi Dave
>
> On Fri, 23 Feb 2018 16:34:05 +0800
> Dave Young wrote:
>
> > On 02/14/18 at 10:54am, Philipp Rudo wrote:
> > > Hi Dave,
> > >
> > > I just browsed AKASHI's patches (v7). The way I see it the common code
> > > changes
> > > are on differ
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 9cb9c07d6b0c5fd97d83b8ab14d7e308ba4b612f
commit: 101110f6271ce956a049250c907bc960030577f8 Kbuild: always define
endianess in kconfig.h
date: 2 days ago
config: m32r-allyesconfig (attached as .config)
compi
Hi Andy,
On 23 February 2018 at 21:35, Andy Shevchenko wrote:
> On Fri, Feb 23, 2018 at 6:44 AM, Baolin Wang wrote:
>> The Spreadtrum SC9860 platform GPIO controller contains 16 groups and
>> each group contains 16 GPIOs. Each GPIO can set input/output and has
>> the interrupt capability.
>>
>
>
On 02/22/2018 01:52 PM, Linus Torvalds wrote:
> Side note - and this may be crazy talk - I wonder if it might make
> sense to have a mode where we allow executable read-only kernel pages
> to be marked global too (but only in the kernel mapping).
We did that accidentally, somewhere. It causes mac
> -Original Message-
> From: Matthew Wilcox [mailto:wi...@infradead.org]
> Sent: Saturday, February 24, 2018 9:15 AM
> To: Cong Wang ; Khalid Aziz
> ; linux-kernel@vger.kernel.org;
> net...@vger.kernel.org
> Cc: Chris Mi
> Subject: Re: Fwd: Re: Kernel panic with 4.16-rc1 (and 4.16-rc2) run
Ping...
Anson Huang
Best Regards!
> -Original Message-
> From: linux-arm-kernel [mailto:linux-arm-kernel-boun...@lists.infradead.org]
> On Behalf Of Anson Huang
> Sent: Monday, February 5, 2018 4:12 PM
> To: rui.zh...@intel.com; edubez...@gmail.com; robh...@kernel.org;
> mark.rutl...@arm
Linus,
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to 9c5e0afaf15788bcbd1c3469da701ac
On 2/23/2018 11:29 PM, Arnaldo Carvalho de Melo wrote:
Em Fri, Feb 23, 2018 at 09:25:00AM +0100, Peter Zijlstra escreveu:
On Fri, Feb 23, 2018 at 10:35:58PM +0800, Jin Yao wrote:
Unlike the perf report interactive annotate mode, the perf annotate
doesn't display the LBR data.
perf record -
On 02/23/2018 08:42 AM, Eugeniy Paltsev wrote:
As of today we use hardcoded MCIP debug mask, so if we launch
kernel via debugger and kick fever cores than HW has all cpus
hang at the momemt of setup MCIP debug mask.
So update MCIP debug mask when the new cpu came online, instead of
use hardcoded
On 02/23/2018 08:41 AM, Eugeniy Paltsev wrote:
Currently GFRC is running regardless state of ARC cores in the SMP cluster.
That means even if ARC cores are halted when doing JTAG debugging GFRC
[our source of wall-time] continues to run giving us unexpected warnings
once we allow ARC cores to run
On Fri, Feb 23, 2018 Randy Dunlap wrote:
> [add Matthew Wilcox; hopefully he can look/see]
Thanks, Randy. I don't understand why nobody else thought to cc the
author of the patch that it was bisected to ...
> On 02/23/2018 04:13 PM, Cong Wang wrote:
> > On Fri, Feb 23, 2018 at 3:27 PM, Cong Wang
ree, please drop us a note to
> help improve the system]
>
> chmod +x ~/bin/make.cross
...snip..
> # save the attached .config to linux build tree
> make.cross ARCH=powerpc
>
> Note: the
> linux-review/Ram-Pai/mm-x86-powerpc-Enhancements-to-M
On Tue, 20 Feb 2018 18:45:39 PST (-0800), alan...@andestech.com wrote:
On Tue, Feb 13, 2018 at 01:13:15PM +0800, Alan Quey-Liang Kao(高魁良) wrote:
This patch set includes the building blocks of dynamic ftrace features
for RISC-V machines.
Changes in v4:
- Organize code structure according to cha
On 02/23/2018 04:19 PM, Saravana Kannan wrote:
Some PMUs events can be read from any CPU. So allow the PMU to mark
events as such. For these events, we don't need to reject reads or
make smp calls to the event's CPU and cause unnecessary wake ups.
Good examples of such events would be events fro
An address_space will only have dax exceptional entries when FS_DAX is
enabled. The current reliance on S_DAX causes compile failures when
S_DAX is defined for DEV_DAX, but FS_DAX is disabled. Make dax_mapping()
always return false so that mm/truncate.c drops its link time
dependencies on fs/dax.c.
Given that S_DAX is non-zero in the FS_DAX=n + DEV_DAX=y case, another
mechanism besides the plain IS_DAX() check to compile out dead
filesystem-dax code paths. Without IS_FSDAX() xfs will fail at link time
with:
ERROR: "dax_finish_sync_fault" [fs/xfs/xfs.ko] undefined!
ERROR: "dax_iomap_f
Make sure S_DAX is defined in the CONFIG_FS_DAX=n + CONFIG_DEV_DAX=y
case. Otherwise vma_is_dax() may incorrectly return false in the
Device-DAX case.
Cc: Alexander Viro
Cc: linux-fsde...@vger.kernel.org
Cc: Christoph Hellwig
Cc: Jan Kara
Cc:
Fixes: dee410792419 ("/dev/dax, core: file operatio
On 01/02/2018 03:25 AM, Suzuki K Poulose wrote:
Add support for the Cluster PMU part of the ARM DynamIQ Shared Unit (DSU).
The DSU integrates one or more cores with an L3 memory system, control
logic, and external interfaces to form a multicore cluster. The PMU
allows counting the various events
Filesystem-DAX is incompatible with 'longterm' page pinning. Without
page cache indirection a DAX mapping maps filesystem blocks directly.
This means that the filesystem must not modify a file's block map while
any page in a mapping is pinned. In order to prevent the situation of
userspace holding
Do not bother looking up the file type in the case when Filesystem-DAX
is disabled at build time.
Cc: Alexander Viro
Cc: linux-fsde...@vger.kernel.org
Cc: Christoph Hellwig
Cc: Jan Kara
Signed-off-by: Dan Williams
---
include/linux/fs.h |2 ++
1 file changed, 2 insertions(+)
diff --git a
Colin King writes:
> From: Colin Ian King
>
> The bool enable_vma_readahead and function swap_vma_readahead are local
> to the source and do not need to be in global scope, so make them static.
>
> Cleans up sparse warnings:
> mm/swap_state.c:41:6: warning: symbol 'enable_vma_readahead' was not
1 - 100 of 1387 matches
Mail list logo
