So far, powerpc Book3S code has been written with an assumption of
only one watchpoint. But Power10[1] is introducing second watchpoint
register (DAWR). Even though this patchset does not enable 2nd DAWR,
it makes the infrastructure ready so that enabling 2nd DAWR should
just be a matter of
So far we had only one watchpoint, so we have hardcoded HBP_NUM to 1.
But Power10 is introducing 2nd DAWR and thus kernel should be able to
dynamically find actual number of watchpoints supported by hw it's
running on. Introduce function for the same. Also convert HBP_NUM macro
to HBP_NUM_MAX,
Power10 is introducing second DAWR. Add SPRN_ macros for the same.
Signed-off-by: Ravi Bangoria
Reviewed-by: Michael Neuling
---
arch/powerpc/include/asm/reg.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/powerpc/include/asm/reg.h b/arch/powerpc/include/asm/reg.h
index
Power10 is introducing second DAWR. Use real register names from ISA
for current macros:
s/SPRN_DAWR/SPRN_DAWR0/
s/SPRN_DAWRX/SPRN_DAWRX0/
Signed-off-by: Ravi Bangoria
Reviewed-by: Michael Neuling
---
arch/powerpc/include/asm/reg.h | 4 ++--
arch/powerpc/kernel/dawr.c
On Sat, May 09, 2020 at 12:01:31AM +0200, Arnd Bergmann wrote:
> In order to call kmap_atomic() etc, we need to include linux/highmem.h:
>
> drivers/gpu/drm/vmwgfx/vmwgfx_blit.c: In function 'vmw_bo_cpu_blit_line':
> drivers/gpu/drm/vmwgfx/vmwgfx_blit.c:377:4: error: implicit declaration of
>
Modified the patch subject and the change description.
PC value is get from regs[15] in REGS_ABI_32 mode, but correct PC
is regs->pc(regs[PERF_REG_ARM64_PC]) in arm64 kernel, which caused
that perf can not parser the backtrace of app with dwarf mode in the
32bit system and 64bit kernel.
On Sat, 9 May 2020 17:27:36 +0800 Huazhong Tan wrote:
> This patchset includes some misc updates for the HNS3 ethernet driver.
>
> #1 & #2 add two cleanups.
> #3 provides an interface for the client to query the CMDQ's status.
> #4 adds a little optimization about debugfs.
> #5 prevents 1000M
On Mon, 11 May 2020 08:13:06 +0800 tanhuazhong wrote:
> On 2020/5/10 4:48, Jakub Kicinski wrote:
> > On Sat, 9 May 2020 17:27:39 +0800 Huazhong Tan wrote:
> >> diff --git a/drivers/net/ethernet/hisilicon/hns3/hnae3.h
> >> b/drivers/net/ethernet/hisilicon/hns3/hnae3.h
> >> index 5602bf2..7506cab
Hi Gwendal,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on iio/togreg]
[also build test ERROR on chrome-platform-linux/for-next linus/master v5.7-rc5
next-20200508]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system.
On Mon, May 11, 2020 at 08:06:29AM +0800, Lai Jiangshan wrote:
> On Sun, May 10, 2020 at 11:49 PM Paul E. McKenney wrote:
> >
> > On Sun, May 10, 2020 at 05:59:27PM +0800, Lai Jiangshan wrote:
> > > On Tue, Mar 17, 2020 at 6:03 AM Steven Rostedt
> > > wrote:
> > > >
> > > > On Mon, 16 Mar 2020
if some function in ndo_stop interface returns failure because of
hardware fault, must go on excuting rest steps rather than return
failure directly, otherwise will cause memory leak.And bump the
timeout for SET_FUNC_STATE to ensure that cmd won't return failure
when hw is busy. Otherwise hw may
Hi Sebastian,
On 2020-05-10 1:08 p.m., Sebastian Reichel wrote:
> Hi,
>
> On Mon, May 04, 2020 at 03:13:00PM -0700, Jonathan Bakker wrote:
>> According to the datasheet (1), the rcomp parameter can
>> vary based on the typical operating temperature and the
>> battery chemistry. If provided,
In order not to enlarge slub meta-data size, so we move free track
from slub meta-data (struct kasan_alloc_meta) into freed object.
Modification of struct kasan_alloc_meta:
- add two call_rcu() stack into kasan_alloc_meta, size is 8 bytes.
- remove free track from kasan_alloc_meta, size is 8
Generic KASAN will support to record first and last call_rcu() call
stack and print them in KASAN report. so we update documentation.
Signed-off-by: Walter Wu
Cc: Andrey Ryabinin
Cc: Dmitry Vyukov
Cc: Alexander Potapenko
Cc: Jonathan Corbet
---
Documentation/dev-tools/kasan.rst | 6 ++
This feature will record first and last call_rcu() call stack and
print two call_rcu() call stack in KASAN report.
When call_rcu() is called, we store the call_rcu() call stack into
slub alloc meta-data, so that KASAN report can print rcu stack.
It doesn't increase the cost of memory
This patchset improves KASAN reports by making them to have
call_rcu() call stack information. It is useful for programmers
to solve use-after-free or double-free memory issue.
The KASAN report was as follows(cleaned up slightly):
BUG: KASAN: use-after-free in kasan_rcu_reclaim+0x58/0x60
Freed
HUGETLBFS only used when MMU enabled, add the dependence.
Reported-by: Hulk Robot
Signed-off-by: Kefeng Wang
---
arch/riscv/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
index 494e670520ae..d0010ed8e0f4 100644
--- a/arch/riscv/Kconfig
+++
DEBUG_VIRTUAL should only used when MMU enabled, add the dependence.
Signed-off-by: Kefeng Wang
---
arch/riscv/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
index 7da0a36a8df0..494e670520ae 100644
--- a/arch/riscv/Kconfig
+++
In file included from ./../include/linux/compiler_types.h:68,
from :
../include/asm-generic/mmiowb.h: In function ‘mmiowb_set_pending’:
../include/asm-generic/percpu.h:34:38: error: implicit declaration of function
‘smp_processor_id’; did you mean ‘raw_smp_processor_id’?
arch/riscv/mm/init.c: In function ‘print_vm_layout’:
arch/riscv/mm/init.c:68:37: error: ‘FIXADDR_START’ undeclared (first use in
this function);
arch/riscv/mm/init.c:69:20: error: ‘FIXADDR_TOP’ undeclared
arch/riscv/mm/init.c:70:37: error: ‘PCI_IO_START’ undeclared
arch/riscv/mm/init.c:71:20:
ERROR: modpost: "riscv_time_val" [crypto/tcrypt.ko] undefined!
Reported-by: Hulk Robot
Signed-off-by: Kefeng Wang
---
drivers/clocksource/timer-riscv.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clocksource/timer-riscv.c
b/drivers/clocksource/timer-riscv.c
index
'KDBFLAGS' is an internal variable of kdb, it is combined by 'KDBDEBUG'
and state flags. But the user can define an environment variable named
'KDBFLAGS' too, so let's make it undefinable to avoid confusion.
Signed-off-by: Wei Li
---
kernel/debug/kdb/kdb_main.c | 3 ++-
1 file changed, 2
When add RISCV arch to huawei build test, there are some build
issue, let's fix them to make riscv build happier :)
Those patches is rebased on next-20200508.
Kefeng Wang (10):
riscv: Fix unmet direct dependencies built based on SOC_VIRT
riscv: stacktrace: Fix undefined reference to
Some drivers use PAGE_SHARED, pgprot_writecombine()/pgprot_device(),
add the defination to fix build error if NOMMU.
Reported-by: Hulk Robot
Signed-off-by: Kefeng Wang
---
arch/riscv/include/asm/mmio.h| 2 ++
arch/riscv/include/asm/pgtable.h | 1 +
2 files changed, 3 insertions(+)
diff
Drop static declaration to fix following build error if FRAME_POINTER disabled,
riscv64-linux-ld: arch/riscv/kernel/perf_callchain.o: in function `.L0':
perf_callchain.c:(.text+0x2b8): undefined reference to `walk_stackframe'
Reported-by: Hulk Robot
Signed-off-by: Kefeng Wang
---
riscv64-none-linux-gnu-ld: mm/page_alloc.o: in function `.L0 ':
page_alloc.c:(.text+0xd34): undefined reference to `__kernel_map_pages'
riscv64-none-linux-gnu-ld: page_alloc.c:(.text+0x104a): undefined reference to
`__kernel_map_pages'
riscv64-none-linux-gnu-ld: mm/page_alloc.o: in function
Fix unmet direct dependencies Warning and fix Kconfig indent.
WARNING: unmet direct dependencies detected for POWER_RESET_SYSCON
Depends on [n]: POWER_RESET [=n] && OF [=y] && HAS_IOMEM [=y]
Selected by [y]:
- SOC_VIRT [=y]
WARNING: unmet direct dependencies detected for
DEBUG_WX is only useful when MMU enabled, diable it if nommu
and fix the build error.
Reported-by: Hulk Robot
Signed-off-by: Kefeng Wang
---
arch/riscv/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
index
From: Kiwoong Kim
Some controller like Exynos determines if FATAL ERROR (0x7)
in OCS field in UTRD occurs for values other than GOOD (0x0)
in STATUS field in response upiu as well as errors that a
host controller can't cover.
This patch is to prevent from reporting command results in
those
This patch adds DT binding for samsung ufs hci
Signed-off-by: Alim Akhtar
---
.../bindings/ufs/samsung,exynos-ufs.yaml | 92 +++
1 file changed, 92 insertions(+)
create mode 100644
Documentation/devicetree/bindings/ufs/samsung,exynos-ufs.yaml
diff --git
In the right behavior, setting the bit to '0' indicates clear and '1'
indicates no change. If host controller handles this the other way,
UFSHCI_QUIRK_BROKEN_REQ_LIST_CLR can be used.
Reviewed-by: Can Guo
Reviewed-by: Avri Altman
Signed-off-by: Seungwon Jeon
Signed-off-by: Alim Akhtar
---
This patch documents Samsung UFS PHY device tree bindings
Reviewed-by: Rob Herring
Signed-off-by: Alim Akhtar
Tested-by: Paweł Chmiel
---
.../bindings/phy/samsung,ufs-phy.yaml | 75 +++
1 file changed, 75 insertions(+)
create mode 100644
This patch introduces Samsung UFS PHY driver. This driver
supports to deal with phy calibration and power control
according to UFS host driver's behavior.
Reviewed-by: Kiwoong Kim
Signed-off-by: Seungwon Jeon
Signed-off-by: Alim Akhtar
Cc: Kishon Vijay Abraham I
Tested-by: Paweł Chmiel
---
This patch introduces Exynos UFS host controller driver,
which mainly handles vendor-specific operations including
link startup, power mode change and hibernation/unhibernation.
Reported-by: kbuild test robot
Reported-by: Julia Lawall
[robot: drivers/scsi/ufs/ufs-exynos.c:931:8-10:
WARNING:
Adding dt node foe UFS and UFS-PHY for exynos7 SoC.
Signed-off-by: Alim Akhtar
Tested-by: Paweł Chmiel
---
.../boot/dts/exynos/exynos7-espresso.dts | 4 ++
arch/arm64/boot/dts/exynos/exynos7.dtsi | 44 ++-
2 files changed, 46 insertions(+), 2 deletions(-)
diff
On 05/09/2020 04:29 PM, Marc Zyngier wrote:
> On Fri, 08 May 2020 03:52:38 +0100,
> Anshuman Khandual wrote:
>>
>> This validates hypervisor capabilities like VMID width, IPA range for any
>> hot plug CPU against system finalized values. While here, it factors out
>> get_vmid_bits() for
Some host controllers don't support host controller enable via HCE.
Reviewed-by: Can Guo
Reviewed-by: Avri Altman
Signed-off-by: Seungwon Jeon
Signed-off-by: Alim Akhtar
---
drivers/scsi/ufs/ufshcd.c | 76 +--
drivers/scsi/ufs/ufshcd.h | 6
2 files
This patch-set introduces UFS (Universal Flash Storage) host controller support
for Samsung family SoC. Mostly, it consists of UFS PHY and host specific driver.
- Changes since v7:
* fixed review comments from Rob and Kishon
* Addeded reviwed-by tags
* rebased on top of v5.7-rc4
- Changes since
Some UFS host controllers like Exynos uses granularities of PRDT length and
offset as bytes, whereas others uses actual segment count.
Reviewed-by: Avri Altman
Signed-off-by: Kiwoong Kim
Signed-off-by: Alim Akhtar
---
drivers/scsi/ufs/ufshcd.c | 30 +++---
Some host controllers support interrupt aggregation but don't allow
resetting counter and timer in software.
Reviewed-by: Avri Altman
Signed-off-by: Seungwon Jeon
Signed-off-by: Alim Akhtar
---
drivers/scsi/ufs/ufshcd.c | 3 ++-
drivers/scsi/ufs/ufshcd.h | 6 ++
2 files changed, 8
Hello Mark
On Fri, May 08, 2020 at 12:53:34PM +0100, Mark Brown wrote:
> On Fri, May 08, 2020 at 02:26:04PM +0300, Andy Shevchenko wrote:
> > On Fri, May 08, 2020 at 01:53:02PM +0300, Serge Semin wrote:
>
> > > Multi-block support provides a way to map the kernel-specific SG-table so
> > > the
Will fix. Thanks.
On 2020/5/10 6:37, Jakub Kicinski wrote:
On Fri, 8 May 2020 20:19:33 + Luo bin wrote:
if some function in ndo_stop interface returns failure because of
hardware fault, must go on excuting rest steps rather than return
failure directly, otherwise will cause memory leak.And
> -Original Message-
> From: Jin, Yao
> Sent: 2020年5月11日 9:12
> To: kajoljain ; Joakim Zhang
> ; a...@kernel.org; Jiri Olsa ;
> Andi Kleen
> Cc: linux-kernel@vger.kernel.org; linux-perf-us...@vger.kernel.org; Kan Liang
> ; Madhavan Srinivasan
> ; Anju T Sudhakar ;
> Ravi Bangoria
>
Hello Dmitry
Thanks for your comment and test,
can you let me know which platform (board) you are using for test,
and DTS changes if you have added any.
Thanks,
Jiada
On 2020/05/11 10:05, Dmitry Osipenko wrote:
08.05.2020 08:56, Jiada Wang пишет:
The path of enabling the IRQ in the probe
On Fri, May 08, 2020 at 12:01:22PM -0400, Johannes Weiner wrote:
> On Thu, Apr 23, 2020 at 02:25:06PM +0900, Joonsoo Kim wrote:
> > On Wed, Apr 22, 2020 at 08:09:46AM -0400, Johannes Weiner wrote:
> > > On Wed, Apr 22, 2020 at 03:40:41PM +0900, Joonsoo Kim wrote:
> > > > On Mon, Apr 20, 2020 at
On Sun, May 10, 2020 at 05:16:28PM +0100, Valentin Schneider wrote:
>
> On 10/05/20 13:56, Pavankumar Kondeti wrote:
> > The intention of commit 96e74ebf8d59 ("sched/debug: Add task uclamp
> > values to SCHED_DEBUG procfs") was to print requested and effective
> > task uclamp values. The
On 2020/5/11 9:11, Stephen Rothwell wrote:
Hi all,
Today's linux-next merge of the vfs tree got a conflict in:
kernel/sysctl.c
between commit:
b6522fa409cf ("parisc: add sysctl file interface panic_on_stackoverflow")
from the parisc-hd tree and commit:
f461d2dcd511 ("sysctl: avoid
The intention of commit 96e74ebf8d59 ("sched/debug: Add task uclamp
values to SCHED_DEBUG procfs") was to print requested and effective
task uclamp values. The requested values printed are read from p->uclamp,
which holds the last effective values. Fix this by printing the values
from
From: Koba Ko
On dell G3-3590, error message is issued during boot up,
"platform::micmute: Setting an LED's brightness failed (-19)",
but there's no micmute led on the machine.
Get the related tokens of SMBIOS, GLOBAL_MIC_MUTE_DISABLE/ENABLE.
If one of two tokens doesn't exist,
don't call
Commit de462e5f1071 ("bootconfig: Fix to remove bootconfig
data from initrd while boot") causes a cosmetic regression
on dmesg, which warns "no bootconfig data" message without
bootconfig cmdline option.
Fix setup_boot_config() by moving no bootconfig check after
commandline option check.
Fixes:
On 5/10/20 6:53 PM, Christophe JAILLET wrote:
> In some error handling paths, a call to 'iio_channel_get()' is not balanced
> by a corresponding call to 'iio_channel_release()'.
>
> This can be achieved easily by using the devm_ variant of
> 'iio_channel_get()'.
>
> This has the extra benefit to
On 5/11/20 9:16 AM, Matthew Wilcox wrote:
On Mon, May 11, 2020 at 09:09:57AM +0800, kernel test robot wrote:
--- tests/btrfs/095.out2020-04-09 10:45:28.0 +0800
+++ /lkp/benchmarks/xfstests/results//btrfs/095.out.bad2020-05-06
21:13:51.276485703 +0800
@@ -1,35
On Mon, 2020-05-11 at 09:24 +0800, chenzhou wrote:
> Sorry, i made a mistake, should be scnprintf().
No worries.
But why do you think this is useful?
Is it likely that either snprint length will exceed PAGE_SIZE?
>
> On 2020/5/9 19:40, Joe Perches wrote:
> > On Sat, 2020-05-09 at 17:18 +0800,
On 2020/5/9 1:13, Palmer Dabbelt wrote:
What's the "-next" for? This seems appropriate for an RC to me, as
it's a
build fix.
Thanks for your review, this patch and "[PATCH -next] riscv: perf:
RISCV_BASE_PMU
should be closeable", I fix the issue based on linux-next, so add the
next
Hi Yongbo
Thank you for the patch
> SSI BUSIF buffer is possible to overflow or underflow, especially in a
> hypervisor environment. If there is no interrupt support, it will eventually
> lead to errors in pcm data.
> This patch adds overflow and underflow interrupt support for SSI BUSIF
On Sun, May 10, 2020 at 12:44:53AM -0700, Sagi Grimberg wrote:
>
> > > > > You're mostly correct. This is exactly why an I/O scheduler may be
> > > > > applicable here IMO. Mostly because I/O schedulers tend to optimize
> > > > > for
> > > > > something specific and always present tradeoffs.
On 2020/5/10 3:03, Jaegeuk Kim wrote:
> On 05/09, Chao Yu wrote:
>> On 2020/5/9 0:10, Jaegeuk Kim wrote:
>>> Hi Sayali,
>>>
>>> In order to address the perf regression, how about this?
>>>
>>> >From 48418af635884803ffb35972df7958a2e6649322 Mon Sep 17 00:00:00 2001
>>> From: Jaegeuk Kim
>>> Date:
Sorry, i made a mistake, should be scnprintf().
On 2020/5/9 19:40, Joe Perches wrote:
> On Sat, 2020-05-09 at 17:18 +0800, Chen Zhou wrote:
>> snprintf() returns the number of bytes that would be written,
>> which may be greater than the the actual length to be written.
> []
>> Chen Zhou (2):
>>
On Fri, 8 May 2020, Guilherme Piccoli wrote:
> On Fri, May 8, 2020 at 3:31 PM David Rientjes wrote:
> > It doesn't make sense because it's only being done here for the entire
> > system, there are also per-node sysfs triggers so you could do something
> > like iterate over the nodemask of all
On 05/05/20 at 09:20am, Qian Cai wrote:
>
>
> > On May 5, 2020, at 8:43 AM, Baoquan He wrote:
> >
> > Hi,
> >
> > On 04/24/20 at 09:45am, Qian Cai wrote:
> >>
> >>
> >>> On Apr 23, 2020, at 11:43 PM, Baoquan He wrote:
> >>>
> >>> On 04/23/20 at 05:25pm, Qian Cai wrote:
> Compaction
On Mon, May 11, 2020 at 09:09:57AM +0800, kernel test robot wrote:
> --- tests/btrfs/095.out 2020-04-09 10:45:28.0 +0800
> +++ /lkp/benchmarks/xfstests/results//btrfs/095.out.bad 2020-05-06
> 21:13:51.276485703 +0800
> @@ -1,35 +1,9 @@
> QA output created by 095
>
From: Koba Ko
On dell G3-3590, error message is issued during boot up,
"platform::micmute: Setting an LED's brightness failed (-19)",
but there's no micmute led on the machine.
Get the related tokens of SMBIOS, GLOBAL_MIC_MUTE_DISABLE/ENABLE.
If one of two tokens doesn't exist,
don't call
Hi all,
Today's linux-next merge of the vfs tree got a conflict in:
arch/mips/lasat/sysctl.c
between commit:
10760dde9be3 ("MIPS: Remove support for LASAT")
from the mips tree and commit:
32927393dc1c ("sysctl: pass kernel pointers to ->proc_handler")
from the vfs tree.
I fixed it up
Hi Kajol,
On 3/24/2020 4:00 PM, kajoljain wrote:
Hello All,
I want to discuss one issue raised by Joakim Zhang where he mentioned
that, we are not getting correct result in-case of multiple events present in
metric
expression.
This is one example pointed by him :
below is the JSON
On 5/10/2020 1:15 PM, Andy Lutomirski wrote:
On Fri, May 8, 2020 at 8:04 PM Xiaoyao Li wrote:
When running as guest, enumerating feature split lock detection through
CPU model is not easy since CPU model is configurable by host VMM.
If running upon KVM, it can be enumerated through
On 2020/5/9 19:21, YueHaibing wrote:
> update_sit_info should be f2fs_update_sit_info,
> otherwise build fails while no CONFIG_F2FS_STAT_FS.
>
> Fixes: fc7100ea2a52 ("f2fs: Add f2fs stats to sysfs")
> Signed-off-by: YueHaibing
Reviewed-by: Chao Yu
Thanks,
On 05/10/20 at 02:22pm, Rafael Aquini wrote:
> > > diff --git a/Documentation/admin-guide/kernel-parameters.txt
> > > b/Documentation/admin-guide/kernel-parameters.txt
> > > index 7bc83f3d9bdf..4a69fe49a70d 100644
> > > --- a/Documentation/admin-guide/kernel-parameters.txt
> > > +++
Hi all,
Today's linux-next merge of the vfs tree got a conflict in:
kernel/sysctl.c
between commit:
b6522fa409cf ("parisc: add sysctl file interface panic_on_stackoverflow")
from the parisc-hd tree and commit:
f461d2dcd511 ("sysctl: avoid forward declarations")
from the vfs tree.
I
On Thu, 2020-05-07 at 13:59 -0500, Gustavo A. R. Silva wrote:
> The current codebase makes use of the zero-length array language
> extension to the C90 standard, but the preferred mechanism to declare
> variable-length types such as these ones is a flexible array
> member[1][2],
> introduced in
08.05.2020 08:56, Jiada Wang пишет:
> The path of enabling the IRQ in the probe function is not safe in level
> triggered operation, if it was already powered up and there is a message
> waiting on the device (eg finger down) because the object table has not yet
> been read. This forces the ISR
On Tue, May 5, 2020 at 7:15 AM Thomas Gleixner wrote:
>
> Provide DECLARE/DEFINE_IDTENTRY() macros.
Acked-by: Andy Lutomirski
except:
>
> DEFINE_IDTENTRY() provides a wrapper which acts as the function
> definition. The exception handler body is just appended to it with curly
> brackets. The
Hi Sudeep,
Yes, mailbox client does not need to know how controller implemented. I
will check with mailbox driver. Thanks!
Regards,
Joe
-邮件原件-
发件人: Sudeep Holla [mailto:sudeep.ho...@arm.com]
发送时间: 2020年5月9日 23:20
收件人: joe_zhu...@126.com
抄送: linux-arm-ker...@lists.infradead.org;
On Sun, 10 May 2020 19:16:47 +0200
Paul Menzel wrote:
> Dear Masami,
>
>
> Commit de462e5f10 (bootconfig: Fix to remove bootconfig data from initrd
> while boot) causes a cosmetic regression on my x86 system with Debian
> Sid/unstable.
>
> Despite having no `bootconfig` parameter on the
On Sat, May 09, 2020 at 05:52:53AM +, Joakim Zhang wrote:
>
> Hi Arnaldo,
>
> Kajol reflects this issue for almost two months, got no feedbacks, do you
> have any comments? That could be appreciated if you can look into it. Thanks
> a lot!
Jin Yao did a lot of fixes to metrics recently.
Hi all,
After merging the clk tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
arch/arm/mach-mmp/time.c:37:10: fatal error: clock.h: No such file or directory
37 | #include "clock.h"
| ^
Caused by commit
e4d1fdf89751 ("ARM: mmp: Remove
On Tue, May 5, 2020 at 7:15 AM Thomas Gleixner wrote:
>
> From: Thomas Gleixner
>
> 32 and 64 bit have unnecessary different ways to populate the exception
> entry code. Provide a idtentry macro which allows to consolidate all of
> that.
>
> Signed-off-by: Thomas Gleixner
> Reviewed-by:
> My interest in this is that we have a few workloads that value the
> ability to access FS/GS base directly and show nice performance
Can you please share some rough numbers, Sasha?
I would expect everything that does a lot of context switches
to benefit automatically, apart from the new free
> So this is a check that checks if you're running in user mode if
> you have a debug trap with single step, but somehow it triggered
> for a user segment.
>
> Probably the regs got corrupted.
>
> Sasha, I suspect you're missing a mov %rsp,%rdi somewhere in the
> debug entry path that sets up
> [ 6402.786418] [ cut here ]
> [ 6402.787769] WARNING: CPU: 0 PID: 13802 at arch/x86/kernel/traps.c:811
> do_debug+0x16c/0x210
...
> [ 6402.848299] ? trace_hardirqs_off_thunk+0x1a/0x33
> [ 6402.849593] trace_hardirqs_off_caller+0xa6/0xd0
> [ 6402.850862] ?
On Sun, 10 May 2020 17:59:27 +0800
Lai Jiangshan wrote:
> On Tue, Mar 17, 2020 at 6:03 AM Steven Rostedt wrote:
> >
> > On Mon, 16 Mar 2020 17:45:40 -0400
> > Joel Fernandes wrote:
> >
> > > >
> > > > Same for the function side (if not even more so). This would require
> > > > adding
> > > >
On Fri, May 08, 2020 at 05:40:46PM +0200, Thomas Bogendoerfer wrote:
> On Wed, May 06, 2020 at 08:42:37PM +0300, sergey.se...@baikalelectronics.ru
> wrote:
> > diff --git a/arch/mips/kernel/cevt-r4k.c b/arch/mips/kernel/cevt-r4k.c
> > index 17a9cbb8b3df..f5b72fb7d5ee 100644
> > ---
On Sun, 10 May 2020, Markus Elfring wrote:
> >
> > Do you know when these bugs were introduced?
>
> I suggest to take another look at a provided tag “Fixes”.
If you can't determine when the bug was introduced, how can you criticise
a patch for the lack of a Fixes tag?
> To which commit would
On 2020/5/10 4:48, Jakub Kicinski wrote:
On Sat, 9 May 2020 17:27:39 +0800 Huazhong Tan wrote:
This patch provides a new interface for the client to query
whether CMDQ is ready to work.
Signed-off-by: Huazhong Tan
diff --git a/drivers/net/ethernet/hisilicon/hns3/hnae3.h
On Sun, May 10, 2020 at 11:49 PM Paul E. McKenney wrote:
>
> On Sun, May 10, 2020 at 05:59:27PM +0800, Lai Jiangshan wrote:
> > On Tue, Mar 17, 2020 at 6:03 AM Steven Rostedt wrote:
> > >
> > > On Mon, 16 Mar 2020 17:45:40 -0400
> > > Joel Fernandes wrote:
> > >
> > > > >
> > > > > Same for the
On Fri, May 08, 2020 at 03:28:09PM +0200, Thomas Bogendoerfer wrote:
> On Wed, May 06, 2020 at 08:42:26PM +0300, sergey.se...@baikalelectronics.ru
> wrote:
> > From: Serge Semin
> > diff --git a/arch/mips/include/asm/cpu-features.h
> > b/arch/mips/include/asm/cpu-features.h
> > index
With current core scheduling patchset, non-threaded IRQ and softirq
victims can leak data from its hyperthread to a sibling hyperthread
running an attacker.
For MDS, it is possible for the IRQ and softirq handlers to leak data to
either host or guest attackers. For L1TF, it is possible to leak to
Hi all,
Today's linux-next merge of the parisc-hd tree got a conflict in:
arch/parisc/Makefile
between commit:
a4e7db3c42bc ("parisc: suppress error messages for 'make clean'")
from the kbuild tree and commit:
0d341e0ddb1a ("parisc: suppress error messages for 'make clean'")
from the
Hi all,
Today's linux-next merge of the mips tree got a conflict in:
arch/mips/loongson2ef/Kconfig
between commit:
bbd7ffdbef68 ("clk: Allow the common clk framework to be selectable")
from the clk tree and commit:
c02e96304451 ("mips: loongsoon2ef: remove private clk api")
from the
Hi Joerg,
On 5/6/20 9:59 AM, Lu Baolu wrote:
Some devices are required to use a specific type (identity or dma) of
default domain when they are used with a vendor iommu. When the system
level default domain type is different from it, the vendor iommu driver
has to request a new default domain
Hi all,
After merging the tegra tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: modpost: "host1x_driver_register_full"
[drivers/staging/media/tegra-video/tegra-video.ko] undefined!
ERROR: modpost: "host1x_device_exit"
So we've had a calm release so far, with most of the rc's up until now
smaller than average.
That changes with rc5, which is still pretty much in line with
historical data, but rather than being slightly on the small side, it
is slightly larger than average for this time in the release cycle.
Hello Rob,
On Fri, May 1, 2020 at 11:53 PM Martin Blumenstingl
wrote:
>
> Hi Rob,
>
> On Fri, May 1, 2020 at 11:09 PM Rob Herring wrote:
> >
> > On Wed, 29 Apr 2020 22:16:35 +0200, Martin Blumenstingl wrote:
> > > The PRG_ETHERNET registers can add an RX delay in RGMII mode. This
> > > requires
On Sat, 9 May 2020, Samuel Zou wrote:
> Fix the following sparse warning:
>
> kernel/livepatch/core.c:748:5: warning: symbol 'klp_apply_object_relocs' was
> not declared.
>
> The klp_apply_object_relocs() has only one call site within core.c
> It should be static
>
> Fixes: 7c8e2bdd5f0d
On Sun, May 10, 2020 at 11:34:49AM -0700, Linus Torvalds wrote:
> On Sun, May 10, 2020 at 5:26 AM Joerg Roedel wrote:
> >
> >The first race condition was around
> > the non-atomic update of the domain page-table root pointer
> > and the variable containing the
On 10/05/20 12:20 pm, Serge Semin wrote:
> On Fri, May 08, 2020 at 12:37:51PM +0100, Mark Brown wrote:
>>> + writel(BIT(req->cs), bs->regs + BC_SPI_SER);
>>> + if (req->cs_gpiod) {
>>> + gpiod_set_value_cansleep(req->cs_gpiod,
>>> +
Hi,
On 2020-05-09 09:42, Christophe Leroy wrote:
> There are other clocks than the standard ones, for instance
> per process clocks. Therefore, being above the last standard clock
> doesn't mean it is a bad clock. So, fallback to syscall instead
> of returning -EINVAL inconditionaly.
>
> Fixes:
On Fri, May 08, 2020 at 11:22:36AM +0200, Thomas Bogendoerfer wrote:
> On Thu, May 07, 2020 at 10:13:37PM +0300, Serge Semin wrote:
> > On Thu, May 07, 2020 at 01:09:51PM +0200, Thomas Bogendoerfer wrote:
> > > On Wed, May 06, 2020 at 08:42:29PM +0300,
> > > sergey.se...@baikalelectronics.ru
On Fri, May 08, 2020 at 02:21:37PM +0200, Thomas Bogendoerfer wrote:
> On Fri, May 08, 2020 at 11:32:59AM +0200, Thomas Bogendoerfer wrote:
> > On Fri, May 08, 2020 at 12:19:23AM +0300, Serge Semin wrote:
> > > On Thu, May 07, 2020 at 01:17:35PM +0200, Thomas Bogendoerfer wrote:
> > > > P5600 is
On Fri, May 08, 2020 at 03:30:40PM +0200, Thomas Bogendoerfer wrote:
> On Wed, May 06, 2020 at 08:42:24PM +0300, sergey.se...@baikalelectronics.ru
> wrote:
> > We also could add CPU_MIPS64_R5 config support here, but I don't think
> > it's necessary at the moment seeing there is no any real chip
On Sat, 9 May 2020, Lukas Bulwahn wrote:
> Commit 1d05334d2899 ("livepatch: Remove .klp.arch") removed
> arch/x86/kernel/livepatch.c, but missed to adjust the LIVE PATCHING entry
> in MAINTAINERS.
>
> Since then, ./scripts/get_maintainer.pl --self-test=patterns complains:
>
> warning: no file
101 - 200 of 561 matches
Mail list logo