Convert the driver to use the timer_of helpers.
This allows to remove custom proprietary structure,
factors out and simplifies the code.
Signed-off-by: Stanley Chu
---
drivers/clocksource/timer-mediatek.c | 205 +-
1 file changed, 80 insertions(+), 125
Convert the driver to use the timer_of helpers.
This allows to remove custom proprietary structure,
factors out and simplifies the code.
Signed-off-by: Stanley Chu
---
drivers/clocksource/timer-mediatek.c | 205 +-
1 file changed, 80 insertions(+), 125
Use specific prefix to specify the name of supported
timer hardware: "General Purpose Timer (GPT)".
Signed-off-by: Stanley Chu
---
drivers/clocksource/timer-mediatek.c | 157 +-
1 file changed, 80 insertions(+), 77 deletions(-)
diff --git
On Thu, Jun 28, 2018 at 4:30 PM Andy Lutomirski wrote:
>
> The idea is that, if someone screws up and sticks a number like
> 0xbaadf00d00045678 into their rseq abort_ip in a 32-bit x86 program
> (when they actually mean 0x00045678), we want to something consistent.
I think the "something
Use specific prefix to specify the name of supported
timer hardware: "General Purpose Timer (GPT)".
Signed-off-by: Stanley Chu
---
drivers/clocksource/timer-mediatek.c | 157 +-
1 file changed, 80 insertions(+), 77 deletions(-)
diff --git
On Thu, Jun 28, 2018 at 4:30 PM Andy Lutomirski wrote:
>
> The idea is that, if someone screws up and sticks a number like
> 0xbaadf00d00045678 into their rseq abort_ip in a 32-bit x86 program
> (when they actually mean 0x00045678), we want to something consistent.
I think the "something
Rename mtk_timer to timer-mediatek to apply new naming convention
in clocksource folder.
Signed-off-by: Stanley Chu
---
drivers/clocksource/Makefile |2 +-
drivers/clocksource/mtk_timer.c | 268 --
drivers/clocksource/timer-mediatek.c | 268
This patch fixes bindings of existed "General Purpose Timer",
and then add bindings of new "System Timer" on Mediatek SoCs.
Signed-off-by: Stanley Chu
---
.../bindings/timer/mediatek,mtk-timer.txt | 38
1 file changed, 32 insertions(+), 6 deletions(-)
diff --git
Rename mtk_timer to timer-mediatek to apply new naming convention
in clocksource folder.
Signed-off-by: Stanley Chu
---
drivers/clocksource/Makefile |2 +-
drivers/clocksource/mtk_timer.c | 268 --
drivers/clocksource/timer-mediatek.c | 268
This patch fixes bindings of existed "General Purpose Timer",
and then add bindings of new "System Timer" on Mediatek SoCs.
Signed-off-by: Stanley Chu
---
.../bindings/timer/mediatek,mtk-timer.txt | 38
1 file changed, 32 insertions(+), 6 deletions(-)
diff --git
This patch adds a new driver for system timer on the Mediatek SoCs.
Changes since v3:
- Use the same binding style for both GPT and System Timer.
- Use timer_of.of_clk->period instead of private structure.
- Arrange patches to contain system timer changes in patch 5/5 only.
Changes since v2:
-
This patch adds a new "System Timer" on the Mediatek SoCs.
The System Timer is introduced as an always-on timer being
clockevent device for tick-broadcasting.
For clock, it is driven by 13 MHz system clock.
The implementation uses the system clock with no clock
source divider.
For interrupt,
This patch adds a new driver for system timer on the Mediatek SoCs.
Changes since v3:
- Use the same binding style for both GPT and System Timer.
- Use timer_of.of_clk->period instead of private structure.
- Arrange patches to contain system timer changes in patch 5/5 only.
Changes since v2:
-
This patch adds a new "System Timer" on the Mediatek SoCs.
The System Timer is introduced as an always-on timer being
clockevent device for tick-broadcasting.
For clock, it is driven by 13 MHz system clock.
The implementation uses the system clock with no clock
source divider.
For interrupt,
On Thu, 2018-06-28 at 16:08 +0200, Daniel Lezcano wrote:
> On 28/06/2018 12:45, Stanley Chu wrote:
> > This patch adds a new "System Timer" on the Mediatek SoCs.
> >
> > The System Timer is introduced as an always-on timer being
> > clockevent device for tick-broadcasting.
> >
> > For clock, it
On Thu, 2018-06-28 at 16:08 +0200, Daniel Lezcano wrote:
> On 28/06/2018 12:45, Stanley Chu wrote:
> > This patch adds a new "System Timer" on the Mediatek SoCs.
> >
> > The System Timer is introduced as an always-on timer being
> > clockevent device for tick-broadcasting.
> >
> > For clock, it
On Thu, 2018-06-28 at 16:08 +0200, Daniel Lezcano wrote:
> > +** System Timer (SYST)
> > +
> > +Required properties:
> > +- compatible: Should contain
> > + * "mediatek,mt6765-systimer" for MT6765 compatible timers
> > +- reg: Should contain the location and length for system timer registers.
>
On Thu, 2018-06-28 at 16:08 +0200, Daniel Lezcano wrote:
> > +** System Timer (SYST)
> > +
> > +Required properties:
> > +- compatible: Should contain
> > + * "mediatek,mt6765-systimer" for MT6765 compatible timers
> > +- reg: Should contain the location and length for system timer registers.
>
On Thu, 2018-06-28 at 16:03 +0200, Daniel Lezcano wrote:
> >
> > -struct mtk_clock_event_device {
> > - void __iomem *gpt_base;
> > - u32 ticks_per_jiffy;
> > - struct clock_event_device dev;
> > +struct mtk_timer_private {
> > + unsigned long ticks_per_jiffy;
> > };
>
> This private
On Thu, 2018-06-28 at 16:03 +0200, Daniel Lezcano wrote:
> >
> > -struct mtk_clock_event_device {
> > - void __iomem *gpt_base;
> > - u32 ticks_per_jiffy;
> > - struct clock_event_device dev;
> > +struct mtk_timer_private {
> > + unsigned long ticks_per_jiffy;
> > };
>
> This private
Hi David,
On Thu, 28 Jun 2018 18:11:03 +0200 David Sterba wrote:
>
> On Wed, Jun 27, 2018 at 08:59:36AM +1000, Stephen Rothwell wrote:
> > After merging the btrfs-kdave tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > fs/btrfs/print-tree.c: In function
Hi David,
On Thu, 28 Jun 2018 18:11:03 +0200 David Sterba wrote:
>
> On Wed, Jun 27, 2018 at 08:59:36AM +1000, Stephen Rothwell wrote:
> > After merging the btrfs-kdave tree, today's linux-next build (powerpc
> > ppc64_defconfig) failed like this:
> >
> > fs/btrfs/print-tree.c: In function
Use GFP_ATOMIC rather GFP_KERNEL in interrupt handler,
as GFP_KERNEL may sleep according to slab allocator.
Signed-off-by: Karim Eshapa
---
drivers/staging/iio/adc/ad7280a.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/iio/adc/ad7280a.c
Use GFP_ATOMIC rather GFP_KERNEL in interrupt handler,
as GFP_KERNEL may sleep according to slab allocator.
Signed-off-by: Karim Eshapa
---
drivers/staging/iio/adc/ad7280a.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/iio/adc/ad7280a.c
Use GFP_ATOMIC rather GFP_KERNEL in interrupt handler,
as GFP_KERNEL may sleep according to slab allocator.
Signed-off-by: Karim Eshapa
---
drivers/staging/iio/adc/ad7280a.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/iio/adc/ad7280a.c
Use GFP_ATOMIC rather GFP_KERNEL in interrupt handler,
as GFP_KERNEL may sleep according to slab allocator.
Signed-off-by: Karim Eshapa
---
drivers/staging/iio/adc/ad7280a.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/iio/adc/ad7280a.c
Hi Guenter/Florian,
On 6/27/2018 11:55 AM, Guenter Roeck wrote:
On Wed, Jun 27, 2018 at 11:47:21AM -0700, Ray Jui wrote:
On 6/27/2018 11:42 AM, Guenter Roeck wrote:
On Wed, Jun 27, 2018 at 11:38:48AM -0700, Ray Jui wrote:
On 6/27/2018 11:33 AM, Guenter Roeck wrote:
On Wed, Jun 20, 2018
Hi Guenter/Florian,
On 6/27/2018 11:55 AM, Guenter Roeck wrote:
On Wed, Jun 27, 2018 at 11:47:21AM -0700, Ray Jui wrote:
On 6/27/2018 11:42 AM, Guenter Roeck wrote:
On Wed, Jun 27, 2018 at 11:38:48AM -0700, Ray Jui wrote:
On 6/27/2018 11:33 AM, Guenter Roeck wrote:
On Wed, Jun 20, 2018
Use GFP_ATOMIC rather GFP_KERNEL in interrupt handler,
as GFP_KERNEL may sleep according to slab allocator.
Signed-off-by: Karim Eshapa
---
drivers/staging/iio/adc/ad7280a.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/iio/adc/ad7280a.c
Use GFP_ATOMIC rather GFP_KERNEL in interrupt handler,
as GFP_KERNEL may sleep according to slab allocator.
Signed-off-by: Karim Eshapa
---
drivers/staging/iio/adc/ad7280a.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/iio/adc/ad7280a.c
Hi all,
Today's linux-next merge of the mips tree got a conflict in:
arch/mips/kernel/process.c
between commit:
b63e132b6433 ("MIPS: Use async IPIs for arch_trigger_cpumask_backtrace()")
from the mips-fixes tree and commit:
8c8d953c2800 ("MIPS: Schedule on CPUs we need to lose FPU for
Hi all,
Today's linux-next merge of the mips tree got a conflict in:
arch/mips/kernel/process.c
between commit:
b63e132b6433 ("MIPS: Use async IPIs for arch_trigger_cpumask_backtrace()")
from the mips-fixes tree and commit:
8c8d953c2800 ("MIPS: Schedule on CPUs we need to lose FPU for
Hi Miquel,
Miquel Raynal writes:
> On Wed, 27 Jun 2018 16:33:43 -0700, Kevin Hilman
> wrote:
>
>> Hi Boris,
>>
>> Boris Brezillon writes:
>>
>> > Hi Yixun,
>> >
>> > On Wed, 13 Jun 2018 16:13:14 +
>> > Yixun Lan wrote:
>> >
>> >> From: Liang Yang
>> >>
>> >> Add initial support for
Hi Miquel,
Miquel Raynal writes:
> On Wed, 27 Jun 2018 16:33:43 -0700, Kevin Hilman
> wrote:
>
>> Hi Boris,
>>
>> Boris Brezillon writes:
>>
>> > Hi Yixun,
>> >
>> > On Wed, 13 Jun 2018 16:13:14 +
>> > Yixun Lan wrote:
>> >
>> >> From: Liang Yang
>> >>
>> >> Add initial support for
' since there are fallbacks for those
two targets.
Documentation/process/changes.rst |8
scripts/kconfig/Makefile |1 +
scripts/kconfig/check-pkgconfig.sh |8
3 files changed, 17 insertions(+)
--- linux-next-20180628.orig/scripts/kconfig/Makefile
+++ linux
' since there are fallbacks for those
two targets.
Documentation/process/changes.rst |8
scripts/kconfig/Makefile |1 +
scripts/kconfig/check-pkgconfig.sh |8
3 files changed, 17 insertions(+)
--- linux-next-20180628.orig/scripts/kconfig/Makefile
+++ linux
On Thu, 2018-06-28 at 18:41 +0800, CK Hu wrote:
> Hi, Houlong:
>
> Some inline comment.
>
> On Wed, 2018-06-27 at 19:16 +0800, Houlong Wei wrote:
> > Add Mediatek CMDQ helper to create CMDQ packet and assemble GCE op code.
> >
> > Signed-off-by: Houlong Wei
> > Signed-off-by: HS Liao
> > ---
On Thu, 2018-06-28 at 18:41 +0800, CK Hu wrote:
> Hi, Houlong:
>
> Some inline comment.
>
> On Wed, 2018-06-27 at 19:16 +0800, Houlong Wei wrote:
> > Add Mediatek CMDQ helper to create CMDQ packet and assemble GCE op code.
> >
> > Signed-off-by: Houlong Wei
> > Signed-off-by: HS Liao
> > ---
On Thu, Jun 28, 2018 at 2:22 PM, Linus Torvalds
wrote:
> On Thu, Jun 28, 2018 at 1:23 PM Andy Lutomirski wrote:
>>
>> This is okay with me for a fix outside the merge window. Can you do a
>> followup for the next merge window that fixes it better, though? In
>> particular, TASK_SIZE is
On Thu, Jun 28, 2018 at 2:22 PM, Linus Torvalds
wrote:
> On Thu, Jun 28, 2018 at 1:23 PM Andy Lutomirski wrote:
>>
>> This is okay with me for a fix outside the merge window. Can you do a
>> followup for the next merge window that fixes it better, though? In
>> particular, TASK_SIZE is
On Thu, Jun 28, 2018 at 6:21 PM ronnie sahlberg
wrote:
>
> On Fri, Jun 29, 2018 at 8:58 AM, Theodore Y. Ts'o via samba-technical
> wrote:
> > On Thu, Jun 28, 2018 at 05:37:15PM -0500, Steve French wrote:
> >> Ronnie brought up an interesting point about the problems consistently
> >> configuring
On Thu, Jun 28, 2018 at 6:21 PM ronnie sahlberg
wrote:
>
> On Fri, Jun 29, 2018 at 8:58 AM, Theodore Y. Ts'o via samba-technical
> wrote:
> > On Thu, Jun 28, 2018 at 05:37:15PM -0500, Steve French wrote:
> >> Ronnie brought up an interesting point about the problems consistently
> >> configuring
On Fri, Jun 29, 2018 at 06:46:25AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
> dev
> head: 0028a1e4fdbb4263539595da08979d59954d4873
> commit: 0028a1e4fdbb4263539595da08979d59954d4873 [110/110] rcu: Apply RCU-bh
> QSes to
On Fri, Jun 29, 2018 at 06:46:25AM +0800, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
> dev
> head: 0028a1e4fdbb4263539595da08979d59954d4873
> commit: 0028a1e4fdbb4263539595da08979d59954d4873 [110/110] rcu: Apply RCU-bh
> QSes to
On Fri, Jun 29, 2018 at 8:58 AM, Theodore Y. Ts'o via samba-technical
wrote:
> On Thu, Jun 28, 2018 at 05:37:15PM -0500, Steve French wrote:
>> Ronnie brought up an interesting point about the problems consistently
>> configuring file systems (or any Linux module for that matter) so that
>>
On Fri, Jun 29, 2018 at 8:58 AM, Theodore Y. Ts'o via samba-technical
wrote:
> On Thu, Jun 28, 2018 at 05:37:15PM -0500, Steve French wrote:
>> Ronnie brought up an interesting point about the problems consistently
>> configuring file systems (or any Linux module for that matter) so that
>>
Michal Hocko wrote:
> From: Michal Hocko
>
> 3812c8c8f395 ("mm: memcg: do not trap chargers with full callstack on OOM")
> has changed the ENOMEM semantic of memcg charges. Rather than invoking
> the oom killer from the charging context it delays the oom killer to the
> page fault path
Michal Hocko wrote:
> From: Michal Hocko
>
> 3812c8c8f395 ("mm: memcg: do not trap chargers with full callstack on OOM")
> has changed the ENOMEM semantic of memcg charges. Rather than invoking
> the oom killer from the charging context it delays the oom killer to the
> page fault path
The HPLL can be configured through a register (SCU24), however some
platforms chose to configure it through the strapping settings and do
not use the register. This was not noticed as the logic for bit 18 in
SCU24 was confused: set means programmed, but the driver read it as set
means strapped.
The HPLL can be configured through a register (SCU24), however some
platforms chose to configure it through the strapping settings and do
not use the register. This was not noticed as the logic for bit 18 in
SCU24 was confused: set means programmed, but the driver read it as set
means strapped.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
dev
head: 0028a1e4fdbb4263539595da08979d59954d4873
commit: 0028a1e4fdbb4263539595da08979d59954d4873 [110/110] rcu: Apply RCU-bh
QSes to RCU-sched and RCU-preempt when safe
config: x86_64-randconfig-i0-201825
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
dev
head: 0028a1e4fdbb4263539595da08979d59954d4873
commit: 0028a1e4fdbb4263539595da08979d59954d4873 [110/110] rcu: Apply RCU-bh
QSes to RCU-sched and RCU-preempt when safe
config: x86_64-randconfig-i0-201825
The RMI4 touchscreen driver applied inversion and axis swap in the
wrong order, violating the DT binding for those properties. This was fixed in
645a397, so correct the RDU1 DT to apply the inversion to the
correct axis.
Tested on Zii RDU1 00-5105-30 rev B
Signed-off-by: Nick Dyer
---
The RMI4 touchscreen driver applied inversion and axis swap in the
wrong order, violating the DT binding for those properties. This was fixed in
645a397, so correct the RDU1 DT to apply the inversion to the
correct axis.
Tested on Zii RDU1 00-5105-30 rev B
Signed-off-by: Nick Dyer
---
Hi,
On Thu, Jun 28, 2018 at 2:09 PM, Matthias Kaehlcke wrote:
> Add pm8998 thermal zone based on the examples in the spmi-temp-alarm
> bindings.
>
> Note: devices with the pm8998 need to have a 'thermal-zones' node (which
> may be empty) with a label 'thermal_zones'.
>
> Signed-off-by: Matthias
Hi,
On Thu, Jun 28, 2018 at 2:09 PM, Matthias Kaehlcke wrote:
> Add pm8998 thermal zone based on the examples in the spmi-temp-alarm
> bindings.
>
> Note: devices with the pm8998 need to have a 'thermal-zones' node (which
> may be empty) with a label 'thermal_zones'.
>
> Signed-off-by: Matthias
On Thu, Jun 28, 2018 at 05:37:15PM -0500, Steve French wrote:
> Ronnie brought up an interesting point about the problems consistently
> configuring file systems (or any Linux module for that matter) so that
> reboot doesn't wipe away security or performance tuning changes.
In general it's
On Thu, Jun 28, 2018 at 05:37:15PM -0500, Steve French wrote:
> Ronnie brought up an interesting point about the problems consistently
> configuring file systems (or any Linux module for that matter) so that
> reboot doesn't wipe away security or performance tuning changes.
In general it's
Hi,
On Thu, Jun 28, 2018 at 2:09 PM, Matthias Kaehlcke wrote:
> The node is empty for now. It is needed to allow other DT snippets
> to add thermal zone entries.
>
> Signed-off-by: Matthias Kaehlcke
> ---
> Sorry if you received this twice, lists were missing in cc in the first
> attempt ...
>
Hi,
On Thu, Jun 28, 2018 at 2:09 PM, Matthias Kaehlcke wrote:
> The node is empty for now. It is needed to allow other DT snippets
> to add thermal zone entries.
>
> Signed-off-by: Matthias Kaehlcke
> ---
> Sorry if you received this twice, lists were missing in cc in the first
> attempt ...
>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
dev
head: 0028a1e4fdbb4263539595da08979d59954d4873
commit: 0028a1e4fdbb4263539595da08979d59954d4873 [110/110] rcu: Apply RCU-bh
QSes to RCU-sched and RCU-preempt when safe
config: i386-alldefconfig (attached as
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git
dev
head: 0028a1e4fdbb4263539595da08979d59954d4873
commit: 0028a1e4fdbb4263539595da08979d59954d4873 [110/110] rcu: Apply RCU-bh
QSes to RCU-sched and RCU-preempt when safe
config: i386-alldefconfig (attached as
Current select_idle_sibling first tries to find a fully idle core using
select_idle_core which can potentially search all cores and if it fails it
finds any idle cpu using select_idle_cpu. select_idle_cpu can potentially
search all cpus in the llc domain. This doesn't scale for large llc domains
Current select_idle_sibling first tries to find a fully idle core using
select_idle_core which can potentially search all cores and if it fails it
finds any idle cpu using select_idle_cpu. select_idle_cpu can potentially
search all cpus in the llc domain. This doesn't scale for large llc domains
Introduce a per-cpu variable to track the limit upto which idle cpu search
was done in select_idle_cpu(). This will help to start the search next time
from there. This is necessary for rotating the search window over entire
LLC domain.
Signed-off-by: subhra mazumdar
---
kernel/sched/core.c | 2
Introduce a per-cpu variable to track the limit upto which idle cpu search
was done in select_idle_cpu(). This will help to start the search next time
from there. This is necessary for rotating the search window over entire
LLC domain.
Signed-off-by: subhra mazumdar
---
kernel/sched/core.c | 2
Put upper and lower limit on cpu search of select_idle_cpu. The lower limit
is amount of cpus in a core while upper limit is twice that. This ensures
for any architecture we will usually search beyond a core. The upper limit
also helps in keeping the search cost low and constant.
Signed-off-by:
Rotate the cpu search window for better spread of threads. This will ensure
an idle cpu will quickly be found if one exists.
Signed-off-by: subhra mazumdar
---
kernel/sched/fair.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/fair.c
Put upper and lower limit on cpu search of select_idle_cpu. The lower limit
is amount of cpus in a core while upper limit is twice that. This ensures
for any architecture we will usually search beyond a core. The upper limit
also helps in keeping the search cost low and constant.
Signed-off-by:
Rotate the cpu search window for better spread of threads. This will ensure
an idle cpu will quickly be found if one exists.
Signed-off-by: subhra mazumdar
---
kernel/sched/fair.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/fair.c
Add a new sched feature SIS_CORE to have an option to disable idle core
search (select_idle_core).
Signed-off-by: subhra mazumdar
---
kernel/sched/features.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/sched/features.h b/kernel/sched/features.h
index 85ae848..de15733 100644
---
Add a new sched feature SIS_CORE to have an option to disable idle core
search (select_idle_core).
Signed-off-by: subhra mazumdar
---
kernel/sched/features.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/sched/features.h b/kernel/sched/features.h
index 85ae848..de15733 100644
---
Use SIS_CORE to disable idle core search. For some workloads
select_idle_core becomes a scalability bottleneck, removing it improves
throughput. Also there are workloads where disabling it can hurt latency,
so need to have an option.
Signed-off-by: subhra mazumdar
---
kernel/sched/fair.c | 8
Use SIS_CORE to disable idle core search. For some workloads
select_idle_core becomes a scalability bottleneck, removing it improves
throughput. Also there are workloads where disabling it can hurt latency,
so need to have an option.
Signed-off-by: subhra mazumdar
---
kernel/sched/fair.c | 8
Ronnie brought up an interesting point about the problems consistently
configuring file systems (or any Linux module for that matter) so that
reboot doesn't wipe away security or performance tuning changes.
Linux file systems typically allow configuration via various ways (I
may have left some
Ronnie brought up an interesting point about the problems consistently
configuring file systems (or any Linux module for that matter) so that
reboot doesn't wipe away security or performance tuning changes.
Linux file systems typically allow configuration via various ways (I
may have left some
- On Jun 28, 2018, at 5:22 PM, Linus Torvalds torva...@linux-foundation.org
wrote:
> On Thu, Jun 28, 2018 at 1:23 PM Andy Lutomirski wrote:
>>
>> This is okay with me for a fix outside the merge window. Can you do a
>> followup for the next merge window that fixes it better, though? In
>>
- On Jun 28, 2018, at 5:22 PM, Linus Torvalds torva...@linux-foundation.org
wrote:
> On Thu, Jun 28, 2018 at 1:23 PM Andy Lutomirski wrote:
>>
>> This is okay with me for a fix outside the merge window. Can you do a
>> followup for the next merge window that fixes it better, though? In
>>
Hello,
Ping?
Samuel
Samuel Thibault, le dim. 03 juin 2018 20:18:58 +0200, a ecrit:
> This completes dead keys definitions for internationalization
> completeness on the console. The representatives have been chosen
> coherently with libx11 compose sequences, which avoid symetry conflicts
>
Hello,
Ping?
Samuel
Samuel Thibault, le dim. 03 juin 2018 20:18:58 +0200, a ecrit:
> This completes dead keys definitions for internationalization
> completeness on the console. The representatives have been chosen
> coherently with libx11 compose sequences, which avoid symetry conflicts
>
On 2018/06/28 08:21:40 -0700, Paul E. McKenney wrote:
[...]
>
> While I am at it, here is the current scorecard:
>
> e9ff68680cd4 tools/memory-model: Add litmus test for full multicopy atomicity
> c21fcc6594f1 tools/memory-model: Fix ISA2+pooncelock+pooncelock+pombonce name
> aa838e0b70e1
On 2018/06/28 08:21:40 -0700, Paul E. McKenney wrote:
[...]
>
> While I am at it, here is the current scorecard:
>
> e9ff68680cd4 tools/memory-model: Add litmus test for full multicopy atomicity
> c21fcc6594f1 tools/memory-model: Fix ISA2+pooncelock+pooncelock+pombonce name
> aa838e0b70e1
Thanks for the quick turnaround.
Good to know about the how the 2M code path differs, I have been
trying to trace through some of this and it's easy to get lost between
which applies to which size.
Thanks!
On Thu, Jun 28, 2018 at 12:03 PM Michal Hocko wrote:
>
> On Wed 27-06-18 14:44:47, Cannon
Thanks for the quick turnaround.
Good to know about the how the 2M code path differs, I have been
trying to trace through some of this and it's easy to get lost between
which applies to which size.
Thanks!
On Thu, Jun 28, 2018 at 12:03 PM Michal Hocko wrote:
>
> On Wed 27-06-18 14:44:47, Cannon
> -Original Message-
> From: Andy Shevchenko [mailto:andy.shevche...@gmail.com]
> Sent: Wednesday, June 27, 2018 10:29 AM
> To: Toralf Förster ; Schmauss, Erik
>
> Cc: ACPI Devel Maling List ; Linux Kernel ker...@vger.kernel.org>
> Subject: Re: small dmesg regression in kernel 4.17.3
>
Hi all,
Today's linux-next merge of the net tree got a conflict in:
net/smc/af_smc.c
between commit:
a11e1d432b51 ("Revert changes to convert to ->poll_mask() and aio
IOCB_CMD_POLL")
from Linus' tree and commit:
24ac3a08e658 ("net/smc: rebuild nonblocking connect")
from the net tree.
> -Original Message-
> From: Andy Shevchenko [mailto:andy.shevche...@gmail.com]
> Sent: Wednesday, June 27, 2018 10:29 AM
> To: Toralf Förster ; Schmauss, Erik
>
> Cc: ACPI Devel Maling List ; Linux Kernel ker...@vger.kernel.org>
> Subject: Re: small dmesg regression in kernel 4.17.3
>
Hi all,
Today's linux-next merge of the net tree got a conflict in:
net/smc/af_smc.c
between commit:
a11e1d432b51 ("Revert changes to convert to ->poll_mask() and aio
IOCB_CMD_POLL")
from Linus' tree and commit:
24ac3a08e658 ("net/smc: rebuild nonblocking connect")
from the net tree.
This appends the controller instance to the trace buffer for nvme commands
to distinguish what controller is dispatching and completing a command.
Signed-off-by: Keith Busch
---
drivers/nvme/host/trace.h | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git
This appends the controller instance to the trace buffer for nvme commands
to distinguish what controller is dispatching and completing a command.
Signed-off-by: Keith Busch
---
drivers/nvme/host/trace.h | 17 +++--
1 file changed, 11 insertions(+), 6 deletions(-)
diff --git
We can not match a command to its completion based on the command id
alone. We need the submitting queue identifier to pair the completion,
so this patch adds that to the trace buffer.
This patch is also collapsing the admin and io submission traces into
a single one since we don't need to
We can not match a command to its completion based on the command id
alone. We need the submitting queue identifier to pair the completion,
so this patch adds that to the trace buffer.
This patch is also collapsing the admin and io submission traces into
a single one since we don't need to
From: Sagi Grimberg
We will need to reference the controller in the setup and completion
time for tracing and future traffic based keep alive support.
Signed-off-by: Sagi Grimberg
---
drivers/nvme/host/fc.c | 1 +
drivers/nvme/host/nvme.h | 1 +
drivers/nvme/host/pci.c| 2 ++
From: Sagi Grimberg
We will need to reference the controller in the setup and completion
time for tracing and future traffic based keep alive support.
Signed-off-by: Sagi Grimberg
---
drivers/nvme/host/fc.c | 1 +
drivers/nvme/host/nvme.h | 1 +
drivers/nvme/host/pci.c| 2 ++
This will print the disk name to the nvme trace for disk based requests
so a user can better distinguish traffic to different disks. This allows
disk based filters. For example, to see only nvme0n2 traffic:
echo "disk == nvme0n2" > /sys/kernel/debug/tracing/events/nvme/filter
Signed-off-by:
This will print the disk name to the nvme trace for disk based requests
so a user can better distinguish traffic to different disks. This allows
disk based filters. For example, to see only nvme0n2 traffic:
echo "disk == nvme0n2" > /sys/kernel/debug/tracing/events/nvme/filter
Signed-off-by:
This patch series based on/inspired by Johannes Thumshirn that improves
the nvme trace events.
The one from Sagi is saving the nvme_ctrl in the driver request data
so we can reference it in other places, both for this series and future
developments.
The others are adding and simplifying the nvme
This patch series based on/inspired by Johannes Thumshirn that improves
the nvme trace events.
The one from Sagi is saving the nvme_ctrl in the driver request data
so we can reference it in other places, both for this series and future
developments.
The others are adding and simplifying the nvme
On Thu, Jun 28, 2018 at 03:13:32PM +0300, Stefan Popa wrote:
> The AD5758 is a single channel DAC with 16-bit precision which uses the
> SPI interface that operates at clock rates up to 50MHz.
>
> The output can be configured as voltage or current and is available on a
> single terminal.
>
>
On Thu, Jun 28, 2018 at 03:13:32PM +0300, Stefan Popa wrote:
> The AD5758 is a single channel DAC with 16-bit precision which uses the
> SPI interface that operates at clock rates up to 50MHz.
>
> The output can be configured as voltage or current and is available on a
> single terminal.
>
>
101 - 200 of 1130 matches
Mail list logo
