Dunlap
> Cc: Jassi Brar
> Cc:
> Cc: CK Hu
> Cc: Houlong Wei
> ---
> drivers/mailbox/mtk-cmdq-mailbox.c |2 ++
> 1 file changed, 2 insertions(+)
>
> --- linux-next-20180807.orig/drivers/mailbox/mtk-cmdq-mailbox.c
> +++ linux-next-20180807/drivers/mailbox/mtk-c
Dunlap
> Cc: Jassi Brar
> Cc:
> Cc: CK Hu
> Cc: Houlong Wei
> ---
> drivers/mailbox/mtk-cmdq-mailbox.c |2 ++
> 1 file changed, 2 insertions(+)
>
> --- linux-next-20180807.orig/drivers/mailbox/mtk-cmdq-mailbox.c
> +++ linux-next-20180807/drivers/mailbox/mtk-c
changed, 2 insertions(+)
--- linux-next-20180807.orig/drivers/mailbox/mtk-cmdq-mailbox.c
+++ linux-next-20180807/drivers/mailbox/mtk-cmdq-mailbox.c
@@ -567,3 +567,5 @@ static void __exit cmdq_drv_exit(void)
subsys_initcall(cmdq_drv_init);
module_exit(cmdq_drv_exit);
+
+MODULE_LICENSE("GPL v2");
changed, 2 insertions(+)
--- linux-next-20180807.orig/drivers/mailbox/mtk-cmdq-mailbox.c
+++ linux-next-20180807/drivers/mailbox/mtk-cmdq-mailbox.c
@@ -567,3 +567,5 @@ static void __exit cmdq_drv_exit(void)
subsys_initcall(cmdq_drv_init);
module_exit(cmdq_drv_exit);
+
+MODULE_LICENSE("GPL v2");
Ard, Mikulas,
pon., 6 sie 2018 o 22:11 Ard Biesheuvel napisał(a):
>
> On 6 August 2018 at 21:54, Mikulas Patocka wrote:
> >
> >
> > On Mon, 6 Aug 2018, Ard Biesheuvel wrote:
> >
> >> On 6 August 2018 at 19:09, Mikulas Patocka wrote:
> >> >
> >> >
> >> > On Mon, 6 Aug 2018, Ard Biesheuvel
On Wed, Aug 01, 2018 at 05:57:41PM -0700, Saravana Kannan wrote:
> Many CPU architectures have caches that can scale independent of the CPUs.
> Frequency scaling of the caches is necessary to make sure the cache is not
> a performance bottleneck that leads to poor performance and power. The same
>
Ard, Mikulas,
pon., 6 sie 2018 o 22:11 Ard Biesheuvel napisał(a):
>
> On 6 August 2018 at 21:54, Mikulas Patocka wrote:
> >
> >
> > On Mon, 6 Aug 2018, Ard Biesheuvel wrote:
> >
> >> On 6 August 2018 at 19:09, Mikulas Patocka wrote:
> >> >
> >> >
> >> > On Mon, 6 Aug 2018, Ard Biesheuvel
On Wed, Aug 01, 2018 at 05:57:41PM -0700, Saravana Kannan wrote:
> Many CPU architectures have caches that can scale independent of the CPUs.
> Frequency scaling of the caches is necessary to make sure the cache is not
> a performance bottleneck that leads to poor performance and power. The same
>
On Tue, Aug 7, 2018 at 9:22 AM Matthias Kaehlcke wrote:
>
> The initializer of rt5677_of_match contains a bogus device id
> (enum type) for the 'type' field (char []). Remove it.
>
> Signed-off-by: Matthias Kaehlcke
> ---
> sound/soc/codecs/rt5677.c | 2 +-
> 1 file changed, 1 insertion(+), 1
On Tue, Aug 7, 2018 at 9:22 AM Matthias Kaehlcke wrote:
>
> The initializer of rt5677_of_match contains a bogus device id
> (enum type) for the 'type' field (char []). Remove it.
>
> Signed-off-by: Matthias Kaehlcke
> ---
> sound/soc/codecs/rt5677.c | 2 +-
> 1 file changed, 1 insertion(+), 1
The initializer of rt5677_of_match contains a bogus device id
(enum type) for the 'type' field (char []). Remove it.
Signed-off-by: Matthias Kaehlcke
---
sound/soc/codecs/rt5677.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/codecs/rt5677.c
The initializer of rt5677_of_match contains a bogus device id
(enum type) for the 'type' field (char []). Remove it.
Signed-off-by: Matthias Kaehlcke
---
sound/soc/codecs/rt5677.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/soc/codecs/rt5677.c
Replace GPL v2.0+ license statements with SPDX license identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/extcon/extcon-max14577.c | 24 +++-
drivers/extcon/extcon-max77693.c | 22 ++
drivers/extcon/extcon-max77843.c | 19 +++
Replace GPL v2.0+ license statements with SPDX license identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/extcon/extcon-max14577.c | 24 +++-
drivers/extcon/extcon-max77693.c | 22 ++
drivers/extcon/extcon-max77843.c | 19 +++
Replace GPL v2.0 and v2.0+ license statements with SPDX license
identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/power/supply/max14577_charger.c | 22 ++
drivers/power/supply/max17040_battery.c | 18 +++---
drivers/power/supply/max17042_battery.c | 32
Replace GPL v2.0 and v2.0+ license statements with SPDX license
identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/power/supply/max14577_charger.c | 22 ++
drivers/power/supply/max17040_battery.c | 18 +++---
drivers/power/supply/max17042_battery.c | 32
Replace GPL v2.0+ license statements with SPDX license
identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/rtc/rtc-max77686.c | 20 +++-
drivers/rtc/rtc-max8997.c | 20 +++-
drivers/rtc/rtc-max8998.c | 20 +++-
3 files changed, 21
Replace GPL v2.0+ license statement with SPDX license
identifier.
Signed-off-by: Krzysztof Kozlowski
---
drivers/rtc/rtc-s5m.c | 22 ++
1 file changed, 6 insertions(+), 16 deletions(-)
diff --git a/drivers/rtc/rtc-s5m.c b/drivers/rtc/rtc-s5m.c
index
Replace GPL v2.0+ license statements with SPDX license
identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/rtc/rtc-max77686.c | 20 +++-
drivers/rtc/rtc-max8997.c | 20 +++-
drivers/rtc/rtc-max8998.c | 20 +++-
3 files changed, 21
Replace GPL v2.0+ license statement with SPDX license
identifier.
Signed-off-by: Krzysztof Kozlowski
---
drivers/rtc/rtc-s5m.c | 22 ++
1 file changed, 6 insertions(+), 16 deletions(-)
diff --git a/drivers/rtc/rtc-s5m.c b/drivers/rtc/rtc-s5m.c
index
Replace GPL v2.0 and v2.0+ license statements with SPDX license
identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/regulator/max14577-regulator.c | 22 +
drivers/regulator/max77686-regulator.c | 32 +++-
Replace GPL v2.0 and v2.0+ license statements with SPDX license
identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/regulator/max14577-regulator.c | 22 +
drivers/regulator/max77686-regulator.c | 32 +++-
Replace GPL v2.0+ license statements with SPDX license
identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/regulator/s2mpa01.c | 14 --
drivers/regulator/s2mps11.c | 21 -
drivers/regulator/s5m8767.c | 16
3 files changed, 12
Replace GPL v2.0+ license statements with SPDX license
identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/regulator/s2mpa01.c | 14 --
drivers/regulator/s2mps11.c | 21 -
drivers/regulator/s5m8767.c | 16
3 files changed, 12
Replace GPL v2.0 and v2.0+ license statements with SPDX license
identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/clk/clk-max77686.c | 27 ++-
include/dt-bindings/clock/maxim,max77686.h | 5 +
include/dt-bindings/clock/maxim,max77802.h | 5
The clock IDs must match between DeviceTree bindings and the driver.
There is already a header file used by DeviceTree sources so include it
in the driver to remove duplicated symbols.
Signed-off-by: Krzysztof Kozlowski
---
drivers/clk/clk-s2mps11.c | 7 +--
1 file changed, 1 insertion(+),
Replace GPL v2.0 and v2.0+ license statements with SPDX license
identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/clk/clk-max77686.c | 27 ++-
include/dt-bindings/clock/maxim,max77686.h | 5 +
include/dt-bindings/clock/maxim,max77802.h | 5
The clock IDs must match between DeviceTree bindings and the driver.
There is already a header file used by DeviceTree sources so include it
in the driver to remove duplicated symbols.
Signed-off-by: Krzysztof Kozlowski
---
drivers/clk/clk-s2mps11.c | 7 +--
1 file changed, 1 insertion(+),
Replace GPL v2.0 and v2.0+ license statements with SPDX license
identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/clk/clk-s2mps11.c | 21 +
include/dt-bindings/clock/samsung,s2mps11.h | 5 +
Replace GPL v2.0 and v2.0+ license statements with SPDX license
identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/clk/clk-s2mps11.c | 21 +
include/dt-bindings/clock/samsung,s2mps11.h | 5 +
Replace GPL v2.0+ license statements with SPDX license identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/mfd/max14577.c | 28 +---
drivers/mfd/max77686.c | 32 +---
drivers/mfd/max77693.c |
Replace GPL v2.0+ license statements with SPDX license identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/mfd/max14577.c | 28 +---
drivers/mfd/max77686.c | 32 +---
drivers/mfd/max77693.c |
The main MFD driver for Samsung PMICs (S2MPSXX, S5M876X) used with
Exynos SoCs can be compiled and used as a module. The dependent clock,
regulator and RTC drivers already can be built as a module.
Building entire set of drivers as modules might require using initial
ramdisk and can make booting
Replace GPL v2.0+ license statements with SPDX license identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/mfd/sec-core.c | 16
drivers/mfd/sec-irq.c | 16
include/linux/mfd/samsung/core.h| 11 ++-
The indentation should be a tab followed by two spaces.
Signed-off-by: Krzysztof Kozlowski
---
drivers/mfd/Kconfig | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
index f3fa516011ec..5810e6ff81f7 100644
---
The main MFD driver for Samsung PMICs (S2MPSXX, S5M876X) used with
Exynos SoCs can be compiled and used as a module. The dependent clock,
regulator and RTC drivers already can be built as a module.
Building entire set of drivers as modules might require using initial
ramdisk and can make booting
Replace GPL v2.0+ license statements with SPDX license identifiers.
Signed-off-by: Krzysztof Kozlowski
---
drivers/mfd/sec-core.c | 16
drivers/mfd/sec-irq.c | 16
include/linux/mfd/samsung/core.h| 11 ++-
The indentation should be a tab followed by two spaces.
Signed-off-by: Krzysztof Kozlowski
---
drivers/mfd/Kconfig | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig
index f3fa516011ec..5810e6ff81f7 100644
---
Introduce the lm3697 LED driver for
backlighting and display.
Datasheet location:
http://www.ti.com/lit/ds/symlink/lm3697.pdf
Signed-off-by: Dan Murphy
---
v2 - Removed unneed 'of' calls in dt_parse, fixed comment, fixed checkpatch
error, and change led registration -
Introduce the lm3697 LED driver for
backlighting and display.
Datasheet location:
http://www.ti.com/lit/ds/symlink/lm3697.pdf
Signed-off-by: Dan Murphy
---
v2 - Removed unneed 'of' calls in dt_parse, fixed comment, fixed checkpatch
error, and change led registration -
Add the device tree bindings for the lm3697
led driver for backlighting and display.
Signed-off-by: Dan Murphy
---
v2 - Fixed subject and patch commit message -
https://lore.kernel.org/patchwork/patch/971326/
.../devicetree/bindings/leds/leds-lm3697.txt | 64 +++
1 file
Add the device tree bindings for the lm3697
led driver for backlighting and display.
Signed-off-by: Dan Murphy
---
v2 - Fixed subject and patch commit message -
https://lore.kernel.org/patchwork/patch/971326/
.../devicetree/bindings/leds/leds-lm3697.txt | 64 +++
1 file
On Tue, 7 Aug 2018 09:25:55 +0200 Christoph Hellwig wrote:
> On Mon, Aug 06, 2018 at 03:27:05PM -0700, Andrew Morton wrote:
> > On Mon, 6 Aug 2018 10:30:58 +0200 Christoph Hellwig wrote:
> >
> > > If we get a keyed wakeup for a aio poll waitqueue and wake can acquire the
> > > ctx_lock
On Tue, 7 Aug 2018 09:25:55 +0200 Christoph Hellwig wrote:
> On Mon, Aug 06, 2018 at 03:27:05PM -0700, Andrew Morton wrote:
> > On Mon, 6 Aug 2018 10:30:58 +0200 Christoph Hellwig wrote:
> >
> > > If we get a keyed wakeup for a aio poll waitqueue and wake can acquire the
> > > ctx_lock
newly idle load balance is not always triggered when a cpu becomes idle.
This prevent the scheduler to get a chance to migrate task for asym packing.
Enable active migration because of asym packing during idle load balance too.
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 2 +-
1
newly idle load balance is not always triggered when a cpu becomes idle.
This prevent the scheduler to get a chance to migrate task for asym packing.
Enable active migration because of asym packing during idle load balance too.
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 2 +-
1
On 07/08/18 16:14, Roger Pau Monné wrote:
> On Tue, Aug 07, 2018 at 08:31:31AM +0200, Juergen Gross wrote:
>> On 06/08/18 18:16, Roger Pau Monné wrote:
>>> On Mon, Aug 06, 2018 at 01:34:01PM +0200, Juergen Gross wrote:
Add a periodic cleanup function to remove old persistent grants which
When check_asym_packing() is triggered, the imbalance is set to :
busiest_stat.avg_load * busiest_stat.group_capacity / SCHED_CAPACITY_SCALE
busiest_stat.avg_load also comes from a division and the final rounding
can make imbalance slightly lower than the weighted load of the cfs_rq.
But this is
In case of active balance, we increase the balance interval to cover
pinned tasks cases not covered by all_pinned logic. Neverthless, the active
migration triggered by asym packing should be treated as the normal
unbalanced case and reset the interval to default value otherwise active
migration
When check_asym_packing() is triggered, the imbalance is set to :
busiest_stat.avg_load * busiest_stat.group_capacity / SCHED_CAPACITY_SCALE
busiest_stat.avg_load also comes from a division and the final rounding
can make imbalance slightly lower than the weighted load of the cfs_rq.
But this is
In case of active balance, we increase the balance interval to cover
pinned tasks cases not covered by all_pinned logic. Neverthless, the active
migration triggered by asym packing should be treated as the normal
unbalanced case and reset the interval to default value otherwise active
migration
On 07/08/18 16:14, Roger Pau Monné wrote:
> On Tue, Aug 07, 2018 at 08:31:31AM +0200, Juergen Gross wrote:
>> On 06/08/18 18:16, Roger Pau Monné wrote:
>>> On Mon, Aug 06, 2018 at 01:34:01PM +0200, Juergen Gross wrote:
Add a periodic cleanup function to remove old persistent grants which
During the review of misfit task patchset, Morten and Valentin raised some
problems with the use of SD_ASYM_PACKING flag on asymetric system like
hikey960 arm64 big/LITTLE platform. The study of the use cases has shown
some problems that can happen for every systems that use the flag.
The 3
During the review of misfit task patchset, Morten and Valentin raised some
problems with the use of SD_ASYM_PACKING flag on asymetric system like
hikey960 arm64 big/LITTLE platform. The study of the use cases has shown
some problems that can happen for every systems that use the flag.
The 3
Hi Sean,
this is even more hackish since the __hci_cmd_sync_ev command is really
meant to get a cmd status first before waiting for that event.
>>>
>>> Understood.
>>>
>>> I've stopped the hack in v8. could we merge v8 first ? and then I will a
>>> fix up with
Hi Sean,
this is even more hackish since the __hci_cmd_sync_ev command is really
meant to get a cmd status first before waiting for that event.
>>>
>>> Understood.
>>>
>>> I've stopped the hack in v8. could we merge v8 first ? and then I will a
>>> fix up with
On Sat, Aug 04, 2018 at 06:08:17PM -0700, Guenter Roeck wrote:
> On 08/02/2018 02:15 PM, Jerry Hoemann wrote:
> > When the pretimeout is specified as a module parameter, the
> > value should be reflected in hpwdt_dev.pretimeout. The default
> > (on) case is correct. But, when disabling
On Sat, Aug 04, 2018 at 06:08:17PM -0700, Guenter Roeck wrote:
> On 08/02/2018 02:15 PM, Jerry Hoemann wrote:
> > When the pretimeout is specified as a module parameter, the
> > value should be reflected in hpwdt_dev.pretimeout. The default
> > (on) case is correct. But, when disabling
Previous patches made all the data, which is touched from
super_cache_count(), destroyed from destroy_super_work():
s_dentry_lru, s_inode_lru and super_block::s_fs_info.
super_cache_scan() can't be called after SB_ACTIVE is cleared
in generic_shutdown_super().
So, it safe to move heavy
Similar to xfs_fs_destroy_super() implement the method
for shmem.
shmem_unused_huge_count() just touches sb->s_fs_info.
After such the later freeing it will be safe for
unregister_shrinker() splitting (which is made in next
patch).
Signed-off-by: Kirill Tkhai
---
mm/shmem.c |8
1
Previous patches made all the data, which is touched from
super_cache_count(), destroyed from destroy_super_work():
s_dentry_lru, s_inode_lru and super_block::s_fs_info.
super_cache_scan() can't be called after SB_ACTIVE is cleared
in generic_shutdown_super().
So, it safe to move heavy
Similar to xfs_fs_destroy_super() implement the method
for shmem.
shmem_unused_huge_count() just touches sb->s_fs_info.
After such the later freeing it will be safe for
unregister_shrinker() splitting (which is made in next
patch).
Signed-off-by: Kirill Tkhai
---
mm/shmem.c |8
1
xfs_fs_nr_cached_objects() touches sb->s_fs_info,
and this patch makes it to be destructed later.
After this patch xfs_fs_nr_cached_objects() is safe
for splitting unregister_shrinker(): mp->m_perag_tree
is stable till destroy_super_work(), while iteration
over it is already RCU-protected by
xfs_fs_nr_cached_objects() touches sb->s_fs_info,
and this patch makes it to be destructed later.
After this patch xfs_fs_nr_cached_objects() is safe
for splitting unregister_shrinker(): mp->m_perag_tree
is stable till destroy_super_work(), while iteration
over it is already RCU-protected by
The patch introduces a new callback, which will be called
asynchronous from delayed work.
This will allows to make ::nr_cached_objects() safe
to be called on destroying superblock in next patches,
and to split unregister_shrinker() into two primitives.
Signed-off-by: Kirill Tkhai
---
The patch introduces a new callback, which will be called
asynchronous from delayed work.
This will allows to make ::nr_cached_objects() safe
to be called on destroying superblock in next patches,
and to split unregister_shrinker() into two primitives.
Signed-off-by: Kirill Tkhai
---
This patch prepares superblock shrinker for delayed unregistering.
It makes super_cache_scan() avoid shrinking of not active superblocks.
SB_ACTIVE is used as such the indicator. In case of superblock is not
active, super_cache_scan() just exits with SHRINK_STOP as result.
Note, that SB_ACTIVE is
The patch makes s_dentry_lru and s_inode_lru be destroyed
later from the workqueue. This is preparation to split
unregister_shrinker(super_block::s_shrink) in two stages,
and to call finalize stage from destroy_super_work().
Note, that generic filesystem shrinker unregistration
is safe to be
This patch prepares superblock shrinker for delayed unregistering.
It makes super_cache_scan() avoid shrinking of not active superblocks.
SB_ACTIVE is used as such the indicator. In case of superblock is not
active, super_cache_scan() just exits with SHRINK_STOP as result.
Note, that SB_ACTIVE is
The patch makes s_dentry_lru and s_inode_lru be destroyed
later from the workqueue. This is preparation to split
unregister_shrinker(super_block::s_shrink) in two stages,
and to call finalize stage from destroy_super_work().
Note, that generic filesystem shrinker unregistration
is safe to be
There are no readers, so rwsem is not need anymore.
Signed-off-by: Kirill Tkhai
---
mm/vmscan.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/mm/vmscan.c b/mm/vmscan.c
index 9dda903a1406..2dc274a385b9 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@
This and the next patches in this series aim to make
time effect of synchronize_srcu() invisible for user.
The patch splits unregister_shrinker() in two functions:
unregister_shrinker_delayed_initiate()
unregister_shrinker_delayed_finalize()
and shrinker users may make the second
This and the next patches in this series aim to make
time effect of synchronize_srcu() invisible for user.
The patch splits unregister_shrinker() in two functions:
unregister_shrinker_delayed_initiate()
unregister_shrinker_delayed_finalize()
and shrinker users may make the second
There are no readers, so rwsem is not need anymore.
Signed-off-by: Kirill Tkhai
---
mm/vmscan.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/mm/vmscan.c b/mm/vmscan.c
index 9dda903a1406..2dc274a385b9 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@
The patch makes shrinker list and shrinker_idr SRCU-safe
for readers. This requires synchronize_srcu() on finalize
stage unregistering stage, which waits till all parallel
shrink_slab() are finished
Note, that patch removes rwsem_is_contended() checks from
the code, and this does not result in
The patch makes shrinker list and shrinker_idr SRCU-safe
for readers. This requires synchronize_srcu() on finalize
stage unregistering stage, which waits till all parallel
shrink_slab() are finished
Note, that patch removes rwsem_is_contended() checks from
the code, and this does not result in
This patch kills all CONFIG_SRCU defines and
the code under !CONFIG_SRCU.
Signed-off-by: Kirill Tkhai
---
drivers/base/core.c| 42
include/linux/device.h |2 -
include/linux/rcutiny.h
This patch kills all CONFIG_SRCU defines and
the code under !CONFIG_SRCU.
Signed-off-by: Kirill Tkhai
---
drivers/base/core.c| 42
include/linux/device.h |2 -
include/linux/rcutiny.h
After bitmaps of not-empty memcg shrinkers were implemented
(see "[PATCH v9 00/17] Improve shrink_slab() scalability..."
series, which is already in mm tree), all the evil in perf
trace has moved from shrink_slab() to down_read_trylock().
As reported by Shakeel Butt:
> I created 255 memcgs,
After bitmaps of not-empty memcg shrinkers were implemented
(see "[PATCH v9 00/17] Improve shrink_slab() scalability..."
series, which is already in mm tree), all the evil in perf
trace has moved from shrink_slab() to down_read_trylock().
As reported by Shakeel Butt:
> I created 255 memcgs,
On Tue, Aug 07, 2018 at 08:26:44AM -0700, Darrick J. Wong wrote:
> On Tue, Aug 07, 2018 at 11:18:36AM -0400, Brian Foster wrote:
> > On Tue, Aug 07, 2018 at 08:10:29AM -0700, Darrick J. Wong wrote:
> > > On Tue, Aug 07, 2018 at 10:37:21AM -0400, Brian Foster wrote:
> > > > On Tue, Aug 07, 2018 at
On Tue, Aug 07, 2018 at 08:26:44AM -0700, Darrick J. Wong wrote:
> On Tue, Aug 07, 2018 at 11:18:36AM -0400, Brian Foster wrote:
> > On Tue, Aug 07, 2018 at 08:10:29AM -0700, Darrick J. Wong wrote:
> > > On Tue, Aug 07, 2018 at 10:37:21AM -0400, Brian Foster wrote:
> > > > On Tue, Aug 07, 2018 at
On 8/6/2018 2:39 PM, Peter Zijlstra wrote:
On Mon, Aug 06, 2018 at 10:23:43AM -0700, kan.li...@linux.intel.com wrote:
+static bool intel_glk_counter_freezing_broken(int cpu)
case INTEL_FAM6_ATOM_GEMINI_LAKE:
+ x86_add_quirk(intel_counter_freezing_quirk);
We really
On 8/6/2018 2:39 PM, Peter Zijlstra wrote:
On Mon, Aug 06, 2018 at 10:23:43AM -0700, kan.li...@linux.intel.com wrote:
+static bool intel_glk_counter_freezing_broken(int cpu)
case INTEL_FAM6_ATOM_GEMINI_LAKE:
+ x86_add_quirk(intel_counter_freezing_quirk);
We really
On 8/6/2018 2:35 PM, Peter Zijlstra wrote:
On Mon, Aug 06, 2018 at 10:23:42AM -0700, kan.li...@linux.intel.com wrote:
@@ -2044,6 +2056,14 @@ static void intel_pmu_disable_event(struct perf_event
*event)
if (unlikely(event->attr.precise_ip))
On 8/6/2018 2:35 PM, Peter Zijlstra wrote:
On Mon, Aug 06, 2018 at 10:23:42AM -0700, kan.li...@linux.intel.com wrote:
@@ -2044,6 +2056,14 @@ static void intel_pmu_disable_event(struct perf_event
*event)
if (unlikely(event->attr.precise_ip))
On 8/6/2018 2:20 PM, Peter Zijlstra wrote:
On Mon, Aug 06, 2018 at 10:23:41AM -0700, kan.li...@linux.intel.com wrote:
+ if (++loops > 100) {
+ static bool warned;
+
+ if (!warned) {
+ WARN(1, "perfevents: irq loop stuck!\n");
+
On 8/6/2018 2:20 PM, Peter Zijlstra wrote:
On Mon, Aug 06, 2018 at 10:23:41AM -0700, kan.li...@linux.intel.com wrote:
+ if (++loops > 100) {
+ static bool warned;
+
+ if (!warned) {
+ WARN(1, "perfevents: irq loop stuck!\n");
+
On 07.08.2018 17:19, Jerome Glisse wrote:
> On Tue, Aug 07, 2018 at 04:54:57PM +0200, David Hildenbrand wrote:
>> On 07.08.2018 15:52, Jerome Glisse wrote:
>>> On Tue, Aug 07, 2018 at 03:37:56PM +0200, osalva...@techadventures.net
>>> wrote:
From: Oscar Salvador
>>>
>>> [...]
>>>
diff
On 07.08.2018 17:19, Jerome Glisse wrote:
> On Tue, Aug 07, 2018 at 04:54:57PM +0200, David Hildenbrand wrote:
>> On 07.08.2018 15:52, Jerome Glisse wrote:
>>> On Tue, Aug 07, 2018 at 03:37:56PM +0200, osalva...@techadventures.net
>>> wrote:
From: Oscar Salvador
>>>
>>> [...]
>>>
diff
On Tue, Aug 07, 2018 at 11:18:36AM -0400, Brian Foster wrote:
> On Tue, Aug 07, 2018 at 08:10:29AM -0700, Darrick J. Wong wrote:
> > On Tue, Aug 07, 2018 at 10:37:21AM -0400, Brian Foster wrote:
> > > On Tue, Aug 07, 2018 at 03:14:07PM +0100, Colin Ian King wrote:
> > > > Hi,
> > > >
> > > >
On Tue, Aug 07, 2018 at 11:18:36AM -0400, Brian Foster wrote:
> On Tue, Aug 07, 2018 at 08:10:29AM -0700, Darrick J. Wong wrote:
> > On Tue, Aug 07, 2018 at 10:37:21AM -0400, Brian Foster wrote:
> > > On Tue, Aug 07, 2018 at 03:14:07PM +0100, Colin Ian King wrote:
> > > > Hi,
> > > >
> > > >
On August 7, 2018 11:09:06 AM EDT, Steven Rostedt wrote:
>On Tue, 07 Aug 2018 10:48:05 -0400
>Joel Fernandes wrote:
>
>> >You mean if someone add a tracepoint callback to the irq disable
>> >tracepoint, and did a lockdep assert to make sure interrupts are
>> >disabled?
>>
>> Yes that's
On August 7, 2018 11:09:06 AM EDT, Steven Rostedt wrote:
>On Tue, 07 Aug 2018 10:48:05 -0400
>Joel Fernandes wrote:
>
>> >You mean if someone add a tracepoint callback to the irq disable
>> >tracepoint, and did a lockdep assert to make sure interrupts are
>> >disabled?
>>
>> Yes that's
Hi Tejun,
On Tue, Aug 07, 2018 at 08:11:46AM -0700, Tejun Heo wrote:
> Hello,
>
> On Tue, Aug 07, 2018 at 02:12:06PM +, Christopher Lameter wrote:
> > > @@ -121,6 +122,7 @@ static int meminfo_proc_show(struct seq_file *m, void
> > > *v)
> > > (unsigned long)VMALLOC_TOTAL >>
Hi Tejun,
On Tue, Aug 07, 2018 at 08:11:46AM -0700, Tejun Heo wrote:
> Hello,
>
> On Tue, Aug 07, 2018 at 02:12:06PM +, Christopher Lameter wrote:
> > > @@ -121,6 +122,7 @@ static int meminfo_proc_show(struct seq_file *m, void
> > > *v)
> > > (unsigned long)VMALLOC_TOTAL >>
Hi Christopher,
On Tue, Aug 07, 2018 at 02:12:06PM +, Christopher Lameter wrote:
> On Mon, 6 Aug 2018, Dennis Zhou wrote:
> > show_val_kb(m, "VmallocUsed:", 0ul);
> > show_val_kb(m, "VmallocChunk: ", 0ul);
> > + show_val_kb(m, "PercpuPopulated:", pcpu_nr_populated_pages());
>
Hi Christopher,
On Tue, Aug 07, 2018 at 02:12:06PM +, Christopher Lameter wrote:
> On Mon, 6 Aug 2018, Dennis Zhou wrote:
> > show_val_kb(m, "VmallocUsed:", 0ul);
> > show_val_kb(m, "VmallocChunk: ", 0ul);
> > + show_val_kb(m, "PercpuPopulated:", pcpu_nr_populated_pages());
>
On Tue, Aug 07, 2018 at 04:54:57PM +0200, David Hildenbrand wrote:
> On 07.08.2018 15:52, Jerome Glisse wrote:
> > On Tue, Aug 07, 2018 at 03:37:56PM +0200, osalva...@techadventures.net
> > wrote:
> >> From: Oscar Salvador
> >
> > [...]
> >
> >> diff --git a/mm/memory_hotplug.c
On Tue, Aug 07, 2018 at 04:54:57PM +0200, David Hildenbrand wrote:
> On 07.08.2018 15:52, Jerome Glisse wrote:
> > On Tue, Aug 07, 2018 at 03:37:56PM +0200, osalva...@techadventures.net
> > wrote:
> >> From: Oscar Salvador
> >
> > [...]
> >
> >> diff --git a/mm/memory_hotplug.c
801 - 900 of 1438 matches
Mail list logo
