We can safely use the preempt-unsafe accessors for irqtime when we
flush its counters to kcpustat as IRQs are disabled at this time.
Cc: Rik van Riel
Cc: Paolo Bonzini
Cc: Wanpeng Li
Cc: Mike Galbraith
Cc: Peter
Introduce light versions of u64_stats helpers for context where
either preempt or IRQs are disabled. This way we can make this library
usable by scheduler irqtime accounting which currenty implement its
ad-hoc version.
Cc: Rik van Riel
Cc: Paolo Bonzini
Cc:
The callers of the functions performing irqtime kcpustat updates have
IRQS disabled, no need to disable them again.
Cc: Rik van Riel
Cc: Paolo Bonzini
Cc: Wanpeng Li
Cc: Mike Galbraith
Cc: Peter Zijlstra
We can safely use the preempt-unsafe accessors for irqtime when we
flush its counters to kcpustat as IRQs are disabled at this time.
Cc: Rik van Riel
Cc: Paolo Bonzini
Cc: Wanpeng Li
Cc: Mike Galbraith
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Eric Dumazet
Signed-off-by: Frederic Weisbecker
The callers of the functions performing irqtime kcpustat updates have
IRQS disabled, no need to disable them again.
Cc: Rik van Riel
Cc: Paolo Bonzini
Cc: Wanpeng Li
Cc: Mike Galbraith
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Eric Dumazet
Signed-off-by: Frederic Weisbecker
---
Introduce light versions of u64_stats helpers for context where
either preempt or IRQs are disabled. This way we can make this library
usable by scheduler irqtime accounting which currenty implement its
ad-hoc version.
Cc: Rik van Riel
Cc: Paolo Bonzini
Cc: Wanpeng Li
Cc: Mike Galbraith
Cc:
The code performing irqtime nsecs stats flushing to kcpustat is roughly
the same for hardirq and softirq. So lets consolidate that common code.
Cc: Rik van Riel
Cc: Paolo Bonzini
Cc: Wanpeng Li
Cc: Mike Galbraith
Cc:
The code performing irqtime nsecs stats flushing to kcpustat is roughly
the same for hardirq and softirq. So lets consolidate that common code.
Cc: Rik van Riel
Cc: Paolo Bonzini
Cc: Wanpeng Li
Cc: Mike Galbraith
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Eric Dumazet
Signed-off-by: Frederic
On 09/02/2016 05:49 AM, Jens Wiklander wrote:
> On Thu, Sep 01, 2016 at 01:06:04PM -0500, Andrew F. Davis wrote:
>> On 09/01/2016 04:22 AM, Jens Wiklander wrote:
>>> On Wed, Aug 31, 2016 at 11:40:20AM -0500, Andrew F. Davis wrote:
On 08/31/2016 08:50 AM, Jens Wiklander wrote:
> On Tue,
On 09/02/2016 05:49 AM, Jens Wiklander wrote:
> On Thu, Sep 01, 2016 at 01:06:04PM -0500, Andrew F. Davis wrote:
>> On 09/01/2016 04:22 AM, Jens Wiklander wrote:
>>> On Wed, Aug 31, 2016 at 11:40:20AM -0500, Andrew F. Davis wrote:
On 08/31/2016 08:50 AM, Jens Wiklander wrote:
> On Tue,
The irqtime accounting currently implement its own ad hoc implementation
of u64_stats API. Lets rather consolidate it with the appropriate
library.
Cc: Rik van Riel
Cc: Paolo Bonzini
Cc: Wanpeng Li
Cc: Mike Galbraith
This series contains a few optimizations against irq disabling, and the
rest is consolidation.
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
sched/irqtime
HEAD: 63024a0947091e0a20bafa33b685ae33c275
Thanks,
Frederic
---
Frederic Weisbecker (5):
The irqtime accounting currently implement its own ad hoc implementation
of u64_stats API. Lets rather consolidate it with the appropriate
library.
Cc: Rik van Riel
Cc: Paolo Bonzini
Cc: Wanpeng Li
Cc: Mike Galbraith
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc: Eric Dumazet
Signed-off-by:
This series contains a few optimizations against irq disabling, and the
rest is consolidation.
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
sched/irqtime
HEAD: 63024a0947091e0a20bafa33b685ae33c275
Thanks,
Frederic
---
Frederic Weisbecker (5):
Detect hugetlbfs. hugetlbfs__mountpoint() will be used during recording
to help recorder identifying hugetlb mmaps: which should be recognized
as anon mapping.
Signed-off-by: Wang Nan
Cc: Hou Pengyang
Cc: He Kuang
Cc: Arnaldo
The requirement of this function is first proposed at 2015.
Please refer to
http://lkml.iu.edu/hypermail/linux/kernel/1506.2/02372.html
http://lkml.iu.edu/hypermail/linux/kernel/1506.3/02290.html
http://lkml.iu.edu/hypermail/linux/kernel/1506.3/03512.html
For systems which use hugetlbfs, if a
During synthesizing mmap events, add MAP_HUGETLB map flag if the
source of mapping is file in hugetlbfs.
After this patch, perf can identify hugetlb mapping even if perf
is started after the mapping of huge pages (like perf top).
Signed-off-by: Wang Nan
Cc: Hou Pengyang
Hugetlbfs mapping should be recognized as anon mapping so user has
a chance to create /tmp/perf-.map file for symbol resolving. This
patch utilizes MAP_HUGETLB to identify hugetlb mapping.
After this patch, if perf is started before the program uses huge pages
starting, perf is able to recognize
Detect hugetlbfs. hugetlbfs__mountpoint() will be used during recording
to help recorder identifying hugetlb mmaps: which should be recognized
as anon mapping.
Signed-off-by: Wang Nan
Cc: Hou Pengyang
Cc: He Kuang
Cc: Arnaldo Carvalho de Melo
---
tools/lib/api/fs/fs.c | 15 +++
The requirement of this function is first proposed at 2015.
Please refer to
http://lkml.iu.edu/hypermail/linux/kernel/1506.2/02372.html
http://lkml.iu.edu/hypermail/linux/kernel/1506.3/02290.html
http://lkml.iu.edu/hypermail/linux/kernel/1506.3/03512.html
For systems which use hugetlbfs, if a
During synthesizing mmap events, add MAP_HUGETLB map flag if the
source of mapping is file in hugetlbfs.
After this patch, perf can identify hugetlb mapping even if perf
is started after the mapping of huge pages (like perf top).
Signed-off-by: Wang Nan
Cc: Hou Pengyang
Cc: He Kuang
Cc:
Hugetlbfs mapping should be recognized as anon mapping so user has
a chance to create /tmp/perf-.map file for symbol resolving. This
patch utilizes MAP_HUGETLB to identify hugetlb mapping.
After this patch, if perf is started before the program uses huge pages
starting, perf is able to recognize
On Fri, Sep 02, 2016 at 07:25:31PM +0530, Hari Bathini wrote:
> >I'm thinking this value is mostly the same for tasks, just like COMM and
>
> I think so, too. Namespaces aren't changed that often for tasks...
>
> >MMAP. Could we therefore not emit (sideband) events whenever a task
> >changes
On 02/09/16 13:34, Rob Herring wrote:
> On Fri, Aug 26, 2016 at 04:37:10PM +0100, Paul Burton wrote:
>> Document a binding for the MIPS Cluster Power Controller (CPC) which
>> simply allows the device tree to specify where the CPC registers should
>> be mapped.
>>
>> Signed-off-by: Paul Burton
On Fri, Sep 02, 2016 at 07:25:31PM +0530, Hari Bathini wrote:
> >I'm thinking this value is mostly the same for tasks, just like COMM and
>
> I think so, too. Namespaces aren't changed that often for tasks...
>
> >MMAP. Could we therefore not emit (sideband) events whenever a task
> >changes
On 02/09/16 13:34, Rob Herring wrote:
> On Fri, Aug 26, 2016 at 04:37:10PM +0100, Paul Burton wrote:
>> Document a binding for the MIPS Cluster Power Controller (CPC) which
>> simply allows the device tree to specify where the CPC registers should
>> be mapped.
>>
>> Signed-off-by: Paul Burton
>>
On Thursday 01 September 2016 02:39 PM, Peter Zijlstra wrote:
On Tue, Aug 30, 2016 at 09:57:02PM +0530, Hari Bathini wrote:
Currently, there is no mechanism to filter events based on containers.
perf -G can be used, but it will not filter events for the containers
created after perf is
On Thursday 01 September 2016 02:39 PM, Peter Zijlstra wrote:
On Tue, Aug 30, 2016 at 09:57:02PM +0530, Hari Bathini wrote:
Currently, there is no mechanism to filter events based on containers.
perf -G can be used, but it will not filter events for the containers
created after perf is
On Wed, 10 Aug 2016, Craig Gallek wrote:
> On Tue, Jul 26, 2016 at 10:25 AM, Craig Gallek wrote:
> > From: Craig Gallek
> >
> > Add struct kobject to struct irq_desc to allow for easy export
> > to sysfs. This allows for much simpler userspace-parsing
On Wed, 10 Aug 2016, Craig Gallek wrote:
> On Tue, Jul 26, 2016 at 10:25 AM, Craig Gallek wrote:
> > From: Craig Gallek
> >
> > Add struct kobject to struct irq_desc to allow for easy export
> > to sysfs. This allows for much simpler userspace-parsing of
> > the information contained in struct
On 31/08/2016 19:05, Luiz Capitulino wrote:
> Memory and debugfs entries are leaked on error. Fix it.
>
> Signed-off-by: Luiz Capitulino
> ---
> virt/kvm/kvm_main.c | 10 +++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/virt/kvm/kvm_main.c
On 31/08/2016 19:05, Luiz Capitulino wrote:
> Memory and debugfs entries are leaked on error. Fix it.
>
> Signed-off-by: Luiz Capitulino
> ---
> virt/kvm/kvm_main.c | 10 +++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
>
On 31/08/2016 19:05, Luiz Capitulino wrote:
> kvm_arch_create_vm_debugfs() allows arch specific code to
> create entries in the VM's directory in debugfs. x86 will
> implement support for this in the next commit.
>
> Signed-off-by: Luiz Capitulino
> ---
>
On 31/08/2016 19:05, Luiz Capitulino wrote:
> kvm_arch_create_vm_debugfs() allows arch specific code to
> create entries in the VM's directory in debugfs. x86 will
> implement support for this in the next commit.
>
> Signed-off-by: Luiz Capitulino
> ---
> arch/arm/kvm/arm.c | 5 +
On Fri, Sep 2, 2016 at 5:41 AM, Sekhar Nori wrote:
> + Robert Nelson
>
> On Friday 02 September 2016 02:36 PM, Nishanth Menon wrote:
>
> I understand that there are existing users of A2 boards and so we simply
> cannot remove support for those boards (at least yet).
>
> But given
On Fri, 2016-09-02 at 15:44 +0300, Ebru Akagunduz wrote:
> Currently, khugepaged does not let swapin, if there is no
> enough young pages in a THP. The problem is when a THP does
> not have enough young page, khugepaged leaks mapped ptes.
>
> This patch prohibits leaking mapped ptes.
>
>
On Fri, Sep 2, 2016 at 5:41 AM, Sekhar Nori wrote:
> + Robert Nelson
>
> On Friday 02 September 2016 02:36 PM, Nishanth Menon wrote:
>
> I understand that there are existing users of A2 boards and so we simply
> cannot remove support for those boards (at least yet).
>
> But given the small
On Fri, 2016-09-02 at 15:44 +0300, Ebru Akagunduz wrote:
> Currently, khugepaged does not let swapin, if there is no
> enough young pages in a THP. The problem is when a THP does
> not have enough young page, khugepaged leaks mapped ptes.
>
> This patch prohibits leaking mapped ptes.
>
>
On 31/08/2016 19:05, Luiz Capitulino wrote:
> This make it possible to call kvm_destroy_vm_debugfs() from
> kvm_create_vm_debugfs() in error conditions.
>
> Signed-off-by: Luiz Capitulino
> ---
> virt/kvm/kvm_main.c | 8 +---
> 1 file changed, 5 insertions(+), 3
On 31/08/2016 19:05, Luiz Capitulino wrote:
> This make it possible to call kvm_destroy_vm_debugfs() from
> kvm_create_vm_debugfs() in error conditions.
>
> Signed-off-by: Luiz Capitulino
> ---
> virt/kvm/kvm_main.c | 8 +---
> 1 file changed, 5 insertions(+), 3 deletions(-)
>
> diff
Hello,
On Fri, Sep 02, 2016 at 09:17:04AM +0800, qiaozhou wrote:
> > > I don't know whether it's meaningful to still check pending work here, or
> > > it's not suggested to use pm_qos_update_request in this early boot up
> > > phase.
> > > Could you help to share some opinions? (I can fix this
Hello,
On Fri, Sep 02, 2016 at 09:17:04AM +0800, qiaozhou wrote:
> > > I don't know whether it's meaningful to still check pending work here, or
> > > it's not suggested to use pm_qos_update_request in this early boot up
> > > phase.
> > > Could you help to share some opinions? (I can fix this
On 02/09/2016 15:31, Roman Kagan wrote:
> >
> > - if (!vcpu->pv_time_enabled)
> > - return 0;
>
> Strictly speaking, you only need .hv_clock updated if either kvmclock or
> tsc_ref_page is enabled, so you may want to still skip the calculations
> otherwise.
Yeah, but that's
On 02/09/2016 15:31, Roman Kagan wrote:
> >
> > - if (!vcpu->pv_time_enabled)
> > - return 0;
>
> Strictly speaking, you only need .hv_clock updated if either kvmclock or
> tsc_ref_page is enabled, so you may want to still skip the calculations
> otherwise.
Yeah, but that's
On Wed, Aug 31, 2016 at 01:05:45PM -0400, Luiz Capitulino wrote:
> We need to retrieve a VM's TSC offset in order to use
> the host's TSC to merge host and guest traces. This is
> explained in detail in this thread:
>
> [Qemu-devel] [RFC] host and guest kernel trace merging
>
On Wed, Aug 31, 2016 at 01:05:45PM -0400, Luiz Capitulino wrote:
> We need to retrieve a VM's TSC offset in order to use
> the host's TSC to merge host and guest traces. This is
> explained in detail in this thread:
>
> [Qemu-devel] [RFC] host and guest kernel trace merging
>
On 09/01/16 17:51, Joe Perches wrote:
> On Fri, 2016-09-02 at 00:47 +, Bart Van Assche wrote:
>> On 09/01/16 13:11, Joe Perches wrote:
>>>
>>> Assigning an int to a bitfield:1 can lose precision.
>>> Change the caller argument uses from 1/0 to true/false.
>> Hello Joe,
>
> Hi Bart.
>
>> Can
On 09/01/16 17:51, Joe Perches wrote:
> On Fri, 2016-09-02 at 00:47 +, Bart Van Assche wrote:
>> On 09/01/16 13:11, Joe Perches wrote:
>>>
>>> Assigning an int to a bitfield:1 can lose precision.
>>> Change the caller argument uses from 1/0 to true/false.
>> Hello Joe,
>
> Hi Bart.
>
>> Can
Hi Laura,
On Thu, Sep 01, 2016 at 03:40:41PM -0700, Laura Abbott wrote:
There is no advantage to having heap types be a mask. The ion client has
long since dropped the mask. Drop the notion of heap type masks as well.
I know this is the same patch you sent last time, so sorry for not
Hi Laura,
On Thu, Sep 01, 2016 at 03:40:41PM -0700, Laura Abbott wrote:
There is no advantage to having heap types be a mask. The ion client has
long since dropped the mask. Drop the notion of heap type masks as well.
I know this is the same patch you sent last time, so sorry for not
On 09/01/2016 11:02 PM, Greg Kroah-Hartman wrote:
On Wed, Aug 24, 2016 at 03:19:21PM +0700, Ivan Safonov wrote:
Driver does not use this function.
Signed-off-by: Ivan Safonov
---
drivers/staging/rtl8188eu/core/rtw_ieee80211.c | 47 --
On 09/01/2016 11:02 PM, Greg Kroah-Hartman wrote:
On Wed, Aug 24, 2016 at 03:19:21PM +0700, Ivan Safonov wrote:
Driver does not use this function.
Signed-off-by: Ivan Safonov
---
drivers/staging/rtl8188eu/core/rtw_ieee80211.c | 47 --
On 09/02/2016 03:46 AM, Naohiro Aota wrote:
Currently, btrfs_relocate_chunk() is removing relocated BG by itself. But
the work can be done by btrfs_delete_unused_bgs() (and it's better since it
trim the BG). Let's dedupe the code.
While btrfs_delete_unused_bgs() is already hitting the relocated
On 09/02/2016 03:46 AM, Naohiro Aota wrote:
Currently, btrfs_relocate_chunk() is removing relocated BG by itself. But
the work can be done by btrfs_delete_unused_bgs() (and it's better since it
trim the BG). Let's dedupe the code.
While btrfs_delete_unused_bgs() is already hitting the relocated
On 02/09/16 13:54, Rob Herring wrote:
> On Tue, Aug 30, 2016 at 04:53:01PM +0100, Paul Burton wrote:
>> On 26/08/16 18:44, Stephen Boyd wrote:
>>> On 08/26, Paul Burton wrote:
diff --git a/Documentation/devicetree/bindings/clock/img,boston-clock.txt
On 02/09/16 13:54, Rob Herring wrote:
> On Tue, Aug 30, 2016 at 04:53:01PM +0100, Paul Burton wrote:
>> On 26/08/16 18:44, Stephen Boyd wrote:
>>> On 08/26, Paul Burton wrote:
diff --git a/Documentation/devicetree/bindings/clock/img,boston-clock.txt
On 02/09/16 11:06, Zubair Lutfullah Kakakhel wrote:
> Hi,
>
> On 09/02/2016 07:25 AM, Michal Simek wrote:
>> On 1.9.2016 18:50, Zubair Lutfullah Kakakhel wrote:
>>> The Xilinx AXI Interrupt Controller IP block is used by the MIPS
>>> based xilfpga platform.
>>>
>>> Move the interrupt controller
On 02/09/16 11:06, Zubair Lutfullah Kakakhel wrote:
> Hi,
>
> On 09/02/2016 07:25 AM, Michal Simek wrote:
>> On 1.9.2016 18:50, Zubair Lutfullah Kakakhel wrote:
>>> The Xilinx AXI Interrupt Controller IP block is used by the MIPS
>>> based xilfpga platform.
>>>
>>> Move the interrupt controller
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp/hotplug
head: 6dc465457fac9a49462bebbb870beea5d536b7c2
commit: 6dc465457fac9a49462bebbb870beea5d536b7c2 [8/8] net/virtio-net: Convert
to hotplug state machine
config: x86_64-allmodconfig (attached as .config)
compiler:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp/hotplug
head: 6dc465457fac9a49462bebbb870beea5d536b7c2
commit: 6dc465457fac9a49462bebbb870beea5d536b7c2 [8/8] net/virtio-net: Convert
to hotplug state machine
config: x86_64-allmodconfig (attached as .config)
compiler:
Hi Michal, Zubair,
On Fri, Sep 02, 2016 at 12:27:54PM +0200, Michal Simek wrote:
> On 2.9.2016 12:06, Zubair Lutfullah Kakakhel wrote:
> > On 09/02/2016 07:25 AM, Michal Simek wrote:
...
> >> Also there is another copy of this driver in the tree which was using
> >> old ppc405 and ppc440 xilinx
Hi Michal, Zubair,
On Fri, Sep 02, 2016 at 12:27:54PM +0200, Michal Simek wrote:
> On 2.9.2016 12:06, Zubair Lutfullah Kakakhel wrote:
> > On 09/02/2016 07:25 AM, Michal Simek wrote:
...
> >> Also there is another copy of this driver in the tree which was using
> >> old ppc405 and ppc440 xilinx
Hi Dave,
On Thu, 2016-09-01 at 09:57 +0800, Dave Young wrote:
> On 08/30/16 at 06:40pm, Mimi Zohar wrote:
> > + * Called during kexec_file_load so that IMA can add a segment to the kexec
> > + * image for the measurement list for the next kernel.
> > + */
> > +void ima_add_kexec_buffer(struct
Hi Dave,
On Thu, 2016-09-01 at 09:57 +0800, Dave Young wrote:
> On 08/30/16 at 06:40pm, Mimi Zohar wrote:
> > + * Called during kexec_file_load so that IMA can add a segment to the kexec
> > + * image for the measurement list for the next kernel.
> > + */
> > +void ima_add_kexec_buffer(struct
On Fri, Sep 02, 2016 at 02:06:43PM +0200, Oleg Nesterov wrote:
> Yes, I considered this option, but to me the addtional finish_wait()
> looks simpler.
its all relative, this stuff always makes my head hurt one way or the
other ;-)
> And, if you agree with this change I will try to change
On Fri, Sep 02, 2016 at 02:06:43PM +0200, Oleg Nesterov wrote:
> Yes, I considered this option, but to me the addtional finish_wait()
> looks simpler.
its all relative, this stuff always makes my head hurt one way or the
other ;-)
> And, if you agree with this change I will try to change
[ Added Cc to hrtimer maintainer ]
On Fri, 2 Sep 2016 18:07:31 +0530
Binoy Jayan wrote:
> Generate a histogram of the latencies of delayed timer offsets in
> nanoseconds. It shows the latency captured due to a delayed timer expire
> event. It happens for example when a
[ Added Cc to hrtimer maintainer ]
On Fri, 2 Sep 2016 18:07:31 +0530
Binoy Jayan wrote:
> Generate a histogram of the latencies of delayed timer offsets in
> nanoseconds. It shows the latency captured due to a delayed timer expire
> event. It happens for example when a timer misses its
On Fri, Sep 02, 2016 at 02:55:34PM +0200, Arnd Bergmann wrote:
> On Friday, September 2, 2016 6:46:19 PM CEST Bamvor Jian Zhang wrote:
> > diff --git a/arch/arm64/include/uapi/asm/unistd.h
> > b/arch/arm64/include/uapi/asm/unistd.h
> > index 043d17a..78bea1d 100644
> > ---
On Fri, Sep 02, 2016 at 02:55:34PM +0200, Arnd Bergmann wrote:
> On Friday, September 2, 2016 6:46:19 PM CEST Bamvor Jian Zhang wrote:
> > diff --git a/arch/arm64/include/uapi/asm/unistd.h
> > b/arch/arm64/include/uapi/asm/unistd.h
> > index 043d17a..78bea1d 100644
> > ---
On Fri, 2 Sep 2016, Ghannam, Yazen wrote:
> > > The Socket ID is ApicId[bits] on Fam17h systems.
> > >
> > > Change substraction to logical AND when extracting socket_id
> > > from c->apicid.
> >
> > So Fam17h will only ever have 2 sockets, right?
> >
>
> This is the decoding of the ApicId
On Fri, 2 Sep 2016, Ghannam, Yazen wrote:
> > > The Socket ID is ApicId[bits] on Fam17h systems.
> > >
> > > Change substraction to logical AND when extracting socket_id
> > > from c->apicid.
> >
> > So Fam17h will only ever have 2 sockets, right?
> >
>
> This is the decoding of the ApicId
fixed comment style and space indent report from checkpatch
in rtl8712/rtl871x_ioctl_linux.c:
* WARNING: Statements should start on a tabstop
* WARNING: Block comments use * on subsequent lines
* WARNING: suspect code indent for conditional statements (16, 32)
Signed-off-by: Louie Lu
fixed comment style and space indent report from checkpatch
in rtl8712/rtl871x_ioctl_linux.c:
* WARNING: Statements should start on a tabstop
* WARNING: Block comments use * on subsequent lines
* WARNING: suspect code indent for conditional statements (16, 32)
Signed-off-by: Louie Lu
---
On Fri, 2 Sep 2016 18:07:30 +0530
Binoy Jayan wrote:
> This work is based on work by Daniel Wagner. A few tracepoints are added
> at the end of the critical section. With the hist trigger in place, the
> hist trigger plots may be generated, with per-cpu breakdown of
On Fri, 2 Sep 2016 18:07:30 +0530
Binoy Jayan wrote:
> This work is based on work by Daniel Wagner. A few tracepoints are added
> at the end of the critical section. With the hist trigger in place, the
> hist trigger plots may be generated, with per-cpu breakdown of events
> captured. It is
On Fri, 02 Sep 2016 14:34:47 +0200,
Vegard Nossum wrote:
>
> On 08/29/2016 09:14 AM, Vegard Nossum wrote:
> > On 08/29/2016 09:02 AM, Takashi Iwai wrote:
> >> On Mon, 29 Aug 2016 00:33:49 +0200,
> >> Vegard Nossum wrote:
> >>> @@ -1602,15 +1602,25 @@ static int snd_timer_user_tselect(struct file
On Fri, 02 Sep 2016 14:34:47 +0200,
Vegard Nossum wrote:
>
> On 08/29/2016 09:14 AM, Vegard Nossum wrote:
> > On 08/29/2016 09:02 AM, Takashi Iwai wrote:
> >> On Mon, 29 Aug 2016 00:33:49 +0200,
> >> Vegard Nossum wrote:
> >>> @@ -1602,15 +1602,25 @@ static int snd_timer_user_tselect(struct file
On Friday, September 2, 2016 12:55:33 PM CEST Robin Murphy wrote:
>
> Huh? There's only no DMA description in DT if the device can be assumed
> to be happy with the defaults. Anything else should be using
> "dma-ranges", "dma-coherent", etc. to describe non-default integration
> aspects. For
On Friday, September 2, 2016 12:55:33 PM CEST Robin Murphy wrote:
>
> Huh? There's only no DMA description in DT if the device can be assumed
> to be happy with the defaults. Anything else should be using
> "dma-ranges", "dma-coherent", etc. to describe non-default integration
> aspects. For
On Thu, 1 Sep 2016, Marc Zyngier wrote:
> On 01/09/16 09:15, majun (F) wrote:
> Well, this issue goes way beyond the hack you wanted to add to the
> generic code, and it should probably be addressed in the GIC code
> itself, as an implementation specific workaround. Without knowing the
> details
On Thu, 1 Sep 2016, Marc Zyngier wrote:
> On 01/09/16 09:15, majun (F) wrote:
> Well, this issue goes way beyond the hack you wanted to add to the
> generic code, and it should probably be addressed in the GIC code
> itself, as an implementation specific workaround. Without knowing the
> details
On Fri, 2 Sep 2016 18:07:29 +0530
Binoy Jayan wrote:
> The field 'cpu' although part of the set of generic fields, is not made
> part of the key fields when mentioned in the trigger command. This hack
> suggested by Daniel marks it as one of the key fields and make it
On Fri, 2 Sep 2016 18:07:29 +0530
Binoy Jayan wrote:
> The field 'cpu' although part of the set of generic fields, is not made
> part of the key fields when mentioned in the trigger command. This hack
> suggested by Daniel marks it as one of the key fields and make it appear
> in the histogram
On Fri, Sep 02, 2016 at 09:04:29PM +0800, Louie Lu wrote:
> 2016-09-02 20:55 GMT+08:00 Greg KH :
> > On Fri, Sep 02, 2016 at 06:16:10PM +0800, Louie Lu wrote:
> >> fixed comment style and space indent report from checkpatch:
> >>
> >> * WARNING: Statements should start
On Fri, Sep 02, 2016 at 09:04:29PM +0800, Louie Lu wrote:
> 2016-09-02 20:55 GMT+08:00 Greg KH :
> > On Fri, Sep 02, 2016 at 06:16:10PM +0800, Louie Lu wrote:
> >> fixed comment style and space indent report from checkpatch:
> >>
> >> * WARNING: Statements should start on a tabstop
> >> * WARNING:
2016-09-02 20:55 GMT+08:00 Greg KH :
> On Fri, Sep 02, 2016 at 06:16:10PM +0800, Louie Lu wrote:
>> fixed comment style and space indent report from checkpatch:
>>
>> * WARNING: Statements should start on a tabstop
>> * WARNING: Block comments use * on subsequent lines
2016-09-02 20:55 GMT+08:00 Greg KH :
> On Fri, Sep 02, 2016 at 06:16:10PM +0800, Louie Lu wrote:
>> fixed comment style and space indent report from checkpatch:
>>
>> * WARNING: Statements should start on a tabstop
>> * WARNING: Block comments use * on subsequent lines
>> * WARNING: suspect code
Hi Tobias,
Would you help fix these errors? They are still in v4.8-rc4 kernel.
Thanks,
Fengguang
On Mon, Aug 08, 2016 at 04:19:10PM +0800, kbuild test robot wrote:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head:
Hi Tobias,
Would you help fix these errors? They are still in v4.8-rc4 kernel.
Thanks,
Fengguang
On Mon, Aug 08, 2016 at 04:19:10PM +0800, kbuild test robot wrote:
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head:
These functions were only mentioned in the rtw_proc_init_one()
function in drivers/staging/rtl8188eu/os_dep/os_intfs.c, which was
under #if 0 and has now been removed completely.
As they are not used anywhere, and also violate the coding style
rules, remove them.
Signed-off-by: Luca Ceresoli
Hi Sudeep,
Thank you for your comments.
>
> I understand the warning we get but the patch is completely wrong.
> One it removes the feature of adding/removing the cache devices on cpu
> hotplug events. Have you tested your patch with simple cpu hotplug and seen no
> change before and after this
These functions were only mentioned in the rtw_proc_init_one()
function in drivers/staging/rtl8188eu/os_dep/os_intfs.c, which was
under #if 0 and has now been removed completely.
As they are not used anywhere, and also violate the coding style
rules, remove them.
Signed-off-by: Luca Ceresoli
Hi Sudeep,
Thank you for your comments.
>
> I understand the warning we get but the patch is completely wrong.
> One it removes the feature of adding/removing the cache devices on cpu
> hotplug events. Have you tested your patch with simple cpu hotplug and seen no
> change before and after this
These functions have been declared without any implementation since
the first commit (58c434013a22fccfdb14abc2bb8408ca29073b76) and there
has been no mention of them in following commits.
Signed-off-by: Luca Ceresoli
Cc: Greg Kroah-Hartman
Cc:
These functions have been declared without any implementation since
the first commit (58c434013a22fccfdb14abc2bb8408ca29073b76) and there
has been no mention of them in following commits.
Signed-off-by: Luca Ceresoli
Cc: Greg Kroah-Hartman
Cc: Kyle Kuffermann
Cc: de...@driverdev.osuosl.org
Cc:
rtw_proc_init_one() and rtw_proc_remove_one() are two very long
functions that are supposed to create a bunch of proc entries to
access debugging features of the driver.
But both of them are under #if 0 since their first commit three years
ago (5adef66acf73705ae95ea0b1e6b5fc7f17d82d30), replaced
Since the removal of rtw_proc_init_one() the proc filesystem is not
mentioned in this driver. So this include becomes useless.
Signed-off-by: Luca Ceresoli
Cc: Greg Kroah-Hartman
Cc: Arnd Bergmann
Cc: Binoy Jayan
These functions have been declared without any implementation since
the first commit (364e30ebd2dbaccba430c603da03e68746eb932a) and there
has been no mention of them in following commits.
Signed-off-by: Luca Ceresoli
Cc: Larry Finger
Cc: Jes
This function is only used inside rtw_recv.c. Which is quite logical,
since it's a timer callback: it is passed as the _fn argument to
setup_timer(). So it is internal to rtw_recv.c and should be static.
Signed-off-by: Luca Ceresoli
Cc: Greg Kroah-Hartman
801 - 900 of 1388 matches
Mail list logo