Hi Andrew,
On 8/8/19 6:32 AM, Andrew Lunn wrote:
>> Let me prepare patch v2 using device tree. I'm not sure if standard
>> "mac-address" fits this situation because all we need is an offset
>> (integer) and BMC MAC is calculated by adding the offset to NIC's
>> MAC address. Anyways, let me work
From: Tejas Patel
For "0" requirement which is used to inform firmware that
device is not required currently by master, Versal LibPM disables
clock, power it down and reset the device. genpd_power_off()
is being called during runtime suspend also. So, if any device
goes to runtime suspend state
On Thu 08-08-19 18:57:02, ndrw...@redhazel.co.uk wrote:
>
>
> On 8 August 2019 17:32:28 BST, Michal Hocko wrote:
> >
> >> Would it be possible to reserve a fixed (configurable) amount of RAM
> >for caches,
> >
> >I am afraid there is nothing like that available and I would even argue
> >it
The *pte_lookup functions can be removed and be easily replaced with
get_user_pages_fast functions. In the case of atomic lookup,
__get_user_pages_fast is used which does not fall back to slow
get_user_pages. get_user_pages_fast on the other hand tries to use
__get_user_pages_fast but fallbacks to
From: Jin Yao
The events defined in pmu-events JSON are parsed and added into perf
tool. For fixed counters, we handle the encodings between JSON and perf
by using a static array fixed[].
But the fixed[] has missed an important event "cpu_clk_unhalted.core".
For example, on the Tremont
On Thu, Aug 08, 2019 at 06:37:06PM +0300, Tomer Maimon wrote:
> for example in our driver we modify the access type (singe, dual or quad)
> according the op->addr.buswidth
> for example in the npcm_fiu_set_drd function.
> regmap_update_bits(fiu->regmap, NPCM_FIU_DRD_CFG,
>
In this 4th version of the patch series, I have compressed the patches
of the v2 patch series into one patch. This was suggested by Christoph Hellwig.
The suggestion was to remove the pte_lookup functions and use the
get_user_pages* functions directly instead of the pte_lookup functions.
There
From: Thomas Richter
During execution of command 'perf top' the error message:
Not enough memory for annotating '__irf_end' symbol!)
is emitted from this call sequence:
__cmd_top
perf_top__mmap_read
perf_top__mmap_read_idx
perf_event__process_sample
From: Thomas Richter
On s390 the modules loaded in memory have the text segment located after
the GOT and Relocation table. This can be seen with this output:
[root@m35lp76 perf]# fgrep qeth /proc/modules
qeth 151552 1 qeth_l2, Live 0x03ff800b2000
...
[root@m35lp76 perf]# cat
From: Jiri Olsa
Michael reported an issue with perf bench numa failing with binding to
cpu0 with '-0' option.
# perf bench numa mem -p 3 -t 1 -P 512 -s 100 -zZcm0 --thp 1 -M 1 -ddd
# Running 'numa/mem' benchmark:
# Running main, "perf bench numa numa-mem -p 3 -t 1 -P 512 -s 100 -zZcm0
From: Ian Rogers
These paths point to the wrong location but still work because they get
picked up by a -I flag that happens to direct to the correct file. Fix
paths to point to the correct location without -I flags.
Signed-off-by: Ian Rogers
Cc: Alexander Shishkin
Cc: Andi Kleen
Cc: Jiri
From: Masanari Iida
This patch fix a spelling typo in a variable name in the Documentation Makefile.
Signed-off-by: Masanari Iida
Reviewed-by: Mukesh Ojha
Cc: Alexander Shishkin
Cc: Namhyung Kim
Cc: Peter Zijlstra
Link: http://lkml.kernel.org/r/20190801032812.25018-1-standby2...@gmail.com
From: Arnaldo Carvalho de Melo
The code to disassemble BPF programs uses binutil's disassembling
routines, and those use in turn fprintf to print to a memstream FILE,
adding a newline at the end of each line, which ends up confusing the
TUI routines called from:
annotate_browser__write()
From: Adrian Hunter
Threads synthesized from /proc have comms with a start time of zero, and
not marked as "exec". Currently, there can be 2 such comms. The first is
created by processing a synthesized fork event and is set to the
parent's comm string, and the second by processing a synthesized
From: He Zhe
cpu_map__snprint_mask() would write to illegal memory pointed by
zalloc(0) when there is only one cpu.
This patch fixes the calculation and adds sanity check against the input
parameters.
Signed-off-by: He Zhe
Cc: Alexander Shishkin
Cc: Alexey Budankov
Cc: Jiri Olsa
Cc: Kan
From: He Zhe
The buffer containing the string used to set cpumask is overwritten at
the end of the string later in cpu_map__snprint_mask due to not enough
memory space, when there is only one cpu.
And thus causes the following failure:
$ perf ftrace ls
failed to reset ftrace
$
This
/acme/linux into perf/urgent
(2019-07-29 23:24:07 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-urgent-for-mingo-5.3-20190808
for you to fetch changes up to 8e6e5bea2e34c61291d00cb3f47560341aa84bc3:
perf pmu-events
On Thu 08-08-19 09:55:45, Mike Kravetz wrote:
> On 8/8/19 12:47 AM, Michal Hocko wrote:
> > On Thu 08-08-19 09:46:07, Michal Hocko wrote:
> >> On Wed 07-08-19 17:05:33, Mike Kravetz wrote:
> >>> Li Wang discovered that LTP/move_page12 V2 sometimes triggers SIGBUS
> >>> in the kernel-v5.2.3
On Thu 08-08-19 11:32:47, Edward Chron wrote:
> For an OOM event: print oomscore, memory pct, oom adjustment of the process
> that OOM kills and the totalpages value in kB (KiB) used in the calculation
> with the OOM killed process message. This is helpful to document why the
> process was
On Thu, Aug 08, 2019 at 07:57:53AM +0300, Denis Efremov wrote:
> octeon_mbox_process_cmd() directly writes the PCI_EXP_DEVCTL_BCR_FLR
> bit, which bypasses timing requirements imposed by the PCIe spec.
> This patch fixes the function to use the pcie_flr() interface instead.
>
> Signed-off-by:
> -Original Message-
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On
> Behalf Of Firo Yang
> Sent: Wednesday, August 7, 2019 9:04 PM
> To: net...@vger.kernel.org
> Cc: maciejromanfijalkow...@gmail.com; Firo Yang ;
> linux-kernel@vger.kernel.org;
For an OOM event: print oomscore, memory pct, oom adjustment of the process
that OOM kills and the totalpages value in kB (KiB) used in the calculation
with the OOM killed process message. This is helpful to document why the
process was selected by OOM at the time of the OOM event.
Sample message
Quoting Maulik Shah (2019-08-07 23:12:28)
> Qualcomm Technologies Inc's (QTI) chipsets support SoC level
> low power modes. Statistics for SoC sleep stats are produced
> by remote processor.
>
> Lets's add a driver to read the shared memory exported by the
> remote processor and export to sysfs.
Sunix Multi I/O boards are different to Timedia's.
This patch adds proper support for Sunix MIO boards with 1 parallel and
up to 4 serial ports.
Cc: Morris Ku
Cc: Debbie Liu
Signed-off-by: Kai-Heng Feng
---
drivers/parport/parport_serial.c | 44 +++-
1 file
Add support to Sunix serial boards with up to 16 ports.
Sunix board need its own setup callback instead of using Timedia's, to
properly support more than 4 ports.
Cc: Morris Ku
Cc: Debbie Liu
Signed-off-by: Kai-Heng Feng
---
drivers/tty/serial/8250/8250_pci.c | 93
On Fri, Feb 01, 2019 at 09:24:11AM +, Lee Jones wrote:
> On Tue, 29 Jan 2019, Jonathan Neuschäfer wrote:
>
> > The RN5T618 family of PMICs can be used as system management
> > controllers, in which case they handle poweroff and restart. Document
> > this capability by referring to the
On Thu, Aug 08, 2019 at 04:47:45PM +0200, Rafael J. Wysocki wrote:
> On Thu, Aug 8, 2019 at 3:43 PM Bjorn Helgaas wrote:
> > On Thu, Aug 08, 2019 at 12:10:06PM +0200, Rafael J. Wysocki wrote:
> > > From: Rafael J. Wysocki
> > >
> > > One of the modifications made by commit d916b1be94b6
From: YueHaibing
Date: Thu, 8 Aug 2019 22:26:23 +0800
> net/sched/sch_taprio.c:680:32: warning:
> entry_list_policy defined but not used [-Wunused-const-variable=]
>
> It is not used since commit a3d43c0d56f1 ("taprio: Add
> support adding an admin schedule")
>
> Reported-by: Hulk Robot
>
On Fri, 2019-08-02 at 21:18 -0700, Jens Axboe wrote:
> On 8/1/19 6:00 PM, Leonardo Bras wrote:
> > Applies some bits.h macros in order to improve readability of
> > linux/blk_types.h.
> >
> > Signed-off-by: Leonardo Bras
> > ---
> > include/linux/blk_types.h | 55
On Wed, Jul 31, 2019 at 11:35 AM Aaron Goidel wrote:
> As of now, setting watches on filesystem objects has, at most, applied a
> check for read access to the inode, and in the case of fanotify, requires
> CAP_SYS_ADMIN. No specific security hook or permission check has been
> provided to control
On Thu, Aug 8, 2019 at 3:01 AM Jessica Yu wrote:
> If you're confident that a hard dependency is not the right approach,
> then perhaps we could add a comment in the Kconfig (You could take a
> look at the comment under MODULE_SIG_ALL in init/Kconfig for an
> example)? If someone is configuring
On 8/8/19 12:09 PM, David Lechner wrote:
Then we can provide a vendor resource hook in the remoteproc driver to handle
these resources:
static int ti_pru_rproc_handle_rsc(struct rproc *rproc, u32 rsc_type, void *rsc,
int offset, int avail)
{
struct ti_pru_data *pru =
Dave Chinner reported a problem pointing a finger at commit
1c30844d2dfe ("mm: reclaim small amounts of memory when an
external fragmentation event occurs"). The report is extensive (see
https://lore.kernel.org/linux-mm/20190807091858.2857-1-da...@fromorbit.com/)
and it's worth recording the most
> Rather than printing a warning at mount time (which may be confusing
> to users for a problem they may never see), it makes sense to only
> print such a warning in the vanishingly small case that someone actually
> tries to modify the inode timestamp but it doesn't fit, rather than on
> the
From: Alexandru Ardelean
Date: Thu, 8 Aug 2019 15:30:11 +0300
> This changeset adds support for Analog Devices Industrial Ethernet PHYs.
> Particularly the PHYs this driver adds support for:
> * ADIN1200 - Robust, Industrial, Low Power 10/100 Ethernet PHY
> * ADIN1300 - Robust, Industrial, Low
From: Neil Armstrong
Date: Thu, 8 Aug 2019 13:40:59 +0200
> This patchsets converts the Amlogic Meson DWMAC glue bindings over to
> YAML schemas using the already converted dwmac bindings.
>
> The first patch is needed because the Amlogic glue needs a supplementary
> reg cell to access the
On Thu, 2019-08-01 at 19:38 -0300, Leonardo Bras wrote:
> Since commit 485ddb4b9741 ("1/2 splice: dont steal")' (2007),
> the SPLICE_F_MOVE support was removed (became a no-op according
> to man pages), and thus disabling steal operation that would make
> moving pages possible.
>
> This fixes the
Contrary to the description, the first parameter (n) should not be
passed as a pointer, but directly as an lvalue. This is possible because
do_div is a macro.
Signed-off-by: Jonathan Neuschäfer
Reviewed-by: Geert Uytterhoeven
---
v2:
- add Geert Uytterhoeven's R-b
v1:
-
When building withW=1, we get a warning..
CC arch/x86/kernel/cpu/common.o
arch/x86/kernel/cpu/common.c:1952:6: warning: no previous prototype for
'arch_smt_update' [-Wmissing-prototypes]
1952 | void arch_smt_update(void)
| ^~~
Provide the proper #include so the
On Thu, Aug 08, 2019 at 06:42:40PM +0300, Christoph Hellwig wrote:
> Use lockdep to check for held locks instead of using home grown
> asserts.
>
> @@ -319,7 +319,7 @@ int walk_page_range(struct mm_struct *mm, unsigned long
> start,
> if (!walk.mm)
> return -EINVAL;
>
> -
On Thu, Aug 08, 2019 at 07:26:10PM +0900, Byungchul Park wrote:
> On Wed, Aug 07, 2019 at 05:45:04AM -0400, Joel Fernandes wrote:
> > On Tue, Aug 06, 2019 at 04:56:31PM -0700, Paul E. McKenney wrote:
>
> [snip]
>
> > > On Tue, Aug 06, 2019 at 05:20:40PM -0400, Joel Fernandes (Google) wrote:
> >
On Thu, Aug 08, 2019 at 11:23:17PM +0900, Byungchul Park wrote:
> On Thu, Aug 8, 2019 at 9:56 PM Joel Fernandes wrote:
> >
> > On Thu, Aug 08, 2019 at 06:52:32PM +0900, Byungchul Park wrote:
> > > On Wed, Aug 07, 2019 at 10:52:15AM -0700, Paul E. McKenney wrote:
> > > > > > On Tue, Aug 06, 2019
On 08.08.19 19:26, Krzysztof Kozlowski wrote:
> Document the compatible for ANV32E61W EEPROM chip.
This chip is actually not an EEPROM, but a SPI nvSRAM. It can be
interfaced by the at25 driver similar to an EEPROM. This is not the
ideal solution, but it works until there's a proper driver for
On Thu, Jul 4, 2019 at 9:34 PM Mans Rullgard wrote:
>
> While the individual CHARLCD_BL_xxx options have help texts, the
> menu itself does not. Fix this.
>
> Signed-off-by: Mans Rullgard
Picked it up and added a bit of extra explanation, thanks!
Cheers,
Miguel
On Mon, Jul 8, 2019 at 2:37 PM zhengbin wrote:
>
> In panel_attach, if misc_register fails, we need to delete scan_timer,
> which was setup in keypad_init->init_scan_timer.
>
> Reported-by: Hulk Robot
> Signed-off-by: zhengbin
Picked it up, thanks!
Cheers,
Miguel
On Tue, Aug 6, 2019 at 4:25 PM Masanari Iida wrote:
>
> This patch fix a spelling typo in cfag12864b-example.c
>
> Signed-off-by: Masanari Iida
Picked it up, thanks!
Cheers,
Miguel
On Tue, Aug 6, 2019 at 9:18 AM Geert Uytterhoeven wrote:
>
> On Tue, Aug 6, 2019 at 9:16 AM Masahiro Yamada
> wrote:
> > This header is included in drivers/auxdisplay/. Make it a local header.
> >
> > Signed-off-by: Masahiro Yamada
>
> Reviewed-by: Geert Uytterhoeven
Picked it up, thanks!
On Tue, Aug 6, 2019 at 9:15 AM Masahiro Yamada
wrote:
>
> Add a header include guard just in case.
>
> Signed-off-by: Masahiro Yamada
Picked it up, thanks!
Cheers,
Miguel
On Thu, Aug 08, 2019 at 08:51:23AM +0200, 'Christoph Hellwig' wrote:
> On Wed, Aug 07, 2019 at 04:07:37PM -0700, Luck, Tony wrote:
> > On Wed, Aug 07, 2019 at 01:26:17PM -0700, Luck, Tony wrote:
> > > Ugh! The rule to do the compression was in arch/ia64/hp/sim/boot/Makefile
> > > which went away
Neil Armstrong writes:
> The Khadas VIM3 uses the Amlogic S922X or A311S SoC, both based on the
> Amlogic G12B SoC family, on a board with the same form factor as the
> VIM/VIM2 models. It ships in two variants; basic and
> pro which differ in RAM and eMMC size:
>
> - 2GB (basic) or 4GB (pro)
On 8 August 2019 17:32:28 BST, Michal Hocko wrote:
>
>> Would it be possible to reserve a fixed (configurable) amount of RAM
>for caches,
>
>I am afraid there is nothing like that available and I would even argue
>it doesn't make much sense either. What would you consider to be a
>cache? A
On Thu, Aug 8, 2019 at 8:42 AM Christoph Hellwig wrote:
>
> this series is based on a patch from Linus to split the callbacks
> passed to walk_page_range and walk_page_vma into a separate structure
> that can be marked const, with various cleanups from me on top.
The whole series looks good to
When building with C=2, sparse makes note of a number of things:
CHECK arch/x86/events/intel/rapl.c
arch/x86/events/intel/rapl.c:637:30: warning: symbol 'rapl_attr_update' was not
declared. Should it be static?
CHECK arch/x86/events/intel/cstate.c
arch/x86/events/intel/cstate.c:449:30:
On Thu, Aug 08, 2019 at 02:50:37PM +0100, Mark Rutland wrote:
> Hi Daniel,
>
> This is looking really good!
>
> I spotted a few more things we need to deal with, so I've suggested some
> (not even compile-tested) code for that below. Mostly that's just error
> handling, and using helpers to
On Thu, Aug 8, 2019 at 8:39 AM Mauro Carvalho Chehab
wrote:
>
> Please pull from:
> git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media
> media/v5.3-2
>
> For a fix at the vivid CEC support.
There's no vivid CEC fix there, and you already asked me to pull that
tag two weeks ago,
Adding "rng-seed" to dtb. It's fine to add this property if original
fdt doesn't contain it. Since original seed will be wiped after
read, so use a default size 128 bytes here.
Signed-off-by: Hsin-Yi Wang
Reviewed-by: Stephen Boyd
---
arch/arm64/kernel/machine_kexec_file.c | 18
Introducing a chosen node, rng-seed, which is an entropy that can be
passed to kernel called very early to increase initial device
randomness. Bootloader should provide this entropy and the value is
read from /chosen/rng-seed in DT.
Signed-off-by: Hsin-Yi Wang
Reviewed-by: Stephen Boyd
Currently in arm64, FDT is mapped to RO before it's passed to
early_init_dt_scan(). However, there might be some codes
(eg. commit "fdt: add support for rng-seed") that need to modify FDT
during init. Map FDT to RO after early fixups are done.
Signed-off-by: Hsin-Yi Wang
Reviewed-by: Stephen
Introducing a chosen node, rng-seed, which is an entropy that can be
passed to kernel called very early to increase initial device
randomness. This can be used for adding sufficient initial entropy
for stack canary. Especially architectures that lack per-stack canary.
Hsin-Yi Wang (3):
arm64:
Hey Saravana,
Thanks for the review!
On 8/8/19 2:51 AM, Saravana Kannan wrote:
On Wed, Aug 7, 2019 at 4:24 AM Sibi Sankar wrote:
On some Qualcomm SoCs, Operating State Manager (OSM) controls the
resources of scaling L3 caches. Add a driver to handle bandwidth
requests to OSM L3 from
Hi Douglas,
On Thursday 08 Aug 2019 at 14:18:57 (+0100), Douglas RAILLARD wrote:
> Add calls to arch_set_freq_scale() in qcom-cpufreq-hw driver to enable
> frequency invariance.
Is there a patch 2/2 ?
>
> Signed-off-by: Douglas RAILLARD
> ---
> drivers/cpufreq/qcom-cpufreq-hw.c | 10
When doing x86_emulate_instruction(EMULTYPE_SKIP) interrupt shadow has to
be cleared if and only if the skipping is successful.
There are two immediate issues:
- In SVM skip_emulated_instruction() we are not zapping interrupt shadow
in case kvm_emulate_instruction(EMULTYPE_SKIP) is used to
Various intercepts hard-code the respective instruction lengths to optimize
skip_emulated_instruction(): when next_rip is pre-set we skip
kvm_emulate_instruction(vcpu, EMULTYPE_SKIP). The optimization is, however,
incorrect: different (redundant) prefixes could be used to enlarge the
instruction.
These patterns are cleaned-up by the top-level Makefile
Signed-off-by: Masahiro Yamada
---
arch/nds32/boot/dts/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/arch/nds32/boot/dts/Makefile b/arch/nds32/boot/dts/Makefile
index fff8ade7a84f..f84bd529b6fd 100644
---
Just like we do with other intercepts, in vmrun_interception() we should be
doing kvm_skip_emulated_instruction() and not just RIP += 3. Also, it is
wrong to increment RIP before nested_svm_vmrun() as it can result in
kvm_inject_gp().
We can't call kvm_skip_emulated_instruction() after
Regardless of whether or not nested_svm_vmrun_msrpm() fails, we return 1
from vmrun_interception() so there's no point in doing goto. Also,
nested_svm_vmrun_msrpm() call can be made from nested_svm_vmrun() where
other nested launch issues are handled.
Suggested-by: Sean Christopherson
To avoid hardcoding xsetbv length to '3' we need to support decoding it in
the emulator.
Signed-off-by: Vitaly Kuznetsov
---
arch/x86/include/asm/kvm_emulate.h | 3 ++-
arch/x86/kvm/emulate.c | 23 ++-
arch/x86/kvm/svm.c | 1 +
On AMD, kvm_x86_ops->skip_emulated_instruction(vcpu) can, in theory,
fail: in !nrips case we call kvm_emulate_instruction(EMULTYPE_SKIP).
Currently, we only do printk(KERN_DEBUG) when this happens and this
is not ideal. Propagate the error up the stack.
On VMX, skip_emulated_instruction() doesn't
svm->next_rip is only used by skip_emulated_instruction() and in case
kvm_set_msr() fails we rightfully don't do that. Move svm->next_rip
advancement to 'else' branch to avoid creating false impression that
it's always advanced (and make it look like rdmsr_interception()).
This is a preparatory
Changes since v2 [Sean Christopherson]:
- Add Reviewed-by tags:
- PATCH2 replaced with the suggested "x86: kvm: svm: propagate errors from
skip_emulated_instruction()" approach.
- PATCH5 split into three separating vmrun_interception() from others and
implementing the suggested solution.
Signed-off-by: Masahiro Yamada
---
arch/um/kernel/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/um/kernel/Makefile b/arch/um/kernel/Makefile
index 2f36d515762e..89afc54f8699 100644
--- a/arch/um/kernel/Makefile
+++ b/arch/um/kernel/Makefile
@@ -13,7 +13,6 @@
When compiling with C=2, sparse warns:
CHECK arch/x86/events/intel/lbr.c
arch/x86/events/intel/lbr.c:276:1: warning: symbol 'lbr_from_quirk_key' was not
declared. Should it be static?
And yes, it can be static.
Signed-off-by: Valdis Kletnieks
diff --git a/arch/x86/events/intel/lbr.c
On 8/7/19 11:47 PM, Aaron Lu wrote:
> On Tue, Aug 06, 2019 at 02:19:57PM -0700, Tim Chen wrote:
>> +void account_core_idletime(struct task_struct *p, u64 exec)
>> +{
>> +const struct cpumask *smt_mask;
>> +struct rq *rq;
>> +bool force_idle, refill;
>> +int i, cpu;
>> +
>> +rq
On Thu, Aug 08, 2019 at 04:47:18PM +0200, Vlastimil Babka wrote:
> On 8/7/19 10:51 PM, Johannes Weiner wrote:
> > From 9efda85451062dea4ea287a886e515efefeb1545 Mon Sep 17 00:00:00 2001
> > From: Johannes Weiner
> > Date: Mon, 5 Aug 2019 13:15:16 -0400
> > Subject: [PATCH] psi: trigger the OOM
Document the compatible for ANV32E61W EEPROM chip.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Fabio Estevam
---
New patch
---
Documentation/devicetree/bindings/eeprom/at25.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/eeprom/at25.txt
Add vendor prefix for Anvo-Systems Dresden GmbH.
Signed-off-by: Krzysztof Kozlowski
Reviewed-by: Rob Herring
---
Changes since v3:
1. Add Rob's tag,
2. Remove Admatec (not needed anymore).
Changes since v2:
1. Use admatecde vendor prefix.
2. Add Anvo-Systems Dresden GmbH.
Changes since v1:
Add support for i.MX6UL modules from Kontron Electronics GmbH (before
acquisition: Exceet Electronics) and evalkit boards based on it:
1. N6310 SOM: i.MX6 UL System-on-Module, a 25x25 mm solderable module
(LGA pads and pin castellations) with 256 MB RAM, 1 MB NOR-Flash,
256 MB NAND and
On Thu, 8 Aug 2019 18:11:53 +0100
Will Deacon wrote:
> > We could make it more descriptive of what it will do and not the reason
> > for why it is done...
> >
> >
> > ARCH_FTRACE_SHIFT_STACK_TRACER
>
> Acked-by: Will Deacon
Thanks Will!
Here's the official patch.
From: "Steven Rostedt
Hello,
syzbot found the following crash on:
HEAD commit:1e78030e Merge tag 'mmc-v5.3-rc1' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1011831a60
kernel config: https://syzkaller.appspot.com/x/.config?x=4c7b914a2680c9c6
On 8/8/19 6:31 AM, Naresh Kamboju wrote:
selftests kvm all test cases need pre-required kernel configs for the
tests to get pass.
The KVM tests are skipped without these configs:
dev_fd = open(KVM_DEV_PATH, O_RDONLY);
if (dev_fd < 0)
exit(KSFT_SKIP);
On Thu, Aug 08, 2019 at 04:10:21PM +0100, Patrick Bellasi
wrote:
> Not sure to get what you mean here: I'm currently exposing uclamp to
> both v1 and v2 hierarchies.
cpu controller has different API for v1 and v2 hierarchies. My question
reworded is -- are the new knobs exposed in the legacy API
On Thu, Aug 08, 2019 at 04:08:10PM +0100, Patrick Bellasi
wrote:
> Well, if I've got correctly your comment in the previous message, I
> would say that at this stage we don't need RCU looks at all.
Agreed.
> Reason being that cpu_util_update_eff() gets called only from
> cpu_uclamp_write()
> On Aug 8, 2019, at 9:37 AM, Oleg Nesterov wrote:
>
> On 08/07, Song Liu wrote:
>>
>> @@ -399,7 +399,7 @@ static struct page *follow_pmd_mask(struct
>> vm_area_struct *vma,
>> spin_unlock(ptl);
>> return follow_page_pte(vma, address, pmd, flags, >pgmap);
>> }
On Thu, Aug 08, 2019 at 12:36:32PM -0400, Steven Rostedt wrote:
> On Thu, 8 Aug 2019 17:28:26 +0100
> Will Deacon wrote:
>
> > > + * Note, this may change in the future, and we will need to deal with
> > > that
> > > + * if it were to happen.
> > > + */
> > > +#define
> On Aug 8, 2019, at 9:33 AM, Oleg Nesterov wrote:
>
> On 08/07, Song Liu wrote:
>>
>> +void collapse_pte_mapped_thp(struct mm_struct *mm, unsigned long addr)
>> +{
>> +unsigned long haddr = addr & HPAGE_PMD_MASK;
>> +struct vm_area_struct *vma = find_vma(mm, haddr);
>> +struct
On Thu, Aug 08, 2019 at 11:38:08AM +0100, Mark Rutland wrote:
> On Wed, Aug 07, 2019 at 11:29:16PM -0400, Qian Cai wrote:
> > The commit 155433cb365e ("arm64: cache: Remove support for ASID-tagged
> > VIVT I-caches") introduced some compiation warnings from GCC (and
> > Clang) with
On 8/2/19 4:26 PM, Suman Anna wrote:
Point is different applications might use mapping differently as per
their firmware and driver/application design and their split across one
or more PRUs (design by contract). And we need to set this up at runtime
when the application driver is getting run.
On Thu, Aug 8, 2019 at 4:47 PM Rafael J. Wysocki wrote:
>
> On Thu, Aug 8, 2019 at 3:43 PM Bjorn Helgaas wrote:
> >
> > On Thu, Aug 08, 2019 at 12:10:06PM +0200, Rafael J. Wysocki wrote:
> > > From: Rafael J. Wysocki
> > >
> > > One of the modifications made by commit d916b1be94b6 ("nvme-pci:
On Sat, Jul 27, 2019 at 4:29 AM Linus Torvalds
wrote:
>
> On Fri, Jul 26, 2019 at 4:26 PM syzbot
> wrote:
> >
> > syzbot has bisected this bug to:
> >
> > commit 0e034f5c4bc408c943f9c4a06244415d75d7108c
> > Author: Linus Torvalds
> > Date: Wed May 18 18:51:25 2016 +
> >
> > iwlwifi:
On 8/8/19 12:47 AM, Michal Hocko wrote:
> On Thu 08-08-19 09:46:07, Michal Hocko wrote:
>> On Wed 07-08-19 17:05:33, Mike Kravetz wrote:
>>> Li Wang discovered that LTP/move_page12 V2 sometimes triggers SIGBUS
>>> in the kernel-v5.2.3 testing. This is caused by a race between hugetlb
>>> page
Hello,
syzbot found the following crash on:
HEAD commit:0d8b3265 Add linux-next specific files for 20190729
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1101fdc860
kernel config: https://syzkaller.appspot.com/x/.config?x=ae96f3b8a7e885f7
One of the more common cases of allocation size calculations is finding
the size of a structure that has a zero-sized array at the end, along
with memory for some number of elements for that array. For example:
struct sdhci_cdns_priv {
...
struct sdhci_cdns_phy_param
On 08/08/2019 16:58, Pierre-Louis Bossart wrote:
+++ b/Documentation/devicetree/bindings/soundwire/slave.txt
@@ -0,0 +1,46 @@
+SoundWire slave device bindings.
+
+SoundWire is a 2-pin multi-drop interface with data and clock line.
+It facilitates development of low cost, efficient, high
On Thu, 2019-08-08 at 18:40 +0200, Greg KH wrote:
> On Thu, Aug 08, 2019 at 06:39:05PM +0200, Greg KH wrote:
> > On Fri, Aug 02, 2019 at 03:05:05PM -0700, Joe Perches wrote:
> > > On Fri, 2019-08-02 at 14:55 -0700, Stephen Hemminger wrote:
> > > > On Fri, 2 Aug 2019 19:56:02 +
> > > > Jose
Hello,
syzbot found the following crash on:
HEAD commit:629f8205 Merge tag 'for-linus-20190730' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13e50eb460
kernel config: https://syzkaller.appspot.com/x/.config?x=e397351d2615e10
, On Thu, Aug 8, 2019 at 6:25 PM Doug Smythies wrote:
>
> On 2019.08.07 00:06 Viresh Kumar wrote:
>
> Thanks for your work on this.
>
> > Intel pstate driver exposes min_perf_pct and max_perf_pct sysfs files,
> > which can be used to force a limit on the min/max P state of the driver.
> > Though
Hello,
syzbot found the following crash on:
HEAD commit:70f4b4ac Add linux-next specific files for 20190730
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=107f7fc860
kernel config: https://syzkaller.appspot.com/x/.config?x=83083aa18c7fa5ce
Hello,
syzbot found the following crash on:
HEAD commit:4010b622 Merge branch 'dax-fix-5.3-rc3' of git://git.kerne..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13e2829fa0
kernel config: https://syzkaller.appspot.com/x/.config?x=e397351d2615e10
Hello,
syzbot found the following crash on:
HEAD commit:107e47cc vrf: make sure skb->data contains ip header to ma..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=139506d860
kernel config: https://syzkaller.appspot.com/x/.config?x=4dba67bf8b8c9ad7
Hello,
syzbot found the following crash on:
HEAD commit:ce96e791 Add linux-next specific files for 20190731
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12b2efd060
kernel config: https://syzkaller.appspot.com/x/.config?x=fca5b9d53db6585c
501 - 600 of 1111 matches
Mail list logo
