Remove null ptr check before kfree because kfree is null ptr safe.
Issue found by checkpatch.
Signed-off-by: Sumit Kumar
---
drivers/staging/gasket/gasket_page_table.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/gasket/gasket_page_table.c
b/drivers/
On Sun, Aug 12, 2018 at 03:17:53AM +0530, Sumit Kumar wrote:
> Remove null ptr check before kfree because kfree is null ptr safe.
> Issue found by checkpatch.
>
> Signed-off-by: Sumit Kumar
Do not use fake email addresses in a signed-off-by line :(
On Sun, Aug 12, 2018 at 03:11:22AM +0530, Sumit Kumar wrote:
> Adding a mailing list in cc as per recommendation from greg's patch bot.
> + linux-kernel@vger.kernel.org
>
> $ scripts/get_maintainer.pl -f
> /tmp/0001-staging-gasket-remove-null-ptr-check-before-kfree.patch
> fatal: /tmp/0001-staging
Hello,
syzbot found the following crash on:
HEAD commit:2b769bb85b48 Add linux-next specific files for 20180807
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1525beac40
kernel config: https://syzkaller.appspot.com/x/.config?x=547d800b8773c2c5
dashb
This commit fixes a couple of typos in README and recipies.txt.
Signed-off-by: SeongJae Park
---
tools/memory-model/Documentation/recipes.txt | 2 +-
tools/memory-model/README| 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/memory-model/Documentati
Hi Craig,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on agross/for-next]
[also build test ERROR on v4.18-rc8 next-20180810]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
This helps builds when builddir != srcdir
Signed-off-by: Khem Raj
---
tools/sg_write_buffer/Makefile.am | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/sg_write_buffer/Makefile.am
b/tools/sg_write_buffer/Makefile.am
index 922c328..19c438d 100644
--- a/tools/sg_write_bu
GNU senorship hit me again, on Phoronix. This is LKML, a usenet mailing
list. So lets try again here.
Linus Torvalds, Richard Stallman, and Andrew Tanenbaum all are
pedophilia victims. And oddly enough think they are gods because of this.
On Linux forums, fanboys attack, because they sympath
ANWALTSKANZLEI JULIA SCHNEIDER & CO.
AV/DE GRAN VIA NO.38, 28008 MADRID. SPAIN
TEL.+34 638 580 441. FAX: +34 931-702-120
E-MAIL: infoofic...@collector.org
Eingetragener Fall NR: UNCCORG / KA749IMF
Sehr geehrte / r Fondsempfänger / E-Mail-Adresse Eigentümer,
Abschließende Mitteilung für die
On Fri, Aug 10, 2018 at 08:58:37AM -0500, Bjorn Helgaas wrote:
> On Fri, Aug 10, 2018 at 05:25:01PM +0800, joeyli wrote:
> > On Wed, Aug 08, 2018 at 04:23:22PM -0500, Bjorn Helgaas wrote:
> > ...
[...snip]
> > hm... I have another question that it may not relates to this issue. I
> > was tracing th
On Sat, Aug 11, 2018 at 1:20 PM, David Howells wrote:
> Miklos Szeredi wrote:
>
>> You can determine at fsopen() time whether the filesystem is able to
>> support the O_EXCL behavior? If so, then it's trivial to enable this
>> conditionally. I think that's what Eric is asking for, it's obviousl
Remove null ptr check before kfree because kfree is null ptr safe.
Issue found by checkpatch.
Signed-off-by: Sumit Kumar
---
drivers/staging/gasket/gasket_page_table.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/gasket/gasket_page_table.c
b/drivers/
Fixes: 851e534f5d75 ("clk: qcom: Add Global Clock controller (GCC) driver for
SDM660")
Signed-off-by: kbuild test robot
---
gcc-sdm660.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/qcom/gcc-sdm660.c b/drivers/clk/qcom/gcc-sdm660.c
index bdb445a..cec8b41 1
://github.com/0day-ci/linux/commits/Craig-Tatlor/clk-qcom-Add-Global-Clock-controller-GCC-driver-for-SDM660/20180811-150111
base: https://git.kernel.org/pub/scm/linux/kernel/git/agross/linux.git
for-next
reproduce:
# apt-get install sparse
make ARCH=x86_64 allmodconfig
Hi,
I noticed the following spurious traceback in next-20180810 when booting an
i386 image in qemu.
[0.00] [ cut here ]
[0.00] CPA: called for zero pte. vaddr = cffe cpa->vaddr = cffe
[0.00] WARNING: CPU: 0 PID: 0 at arch/x86/mm/pageattr.c
On 11.08.2018 18:57, Russell King - ARM Linux wrote:
> On Sat, Aug 11, 2018 at 12:31:27PM +0200, Stefan Agner wrote:
>> ARM stack unwinding is upstream since 2009 and has been proven
>> working well. At this time it is the preferred stack unwinding
>> support since it also supports Thumb 2. Do not
LTC1665/LTC1660 is a 8/10-bit Digital-to-Analog Converter
(DAC) with eight individual channels.
Signed-off-by: Marcus Folkesson
---
drivers/iio/dac/Kconfig | 10 ++
drivers/iio/dac/Makefile | 1 +
drivers/iio/dac/ltc166x.c | 244 ++
3 files chang
LTC1665/LTC1660 is a 8/10-bit Digital-to-Analog Converter (DAC)
with eight individual channels.
Signed-off-by: Marcus Folkesson
---
.../devicetree/bindings/iio/dac/ltc166x.txt | 21 +
1 file changed, 21 insertions(+)
create mode 100644 Documentation/devicetree/bindin
Add entry for ltc166x DAC driver and add myself as
maintainer of this driver.
Signed-off-by: Marcus Folkesson
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9276da915d9d..2dc4c773fb2e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8363,
On Sat, Aug 11, 2018 at 5:42 AM, Tomas Winkler wrote:
> What platform is this? This is not regular 0xfed4 address space. I
> guess this is BYT or CHT. It's better to get dmideoce dump as well.
Hello Tomas, Jarkko, all,
I'm not sure what's up with that. I've updated the firmware to the
late
Miklos Szeredi wrote:
> You can determine at fsopen() time whether the filesystem is able to
> support the O_EXCL behavior? If so, then it's trivial to enable this
> conditionally. I think that's what Eric is asking for, it's obviously
> not fair to ask for a change in behavior of the legacy in
Hello,
syzbot found the following crash on:
HEAD commit:2b769bb85b48 Add linux-next specific files for 20180807
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1356aef040
kernel config: https://syzkaller.appspot.com/x/.config?x=547d800b8773c2c5
dashb
On Sat, Aug 11, 2018 at 3:56 PM, Michael Jin wrote:
> On Sat, Aug 11, 2018 at 9:30 AM, Pu Wen wrote:
>> @@ -1051,6 +1065,16 @@ static void determine_memory_type(struct amd64_pvt
>> *pvt)
>> else
>> pvt->dram_type = MEM_DDR4;
>> return;
>> +
On Sat, Aug 11, 2018 at 12:31:27PM +0200, Stefan Agner wrote:
> ARM stack unwinding is upstream since 2009 and has been proven
> working well. At this time it is the preferred stack unwinding
> support since it also supports Thumb 2. Do not scare people
> and drop the EXPERIMENTAL mark.
Actually,
On Saturday, August 11, 2018 6:25:19 PM CEST Craig Tatlor wrote:
> Add initial pinctrl driver to support pin configuration with
> pinctrl framework for sdm660.
> Based off CAF implementation.
>
> Signed-off-by: Craig Tatlor
> ---
>
> diff --git
> a/Documentation/devicetree/bindings/pinctrl/qcom
On Sat, Aug 11, 2018 at 9:30 AM, Pu Wen wrote:
> diff --git a/drivers/edac/amd64_edac.c b/drivers/edac/amd64_edac.c
> index 18aeabb..fb81354 100644
> --- a/drivers/edac/amd64_edac.c
> +++ b/drivers/edac/amd64_edac.c
> @@ -211,7 +211,7 @@ static int __set_scrub_rate(struct amd64_pvt *pvt, u32
> ne
Hello,
sorry to disturb you all but after one month and a half I never received
any comment about this patch set and I fear it ended up in a forgotten
corner. I would like to know if someone is considering it or not.
Thanks :)
On Monday, June 25, 2018 6:13:00 PM CEST Federico Vaga wrote:
> The
Hello,
syzbot found the following crash on:
HEAD commit:2b769bb85b48 Add linux-next specific files for 20180807
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=154d667240
kernel config: https://syzkaller.appspot.com/x/.config?x=547d800b8773c2c5
dashb
This patch fixes some issues with missing SPDX-License-Identifier comments.
Signed-off-by: Michael Anckaert
---
Changes in v2:
- Removed unrelated change to different patch.
drivers/staging/netlogic/platform_net.c | 1 +
drivers/staging/netlogic/platform_net.h | 1 +
drivers/staging/netlogic
/linux/commits/Rafael-J-Wysocki/cpuidle-menu-Handle-stopped-tick-more-aggressively/20180811-191914
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
linux-next
config: mips-allyesconfig (attached as .config)
compiler: mips-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0
reproduce
On Sat, Aug 11, 2018 at 06:15:05PM +0200, Michael Anckaert wrote:
> This patch fixes some issues with missing SPDX-License-Identifier
> comments.
>
> Disclaimer: this is my first patch and instructions were taken from the
> KernelNewbies project.
This does not belong in a changelog comment. If
Initial device tree support for Qualcomm SDM630 SoC and
Sony Pioneer (Xperia XA2).
SDM630 is based off of the SDM660 soc and all SDM660 specific drivers are
compatible with it. SDM660 is also based off of MSM8998 so it uses some
of its drivers aswell.
The device tree is based on the CAF 4.4 kerne
Add initial pinctrl driver to support pin configuration with
pinctrl framework for sdm660.
Based off CAF implementation.
Signed-off-by: Craig Tatlor
---
.../bindings/pinctrl/qcom,sdm660-pinctrl.txt | 195 +++
drivers/pinctrl/qcom/Kconfig | 10 +
drivers/pinctrl/qcom/Makefile
Add the compatible for SDM660.
This does not need clocks to do scm calls
Signed-off-by: Craig Tatlor
---
Documentation/devicetree/bindings/firmware/qcom,scm.txt | 1 +
drivers/firmware/qcom_scm.c | 3 +++
2 files changed, 4 insertions(+)
diff --git a/Documentation/de
Add the compatible for the RPM in SDM660, so that rpm resources can be
made available.
Signed-off-by: Craig Tatlor
---
Documentation/devicetree/bindings/soc/qcom/qcom,smd-rpm.txt | 1 +
drivers/soc/qcom/smd-rpm.c | 1 +
2 files changed, 2 insertions(+)
diff --gi
This patch fixes some issues with missing SPDX-License-Identifier
comments.
Disclaimer: this is my first patch and instructions were taken from the
KernelNewbies project.
Signed-off-by: Michael Anckaert
---
drivers/staging/netlogic/Kconfig| 6 +++---
drivers/staging/netlogic/platform_
On Sat, 11 Aug 2018 00:57:12 -0700
Song Liu wrote:
> > +
> > +static void delayed_uprobe_delete(struct delayed_uprobe *du)
> > +{
> > + if (!du)
> > + return;
> Do we really need this check?
I'd suggest we keep it. It's not a fast path, and operations like this
should reall
Hi Parthiban,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on iio/togreg]
[also build test ERROR on v4.18-rc8 next-20180810]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/
On 06/08/2018 12:58 AM, Florian Fainelli wrote:
> Per the ARM reference manual for the Cortex-A15, The ACTLR:
>
> Is a read/write register.
>
> Common to the Secure and Non-secure states.
>
> Is only accessible from PL1 or higher, with access rights that depend
> on the mode:
>
> * Read
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: f8a79d5c7ef47c62d97a30e16064caf2ef91f648
Colin Ian King (1):
ftrace: Remove unused pointer ftrace_swapper_pid
Erica Bugden (1):
ftrace: Add missing check for existing hwlat thread
Francis De
From: "Joel Fernandes (Google)"
In the last patch in this series, we are making lockdep register hooks
onto the irq_{disable,enable} tracepoints. These tracepoints use the
_rcuidle tracepoint variant. In this series we switch the _rcuidle
tracepoint callers to use SRCU instead of sched-RCU. Inord
From: Paul McKenney
This is needed for a future tracepoint patch that uses srcu, and to make
sure it doesn't call into lockdep.
tracepoint code already calls notrace variants for rcu_read_lock_sched
so this patch does the same for srcu which will be used in a later
patch. Keeps it consistent wit
From: "Joel Fernandes (Google)"
Split reset functions into seperate functions in preparation
of future patches that need to do tracer specific reset.
Link: http://lkml.kernel.org/r/20180628182149.226164-4-j...@joelfernandes.org
Reviewed-by: Namhyung Kim
Signed-off-by: Joel Fernandes (Google)
From: Masami Hiramatsu
Remove using_ftrace_ops_list_func() since it is no longer used.
Using ftrace_ops_list_func() has been introduced by commit 7eea4fce0246
("tracing/stack_trace: Skip 4 instead of 3 when using ftrace_ops_list_func")
as a helper function, but its caller has been removed by com
From: "Joel Fernandes (Google)"
Here we introduce a test module for introducing a long preempt or irq
disable delay in the kernel which the preemptoff or irqsoff tracers can
detect. This module is to be used only for test purposes and is default
disabled.
Following is the expected output (only b
From: "Steven Rostedt (VMware)"
Nothing uses unregister_trigger() outside of trace_events_trigger.c file,
thus it should be static. Not sure why this was ever converted, because
its counter part, register_trigger(), was always static.
Signed-off-by: Steven Rostedt (VMware)
---
kernel/trace/tra
From: Masami Hiramatsu
Remove ftrace_nr_registered_ops() because it is no longer used.
ftrace_nr_registered_ops() has been introduced by commit ea701f11da44
("ftrace: Add selftest to test function trace recursion protection"), but
its caller has been removed by commit 05cbbf643b8e ("tracing: Fix
From: "Steven Rostedt (VMware)"
The function enable_trace_kprobe() performs slightly differently if the file
parameter is passed in as NULL on non-NULL. Instead of checking file twice,
move the code between the two tests into a static inline helper function to
make the code easier to follow.
Lin
From: kbuild test robot
Automatically found by kbuild test robot.
Fixes: ffdc73a3b2ad ("lib: Add module for testing preemptoff/irqsoff latency
tracers")
Signed-off-by: kbuild test robot
Signed-off-by: Steven Rostedt (VMware)
---
kernel/trace/preemptirq_delay_test.c | 2 +-
1 file changed, 1
From: "Steven Rostedt (VMware)"
The value of ring_buffer_record_is_on() is either true or false, so have its
return value be bool.
Signed-off-by: Steven Rostedt (VMware)
---
include/linux/ring_buffer.h | 2 +-
kernel/trace/ring_buffer.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
From: Francis Deslauriers
Move selftest function to its own compile unit so it can be compiled
with the ftrace cflags (CC_FLAGS_FTRACE) allowing it to be probed
during the ftrace startup tests.
Link:
http://lkml.kernel.org/r/153294604271.32740.16490677128630177030.stgit@devbox
Signed-off-by: F
From: Masami Hiramatsu
Prohibit kprobe-events probing on notrace functions. Since probing on a
notrace function can cause a recursive event call. In most cases those are just
skipped, but in some cases it falls into an infinite recursive call.
This protection can be disabled by the kconfig
CONF
From: "Joel Fernandes (Google)"
get_cpu_var disables preemption which has the potential to call into the
preemption disable trace points causing some complications. There's also
no need to disable preemption in uses of get_lock_stats anyway since
preempt is already disabled. So lets simplify the
From: "Steven Rostedt (VMware)"
Currently, when one echo's in 1 into tracing_on, the current tracer's
"start()" function is executed, even if tracing_on was already one. This can
lead to strange side effects. One being that if the hwlat tracer is enabled,
and someone does "echo 1 > tracing_on" in
From: "Steven Rostedt (VMware)"
There's code that expects tracer_tracing_is_on() to be either true or false,
not some random number. Currently, it should only return one or zero, but
just in case, change its return value to bool, to enforce it.
Signed-off-by: Steven Rostedt (VMware)
---
kernel
From: "Steven Rostedt (VMware)"
The start function of the hwlat tracer should never be called when the hwlat
thread already exists. If it is called, do a WARN_ON().
Signed-off-by: Steven Rostedt (VMware)
---
kernel/trace/trace_hwlat.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
From: Zubin Mithra
tracefs_ops is initialized inside tracefs_create_instance_dir and not
modified after. tracefs_create_instance_dir allows for initialization
only once, and is called from create_trace_instances(marked __init),
which is called from tracer_init_tracefs(marked __init). Also, mark
t
From: "Joel Fernandes (Google)"
This patch detaches the preemptirq tracepoints from the tracers and
keeps it separate.
Advantages:
* Lockdep and irqsoff event can now run in parallel since they no longer
have their own calls.
* This unifies the usecase of adding hooks to an irqsoff and irqson
e
From: "Steven Rostedt (VMware)"
The value of ring_buffer_record_is_set_on() is either true or false, so have
its return value be bool.
Signed-off-by: Steven Rostedt (VMware)
---
include/linux/ring_buffer.h | 2 +-
kernel/trace/ring_buffer.c | 2 +-
2 files changed, 2 insertions(+), 2 deletion
From: "Joel Fernandes (Google)"
In recent tests with IRQ on/off tracepoints, a large performance
overhead ~10% is noticed when running hackbench. This is root caused to
calls to rcu_irq_enter_irqson and rcu_irq_exit_irqson from the
tracepoint code. Following a long discussion on the list [1] abou
From: "Steven Rostedt (VMware)"
Joel Fernandes created a nice patch that cleaned up the duplicate hooks used
by lockdep and irqsoff latency tracer. It made both use tracepoints. But it
caused lockdep to trigger several false positives. We have not figured out
why yet, but removing lockdep from us
From: Masami Hiramatsu
Fix within_notrace_func() to check only notrace functions and to ignore the
kprobe-event which can not solve symbol addresses.
within_notrace_func() returns true if the given kprobe events probe point
seems to be out-of-range. But that is not the correct place to check for
From: "Joel Fernandes (Google)"
Recently we tried to make the preemptirqsoff tracer to use irqsoff
tracepoint probes. However this causes issues as reported by Masami:
[2.271078] Testing tracer preemptirqsoff: .. no entries found ..FAILED!
[2.381015] WARNING: CPU: 0 PID: 1 at /home/mhiramat/ksrc
From: "Gustavo A. R. Silva"
Return statements in functions returning bool should use true or false
instead of an integer value.
This code was detected with the help of Coccinelle.
Link: http://lkml.kernel.org/r/20180802010056.ga31...@embeddedor.com
Signed-off-by: Gustavo A. R. Silva
Signed-of
From: "Steven Rostedt (VMware)"
I was hitting the following warning:
WARNING: CPU: 0 PID: 1 at kernel/trace/trace_irqsoff.c:631
tracer_hardirqs_off+0x15/0x2a
Modules linked in:
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.0-rc6-test+ #13
Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), BIO
From: "Steven Rostedt (VMware)"
Joel Fernandes created a nice patch that cleaned up the duplicate hooks used
by lockdep and irqsoff latency tracer. It made both use tracepoints. But the
latency tracer is triggering warnings when using tracepoints to call into
the latency tracer's routines. Mainly
From: "Joel Fernandes (Google)"
Since we switched to using SRCU for tracepoints used in the idle path,
we can no longer use rcu_dereference_sched for dereferencing points in
trace-event hooks.
Since tracepoints can now use either SRCU or sched-RCU, just use
rcu_dereference_raw for traceevents ju
From: Masami Hiramatsu
Fix kprobe string argument testcase to not probe notrace
function. Instead, it probes tracefs function which must
be available with ftrace.
Link:
http://lkml.kernel.org/r/153294607107.32740.1664854684396589624.stgit@devbox
Signed-off-by: Masami Hiramatsu
Signed-off-by:
From: "Joel Fernandes (Google)"
Here we add unit tests for the preemptoff and irqsoff tracer by using a
kernel module introduced previously to trigger long preempt or irq
disabled sections in the kernel.
Link: http://lkml.kernel.org/r/20180711063540.91101-3-j...@joelfernandes.org
Reviewed-by: M
From: Erica Bugden
The hwlat tracer uses a kernel thread to measure latencies. The function
that creates this kernel thread, start_kthread(), can be called when the
tracer is initialized and when the tracer is explicitly enabled.
start_kthread() does not check if there is an existing hwlat kernel
From: Colin Ian King
Pointer ftrace_swapper_pid is defined but is never used hence it is
redundant and can be removed. The use of this variable was removed
in commit 345ddcc882d8 ("ftrace: Have set_ftrace_pid use the bitmap
like events do").
Cleans up clang warning:
warning: 'ftrace_swapper_pid'
From: "Steven Rostedt (VMware)"
While debugging another bug, I was looking at all the synchronize*()
functions being used in kernel/trace, and noticed that trace_uprobes was
using synchronize_sched(), with a comment to synchronize with
{u,ret}_probe_trace_func(). When looking at those functions,
From: "Steven Rostedt (VMware)"
Now that some trace events can be protected by srcu_read_lock(tracepoint_srcu),
we need to make sure all locations that depend on this are also protected.
There were many places that did a synchronize_sched() thinking that it was
enough to protect againts access to
From: "Steven Rostedt (VMware)"
When enabling trace events via the kernel command line, I hit this warning:
WARNING: CPU: 0 PID: 13 at kernel/rcu/srcutree.c:236
check_init_srcu_struct+0xe/0x61
Modules linked in:
CPU: 0 PID: 13 Comm: watchdog/0 Not tainted 4.18.0-rc6-test+ #6
Hardware name: MSI
Tool cpupower is useful to get CPU frequency information and monitor
power stats on Hygon platforms. So enable platform support to cpupower
for Hygon Dhyana Family 18h processors by checking vendor ID and vendor
string.
Signed-off-by: Pu Wen
---
tools/power/cpupower/utils/cpufreq-info.c
To make AMD64 EDAC and MCE drivers working on Hygon platforms, add
vendor checking for Hygon by using the code path of AMD 0x17. Add a
vendor field to struct amd64_pvt and initialize it in per_family_init
for vendor checking.
Also Hygon PCI Device ID DF_F0/DF_F6(0x1460/0x1466) of Host bridges
is n
Enable ACPI cpufreq driver support for Hygon by adding family ID check
along with AMD.
As Hygon platforms have SMBus device(PCI device ID 0x790b), enable Hygon
support to function amd_freq_sensitivity_init().
Signed-off-by: Pu Wen
---
drivers/cpufreq/acpi-cpufreq.c | 5 +
drivers/cp
For Dhyana processors have NONSTOP TSC feature, so enable the support
to ACPI driver.
Signed-off-by: Pu Wen
---
drivers/acpi/acpi_pad.c | 1 +
drivers/acpi/processor_idle.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/acpi/acpi_pad.c b/drivers/acpi/acpi_pad.c
index 552c1f7
Hygon Dhyana CPU has the SVM feature as AMD family 17h does.
Add Hygon support in the KVM infrastructure.
Signed-off-by: Pu Wen
---
arch/x86/include/asm/kvm_emulate.h | 4
arch/x86/include/asm/virtext.h | 5 +++--
arch/x86/kvm/emulate.c | 11 ++-
3 files changed, 1
Hygon machine check arch is similar to AMD family 17h. To enable the MCE
infrastructure support, add CPU vendor check for Hygon to share the code
path of AMD.
Add hygon mce init function mce_hygon_feature_init() to minimize further
maintenance effort.
Signed-off-by: Pu Wen
---
arch/x86/include/
Hygon PMU arch is similar to AMD Family 17h. To support Hygon PMU, the
initialization flow for it just call amd_pmu_init() and change PMU name
to "HYGON". To share AMD's flow, add code check for Hygon family ID 18h
to run the code path of AMD family 17h in core/uncore functions.
Signed-off-by: Pu
To share codes between AMD and Hygon to mitigate Spectre V2 Retpoline
vulnerability, rename macros SPECTRE_V2_RETPOLINE_MINIMAL_AMD to
SPECTRE_V2_RETPOLINE_MINIMAL_LFENCE, and SPECTRE_V2_CMD_RETPOLINE_AMD
to SPECTRE_V2_CMD_RETPOLINE_LFENCE.
As Hygon processors are not affected by meltdown vulnerab
Hygon Dhyana shares similar perfctr arch with AMD family 17h.
It returns the bit offset of the performance counter register and the
event selection register for Hygon CPU in the similar way as AMD does.
Signed-off-by: Pu Wen
---
arch/x86/kernel/cpu/perfctr-watchdog.c | 2 ++
1 file changed, 2 in
Hygon processors use modern APIC, so just return in modern_apic() and
sync_Arb_IDs(). And should break in switch case in detect_init_API().
When running on 32 bit mode, should set bigsmp if there are more than
8 cores.
Signed-off-by: Pu Wen
---
arch/x86/kernel/apic/apic.c | 19 +
As Hygon register its PCI Vendor ID as a new one "0x1d94", so add a new
definition PCI_VENDOR_ID_HYGON in include/linux/pci_ids.h.
Also Hygon PCI Device ID(0x1450/0x1463/0x1464) for Host bridge is added
to amd_nb.c. And it need to define new arrays for Hygon:
hygon_root_ids[], hygon_nb_misc_ids[],
The ideal_nops for Dhyana processors should be p6_nops.
Signed-off-by: Pu Wen
---
arch/x86/kernel/alternative.c | 4
1 file changed, 4 insertions(+)
diff --git a/arch/x86/kernel/alternative.c b/arch/x86/kernel/alternative.c
index a481763..8f4925b 100644
--- a/arch/x86/kernel/alternative.c
Dhyana use no delay in smp_quirk_init_udelay(), and return in
mwait_play_dead() as AMD does.
Signed-off-by: Pu Wen
---
arch/x86/kernel/smpboot.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
index db9656e..32eec7f
Hygon CPU have a special magic MSR way to force WB for memory >4GB,
and also support TOP_MEM2. Therefore, it is necessary to add Hygon
support in amd_special_default_mtrr().
The MtrrFixDramModEn bit on Hygon platform should also be set to 1
during BIOS initialization of the fixed MTRRs, then clear
Add x86 architecture support for new processor Hygon Dhyana Family 18h.
Rework to create a separated file(arch/x86/kernel/cpu/hygon.c) from the
AMD init one(arch/x86/kernel/cpu/amd.c) to initialize Dhyana CPU. In
this way we can remove old AMD architecture support codes from Hygon
code path and gen
Hygon Dhyana processor has the topology extensions bit in CPUID.
With this bit kernel can get the cache info. So add support
in cpuid4_cache_lookup_regs() to get the correct cache size.
Dhyana also find num_cache_leaves via CPUID leaf 0x801d, so
add Hygon support in find_num_cache_leaves().
A
On Sat, 2018-08-11 at 08:21 -0400, J. Bruce Fields wrote:
> On Sat, Aug 11, 2018 at 07:51:13AM -0400, Jeff Layton wrote:
> > On Thu, 2018-08-09 at 20:29 -0400, J. Bruce Fields wrote:
> > > On Fri, Aug 10, 2018 at 08:12:43AM +1000, NeilBrown wrote:
> > > > On Thu, Aug 09 2018, J. Bruce Fields wrote:
We would like to check if your photos need editing. We can do it for you.
Our image editing is for web store photos, jewelries images and beauty and
portrait photos etc.
It is including cut out and clipping path , and also retouching if it is
needed.
We can do test on your photos. Just send us a
On Sat, Aug 11, 2018 at 07:56:25AM -0400, Jeff Layton wrote:
> FWIW, I did a bit of testing with lockperf tests that I had written on
> an earlier rework of this code:
>
> https://git.samba.org/jlayton/linux.git/?p=jlayton/lockperf.git;a=summary
>
>
> The posix01 and flock01 tests in there s
We would like to check if your photos need editing. We can do it for you.
Our image editing is for web store photos, jewelries images and beauty and
portrait photos etc.
It is including cut out and clipping path , and also retouching if it is
needed.
We can do test on your photos. Just send us a
On Sat, Aug 11, 2018 at 07:51:13AM -0400, Jeff Layton wrote:
> On Thu, 2018-08-09 at 20:29 -0400, J. Bruce Fields wrote:
> > On Fri, Aug 10, 2018 at 08:12:43AM +1000, NeilBrown wrote:
> > > On Thu, Aug 09 2018, J. Bruce Fields wrote:
> > >
> > > > I think there's also a problem with multiple tasks
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f313b43be461f157755a57c1156f86abe10588de
commit: 816f670623692b5da2787f278cbfdb331ed29b8a net/mlx5e: Properly check if
hairpin is possible between two functions
New smatch warnings:
drivers/net/ethernet/mel
On Fri, 2018-08-10 at 11:47 -0400, J. Bruce Fields wrote:
> On Fri, Aug 10, 2018 at 01:17:14PM +1000, NeilBrown wrote:
> > On Thu, Aug 09 2018, J. Bruce Fields wrote:
> >
> > > On Fri, Aug 10, 2018 at 11:50:58AM +1000, NeilBrown wrote:
> > > > You're good at this game!
> > >
> > > Everybody's got
On Thu, 2018-08-09 at 20:29 -0400, J. Bruce Fields wrote:
> On Fri, Aug 10, 2018 at 08:12:43AM +1000, NeilBrown wrote:
> > On Thu, Aug 09 2018, J. Bruce Fields wrote:
> >
> > > I think there's also a problem with multiple tasks sharing the same
> > > lock owner.
> > >
> > > So, all locks are excl
ARM stack unwinding is upstream since 2009 and has been proven
working well. At this time it is the preferred stack unwinding
support since it also supports Thumb 2. Do not scare people
and drop the EXPERIMENTAL mark.
Signed-off-by: Stefan Agner
---
arch/arm/Kconfig.debug | 2 +-
1 file changed,
val2 is responsible for the floating part of the number to be
written to the device. We don't need the floating part
while writing the oversampling ratio for BME680 since the
available oversampling ratios are pure natural numbers.
So, add a sanity check to make sure val2 is 0.
Signed-off-by: Hima
1 - 100 of 122 matches
Mail list logo
