Hi Uwe,
On 08.01.2019 00:10, Uwe Kleine-König wrote:
> Hello Claudiu,
>
> On Mon, Jan 07, 2019 at 09:30:55AM +, claudiu.bez...@microchip.com wrote:
>> On 05.01.2019 23:05, Uwe Kleine-König wrote:
>>> On Thu, Jan 03, 2019 at 01:29:44PM +, claudiu.bez...@microchip.com
>>> wrote:
From:
On Sat, Dec 29, 2018 at 3:25 PM Geert Uytterhoeven wrote:
> On Fri, Aug 24, 2018 at 12:00 AM Joe Perches wrote:
> > On Thu, 2018-08-23 at 23:52 +0200, Geert Uytterhoeven wrote:
> > > Reverted locally (incl. the follow-up), applied Andrew's fix, detected new
> > > warnings in v4.18+, and sent patc
On Tue 08-01-19 13:04:22, Dave Chinner wrote:
> On Mon, Jan 07, 2019 at 05:41:39PM -0500, Waiman Long wrote:
> > On 01/07/2019 05:32 PM, Dave Chinner wrote:
> > > On Mon, Jan 07, 2019 at 10:12:56AM -0500, Waiman Long wrote:
> > >> As newer systems have more and more IRQs and CPUs available in their
From: Guo Ren
810 doesn't support jsri instruction and csky-as will leave
jsri + nop for relocation. Module-probe need replace them with
lrw + jsr.
Signed-off-by: Guo Ren
Cc: Hui Kai
---
arch/csky/kernel/module.c | 38 ++
1 file changed, 22 insertions(+), 1
From: Guo Ren
The handle_irq_perbit function loop every bit in hwirq local variable.
handle_irq_perbit(hwirq) {
for_everyt_bit_in(hwirq) {
handle_domain_irq()
->irq_exit()
->invoke_softirq()
->__do_softirq()
->local_irq_en
From: Guo Ren
core/ cBPF-JIT : TODO |
core/ eBPF-JIT : TODO |
core/ generic-idle-thread : ok |
core/ jump-labels : TODO |
core/ tracehook: ok |
debug/ KASAN: TODO |
debug/ gcov-profile-all
From: Guo Ren
For I/O access, 810/807 store instruction fast retire will cause wrong
primitive. For example:
stw (clear interrupt source)
stw (unmask interrupt controller)
enable interrupt
stw is fast retire instruction. When PC is run at enable interrupt
stage, the clea
From: Guo Ren
Commit: 4cf58924951e remove the address argument of pte_alloc without
modify csky related code. linux-5.0-rc1 compile failed with csky.
Remove the unnecessary address testing in pte_alloc().
Signed-off-by: Guo Ren
Cc: Joel Fernandes (Google)
Cc: Guenter Roeck
Cc: Arnd Bergmann
On 01/07/2019 09:04 PM, Dave Chinner wrote:
> On Mon, Jan 07, 2019 at 05:41:39PM -0500, Waiman Long wrote:
>> On 01/07/2019 05:32 PM, Dave Chinner wrote:
>>> On Mon, Jan 07, 2019 at 10:12:56AM -0500, Waiman Long wrote:
As newer systems have more and more IRQs and CPUs available in their
s
On Mon, Jan 07, 2019 at 04:18:47PM -0700, Jonathan Corbet wrote:
> On Mon, 7 Jan 2019 15:16:22 -0800
> Guenter Roeck wrote:
>
> > > Applied, thanks.
> > >
> > Ok, I'll drop the patch from hwmon.
>
> Oops, sorry, I didn't realize you'd picked that up. Would you prefer that
> I stood back an
On 01/08/2019 11:11 AM, Michal Hocko wrote:
> On Tue 08-01-19 13:04:22, Dave Chinner wrote:
>> On Mon, Jan 07, 2019 at 05:41:39PM -0500, Waiman Long wrote:
>>> On 01/07/2019 05:32 PM, Dave Chinner wrote:
On Mon, Jan 07, 2019 at 10:12:56AM -0500, Waiman Long wrote:
> As newer systems have m
On 01/08/2019 12:05 PM, Waiman Long wrote:
> On 01/08/2019 11:11 AM, Michal Hocko wrote:
>> On Tue 08-01-19 13:04:22, Dave Chinner wrote:
>>> On Mon, Jan 07, 2019 at 05:41:39PM -0500, Waiman Long wrote:
On 01/07/2019 05:32 PM, Dave Chinner wrote:
> On Mon, Jan 07, 2019 at 10:12:56AM -0500,
On Tue, Jan 8, 2019 at 8:27 AM wrote:
>
> + for (i = 0; i < PAGE_SIZE/sizeof(pte_t); i++)
> + (pte + i)->pte_low = _PAGE_GLOBAL;
When I first read this, I went "hmm. pte_high is not initialized".
But csky doesn't have a pte_high, and it seems that csky and SH both
decided to
From: Michal Hocko
[ Upstream commit 7550c6079846a24f30d15ac75a941c8515dbedfb ]
Patch series "THP eligibility reporting via proc".
This series of three patches aims at making THP eligibility reporting much
more robust and long term sustainable. The trigger for the change is a
regression report
From: Michal Hocko
[ Upstream commit 7550c6079846a24f30d15ac75a941c8515dbedfb ]
Patch series "THP eligibility reporting via proc".
This series of three patches aims at making THP eligibility reporting much
more robust and long term sustainable. The trigger for the change is a
regression report
From: Michal Hocko
[ Upstream commit 7550c6079846a24f30d15ac75a941c8515dbedfb ]
Patch series "THP eligibility reporting via proc".
This series of three patches aims at making THP eligibility reporting much
more robust and long term sustainable. The trigger for the change is a
regression report
Add a script to the tools/ directory that shows if or why the running kernel was
tainted. The script was mostly written by Randy Dunlap (thx!), who published it
while discussing changes that try to make admin-guide/tainted-kernels.rst more
comprehensible (
https://lore.kernel.org/lkml/8f67a8ca-bf64
While working on an update for reporting-bugs.rst I noticed there is no easy
comprehensible document showing how to check if or why the running kernel might
be tainted. That's why I started updating the document which in the end became
nearly a rewrite.
Main goal was to make decoding /proc/sys/ker
Hi! This is the second version of my patch to make
admin-guide/tainted-kernels.rst more comprehensible. It got triggered while
working on an update for reporting-bugs.rst, as improving the documentation
around reporting bugs and regressions was one of the main things that a lot of
people wanted to
From: Michal Hocko
[ Upstream commit 7550c6079846a24f30d15ac75a941c8515dbedfb ]
Patch series "THP eligibility reporting via proc".
This series of three patches aims at making THP eligibility reporting much
more robust and long term sustainable. The trigger for the change is a
regression report
From: Michal Hocko
[ Upstream commit 7550c6079846a24f30d15ac75a941c8515dbedfb ]
Patch series "THP eligibility reporting via proc".
This series of three patches aims at making THP eligibility reporting much
more robust and long term sustainable. The trigger for the change is a
regression report
From: Michal Hocko
[ Upstream commit 7550c6079846a24f30d15ac75a941c8515dbedfb ]
Patch series "THP eligibility reporting via proc".
This series of three patches aims at making THP eligibility reporting much
more robust and long term sustainable. The trigger for the change is a
regression report
On 1/7/19 11:52 AM, Christophe de Dinechin wrote:
> The URL of [api-spec] in Documentation/virtual/kvm/amd-memory-encryption.rst
> is no longer valid, replaced space with underscore.
>
> Signed-off-by: Christophe de Dinechin
thanks
Reviewed-by: Brijesh Singh
Make syscall_get_arch() distinguish arm64 and arm64/ilp32 by adding
AUDIT_ARCH_AARCH64ILP32.
Sugested-by: Andy Lutomirski
Signed-off-by: Yury Norov
---
arch/arm64/include/asm/syscall.h | 3 +++
include/uapi/linux/audit.h | 1 +
2 files changed, 4 insertions(+)
diff --git a/arch/arm64/inc
Of the tunables available for the bfq I/O scheduler,
the only one missing from the documentation in
'Documentation/block/bfq-iosched.txt' is slice_idle_us.
Add this tunable to the documentation and a short
explanation of its purpose.
Signed-off-by: John Pittman
---
Documentation/block/bfq-iosche
On Tue, Jan 08, 2019 at 09:21:34AM +, claudiu.bez...@microchip.com wrote:
> Hi Uwe,
>
> On 08.01.2019 00:10, Uwe Kleine-König wrote:
> > Hello Claudiu,
> >
> > On Mon, Jan 07, 2019 at 09:30:55AM +, claudiu.bez...@microchip.com
> > wrote:
> >> On 05.01.2019 23:05, Uwe Kleine-König wrote:
On Tue, Jan 08, 2019 at 11:58:26AM -0500, Waiman Long wrote:
> On 01/07/2019 09:04 PM, Dave Chinner wrote:
> > On Mon, Jan 07, 2019 at 05:41:39PM -0500, Waiman Long wrote:
> >> On 01/07/2019 05:32 PM, Dave Chinner wrote:
> >>> On Mon, Jan 07, 2019 at 10:12:56AM -0500, Waiman Long wrote:
> > What I
On Tue, 8 Jan 2019 20:40:05 +0100
Thorsten Leemhuis wrote:
> Hi! This is the second version of my patch to make
> admin-guide/tainted-kernels.rst more comprehensible. It got triggered while
> working on an update for reporting-bugs.rst, as improving the documentation
> around reporting bugs and
Old cpuidle/sysfs.txt file was replaced in aa5eee355b46. So, refer to
an updated file.
Fixes: aa5eee355b46 ("Documentation: admin-guide: PM: Add cpuidle document")
Signed-off-by: Otto Sabart
---
Documentation/trace/coresight-cpu-debug.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
di
From: Huaisheng Ye
This patch set could be used for dm-writecache when use persistent
memory as cache data device.
Patch 1 and 2 go towards removing unused parameter and codes which
actually doesn't really work.
Patch 3 and 4 are targeted at solving problem fn ctr failed to work
due to invalid
From: Huaisheng Ye
writecache_flush_region doesn't use size to calculate flush region.
That uses _set_bits to mark the region in dirty_bitmap directly.
Signed-off-by: Huaisheng Ye
---
drivers/md/dm-writecache.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/dr
From: Huaisheng Ye
writecache_flush_region only works when SSD mode.
If wc->pmem_mode sets, writecache_flush_region doesn't need to be called in
writecache_flush_entry.
Signed-off-by: Huaisheng Ye
---
drivers/md/dm-writecache.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/md/dm
From: Huaisheng Ye
When use persistent memory as cache data device, sometimes
the super block of pmem has messy data stored in it. That would
have risk to lead fn ctr failed to work due to invalid magic or
version.
Here we expand pmem_reinit to optional parameters in order to solve
this issue. W
From: Huaisheng Ye
Add intro and usage guide for reinit.
Signed-off-by: Huaisheng Ye
---
Documentation/device-mapper/writecache.txt | 4
1 file changed, 4 insertions(+)
diff --git a/Documentation/device-mapper/writecache.txt
b/Documentation/device-mapper/writecache.txt
index 01532b3..25
> Il giorno 8 gen 2019, alle ore 22:56, John Pittman ha
> scritto:
>
> Of the tunables available for the bfq I/O scheduler,
> the only one missing from the documentation in
> 'Documentation/block/bfq-iosched.txt' is slice_idle_us.
> Add this tunable to the documentation and a short
> explanat
35 matches
Mail list logo
