erf-urgent-for-mingo-5.1-20190416' of
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/urgent
> (2019-04-16 17:24:14 +0200)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
> tags/perf-urgent-f
On Fri, Apr 19, 2019 at 01:21:45PM -0400, Alan Stern wrote:
> The description of smp_mb__before_atomic() and smp_mb__after_atomic()
> in Documentation/atomic_t.txt is slightly terse and misleading. It
> does not clearly state that these barriers only affect the ordering of
> other instructions
On Fri, Apr 19, 2019 at 10:34:06AM -0400, Alan Stern wrote:
> On Fri, 19 Apr 2019, Paul E. McKenney wrote:
>
> > On Fri, Apr 19, 2019 at 02:53:02AM +0200, Andrea Parri wrote:
> > > > Are you saying that on x86, atomic_inc() acts as a full memory barrier
> > > > but not as a compiler barrier, and
On Fri, Apr 19, 2019 at 02:54:54PM +0200, Vlastimil Babka wrote:
> On 4/19/19 10:51 AM, Mel Gorman wrote:
> > During the development of commit 5e1f0f098b46 ("mm, compaction: capture
> > a page under direct compaction"), a paranoid check was added to ensure
> > that if a captured page was available
The presence detect state (PDS) is normally a logical or of in-band
and out-of-band presence. In PCIe 4.0, there is the option to disable
in-band presence so that the PDS bit always reflects the state of the
out-of-band presence.
The recommendation of the PCIe spec is to disable in-band presence
On Thu, Apr 18, 2019 at 04:59:07PM -0400, Jerome Glisse wrote:
> On Wed, Mar 20, 2019 at 10:06:31AM +0800, Peter Xu wrote:
> > For either swap and page migration, we all use the bit 2 of the entry to
> > identify whether this entry is uffd write-protected. It plays a similar
> > role as the
According to PCIe 3.0, the presence detect state is a logical OR of
in-band and out-of-band presence. With this, we'd expect the presence
state to always be asserted when the link comes up.
Not all hardware follows this, and it is possible for the presence to
come up after the link. In this case,
-Original Message-
From: Corey Minyard On Behalf Of Corey Minyard
Sent: Tuesday, April 16, 2019 12:16 PM
To: Asmaa Mnebhi
Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org
Subject: Re: [PATCH v1 1/1] Add support for IPMB driver
On Fri, Apr 12, 2019 at 05:59:16PM -0400,
The core will print out details now.
Reviewed-by: Guenter Roeck
Signed-off-by: Wolfram Sang
---
drivers/watchdog/hpwdt.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/watchdog/hpwdt.c b/drivers/watchdog/hpwdt.c
index ef30c7e9728d..db1bf6f546ae 100644
---
- On Apr 19, 2019, at 10:17 AM, shuah sh...@kernel.org wrote:
> On 4/19/19 7:48 AM, Mathieu Desnoyers wrote:
>> - On Apr 19, 2019, at 9:42 AM, Mathieu Desnoyers
>> mathieu.desnoy...@efficios.com wrote:
>>
>>> - On Apr 19, 2019, at 8:55 AM, Mathieu Desnoyers
>>>
This prepares to move CONFIG_OPTIMIZE_INLINING from x86 to a common
place. We need to eliminate potential issues beforehand.
If it is enabled for powerpc, the following modpost warnings are
reported:
WARNING: vmlinux.o(.text.unlikely+0x20): Section mismatch in reference from the
function
Just returned to work today dealing with "life" issues, apologies for the
delays in replying. :)
On Wed, Apr 17, 2019 at 03:09:41PM +0200, Oleg Nesterov wrote:
> On 04/16, Joel Fernandes wrote:
> >
> > On Tue, Apr 16, 2019 at 02:04:31PM +0200, Oleg Nesterov wrote:
> > >
> > > Could you explain
On Fri, Apr 19, 2019 at 09:02:11AM +0200, Peter Zijlstra wrote:
> On Thu, Apr 18, 2019 at 05:42:55PM +0200, Thomas Gleixner wrote:
> > On Thu, 18 Apr 2019, Josh Poimboeuf wrote:
>
> > > Another idea I had (but never got a chance to work on) was to extend the
> > > x86 unwind interface to all
If vfio_pci_register_dev_region() fails then we should rollback
previous changes, ie. unmap the ATSD registers.
Signed-off-by: Greg Kurz
---
drivers/vfio/pci/vfio_pci_nvlink2.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/vfio/pci/vfio_pci_nvlink2.c
According to the old PCIe spec, PDS would always have to come up with
or before DLLLA. For various reasons, not all OEMs followed this
requirement. As a result, in PCIe 4.0(*), there is a new way to disable
in-band presence reporting, such that PDS always reports the status of
the out-of-band
The patch
regulator: ltc3589: Switch to SPDX identifier
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
On 2019/4/19 21:24, Paul Moore wrote:
On Thu, Apr 18, 2019 at 10:42 PM Yang Yingliang
wrote:
On 2019/4/19 10:04, Paul Moore wrote:
On Wed, Apr 17, 2019 at 10:50 PM Yang Yingliang
wrote:
On 2019/4/18 8:24, Casey Schaufler wrote:
On 4/17/2019 4:39 PM, Paul Moore wrote:
Since it looks
CMD of Source/Destination descriptior format should be lower of
struct fsl_qdma_engine number data address.
Signed-off-by: Peng Ma
---
drivers/dma/fsl-qdma.c | 29 ++---
1 files changed, 18 insertions(+), 11 deletions(-)
diff --git a/drivers/dma/fsl-qdma.c
The patch
regulator: ltc3589: Convert to use simplified DT parsing
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in
The patch
ASoC: Intel: Haswell: Remove set but not used variable 'stage_type'
has been applied to the asoc tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in
During the development of commit 5e1f0f098b46 ("mm, compaction: capture
a page under direct compaction"), a paranoid check was added to ensure
that if a captured page was available after compaction that it was
consistent with the final state of compaction. The intent was to catch
serious
The patch
regulator: fan53555: Clean up unneeded fields from struct
fan53555_device_info
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2
All being well this means that it will be integrated into the linux-next
tree
On Thu, Apr 18, 2019 at 09:18:15AM -0700, Yang Shi wrote:
>
>
> On 4/17/19 11:32 PM, Michal Hocko wrote:
> > On Wed 17-04-19 21:15:41, Yang Shi wrote:
> > > Hi folks,
> > >
> > >
> > > I noticed that there might be new THP allocation in NUMA fault migration
> > > path
The description of smp_mb__before_atomic() and smp_mb__after_atomic()
in Documentation/atomic_t.txt is slightly terse and misleading. It
does not clearly state that these barriers only affect the ordering of
other instructions with respect to the atomic operation.
This improves the text to make
On Fri, Apr 19, 2019 at 06:54:32PM +0800, Baolin Wang wrote:
> On Spreadtrum platform, the audio subsystem will use the multi-channel
> data transfer controller to transfer sound stream between audio subsystem
> and other AP/CP subsystem.
>
> It can support 10 DAC channel and 10 ADC channel, and
This prepares to move CONFIG_OPTIMIZE_INLINING from x86 to a common
place. We need to eliminate potential issues beforehand.
If it is enabled for arm, Clang build results in the following modpost
warning:
WARNING: vmlinux.o(.text+0x1124): Section mismatch in reference from the
function
This prepares to move CONFIG_OPTIMIZE_INLINING from x86 to a common
place. We need to eliminate potential issues beforehand.
If it is enabled for s390, the following error is reported:
In file included from arch/s390/crypto/des_s390.c:19:
./arch/s390/include/asm/cpacf.h: In function
On Mon, Apr 15, 2019 at 02:30:30PM -0700, Sowjanya Komatineni wrote:
> This patch exports spi_set_cs of the spi core to allow SPI masters
> to use when gpio based chip select is needed.
This isn't really what I meant when I said it'd be good to use the core
GPIO code - this function doesn't do a
The WMI exposes two methods for controlling RGB keyboard backlight, which
allows controlling:
* RGB components in range 00 - ff,
* Switch between 4 effects,
* Switch between 3 effect speed modes,
* Separately enable the backlight on boot, in the awake state (after driver
load), in sleep mode,
Hi,
This patch can be dropped, as it needs more work.
In fact, the interrupts seems to be wrong. The interrupts suggested by
Anand Moon gave the same following results.
export CCI_DEV=CCI_400
export OMP_NUM_THREADS=2
sudo --preserve-env ./perf stat -a \
-e
Hi Sergey,
> -Original Message-
> From: Sergey Senozhatsky [mailto:sergey.senozhatsky.w...@gmail.com]
> Sent: Friday, April 19, 2019 5:34 PM
> To: Yamada, Masahiro/山田 真弘
> Cc: linux-kernel@vger.kernel.org; Sergey Senozhatsky
>
> Subject: [next] kbuild: use $(srctree) instead of
On Fri, Apr 19, 2019 at 10:23:53AM +, S.j. Wang wrote:
> @@ -289,6 +318,12 @@ static int fsl_asrc_config_pair(struct fsl_asrc_pair
> *pair)
> return -EINVAL;
> }
>
> + ret = fsl_asrc_sel_proc(inrate, outrate, _proc, _proc);
Since the function always return 0, I am
Instead of adding CFLAGS_.o to every file, let's use
ccflags-y, which is effective for all C files in the directory.
No behavior change.
Signed-off-by: Masahiro Yamada
---
drivers/crypto/ux500/cryp/Makefile | 6 +-
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git
From: Arnd Bergmann
When function tracing for IPIs is enabled, we get a warning for an
overflow of the ipi_types array with the IPI_CPU_BACKTRACE type
as triggered by raise_nmi():
arch/arm/kernel/smp.c: In function 'raise_nmi':
arch/arm/kernel/smp.c:489:2: error: array subscript is above array
Hi Chanwoo,
please ignore this patch there is a comment below.
It wrongly sets the default value.
On 4/18/19 3:38 PM, Lukasz Luba wrote:
> This patch adds posibility to choose what type of data should be counted
> by the PPMU counter. Now the type comes from DT where the event has been
>
On Fri, 2019-04-19 at 12:28 +0900, Masahiro Yamada wrote:
> Hi Joe,
>
> Can you detect redundant Cc: by checkpatch?
>
> Please see below in details.
> Thanks.
Yes, but I'm not sure why it's useful or necessary.
git send-email using some scripts elides duplicate email addresses
---
On Mon, Apr 15, 2019 at 05:23:53PM +0800, Mason Yang wrote:
> Patch Macronix MX25F0A SPI controller driver according to it's MFD driver.
It'd be much better to describe what the above actually means - what
changes have been made in the introduction of the MFD driver? It does
feel like there's
This prepares to move CONFIG_OPTIMIZE_INLINING from x86 to a common
place. We need to eliminate potential issues beforehand.
If it is enabled for powerpc, the following error is reported:
arch/powerpc/mm/tlb-radix.c: In function '__radix__flush_tlb_range_psize':
Sometimes the exec_op parser does not choose the optimal pattern if
multiple patterns with optional elements are available. Since the stack
automatically splits operations in multiple exec_op calls, a non-optimal
pattern gets broken up into multiple calls. E.g. an OOB read using the
vf610 driver:
- Adds rotation property to plane.
- Komeda display rotation support diverges from the specific formats,
so need to check the user required rotation type with the format caps
and reject the commit if it can not be supported.
- In the layer validate flow, sets the rotation value to the layer
state.
Hi,
This serie aims at adding the support for rotation on Komeda driver.
This patch series depends on:
- https://patchwork.freedesktop.org/series/54449/
- https://patchwork.freedesktop.org/series/54450/
- https://patchwork.freedesktop.org/series/58710/
-
CFLAGS_tracepoint.o specifies CFLAGS for compiling tracepoint.c but
it does not exist under drivers/net/ethernet/mellanox/mlx5/core/.
CFLAGS_tracepoint.o is unused.
Signed-off-by: Masahiro Yamada
---
drivers/net/ethernet/mellanox/mlx5/core/Makefile | 2 --
1 file changed, 2 deletions(-)
diff
Komeda series hardware doesn't support Rot90 for AFBC wide block. So
add limitation check to reject it if such configuration has been posted.
Signed-off-by: Lowry Li (Arm Technology China)
---
drivers/gpu/drm/arm/display/komeda/d71/d71_dev.c | 15 +++
On Fri, Apr 19, 2019 at 09:46:39PM +0800, YueHaibing wrote:
> On 2019/4/19 21:31, Bjorn Helgaas wrote:
> > On Fri, Apr 19, 2019 at 10:58:55AM +0800, Yue Haibing wrote:
> >> From: YueHaibing
> >>
> >> During randconfig builds, I occasionally run into an invalid configuration
> >>
> >>
On Tue, Apr 16, 2019 at 10:41:09PM +0800, Yue Haibing wrote:
> From: YueHaibing
>
> Fix sparse warnings:
>
> drivers/regulator/stm32-pwr.c:35:5: warning:
> symbol 'ready_mask_table' was not declared. Should it be static?
> drivers/regulator/stm32-pwr.c:47:5: warning:
> symbol
On Mon, Apr 15, 2019 at 02:30:28PM -0700, Sowjanya Komatineni wrote:
> Some SPI slaves expect bytes to be in least significant first order
> and some expects most significant first oder.
>
> This patch adds support for requesting SPI master controllers for
> least significant first order using
The patch
regulator: fan53555: Switch to SPDX identifier
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24
Hi Marcel, Stefan,
Could you please look into this and ack if there are no any objections
from your end?
Thanks!
On Thu, Apr 4, 2019 at 12:19 PM Igor Opaniuk wrote:
>
> Introduce DTS for Colibri iMX6DL with proper configuration for VGEN3,
> which allows that rail to be automatically switched
Performing i2c write operation while SDA or SCL line is grounded,
TXRDY interrupt spam hangs the processor, not allowing to boot.
Signed-off-by: raag
---
drivers/i2c/busses/i2c-at91.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-at91.c
This changeset adds a driver for the SPI keyboard and trackpad on recent
MacBook's and MacBook Pro's. The driver has seen a fair amount of use
over the last 2 years (basically anybody running linux on these
machines), with only relatively small changes in the last year or so.
For those interested,
The patch
regulator: ltc3589: Get rid of struct ltc3589_regulator
has been applied to the regulator tree at
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-5.2
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the
Hi,
this is the third version of the patch series.
Changelog:
v3:
* Use devm_* function in patch 01
* Detect DSTS/DCTS using _UID in patch 04
* Detect event queue by _UID as well in patch 05
* Rename poll function in patch 05
* Fix terminology in patches 09 and 10
* Correct commit
We have a default timeout value in the driver which we will fall back to
if the user supplied values are out of bounce.
Reviewed-by: Guenter Roeck
Signed-off-by: Wolfram Sang
---
drivers/watchdog/cadence_wdt.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git
Dear,
I am Mr.Marck Csady a solicitor at law, i need your assistance to
represent my late client fund valued at $2.5 million dollars that his
bank wants to comfiscate, You bear the same last name with my late
client and he is also a national of your country.
Please if you are interested to
This prepares to move CONFIG_OPTIMIZE_INLINING from x86 to a common
place. We need to eliminate potential issues beforehand.
If it is enabled for powerpc, the following errors are reported:
arch/powerpc/mm/tlb-radix.c: In function '__tlbie_lpid':
arch/powerpc/mm/tlb-radix.c:148:2: warning: asm
On Fri, Apr 19, 2019 at 06:26:00PM +0200, Oleg Nesterov wrote:
> On 04/19, Roman Gushchin wrote:
> >
> > > Once again, suppose we race with CGRP_FREEZE. If JOBCTL_TRAP_FREEZE is
> > > already
> > > set then signal_pending() must be already T and we do not need
> > > recalc_sigpending?
> > > If
On Thu, Apr 18, 2019 at 05:07:12PM +0200, Rafael J. Wysocki wrote:
> On Thu, Apr 18, 2019 at 5:02 PM Keith Busch wrote:
> >
> > On Wed, Apr 17, 2019 at 11:13:10AM -0700, Alison Schofield wrote:
> > > ACPI 6.3 changed the subtable "Memory Subsystem Address Range Structure"
> > > to "Memory
On Fri, Apr 19, 2019 at 02:29:11AM +0200, Borislav Petkov wrote:
> On Thu, Apr 18, 2019 at 05:07:45PM -0700, Luck, Tony wrote:
> > On Fri, Apr 19, 2019 at 01:29:10AM +0200, Borislav Petkov wrote:
> > > Which reminds me, Tony, I think all those debugging files "pfn"
> > > and "array" and the one
On Thu, 18 Apr 2019 at 23:34, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.113 release.
> There are 92 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
enum sdw_command_response
cdns_xfer_msg_defer(struct sdw_bus *bus,
- struct sdw_msg *msg, struct sdw_defer *defer)
+ struct sdw_msg *msg, struct sdw_defer *defer)
this one too..
static int cdns_port_params(struct sdw_bus *bus,
- struct sdw_port_params
On Fri, Apr 19, 2019 at 08:00:17PM +0200, Peter Zijlstra wrote:
> On Fri, Apr 19, 2019 at 01:21:45PM -0400, Alan Stern wrote:
> > Index: usb-devel/Documentation/atomic_t.txt
> > ===
> > --- usb-devel.orig/Documentation/atomic_t.txt
>
syzbot has found a reproducer for the following crash on:
HEAD commit:6d906f99 Merge tag 'arm64-fixes' of git://git.kernel.org/p..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=10917b8f20
kernel config:
On Thu, 18 Apr 2019 at 23:38, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.170 release.
> There are 50 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
On Fri, Apr 19, 2019 at 05:30:48PM +0200, Oleg Nesterov wrote:
> On 04/19, Christian Brauner wrote:
> >
> > +int main(int argc, char *argv[])
> > +{
> > + int ret = EXIT_FAILURE;
> > + char buf[4096] = { 0 };
> > + pid_t pid;
> > + int pidfd, procfd, statusfd;
>
> I think you need to
into perf/urgent
(2019-04-16 17:24:14 +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.1-20190419
for you to fetch changes up to 2db7b1e0bd49d2b0e7d16949e167b1cfaf5c07cf:
perf bpf: Return NULL when RB tree
> *
> eInfochips Business Disclaimer: This e-mail message and all
> attachments transmitted with it are intended solely for the use of the
>
On 4/19/19 4:13 AM, Mel Gorman wrote:
On Thu, Apr 18, 2019 at 09:18:15AM -0700, Yang Shi wrote:
On 4/17/19 11:32 PM, Michal Hocko wrote:
On Wed 17-04-19 21:15:41, Yang Shi wrote:
Hi folks,
I noticed that there might be new THP allocation in NUMA fault migration
path
From: Jiri Olsa
Current perf_evlist__poll_thread() code could finish without draining
the data. Adding the logic that makes sure we won't finish before the
drain.
Signed-off-by: Jiri Olsa
Cc: Adrian Hunter
Cc: Alexander Shishkin
Cc: Alexei Starovoitov
Cc: Andi Kleen
Cc: Daniel Borkmann
On Fri, Apr 19, 2019 at 10:58:55AM +0800, Yue Haibing wrote:
> From: YueHaibing
>
> During randconfig builds, I occasionally run into an invalid configuration
>
> drivers/pci/controller/dwc/pci-keystone.o: In function `ks_pcie_link_up':
> pci-keystone.c:(.text+0x90): undefined reference to
On Fri, Apr 05, 2019 at 10:46:59AM -0700, Roman Gushchin wrote:
> This patchset implements freezer for cgroup v2.
>
> It provides similar functionality as v1 freezer, but the interface
> conforms to the cgroup v2 interface design principles, and it
> provides a better user experience: tasks can
At least the following versions of gcc-8:
- gcc version 8.0.1 20180414 (experimental) [trunk revision 259383] (Ubuntu
8-20180414-1ubuntu2)
- gcc 8.2.0-7ubuntu1 (Ubuntu 18.10 (Cosmic)),
generate broken assembler with asm goto that have a thread-local storage
"m" input operand on both x86-32 and
- On Apr 19, 2019, at 8:55 AM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Apr 19, 2019, at 8:41 AM, Mathieu Desnoyers
> mathieu.desnoy...@efficios.com wrote:
>
>> - On Apr 19, 2019, at 6:38 AM, Ingo Molnar mi...@kernel.org wrote:
>>
>>> * Mathieu Desnoyers
Initial introduction of Lenovo Hr630 family equipped with
Aspeed 2500 BMC SoC. Hr630 is a x86 server development kit
with a ASPEED ast2500 BMC manufactured by Lenovo.
Specifically, This adds the Hr630 platform device tree file
used by the Hr630 BMC machines.
This also adds an entry of Hr630
syzbot has found a reproducer for the following crash on:
HEAD commit:3f018f4a Add linux-next specific files for 20190418
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=128f767b20
kernel config:
On 4/19/19 7:30 AM, Po-Hsu Lin wrote:
Hello,
Commit f8a0590f fix some part of this issue.
I will send out V3 base on this commit in linux-kselftest next branch.
Thank you.
Yes. That sounds right based on my quick look at both patches.
Please send v3. I will get that into next.
thanks,
--
On 4/18/19 11:57 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.9.170 release.
There are 50 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On Fri, Apr 19, 2019 at 03:52:43PM +0530, Bhanusree Pola wrote:
> Replace rtw_malloc with kmalloc to make code OS independent
> use kmalloc second argument as GFP_ATOMIC as these are called by functions
> that holds lock.
>
> Signed-off-by: Bhanusree Pola
> ---
>
On Thu, 18 Apr 2019, Mauro Carvalho Chehab wrote:
> Em Thu, 18 Apr 2019 17:42:29 +0300
> Jani Nikula escreveu:
>
>> On Thu, 18 Apr 2019, Mauro Carvalho Chehab
>> wrote:
>> > Those three new drivers were missed on the initial conversion
>> > to ReST format. So:
>> >
>> > - Rename them to .rst;
Major changes in v2:
- Eliminate more errors and warnings
- Delete 'depends on !MIPS'
- Split into separate patches
Arnd Bergmann (1):
ARM: prevent tracing IPI_CPU_BACKTRACE
Masahiro Yamada (10):
arm64: mark (__)cpus_have_const_cap as __always_inline
MIPS: mark mult_sh_align_mod() as
The following changes since commit 79a3aaa7b82e3106be97842dedfd8429248896e6:
Linux 5.1-rc3 (2019-03-31 14:39:29 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git
tags/staging-5.1-rc6
for you to fetch changes up to
Atom-based CPUs trigger stack fault when invoke 32-bit SYSENTER instruction
with invalid register values. So we also need SIGBUS handling in this case.
Following is assembly when the fault exception happens.
(gdb) disassemble $eip
Dump of assembler code for function __kernel_vsyscall:
Hi Kuppuswamy,
On Wed, Mar 06, 2019 at 02:11:14PM -0800,
sathyanarayanan.kuppusw...@linux.intel.com wrote:
> From: Kuppuswamy Sathyanarayanan
>
> PF/VF implementation must comply with PCIe specification as
> defined in r4.0, sec 9.3.4, 9.3.5, 9.3.6 and 9.3.7. And if
> it does not comply,
From: Jiri Olsa
We currently don't return NULL in case we don't find the
bpf_prog_info_node, fixing that.
Signed-off-by: Jiri Olsa
Acked-by: Song Liu
Cc: Alexander Shishkin
Cc: Namhyung Kim
Cc: Peter Zijlstra
Fixes: e4378f0cb90b ("perf bpf: Save bpf_prog_info in a rbtree in perf_env")
On 4/19/19 7:48 AM, Mathieu Desnoyers wrote:
- On Apr 19, 2019, at 9:42 AM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
- On Apr 19, 2019, at 8:55 AM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
- On Apr 19, 2019, at 8:41 AM, Mathieu Desnoyers
Looks good, nice Job, Maomao
On Thu, Apr 18, 2019 at 02:20:40PM +0800, Mao Han wrote:
> This patch add support for page fault count, major fault count
> and minorfault count. Without this patch page faults are not
> sampled for perf event.
>
> Performance counter stats for
These switches are used to fornicate the motherboard's x16 PCIe ports
into four x4 ports for NVMe drives. In conjunction with the storage
backplane, the PDS bit reports only the out-of-band presence. The fact
that inband presence is disabled is not reported in the slot
capabilities 2 (SLTCAP2)
On 4/19/19 7:12 AM, Po-Hsu Lin wrote:
Test files created by test_create*() tests will stay in the
$efivarfs_mount directory unless the system was rebooted.
When the tester tries to run this efivarfs test again on the same
system, the immutable characteristics in that directory will cause some
> On Apr 19, 2019, at 7:17 AM, Dr. Greg wrote:
>
> On Thu, Apr 18, 2019 at 11:01:00AM -0700, Dave Hansen wrote:
> "The value of Intel SGX is to execute code in a protected enclave;
> however, Intel SGX does not guarantee that the code executed in the
> enclave is from a trusted source. In all
Hi Ingo,
On Fri, Apr 19, 2019 at 09:57:16AM +0200, Ingo Molnar wrote:
> > On Thu, Apr 18, 2019 at 04:46:45PM +0200, Lubomir Rintel wrote:
> > > This patch set modifies the OLPC battery driver so that it could
> > > eventually
> > > be used on an Arm-based OLPC XO 1.75 machine.
> > >
> > >
On Fri, Apr 19, 2019 at 07:13:07AM +, nobuhiro1.iwama...@toshiba.co.jp
wrote:
Hi,
[ Upstream commit 81b74ac68c28fddb3589ad5d4d5e587baf4bb781 ]
The driver allocates queues for all the units it potentially
supports. But if we fail to detect any drives, then we fail
loading the module
On Thu, Apr 18, 2019 at 09:35:44AM +0200, Marc Gonzalez wrote:
>
> It is not clear to me what I could/should have done differently to avoid
> the conflict?
I dropped the patch for now. We can deal with this later as it is trivial.
The best way probably would have been for Kishon to take this
On Thu, Apr 18, 2019 at 05:07:02PM -0400, Jerome Glisse wrote:
> On Tue, Apr 09, 2019 at 02:08:39PM +0800, Peter Xu wrote:
> > On Wed, Mar 20, 2019 at 10:06:14AM +0800, Peter Xu wrote:
> > > This series implements initial write protection support for
> > > userfaultfd. Currently both shmem and
From: Jiri Olsa
We don't return NULL when we don't find the bpf_prog_info_node, fix
that.
Signed-off-by: Jiri Olsa
Reported-by: Song Liu
Acked-by: Song Liu
Cc: Alexander Shishkin
Cc: Namhyung Kim
Cc: Peter Zijlstra
Fixes: 3792cb2ff43b ("perf bpf: Save BTF in a rbtree in perf_env")
Link:
On Wed, Mar 06, 2019 at 02:11:13PM -0800,
sathyanarayanan.kuppusw...@linux.intel.com wrote:
> From: Kuppuswamy Sathyanarayanan
>
> Current implementation of ATS, PASID, PRI does not handle the PF/VF
> dependencies as defined in PCIe spec r4.0. Following patches
> addresses this issue.
Some of
From: Jiri Olsa
Bastian reported broken 'perf top -p PID' command, it won't display any
data.
The problem is that for -p option we monitor single thread, so we don't
enable time in samples, because it's not needed.
However since commit 16c66bc167cc we use ordered queues to stash data
plus
From: Song Liu
As reported by Jiri Olsa in:
"[BUG] perf: intel_pt won't display kernel function"
https://lore.kernel.org/lkml/20190403143738.GB32001@krava
Recent changes to support PERF_RECORD_KSYMBOL and PERF_RECORD_BPF_EVENT
broke --kallsyms option. This is because it broke test
On 4/15/19 7:57 AM, Pierre-Louis Bossart wrote:
On 4/14/19 5:04 AM, Vinod Koul wrote:
On 10-04-19, 22:16, Pierre-Louis Bossart wrote:
SoundWire support will be provided in Linux with the Sound Open
Firmware (SOF) on Intel platforms. Before we start adding the missing
pieces, there are a
On 4/18/19 11:56 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.14.113 release.
There are 92 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On Thu, Apr 18, 2019 at 09:14:09PM +0100, Sudip Mukherjee wrote:
Hi Greg,
On Thu, Apr 18, 2019 at 7:25 PM Greg Kroah-Hartman
wrote:
[ Upstream commit 6377f787aeb945cae7abbb6474798de129e1f3ac ]
This has been fixed by 27da0d2ef998 ("appletalk: Fix compile regression").
I've queued it up,
On 4/19/19 1:10 AM, Tong Bo wrote:
Atom-based CPUs trigger stack fault when invoke 32-bit SYSENTER instruction
with invalid register values. So we also need SIGBUS handling in this case.
Following is assembly when the fault exception happens.
(gdb) disassemble $eip
Dump of assembler code for
1 - 100 of 522 matches
Mail list logo
