This patch implements the perf registers sampling and validation API
for riscv arch. The valid registers and their register ID are defined in
perf_regs.h. Perf tool can backtrace in userspace with unwind library
and the registers/user stack dump support.
Signed-off-by: Mao Han
CC: Palmer Dabbelt
This patch add support for perf callchain sampling on riscv platform.
The return address of leaf function is retrieved from pt_regs as
it is not saved in the outmost frame.
Signed-off-by: Mao Han
CC: Palmer Dabbelt
CC: linux-riscv
CC: Christoph Hellwig
CC: Guo Ren
---
arch/riscv/Makefile
This patch set add perf callchain(FP/DWARF) support for RISC-V.
It comes from the csky version callchain support with some
slight modifications. The patchset base on Linux 5.1.
CC: Palmer Dabbelt
CC: linux-riscv
CC: Christoph Hellwig
CC: Guo Ren
Changes since v2:
- fix inconsistent comment
This patch add support for DWARF register mappings and libdw registers
initialization, which is used by perf callchain analyzing when
--call-graph=dwarf is given.
Signed-off-by: Mao Han
CC: Palmer Dabbelt
CC: linux-riscv
CC: Christoph Hellwig
CC: Guo Ren
---
On Thu 16 May 2019 at 19:02, Robin Murphy wrote:
>> -/*
>> - * FIXME: need to provide subdriver defaults or separate dt parsing from
>> - * allocation.
>> - */
>> static int gnss_serial_parse_dt(struct serdev_device *serdev)
>> {
>> struct gnss_serial *gserial =
Use struct_size() helper to keep code simple.
Signed-off-by: xiaolinkui
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_ras.c
index 22bd21e..4717a64
Let's add Kees to CC for usercopy expertise...
On Thu 16-05-19 17:33:38, Dan Williams wrote:
> Jeff discovered that performance improves from ~375K iops to ~519K iops
> on a simple psync-write fio workload when moving the location of 'struct
> page' from the default PMEM location to DRAM. This
On Thu, May 16, 2019 at 11:40:10AM -0700, Yabin Cui wrote:
> In perf_output_put_handle(), an IRQ/NMI can happen in below location and
> write records to the same ring buffer:
> ...
> local_dec_and_test(>nest)
> ... <-- an IRQ/NMI can happen here
>
On Fri, May 17, 2019 at 5:09 PM Martin Schwidefsky
wrote:
>
> On Fri, 17 May 2019 15:54:24 +0900
> Masahiro Yamada wrote:
>
> > Commit e60fb8bf68d4 ("s390/cpacf: mark scpacf_query() as __always_inline")
> > was not enough to make sure to meet the 'i' (immediate) constraint for the
> > asm
From: Wanpeng Li
WARNING: CPU: 0 PID: 13554 at
kvm/arch/x86/kvm//../../../virt/kvm/kvm_main.c:4183 kvm_resume+0x3c/0x40 [kvm]
CPU: 0 PID: 13554 Comm: step_after_susp Tainted: G OE
5.1.0-rc4+ #1
RIP: 0010:kvm_resume+0x3c/0x40 [kvm]
Call Trace:
syscore_resume+0x63/0x2d0
From: Wanpeng Li
MSR IA32_MSIC_ENABLE bit 18, according to SDM:
| When this bit is set to 0, the MONITOR feature flag is not set
(CPUID.01H:ECX[bit 3] = 0).
| This indicates that MONITOR/MWAIT are not supported.
|
| Software attempts to execute MONITOR/MWAIT will cause #UD when this bit is 0.
From: Wanpeng Li
BUG: using __this_cpu_read() in preemptible [] code:
qemu-system-x86/4590
caller is nested_vmx_enter_non_root_mode+0xebd/0x1790 [kvm_intel]
CPU: 4 PID: 4590 Comm: qemu-system-x86 Tainted: G OE 5.1.0-rc4+
#1
Call Trace:
dump_stack+0x67/0x95
From: Wanpeng Li
Allow guest reads CORE cstate when exposing host CPU power management
capabilities
to the guest. PKG cstate is restricted to avoid a guest to get the whole
package
information in multi-tenant scenario.
Cc: Paolo Bonzini
Cc: Radim Krčmář
Cc: Sean Christopherson
Cc: Liran
On Fri, May 17, 2019 at 10:35:29AM +0200, Miguel Ojeda wrote:
> On Fri, May 17, 2019 at 9:38 AM Peter Zijlstra wrote:
> >
> > On Fri, May 17, 2019 at 07:09:31AM +0200, Greg KH wrote:
> > > On Thu, May 16, 2019 at 08:14:25PM -0700, Ivan Babrou wrote:
> > > > We are building the upstream kernel.
Hi Linus,
On Fri, May 17, 2019 at 12:06 AM Linus Torvalds
wrote:
> On Thu, May 16, 2019 at 1:34 PM Arnd Bergmann wrote:
> > I have reconfigured it locally now and pushed an identical tag with a
> > new signature. Can you see if that gives you the same warning if you
> > try to pull that?
>
>
On Fri, May 17, 2019 at 5:21 AM Xiaowei Bao wrote:
> -Original Message-
> From: Arnd Bergmann
> On Wed, May 15, 2019 at 9:36 AM Xiaowei Bao wrote:
> > Signed-off-by: Xiaowei Bao
> > ---
> > arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi | 52
> >
> > 1
Variables 'n' and 'err' are both used for less-than-zero error checking,
however both are declared as unsigned. Ensure ext4_map_blocks() and
add_system_zone() are able to have their return values propagated
correctly by redefining them both as signed integers.
../fs/ext4/block_validity.c:158:9:
On Fri, May 17, 2019 at 10:51 AM Greg KH wrote:
>
> On Fri, May 17, 2019 at 10:35:29AM +0200, Miguel Ojeda wrote:
> > On Fri, May 17, 2019 at 9:38 AM Peter Zijlstra wrote:
> > >
> > > Right; if there is anything you can reproduce on linus.git I'll happily
> > > have a look. If it doesn't
So far the KVM selftests are compiled without any compiler warnings
enabled. That's quite bad, since we miss a lot of possible bugs this
way. Let's enable at least "-Wall" and some other useful warning flags
now, and fix at least the trivial problems in the code (like unused
variables).
From: Jan Kara
> Sent: 17 May 2019 09:48
...
> So this last paragraph is not obvious to me as check_copy_size() does a lot
> of various checks in CONFIG_HARDENED_USERCOPY case. I agree that some of
> those checks don't make sense for PMEM pages but I'd rather handle that by
> refining
Hi, Stu:
On Tue, 2019-05-14 at 14:13 +0800, Stu Hsieh wrote:
> This patch add ISR for writing the data to buffer
>
> When mipicsi HW complete to write the data in buffer,
> the interrupt woulb be trigger.
> So, the ISR need to clear interrupt status for next interrupt.
>
> Signed-off-by: Stu
On Fri, May 17, 2019 at 10:26:55AM +0200, Peter Zijlstra wrote:
> On Fri, May 17, 2019 at 09:04:20AM +0100, Mark Rutland wrote:
>
> > Remember that this is in an undefined (trap) handler.
> >
> > If userspace _attempts_ to write to the registers, the CPU will trap to the
> > kernel. The comment
On Fri, May 17, 2019 at 10:41:28AM +0200, Ard Biesheuvel wrote:
> Returning an error here is not going to make much difference, given
> that the caller of efi_call_phys_prolog() does not bother to check it,
> and passes the result straight into efi_call_phys_epilog(), which
> happily attempts to
On Tue, May 14, 2019 at 9:42 PM Niklas Cassel wrote:
>
> On Fri, May 10, 2019 at 04:59:44PM +0530, Amit Kucheria wrote:
> > Add device bindings for cpuidle states for cpu devices.
> >
> > Signed-off-by: Amit Kucheria
> > ---
> > arch/arm64/boot/dts/qcom/msm8996.dtsi | 28
From: Rafael J. Wysocki
If a PCI driver leaves the device handled by it in D0 and calls
pci_save_state() on the device in its ->suspend() or ->suspend_late()
callback, it can expect the device to stay in D0 over the whole
s2idle cycle. However, that may not be the case if there is a
spurious
On Fri, May 17, 2019 at 04:15:39PM +0800, Kairui Song wrote:
> Hi, I think the actual problem is that bpf_get_stackid_tp (and maybe
> some other bfp functions) is now broken, or, strating an unwind
> directly inside a bpf program will end up strangely. It have following
> kernel message:
Urgh,
Commit-ID: 5a28fc94c9143db766d1ba5480cae82d856ad080
Gitweb: https://git.kernel.org/tip/5a28fc94c9143db766d1ba5480cae82d856ad080
Author: Dave Hansen
AuthorDate: Fri, 19 Apr 2019 12:47:47 -0700
Committer: Ingo Molnar
CommitDate: Thu, 9 May 2019 10:37:17 +0200
x86/mpx, mm/core: Fix
Commit-ID: 8ea58f1e8b11cca3087b294779bf5959bf89cc10
Gitweb: https://git.kernel.org/tip/8ea58f1e8b11cca3087b294779bf5959bf89cc10
Author: Nathan Chancellor
AuthorDate: Thu, 16 May 2019 12:49:42 -0500
Committer: Ingo Molnar
CommitDate: Fri, 17 May 2019 11:10:42 +0200
objtool: Allow AR to
Commit-ID: f8585539df0a1527c78b5d760665c89fe1c105a9
Gitweb: https://git.kernel.org/tip/f8585539df0a1527c78b5d760665c89fe1c105a9
Author: Ard Biesheuvel
AuthorDate: Thu, 16 May 2019 23:31:59 +0200
Committer: Ingo Molnar
CommitDate: Fri, 17 May 2019 11:07:42 +0200
fbdev/efifb: Ignore
On Fri, May 17, 2019 at 07:53:49AM +, Quentin Deslandes wrote:
> Returns error code from 'vnt_int_start_interrupt()' so the device's private
> buffers will be correctly freed and 'struct ieee80211_hw' start function
> will return an error code.
>
> Signed-off-by: Quentin Deslandes
> ---
>
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 foo {
int stuff;
struct boo entry[];
};
instance =
Am Donnerstag, 9. Mai 2019, 19:03:14 CEST schrieb Katsuhiro Suzuki:
> This patch adds PCIe, PCIe phy and pinctrl (for PERST#) nodes for
> RockPro64 board.
>
> Signed-off-by: Katsuhiro Suzuki
applied for 5.3 after a bit of alphabetical sorting
- num-lanes above pinctrl properties
- pcie-perst
On Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda wrote:
> On Fri, May 17, 2019 at 10:51 AM Greg KH wrote:
> >
> > On Fri, May 17, 2019 at 10:35:29AM +0200, Miguel Ojeda wrote:
> > > On Fri, May 17, 2019 at 9:38 AM Peter Zijlstra
> > > wrote:
> > > >
> > > > Right; if there is anything you
Hi Ted,
On Sun, May 12, 2019 at 12:07 AM Theodore Ts'o wrote:
> On Sat, May 11, 2019 at 02:43:16PM +0200, Richard Weinberger wrote:
> > [CC'in linux-ext4]
> >
> > On Sat, May 11, 2019 at 1:47 PM Arthur Marsh
> > wrote:
> > >
> > >
> > > The filesystem with the kernel source tree is the root
Starting with GCC 9, -Warray-bounds detects cases when memset is called
starting on a member of a struct but the size to be cleared ends up
writing over further members.
Such a call happens in the trace code to clear, at once, all members
after and including `seq` on struct trace_iterator:
On Fri, May 17, 2019 at 11:58 AM Bernd Petrovitsch
wrote:
>
> On 17/05/2019 10:16, Alexander Kapshuk wrote:
> [...]
> > The 'xargs' '-r' flag is a GNU extension.
> > If POSIX compliance is important here, the use of 'cat', 'xargs' and
> > 'basename' may be substituted with that of 'sed' to
Add "Jiangsu HopeRun Software Co., Ltd." to the list of devicetree
vendor prefixes as "hoperun".
Website: http://www.hoperun.com/en
Signed-off-by: Fabrizio Castro
Reviewed-by: Chris Paterson
---
v2->v3:
* Moved to vendor-prefixes.yaml
* Dropped Reviewed-by Simon as this is a completely new
Dear All,
this series aims at documenting the HiHope RZ/G2M platform from
HopeRun, and its corresponding expansion board.
V2->V3:
* Moved to vendor-prefixes.yaml
v1->v2:
* Applied Rob's comments
Thanks,
Fab
Fabrizio Castro (2):
dt-bindings: Add vendor prefix for HopeRun
dt-bindings: arm:
This patch adds board HiHope RZ/G2M (the main board, powered by
the R8A774A1) and board HiHope RZ/G2 EX (the expansion board
that sits on top of the HiHope RZ/G2M). Both boards are made
by Jiangsu HopeRun Software Co., Ltd. (a.k.a. HopeRun).
Useful links:
http://hihope.org/product/detail/rzg2
>-Original Message-
>From: Pavel Machek
>Sent: Friday, May 17, 2019 11:17 AM
>To: Greg Kroah-Hartman
>Cc: linux-kernel@vger.kernel.org; sta...@vger.kernel.org; Claudiu Manoil
>; David S. Miller ; Sasha
>Levin
>Subject: Re: [PATCH 4.19 042/113] ocelot: Dont sleep in atomic context
On Fri, May 17, 2019 at 11:23 AM Greg KH wrote:
>
> On Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda wrote:
>
> > a6e60d84989f ("include/linux/module.h: copy __init/__exit attrs to
> > init/cleanup_module")
>
> That patch I applied now.
Note that this one requires the second one
Hi Miquel,
> > +
> > +static void mxic_nand_select_chip(struct nand_chip *chip, int chipnr)
>
> _select_target() is preferred now
Do you mean I implement mxic_nand_select_target() to control #CS ?
If so, I need to call mxic_nand_select_target( ) to control #CS ON
and then #CS OFF in
On Fri, May 17, 2019 at 11:04:45AM +0200, Thomas Huth wrote:
> So far the KVM selftests are compiled without any compiler warnings
> enabled. That's quite bad, since we miss a lot of possible bugs this
> way. Let's enable at least "-Wall" and some other useful warning flags
> now, and fix at least
Hi!
> >On Wed 2019-05-15 12:55:33, Greg Kroah-Hartman wrote:
> >> [ Upstream commit a8fd48b50deaa20808bbf0f6685f6f1acba6a64c ]
> >>
> >> Preemption disabled at:
> >> [] dev_set_rx_mode+0x1c/0x38
> >> Call trace:
> >> [] dump_backtrace+0x0/0x3d0
> >> [] show_stack+0x14/0x20
> >> []
On 16/05/2019 22:38, Doug Anderson wrote:
> Hi,
>
> From: kernelci.org bot
> Date: Tue, May 14, 2019 at 9:06 AM
> To: , ,
> , ,
> , ,
> , Elaine Zhang, Eduardo Valentin, Daniel
> Lezcano
> Cc: Heiko Stuebner, ,
> , ,
> Zhang Rui,
>
>> * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Peter Xu writes:
> On Fri, May 17, 2019 at 11:04:45AM +0200, Thomas Huth wrote:
>> So far the KVM selftests are compiled without any compiler warnings
>> enabled. That's quite bad, since we miss a lot of possible bugs this
>> way. Let's enable at least "-Wall" and some other useful warning flags
On 17.05.2019 07:21, Stephen Rothwell wrote:
> Hi all,
>
> Please do not add any v5.3 material to your linux-next included
> trees/branches until after v5.2-rc1 has been released.
>
> Changes since 20190516:
>
> The kvm tree gained conflicts against Linus' tree.
>
> Non-merge commits (relative
On Fri, 2019-05-17 at 10:06 +0200, Pavel Machek wrote:
> Hi!
>
> > commit 25dc1d6cc3082aab293e5dad47623b550f7ddd2a upstream.
> >
> > Even if this file was not in an uapi directory, it was exported
> > because
> > it was listed in the Kbuild file.
> >
>
> While good idea for mainline, I don't
On Fri, May 17, 2019 at 11:27:41AM +0200, Miguel Ojeda wrote:
> On Fri, May 17, 2019 at 11:23 AM Greg KH wrote:
> >
> > On Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda wrote:
> >
> > > a6e60d84989f ("include/linux/module.h: copy __init/__exit attrs to
> > > init/cleanup_module")
> >
> >
On 17.05.2019 12:41, Kirill Tkhai wrote:
> On 17.05.2019 07:21, Stephen Rothwell wrote:
>> Hi all,
>>
>> Please do not add any v5.3 material to your linux-next included
>> trees/branches until after v5.2-rc1 has been released.
>>
>> Changes since 20190516:
>>
>> The kvm tree gained conflicts
On Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda wrote:
> On Fri, May 17, 2019 at 10:51 AM Greg KH wrote:
> >
> > On Fri, May 17, 2019 at 10:35:29AM +0200, Miguel Ojeda wrote:
> > > On Fri, May 17, 2019 at 9:38 AM Peter Zijlstra
> > > wrote:
> > > >
> > > > Right; if there is anything you
Hi all,
On Fri, 17 May 2019 12:43:08 +0300 Kirill Tkhai wrote:
>
> On 17.05.2019 12:41, Kirill Tkhai wrote:
> > On 17.05.2019 07:21, Stephen Rothwell wrote:
> >> Hi all,
> >>
> >> Please do not add any v5.3 material to your linux-next included
> >> trees/branches until after v5.2-rc1 has been
On 2019-05-13 at 09:31 +, Lucas Stach wrote:
> PS:
> > Please get sdma firmware from below linux-firmware and copy it to
> > your
> > local rootfs /lib/firmware/imx/sdma.
> > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fg
> >
From: Oleksandr Tyshchenko
If PSCI is available then most likely we are running on PSCI-enabled
U-Boot which, we assume, has already taken care of resetting CNTVOFF
and updating counter module before switching to non-secure mode
and we don't need to.
As the psci_smp_available() helper always
On 17/05/2019 10:16, Alexander Kapshuk wrote:
[...]
> The 'xargs' '-r' flag is a GNU extension.
> If POSIX compliance is important here, the use of 'cat', 'xargs' and
> 'basename' may be substituted with that of 'sed' to initialise
> same_name_modules:
> sed 's!.*/!!' modules.order modules.builtin
On 17/05/2019 11.41, Vitaly Kuznetsov wrote:
> Peter Xu writes:
>
>> On Fri, May 17, 2019 at 11:04:45AM +0200, Thomas Huth wrote:
>>> So far the KVM selftests are compiled without any compiler warnings
>>> enabled. That's quite bad, since we miss a lot of possible bugs this
>>> way. Let's enable
On Fri, Mar 29, 2019 at 10:55 AM syzbot
wrote:
>
> Hello,
>
> syzbot has tested the proposed patch and the reproducer did not trigger
> crash:
>
> Reported-and-tested-by:
> syzbot+f9f3f388440283da2...@syzkaller.appspotmail.com
>
> Tested on:
>
> commit: 8c2ffd91 Linux 5.1-rc2
> git tree:
On Thu, May 16, 2019 at 01:59:43PM -0700, Luck, Tony wrote:
> I think the intent of the original patch was to find out
> which bits are "implemented in hardware". I.e. throw all
> 1's at the register and see if any of them stick.
And, in addition, check ->init before showing/setting a bank:
---
This bug is marked as fixed by commit:
vfs: namespace: error pointer dereference in do_remount()
But I can't find it in any tested tree for more than 90 days.
Is it a correct commit? Please update it by replying:
#syz fix: exact-commit-title
Until then the bug is still considered open and
new
On Fri, 17 May 2019, Philippe Mazenauer wrote:
> Variables 'n' and 'err' are both used for less-than-zero error checking,
> however both are declared as unsigned. Ensure ext4_map_blocks() and
> add_system_zone() are able to have their return values propagated
> correctly by redefining them both
Hi,
I have 2 questions re drivers/android/binder.c stress testing.
1. Are there any docs on the kernel interface? Or some examples on how
to use it and reference syscall sequences to make it do something
meaningful?
I hopefully figured out struct layouts and offsets of objects thing,
but I still
Am Freitag, 17. Mai 2019, 06:06:24 CEST schrieb Manivannan Sadhasivam:
> Enable SPI0 and SPI4 exposed on the Low and High speed expansion
> connectors of Rock960.
>
> Signed-off-by: Manivannan Sadhasivam
applied both patches for 5.3
Thanks
Heiko
The patch
ASoC: tlv320aic3x: Add support for high power analog output
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
Hi all,
I would like to ask a question regarding cpu frequency scaling / cpu
performance using intel_pstate with activated HWP.
I think the special CPU doesn't matter. I checked it with i7-8550U and
i7-8565U. Currently I am not sure if this is a
bug. Thats why I am asking...
Using intel_pstate
The presence of struct page does not guarantee linear mapping for the pfn
physical range. Device private memory which is non-coherent is excluded
from linear mapping during devm_memremap_pages() though they will still
have struct page coverage. Just check for device private memory before
giving
Variable 'rdp' is set but not used in synchronize_rcu_expidited(). The
macro per_cpu_ptr() used to set the value of 'rdp' has no side effect.
../kernel/rcu/tree_exp.h:768:19: warning: variable ‘rdp’ set but not used
[-Wunused-but-set-variable]
struct rcu_data *rdp;
^~~
Am Donnerstag, 16. Mai 2019, 18:29:40 CEST schrieb Matthias Kaehlcke:
> This value matches what is used by the downstream Chrome OS 3.14
> kernel, the 'official' kernel for veyron devices. Keep the temperature
> for 'speedy' at 90°C, as in the downstream kernel.
>
> Increase the temperature for a
The Kernel has nice hexdump facilities, use them rather a homebrew
hexdump function.
Signed-off-by: Sascha Hauer
---
fs/ecryptfs/debug.c | 22 +++---
1 file changed, 3 insertions(+), 19 deletions(-)
diff --git a/fs/ecryptfs/debug.c b/fs/ecryptfs/debug.c
index
Variable 'entropy' was wrongly documented as 'seed', changed comment to
reflect actual variable name.
../lib/random32.c:179: warning: Function parameter or member 'entropy' not
described in 'prandom_seed'
../lib/random32.c:179: warning: Excess function parameter 'seed' description in
On Fri, 17 May 2019 at 10:59, Arnd Bergmann wrote:
>
> On Fri, May 17, 2019 at 5:21 AM Xiaowei Bao wrote:
> > -Original Message-
> > From: Arnd Bergmann
> > On Wed, May 15, 2019 at 9:36 AM Xiaowei Bao wrote:
> > > Signed-off-by: Xiaowei Bao
> > > ---
> > >
On Fri, May 17, 2019 at 4:27 AM Peng Fan wrote:
>
> Fixes: ba5625c3e27 ("clk: imx: Add clock driver support for imx8mm")
> To Frac pll, the gate shift is 13, however to Int PLL the gate shift
> is 11.
>
> Cc:
The Fixes tag should go here instead.
> Signed-off-by: Peng Fan
> Reviewed-by: Fabio
On Fri, 17 May 2019, Philippe Mazenauer wrote:
> Variable 'rdp' is set but not used in synchronize_rcu_expidited(). The
> macro per_cpu_ptr() used to set the value of 'rdp' has no side effect.
>
> ../kernel/rcu/tree_exp.h:768:19: warning: variable ‘rdp’ set but not used
>
Thomas Huth writes:
>
> x86_64/vmx_set_nested_state_test.c: In function
> ‘set_revision_id_for_vmcs12’:
> x86_64/vmx_set_nested_state_test.c:78:2: warning: dereferencing
> type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing]
> *(u32 *)(state->data) = vmcs12_revision;
>
>
From: Rafael J. Wysocki
Add kerneldoc comments to pm_suspend_via_firmware(),
pm_resume_via_firmware() and pm_suspend_via_s2idle() to explain
what they do.
Signed-off-by: Rafael J. Wysocki
---
include/linux/suspend.h | 20
kernel/power/suspend.c |6 ++
2 files
Hi all,
In commit
4fa0b1f971fc ("crypto: caam - fix typo in i.MX6 devices list for errata")
Fixes tag
Fixes: 33d69455e402 ("crypto: caam - limit AXI pipeline to a depth of
has these problem(s):
- Subject has leading but no trailing parentheses
- Subject has leading but no trailing
Hi all,
In commit
ad6eecbfc01c ("ASoC: cs42xx8: Add regcache mask dirty")
Fixes tag
Fixes: 0c516b4ff85c ("ASoC: cs42xx8: Add codec driver
has these problem(s):
- Subject has leading but no trailing parentheses
- Subject has leading but no trailing quotes
Please do not split Fixes
Estimado usuario de correo electrónico,
Aviso de seguridad:
Este mensaje es de nuestro centro de mensajería Web Admin a todos nuestros
propietarios de cuentas de correo electrónico. Estamos eliminando el acceso a
todos nuestros clientes de correo web. Su cuenta de correo electrónico se
srikanth writes:
> Hello,
>
> On power9 host, performing memory hotunplug from ppc64le guest results
> in kernel oops.
Thanks for the report.
Did this used to work in the past? If so what is the last version that
worked?
> Kernel used : https://github.com/torvalds/linux/tree/v5.1 built using
Estimado usuario de correo electrónico,
Aviso de seguridad:
Este mensaje es de nuestro centro de mensajería Web Admin a todos nuestros
propietarios de cuentas de correo electrónico. Estamos eliminando el acceso a
todos nuestros clientes de correo web. Su cuenta de correo electrónico se
On Thu, 16 May 2019 18:30:34 -0500
Parav Pandit wrote:
> In following sequences, child devices created while removing mdev parent
> device can be left out, or it may lead to race of removing half
> initialized child mdev devices.
>
> issue-1:
>
>cpu-0
On 4/26/19 4:59 PM, Grzegorz Halat wrote:
> After memory allocation failure vc_allocate() doesn't clean up data
> which has been initialized in visual_init(). In case of fbcon this
> leads to divide-by-0 in fbcon_init() on next open of the same tty.
>
> memory allocation in vc_allocate() may
On 5/16/2019 5:23 PM, Krishna Yarlagadda wrote:
Tegra194 has PCIE L5 rst and clkreq pins which need to be controlled
dynamically at runtime. This driver supports change pinmux for these
pins. Pinmux for rest of the pins is set statically by bootloader and
will not be changed by this driver
On Wed, 15 May 2019 10:54:42 +
Sasha Levin wrote:
> Hi,
>
Hi,
> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: eac1e731b59e powerpc/xive: guest exploitation of the XIVE
> interrupt controller.
>
> The bot has tested
On 5/16/2019 5:23 PM, Krishna Yarlagadda wrote:
Add binding doc for Tegra 194 pinctrl driver
Signed-off-by: Krishna Yarlagadda
---
Changes in V3:
remove optional fields not supported by pins published here
.../bindings/pinctrl/nvidia,tegra194-pinmux.txt| 107 +
1
On Fri, May 17, 2019 at 10:26:28AM +0100, Fabrizio Castro wrote:
> Add "Jiangsu HopeRun Software Co., Ltd." to the list of devicetree
> vendor prefixes as "hoperun".
>
> Website: http://www.hoperun.com/en
>
> Signed-off-by: Fabrizio Castro
> Reviewed-by: Chris Paterson
Reviewed-by: Simon
We have a single node system with node 0 disabled:
Scanning NUMA topology in Northbridge 24
Number of physical nodes 2
Skipping disabled node 0
Node 1 MemBase Limit fbff
NODE_DATA(1) allocated [mem 0xfbfda000-0xfbfe]
This causes crashes in memcg when
On 16.05.2019 20:59, Roman Gushchin wrote:
On Wed, May 15, 2019 at 02:49:48PM +0300, Konstantin Khlebnikov wrote:
Some kernel memory allocations are not accounted anywhere.
This adds easy-read counter for them by subtracting all tracked kinds.
Signed-off-by: Konstantin Khlebnikov
We have
On 17/05/19 08:22, Nathan Chancellor wrote:
> On Fri, May 17, 2019 at 05:59:36AM +0200, Paolo Bonzini wrote:
>> Linus,
>>
>> The following changes since commit 7a223e06b1a411cef6c4cd7a9b9a33c8d225b10e:
>>
>> KVM: x86: avoid misreporting level-triggered irqs as edge-triggered in
>> tracing
Estimado usuario de correo electrónico,
Aviso de seguridad:
Este mensaje es de nuestro centro de mensajería Web Admin a todos nuestros
propietarios de cuentas de correo electrónico. Estamos eliminando el acceso a
todos nuestros clientes de correo web. Su cuenta de correo electrónico se
On Fri, May 17, 2019 at 11:42:17AM +0200, Greg KH wrote:
> On Fri, May 17, 2019 at 11:27:41AM +0200, Miguel Ojeda wrote:
> > On Fri, May 17, 2019 at 11:23 AM Greg KH wrote:
> > >
> > > On Fri, May 17, 2019 at 11:01:45AM +0200, Miguel Ojeda wrote:
> > >
> > > > a6e60d84989f
We must use {READ,WRITE}_ONCE() on rb->user_page data such that
concurrent usage will see whole values. A few key sites were missing
this.
Fixes:7b732a750477 ("perf_counter: new output ABI - part 1")
Suggested-by: Yabin Cui
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/events/ring_buffer.c
While the IRQ/NMI will nest, the nest-count will be invariant over the
actual exception, since it will decrement equal to increment.
This means we can -- carefully -- use a regular variable since the
typical LOAD-STORE race doesn't exist (similar to preempt_count).
This optimizes the ring-buffer
In perf_output_put_handle(), an IRQ/NMI can happen in below location and
write records to the same ring buffer:
...
local_dec_and_test(>nest)
... <-- an IRQ/NMI can happen here
rb->user_page->data_head = head;
...
In this case, a
This is basically a split of Yabin's last patch.
Similar to how decrementing rb->next too early can cause data_head to
(temporarily) be observed to go backward, so too can this happen when
we increment too late.
This barrier() ensures the rb->head load happens after the increment,
both the one in the 'goto again' path, as the one from
On Fri, May 17, 2019 at 4:12 AM Richard Weinberger
wrote:
>
> On Thu, May 16, 2019 at 6:42 PM Kamal Dasu wrote:
> >
> > If mtd_oops is in progress, switch to polling during NAND command
> > completion instead of relying on DMA/interrupts so that the mtd_oops
> > buffer can be completely written
On Fri, May 17, 2019 at 11:51:11AM +0100, Lee Jones wrote:
> On Fri, 17 May 2019, Philippe Mazenauer wrote:
>
> > Variable 'rdp' is set but not used in synchronize_rcu_expidited(). The
> > macro per_cpu_ptr() used to set the value of 'rdp' has no side effect.
> >
> >
Commit e45adf665a53 ("KVM: Introduce a new guest mapping API", 2019-01-31)
introduced a build failure on aarch64 defconfig:
$ make -j$(nproc) ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- O=out defconfig \
Image.gz
...
../arch/arm64/kvm/../../../virt/kvm/kvm_main.c:
In function
On Fri, May 17, 2019 at 4:42 AM Jiri Slaby wrote:
>
> We have a single node system with node 0 disabled:
> Scanning NUMA topology in Northbridge 24
> Number of physical nodes 2
> Skipping disabled node 0
> Node 1 MemBase Limit fbff
> NODE_DATA(1) allocated
3000+ tests for the Linux
and can be downloaded at:
https://github.com/linux-test-project/ltp/releases/tag/20190517
The project pages as well as GIT repository are hosted on GitHub:
https://github.com/linux-test-project/ltp
http://linux-test-project.github.io/
If you ever wondered how to write
101 - 200 of 617 matches
Mail list logo
