> +int pvcalls_front_release(struct socket *sock)
> +{
> + struct pvcalls_bedata *bedata;
> + struct sock_mapping *map;
> + int req_id, notify;
> + struct xen_pvcalls_request *req;
> +
> + if (!pvcalls_front_dev)
> + return -EIO;
> + bedata =
> +int pvcalls_front_release(struct socket *sock)
> +{
> + struct pvcalls_bedata *bedata;
> + struct sock_mapping *map;
> + int req_id, notify;
> + struct xen_pvcalls_request *req;
> +
> + if (!pvcalls_front_dev)
> + return -EIO;
> + bedata =
On Thu, Jul 27, 2017 at 11:12 AM, Paul E. McKenney
wrote:
> Hello!
> But my main question is whether the throttling shown below is acceptable
> for your use cases, namely only one expedited sys_membarrier() permitted
> per scheduling-clock period (1 millisecond on many
On Thu, Jul 27, 2017 at 11:12 AM, Paul E. McKenney
wrote:
> Hello!
> But my main question is whether the throttling shown below is acceptable
> for your use cases, namely only one expedited sys_membarrier() permitted
> per scheduling-clock period (1 millisecond on many platforms), with any
>
This adds the mmap and mmap2 events to the CTF trace obtained from perf
data.
These events will allow CTF trace visualization tools like Trace
Compass to automatically resolve the symbols of the callchain to the
corresponding function or origin library.
To include those events, one needs to
This adds the mmap and mmap2 events to the CTF trace obtained from perf
data.
These events will allow CTF trace visualization tools like Trace
Compass to automatically resolve the symbols of the callchain to the
corresponding function or origin library.
To include those events, one needs to
On Thu, Jul 27, 2017 at 01:15:48PM -0500, Michael Bringmann wrote:
>
> On NUMA systems with dynamic processors, the content of the cpumask
> may change over time. As new processors are added via DLPAR operations,
> workqueues are created for them. Depending upon the order in which CPUs
> are
On Thu, Jul 27, 2017 at 01:15:48PM -0500, Michael Bringmann wrote:
>
> On NUMA systems with dynamic processors, the content of the cpumask
> may change over time. As new processors are added via DLPAR operations,
> workqueues are created for them. Depending upon the order in which CPUs
> are
Found this in the logs this morning after an overnight fuzz run..
BUG: KASAN: use-after-free in __lock_acquire+0x1aa/0x1970
Read of size 8 at addr 880406805e30 by task trinity-c8/25954
CPU: 1 PID: 25954 Comm: trinity-c8 Not tainted 4.13.0-rc2-think+ #1
Call Trace:
dump_stack+0x68/0xa1
Found this in the logs this morning after an overnight fuzz run..
BUG: KASAN: use-after-free in __lock_acquire+0x1aa/0x1970
Read of size 8 at addr 880406805e30 by task trinity-c8/25954
CPU: 1 PID: 25954 Comm: trinity-c8 Not tainted 4.13.0-rc2-think+ #1
Call Trace:
dump_stack+0x68/0xa1
This adds documentation on the environment variables needed to the
message telling that no conversion support is compiled in.
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Arnaldo Carvalho de Melo
Cc: Alexander Shishkin
This adds documentation on the environment variables needed to the
message telling that no conversion support is compiled in.
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Arnaldo Carvalho de Melo
Cc: Alexander Shishkin
Cc: Mathieu Desnoyers
Cc: Julien Desfossez
Cc: Francis Deslauriers
Cc: Jiri
The field perf_callchain, if available, is added to the sampling
events during the CTF conversion. It is an array of u64 values.
The perf_callchain_size field contains the size of the array.
It will allow the analysis of sampling data in trace visualization tools
like Trace Compass. Possible
The field perf_callchain, if available, is added to the sampling
events during the CTF conversion. It is an array of u64 values.
The perf_callchain_size field contains the size of the array.
It will allow the analysis of sampling data in trace visualization tools
like Trace Compass. Possible
On 27.07.2017 15:20, Paolo Bonzini wrote:
> Expose the "Enable INVPCID" secondary execution control to the guest
> and properly reflect the exit reason.
>
> In addition, before this patch the guest was always running with
> INVPCID enabled, causing pcid.flat's "Test on INVPCID when disabled"
>
On 27.07.2017 15:20, Paolo Bonzini wrote:
> Expose the "Enable INVPCID" secondary execution control to the guest
> and properly reflect the exit reason.
>
> In addition, before this patch the guest was always running with
> INVPCID enabled, causing pcid.flat's "Test on INVPCID when disabled"
>
Dear Friend
I am contacting you on a business deal of $9,500,000.00 Million United States
Dollars, ready for transfer into your own personal account and if we make this
claim, we will share it on the ratio of 50% / 50% basis, I would like to assure
you that it be 100% risk free and it will be
Dear Friend
I am contacting you on a business deal of $9,500,000.00 Million United States
Dollars, ready for transfer into your own personal account and if we make this
claim, we will share it on the ratio of 50% / 50% basis, I would like to assure
you that it be 100% risk free and it will be
On Fri, 14 Jul 2017 14:44:42 +0200
Vitaly Kuznetsov wrote:
> Add Hyper-V tracing subsystem and trace hyperv_mmu_flush_tlb_others().
> Tracing is done the same way we do xen_mmu_flush_tlb_others().
>
> Signed-off-by: Vitaly Kuznetsov
> Reviewed-by: Andy
On Fri, 14 Jul 2017 14:44:42 +0200
Vitaly Kuznetsov wrote:
> Add Hyper-V tracing subsystem and trace hyperv_mmu_flush_tlb_others().
> Tracing is done the same way we do xen_mmu_flush_tlb_others().
>
> Signed-off-by: Vitaly Kuznetsov
> Reviewed-by: Andy Shevchenko
> Reviewed-by: Stephen
Hi Miklos,
I made a first attempt to reproduce the failure but did not get lucky.
> Inode 3093, i_blocks is 16, should be 8. Fix? yes
Does this inode correspond to foo, bar or a preexisting file?
Do you mind sharing the output of the following command?
debugfs -R "stat <3093>" /dev/${ext4_dev}
Hi Miklos,
I made a first attempt to reproduce the failure but did not get lucky.
> Inode 3093, i_blocks is 16, should be 8. Fix? yes
Does this inode correspond to foo, bar or a preexisting file?
Do you mind sharing the output of the following command?
debugfs -R "stat <3093>" /dev/${ext4_dev}
On 07/26/2017 12:13 PM, Måns Rullgård wrote:
> Florian Fainelli writes:
>
>> On 07/25/2017 06:29 AM, Måns Rullgård wrote:
>>> Marc Gonzalez writes:
>>>
On 25/07/2017 15:16, Måns Rullgård wrote:
> What happened to the patch
On 07/26/2017 12:13 PM, Måns Rullgård wrote:
> Florian Fainelli writes:
>
>> On 07/25/2017 06:29 AM, Måns Rullgård wrote:
>>> Marc Gonzalez writes:
>>>
On 25/07/2017 15:16, Måns Rullgård wrote:
> What happened to the patch adding the proper combined function?
It appears
On NUMA systems with dynamic processors, the content of the cpumask
may change over time. As new processors are added via DLPAR operations,
workqueues are created for them. Depending upon the order in which CPUs
are added/removed, we may run into problems with the content of the
cpumask used by
On NUMA systems with dynamic processors, the content of the cpumask
may change over time. As new processors are added via DLPAR operations,
workqueues are created for them. Depending upon the order in which CPUs
are added/removed, we may run into problems with the content of the
cpumask used by
This is useful for directly looking up a task based on class id rather than
having to scan through all open file descriptors.
Signed-off-by: Sasha Levin
---
Changes in V2:
- Addressed comments from Cong Wang (use nla_put_u32())
include/uapi/linux/inet_diag.h | 1
This is useful for directly looking up a task based on class id rather than
having to scan through all open file descriptors.
Signed-off-by: Sasha Levin
---
Changes in V2:
- Addressed comments from Cong Wang (use nla_put_u32())
include/uapi/linux/inet_diag.h | 1 +
net/ipv4/inet_diag.c
Hello!
Please see below for a prototype sys_membarrier() speedup patch.
Please note that there is some controversy on this subject, so the final
version will probably be quite a bit different than this prototype.
But my main question is whether the throttling shown below is acceptable
for your
Hello!
Please see below for a prototype sys_membarrier() speedup patch.
Please note that there is some controversy on this subject, so the final
version will probably be quite a bit different than this prototype.
But my main question is whether the throttling shown below is acceptable
for your
From: Kuppuswamy Sathyanarayanan
In iTCO_wdt_start() and iTCO_wdt_stop() functions, update_no_reboot_bit()
call has been made within io_lock spin lock context. But if the
update_no_reboot_bit() function is implemented by chipset/PMC driver
then we
From: Kuppuswamy Sathyanarayanan
In iTCO_wdt_start() and iTCO_wdt_stop() functions, update_no_reboot_bit()
call has been made within io_lock spin lock context. But if the
update_no_reboot_bit() function is implemented by chipset/PMC driver
then we can't be sure whether their implementation does
On 07/27/2017 11:01 AM, Salil Mehta wrote:
> Hi Florian,
>
>> -Original Message-
>> From: Florian Fainelli [mailto:f.faine...@gmail.com]
>> Sent: Sunday, July 23, 2017 6:05 PM
>> To: Salil Mehta; da...@davemloft.net
>> Cc: Zhuangyuzeng (Yisen); huangdaode; lipeng (Y);
>>
On 07/27/2017 11:01 AM, Salil Mehta wrote:
> Hi Florian,
>
>> -Original Message-
>> From: Florian Fainelli [mailto:f.faine...@gmail.com]
>> Sent: Sunday, July 23, 2017 6:05 PM
>> To: Salil Mehta; da...@davemloft.net
>> Cc: Zhuangyuzeng (Yisen); huangdaode; lipeng (Y);
>>
Hi Florian,
> -Original Message-
> From: Florian Fainelli [mailto:f.faine...@gmail.com]
> Sent: Sunday, July 23, 2017 6:05 PM
> To: Salil Mehta; da...@davemloft.net
> Cc: Zhuangyuzeng (Yisen); huangdaode; lipeng (Y);
> mehta.salil@gmail.com; net...@vger.kernel.org; linux-
>
Hi Florian,
> -Original Message-
> From: Florian Fainelli [mailto:f.faine...@gmail.com]
> Sent: Sunday, July 23, 2017 6:05 PM
> To: Salil Mehta; da...@davemloft.net
> Cc: Zhuangyuzeng (Yisen); huangdaode; lipeng (Y);
> mehta.salil@gmail.com; net...@vger.kernel.org; linux-
>
On Thu, 27 Jul 2017 17:17:48 +0100
"Daniel P. Berrange" wrote:
> On Wed, Jul 26, 2017 at 10:43:43AM -0600, Alex Williamson wrote:
> > [cc +libvir-list]
> >
> > On Wed, 26 Jul 2017 21:16:59 +0800
> > "Gao, Ping A" wrote:
> >
> > > The vfio-mdev
On Thu, 27 Jul 2017 17:17:48 +0100
"Daniel P. Berrange" wrote:
> On Wed, Jul 26, 2017 at 10:43:43AM -0600, Alex Williamson wrote:
> > [cc +libvir-list]
> >
> > On Wed, 26 Jul 2017 21:16:59 +0800
> > "Gao, Ping A" wrote:
> >
> > > The vfio-mdev provide the capability to let different guest
Hello, Michael.
On Thu, Jul 27, 2017 at 12:06:22PM -0500, Michael Bringmann wrote:
>
> On NUMA systems with dynamic processors, the content of the cpumask
> may change over time. As new processors are added via DLPAR operations,
> workqueues are created for them. Depending upon the order in
Hello, Michael.
On Thu, Jul 27, 2017 at 12:06:22PM -0500, Michael Bringmann wrote:
>
> On NUMA systems with dynamic processors, the content of the cpumask
> may change over time. As new processors are added via DLPAR operations,
> workqueues are created for them. Depending upon the order in
On Sun, May 21, 2017 at 11:51:39AM +0300, Konstantin Khlebnikov wrote:
> On 20.05.2017 19:42, Paul E. McKenney wrote:
> >On Fri, May 19, 2017 at 10:03:59AM +0300, Konstantin Khlebnikov wrote:
> >>This allows to get rid of unneeded invocations.
> >>
> >>Function debug_lockdep_rcu_enabled() becomes
On Sun, May 21, 2017 at 11:51:39AM +0300, Konstantin Khlebnikov wrote:
> On 20.05.2017 19:42, Paul E. McKenney wrote:
> >On Fri, May 19, 2017 at 10:03:59AM +0300, Konstantin Khlebnikov wrote:
> >>This allows to get rid of unneeded invocations.
> >>
> >>Function debug_lockdep_rcu_enabled() becomes
Hi Florian,
> -Original Message-
> From: Florian Fainelli [mailto:f.faine...@gmail.com]
> Sent: Sunday, July 23, 2017 5:54 PM
> To: Salil Mehta; da...@davemloft.net
> Cc: Zhuangyuzeng (Yisen); huangdaode; lipeng (Y);
> mehta.salil@gmail.com; net...@vger.kernel.org; linux-
>
Hi Florian,
> -Original Message-
> From: Florian Fainelli [mailto:f.faine...@gmail.com]
> Sent: Sunday, July 23, 2017 5:54 PM
> To: Salil Mehta; da...@davemloft.net
> Cc: Zhuangyuzeng (Yisen); huangdaode; lipeng (Y);
> mehta.salil@gmail.com; net...@vger.kernel.org; linux-
>
Em Thu, Jul 27, 2017 at 09:48:34AM +1000, Stephen Rothwell escreveu:
> Hi all,
>
> Commit
>
> 585d93c5ffcc ("perf annotate stdio: Fix --show-total-period")
>
> has no Signed-off-by for its author.
Ouch, my bad, will have this added to my git hooks...
- Arnaldo
Em Thu, Jul 27, 2017 at 09:48:34AM +1000, Stephen Rothwell escreveu:
> Hi all,
>
> Commit
>
> 585d93c5ffcc ("perf annotate stdio: Fix --show-total-period")
>
> has no Signed-off-by for its author.
Ouch, my bad, will have this added to my git hooks...
- Arnaldo
On 07/27/2017 01:46 PM, Roman Gushchin wrote:
> On Thu, Jul 27, 2017 at 01:38:55PM -0400, Waiman Long wrote:
>> On 07/27/2017 12:14 PM, Roman Gushchin wrote:
>>> Add a cgroup.stat interface to the base cgroup control files
>>> with the following metrics:
>>>
>>> nr_descendants total
On 07/27/2017 01:46 PM, Roman Gushchin wrote:
> On Thu, Jul 27, 2017 at 01:38:55PM -0400, Waiman Long wrote:
>> On 07/27/2017 12:14 PM, Roman Gushchin wrote:
>>> Add a cgroup.stat interface to the base cgroup control files
>>> with the following metrics:
>>>
>>> nr_descendants total
On 27.07.2017 15:54, Paolo Bonzini wrote:
> Since the current implementation of VMCS12 does a memcpy in and out
> of guest memory, we do not need current_vmcs12 and current_vmcs12_page
> anymore. current_vmptr is enough to read and write the VMCS12.
>
> Signed-off-by: Paolo Bonzini
On 27.07.2017 15:54, Paolo Bonzini wrote:
> Since the current implementation of VMCS12 does a memcpy in and out
> of guest memory, we do not need current_vmcs12 and current_vmcs12_page
> anymore. current_vmptr is enough to read and write the VMCS12.
>
> Signed-off-by: Paolo Bonzini
This looks
On 07/27/2017 01:18 PM, Magalhaes, Guilherme (Brazil R) wrote:
-Original Message-
From: Mimi Zohar [mailto:zo...@linux.vnet.ibm.com]
Sent: quinta-feira, 27 de julho de 2017 11:39
To: Magalhaes, Guilherme (Brazil R)
; Serge E. Hallyn
Cc:
On 07/27/2017 01:18 PM, Magalhaes, Guilherme (Brazil R) wrote:
-Original Message-
From: Mimi Zohar [mailto:zo...@linux.vnet.ibm.com]
Sent: quinta-feira, 27 de julho de 2017 11:39
To: Magalhaes, Guilherme (Brazil R)
; Serge E. Hallyn
Cc: Mehmet Kayaalp ; Yuqiong Sun
; containers ;
On Wed, Jul 26, 2017 at 6:08 PM, Ding Tianhong wrote:
>
>
> On 2017/7/27 2:26, Casey Leedom wrote:
>> By the way Ding, two issues:
>>
>> 1. Did we ever get any acknowledgement from either Intel or AMD
>> on this patch? I know that we can't ensure that, but it sure
On Wed, Jul 26, 2017 at 6:08 PM, Ding Tianhong wrote:
>
>
> On 2017/7/27 2:26, Casey Leedom wrote:
>> By the way Ding, two issues:
>>
>> 1. Did we ever get any acknowledgement from either Intel or AMD
>> on this patch? I know that we can't ensure that, but it sure would
>> be nice
On Thu, Jul 27, 2017 at 01:38:55PM -0400, Waiman Long wrote:
> On 07/27/2017 12:14 PM, Roman Gushchin wrote:
> > Add a cgroup.stat interface to the base cgroup control files
> > with the following metrics:
> >
> > nr_descendants total number of descendant cgroups
> >
On Thu, Jul 27, 2017 at 01:38:55PM -0400, Waiman Long wrote:
> On 07/27/2017 12:14 PM, Roman Gushchin wrote:
> > Add a cgroup.stat interface to the base cgroup control files
> > with the following metrics:
> >
> > nr_descendants total number of descendant cgroups
> >
| From: Ding Tianhong
| Sent: Wednesday, July 26, 2017 6:01 PM
|
| On 2017/7/27 3:05, Casey Leedom wrote:
| >
| > Ding, send me a note if you'd like me to work that [cxgb4vf patch] up
| > for you.
|
| Ok, you could send the change log and I could put it in the v8 version
| From: Ding Tianhong
| Sent: Wednesday, July 26, 2017 6:01 PM
|
| On 2017/7/27 3:05, Casey Leedom wrote:
| >
| > Ding, send me a note if you'd like me to work that [cxgb4vf patch] up
| > for you.
|
| Ok, you could send the change log and I could put it in the v8 version
| together, will you base
On 07/27/2017 12:14 PM, Roman Gushchin wrote:
> Add a cgroup.stat interface to the base cgroup control files
> with the following metrics:
>
> nr_descendantstotal number of descendant cgroups
> nr_dying_descendants total number of dying descendant cgroups
> max_descendant_depth
On 07/27/2017 12:14 PM, Roman Gushchin wrote:
> Add a cgroup.stat interface to the base cgroup control files
> with the following metrics:
>
> nr_descendantstotal number of descendant cgroups
> nr_dying_descendants total number of dying descendant cgroups
> max_descendant_depth
On Thu, Jul 27, 2017 at 7:15 AM, Tom Lendacky wrote:
>
> I can #ifdef the wbinvd based on whether AMD_MEM_ENCRYPT is configured
> or not so that the wbinvd is avoided if not configured.
I suspect an ifdef will be useless, since things like distro kernels
tend to enable
On Thu, Jul 27, 2017 at 7:15 AM, Tom Lendacky wrote:
>
> I can #ifdef the wbinvd based on whether AMD_MEM_ENCRYPT is configured
> or not so that the wbinvd is avoided if not configured.
I suspect an ifdef will be useless, since things like distro kernels
tend to enable everything.
So it should
On Wed, Jul 26, 2017 at 07:09:34PM -0400, Steven Rostedt wrote:
> On Wed, 26 Jul 2017 14:47:41 -0700
> "Paul E. McKenney" wrote:
>
>
> > > It is much lighter weight than a timer setup.
> >
> > How much lighter weight? In other words, what fraction of the
> >
On Wed, Jul 26, 2017 at 07:09:34PM -0400, Steven Rostedt wrote:
> On Wed, 26 Jul 2017 14:47:41 -0700
> "Paul E. McKenney" wrote:
>
>
> > > It is much lighter weight than a timer setup.
> >
> > How much lighter weight? In other words, what fraction of the
> > timers have to avoid being
Ram Pai writes:
> Store and restore the AMR, IAMR and UMOR register state of the task
> before scheduling out and after scheduling in, respectively.
>
> Signed-off-by: Ram Pai
s/UMOR/UAMOR/
> diff --git a/arch/powerpc/kernel/process.c
Ram Pai writes:
> Store and restore the AMR, IAMR and UMOR register state of the task
> before scheduling out and after scheduling in, respectively.
>
> Signed-off-by: Ram Pai
s/UMOR/UAMOR/
> diff --git a/arch/powerpc/kernel/process.c b/arch/powerpc/kernel/process.c
> index 2ad725e..9429361
On Thu, Jul 27, 2017 at 09:54:01AM -0700, Florian Fainelli wrote:
> On 07/27/2017 06:48 AM, Andrew Lunn wrote:
> > On Thu, Jul 27, 2017 at 09:02:16PM +0800, David Wu wrote:
> >> To make internal phy work, need to configure the phy_clock,
> >> phy cru_reset and related registers.
> >>
> >>
On Thu, Jul 27, 2017 at 09:54:01AM -0700, Florian Fainelli wrote:
> On 07/27/2017 06:48 AM, Andrew Lunn wrote:
> > On Thu, Jul 27, 2017 at 09:02:16PM +0800, David Wu wrote:
> >> To make internal phy work, need to configure the phy_clock,
> >> phy cru_reset and related registers.
> >>
> >>
On 07/26/2017 07:29 PM, Greg KH wrote:
On Wed, Jul 26, 2017 at 02:02:42PM -0700, David Daney wrote:
On 07/26/2017 01:08 PM, Greg KH wrote:
On Wed, Jul 26, 2017 at 01:02:38PM -0700, David Daney wrote:
On 07/26/2017 10:33 AM, Greg KH wrote:
On Wed, Jul 26, 2017 at 06:30:49PM +0200, Borislav
On 07/26/2017 07:29 PM, Greg KH wrote:
On Wed, Jul 26, 2017 at 02:02:42PM -0700, David Daney wrote:
On 07/26/2017 01:08 PM, Greg KH wrote:
On Wed, Jul 26, 2017 at 01:02:38PM -0700, David Daney wrote:
On 07/26/2017 10:33 AM, Greg KH wrote:
On Wed, Jul 26, 2017 at 06:30:49PM +0200, Borislav
On Thu, Jul 27, 2017 at 6:54 AM, Paolo Bonzini wrote:
> Since the current implementation of VMCS12 does a memcpy in and out
> of guest memory, we do not need current_vmcs12 and current_vmcs12_page
> anymore. current_vmptr is enough to read and write the VMCS12.
This patch
On Thu, Jul 27, 2017 at 6:54 AM, Paolo Bonzini wrote:
> Since the current implementation of VMCS12 does a memcpy in and out
> of guest memory, we do not need current_vmcs12 and current_vmcs12_page
> anymore. current_vmptr is enough to read and write the VMCS12.
This patch also fixes dirty
Coccinelle script to remove unnecessary static on local variables when
the variables are not used before update.
Signed-off-by: Gustavo A. R. Silva
---
scripts/coccinelle/misc/static_unnecessary.cocci | 89
1 file changed, 89 insertions(+)
Coccinelle script to remove unnecessary static on local variables when
the variables are not used before update.
Signed-off-by: Gustavo A. R. Silva
---
scripts/coccinelle/misc/static_unnecessary.cocci | 89
1 file changed, 89 insertions(+)
create mode 100644
> -Original Message-
> From: Mimi Zohar [mailto:zo...@linux.vnet.ibm.com]
> Sent: quinta-feira, 27 de julho de 2017 11:39
> To: Magalhaes, Guilherme (Brazil R)
> ; Serge E. Hallyn
> Cc: Mehmet Kayaalp ; Yuqiong
> -Original Message-
> From: Mimi Zohar [mailto:zo...@linux.vnet.ibm.com]
> Sent: quinta-feira, 27 de julho de 2017 11:39
> To: Magalhaes, Guilherme (Brazil R)
> ; Serge E. Hallyn
> Cc: Mehmet Kayaalp ; Yuqiong Sun
> ; containers foundation.org>; linux-kernel ; David Safford
> ; James
The s3c_i2sv2_probe() only enabled iis clock. Missing prepare isn't
probably fatal, because for SoC clocks this is usually no-op, but for
correctness this clock should be prepared.
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. New patch
---
The s3c_i2sv2_probe() only enabled iis clock. Missing prepare isn't
probably fatal, because for SoC clocks this is usually no-op, but for
correctness this clock should be prepared.
Signed-off-by: Krzysztof Kozlowski
---
Changes since v1:
1. New patch
---
sound/soc/samsung/s3c-i2s-v2.c | 2 +-
s3c2412_i2s_probe() might fail so driver has to revert work done by
s3c_i2sv2_probe() (clock enabling). Missing doing this would lead to
clock enable in-balance.
Signed-off-by: Krzysztof Kozlowski
---
Please, kindly test on S3C24xx hardware.
Changes since v1:
1. Drop clk
Commit 87b132bc0315 ("ASoC: samsung: s3c24{xx,12}-i2s: port to use
generic dmaengine API") moved ioremap() call from
s3c-i2s-v2.c:s3c_i2sv2_probe() to s3c2412-i2s.c:s3c2412_iis_dev_probe()
and converted it to devm- resource managed interface.
However the error path in first of them -
s3c2412_i2s_probe() might fail so driver has to revert work done by
s3c_i2sv2_probe() (clock enabling). Missing doing this would lead to
clock enable in-balance.
Signed-off-by: Krzysztof Kozlowski
---
Please, kindly test on S3C24xx hardware.
Changes since v1:
1. Drop clk assignment to
Commit 87b132bc0315 ("ASoC: samsung: s3c24{xx,12}-i2s: port to use
generic dmaengine API") moved ioremap() call from
s3c-i2s-v2.c:s3c_i2sv2_probe() to s3c2412-i2s.c:s3c2412_iis_dev_probe()
and converted it to devm- resource managed interface.
However the error path in first of them -
Hi,
Changes since v1:
1. Add patch 2/3.
2. Drop assignment of iis_cclk=iis_pclk to have balance with clk disables error
and remove paths (pointed by Arvind).
Best regards,
Krzysztof
Krzysztof Kozlowski (3):
ASoC: samsung: Fix possible double iounmap on s3c24xx driver probe
failure
Hi,
Changes since v1:
1. Add patch 2/3.
2. Drop assignment of iis_cclk=iis_pclk to have balance with clk disables error
and remove paths (pointed by Arvind).
Best regards,
Krzysztof
Krzysztof Kozlowski (3):
ASoC: samsung: Fix possible double iounmap on s3c24xx driver probe
failure
Hi Yury,
On Mon, Jul 24, 2017 at 02:26:24PM +0300, Yury Norov wrote:
> On Fri, Jul 07, 2017 at 06:11:36PM +0100, Catalin Marinas wrote:
> > On Fri, Jul 07, 2017 at 12:59:02AM +0300, Yury Norov wrote:
> > > If so, I would like to ask you to do the first ILP32 community poll
> > > now, not in 6
Hi Yury,
On Mon, Jul 24, 2017 at 02:26:24PM +0300, Yury Norov wrote:
> On Fri, Jul 07, 2017 at 06:11:36PM +0100, Catalin Marinas wrote:
> > On Fri, Jul 07, 2017 at 12:59:02AM +0300, Yury Norov wrote:
> > > If so, I would like to ask you to do the first ILP32 community poll
> > > now, not in 6
On NUMA systems with dynamic processors, the content of the cpumask
may change over time. As new processors are added via DLPAR operations,
workqueues are created for them. Depending upon the order in which CPUs
are added/removed, we may run into problems with the content of the
cpumask used by
On NUMA systems with dynamic processors, the content of the cpumask
may change over time. As new processors are added via DLPAR operations,
workqueues are created for them. Depending upon the order in which CPUs
are added/removed, we may run into problems with the content of the
cpumask used by
Sorry, I did try it. I must have forgotten to notify you of its success.
Will next post an updated patch using 'pr_warn_once'. It prints a message
during system initialization, by the way.
Thanks.
On 07/26/2017 02:16 PM, Tejun Heo wrote:
> On Wed, Jul 26, 2017 at 10:25:08AM -0500, Michael
Sorry, I did try it. I must have forgotten to notify you of its success.
Will next post an updated patch using 'pr_warn_once'. It prints a message
during system initialization, by the way.
Thanks.
On 07/26/2017 02:16 PM, Tejun Heo wrote:
> On Wed, Jul 26, 2017 at 10:25:08AM -0500, Michael
Checkpatch reported warnings for use of embedded function names.
Use __func__ instead of embedded function names.
Signed-off-by: Diwakar Sharma
---
drivers/staging/media/davinci_vpfe/dm365_ipipe.c | 10 +-
drivers/staging/media/davinci_vpfe/vpfe_mc_capture.c
Checkpatch reported warnings for use of embedded function names.
Use __func__ instead of embedded function names.
Signed-off-by: Diwakar Sharma
---
drivers/staging/media/davinci_vpfe/dm365_ipipe.c | 10 +-
drivers/staging/media/davinci_vpfe/vpfe_mc_capture.c | 8
2 files
On Thu, Jul 27, 2017 at 11:48:53AM -0400, Waiman Long wrote:
> atomic_long_sub_return_release() is implmented.
I've not had time to really thing about the problem at hand, but this I
can answer:
TSO (x86, s390, sparc): fully serialized
PPC: lwsync; ll/sc (RCpc)
ARM64: ll/sc-release
On Thu, Jul 27, 2017 at 11:48:53AM -0400, Waiman Long wrote:
> atomic_long_sub_return_release() is implmented.
I've not had time to really thing about the problem at hand, but this I
can answer:
TSO (x86, s390, sparc): fully serialized
PPC: lwsync; ll/sc (RCpc)
ARM64: ll/sc-release
Em Fri, Jul 28, 2017 at 01:16:02AM +0900, Taeung Song escreveu:
> Currently the toggle total period view on the annotate TUI
> shows the number of samples, not period like below.
> So fix the toggle total period view on the annotate TUI like below.
>
> $ perf annotate --show-total-period
>
>
Em Fri, Jul 28, 2017 at 01:16:02AM +0900, Taeung Song escreveu:
> Currently the toggle total period view on the annotate TUI
> shows the number of samples, not period like below.
> So fix the toggle total period view on the annotate TUI like below.
>
> $ perf annotate --show-total-period
>
>
On Thu, Jul 27, 2017 at 06:51:13PM +0200, Krzysztof Kozlowski wrote:
> On Thu, Jul 27, 2017 at 10:41:35AM +0530, Arvind Yadav wrote:
> > On Thursday 27 July 2017 12:27 AM, Krzysztof Kozlowski wrote:
> > Now s3c2412_i2s.iis_cclk and s3c2412_i2s.iis_pclk are holding "iis" clock.
> > Now no one
On Thu, Jul 27, 2017 at 06:51:13PM +0200, Krzysztof Kozlowski wrote:
> On Thu, Jul 27, 2017 at 10:41:35AM +0530, Arvind Yadav wrote:
> > On Thursday 27 July 2017 12:27 AM, Krzysztof Kozlowski wrote:
> > Now s3c2412_i2s.iis_cclk and s3c2412_i2s.iis_pclk are holding "iis" clock.
> > Now no one
Em Fri, Jul 28, 2017 at 01:15:56AM +0900, Taeung Song escreveu:
> When using --show-total-period or not,
> set the width value for first column.
>
> Suggested-by: Arnaldo Carvalho de Melo
> Cc: Namhyung Kim
> Cc: Jiri Olsa
>
Em Fri, Jul 28, 2017 at 01:15:56AM +0900, Taeung Song escreveu:
> When using --show-total-period or not,
> set the width value for first column.
>
> Suggested-by: Arnaldo Carvalho de Melo
> Cc: Namhyung Kim
> Cc: Jiri Olsa
> Signed-off-by: Taeung Song
> ---
> tools/perf/util/annotate.c | 4
501 - 600 of 1560 matches
Mail list logo