Commit-ID: 03b32cb2810814756095dbd91fce0c77617d096b
Gitweb: https://git.kernel.org/tip/03b32cb2810814756095dbd91fce0c77617d096b
Author: Adrian Hunter
AuthorDate: Fri, 21 Dec 2018 14:06:13 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 2 Jan 2019 10:42:45 -0300
perf thread-s
Commit-ID: e0b8951190c11797971864c845e0909561525621
Gitweb: https://git.kernel.org/tip/e0b8951190c11797971864c845e0909561525621
Author: Adrian Hunter
AuthorDate: Fri, 21 Dec 2018 14:06:14 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 2 Jan 2019 10:45:26 -0300
perf thread-s
On 03.01.2019 12:08, Marc Zyngier wrote:
> Hi Stephan,
>
> On 29/12/2018 14:14, Stefan Agner wrote:
>> Compiling with section mismatch debugging enabled prints the
>> following warning:
>> WARNING: vmlinux.o(.text+0xffa1b8): Section mismatch in reference from
>> the function gic_smp_init() to
Commit-ID: bd8e68ace110941f375f5d566b0cd99fe80634b8
Gitweb: https://git.kernel.org/tip/bd8e68ace110941f375f5d566b0cd99fe80634b8
Author: Adrian Hunter
AuthorDate: Fri, 21 Dec 2018 14:06:15 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 2 Jan 2019 10:48:18 -0300
perf thread-s
On Thu, 03 Jan 2019 12:43:54 +0100,
Con Kolivas wrote:
>
> Upon switching from 4.19.0 to 4.20.0, pulseaudio started complaining
> that sinks that previously worked are no longer supported.
>
> On 4.19.0 trying 24 bit 88200, 176400, and 192000 I get the following
> output from pulse.
> resampler.c
Commit-ID: f6060ac60190c625101a0b94c2d96e9ca14a7d73
Gitweb: https://git.kernel.org/tip/f6060ac60190c625101a0b94c2d96e9ca14a7d73
Author: Adrian Hunter
AuthorDate: Fri, 21 Dec 2018 14:06:16 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 2 Jan 2019 10:49:51 -0300
perf thread-s
Commit-ID: 2e9e8688763ff80f032d9a78c3b4b951fb6dd7a4
Gitweb: https://git.kernel.org/tip/2e9e8688763ff80f032d9a78c3b4b951fb6dd7a4
Author: Adrian Hunter
AuthorDate: Fri, 21 Dec 2018 14:06:17 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 2 Jan 2019 10:53:41 -0300
perf thread-s
Commit-ID: 139f42f3b3b495e61bb2cfef40e1dd5e845e3052
Gitweb: https://git.kernel.org/tip/139f42f3b3b495e61bb2cfef40e1dd5e845e3052
Author: Adrian Hunter
AuthorDate: Fri, 21 Dec 2018 14:06:18 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 2 Jan 2019 10:55:55 -0300
perf thread-s
Commit-ID: 256d92bc93fd40411a02be5cdba74a7bf91e6e09
Gitweb: https://git.kernel.org/tip/256d92bc93fd40411a02be5cdba74a7bf91e6e09
Author: Adrian Hunter
AuthorDate: Fri, 21 Dec 2018 14:06:19 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 2 Jan 2019 11:03:17 -0300
perf thread-s
Linus,
please pull sound fixes for v4.21-rc1 from:
git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git
tags/sound-fix-4.21-rc1
The topmost commit is 3e9ad24b0e91c066311a958afbd6210dda8a43eb
sound fixes for 4.21-rc1 (
Commit-ID: b25756df5b28cd7b6e91200fc5012e7c76e8ec69
Gitweb: https://git.kernel.org/tip/b25756df5b28cd7b6e91200fc5012e7c76e8ec69
Author: Adrian Hunter
AuthorDate: Fri, 21 Dec 2018 14:06:20 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 2 Jan 2019 11:05:06 -0300
perf session:
On Sun, Dec 23, 2018 at 12:55:12PM +0100, Michael Niewöhner wrote:
> There is another issue but I don't know if both are related. Maybe that's
> just a
> timing issue...
>
> root@debian:~# dd if=/dev/hwrng bs=1 count=1
> dd: error reading '/dev/hwrng': Operation not permitted
> 0+0 records in
> 0
From: Claudiu Beznea
Add push-pull mode support. In push-pull mode the channels' outputs have
same polarities and the edges are complementary delayed for one period.
Signed-off-by: Claudiu Beznea
---
drivers/pwm/core.c | 3 +++
include/linux/pwm.h | 3 +++
2 files changed, 6 insertions(+)
di
From: Claudiu Beznea
Add basic PWM modes: normal and complementary. These modes should
differentiate the single output PWM channels from two outputs PWM
channels. These modes could be set as follow:
1. PWM channels with one output per channel:
- normal mode
2. PWM channels with two outputs per ch
From: Claudiu Beznea
Add documentation for PWM push-pull mode.
Signed-off-by: Claudiu Beznea
---
Documentation/pwm.txt | 16
1 file changed, 16 insertions(+)
diff --git a/Documentation/pwm.txt b/Documentation/pwm.txt
index 669fd4c9cc8e..80552627627d 100644
--- a/Documentation
From: Claudiu Beznea
Add support for PWM push-pull mode. This is only supported by SAMA5D2 SoCs.
Signed-off-by: Claudiu Beznea
---
drivers/pwm/pwm-atmel.c | 40
1 file changed, 36 insertions(+), 4 deletions(-)
diff --git a/drivers/pwm/pwm-atmel.c b/dri
From: Claudiu Beznea
Add PWM normal and complementary modes.
Signed-off-by: Claudiu Beznea
---
Documentation/pwm.txt | 22 ++
1 file changed, 22 insertions(+)
diff --git a/Documentation/pwm.txt b/Documentation/pwm.txt
index 8fbf0aa3ba2d..669fd4c9cc8e 100644
--- a/Documenta
From: Claudiu Beznea
Add pwm capabilities for Atmel/Microchip PWM controllers.
Signed-off-by: Claudiu Beznea
---
drivers/pwm/pwm-atmel.c | 86 -
1 file changed, 57 insertions(+), 29 deletions(-)
diff --git a/drivers/pwm/pwm-atmel.c b/drivers/pwm
From: Claudiu Beznea
Hi,
This series extends PWM framework with PWM modes.
The current patch series add the following PWM modes:
- PWM mode normal
- PWM mode complementary
- PWM mode push-pull
In the following description PWMx_y refers to output y of PWM with ID x.
Normal mode - for PWM chann
On Thu, Jan 03, 2019 at 01:47:40PM +0100, Petr Mladek wrote:
> On Mon 2018-12-17 16:27:41, Petr Mladek wrote:
> > On Thu 2018-12-13 16:55:28, Josh Poimboeuf wrote:
> > > On Thu, Nov 29, 2018 at 10:44:27AM +0100, Petr Mladek wrote:
> > > Side note, it would probably be useful to have a klp_for_each_
On Thu, 2019-01-03 at 15:27 +0200, Jarkko Sakkinen wrote:
> On Sun, Dec 23, 2018 at 12:55:12PM +0100, Michael Niewöhner wrote:
> > There is another issue but I don't know if both are related. Maybe that's
> > just a
> > timing issue...
> >
> > root@debian:~# dd if=/dev/hwrng bs=1 count=1
> > dd: e
On Sun, Dec 16, 2018 at 02:32:38PM +0100, Michael Niewöhner wrote:
> dmesg cold boot with tpm_tis.interrupts=0 tpm_tis.force=1:
> --
> > dmesg | grep -i tpm
> [0.00] Command line: initrd=\initrd-test console=ttyS0,115200n8
> break=pr
Hi Rob,
On Vi, 2018-12-28 at 17:32 -0600, Rob Herring wrote:
> On Tue, Dec 18, 2018 at 04:30:01PM +, Viorel Suman wrote:
> >
> > This patch implements Audio Mixer CPU DAI driver for NXP iMX8 SOCs.
> > The Audio Mixer is a on-chip functional module that allows mixing
> > of
> > two audio strea
These options apply to all regulators in this chip.
ti,strict-supply-voltage-supervision:
Set STRICT flag in CONFIG1
ti,under-voltage-limit-microvolt:
Select 2.75, 2.95, 3.25 or 3.35 V UVLO in CONFIG1
ti,under-voltage-hyst-microvolt:
Select 200mV or 400mV UVLOHYS in CONFIG2
Signed-off-by: C
On 03/01/2019 03:37, Laura Abbott wrote:
> Hi,
>
> I got a compilation failure when building with CONFIG_VFIO_PCI_NVLINK2
> enabled:
>
> + make -s 'HOSTCFLAGS=-O2 -g -pipe -Wall -Werror=format-security
> -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions
> -fstack-protector-strong
This patch allows to configure input-voltage settings
of the TPS65218 regulator via device tree.
Changes for v2:
- handle the different options in separate functions
- add "ti," prefix and "-microvolt" postfix
- remove debug prints
- abort with an error in case of invalid values.
- extend doc
Add input voltage configuration options
Signed-off-by: Christian Hohnstaedt
---
.../devicetree/bindings/regulator/tps65218.txt | 22 ++
1 file changed, 22 insertions(+)
diff --git a/Documentation/devicetree/bindings/regulator/tps65218.txt
b/Documentation/devicetree/bind
On Thu, 2019-01-03 at 15:41 +0200, Jarkko Sakkinen wrote:
> On Sun, Dec 16, 2018 at 02:32:38PM +0100, Michael Niewöhner wrote:
>
> > dmesg cold boot with tpm_tis.interrupts=0 tpm_tis.force=1:
> > --
> > > dmesg | grep -i tpm
> > [0.0
Hi,
Each McASP pins can be configured individually to be used as McASP or GPIO pin.
This series will allow client drivers to use pins as GPIO (optional) in case the
board wired up them to be used in this mode.
Regards,
Peter
---
Peter Ujfalusi (3):
ASoC: ti: davinci-mcasp: Move context save/re
McASP can loose it's context when runtime_pm is disabled.
Save and restore the context when suspending and resuming the device.
Signed-off-by: Peter Ujfalusi
---
sound/soc/ti/davinci-mcasp.c | 136 +--
1 file changed, 64 insertions(+), 72 deletions(-)
diff --git
All McASP pin can be configured as GPIO.
Add gpiochip support for McASP and only enable it when the
gpio-controller is present in the DT node.
Signed-off-by: Peter Ujfalusi
---
sound/soc/ti/davinci-mcasp.c | 159 ++-
1 file changed, 156 insertions(+), 3 deletions(
McASP pins can be used as GPIO, add optional section to enable GPIO support
for McASP.
Signed-off-by: Peter Ujfalusi
---
.../bindings/sound/davinci-mcasp-audio.txt | 17 +
1 file changed, 17 insertions(+)
diff --git a/Documentation/devicetree/bindings/sound/davinci-mcasp-au
Hi Linus,
The following changes since commit 8e143b90e4d45cca3dc53760d3cfab988bc74571:
Merge tag 'iommu-updates-v4.21' of
git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu (2019-01-01 15:55:29
-0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/
On Thu, 2019-01-03 at 10:16 +0800, Nicolas Boichat wrote:
> On Wed, Jan 2, 2019 at 10:01 PM Henry Chen wrote:
> >
> > Add dvfsrc driver for MT8183
> >
> > Signed-off-by: Henry Chen
> > ---
> > drivers/soc/mediatek/Kconfig | 15 ++
> > drivers/soc/mediatek/Makefile | 1 +
> > drivers/
On Thu, 2019-01-03 at 09:48 +0800, Nicolas Boichat wrote:
> On Wed, Jan 2, 2019 at 10:01 PM Henry Chen wrote:
> >
> > Support power domain performance state, add header file for scp event.
> >
> > Signed-off-by: Henry Chen
> > ---
> > drivers/soc/mediatek/mtk-scpsys.c | 60
> > +
On Thu, 2019-01-03 at 10:17 +0530, Viresh Kumar wrote:
> On 02-01-19, 22:09, Henry Chen wrote:
> > Add support for performance state of scpsys on mt8183 platform.
> >
> > Signed-off-by: Henry Chen
> > ---
> > arch/arm64/boot/dts/mediatek/mt8183.dtsi | 21 +
> > 1 file changed
Hello.
This is v4. I think it is ready to go with, unless there are extra requests
or comments.
Changes in v4:
- Since the test can take time, switch to wait_for_completion_timeout()
with HZ sleep interval to prevent triggering of the trace about hung
task;
- Fix clean apply f
Export __vmaloc_node_range() function if CONFIG_TEST_VMALLOC_MODULE is
enabled. Some test cases in vmalloc test suite module require and make
use of that function. Please note, that it is not supposed to be used
for other purposes.
We need it only for performance analysis, stressing and stability
This adds a new kernel module for analysis of vmalloc allocator. It is
only enabled as a module. There are two main reasons this module should
be used for: performance evaluation and stressing of vmalloc subsystem.
It consists of several test cases. As of now there are 8. The module
has five param
Add the test script for the kernel test driver to analyse vmalloc
allocator for benchmarking and stressing purposes. It is just a kernel
module loader. You can specify and pass different parameters in order
to investigate allocations behaviour. See "usage" output for more
details.
Also add basic v
On Fri, 2018-12-21 at 16:20 +0100, Paolo Bonzini wrote:
> On 06/12/18 00:10, Jim Mattson wrote:
> >
> > On Mon, Dec 3, 2018 at 1:31 AM KarimAllah Ahmed wrote:
> > >
> > >
> > > Copy the VMCS12 directly from guest memory instead of the map->copy->unmap
> > > sequence. This also avoids using kvm_
The supported module parameters are detailed in both RCU/torture.txt and
admin-guide/kernel-parameters.txt, and the latter is actively maintained.
So this patch removes section MODULE PARAMETERS in torture.txt and
adds a reference to the information in kernel-parameters.txt.
Signed-off-by: Juncha
On Wed, Jan 02, 2019 at 08:18:33PM -0800, Matthew Wilcox wrote:
> On Wed, Jan 02, 2019 at 07:32:08PM -0800, John Hubbard wrote:
> > Having the range struct declared in separate places from the
> > mmu_notifier_range_init()
> > calls is not great. But I'm not sure I see a way to make it significant
On Wed, Jan 02, 2019 at 04:21:26PM -0800, Matthew Wilcox wrote:
>
> One of the paths in follow_pte_pmd() initialised the mmu_notifier_range
> incorrectly.
>
> Signed-off-by: Matthew Wilcox
> Fixes: ac46d4f3c432 ("mm/mmu_notifier: use structure for
> invalidate_range_start/end calls v2")
> Teste
On Thu, 2019-01-03 at 10:18 +0530, Viresh Kumar wrote:
> On 02-01-19, 22:09, Henry Chen wrote:
> > The patchsets add support for MediaTek hardware module named DVFSRC
> > (dynamic voltage and frequency scaling resource collector). The DVFSRC is
> > a HW module which is used to collect all the reque
Hi,
This patchset is the implementation of encryption and authentication
for hibernate snapshot image. The image will be encrypted by AES and
authenticated by HMAC.
The hibernate function can be used to snapshot memory pages to an image,
then kernel restores the image to memory space in a appropr
This patch adds a snapshot keys handler for using the key retention
service api to create keys for snapshot image encryption and
authentication.
This handler uses TPM trusted key as the snapshot master key, and the
encryption key and authentication key are derived from the snapshot
key. The user d
When producing memory snapshot image, hibernation uses HMAC-SHA512
with snapshot key (from TPM trusted key) to calculate the hash of
all data pages in snapshot image. The hash result will be kept in the
snapshot header as the image signature. Before hibernation restores
image, kernel executes HMAC-
If the encryption key be guessed then the snapshot master key can
also be grabbed from snapshot image. Which means that the authentication
key can also be calculated. So kernel erases master key in snapshot
pages.
Because the master key in image kernel be erased, kernel uses the
trampoline page to
To protect the secret in memory snapshot image, this patch adds the
logic to encrypt snapshot pages by AES-CTR. Using AES-CTR is because
it's simple, fast and parallelizable. But this patch didn't implement
parallel encryption.
The encrypt key is derived from the snapshot key. And the initializati
This kernel option is similar to the option for kernel module signature
verification. When this option is unselected, kernel will be tainted by
restored from a snapshot image without (valid) signature.
When the option is selected, kernel will refuse the system to be restored
from a unauthenticated
On Thu, Jan 03, 2019 at 09:31:16AM -0500, Jerome Glisse wrote:
> On Wed, Jan 02, 2019 at 04:21:26PM -0800, Matthew Wilcox wrote:
> >
> > One of the paths in follow_pte_pmd() initialised the mmu_notifier_range
> > incorrectly.
> >
> > Signed-off-by: Matthew Wilcox
> > Fixes: ac46d4f3c432 ("mm/mmu
The symbols provided by ssi-fiq are used in sound/soc/fsl/imx-pcm-fiq.c
only. Build ssi-fiq.o/ssi-fiq-ksym.o only if SND_SOC_IMX_PCM_FIQ is
enabled.
Signed-off-by: Stefan Agner
---
arch/arm/mach-imx/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/mach-imx/Ma
Hi Gregory,
Gregory CLEMENT wrote on Fri, 21 Dec 2018
18:32:56 +0100:
> Hello,
>
> this small series fixes wrong pins configuration we currently have on
> Armada 37xx.
>
> For now it is especially annoying it we want to enable suspend to
> RAM for PCie.
Thanks for the series, it works for me.
On Thu, Jan 03, 2019 at 09:29:59AM -0500, Jerome Glisse wrote:
> On Wed, Jan 02, 2019 at 08:18:33PM -0800, Matthew Wilcox wrote:
> > On Wed, Jan 02, 2019 at 07:32:08PM -0800, John Hubbard wrote:
> > > Having the range struct declared in separate places from the
> > > mmu_notifier_range_init()
> >
On Thu, Jan 03, 2019 at 09:31:16AM -0500, Jerome Glisse wrote:
> On Wed, Jan 02, 2019 at 04:21:26PM -0800, Matthew Wilcox wrote:
> >
> > One of the paths in follow_pte_pmd() initialised the mmu_notifier_range
> > incorrectly.
> >
> > Signed-off-by: Matthew Wilcox
> > Fixes: ac46d4f3c432 ("mm/mmu
On 19/12/2018 20:17, Michael Mueller wrote:
This function processes the Gib Alert List (GAL). It is required
to run when either a gib alert interruption has been received or
a gisa that is in the alert list is cleared or dropped.
The GAL is build up by millicode, when the respective ISC bit is
s
On Thu, Jan 03, 2019 at 10:26:54AM +0100, Jan Kara wrote:
> On Wed 02-01-19 20:55:33, Jerome Glisse wrote:
> > On Wed, Dec 19, 2018 at 12:08:56PM +0100, Jan Kara wrote:
> > > On Tue 18-12-18 21:07:24, Jerome Glisse wrote:
> > > > On Tue, Dec 18, 2018 at 03:29:34PM -0800, John Hubbard wrote:
> > > >
On 2/01/19 8:10 PM, Sinan Kaya wrote:
> After 'commit 5d32a66541c4 ("PCI/ACPI: Allow ACPI to be built without
> CONFIG_PCI set")' dependencies on CONFIG_PCI that previously were
> satisfied implicitly through dependencies on CONFIG_ACPI have to be
> specified directly. This driver relies on IOSF_MB
On Thu, Jan 3, 2019 at 2:50 PM Adrian Hunter wrote:
>
> On 2/01/19 8:10 PM, Sinan Kaya wrote:
> > After 'commit 5d32a66541c4 ("PCI/ACPI: Allow ACPI to be built without
> > CONFIG_PCI set")' dependencies on CONFIG_PCI that previously were
> > satisfied implicitly through dependencies on CONFIG_ACPI
On Wed, Jan 02, 2019 at 07:27:17PM -0800, John Hubbard wrote:
> On 1/2/19 5:55 PM, Jerome Glisse wrote:
> > On Wed, Dec 19, 2018 at 12:08:56PM +0100, Jan Kara wrote:
> >> On Tue 18-12-18 21:07:24, Jerome Glisse wrote:
> >>> On Tue, Dec 18, 2018 at 03:29:34PM -0800, John Hubbard wrote:
> OK, so
From: Claudiu Beznea
Commit 653e92a9175e ("net: macb: add support for padding and fcs
computation") introduced a bug fixed by commit 899ecaedd155 ("net:
ethernet: cadence: fix socket buffer corruption problem"). Code removed
in this patch is not reachable at all so remove it.
Fixes: 653e92a9175e
On Thu, Jan 03, 2019 at 06:39:08AM -0800, Matthew Wilcox wrote:
> On Thu, Jan 03, 2019 at 09:29:59AM -0500, Jerome Glisse wrote:
> > On Wed, Jan 02, 2019 at 08:18:33PM -0800, Matthew Wilcox wrote:
> > > On Wed, Jan 02, 2019 at 07:32:08PM -0800, John Hubbard wrote:
> > > > Having the range struct de
vmalloc_user*() calls differ from normal vmalloc() only in that they
set VM_USERMAP flags for the area. During the whole history of
vmalloc.c changes now it is possible simply to pass VM_USERMAP flags
directly to __vmalloc_node_range() call instead of finding the area
(which obviously takes time)
The first patch in series fixes size check for remap_vmalloc_range_partial()
which can lead to kernel crash by unfaithful userspace mapping. Others two
are minor cleanups.
Roman Penyaev (3):
mm/vmalloc: fix size check for remap_vmalloc_range_partial()
mm/vmalloc: do not call kmemleak_free() o
area->size can include adjacent guard page but get_vm_area_size()
returns actual size of the area.
This fixes possible kernel crash when userspace tries to map area
on 1 page bigger: size check passes but the following vmalloc_to_page()
returns NULL on last guard (non-existing) page.
Signed-off-b
__vmalloc_area_node() calls vfree() on error path, which in turn calls
kmemleak_free(), but area is not yet accounted by kmemleak_vmalloc().
Signed-off-by: Roman Penyaev
Cc: Andrew Morton
Cc: Michal Hocko
Cc: Andrey Ryabinin
Cc: Joe Perches
Cc: "Luis R. Rodriguez"
Cc: linux...@kvack.org
Cc:
The intention of a new benchmark is to measure events delivery
bandwidth: N threads produce events and 1 thread consumes events
calling epoll_wait(2).
Benchmark does measurements for 8, 16, 32, 64 and 128 threads in
a loop.
This one differs from epoll-wait in that it produces events from
many thr
I want to rename this in order to add another epoll-wait bench in next
patch and to stress in the name, that the bench corresponds to 1 producer
and many consumers.
In the following patch I plan to add epoll-wait-mp1c bench.
Signed-off-by: Roman Penyaev
Cc: Arnaldo Carvalho de Melo
Cc: Andrew M
On 19/12/2018 20:17, Michael Mueller wrote:
The IAM shall no be restored when deliverable interruptions are
delivered to vcpus by means of the PSW swap mechanism. That would
trigger the GIB alert millicode although we know that SIE will be
able to handle the pending interruption on entry.
Signed
The intention of this benchmark is to measure events delivery
bandwidth: N threads produce events and 1 thread consumes events
calling epoll_wait(2).
Benchmark does measurements for 8, 16, 32, 64 and 128 threads in
a loop.
This one differs from epoll-wait-1pmc in that it produces events
from many
The last patch targets the contention problem in ep_poll_callback(), which
can be very well reproduced by generating events (write to pipe or eventfd)
from many threads, while consumer thread does polling.
The following are some microbenchmark results based on the test [1] which
starts threads whi
The goal of this patch is to reduce contention of ep_poll_callback() which
can be called concurrently from different CPUs in case of high events
rates and many fds per epoll. Problem can be very well reproduced by
generating events (write to pipe or eventfd) from many threads, while
consumer threa
Original comment "Activate ep->ws since epi->ws may get deactivated
at any time" indeed sounds loud, but it is incorrect, because the path
where we check epi->ws is a path where insert to ovflist happens, i.e.
ep_scan_ready_list() has taken ep->mtx and waits for this callback
to finish, thus ep_mod
All coming events are stored in FIFO order and this is also should be
applicable to ->ovflist, which originally is stack, i.e. LIFO.
Thus to keep correct FIFO order ->ovflist should reversed by adding
elements to the head of the read list but not to the tail.
Signed-off-by: Roman Penyaev
Reviewe
Callers of the ep_poll_callback() (all set of wake_up_*poll()) disable
interrupts, so no need to save/restore irq flags.
Signed-off-by: Roman Penyaev
Cc: Davidlohr Bueso
Cc: Jason Baron
Cc: Al Viro
Cc: Andrew Morton
Cc: Linus Torvalds
Cc: linux-fsde...@vger.kernel.org
Cc: linux-kernel@vger.k
On Wed, Jan 02, 2019 at 12:47:52PM -0800, Sean Christopherson wrote:
> On Sat, Dec 22, 2018 at 10:25:02AM +0200, Jarkko Sakkinen wrote:
> > On Sat, Dec 22, 2018 at 10:16:49AM +0200, Jarkko Sakkinen wrote:
> > > On Thu, Dec 20, 2018 at 12:32:04PM +0200, Jarkko Sakkinen wrote:
> > > > On Wed, Dec 19,
On Thu, Jan 03, 2019 at 02:38:11PM +0100, Michael Niewöhner wrote:
> On Thu, 2019-01-03 at 15:27 +0200, Jarkko Sakkinen wrote:
> > On Sun, Dec 23, 2018 at 12:55:12PM +0100, Michael Niewöhner wrote:
> > > There is another issue but I don't know if both are related. Maybe that's
> > > just a
> > > ti
On Thu, Jan 03, 2019 at 06:43:13AM -0800, Matthew Wilcox wrote:
> On Thu, Jan 03, 2019 at 09:31:16AM -0500, Jerome Glisse wrote:
> > On Wed, Jan 02, 2019 at 04:21:26PM -0800, Matthew Wilcox wrote:
> > >
> > > One of the paths in follow_pte_pmd() initialised the mmu_notifier_range
> > > incorrectly
PCI changes:
- Remove unused lists from ASPM pcie_link_state (Frederick Lawler)
- Fix Broadcom CNB20LE host bridge unintended sign extension (Colin Ian
King)
- Expand Kconfig "PF" acronyms (Randy Dunlap)
- Update MAINTAINERS for arch/x86/kernel/early-quirks.c (Bjorn Helgaas)
- Ad
On Thu, 3 Jan 2019, Icenowy Zheng wrote:
> SMI SM3350 UFS-USB bridge controller cannot handle REQUEST SENSE command
> with long sense (96-bytes) well, and will even trap the controller into
> a state that refuses to do read/write command.
>
> Currently Linux uncondintionally set US_FL_SANE_SENSE
On 19/12/2018 20:17, Michael Mueller wrote:
The patch adds the parameter irq_flags and allows to
restore the Interruption Alert Mask (IAM) in the GISA
atomically while guaranteeing the IPM is clean.
The function returns the IPM of the GISA. If the returned
value is 0x00 and the IRQ_FLAG_IAM was
On 1/3/19 5:49 AM, Alexey Kardashevskiy wrote:
On 03/01/2019 03:37, Laura Abbott wrote:
Hi,
I got a compilation failure when building with CONFIG_VFIO_PCI_NVLINK2
enabled:
+ make -s 'HOSTCFLAGS=-O2 -g -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexc
From: Bartosz Golaszewski
Hi Sekhar,
I noticed some more breakage resulting from commit 587f7a694f01 ("gpio:
davinci: Use dev name for label and automatic base selection"). This
series fixes GPIO lookups in legacy mode for DaVinci.
Bartosz Golaszewski (5):
ARM: davinci: da830-evm: fix label n
From: Bartosz Golaszewski
Since commit 587f7a694f01 ("gpio: davinci: Use dev name for label and
automatic base selection") the gpiochip label no longer has an ID
suffix. Update the GPIO lookup entries.
Fixes: 587f7a694f01 ("gpio: davinci: Use dev name for label and automatic base
selection")
Cc
From: Bartosz Golaszewski
Since commit 587f7a694f01 ("gpio: davinci: Use dev name for label and
automatic base selection") the gpiochip label no longer has an ID
suffix. Update the GPIO lookup entries.
Fixes: 587f7a694f01 ("gpio: davinci: Use dev name for label and automatic base
selection")
Cc
From: Bartosz Golaszewski
Since commit 587f7a694f01 ("gpio: davinci: Use dev name for label and
automatic base selection") the gpiochip label no longer has an ID
suffix. Update the GPIO lookup entries.
Fixes: 587f7a694f01 ("gpio: davinci: Use dev name for label and automatic base
selection")
Cc
On Wed, 2 Jan 2019, Michael S. Tsirkin wrote:
> On Wed, Jan 02, 2019 at 04:36:40PM -0500, Alan Stern wrote:
> > On Wed, 2 Jan 2019, Michael S. Tsirkin wrote:
> >
> > > So as explained in Documentation/memory-barriers.txt e.g.
> > > a load followed by a store require a full memory barrier,
> > > t
From: Bartosz Golaszewski
Since commit 587f7a694f01 ("gpio: davinci: Use dev name for label and
automatic base selection") the gpiochip label no longer has an ID
suffix. Update the GPIO lookup entries.
Fixes: 587f7a694f01 ("gpio: davinci: Use dev name for label and automatic base
selection")
Cc
From: Bartosz Golaszewski
Since commit 587f7a694f01 ("gpio: davinci: Use dev name for label and
automatic base selection") the gpiochip label no longer has an ID
suffix. Update the GPIO lookup entries.
Fixes: 587f7a694f01 ("gpio: davinci: Use dev name for label and automatic base
selection")
Cc
On Thu 03-01-19 15:59:52, Roman Penyaev wrote:
> area->size can include adjacent guard page but get_vm_area_size()
> returns actual size of the area.
>
> This fixes possible kernel crash when userspace tries to map area
> on 1 page bigger: size check passes but the following vmalloc_to_page()
> re
On 19/12/2018 20:17, Michael Mueller wrote:
The patch implements a handler for GIB alert interruptions
on the host. Its task is to alert guests that interrupts are
pending for them.
A GIB alert interrupt statistic counter is added as well:
$ cat /proc/interrupts
CPU0 CPU1
..
On Thu 03-01-19 15:59:54, Roman Penyaev wrote:
> vmalloc_user*() calls differ from normal vmalloc() only in that they
> set VM_USERMAP flags for the area. During the whole history of
> vmalloc.c changes now it is possible simply to pass VM_USERMAP flags
> directly to __vmalloc_node_range() call in
On Wed, Jan 2, 2019 at 11:55 PM Wei Wang wrote:
> Right, thanks. Probably better to change it to below:
>
> msr_info->data = 0;
> data = native_read_msr(MSR_IA32_PERF_CAPABILITIES);
> if (vcpu->kvm->arch.lbr_in_guest)
> msr_info->data |= (data & X86_PERF_CAP_MASK_LBR_FMT);
>
This still brea
On Wed 02-01-19 19:40:15, YueHaibing wrote:
> On 2019/1/2 18:55, Dan Carpenter wrote:
> > On Fri, Dec 28, 2018 at 09:58:04AM +0100, Michal Hocko wrote:
> >> On Fri 28-12-18 02:46:30, YueHaibing wrote:
> >>> Fixes gcc '-Wunused-but-set-variable' warning when
> >>> CONFIG_VMAP_STACK is not set:
> >>
On Wed, Jan 2, 2019 at 11:16 PM Wei Wang wrote:
>
> On 01/03/2019 07:26 AM, Jim Mattson wrote:
> > On Wed, Dec 26, 2018 at 2:01 AM Wei Wang wrote:
> >> The lbr stack is architecturally specific, for example, SKX has 32 lbr
> >> stack entries while HSW has 16 entries, so a HSW guest running on a S
On Thu, Jan 03, 2019 at 06:11:59PM +0800, Huang Shijie wrote:
> On Wed, Jan 02, 2019 at 11:55:50PM -0800, Christoph Hellwig wrote:
> > On Mon, Dec 24, 2018 at 03:06:22PM +0800, Huang Shijie wrote:
> > > We may use the addr_in_gen_pool() in the driver module.
> > > So export the addr_in_gen_pool for
Hi Linus,
The following changes since commit 8fe28cb58bcb235034b64cbbb7550a8a43fd88be:
Linux 4.20 (2018-12-23 15:55:59 -0800)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-4.21-rc1
for you to fetch changes up to 5ccedf1ccd710ba32f36986b49eeb7
Add Makefile changes to invoke the system call table generation
script which is placed in scripts directory as a common location
accessible for all the architectures.
Add syscall_arm32.tbl in syscalls directory which is copied from
arch/arm/tools/syscall.tbl and made some changes as per the req-
u
This will be an automated scripts to provide easy support
for add/modify/delete the system call entry by add in
respective *.tbl file.
System call table generation support for asm-generic is
provide for arm64 architecture which will use the common
scripts resides in scripts directory and use sysc
201 - 300 of 687 matches
Mail list logo
