>
>
> On Sat, 20 Oct 2018, Winkler, Tomas wrote:
>
> >>
> >> On Thu, 18 Oct 2018, Winkler, Tomas wrote:
> -Original Message-
> From: Jarkko Sakkinen [mailto:jarkko.sakki...@linux.intel.com]
> Sent: Thursday, October 18, 2018 03:15
> To: Winkler, Tomas
> Cc:
>
>
> On Sat, 20 Oct 2018, Winkler, Tomas wrote:
>
> >>
> >> On Thu, 18 Oct 2018, Winkler, Tomas wrote:
> -Original Message-
> From: Jarkko Sakkinen [mailto:jarkko.sakki...@linux.intel.com]
> Sent: Thursday, October 18, 2018 03:15
> To: Winkler, Tomas
> Cc:
On Mon, Oct 22, 2018 at 8:11 AM Krein, Dennis wrote:
> Hi Paul,
>
> My name is Dennis Krein - I am a software engineer at Netapp/Solidfire. I
> was referred to you by a tech lead in my departement, Marshalll McMullen.
> We have encountered a bug in Linux kernel - lately occurring in 4.14.67,
>
On Mon, Oct 22, 2018 at 8:11 AM Krein, Dennis wrote:
> Hi Paul,
>
> My name is Dennis Krein - I am a software engineer at Netapp/Solidfire. I
> was referred to you by a tech lead in my departement, Marshalll McMullen.
> We have encountered a bug in Linux kernel - lately occurring in 4.14.67,
>
On Tue, Oct 23, 2018 at 12:06 PM Ingo Molnar wrote:
>
> Please pull the latest sched-core-for-linus git tree from:
Hmm. I've pulled, but this message was odd and mis-formed.
First off, it didn't have a diffstat (I did verify the shortlog instead).
Secondly, can you please check how you send
On Tue, Oct 23, 2018 at 12:06 PM Ingo Molnar wrote:
>
> Please pull the latest sched-core-for-linus git tree from:
Hmm. I've pulled, but this message was odd and mis-formed.
First off, it didn't have a diffstat (I did verify the shortlog instead).
Secondly, can you please check how you send
Hi Clément,
On 10/09/2018 06:28 AM, Clément Péron wrote:
> Cyclone5 and Arria10 doesn't have the same memory map for UART1.
>
> Split the SOCFPGA_UART1 into 2 options to allow debugging on UART1 for
> Cylone5.
>
I'm not sure the need for this patch. Are there any cyclone5 based
boards that
Hi Clément,
On 10/09/2018 06:28 AM, Clément Péron wrote:
> Cyclone5 and Arria10 doesn't have the same memory map for UART1.
>
> Split the SOCFPGA_UART1 into 2 options to allow debugging on UART1 for
> Cylone5.
>
I'm not sure the need for this patch. Are there any cyclone5 based
boards that
This patch was initially posted by Kelley(kelley...@gmail.com).
Reposting the patch with all review comments addressed and with minor
modifications and optimizations. Tests were rerun and commit message
updated with new results.
The function try_to_unuse() is of quadratic complexity, with a lot
This patch was initially posted by Kelley(kelley...@gmail.com).
Reposting the patch with all review comments addressed and with minor
modifications and optimizations. Tests were rerun and commit message
updated with new results.
The function try_to_unuse() is of quadratic complexity, with a lot
Hi Lokesh,
On Mon, 22 Oct 2018 15:35:41 +0100,
Lokesh Vutla wrote:
>
> Hi Marc,
>
> On Friday 19 October 2018 08:52 PM, Marc Zyngier wrote:
> > Hi Lokesh,
> >
> > On 18/10/18 16:40, Lokesh Vutla wrote:
> >> Texas Instruments' K3 generation SoCs has an IP Interrupt Aggregator
> >> which is an
Hi Lokesh,
On Mon, 22 Oct 2018 15:35:41 +0100,
Lokesh Vutla wrote:
>
> Hi Marc,
>
> On Friday 19 October 2018 08:52 PM, Marc Zyngier wrote:
> > Hi Lokesh,
> >
> > On 18/10/18 16:40, Lokesh Vutla wrote:
> >> Texas Instruments' K3 generation SoCs has an IP Interrupt Aggregator
> >> which is an
The following changes since commit be65e2595b4c1fbeceba336d8ee83406726b1d8d:
Merge tag 'trace-v4.19-rc2' of
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace (2018-09-06
09:06:49 -0700)
are available in the Git repository at:
git://github.com/kleikamp/linux-shaggy.git
The following changes since commit be65e2595b4c1fbeceba336d8ee83406726b1d8d:
Merge tag 'trace-v4.19-rc2' of
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace (2018-09-06
09:06:49 -0700)
are available in the Git repository at:
git://github.com/kleikamp/linux-shaggy.git
When running on linux-next (8c60c36d0b8c ("Add linux-next specific files
for 20181019")) + CONFIG_PROVE_LOCKING=y on a big.LITTLE system (e.g.
Juno or HiKey960), we get the following report:
[0.748225] Call trace:
[0.750685] lockdep_assert_cpus_held+0x30/0x40
[0.755236]
When running on linux-next (8c60c36d0b8c ("Add linux-next specific files
for 20181019")) + CONFIG_PROVE_LOCKING=y on a big.LITTLE system (e.g.
Juno or HiKey960), we get the following report:
[0.748225] Call trace:
[0.750685] lockdep_assert_cpus_held+0x30/0x40
[0.755236]
>
> On Mon, 22 Oct 2018, Winkler, Tomas wrote:
> >> This is the list of patches (assuming that I didn't miss anything)
> >> that still need tested-by tags:
> >
> > Those are just code movements, we are running them form months on our
> > systems.
>
> I'm not sure what point you are trying to
>
> On Mon, 22 Oct 2018, Winkler, Tomas wrote:
> >> This is the list of patches (assuming that I didn't miss anything)
> >> that still need tested-by tags:
> >
> > Those are just code movements, we are running them form months on our
> > systems.
>
> I'm not sure what point you are trying to
tx_empty is not used after setting its value. It is safe to remove
the unused variable.
Signed-off-by: zhong jiang
---
drivers/tty/serial/pch_uart.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/tty/serial/pch_uart.c b/drivers/tty/serial/pch_uart.c
index cb85002..9ed121f 100644
tx_empty is not used after setting its value. It is safe to remove
the unused variable.
Signed-off-by: zhong jiang
---
drivers/tty/serial/pch_uart.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/tty/serial/pch_uart.c b/drivers/tty/serial/pch_uart.c
index cb85002..9ed121f 100644
On Sat, 20 Oct 2018, Winkler, Tomas wrote:
On Thu, 18 Oct 2018, Winkler, Tomas wrote:
-Original Message-
From: Jarkko Sakkinen [mailto:jarkko.sakki...@linux.intel.com]
Sent: Thursday, October 18, 2018 03:15
To: Winkler, Tomas
Cc: Jarkko Sakkinen ; Jason
Gunthorpe ; Nayna Jain ;
On Sat, 20 Oct 2018, Winkler, Tomas wrote:
On Thu, 18 Oct 2018, Winkler, Tomas wrote:
-Original Message-
From: Jarkko Sakkinen [mailto:jarkko.sakki...@linux.intel.com]
Sent: Thursday, October 18, 2018 03:15
To: Winkler, Tomas
Cc: Jarkko Sakkinen ; Jason
Gunthorpe ; Nayna Jain ;
Al Viro wrote:
> On Sat, Oct 20, 2018 at 02:10:52AM +0100, David Howells wrote:
> > Renumber the ITER_* constants in uio.h to be contiguous to make comparing
> > them more efficient in a switch-statement.
>
> Are you sure that they *are* more efficient that way? Some of those paths
> are
Al Viro wrote:
> On Sat, Oct 20, 2018 at 02:10:52AM +0100, David Howells wrote:
> > Renumber the ITER_* constants in uio.h to be contiguous to make comparing
> > them more efficient in a switch-statement.
>
> Are you sure that they *are* more efficient that way? Some of those paths
> are
On 10/22/2018 10:59 AM, Steve Sistare wrote:
[...]
> diff --git a/kernel/sched/topology.c b/kernel/sched/topology.c
> index f18c416..b7d2070 100644
> --- a/kernel/sched/topology.c
> +++ b/kernel/sched/topology.c
> @@ -1337,6 +1337,30 @@ static void init_numa_topology_type(void)
> }
> }
>
On 10/22/2018 10:59 AM, Steve Sistare wrote:
[...]
> diff --git a/kernel/sched/topology.c b/kernel/sched/topology.c
> index f18c416..b7d2070 100644
> --- a/kernel/sched/topology.c
> +++ b/kernel/sched/topology.c
> @@ -1337,6 +1337,30 @@ static void init_numa_topology_type(void)
> }
> }
>
Em Tue, Oct 23, 2018 at 02:43:05PM +0300, Alexey Budankov escreveu:
> Hi Arnaldo,
>
> On 09.10.2018 22:32, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Oct 09, 2018 at 05:36:24PM +0300, Alexey Budankov escreveu:
> >>
> >> Store -k clockid frequency into Perf trace to enable timestamps
> >>
Em Tue, Oct 23, 2018 at 02:43:05PM +0300, Alexey Budankov escreveu:
> Hi Arnaldo,
>
> On 09.10.2018 22:32, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Oct 09, 2018 at 05:36:24PM +0300, Alexey Budankov escreveu:
> >>
> >> Store -k clockid frequency into Perf trace to enable timestamps
> >>
On Mon, 22 Oct 2018, Winkler, Tomas wrote:
This is the list of patches (assuming that I didn't miss anything)
that still need tested-by tags:
Those are just code movements, we are running them form months on our
systems.
I'm not sure what point you are trying to make. You cannot give
On Mon, 22 Oct 2018, Winkler, Tomas wrote:
This is the list of patches (assuming that I didn't miss anything)
that still need tested-by tags:
Those are just code movements, we are running them form months on our
systems.
I'm not sure what point you are trying to make. You cannot give
Let arm64 subscribe to generic HugeTLB page migration framework. Right now
this only works on the following PMD and PUD level HugeTLB page sizes with
various kernel base page size combinations.
CONT PTEPMDCONT PMDPUD
------
4K: NA
Let arm64 subscribe to the previously added framework in which architecture
can inform whether a given huge page size is supported for migration. This
just overrides the default function arch_hugetlb_migration_supported() and
enables migration for all possible HugeTLB page sizes on arm64. With
Let arm64 subscribe to generic HugeTLB page migration framework. Right now
this only works on the following PMD and PUD level HugeTLB page sizes with
various kernel base page size combinations.
CONT PTEPMDCONT PMDPUD
------
4K: NA
Let arm64 subscribe to the previously added framework in which architecture
can inform whether a given huge page size is supported for migration. This
just overrides the default function arch_hugetlb_migration_supported() and
enables migration for all possible HugeTLB page sizes on arm64. With
On 16 October 2018 at 10:19, Chunyan Zhang wrote:
> The driver should clean resources requested in the function before
> unnormal return.
>
> CC: Linus Walleij
> Signed-off-by: Chunyan Zhang
> Fixes: bd9b902798ab ("mmc: sdhci: Implement an SDHCI-specific bounce buffer")
> ---
>
During huge page allocation it's migratability is checked to determine if
it should be placed under movable zones with GFP_HIGHUSER_MOVABLE. But the
movability aspect of the huge page could depend on other factors than just
migratability. Movability in itself is a distinct property which should
On 16 October 2018 at 10:19, Chunyan Zhang wrote:
> The driver should clean resources requested in the function before
> unnormal return.
>
> CC: Linus Walleij
> Signed-off-by: Chunyan Zhang
> Fixes: bd9b902798ab ("mmc: sdhci: Implement an SDHCI-specific bounce buffer")
> ---
>
During huge page allocation it's migratability is checked to determine if
it should be placed under movable zones with GFP_HIGHUSER_MOVABLE. But the
movability aspect of the huge page could depend on other factors than just
migratability. Movability in itself is a distinct property which should
Architectures like arm64 have PUD level HugeTLB pages for certain configs
(1GB huge page is PUD based on ARM64_4K_PAGES base page size) that can be
enabled for migration. It can be achieved through checking for PUD_SHIFT
order based HugeTLB pages during migration.
Reviewed-by: Naoya Horiguchi
Architectures like arm64 have PUD level HugeTLB pages for certain configs
(1GB huge page is PUD based on ARM64_4K_PAGES base page size) that can be
enabled for migration. It can be achieved through checking for PUD_SHIFT
order based HugeTLB pages during migration.
Reviewed-by: Naoya Horiguchi
Architectures like arm64 have HugeTLB page sizes which are different than
generic sizes at PMD, PUD, PGD level and implemented via contiguous bits.
At present these special size HugeTLB pages cannot be identified through
macros like (PMD|PUD|PGDIR)_SHIFT and hence chosen not be migrated.
Enabling
Architectures like arm64 have HugeTLB page sizes which are different than
generic sizes at PMD, PUD, PGD level and implemented via contiguous bits.
At present these special size HugeTLB pages cannot be identified through
macros like (PMD|PUD|PGDIR)_SHIFT and hence chosen not be migrated.
Enabling
This patch series enables HugeTLB migration support for all supported
huge page sizes at all levels including contiguous bit implementation.
Following HugeTLB migration support matrix has been enabled with this
patch series. All permutations have been tested except for the 16GB.
CONT PTE
This patch series enables HugeTLB migration support for all supported
huge page sizes at all levels including contiguous bit implementation.
Following HugeTLB migration support matrix has been enabled with this
patch series. All permutations have been tested except for the 16GB.
CONT PTE
On Tue 23-10-18 21:33:43, Tetsuo Handa wrote:
> On 2018/10/23 21:10, Michal Hocko wrote:
> > On Tue 23-10-18 13:42:46, Michal Hocko wrote:
> >> On Tue 23-10-18 10:01:08, Tetsuo Handa wrote:
> >>> Michal Hocko wrote:
> On Mon 22-10-18 20:45:17, Tetsuo Handa wrote:
> >> diff --git
On Tue 23-10-18 21:33:43, Tetsuo Handa wrote:
> On 2018/10/23 21:10, Michal Hocko wrote:
> > On Tue 23-10-18 13:42:46, Michal Hocko wrote:
> >> On Tue 23-10-18 10:01:08, Tetsuo Handa wrote:
> >>> Michal Hocko wrote:
> On Mon 22-10-18 20:45:17, Tetsuo Handa wrote:
> >> diff --git
Hi Matthias,
> matthias@kernel.org hat am 21. Oktober 2018 um 23:58 geschrieben:
>
>
> From: Matthias Brugger
>
> By defaul of-based thermal driver do not enable hwmon.
> This patch does this explicitly, so that the temperature can be read
> through the common hwmon sysfs.
>
>
Hi Matthias,
> matthias@kernel.org hat am 21. Oktober 2018 um 23:58 geschrieben:
>
>
> From: Matthias Brugger
>
> By defaul of-based thermal driver do not enable hwmon.
> This patch does this explicitly, so that the temperature can be read
> through the common hwmon sysfs.
>
>
Linus,
Please pull the latest x86-hyperv-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-hyperv-for-linus
# HEAD: 5140a6f471137205687428b0b8f12f7187bffd18 x86/hyperv: Remove unused
include
Two small changes: a boot warning removal and a minor
Linus,
Please pull the latest x86-hyperv-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-hyperv-for-linus
# HEAD: 5140a6f471137205687428b0b8f12f7187bffd18 x86/hyperv: Remove unused
include
Two small changes: a boot warning removal and a minor
Linus,
Please pull the latest x86-vdso-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-vdso-for-linus
# HEAD: 99c19e6a8fe4a95fa0dac191207a1d40461b1604 x86/vdso: Rearrange
do_hres() to improve code generation
Two main changes:
- Cleanups,
Linus,
Please pull the latest x86-vdso-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-vdso-for-linus
# HEAD: 99c19e6a8fe4a95fa0dac191207a1d40461b1604 x86/vdso: Rearrange
do_hres() to improve code generation
Two main changes:
- Cleanups,
On 2018/10/23 21:10, Michal Hocko wrote:
> On Tue 23-10-18 13:42:46, Michal Hocko wrote:
>> On Tue 23-10-18 10:01:08, Tetsuo Handa wrote:
>>> Michal Hocko wrote:
On Mon 22-10-18 20:45:17, Tetsuo Handa wrote:
>> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
>> index
On 2018/10/23 21:10, Michal Hocko wrote:
> On Tue 23-10-18 13:42:46, Michal Hocko wrote:
>> On Tue 23-10-18 10:01:08, Tetsuo Handa wrote:
>>> Michal Hocko wrote:
On Mon 22-10-18 20:45:17, Tetsuo Handa wrote:
>> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
>> index
Linus,
Please pull the latest x86-pti-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-pti-for-linus
# HEAD: bb4b3b7762735cdaba5a40fd94c9303d9ffa147a x86/speculation: Propagate
information about RSB filling mitigation to sysfs
The main changes:
-
Linus,
Please pull the latest x86-pti-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-pti-for-linus
# HEAD: bb4b3b7762735cdaba5a40fd94c9303d9ffa147a x86/speculation: Propagate
information about RSB filling mitigation to sysfs
The main changes:
-
On Wed, Oct 10, 2018 at 03:19:03PM +0800, Huang Ying wrote:
> And for all, Any comment is welcome!
>
> This patchset is based on the 2018-10-3 head of mmotm/master.
There seems to be some infrequent memory corruption with THPs that have been
swapped out: page contents differ after swapin.
On Wed, Oct 10, 2018 at 03:19:03PM +0800, Huang Ying wrote:
> And for all, Any comment is welcome!
>
> This patchset is based on the 2018-10-3 head of mmotm/master.
There seems to be some infrequent memory corruption with THPs that have been
swapped out: page contents differ after swapin.
Hi Pavan,
On Tue, 23 Oct 2018 at 07:59, Pavan Kondeti wrote:
>
> Hi Vincent,
>
> On Fri, Oct 19, 2018 at 06:17:51PM +0200, Vincent Guittot wrote:
> >
> > /*
> > + * The clock_pelt scales the time to reflect the effective amount of
> > + * computation done during the running delta time but then
Hi Pavan,
On Tue, 23 Oct 2018 at 07:59, Pavan Kondeti wrote:
>
> Hi Vincent,
>
> On Fri, Oct 19, 2018 at 06:17:51PM +0200, Vincent Guittot wrote:
> >
> > /*
> > + * The clock_pelt scales the time to reflect the effective amount of
> > + * computation done during the running delta time but then
tocuse is not used after setting its value. It is safe to remove
the unused variable.
Signed-off-by: zhong jiang
---
drivers/cdrom/gdrom.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/cdrom/gdrom.c b/drivers/cdrom/gdrom.c
index 757e85b..b45c543 100644
---
tocuse is not used after setting its value. It is safe to remove
the unused variable.
Signed-off-by: zhong jiang
---
drivers/cdrom/gdrom.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/cdrom/gdrom.c b/drivers/cdrom/gdrom.c
index 757e85b..b45c543 100644
---
On 23 October 2018 at 10:41, Linus Torvalds
wrote:
> So I've obviously started pulling stuff for the merge window, and one
> of the things I noticed with Greg doing it for the last few weeks was
> that he has this habit (or automation) to send Ack emails when he
> pulls.
>
> In fact, I reacted to
On 23 October 2018 at 10:41, Linus Torvalds
wrote:
> So I've obviously started pulling stuff for the merge window, and one
> of the things I noticed with Greg doing it for the last few weeks was
> that he has this habit (or automation) to send Ack emails when he
> pulls.
>
> In fact, I reacted to
On Tue 23-10-18 13:42:46, Michal Hocko wrote:
> On Tue 23-10-18 10:01:08, Tetsuo Handa wrote:
> > Michal Hocko wrote:
> > > On Mon 22-10-18 20:45:17, Tetsuo Handa wrote:
> > > > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > > > > index e79cb59552d9..a9dfed29967b 100644
> > > > > ---
Linus,
Please pull the latest x86-platform-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-platform-for-linus
# HEAD: fa112cf1e8bc693d5a666b1c479a2859c8b6e0f1 x86/olpc: Fix build error
with CONFIG_MFD_CS5535=m
Two minor OLPC changes: a build fix
On Tue 23-10-18 13:42:46, Michal Hocko wrote:
> On Tue 23-10-18 10:01:08, Tetsuo Handa wrote:
> > Michal Hocko wrote:
> > > On Mon 22-10-18 20:45:17, Tetsuo Handa wrote:
> > > > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > > > > index e79cb59552d9..a9dfed29967b 100644
> > > > > ---
Linus,
Please pull the latest x86-platform-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-platform-for-linus
# HEAD: fa112cf1e8bc693d5a666b1c479a2859c8b6e0f1 x86/olpc: Fix build error
with CONFIG_MFD_CS5535=m
Two minor OLPC changes: a build fix
On Tue, 23 Oct 2018 at 12:01, Peter Zijlstra wrote:
>
> On Fri, Oct 19, 2018 at 06:17:51PM +0200, Vincent Guittot wrote:
> > In order to achieve this time scaling, a new clock_pelt is created per rq.
>
>
> > diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
> > index 3990818..d987f50
On Tue, 23 Oct 2018 at 12:01, Peter Zijlstra wrote:
>
> On Fri, Oct 19, 2018 at 06:17:51PM +0200, Vincent Guittot wrote:
> > In order to achieve this time scaling, a new clock_pelt is created per rq.
>
>
> > diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
> > index 3990818..d987f50
On (10/23/18 21:04), Sergey Senozhatsky wrote:
>
> Seems that s390 is the only arch which defines its own bust_spinlocks().
> Not sure why... Just to play games with console_loglevel?
>
> ---
>
> void bust_spinlocks(int yes)
> {
> if (yes) {
> oops_in_progress = 1;
> }
On (10/23/18 21:04), Sergey Senozhatsky wrote:
>
> Seems that s390 is the only arch which defines its own bust_spinlocks().
> Not sure why... Just to play games with console_loglevel?
>
> ---
>
> void bust_spinlocks(int yes)
> {
> if (yes) {
> oops_in_progress = 1;
> }
On 10/17/2018 3:58 AM, Evan Green wrote:
On Mon, Oct 8, 2018 at 6:26 AM Veerabhadrarao Badiganti
wrote:
On few SDHCI-MSM controllers, the host controller's clock tuning
circuit may go out of sync if controller clocks are gated which
eventually will result in data CRC, command CRC/timeout
Linus,
Please pull the latest x86-paravirt-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-paravirt-for-linus
# HEAD: 3a025de64bf89c84a79909069e3c24ad9e710d27 x86/hyperv: Enable PV
qspinlock for Hyper-V
Two main changes:
- Remove no longer parts
On 10/17/2018 3:58 AM, Evan Green wrote:
On Mon, Oct 8, 2018 at 6:26 AM Veerabhadrarao Badiganti
wrote:
On few SDHCI-MSM controllers, the host controller's clock tuning
circuit may go out of sync if controller clocks are gated which
eventually will result in data CRC, command CRC/timeout
Linus,
Please pull the latest x86-paravirt-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-paravirt-for-linus
# HEAD: 3a025de64bf89c84a79909069e3c24ad9e710d27 x86/hyperv: Enable PV
qspinlock for Hyper-V
Two main changes:
- Remove no longer parts
Linus,
Please pull the latest x86-mm-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-mm-for-linus
# HEAD: 977e4be5eb714c48a67afc26a6c477f24130a1f2 x86/stackprotector: Remove
the call to boot_init_stack_canary() from cpu_startup_entry()
Lots of
Linus,
Please pull the latest x86-mm-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-mm-for-linus
# HEAD: 977e4be5eb714c48a67afc26a6c477f24130a1f2 x86/stackprotector: Remove
the call to boot_init_stack_canary() from cpu_startup_entry()
Lots of
On (10/23/18 20:54), Sergey Senozhatsky wrote:
> So I did look at what lib/bust_spinlocks.c does; and I agree that waking
> up klogd makes little sense, on the other hand it just sets per-cpu
> pending bit, so not a big deal. console_unlock() should do there the
> same thing as
On (10/23/18 20:54), Sergey Senozhatsky wrote:
> So I did look at what lib/bust_spinlocks.c does; and I agree that waking
> up klogd makes little sense, on the other hand it just sets per-cpu
> pending bit, so not a big deal. console_unlock() should do there the
> same thing as
On (10/23/18 13:07), Petr Mladek wrote:
> Though this looks a bit weird.
>
> I have just realized that console_unblank() is called by
> bust_spinlocks(0) and does basically the same as
> console_flush_on_panic(). Also it does not make much
> sense wake_up_klogd() there. Finally, it seems to be
>
On (10/23/18 13:07), Petr Mladek wrote:
> Though this looks a bit weird.
>
> I have just realized that console_unblank() is called by
> bust_spinlocks(0) and does basically the same as
> console_flush_on_panic(). Also it does not make much
> sense wake_up_klogd() there. Finally, it seems to be
>
On 22 October 2018 at 20:06, Edgecombe, Rick P
wrote:
> On Sat, 2018-10-20 at 19:20 +0200, Ard Biesheuvel wrote:
>> Hi Rick,
>>
>> On 19 October 2018 at 22:47, Rick Edgecombe
>> wrote:
>> > If BPF JIT is on, there is no effective limit to prevent filling the entire
>> > module space with JITed
On 22 October 2018 at 20:06, Edgecombe, Rick P
wrote:
> On Sat, 2018-10-20 at 19:20 +0200, Ard Biesheuvel wrote:
>> Hi Rick,
>>
>> On 19 October 2018 at 22:47, Rick Edgecombe
>> wrote:
>> > If BPF JIT is on, there is no effective limit to prevent filling the entire
>> > module space with JITed
Hi Taniya,
Both the patches are missing v9 in their subject line - this threw off
patchwork when trying to download the patches.
On Thu, Oct 11, 2018 at 5:06 PM Taniya Das wrote:
>
> Add QCOM cpufreq firmware device bindings for Qualcomm Technology Inc's
> SoCs. This is required for managing
Hi Taniya,
Both the patches are missing v9 in their subject line - this threw off
patchwork when trying to download the patches.
On Thu, Oct 11, 2018 at 5:06 PM Taniya Das wrote:
>
> Add QCOM cpufreq firmware device bindings for Qualcomm Technology Inc's
> SoCs. This is required for managing
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
to receive merge window updates for HID subsystem. Highlights:
=
- rumble support for Xbox One S, from Andrey Smirnov
- high-resolution support for Logitech mice, from Harry Cutts
- support for
Linus,
please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus
to receive merge window updates for HID subsystem. Highlights:
=
- rumble support for Xbox One S, from Andrey Smirnov
- high-resolution support for Logitech mice, from Harry Cutts
- support for
Good day,
I am Mr. Aziz Dake, from Burkina Faso a Minister confide on me to
look for foreign partner who will assist him to invest the sum of
Thirty Million Dollars ($30,000,000) in your country.
He has investment interest in mining, exotic properties for commercial
resident, development
Good day,
I am Mr. Aziz Dake, from Burkina Faso a Minister confide on me to
look for foreign partner who will assist him to invest the sum of
Thirty Million Dollars ($30,000,000) in your country.
He has investment interest in mining, exotic properties for commercial
resident, development
Linus,
Please pull the latest x86-grub2-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-grub2-for-linus
# HEAD: e7b66d16fe41722350ba87f5788052ef53ee28bb x86/acpi, x86/boot: Take
RSDP address for boot params if available
This tree extends the x86
Linus,
Please pull the latest x86-grub2-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-grub2-for-linus
# HEAD: e7b66d16fe41722350ba87f5788052ef53ee28bb x86/acpi, x86/boot: Take
RSDP address for boot params if available
This tree extends the x86
Hi Arnaldo,
On 09.10.2018 22:32, Arnaldo Carvalho de Melo wrote:
> Em Tue, Oct 09, 2018 at 05:36:24PM +0300, Alexey Budankov escreveu:
>>
>> Store -k clockid frequency into Perf trace to enable timestamps
>> derived metrics conversion into wall clock time on reporting stage.
>>
>> Below is the
On Tue 23-10-18 10:01:08, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > On Mon 22-10-18 20:45:17, Tetsuo Handa wrote:
> > > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > > > index e79cb59552d9..a9dfed29967b 100644
> > > > --- a/mm/memcontrol.c
> > > > +++ b/mm/memcontrol.c
> > > > @@
Hi Arnaldo,
On 09.10.2018 22:32, Arnaldo Carvalho de Melo wrote:
> Em Tue, Oct 09, 2018 at 05:36:24PM +0300, Alexey Budankov escreveu:
>>
>> Store -k clockid frequency into Perf trace to enable timestamps
>> derived metrics conversion into wall clock time on reporting stage.
>>
>> Below is the
On Tue 23-10-18 10:01:08, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > On Mon 22-10-18 20:45:17, Tetsuo Handa wrote:
> > > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > > > index e79cb59552d9..a9dfed29967b 100644
> > > > --- a/mm/memcontrol.c
> > > > +++ b/mm/memcontrol.c
> > > > @@
On Tue, Oct 23, 2018 at 5:08 PM Luis Henriques wrote:
>
> If we try to copy into a file that was just written, any data that is remote
> copied will be overwritten by our buffered writes once they are flushed. When
> this happens, the call to invalidate_inode_pages2_range will also return a
>
On Tue, Oct 23, 2018 at 5:08 PM Luis Henriques wrote:
>
> If we try to copy into a file that was just written, any data that is remote
> copied will be overwritten by our buffered writes once they are flushed. When
> this happens, the call to invalidate_inode_pages2_range will also return a
>
Linus,
Please pull the latest x86-cpu-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-cpu-for-linus
# HEAD: 995d5f64b62f20f05b8e0972f07ec4d6c2c9 tools/cpupower: Add Hygon
Dhyana support
The main changes in this cycle were:
- Add support for
Linus,
Please pull the latest x86-cpu-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-cpu-for-linus
# HEAD: 995d5f64b62f20f05b8e0972f07ec4d6c2c9 tools/cpupower: Add Hygon
Dhyana support
The main changes in this cycle were:
- Add support for
701 - 800 of 1128 matches
Mail list logo
