On Tue, Oct 30, 2018 at 4:48 PM Hans de Goede wrote:
> On 30-10-18 15:38, Dean Wallace wrote:
> > Excellent work Hans. Compiled 4.19 with
> > 0001-ASoC-intel-cht_bsw_max98090_ti-Use-pmc_plt_clk_0-ins.patch, sound
> > works as before.
> >
> > for i in /sys/kernel/debug/clk/pmc_plt_clk_?; do echo
On Tue, Oct 30, 2018 at 4:48 PM Hans de Goede wrote:
> On 30-10-18 15:38, Dean Wallace wrote:
> > Excellent work Hans. Compiled 4.19 with
> > 0001-ASoC-intel-cht_bsw_max98090_ti-Use-pmc_plt_clk_0-ins.patch, sound
> > works as before.
> >
> > for i in /sys/kernel/debug/clk/pmc_plt_clk_?; do echo
On 10/29, Tycho Andersen wrote:
>
> +static long seccomp_notify_recv(struct seccomp_filter *filter,
> + void __user *buf)
> +{
> + struct seccomp_knotif *knotif = NULL, *cur;
> + struct seccomp_notif unotif;
> + ssize_t ret;
> +
> + memset(, 0,
On 10/29, Tycho Andersen wrote:
>
> +static long seccomp_notify_recv(struct seccomp_filter *filter,
> + void __user *buf)
> +{
> + struct seccomp_knotif *knotif = NULL, *cur;
> + struct seccomp_notif unotif;
> + ssize_t ret;
> +
> + memset(, 0,
On Tue, 2018-10-30 at 08:01 -0400, Bo YU wrote:
> Fix warning from checkpatch.pl use pr_* to replace printk
If you look at msg, it can be unterminated with newline.
> diff --git a/lib/kobject_uevent.c b/lib/kobject_uevent.c
[]
> @@ -224,7 +224,7 @@ int kobject_synth_uevent(struct kobject *kobj,
On Tue, 2018-10-30 at 08:01 -0400, Bo YU wrote:
> Fix warning from checkpatch.pl use pr_* to replace printk
If you look at msg, it can be unterminated with newline.
> diff --git a/lib/kobject_uevent.c b/lib/kobject_uevent.c
[]
> @@ -224,7 +224,7 @@ int kobject_synth_uevent(struct kobject *kobj,
Hello,
syzbot found the following crash on:
HEAD commit:4b42745211af Merge tag 'armsoc-soc' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1187d06d40
kernel config: https://syzkaller.appspot.com/x/.config?x=93932074d01b4a5
Hello,
syzbot found the following crash on:
HEAD commit:4b42745211af Merge tag 'armsoc-soc' of git://git.kernel.or..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1187d06d40
kernel config: https://syzkaller.appspot.com/x/.config?x=93932074d01b4a5
Hello,
syzbot found the following crash on:
HEAD commit:b179f0826c6a Add linux-next specific files for 20181029
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1243d1c540
kernel config: https://syzkaller.appspot.com/x/.config?x=6b2b22387bad67fc
On Tue, 30 Oct 2018 09:28:22 -0400
Sasha Levin wrote:
> From: Masami Hiramatsu
>
> [ Upstream commit ba0e41ca81b935b958006c7120466e2217357827 ]
>
> Add a testcase to check the syntax and field types for
> synthetic_events interface.
>
> Link:
>
On Tue, 30 Oct 2018 09:28:22 -0400
Sasha Levin wrote:
> From: Masami Hiramatsu
>
> [ Upstream commit ba0e41ca81b935b958006c7120466e2217357827 ]
>
> Add a testcase to check the syntax and field types for
> synthetic_events interface.
>
> Link:
>
Hello,
syzbot found the following crash on:
HEAD commit:b179f0826c6a Add linux-next specific files for 20181029
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1243d1c540
kernel config: https://syzkaller.appspot.com/x/.config?x=6b2b22387bad67fc
> No, that's fine. Now I get this, and I totally agree with the approach:
>
> Reviewed-by: Benjamin Tissoires
Thanks! If one of you could provide me with a Fixes tag (for this. or
both patches?), that would be most helpful.
signature.asc
Description: PGP signature
> No, that's fine. Now I get this, and I totally agree with the approach:
>
> Reviewed-by: Benjamin Tissoires
Thanks! If one of you could provide me with a Fixes tag (for this. or
both patches?), that would be most helpful.
signature.asc
Description: PGP signature
Both graphics and serial consoles are exposed to hard lockups
when handling a large amount of messaging. The kernel watchdog_thresh
parameter up to now has not been available to be set on the kernel line for
early boot.
This patch allows the setting of watchdog_thresh to be increased
when needed
Both graphics and serial consoles are exposed to hard lockups
when handling a large amount of messaging. The kernel watchdog_thresh
parameter up to now has not been available to be set on the kernel line for
early boot.
This patch allows the setting of watchdog_thresh to be increased
when needed
Hi,
On 30-10-18 15:38, Dean Wallace wrote:
On 30-10-18, Hans de Goede wrote:
Hi Dean,
Attached are 2 different attempts at fixing this.
When trying these patches do not forget to remove the revert of the
"Stop-marking-clocks-as-CLK_IS_CRITICAL" commit.
Please first try the
Hi,
On 30-10-18 15:38, Dean Wallace wrote:
On 30-10-18, Hans de Goede wrote:
Hi Dean,
Attached are 2 different attempts at fixing this.
When trying these patches do not forget to remove the revert of the
"Stop-marking-clocks-as-CLK_IS_CRITICAL" commit.
Please first try the
On some laptops the ACPI device with BOSC0200 _HID is representing
two accelerometers under one node.
We add an ID to the I2C multi instantiate list to enumerate
all I2C slaves correctly.
For reference here is the relevant DSDT blurb from the Yoga 11e:
Device (ACC)
{
Name (_ADR, Zero)
On some laptops the ACPI device with BOSC0200 _HID is representing
two accelerometers under one node.
We add an ID to the I2C multi instantiate list to enumerate
all I2C slaves correctly.
For reference here is the relevant DSDT blurb from the Yoga 11e:
Device (ACC)
{
Name (_ADR, Zero)
When CONFIG_RT_GROUP_SCHED is not configured, group_rt_rq() will
return NULL. With this patch applied, we also can get the same result.
Because the compiler will help us optimize the code.
So, we can remove unnecessary CONFIG_RT_GROUP_SCHED in rt_se_prio().
Signed-off-by: Muchun Song
---
When CONFIG_RT_GROUP_SCHED is not configured, group_rt_rq() will
return NULL. With this patch applied, we also can get the same result.
Because the compiler will help us optimize the code.
So, we can remove unnecessary CONFIG_RT_GROUP_SCHED in rt_se_prio().
Signed-off-by: Muchun Song
---
Em Mon, Oct 29, 2018 at 11:32:11PM +, Colin King escreveu:
> From: Colin Ian King
>
> Replace a bunch of spaces with tab, cleans up indentation
I think we can live with the spaces as the 'git blame' information is
more valuable, i.e. who was that touched that line last?
Thanks,
- Arnaldo
Em Mon, Oct 29, 2018 at 11:32:11PM +, Colin King escreveu:
> From: Colin Ian King
>
> Replace a bunch of spaces with tab, cleans up indentation
I think we can live with the spaces as the 'git blame' information is
more valuable, i.e. who was that touched that line last?
Thanks,
- Arnaldo
On 30-10-18, Hans de Goede wrote:
> Hi Dean,
>
> Attached are 2 different attempts at fixing this.
>
> When trying these patches do not forget to remove the revert of the
> "Stop-marking-clocks-as-CLK_IS_CRITICAL" commit.
>
> Please first try the
>
On 30-10-18, Hans de Goede wrote:
> Hi Dean,
>
> Attached are 2 different attempts at fixing this.
>
> When trying these patches do not forget to remove the revert of the
> "Stop-marking-clocks-as-CLK_IS_CRITICAL" commit.
>
> Please first try the
>
On Tue, Oct 30, 2018 at 12:51 PM Charles Keepax
wrote:
>
> On Mon, Oct 29, 2018 at 11:15:47AM +0100, Benjamin Tissoires wrote:
> > On Sun, Oct 28, 2018 at 11:31 PM Wolfram Sang wrote:
> > >
> > > On Fri, Oct 19, 2018 at 09:59:58AM +0100, Charles Keepax wrote:
> > > > The IRQ will be mapped in
On Tue, Oct 30, 2018 at 12:51 PM Charles Keepax
wrote:
>
> On Mon, Oct 29, 2018 at 11:15:47AM +0100, Benjamin Tissoires wrote:
> > On Sun, Oct 28, 2018 at 11:31 PM Wolfram Sang wrote:
> > >
> > > On Fri, Oct 19, 2018 at 09:59:58AM +0100, Charles Keepax wrote:
> > > > The IRQ will be mapped in
On 10/29, Tycho Andersen wrote:
>
> + /* This is where we wait for a reply from userspace. */
> + err = wait_for_completion_interruptible();
> + mutex_lock(>notify_lock);
> +
> + /*
> + * If the noticiation fd died before we re-acquired the lock, we still
> + * give
On 10/29, Tycho Andersen wrote:
>
> + /* This is where we wait for a reply from userspace. */
> + err = wait_for_completion_interruptible();
> + mutex_lock(>notify_lock);
> +
> + /*
> + * If the noticiation fd died before we re-acquired the lock, we still
> + * give
Em Tue, Oct 30, 2018 at 03:18:28PM +0800, Leo Yan escreveu:
> Since commit 9042f5e3539e ("perf tools: Stop fallbacking to kallsyms
> for vdso symbols lookup"), the kernel address cannot be properly parsed
> to kernel symbol with command 'perf script -k vmlinux'. The reason is
> CoreSight samples
Em Tue, Oct 30, 2018 at 03:18:28PM +0800, Leo Yan escreveu:
> Since commit 9042f5e3539e ("perf tools: Stop fallbacking to kallsyms
> for vdso symbols lookup"), the kernel address cannot be properly parsed
> to kernel symbol with command 'perf script -k vmlinux'. The reason is
> CoreSight samples
On Tue 30-10-18 22:57:37, Tetsuo Handa wrote:
> On 2018/10/30 21:10, Michal Hocko wrote:
> > I misunderstood your concern. oom_reaper would back off without
> > MMF_OOF_SKIP as well. You are right we cannot assume anything about
> > close callbacks so MMF_OOM_SKIP has to come before that. I will
On Tue 30-10-18 22:57:37, Tetsuo Handa wrote:
> On 2018/10/30 21:10, Michal Hocko wrote:
> > I misunderstood your concern. oom_reaper would back off without
> > MMF_OOF_SKIP as well. You are right we cannot assume anything about
> > close callbacks so MMF_OOM_SKIP has to come before that. I will
Am Mittwoch, 17. Oktober 2018, 11:18:30 CET schrieb Daniel Lezcano:
> When the performance governor is set as default, the rock960 hangs
> around one minute after booting, whatever the activity is (idle, key
> pressed, loaded, ...).
>
> Based on the commit log found at
Am Mittwoch, 17. Oktober 2018, 11:18:30 CET schrieb Daniel Lezcano:
> When the performance governor is set as default, the rock960 hangs
> around one minute after booting, whatever the activity is (idle, key
> pressed, loaded, ...).
>
> Based on the commit log found at
From: Colin Ian King
Trivial fix to clean up an indentation issue, remove space
Signed-off-by: Colin Ian King
---
security/apparmor/apparmorfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/apparmor/apparmorfs.c b/security/apparmor/apparmorfs.c
index
From: Colin Ian King
Trivial fix to clean up an indentation issue, remove space
Signed-off-by: Colin Ian King
---
security/apparmor/apparmorfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/apparmor/apparmorfs.c b/security/apparmor/apparmorfs.c
index
On 30 October 2018 at 08:49, Ard Biesheuvel wrote:
> Hi Anders,
>
>> On 30 Oct 2018, at 08:38, Anders Roxell wrote:
>>
>> Commit 1404d6f13e47 ("arm64: dump: Add checking for writable and exectuable
>> pages")
>> has successfully identified code that leaves a page with W+X
>> permissions.
>>
>>
On 30 October 2018 at 08:49, Ard Biesheuvel wrote:
> Hi Anders,
>
>> On 30 Oct 2018, at 08:38, Anders Roxell wrote:
>>
>> Commit 1404d6f13e47 ("arm64: dump: Add checking for writable and exectuable
>> pages")
>> has successfully identified code that leaves a page with W+X
>> permissions.
>>
>>
From: Colin Ian King
Trivial fix to clean up an indentation issue, remove space
Signed-off-by: Colin Ian King
---
drivers/gpio/gpio-sch311x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/gpio-sch311x.c b/drivers/gpio/gpio-sch311x.c
index
From: Colin Ian King
Trivial fix to clean up an indentation issue, remove space
Signed-off-by: Colin Ian King
---
drivers/gpio/gpio-sch311x.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/gpio-sch311x.c b/drivers/gpio/gpio-sch311x.c
index
On Tue, Oct 30, 2018 at 02:04:20PM +0100, Linus Walleij wrote:
> On Fri, Oct 19, 2018 at 11:50 AM Charles Keepax
> wrote:
>
> > Lochnagar is an evaluation and development board for Cirrus
> > Logic Smart CODEC and Amp devices. It allows the connection of
> > most Cirrus Logic devices on
On Tue, Oct 30, 2018 at 02:04:20PM +0100, Linus Walleij wrote:
> On Fri, Oct 19, 2018 at 11:50 AM Charles Keepax
> wrote:
>
> > Lochnagar is an evaluation and development board for Cirrus
> > Logic Smart CODEC and Amp devices. It allows the connection of
> > most Cirrus Logic devices on
On 2018/10/30 21:10, Michal Hocko wrote:
> I misunderstood your concern. oom_reaper would back off without
> MMF_OOF_SKIP as well. You are right we cannot assume anything about
> close callbacks so MMF_OOM_SKIP has to come before that. I will move it
> behind the pagetable freeing.
>
And at that
On 2018/10/30 21:10, Michal Hocko wrote:
> I misunderstood your concern. oom_reaper would back off without
> MMF_OOF_SKIP as well. You are right we cannot assume anything about
> close callbacks so MMF_OOM_SKIP has to come before that. I will move it
> behind the pagetable freeing.
>
And at that
>> struct anybus_s_host *cd = data;
>> drivers/bus/anybus-s-host.c
>> include/linux/anybus-s-client.h
>
> Hm I think this looks pretty neat actually. Anyways, in the overall
> architecture explain the three Anybus:es and why things pertaining
> to Anybus-s are named as they are.
Ok, so should I
>> struct anybus_s_host *cd = data;
>> drivers/bus/anybus-s-host.c
>> include/linux/anybus-s-client.h
>
> Hm I think this looks pretty neat actually. Anyways, in the overall
> architecture explain the three Anybus:es and why things pertaining
> to Anybus-s are named as they are.
Ok, so should I
On 30/10/2018 14:33, Marc Dionne wrote:
> On Mon, Oct 29, 2018 at 11:25 AM Juergen Gross wrote:
>>
>> On 29/10/2018 13:58, Marc Dionne wrote:
>>> On Tue, Oct 23, 2018 at 2:37 PM Linux Kernel Mailing List
>>> wrote:
Commit: 5c83511bdb9832c86be20fb86b783356e2f58062
Parent:
On 30/10/2018 14:33, Marc Dionne wrote:
> On Mon, Oct 29, 2018 at 11:25 AM Juergen Gross wrote:
>>
>> On 29/10/2018 13:58, Marc Dionne wrote:
>>> On Tue, Oct 23, 2018 at 2:37 PM Linux Kernel Mailing List
>>> wrote:
Commit: 5c83511bdb9832c86be20fb86b783356e2f58062
Parent:
please drop this one, it isn't correct.
On 10/29/2018 06:25 PM, Vasily Averin wrote:
> Fixes ac27a0ec112a ("ext4: initial copy of files from ext3")
> #? cc: stable # 2.6.19 or evel earlier in ext3
>
> Signed-off-by: Vasily Averin
> ---
> fs/ext4/resize.c | 1 +
> 1 file changed, 1
please drop this one, it isn't correct.
On 10/29/2018 06:25 PM, Vasily Averin wrote:
> Fixes ac27a0ec112a ("ext4: initial copy of files from ext3")
> #? cc: stable # 2.6.19 or evel earlier in ext3
>
> Signed-off-by: Vasily Averin
> ---
> fs/ext4/resize.c | 1 +
> 1 file changed, 1
On 10/26/2018 11:00 AM, Joakim Zhang wrote:
> From: Dong Aisheng
>
> If wakeup is enabled, enter stop mode, else enter disabled mode.
> Self wake can only work on stop mode.
>
> Starting from IMX6, the flexcan stop mode control bits is SoC specific,
> move it out of IP driver and parse it from
On 10/26/2018 11:00 AM, Joakim Zhang wrote:
> From: Dong Aisheng
>
> If wakeup is enabled, enter stop mode, else enter disabled mode.
> Self wake can only work on stop mode.
>
> Starting from IMX6, the flexcan stop mode control bits is SoC specific,
> move it out of IP driver and parse it from
Hi Jerome,
On 2018/10/29 3:16, Jerome Brunet wrote:
> On Thu, 2018-10-25 at 22:58 +0200, Martin Blumenstingl wrote:
>> Hi Jerome,
>>
>> On Thu, Oct 25, 2018 at 2:54 PM Jerome Brunet wrote:
>> [snip]
>> +static void clk_regmap_div_init(struct clk_hw *hw)
>> +{
>> + struct clk_regmap
Hi Jerome,
On 2018/10/29 3:16, Jerome Brunet wrote:
> On Thu, 2018-10-25 at 22:58 +0200, Martin Blumenstingl wrote:
>> Hi Jerome,
>>
>> On Thu, Oct 25, 2018 at 2:54 PM Jerome Brunet wrote:
>> [snip]
>> +static void clk_regmap_div_init(struct clk_hw *hw)
>> +{
>> + struct clk_regmap
From: Thomas Gleixner Sent: Tuesday, October 30, 2018 1:36
AM
>
> You can avoid the ideffery completely. Something like the uncompiled patch
> (lacks comments) below keeps everything in i8253 and should just work.
>
Thanks. I'll spin a new version with that approach. Having to clutter the
From: Thomas Gleixner Sent: Tuesday, October 30, 2018 1:36
AM
>
> You can avoid the ideffery completely. Something like the uncompiled patch
> (lacks comments) below keeps everything in i8253 and should just work.
>
Thanks. I'll spin a new version with that approach. Having to clutter the
All
On 10/26/2018 03:37 AM, Pavel Machek wrote:
> Hi!
>
>>> Do you have an opinion on this?
>>
>> This is this problem with the Device Tree's scope of responsibility.
>> It is defined as a means for "describing the hardware", but often
>> this rule is abused by the properties that fall into
All
On 10/26/2018 03:37 AM, Pavel Machek wrote:
> Hi!
>
>>> Do you have an opinion on this?
>>
>> This is this problem with the Device Tree's scope of responsibility.
>> It is defined as a means for "describing the hardware", but often
>> this rule is abused by the properties that fall into
Linus,
The biggest change here is the updates to kprobes
Back in January I posted patches to create function based events. These were
the events that you suggested I make to allow developers to easily create
events in code where no trace event exists. After posting those changes for
review, it
Linus,
The biggest change here is the updates to kprobes
Back in January I posted patches to create function based events. These were
the events that you suggested I make to allow developers to easily create
events in code where no trace event exists. After posting those changes for
review, it
On 30/10/2018 09:33, Viresh Kumar wrote:
> On 30-10-18, 08:55, Daniel Lezcano wrote:
>> The workqueue is called from init_cpu_capacity_callback(). This one is
>> called in the notifier callback. IOW the notification callback
>> unregisters itself. But if it is not registered, it won't unregister,
On 30/10/2018 09:33, Viresh Kumar wrote:
> On 30-10-18, 08:55, Daniel Lezcano wrote:
>> The workqueue is called from init_cpu_capacity_callback(). This one is
>> called in the notifier callback. IOW the notification callback
>> unregisters itself. But if it is not registered, it won't unregister,
On Mon, Oct 29, 2018 at 11:25 AM Juergen Gross wrote:
>
> On 29/10/2018 13:58, Marc Dionne wrote:
> > On Tue, Oct 23, 2018 at 2:37 PM Linux Kernel Mailing List
> > wrote:
> >>
> >> Commit: 5c83511bdb9832c86be20fb86b783356e2f58062
> >> Parent: 27876f3882fdd4acb3d3614a0133ecdc777fc292
> >>
From: Jiri Olsa
[ Upstream commit 1b9caa10b31dda0866f4028e4bfb923fb6e4072f ]
This reverts commit ac0e2cd555373ae6f8f3a3ad3fbbf5b6d1e7.
Michael reported an issue with oversized terms values assignment
and I noticed there was actually a misunderstanding of the max
value check in the past.
From: Jian-Hong Pan
[ Upstream commit d49c88d7677ba737e9d2759a87db0402d5ab2607 ]
Originally, we have an issue where r8169 MSI-X interrupt is broken after
S3 suspend/resume on RTL8106e of ASUS X441UAR.
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8101/2/6E PCI Express
From: Fugang Duan
[ Upstream commit ec20a63aa8b8ec3223fb25cdb2a49f9f9dfda88c ]
Commit db65f35f50e0 ("net: fec: add support of ethtool get_regs") introduce
ethool "--register-dump" interface to dump all FEC registers.
But not all silicon implementations of the Freescale FEC hardware module
have
From: Eric Dumazet
[ Upstream commit 262f9d811c7608f1e74258ceecfe1fa213bdf912 ]
If the current process has unlimited RLIMIT_MEMLOCK,
we should should leave it as is.
Fixes: 941ff6f11c02 ("bpf: fix rlimit in reuseport net selftest")
Signed-off-by: John Sperbeck
Signed-off-by: Eric Dumazet
From: "David S. Miller"
[ Upstream commit 455adb3174d2c8518cef1a61140c211f6ac224d2 ]
Like x86 and arm, call perf_sample_event_took() in perf event
NMI interrupt handler.
Signed-off-by: David S. Miller
Signed-off-by: Sasha Levin
---
arch/sparc/kernel/perf_event.c | 9 +
1 file
From: Jian-Hong Pan
[ Upstream commit d49c88d7677ba737e9d2759a87db0402d5ab2607 ]
Originally, we have an issue where r8169 MSI-X interrupt is broken after
S3 suspend/resume on RTL8106e of ASUS X441UAR.
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8101/2/6E PCI Express
From: Fugang Duan
[ Upstream commit ec20a63aa8b8ec3223fb25cdb2a49f9f9dfda88c ]
Commit db65f35f50e0 ("net: fec: add support of ethtool get_regs") introduce
ethool "--register-dump" interface to dump all FEC registers.
But not all silicon implementations of the Freescale FEC hardware module
have
From: Eric Dumazet
[ Upstream commit 262f9d811c7608f1e74258ceecfe1fa213bdf912 ]
If the current process has unlimited RLIMIT_MEMLOCK,
we should should leave it as is.
Fixes: 941ff6f11c02 ("bpf: fix rlimit in reuseport net selftest")
Signed-off-by: John Sperbeck
Signed-off-by: Eric Dumazet
From: "David S. Miller"
[ Upstream commit 455adb3174d2c8518cef1a61140c211f6ac224d2 ]
Like x86 and arm, call perf_sample_event_took() in perf event
NMI interrupt handler.
Signed-off-by: David S. Miller
Signed-off-by: Sasha Levin
---
arch/sparc/kernel/perf_event.c | 9 +
1 file
On Mon, Oct 29, 2018 at 11:25 AM Juergen Gross wrote:
>
> On 29/10/2018 13:58, Marc Dionne wrote:
> > On Tue, Oct 23, 2018 at 2:37 PM Linux Kernel Mailing List
> > wrote:
> >>
> >> Commit: 5c83511bdb9832c86be20fb86b783356e2f58062
> >> Parent: 27876f3882fdd4acb3d3614a0133ecdc777fc292
> >>
From: Jiri Olsa
[ Upstream commit 1b9caa10b31dda0866f4028e4bfb923fb6e4072f ]
This reverts commit ac0e2cd555373ae6f8f3a3ad3fbbf5b6d1e7.
Michael reported an issue with oversized terms values assignment
and I noticed there was actually a misunderstanding of the max
value check in the past.
From: Sebastian Andrzej Siewior
[ Upstream commit 6aa676761d4c1acfa31320e55fa1f83f3fcbbc7a ]
Commit:
c5bedc6847c3b ("x86/fpu: Get rid of PF_USED_MATH usage, convert it to
fpu->fpstate_active")
introduced the 'fpu' variable at top of __restore_xstate_sig(),
which now shadows the other
From: Sebastian Andrzej Siewior
[ Upstream commit 6aa676761d4c1acfa31320e55fa1f83f3fcbbc7a ]
Commit:
c5bedc6847c3b ("x86/fpu: Get rid of PF_USED_MATH usage, convert it to
fpu->fpstate_active")
introduced the 'fpu' variable at top of __restore_xstate_sig(),
which now shadows the other
From: "David S. Miller"
[ Upstream commit 455adb3174d2c8518cef1a61140c211f6ac224d2 ]
Like x86 and arm, call perf_sample_event_took() in perf event
NMI interrupt handler.
Signed-off-by: David S. Miller
Signed-off-by: Sasha Levin
---
arch/sparc/kernel/perf_event.c | 9 +
1 file
From: Masami Hiramatsu
[ Upstream commit ba0e41ca81b935b958006c7120466e2217357827 ]
Add a testcase to check the syntax and field types for
synthetic_events interface.
Link:
http://lkml.kernel.org/r/153986838264.18251.16627517536956299922.stgit@devbox
Acked-by: Shuah Khan
Signed-off-by:
From: "David S. Miller"
[ Upstream commit 455adb3174d2c8518cef1a61140c211f6ac224d2 ]
Like x86 and arm, call perf_sample_event_took() in perf event
NMI interrupt handler.
Signed-off-by: David S. Miller
Signed-off-by: Sasha Levin
---
arch/sparc/kernel/perf_event.c | 9 +
1 file
From: Masami Hiramatsu
[ Upstream commit ba0e41ca81b935b958006c7120466e2217357827 ]
Add a testcase to check the syntax and field types for
synthetic_events interface.
Link:
http://lkml.kernel.org/r/153986838264.18251.16627517536956299922.stgit@devbox
Acked-by: Shuah Khan
Signed-off-by:
From: Nathan Chancellor
[ Upstream commit 8c3bf9b62b667456a57aefcf1689e826df146159 ]
Clang currently warns:
drivers/net/ethernet/qlogic/qla3xxx.c:384:24: warning: signed shift
result (0xF) requires 37 bits to represent, but 'int' only has
32 bits [-Wshift-overflow]
From: "David S. Miller"
[ Upstream commit cfdc3170d214046b9509183fe9b9544dc644d40b ]
It is important to clear the hw->state value for non-stopped events
when they are added into the PMU. Otherwise when the event is
scheduled out, we won't read the counter because HES_UPTODATE is still
set.
From: Heiner Kallweit
[ Upstream commit 6b839b6cf9eada30b086effb51e5d6076bafc761 ]
rtl_rx() and rtl_tx() are called only if the respective bits are set
in the interrupt status register. Under high load NAPI may not be
able to process all data (work_done == budget) and it will schedule
From: Nathan Chancellor
[ Upstream commit 8c3bf9b62b667456a57aefcf1689e826df146159 ]
Clang currently warns:
drivers/net/ethernet/qlogic/qla3xxx.c:384:24: warning: signed shift
result (0xF) requires 37 bits to represent, but 'int' only has
32 bits [-Wshift-overflow]
From: "David S. Miller"
[ Upstream commit cfdc3170d214046b9509183fe9b9544dc644d40b ]
It is important to clear the hw->state value for non-stopped events
when they are added into the PMU. Otherwise when the event is
scheduled out, we won't read the counter because HES_UPTODATE is still
set.
From: Heiner Kallweit
[ Upstream commit 6b839b6cf9eada30b086effb51e5d6076bafc761 ]
rtl_rx() and rtl_tx() are called only if the respective bits are set
in the interrupt status register. Under high load NAPI may not be
able to process all data (work_done == budget) and it will schedule
On 10/30/18, Yoshinori Sato wrote:
> On Mon, 29 Oct 2018 18:44:59 +0900, Arnd Bergmann wrote:
>> just like ARM has mostly killed off the custom vendor-specific
>> instruction
>> sets already. If we add another architecture in the future, it may
>> instead
>> be something like the LLVM bitcode or
On 10/30/18, Yoshinori Sato wrote:
> On Mon, 29 Oct 2018 18:44:59 +0900, Arnd Bergmann wrote:
>> just like ARM has mostly killed off the custom vendor-specific
>> instruction
>> sets already. If we add another architecture in the future, it may
>> instead
>> be something like the LLVM bitcode or
From: David Miller
[ Upstream commit 0ed149cf5239cc6e7e65bf00f769e8f1e91076c0 ]
The size of the resulting cpu map can be smaller than a multiple of
sizeof(u64), resulting in SIGBUS on cpus like Sparc as the next event
will not be aligned properly.
Signed-off-by: David S. Miller
Cc: Jiri Olsa
From: David Miller
[ Upstream commit 0ed149cf5239cc6e7e65bf00f769e8f1e91076c0 ]
The size of the resulting cpu map can be smaller than a multiple of
sizeof(u64), resulting in SIGBUS on cpus like Sparc as the next event
will not be aligned properly.
Signed-off-by: David S. Miller
Cc: Jiri Olsa
From: Masami Hiramatsu
[ Upstream commit ba0e41ca81b935b958006c7120466e2217357827 ]
Add a testcase to check the syntax and field types for
synthetic_events interface.
Link:
http://lkml.kernel.org/r/153986838264.18251.16627517536956299922.stgit@devbox
Acked-by: Shuah Khan
Signed-off-by:
From: Masami Hiramatsu
[ Upstream commit ba0e41ca81b935b958006c7120466e2217357827 ]
Add a testcase to check the syntax and field types for
synthetic_events interface.
Link:
http://lkml.kernel.org/r/153986838264.18251.16627517536956299922.stgit@devbox
Acked-by: Shuah Khan
Signed-off-by:
From: Nathan Chancellor
[ Upstream commit 8c3bf9b62b667456a57aefcf1689e826df146159 ]
Clang currently warns:
drivers/net/ethernet/qlogic/qla3xxx.c:384:24: warning: signed shift
result (0xF) requires 37 bits to represent, but 'int' only has
32 bits [-Wshift-overflow]
From: Heiner Kallweit
[ Upstream commit 6b839b6cf9eada30b086effb51e5d6076bafc761 ]
rtl_rx() and rtl_tx() are called only if the respective bits are set
in the interrupt status register. Under high load NAPI may not be
able to process all data (work_done == budget) and it will schedule
From: Nathan Chancellor
[ Upstream commit 8c3bf9b62b667456a57aefcf1689e826df146159 ]
Clang currently warns:
drivers/net/ethernet/qlogic/qla3xxx.c:384:24: warning: signed shift
result (0xF) requires 37 bits to represent, but 'int' only has
32 bits [-Wshift-overflow]
From: Heiner Kallweit
[ Upstream commit 6b839b6cf9eada30b086effb51e5d6076bafc761 ]
rtl_rx() and rtl_tx() are called only if the respective bits are set
in the interrupt status register. Under high load NAPI may not be
able to process all data (work_done == budget) and it will schedule
From: "David S. Miller"
[ Upstream commit 455adb3174d2c8518cef1a61140c211f6ac224d2 ]
Like x86 and arm, call perf_sample_event_took() in perf event
NMI interrupt handler.
Signed-off-by: David S. Miller
Signed-off-by: Sasha Levin
---
arch/sparc/kernel/perf_event.c | 9 +
1 file
From: "David S. Miller"
[ Upstream commit cfdc3170d214046b9509183fe9b9544dc644d40b ]
It is important to clear the hw->state value for non-stopped events
when they are added into the PMU. Otherwise when the event is
scheduled out, we won't read the counter because HES_UPTODATE is still
set.
601 - 700 of 1220 matches
Mail list logo
