Hi,
In virtualization environment, PV extensions (drivers, interrupts,
timers, etc) are enabled in the majority of use cases which is the
best option.
However, in some cases (kexec not fully working, benchmarking, etc)
we want to disable PV extensions. We have xen_nopv for that purpose
but only f
This reverts commit 8d693b911bb9c57009c24cb1772d205b84c7985c.
Instead we use an unified parameter 'nopv' for all the hypervisor
platforms.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Juergen Gross
Cc: Boris Ostrovsky
Cc: Juergen Gross
Cc: Stefano Stabellini
Cc: Thomas Gleixner
Cc: Ingo Molna
PVH guest needs PV extentions to work, so 'nopv' parameter should be
ignored for PVH but not for HVM guest.
If PVH guest boots up via the Xen-PVH boot entry, xen_pvh is set early,
we know it's PVH guest and ignore 'nopv' parameter directly.
If PVH guest boots up via the normal boot entry same as
.. as they are only called at early bootup stage. In fact, other
functions in x86_hyper_xen_hvm.init.* are all marked as __init.
Unexport xen_hvm_need_lapic as it's never used outside.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Juergen Gross
Cc: Boris Ostrovsky
Cc: Stefano Stabellini
Cc: Thom
From: Adrian Hunter
The core-to-bus ratio (CBR) provides the CPU frequency. With branches
enabled, the decoder was outputting CBR changes only when there was a
branch. That loses the correct time of the change if the trace is not in
context (e.g. not tracing kernel space). Change to output the CB
From: Adrian Hunter
PSB+ provides status information only so the core-to-bus ratio (CBR) in
PSB+ will not have changed from its previous value. However, cater for
the possibility of a another CBR change that gets caught up in the PSB+
anyway.
Signed-off-by: Adrian Hunter
Cc: Jiri Olsa
Link: ht
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-core-for-mingo-5.3-20190701
for you to fetch changes up to 06c642c0e9fceafd16b1a4c80d44b1c09e282215:
perf jevents: Use nonlocal include statements in pmu-events.c (2019-07-01
22:
From: Numfor Mbiziwo-Tiapo
Change the include path so that progress.c can find cache.h since it was
previously searching in the wrong directory.
Committer notes:
$ ls -la tools/perf/ui/../cache.h
ls: cannot access 'tools/perf/ui/../cache.h': No such file or directory
So it really should in
From: Adrian Hunter
Use new function thread_stack__pop_ks() in place of equivalent code.
Signed-off-by: Adrian Hunter
Cc: Jiri Olsa
Link: http://lkml.kernel.org/r/20190619064429.14940-3-adrian.hun...@intel.com
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/util/thread-stack.c | 18 ++
From: Adrian Hunter
The first core-to-bus ratio (CBR) event will not be shown if --itrace
's' option (skip initial number of events) is used, nor if time
intervals are specified that do not include the start of tracing. Change
the logic to record the last CBR value seen by the user, and synthesiz
From: Arnaldo Carvalho de Melo
Not being used at all anywhere.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-1e567f8tn8m4ii7dy1w9d...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/util/ctype.c | 4
tools/perf/util/sane
From: Adrian Hunter
Synthesized events are samples but with architecture-specific data
stored in sample->raw_data. They are identified by attribute type
PERF_TYPE_SYNTH. Add a function to export them.
Signed-off-by: Adrian Hunter
Cc: Jiri Olsa
Link: http://lkml.kernel.org/r/20190622093248.581
From: Kyle Meyer
Attempting to profile 1024 or more CPUs with perf causes two errors:
perf record -a
[ perf record: Woken up X times to write data ]
way too many cpu caches..
[ perf record: Captured and wrote X MB perf.data (X samples) ]
perf report -C 1024
Error: failed to set cpu
From: Adrian Hunter
The format of synthesized events is determined by the attribute config.
For the formats for Intel PT power and ptwrite events, create tables and
populate them when the synth_data handler is called. If the tables
remain empty, drop them at the end.
The tables and views, includ
From: Adrian Hunter
For convenience, add the core-to-bus ratio (CBR) value to the decoder
state.
Signed-off-by: Adrian Hunter
Cc: Jiri Olsa
Link: http://lkml.kernel.org/r/20190622093248.581-4-adrian.hun...@intel.com
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/util/intel-pt-decoder
From: Arnaldo Carvalho de Melo
We can just use the 'field width' for the %s used to print the
alignment, this way we'll get the same result without requiring having a
variable with just lots of space chars.
No way to do that for the dots tho, we still need that variable filled
with dot chars.
From: Arnaldo Carvalho de Melo
The skip_sep() routine has the same implementation as skip_spaces(),
recently adopted from the kernel, sources, switch to it.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-0ix211a81z2016dl5nmtd...@git.
From: Arnaldo Carvalho de Melo
Same implementation, will be used to replace ad-hoc equivalent code in
tools/.
Cc: Adrian Hunter
Cc: André Goddard Rosa
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-dig691cg9ripvoiprpidt...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de
From: Arnaldo Carvalho de Melo
There were a few places where we still were using the libc version of
ctype.h, switch to the one in tools/lib/ctype.c that the rest of perf
uses.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-wa4nz4kt61eze88eprk20...@git.ke
From: Arnaldo Carvalho de Melo
No change in behaviour intended.
Cc: Adrian Hunter
Cc: David Ahern
Cc: Jin Yao
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-cpugv7qd5vzhbtvnlydo9...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/util/time-utils.c
From: Arnaldo Carvalho de Melo
We can left justify just fine using the 'field width' modifier in %s
printf, ditch this variable.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-2td8u86mia7143lbr5ttl...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
From: Arnaldo Carvalho de Melo
No change in behaviour.
Cc: Stephane Eranian
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-0dbfpi70aa66s6mtd8z6p...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/util/header.c | 5 ++---
1 file ch
From: Arnaldo Carvalho de Melo
No change in behaviour.
Cc: Andi Kleen
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-ncpvp4eelf8fqhuy29uv5...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/util/stat-display.c | 5 ++---
1 file ch
From: Arnaldo Carvalho de Melo
We're getting it by sheer luck, add that util.h to get the 'page_size'
definition.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-347078mgj3d2jfygtxs4n...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/pe
From: Arnaldo Carvalho de Melo
Those are not in that file in the git repo, lets move it from there so
that we get that sane ctype code fully isolated to allow getting it in
sync either with the git sources or better with the kernel sources
(include/linux/ctype.h + lib/ctype.h), that way we can us
From: Arnaldo Carvalho de Melo
It was just including a ../util.h that wasn't even there:
$ cat tools/perf/util/include/linux/../util.h
cat: tools/perf/util/include/linux/../util.h: No such file or directory
$
This would make kallsyms.h get util.h somehow and then files including
it would
From: Arnaldo Carvalho de Melo
Not to depend of getting it indirectly.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-tirjsmvu4ektw0k7lm8k9...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/arch/arm/util/cs-etm.c | 1 +
tools/
From: Arnaldo Carvalho de Melo
Just removing more stuff from tools/perf/, this is mostly used in the
kallsyms parsing and in places in perf where kallsyms is involved, so we
get it for free there.
With this we reduce a bit more util.h.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: h
From: Arnaldo Carvalho de Melo
We'll use it to further reduce the size of tools/perf/util/string.c,
replacing the strxfrchar() equivalent function we have there.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-x3r61ikjrso1buygxwke8...@git.kernel.org
Signed
From: Arnaldo Carvalho de Melo
No change in behaviour intended, trivial optimization done by avoiding
looking for spaces in 'g' right after setting it to "No_group".
Cc: Adrian Hunter
Cc: Andi Kleen
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-f2siadtp3hb5o0l1w7bvd...@g
From: Arnaldo Carvalho de Melo
Cleaning up a bit more tools/perf/util/ by using things we got from the
kernel and have in tools/lib/
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-7hluuoveryoicvkclshzj...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de
From: Arnaldo Carvalho de Melo
This came from the kernel lib/argv_split.c, so move it to
tools/lib/argv_split.c, to get it closer to the kernel structure.
We need to audit the usage of argv_split() to figure out if it is really
necessary to do have one allocation per argv[] entry, looking at one
From: Arnaldo Carvalho de Melo
No change in behaviour, just using the same kernel idiom for such
operation.
Cc: Adrian Hunter
Cc: André Goddard Rosa
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-a85lkptkt0ru40irpga8y...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de M
From: Arnaldo Carvalho de Melo
No change in behaviour intended, just reducing the codebase and using
something available in tools/lib/.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-oyi6zif3810nwi4uu85od...@git.kernel.org
Signed-off-by: Arnaldo Carvalho
From: Arnaldo Carvalho de Melo
No change in behaviour intended.
Cc: Adrian Hunter
Cc: Andi Kleen
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-lcywlfqbi37nhegmhl1ar...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/builtin-report.c | 3 +--
1 fil
From: Andi Kleen
After setting up metric groups through the event parser, the metricgroup
code looks them up again in the event list.
Make sure we only look up events that haven't been used by some other
metric. The data structures currently cannot handle more than one metric
per event. This avo
From: Arnaldo Carvalho de Melo
Since we're working on moving stuff out of tools/perf/util/ to
tools/lib/, take the opportunity to adopt routines from the kernel that
are equivalent, so that tools/ code look more like the kernel.
Cc: Adrian Hunter
Cc: André Goddard Rosa
Cc: Jiri Olsa
Cc: Namhy
From: Arnaldo Carvalho de Melo
No change in behaviour.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Masami Hiramatsu
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-p9rtamq7lvre9zhti70az...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/util/strfilter.c | 4 ++--
1 file
From: Arnaldo Carvalho de Melo
Moving more stuff out of tools/perf/util/ and using the kernel idiom.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-wpj8rktj62yse5dq6ckny...@git.kernel.org
Signed-off-by: Arnaldo Carvalho de Melo
---
tools/perf/tests/buil
From: Arnaldo Carvalho de Melo
Continuing to untangle the headers, we're about to remove the old odd
baggage that is tools/perf/util/include/linux/ctype.h.
Cc: Adrian Hunter
Cc: Jiri Olsa
Cc: Namhyung Kim
Link: https://lkml.kernel.org/n/tip-gapezcq3p8bzrsi96vdtq...@git.kernel.org
Signed-off-b
From: Arnaldo Carvalho de Melo
We got the sane_ctype.h headers from git and kept using it so far, but
since that code originally came from the kernel sources to the git
sources, perhaps its better to just use the one in the kernel, so that
we can leverage tools/perf/check_headers.sh to be notifie
From: Adrian Hunter
The format of synthesized events is determined by the attribute config.
For the formats for Intel PT power and ptwrite events, create tables and
populate them when the synth_data handler is called. If the tables
remain empty, drop them at the end.
The tables and views, includ
From: Andi Kleen
Since Fixes: 8c5421c016a4 ("perf pmu: Display pmu name when printing
unmerged events in stat") using --no-merge adds the PMU name to the
evsel name.
This breaks the metric value lookup because the parser doesn't know
about this.
Remove the extra postfixes for the metric evaluat
From: Andi Kleen
Event merging is mainly to collapse similar events in lots of different
duplicated PMUs.
It can break metric displaying. It's possible for two metrics to have
the same event, and when the two events happen in a row the second
wouldn't be displayed. This would also not show the
From: Andi Kleen
The metric group code tries to find a group it added earlier in the
evlist. Fix the lookup to handle groups with partially overlaps
correctly. When a sub string match fails and we reset the match, we have
to compare the first element again.
I also renamed the find_evsel function
From: Mao Han
This patch add basic arch initialization and instruction associate
support for the csky CPU architecture.
E.g.:
$ perf annotate --stdio2
Samples: 161 of event 'cpu-clock:pppH', 4000 Hz, Event count (approx.):
4025, [percent: local period]
test_4() /usr/lib/perf-test/c
From: Luke Mujica
Change pmu-events.c to not use local include statements. The code that
creates the include statements for pmu-events.c is in jevents.c.
pmu-events.c is a generated file, and for build systems that put
generated files in a separate directory, include statements with local
pathin
From: Hariprasad Kelam
Date: Sun, 30 Jun 2019 19:59:49 +0530
> Remove unneeded memset as alloc_etherdev is using kvzalloc which uses
> __GFP_ZERO flag
>
> Signed-off-by: Hariprasad Kelam
Applied to net-next, thanks.
From: Adrian Hunter
Commit f08046cb3082 ("perf thread-stack: Represent jmps to the start of a
different symbol") had the side-effect of introducing more stack entries
before return from kernel space.
When user space is also traced, those entries are popped before entry to
user space, but when us
Munchun, is this what your patch fixes ?
On Mon, 2019-07-01 at 16:27 -0700, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit 726e41097920a73e4c7c33385dcc0debb1281e18
> Author: Benjamin Herrenschmidt
> Date: Tue Jul 10 00:29:10 2018 +
>
> drivers: core: Remove glue dirs fr
Hi Ben,
On 6/18/2019 7:28 AM, Ben Hutchings wrote:
> 3.16.69-rc1 review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Eric Dumazet
>
> commit f070ef2ac66716357066b683fb0baf55f8191a2e upstream.
>
> Jonathan Looney reported that a malicious peer can
Hi Ben,
Benjamin Herrenschmidt 于2019年7月2日周二 上午10:44写道：
>
> Munchun, is this what your patch fixes ?
>
Yes, this is what my patch fixes.
The patchs can reference to:
[PATCH v1 OPT1] driver core: Fix use-after-free and double
free on glue directory
[PATCH v4 OPT2] driver core: Fix
Hi all,
Today's linux-next merge of the mlx5-next tree got conflicts in:
drivers/net/ethernet/mellanox/mlx5/core/eswitch.c
between commits:
02f3afd97556 ("net/mlx5: E-Switch, Correct type to u16 for vport_num and int
for vport_index")
from Linus' tree and commit:
5f5d2536be8d ("net/mlx
Hi all,
Today's linux-next merge of the mlx5-next tree got a conflict in:
drivers/net/ethernet/mellanox/mlx5/core/eswitch_offloads.c
between commit:
955858009708 ("net/mlx5e: Fix number of vports for ingress ACL configuration")
from Linus' tree and commit:
062f4bf4aab5 ("net/mlx5: E-Swi
Hi, Rob,
Sorry to bother you, could you please review this patch when you are
available? Thanks.
On Mon, 2019-07-01 at 15:48 +0800, Bibby Hsieh wrote:
> cmdq driver provide a function that get the relationship
> of sub system number from device node for client.
> add specification for #subsys-cel
On 7/1/19 1:59 AM, Mel Gorman wrote:
> On Fri, Jun 28, 2019 at 11:20:42AM -0700, Mike Kravetz wrote:
>> On 4/24/19 7:35 AM, Vlastimil Babka wrote:
>>> On 4/23/19 6:39 PM, Mike Kravetz wrote:
> That being said, I do not think __GFP_RETRY_MAYFAIL is wrong here. It
> looks like there is someth
This patch add device node for MT2712 rtc.
Signed-off-by: Ran Bi
---
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
index 43307bad3f0d..31166c17c39a 100644
This add support for the MediaTek MT2712 RTC. It was SoC based RTC, but
had different architecture compared with MT7622 RTC.
Signed-off-by: Ran Bi
---
drivers/rtc/Kconfig | 10 +
drivers/rtc/Makefile | 1 +
drivers/rtc/rtc-mt2712.c | 495 +++
3 fil
This patchset add support to MT2712 RTC. MT2712 RTC is a SoC based RTC
with different architecture compared to MT7622 RTC.
Ran Bi (3):
bindings: rtc: add bindings for MT2712 RTC
rtc: Add support for the MediaTek MT2712 RTC
arm64: dts: add rtc nodes for MT2712
.../devicetree/bindings/rtc/rt
Document the binding for MT2712 RTC implemented by rtc-mt2712.
Signed-off-by: Ran Bi
---
.../devicetree/bindings/rtc/rtc-mt2712.txt | 14 ++
1 file changed, 14 insertions(+)
create mode 100644 Documentation/devicetree/bindings/rtc/rtc-mt2712.txt
diff --git a/Documentation/d
On Mon, Jul 1, 2019 at 6:32 PM Rob Herring wrote:
>
> On Mon, Jul 1, 2019 at 6:48 PM Saravana Kannan wrote:
> >
> > Add device-links after the devices are created (but before they are
> > probed) by looking at common DT bindings like clocks and
> > interconnects.
> >
> > Automatically adding devi
On Sun, Jun 30, 2019 at 02:37:32PM -0700, Dan Williams wrote:
> On Sun, Jun 30, 2019 at 8:23 AM Matthew Wilcox wrote:
> > I think my theory was slightly mistaken, but your fix has the effect of
> > fixing the actual problem too.
> >
> > The xas->xa_index for a PMD is going to be PMD-aligned (ie a
Add support for NI-Serial PXIe-RS232, PXI-RS485 and PXIe-RS485 devices.
Signed-off-by: jeyentam
---
drivers/tty/serial/8250/8250_pci.c | 879 +++--
1 file changed, 582 insertions(+), 297 deletions(-)
diff --git a/drivers/tty/serial/8250/8250_pci.c
b/drivers/tty/serial/8
On 06/28/2019 03:50 PM, Catalin Marinas wrote:
> Hi Anshuman,
Hello Catalin,
>
> On Thu, Jun 27, 2019 at 06:18:15PM +0530, Anshuman Khandual wrote:
>> pmd_present() and pmd_trans_huge() are expected to behave in the following
>> manner during various phases of a given PMD. It is derived from a
Add NI PXIe-RS232, PXI-RS485 and PXIe-RS485 device IDs.
Signed-off-by: jeyentam
---
include/linux/pci_ids.h | 62 -
1 file changed, 37 insertions(+), 25 deletions(-)
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index 70e86148cb1e..cc1f61
On Mon, Jul 1, 2019 at 6:46 PM Rob Herring wrote:
>
> On Mon, Jul 1, 2019 at 6:48 PM Saravana Kannan wrote:
> >
> > The driver core/bus adding dependencies by default makes sure that
> > suppliers don't sync the hardware state with software state before all the
> > consumers have their drivers lo
Make sure that we exercise both variants of the nasty
TF-in-compat-syscall regardless of what vendor's CPU is running the
tests.
Also change the intentional signal after SYSCALL to use ud2, which
is a lot more comprehensible.
This crashes the kernel due to an FSGSBASE bug right now.
This test *a
It's only used if !CONFIG_IA32_EMULATION, so disable it in normal
configs. This will save a few bytes of text and reduce confusion.
Cc: "Bae, Chang Seok"
Signed-off-by: Andy Lutomirski
---
arch/x86/entry/entry_64.S | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/x86/entry/entry_
In -tip, if FSGSBASE and PTI are on, the kernel crashes if SYSENTER
happens with TF set. It also crashes under if a non-NMI paranoid
entry happens for any other reason from kernel mode with user GSBASE
and user CR3, e.g. due to MOV SS shenanigans.
This series fixes the bug. It also adds another
paranoid_exit needs to restore CR3 before GSBASE. Doing it in the
opposite order crashes if the exception came from a context with
user GSBASE and user CR3 -- RESTORE_CR3 cannot resture user CR3 if
run with user GSBASE. This results in infinitely recursing
exceptions if user code does SYSENTER wi
On Mon, Jul 01, 2019 at 12:04:13AM -0400, Joel Fernandes (Google) wrote:
> The t->rcu_read_unlock_special union's need_qs bit can be set by the
> scheduler tick (in rcu_flavor_sched_clock_irq) to indicate that help is
> needed from the rcu_read_unlock path. When this help arrives however, we
> can
On Mon, Jul 01, 2019 at 10:20:27AM +0800, Zhenzhong Duan wrote:
> This reverts commit 8d693b911bb9c57009c24cb1772d205b84c7985c.
>
> Instead we use an unified parameter 'nopv' for all the hypervisor
> platforms.
>
> Signed-off-by: Zhenzhong Duan
> Reviewed-by: Juergen Gross
> Cc: Boris Ostrovsky
Hi all,
After merging the amdgpu tree, today's linux-next build (x86_64
allmodcnofig) produced this warning:
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device.c: In function 'kgd2kfd_probe':
drivers/gpu/drm/amd/amdgpu/../amdkfd/kfd_device.c:490:6: warning: unused
variable 'ret' [-Wunused-variable]
On Mon, Jul 1, 2019 at 8:43 PM Andy Lutomirski wrote:
>
> In -tip, if FSGSBASE and PTI are on, the kernel crashes if SYSENTER
> happens with TF set. It also crashes under if a non-NMI paranoid
> entry happens for any other reason from kernel mode with user GSBASE
> and user CR3, e.g. due to MOV S
On Thu, Jun 27, 2019 at 11:24:41PM +0200, Thomas Gleixner wrote:
> On Wed, 26 Jun 2019, Zhenzhong Duan wrote:
>
> > This reverts commit ca5d376e17072c1b60c3fee66f3be58ef018952d.
> >
> > Commit 8990cac6e5ea ("x86/jump_label: Initialize static branching
> > early") adds jump_label_init() call in se
On Tue, Jul 02, 2019 at 01:13:27PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the mlx5-next tree got a conflict in:
>
> drivers/net/ethernet/mellanox/mlx5/core/eswitch_offloads.c
>
> between commit:
>
> 955858009708 ("net/mlx5e: Fix number of vports for ingress ACL
On Tue, Jul 02, 2019 at 10:05:33AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> In commit
>
> 16fff98a7e82 ("net/mlx5: E-Switch, Reg/unreg function changed event at
> correct stage")
>
> Fixes tag
>
> Fixes: 61fc880839e6 ("net/mlx5: E-Switch, Handle representors creation in
> handler context"
On Mon, 2019-07-01 at 12:46 +0200, Michal Hocko wrote:
> On Fri 28-06-19 10:46:28, Alastair D'Silva wrote:
> [...]
> > Given that there is already a VM_BUG_ON in the code, how do you
> > feel
> > about broadening the scope from 'VM_BUG_ON(!root)' to
> > 'VM_BUG_ON(!root
> > > > (root_nr == NR_SECTI
On 7/1/19 4:44 AM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> Both the PCI bus type and the ACPI PM domain avoid resuming
> runtime-suspended devices with DPM_FLAG_SMART_SUSPEND set during
> hibernation (before creating the snapshot image of system memory),
> but that turns out to be
Hi Stephen,
You are correct, Its
Fixes: ba94c753ccb4 ("ath10k: add QMI message handshake for wcn3990 client")
My bad, I added last 12 digits instead of first 12 digits of SHA1.
Regards,
Dundi
-Original Message-
From: Stephen Rothwell
Sent: Tuesday, July 2, 2019 3:03 AM
To: Kalle Valo
Sorry to break into your privacy in this manner,
I'm Smadar Barber-Tsadik, Deputy Chief Executive Officer
of First International Bank of Israel Ltd (FIBI).
I am getting in touch with you regarding an extremely
important and urgent matter. If you would oblige me the
opportunity, I shall provide
With OPP core now supporting DVFS for IO devices, we have instances of
IO devices (same IP block) with require an OPP on some platforms/SoCs
while just needing to scale the clock on some others.
In order to avoid conditional code in every driver, (to check for
availability of OPPs and then decidin
Export dev_pm_opp_set_genpd_virt_dev() so loadable modules can use it.
Signed-off-by: Rajendra Nayak
---
drivers/opp/core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/opp/core.c b/drivers/opp/core.c
index 8fbdbedc009c..ae033bb1e5b7 100644
--- a/drivers/opp/core.c
+++ b/drivers/o
The subsystem was merged some time ago but we did not have a maintainers
entry.
Signed-off-by: Joel Stanley
---
MAINTAINERS | 13 +
1 file changed, 13 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 01a52fc964da..2a5df9c20ecb 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@
On 2019/7/2 11:48, Boris Ostrovsky wrote:
On Mon, Jul 01, 2019 at 10:20:27AM +0800, Zhenzhong Duan wrote:
This reverts commit 8d693b911bb9c57009c24cb1772d205b84c7985c.
Instead we use an unified parameter 'nopv' for all the hypervisor
platforms.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Juer
Hi Joel,
> The subsystem was merged some time ago but we did not have a
> maintainers
> entry.
Acked-by: Jeremy Kerr
Cheers,
Jeremy
Hi Stan,
On 2019-07-01 17:13, Stanimir Varbanov wrote:
On 6/25/19 7:27 PM, Aniket Masule wrote:
Add vpp cycles for for different types of codec
It indicates the cycles required by video hardware
to process each macroblock. Initialize the codec
data with core resources.
Signed-off-by: Aniket Ma
On 7/2/2019 1:34 AM, Alex Williamson wrote:
> On Mon, 1 Jul 2019 23:20:35 +0530
> Kirti Wankhede wrote:
>
>> On 7/1/2019 10:54 PM, Alex Williamson wrote:
>>> On Mon, 1 Jul 2019 22:43:10 +0530
>>> Kirti Wankhede wrote:
>>>
On 7/1/2019 8:24 PM, Alex Williamson wrote:
> This allows
Hi Stan,
On 2019-07-01 18:41, Stanimir Varbanov wrote:
On 6/25/19 7:27 PM, Aniket Masule wrote:
Current clock scaling calculations are same for vpu4 and
previous versions. For vpu4, Clock scaling calculations
are updated with cycles/mb. This helps in getting precise
clock required.
Signed-off-
Hi Stan,
On 2019-07-01 19:28, Stanimir Varbanov wrote:
Hi,
On 6/25/19 7:27 PM, Aniket Masule wrote:
Present core assignment is static. Introduced load balancing
across the cores. Load on earch core is calculated and core
with minimum load is assigned to given instance.
Signed-off-by: Aniket M
Hi Jolly,
> -Original Message-
> From: Jolly Shah
> Sent: Monday, July 1, 2019 11:36 PM
> To: Manish Narani ; ulf.hans...@linaro.org;
> robh...@kernel.org; mark.rutl...@arm.com; he...@sntech.de; Michal Simek
> ; adrian.hun...@intel.com;
> christoph.muell...@theobroma-systems.com; philipp.
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 1 of them as possibly being a bug in the hid subsystem.
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 1 of them as possibly being a bug in the rtc subsystem.
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 1 of them as possibly being a bug in the "security/smack
On Mon, Jul 01, 2019 at 01:12:16PM -0700, Paul E. McKenney wrote:
> On Mon, Jul 01, 2019 at 09:40:39AM +0900, Byungchul Park wrote:
> > Hello,
> >
> > I tested again if the WARN_ON_ONCE() is fired with my box.
> >
> > And it was OK.
> >
> > Thanks,
> > Byungchul
>
> And it now applies just fine
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 2 of them as possibly being bugs in the "security/tomoyo
[This email was generated by a script. Let me know if you have any suggestions
to make it better, or if you want it re-generated with the latest status.]
Of the currently open syzbot reports against the upstream kernel, I've manually
marked 2 of them as possibly being bugs in the vhost subsystem.
.. as they are only called at early bootup stage. In fact, other
functions in x86_hyper_xen_hvm.init.* are all marked as __init.
Unexport xen_hvm_need_lapic as it's never used outside.
Signed-off-by: Zhenzhong Duan
Reviewed-by: Juergen Gross
Cc: Boris Ostrovsky
Cc: Stefano Stabellini
Cc: Thom
Hi,
In virtualization environment, PV extensions (drivers, interrupts,
timers, etc) are enabled in the majority of use cases which is the
best option.
However, in some cases (kexec not fully working, benchmarking, etc)
we want to disable PV extensions. We have xen_nopv for that purpose
but only f
PVH guest needs PV extentions to work, so 'nopv' parameter should be
ignored for PVH but not for HVM guest.
If PVH guest boots up via the Xen-PVH boot entry, xen_pvh is set early,
we know it's PVH guest and ignore 'nopv' parameter directly.
If PVH guest boots up via the normal boot entry same as
1 - 100 of 816 matches
Mail list logo
