On Thu, May 07, 2020 at 02:58:19PM +0800, Jin Yao wrote:
SNIP
> diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> index e0c1ad23c768..97ee941649e6 100644
> --- a/tools/perf/builtin-stat.c
> +++ b/tools/perf/builtin-stat.c
> @@ -351,6 +351,16 @@ static void read_counters(struct
On Thu, May 07, 2020 at 02:58:20PM +0800, Jin Yao wrote:
> The evsel->prev_raw_counts is updated in perf_evsel__compute_deltas:
>
> perf_evsel__compute_deltas()
> {
> tmp = *perf_counts(evsel->prev_raw_counts, cpu, thread);
> *perf_counts(evsel->prev_raw_counts, cpu, thread) = *count;
On Thu, May 07, 2020 at 02:58:21PM +0800, Jin Yao wrote:
> It would be useful to support the overall statistics for perf-stat
> interval mode. For example, report the summary at the end of
> "perf-stat -I" output.
>
> But since perf-stat can support many aggregation modes, such as
> --per-thread,
Am 06.05.20 um 06:52 schrieb Christoph Hellwig:
>
> No, I mean the series that I actually sent out:
>
> https://lkml.org/lkml/2020/4/21/66
> https://lkml.org/lkml/2020/4/21/68
> https://lkml.org/lkml/2020/4/21/69
OK, just thought again about your suggestion and also that
you have already been talk
Hi Mel,
> > Yes, it's indeed OMP. With low threads count, I mean up to 2x number of
> > NUMA nodes (8 threads on 4 NUMA node servers, 16 threads on 8 NUMA node
> > servers).
>
> Ok, so we know it's within the imbalance threshold where a NUMA node can
> be left idle.
we have discussed today with
On Wed, May 6, 2020 at 3:39 PM Daniel Jordan wrote:
>
> On Tue, May 05, 2020 at 08:27:52AM -0700, Alexander Duyck wrote:
> > As it turns out that deferred_free_range will be setting the
> > migratetype for the page. In a sparse config the migratetype bits are
> > stored in the section bitmap. So t
On 5/5/20 3:43 PM, Thomas Gleixner wrote:
Traps enable interrupts conditionally but rely on the ASM return code to
disable them again. That results in redundant interrupt disable and trace
calls.
Make the trap handlers disable interrupts before returning to avoid that,
which allows simplificat
The following commit has been merged into the objtool/urgent branch of tip:
Commit-ID: 1119d265bc20226c241e5540fc8a246d9e30b272
Gitweb:
https://git.kernel.org/tip/1119d265bc20226c241e5540fc8a246d9e30b272
Author:Josh Poimboeuf
AuthorDate:Tue, 28 Apr 2020 16:45:16 -05:00
Com
On Thu, May 07, 2020 at 05:22:28PM +0200, Stefan Haberland wrote:
> OK, just thought again about your suggestion and also that
> you have already been talking about a symbol lookup I just
> have written a prototype that took your first two patches
> as base, exports the symbol of dasd_biodasdinfo a
On Thu, May 07, 2020 at 11:34:55AM +0200, Marco Elver wrote:
> On Wed, 6 May 2020 at 23:47, Paul E. McKenney wrote:
> >
> > On Wed, May 06, 2020 at 12:37:13PM -0700, Paul E. McKenney wrote:
> > > On Wed, May 06, 2020 at 09:11:23PM +0200, Marco Elver wrote:
> > > > On Wed, 6 May 2020 at 20:02, Paul
On Thu, May 07, 2020 at 07:37:50PM +0530, Manivannan Sadhasivam wrote:
> Hi Greg,
>
> On Mon, Apr 20, 2020 at 10:32:02PM +0530, m...@kernel.org wrote:
> > From: Manivannan Sadhasivam
> >
> > Hello,
> >
> > This patchset adds CTS/RTS gpio support to STM32 UART controller.
> > Eventhough the UART
On 5/5/20 3:43 PM, Thomas Gleixner wrote:
From: Thomas Gleixner
So they can be used in ASM code. For this it is also necessary to convert
them to defines. Will be used for the rework of the entry code.
Signed-off-by: Thomas Gleixner
Reviewed-by: Andy Lutomirski
Reviewed-by: Alexandre Chart
Hi Bernard,
On 5/7/20 12:45 PM, Bernard Zhao wrote:
In function create_timings_aligned, all the max is to use
dmc->min_tck->xxx, aligned with val dmc->timings->xxx.
But the dmc->timings->tFAW use dmc->min_tck->tXP?
Maybe this point is wrong parameter useing.
Signed-off-by: Bernard Zhao
---
Am 07.05.20 um 17:29 schrieb Christoph Hellwig:
> On Thu, May 07, 2020 at 05:22:28PM +0200, Stefan Haberland wrote:
>> OK, just thought again about your suggestion and also that
>> you have already been talking about a symbol lookup I just
>> have written a prototype that took your first two patche
On 5/7/2020 1:03 AM, Zheng Zengkai wrote:
> Fix sparse warnings:
>
> drivers/net/phy/mdio-bcm-iproc.c:182:5: warning:
> symbol 'iproc_mdio_resume' was not declared. Should it be static?
>
> Reported-by: Hulk Robot
> Signed-off-by: Zheng Zengkai
Acked-by: Florian Fainelli
--
Florian
On Thu, May 07, 2020 at 05:43:40PM +0200, Stefan Haberland wrote:
> Not checked till now. I just was thinking about the basicapproach.
>
> I could either check the block_device_operations like you suggested
> or I could verify that the gendisk pointer is already in our devmap
> and therefor belong
On 5/4/20 1:39 PM, Pavel Begunkov wrote:
> do_splice() is used by io_uring, as will be do_tee(). Move f_mode
> checks from sys_{splice,tee}() to do_{splice,tee}(), so they're
> enforced for io_uring as well.
Applied for 5.7, thanks.
--
Jens Axboe
On Thu, 7 May 2020 18:59:55 +0900
Masami Hiramatsu wrote:
> Make kprobes to accept 1-level nesting instead of
> diff --git a/arch/x86/kernel/kprobes/ftrace.c
> b/arch/x86/kernel/kprobes/ftrace.c
> index 681a4b36e9bb..b695c2e118f8 100644
> --- a/arch/x86/kernel/kprobes/ftrace.c
> +++ b/arch/x86/
Em Thu, May 07, 2020 at 11:50:19AM +0200, Jiri Olsa escreveu:
> hi,
> sending changes that allows callchain detection in pipe mode,
> fixing followign use case:
>
> # perf record --no-buffering --call-graph dwarf -e sdt_rtld:init_start -a
> -o - | perf --no-pager script -i -
>
> plus change th
On Thu, May 07, 2020 at 05:36:47PM +0800, Hillf Danton wrote:
>
> Hello Paul
>
> On Wed, 6 May 2020 17:42:40 Paul E. McKenney wrote:
> >
> > This commit adds a shrinker so as to inform RCU when memory is scarce.
>
> A simpler hook is added in the logic of kswapd for subscribing the info
> that
On Thu, 7 May 2020 09:12:07 -0400
Steven Rostedt wrote:
> On Sat, 2 May 2020 12:08:42 +0900
> Masami Hiramatsu wrote:
>
> > > > diff --git
> > > > a/tools/testing/selftests/ftrace/test.d/trigger/trigger-trace-marker-hist.tc
> > > >
> > > > b/tools/testing/selftests/ftrace/test.d/trigger/trig
On Thu, May 07, 2020 at 09:48:30AM +0200, Niklas Schnelle wrote:
> On 5/6/20 11:10 PM, Bjorn Helgaas wrote:
> > On Wed, May 06, 2020 at 05:41:38PM +0200, Niklas Schnelle wrote:
> >> currently pci_iov_add_virtfn() scans the SR-IOV bars, adds the VF to the
> >> bus and also creates the sysfs links be
The following commit has been merged into the x86/cpu branch of tip:
Commit-ID: d8422f6bb052b44db923a28afd8ceaef63d38d26
Gitweb:
https://git.kernel.org/tip/d8422f6bb052b44db923a28afd8ceaef63d38d26
Author:Borislav Petkov
AuthorDate:Tue, 05 May 2020 19:25:08 +02:00
Committer
The following commit has been merged into the x86/cpu branch of tip:
Commit-ID: e9d7144597b10ff13ff2264c059f7d4a7fbc89ac
Gitweb:
https://git.kernel.org/tip/e9d7144597b10ff13ff2264c059f7d4a7fbc89ac
Author:Mark Gross
AuthorDate:Thu, 16 Apr 2020 17:23:10 +02:00
Committer:
The following commit has been merged into the x86/cpu branch of tip:
Commit-ID: e2abfc0448a46d8a137505aa180caf14070ec535
Gitweb:
https://git.kernel.org/tip/e2abfc0448a46d8a137505aa180caf14070ec535
Author:Kim Phillips
AuthorDate:Fri, 17 Apr 2020 09:33:56 -05:00
Committer:
Hi Suman
On 4/20/20 6:05 PM, Suman Anna wrote:
> From: Tero Kristo
>
> In some cases, like with OMAP remoteproc, we are not creating dedicated
> memory pool for the virtio device. Instead, we use the same memory pool
> for all shared memories. The current virtio memory pool handling forces
> a s
The following commit has been merged into the x86/cpu branch of tip:
Commit-ID: 66abf2388331b800f290e854cca3ae71de7977fe
Gitweb:
https://git.kernel.org/tip/66abf2388331b800f290e854cca3ae71de7977fe
Author:Borislav Petkov
AuthorDate:Tue, 05 May 2020 19:27:16 +02:00
Committer
On Thu, 07 May 2020 11:22:28 +0200
Andreas Schwab wrote:
> On Mai 01 2020, Masami Hiramatsu wrote:
>
> > Since the built-in echo has different behavior in POSIX shell
> > (dash) and bash, we forcibly use /bin/echo -E (not interpret
> > backslash escapes) by default.
>
> How about using printf i
On 5/7/2020 3:03 AM, Marek Szyprowski wrote:
> Hi
>
> On 07.05.2020 11:46, Marek Szyprowski wrote:
>> On 25.02.2020 14:11, Nicolas Saenz Julienne wrote:
>>> Outdated Raspberry Pi 4 firmware might configure the external PHY as
>>> rgmii although the kernel currently sets it as rgmii-rxid. This m
On Thu, May 07, 2020 at 05:24:17PM +0200, Jirka Hladky wrote:
> Hi Mel,
>
> > > Yes, it's indeed OMP. With low threads count, I mean up to 2x number of
> > > NUMA nodes (8 threads on 4 NUMA node servers, 16 threads on 8 NUMA node
> > > servers).
> >
> > Ok, so we know it's within the imbalance th
On 5/7/20 4:36 AM, Maciej Żenczykowski wrote:
From: Maciej Żenczykowski
__bpf_skb_max_len(skb) is used from:
bpf_skb_adjust_room
__bpf_skb_change_tail
__bpf_skb_change_head
but in the case of forwarding we're likely calling these functions
during receive processing on ingress and bpf_
On 4/29/20 3:07 PM, Yu-cheng Yu wrote:
> +config X86_INTEL_SHADOW_STACK_USER
> + prompt "Intel Shadow Stacks for user-mode"
> + def_bool n
> + depends on CPU_SUP_INTEL && X86_64
> + depends on AS_HAS_SHADOW_STACK
> + select ARCH_USES_HIGH_VMA_FLAGS
> + select X86_INTEL_CET
>
On Wed, May 6, 2020 at 1:50 PM Andrey Konovalov wrote:
>
> On Wed, May 6, 2020 at 10:54 AM Oliver Neukum wrote:
> >
> > Am Freitag, den 20.03.2020, 12:28 -0700 schrieb syzbot:
> > > Hello,
> > >
> > > syzbot found the following crash on:
> > >
> > > HEAD commit:e17994d1 usb: core: kcov: colle
The function sanitize_restored_xstate() sanitizes user xstates of an XSAVE
buffer by clearing bits not in the input 'xfeatures' from the buffer's
header->xfeatures, effectively resetting those features back to the init
state.
When supervisor xstates are introduced, it is necessary to make sure onl
On Thu, 7 May 2020 17:23:36 +0800
Yunfeng Ye wrote:
> The @data and @fd is leak in the error path of apply_xbc(), so this
> patch fix it.
Good catch! Thanks for fixing!
Acked-by: Masami Hiramatsu
>
> Signed-off-by: Yunfeng Ye
> ---
> tools/bootconfig/main.c | 9 ++---
> 1 file changed,
On 23/04/2020 11:34, Bryan O'Donoghue wrote:
V3:
This update removes the old clock name arrays which I forgot to prune in
the previous V2.
git diff bod/clk-next+msm8939 bod/clk-next+msm8939-v2.1
I should have mentioned.
If you want to test this you'll need to do the following to your
msm8939
Hello,
A few month ago this series was sent and has not been merged while it
didn't have anything against it. I've ported the series onto v5.7-rc1,
added the acked by and reviewed by received on the first series and
took into account the comment from Robin Murphy for the last patch.
For the recor
The endpoint configuration used to be stored in the device tree,
however the configuration depend on the "version" of the controller
itself.
Then the EP child node are useless and describe as deprecated in the
documentation binding: remove all the nodes from the SoC device tree
file. Remove also t
On Thu, May 07, 2020 at 11:12:59PM +0800, Chuhong Yuan wrote:
> This driver calls input_register_device() in probe, but misses
> input_unregister_device() in remove.
> Add the missed function call to fix it.
>
> Signed-off-by: Chuhong Yuan
> ---
> drivers/input/touchscreen/wm831x-ts.c | 1 +
> 1
There is no need to describe the end point in the deice tree. These
properties won't be use anymore, so mark them as deprecated to keep
the old device tree documented.
Reviewed-by: Rob Herring
Signed-off-by: Gregory CLEMENT
---
.../devicetree/bindings/usb/atmel-usb.txt | 56 +---
On Thu, May 07, 2020 at 03:08:46PM +0300, Georgi Djakov wrote:
> There is a repeated pattern in multiple drivers where they want to switch
> the bandwidth between zero and some other value. This is happening often
> in the suspend/resume callbacks. Let's add helper functions to enable and
> disable
The endpoint configuration used to be stored in the device tree,
however the configuration depend on the "version" of the controller
itself.
This information is already documented by the compatible string. It
then possible to just rely on the compatible string and completely
remove the full ep con
On Fri, 8 May 2020 00:56:47 +0900
Masami Hiramatsu wrote:
> On Thu, 7 May 2020 17:23:36 +0800
> Yunfeng Ye wrote:
>
> > The @data and @fd is leak in the error path of apply_xbc(), so this
> > patch fix it.
>
> Good catch! Thanks for fixing!
>
> Acked-by: Masami Hiramatsu
>
Hi Steve, can yo
On 5/7/20 12:04 AM, Martin KaFai Lau wrote:
On Wed, May 06, 2020 at 10:03:52PM +0800, Jason Yan wrote:
The '==' expression itself is bool, no need to convert it to bool again.
This fixes the following coccicheck warning:
Make sense.
It may belong to bpf-next instead.
Acked-by: Martin KaFai La
The function copy_kernel_to_xregs_err() uses XRSTOR, which can work with
standard or compacted format without supervisor xstates. However, when
supervisor xstates are present, XRSTORS must be used. Fix it by using
XRSTORS when XSAVES is enabled.
I also considered if there were additional cases w
Hi Chuhong,
On Thu, May 07, 2020 at 11:10:41PM +0800, Chuhong Yuan wrote:
> This driver calls input_register_device() in probe, but misses
> input_unregister_device() in probe failure and remove.
> Add the missed function calls to fix it.
The input device in question is devm-managed and therefore
Em Thu, May 07, 2020 at 10:44:45AM +0200, Jiri Olsa escreveu:
> On Fri, May 01, 2020 at 10:33:21AM -0700, Ian Rogers wrote:
> > Add a test that all perf metrics (for your architecture) are parsable
> > with the simple expression parser. Attempt to parse all events in
> > metrics but only fail if th
Hi Chuhong,
On Thu, May 07, 2020 at 11:11:15PM +0800, Chuhong Yuan wrote:
> This driver calls input_register_device() in probe, but misses
> input_unregister_device() in probe failure and remove.
> Add the missed function calls to fix it.
The input device in question is devm-managed and therefore
Sorry I forgot to add back the title of the series which was:
"Remove the USB EP configuration from device tree"
Gregory
Gregory CLEMENT writes:
> Hello,
>
> A few month ago this series was sent and has not been merged while it
> didn't have anything against it. I've ported the series onto v
On Thu, May 07, 2020 at 11:11:47PM +0800, Chuhong Yuan wrote:
> This driver calls input_register_device() in probe, but misses
> input_unregister_device() in probe failure and remove.
> Add the missed function calls to fix it.
The input device in question is devm-managed and therefore does not nee
On Thu, May 07, 2020 at 11:12:13PM +0800, Chuhong Yuan wrote:
> This driver calls input_register_device() in probe, but misses
> input_unregister_device() in remove.
> Add the missed function call to fix it.
The input device in question is devm-managed and therefore does not need
explicit unregist
On Thu, May 07, 2020 at 11:12:59PM +0800, Chuhong Yuan wrote:
> This driver calls input_register_device() in probe, but misses
> input_unregister_device() in remove.
> Add the missed function call to fix it.
The input device in question is devm-managed and therefore does not need
explicit unregist
On Thu, 7 May 2020 15:36:48 +0200 (CEST)
Jiri Kosina wrote:
> On Wed, 29 Apr 2020, Josh Poimboeuf wrote:
>
> > s390_kernel_write()'s function type is almost identical to memcpy().
> > Change its return type to "void *" so they can be used interchangeably.
> >
> > Cc: linux-s...@vger.kernel.org
On Wed, 1 Apr 2020, Daniel Colascione wrote:
> This change adds two new functions, anon_inode_getfile_secure and
> anon_inode_getfd_secure, that create anonymous-node files with
> individual non-S_PRIVATE inodes to which security modules can apply
> policy. Existing callers continue using the orig
On 07/05/2020 16:57, Bryan O'Donoghue wrote:
On 23/04/2020 11:34, Bryan O'Donoghue wrote:
V3:
This update removes the old clock name arrays which I forgot to prune in
the previous V2.
git diff bod/clk-next+msm8939 bod/clk-next+msm8939-v2.1
I should have mentioned.
If you want to test this yo
Hi,
I have one query regarding pseudo NMI support on GIC v3; from what I
could understand, GIC v3 supports pseudo NMI setup for SPIs and PPIs.
However the request_nmi() in irq framework requires NMI to be per cpu
interrupt source (it checks for IRQF_PERCPU). Can you please help
understand this
On 5/7/20 10:16 AM, Paolo Bonzini wrote:
> On 07/05/20 16:44, Dave Hansen wrote:
>>> You could add a new option (X86_MEMORY_PROTECTION_KEYS) which is
>>> def_bool X86_INTEL_MEMORY_PROTECTION_KEYS and avoiding the prompt line.
>>> Soo it is selected based on the old option and the user isn't both
On 5/7/20 1:15 AM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20200505:
>
on i386 or x86_64:
ERROR: modpost: "usb_hid_driver" [drivers/hid/hid-asus.ko] undefined!
or
(when builtin:)
ld: drivers/hid/hid-asus.o: in function `asus_probe':
hid-asus.c:(.text+0x60f): undefined reference to
On 07/05/20 18:06, Babu Moger wrote:
>>> So, for now my preference would be to change the prompt, but leave the
>>> CONFIG_ naming in place.
>> I agree.
>>
>> What's in a name? An Intel rose by any other name would smell as sweet.
>
> How about X86_MPK? Or I will use already proposed name
> X86_M
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: a811c1fa0a02c062555b54651065899437bacdbe
commit: 505a0ef15f96c6c43ec719c9fc1833d98957bb39 kasan: stackdepot: move
filter_irq_stacks() to stackdepot.c
date: 4 weeks ago
config: arc-randconfig-r034-20200507
On 5/7/20 11:07 AM, Paolo Bonzini wrote:
> On 07/05/20 18:06, Babu Moger wrote:
So, for now my preference would be to change the prompt, but leave the
CONFIG_ naming in place.
>>> I agree.
>>>
>>> What's in a name? An Intel rose by any other name would smell as sweet.
>>
>> How about
__read_mostly can easily be misused by folks, its not meant for
just read-only data. There are performance reasons for using it, but
we also don't provide any guidance about its use. Provide a bit more
guidance over its use.
Acked-by: Christoph Lameter
Signed-off-by: Luis Chamberlain
---
This v
Hi,
On Thu, May 07, 2020 at 02:16:56PM +0200, Marek Szyprowski wrote:
> Hi
>
> On 14.04.2020 17:34, Mike Rapoport wrote:
> > From: Mike Rapoport
> >
> > Implement primitives necessary for the 4th level folding, add walks of p4d
> > level where appropriate, and remove __ARCH_USE_5LEVEL_HACK.
> >
From: Sarthak Garg
Consider the following stack trace
-001|raw_spin_lock_irqsave
-002|mmc_blk_cqe_complete_rq
-003|__blk_mq_complete_request(inline)
-003|blk_mq_complete_request(rq)
-004|mmc_cqe_timed_out(inline)
-004|mmc_mq_timed_out
mmc_mq_timed_out acquires the queue_lock for the first
time.
The following changes since commit 6a8b55ed4056ea5559ebe4f6a4b247f627870d4c:
Linux 5.7-rc3 (2020-04-26 13:51:02 -0700)
are available in the Git repository at:
git://git.infradead.org/users/hch/configfs.git tags/configfs-for-5.7
for you to fetch changes up to 8aebfffacfa379ba400da573a5bf9e49
On 2020-05-07 4:27 p.m., Sasha Levin wrote:
> From: Marek Olšák
>
> [ Upstream commit 9017a4897a20658f010bebea825262963c10afa6 ]
>
> This fixes GPU hangs due to cache coherency issues.
> Bump the driver version. Split out from the original patch.
>
> Signed-off-by: Marek Olšák
> Reviewed-by: C
These few patches are on top of the very latest tarball tglx gave me and do not
apply to hit posted patches or his git-tree (although I suspect that might
change at some point in the near future).
Aside from relying on tip/objtool/core, this also relies on the patch I just
pushed into tip/objtool/
Thomas would very much like objtool to understand and generate correct
ORC unwind information for the minimal stack swizzle sequence:
mov %rsp, (%[ts])
mov %[ts], %rsp
...
pop %rsp
This sequence works for the fp and guess unwinders -- all they need is
that top-of-s
Because 1 copy of this magic is plenty.
Signed-off-by: Peter Zijlstra (Intel)
---
--- a/arch/x86/include/asm/irq_stack.h
+++ b/arch/x86/include/asm/irq_stack.h
@@ -12,10 +12,8 @@ static __always_inline bool irqstack_act
return __this_cpu_read(irq_count) != -1;
}
-/*
- * Macro to emit c
To reduce clutter.
Signed-off-by: Peter Zijlstra (Intel)
---
arch/x86/include/asm/irq_stack.h | 10 ++
arch/x86/include/asm/kvm_host.h | 10 ++
include/linux/compiler.h | 14 ++
3 files changed, 18 insertions(+), 16 deletions(-)
--- a/arch/x86/include/
On Thu, May 07, 2020 at 07:50:11AM -0400, Paolo Bonzini wrote:
> When KVM_EXIT_DEBUG is raised for the disabled-breakpoints case (DR7.GD),
> DR6 was incorrectly copied from the value in the VM. Instead,
> DR6.BD should be set in order to catch this case.
>
> On AMD this does not need any special
The MHI device may be in the syserr state when we attempt to init it in
power_up(). Since we have no local state, the handling is simple -
reset the device and wait for it to transition out of the reset state.
Signed-off-by: Jeffrey Hugo
---
v4:
-Implemented Hemant's suggested solution from v2.
I do not have access to my @marvell.com email ID anymore.
Lets map my new email address correctly in .mailmap
Signed-off-by: Himanshu Madhani
---
.mailmap | 2 ++
1 file changed, 2 insertions(+)
diff --git a/.mailmap b/.mailmap
index db3754a41018..30d8c3f10ca7 100644
--- a/.mailmap
+++ b/.mailm
Some chips have 4B opcodes, but there is no way to know if they have
them. This device tree option allows platform owners to force enable 4b
opcodes when they know their chips support it even when it can be
automatically identified.
Cc: xe-linux-exter...@cisco.com
Signed-off-by: Daniel Walker
---
On 07/05/20 18:18, Peter Xu wrote:
>> if (vcpu->guest_debug & KVM_GUESTDBG_USE_HW_BP) {
>> -vcpu->run->debug.arch.dr6 = vcpu->arch.dr6;
>> +vcpu->run->debug.arch.dr6 = DR6_BD | DR6_RTM |
>> DR6_FIXED_1;
> After a second thought I'm thinking whet
Hi Pavel,
On 26/03/2020 03:24, Pavel Tatashin wrote:
> Soon, relocation function will share the same page with EL2 vectors.
The EL2 vectors would only be executed with the MMU off, so they don't need to
be mapped
anywhere in particular. (this is something hibernate probably does sloppily).
> A
Hi Pavel,
On 26/03/2020 03:24, Pavel Tatashin wrote:
> Remove excessive empty lines from arm64_relocate_new_kernel.
To make it harder to read? Or just for the churn ...
> Also, use comments on the same lines with instructions where
> appropriate.
Churn,
> Change ENDPROC to END it never return
Hi Pavel,
What happened to the subject?
(it really needs a verb to make any sense)
On 26/03/2020 03:24, Pavel Tatashin wrote:
> If we have a EL2 mode without VHE, the EL2 vectors are needed in order
> to switch to EL2 and jump to new world with hyperivsor privileges.
Yes, but the hyp-stub has an
Hi Pavel,
On 26/03/2020 03:24, Pavel Tatashin wrote:
> Configure a page table located in kexec-safe memory that has
> the following mappings:
>
> 1. identity mapping for text of relocation function with executable
>permission.
> 2. linear mappings for all source ranges
> 3. linear mappings fo
Hi Pavel,
On 26/03/2020 03:24, Pavel Tatashin wrote:
> x0 will contain the only argument to arm64_relocate_new_kernel; don't
> use it as a temp. Reassigned registers to free-up x0.
The missing bit of motivation is _why_ you need x0 keep its value until the end
of this code.
With that covered,
R
Hi Pavel,
On 26/03/2020 03:24, Pavel Tatashin wrote:
> Currently, kexec relocation function (arm64_relocate_new_kernel) accepts
> the following arguments:
>
> head: start of array that contains relocation information.
> entry:entry point for new kernel or purgatory.
> dtb_
...@lists.freedesktop.org
---
drivers/gpu/drm/panel/panel-visionox-rm69299.c |1 +
1 file changed, 1 insertion(+)
--- linux-next-20200507.orig/drivers/gpu/drm/panel/panel-visionox-rm69299.c
+++ linux-next-20200507/drivers/gpu/drm/panel/panel-visionox-rm69299.c
@@ -300,3 +300,4 @@ static struct mipi_dsi_driver
On Thu, May 7, 2020 at 3:44 PM Jeff Layton wrote:
>
> On Tue, 2020-05-05 at 13:59 +0100, Luis Henriques wrote:
> > A misconfigured cephx can easily result in having the kernel client
> > flooding the logs with:
> >
> > ceph: Can't lookup inode 1 (err: -13)
> >
> > Change his message to debug lev
Clang does not allow -fsanitize-coverage=trace-{pc,cmp} together
with -fsanitize=bounds or with ubsan:
clang: error: argument unused during compilation:
'-fsanitize-coverage=trace-pc' [-Werror,-Wunused-command-line-argument]
clang: error: argument unused during compilation:
'-fsanitize-coverage=
From: "Paul A. Clarke"
The metric definition is too long for the current value of EXPR_MAX_OTHER.
Increase the value EXPR_MAX_OTHER sufficiently to allow
'lsu_other_stall_cpi' to build properly.
Before:
--
$ perf list | grep lsu_other
lsu_other_stall_cpi
# perf stat -a --metrics lsu_other_stal
From: "Paul A. Clarke"
Add the following metrics to the POWER9 'cpi_breakdown' metricgroup:
- ict_noslot_br_mpred_cpi
- ict_noslot_br_mpred_icmiss_cpi
- ict_noslot_cyc_other_cpi
- ict_noslot_disp_held_cpi
- ict_noslot_disp_held_hb_full_cpi
- ict_noslot_disp_held_issq_cpi
- ict_noslot_disp_held_ot
From: "Paul A. Clarke"
The recent patches posted by Ian Rogers motivated a deeper dive into
the POWER9 perf metrics, which uncovered some additional issues:
- 'lsu_other_stall_cpi' doesn't work at all
- All of the "ICT" metrics are missing from the metricgroup
Paul A. Clarke (2):
perf: Fix PO
Hi Mel,
we are not targeting just OMP applications. We see the performance
degradation also for other workloads, like SPECjbb2005 and
SPECjvm2008. Even worse, it also affects a higher number of threads.
For example, comparing 5.7.0-0.rc2 against 5.6 kernel, on 4 NUMA
server with 2x AMD 7351 CPU, w
On 5/5/20 3:44 PM, Thomas Gleixner wrote:
Provide functions which handle the low level entry and exit similiar to
enter/exit from user mode.
typo: "similiar"
Signed-off-by: Thomas Gleixner
---
arch/x86/entry/common.c | 89
arch/x86/inc
On 5/6/20 5:42 PM, Anthony Yznaga wrote:
> Improve performance by multithreading the work to preserve and restore
> shmem pages.
>
> Add 'pkram_max_threads=' kernel option to specify the maximum number
> of threads to use to preserve or restore the pages of a shmem file.
> The default is 16.
Hi,
Hi Linus,
Please pull the arm64 fix below. Thanks.
The following changes since commit 1578e5d03112e3e9d37e1c4d95b6dfb734c73955:
arm64: vdso: Add -fasynchronous-unwind-tables to cflags (2020-04-30 18:35:32
+0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/ke
Hi Christophe,
I love your patch! Yet something to improve:
[auto build test ERROR on v5.7-rc4]
[cannot apply to powerpc/next next-20200507]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option
Currently the reclaim of excessive usage over memory.high is scheduled
to run on returning to the userland. The main reason behind this
approach was simplicity i.e. always reclaim with GFP_KERNEL context.
However the underlying assumptions behind this approach are: the current
task shares the memcg
On 5/6/2020 10:06 PM, Ulf Hansson wrote:
On Wed, 6 May 2020 at 15:01, Veerabhadrarao Badiganti
wrote:
On 4/28/2020 5:26 AM, Chun-Hung Wu wrote:
Parse CQE bindings "supports-cqe" and "disable-cqe-dcmd"
in mmc_of_parse().
Signed-off-by: Chun-Hung Wu
---
drivers/mmc/core/host.c | 5 +
On Thu, May 07, 2020 at 11:13:43PM +0800, Chuhong Yuan wrote:
> This driver calls sysfs_create_bin_file() in probe, but forgets to
> call sysfs_remove_bin_file() in remove.
> Add the missed call to fix it.
>
> Signed-off-by: Chuhong Yuan
> ---
> drivers/uio/uio_hv_generic.c | 1 +
> 1 file chang
On Thu, May 07, 2020 at 06:21:18PM +0200, Paolo Bonzini wrote:
> On 07/05/20 18:18, Peter Xu wrote:
> >>if (vcpu->guest_debug & KVM_GUESTDBG_USE_HW_BP) {
> >> - vcpu->run->debug.arch.dr6 = vcpu->arch.dr6;
> >> + vcpu->run->debug.arch.dr6 = DR6_BD | DR6_
Hi Baolu,
Very helpful feature, thanks for doing this. Just a small suggestion.
On Thu, 7 May 2020 08:55:31 +0800
Lu Baolu wrote:
> Export invalidation queue internals of each iommu device through the
> debugfs.
>
> Example of such dump on a Skylake machine:
>
> $ sudo cat /sys/kernel/debug/
On Thu, 7 May 2020 at 15:37, Lenny Szubowicz wrote:
>
> In allocate_e820(), call the EFI get_memory_map() service directly
> instead of indirectly via efi_get_memory_map(). This avoids allocation
> of a buffer and return of the full EFI memory map, which is not needed
> here and would otherwise ne
On 5/7/2020 1:39 AM, Dan Williams wrote:
Recently a performance problem was reported for a process invoking a
non-trival ASL program. The method call in this case ends up
repetitively triggering a call path like:
acpi_ex_store
acpi_ex_store_object_to_node
acpi_ex_write_data_to_fie
Em Thu, Apr 30, 2020 at 10:45:29AM +0200, Jiri Olsa escreveu:
> On Thu, Apr 30, 2020 at 08:36:18AM +0800, Jin Yao wrote:
> > A big uncore event group is split into multiple small groups which
> > only include the uncore events from the same PMU. This has been
> > supported in the commit 3cdc5c2cb92
801 - 900 of 1862 matches
Mail list logo
