Hi Jiri,
> Both vhci_get_user and vhci_release race with open_timeout work. They
> both contain cancel_delayed_work_sync, but do not test whether the
> work actually created hdev or not. Since the work can be in progress
> and _sync will wait for finishing it, we can have data->hdev allocated
>
Hi Jiri,
> Both vhci_get_user and vhci_release race with open_timeout work. They
> both contain cancel_delayed_work_sync, but do not test whether the
> work actually created hdev or not. Since the work can be in progress
> and _sync will wait for finishing it, we can have data->hdev allocated
>
On Fri, 8 Apr 2016, Andy Shevchenko wrote:
> On Fri, Apr 8, 2016 at 6:34 PM, wrote:
> >> On Thu, Apr 7, 2016 at 2:39 PM, Andy Shevchenko
> >> wrote:
> >> > On Mon, Apr 4, 2016 at 11:26 PM, Martin Brandenburg
> >> > wrote:
>
On Fri, 8 Apr 2016, Andy Shevchenko wrote:
> On Fri, Apr 8, 2016 at 6:34 PM, wrote:
> >> On Thu, Apr 7, 2016 at 2:39 PM, Andy Shevchenko
> >> wrote:
> >> > On Mon, Apr 4, 2016 at 11:26 PM, Martin Brandenburg
> >> > wrote:
> >> >> From: Martin Brandenburg
> >> >>
> >> >> Almost everywhere we
Hi,
Am Mittwoch, 6. April 2016, 16:38:22 schrieb Sugar Zhang:
> There are 3 i2s sdio pins, which iomux mode is as follows:
>
> - sdi3_sdo1
> - sdi2_sdo2
> - sdi1_sdo3
>
> we need to configure these pins' iomux mode via the GRF register
> when use multi channel playback/capture.
>
>
Hi,
Am Mittwoch, 6. April 2016, 16:38:22 schrieb Sugar Zhang:
> There are 3 i2s sdio pins, which iomux mode is as follows:
>
> - sdi3_sdo1
> - sdi2_sdo2
> - sdi1_sdo3
>
> we need to configure these pins' iomux mode via the GRF register
> when use multi channel playback/capture.
>
>
On 08/04/2016 18:00, Andy Lutomirski wrote:
> But %ss can be loaded with 0 on 64-bit kernels. (I assume that
> loading 0 into %ss sets SS.DPL to 0 if done at CPL0, but I'm vague on
> this, since it only really matters to hypervisor code AFAIK.)
It's even simpler, unless CPL=0 SS cannot be
On 08/04/2016 18:00, Andy Lutomirski wrote:
> But %ss can be loaded with 0 on 64-bit kernels. (I assume that
> loading 0 into %ss sets SS.DPL to 0 if done at CPL0, but I'm vague on
> this, since it only really matters to hypervisor code AFAIK.)
It's even simpler, unless CPL=0 SS cannot be
Hi Amitkumar,
> On some arm-based platforms, we need to configure platform specific
> parameters by device tree node and we need define our node as a child
> node of parent SDIO host controller.
> This patch parses these parameters from device tree. It includes
> calibration data download to
Hi Amitkumar,
> On some arm-based platforms, we need to configure platform specific
> parameters by device tree node and we need define our node as a child
> node of parent SDIO host controller.
> This patch parses these parameters from device tree. It includes
> calibration data download to
On 08/04/16 18:03, Christoffer Dall wrote:
On Fri, Apr 08, 2016 at 04:37:02PM +0100, Suzuki K Poulose wrote:
On 08/04/16 14:42, Christoffer Dall wrote:
On Mon, Apr 04, 2016 at 05:26:13PM +0100, Suzuki K Poulose wrote:
-static void clear_pud_entry(struct kvm *kvm, pud_t *pud, phys_addr_t
On 08/04/16 18:03, Christoffer Dall wrote:
On Fri, Apr 08, 2016 at 04:37:02PM +0100, Suzuki K Poulose wrote:
On 08/04/16 14:42, Christoffer Dall wrote:
On Mon, Apr 04, 2016 at 05:26:13PM +0100, Suzuki K Poulose wrote:
-static void clear_pud_entry(struct kvm *kvm, pud_t *pud, phys_addr_t
On Apr 08, 2016 18:00, Peter Meerwald-Stadler wrote:
>
> > > maybe a #define to explain the name of register 0
> >
> > Well this zero is not register nor any kind of command that DS1803 needs to
> > send
> > back pots values.
> > DS1803 only requires the standard R/W bit to be set as read.
> >
On Apr 08, 2016 18:00, Peter Meerwald-Stadler wrote:
>
> > > maybe a #define to explain the name of register 0
> >
> > Well this zero is not register nor any kind of command that DS1803 needs to
> > send
> > back pots values.
> > DS1803 only requires the standard R/W bit to be set as read.
> >
On Fri, 2016-04-08 at 18:00 +0100, David Vrabel wrote:
> On 08/04/16 17:34, Toshi Kani wrote:
> >
> > On Tue, 2016-04-05 at 09:24 -0600, Toshi Kani wrote:
> > >
> > > +xen-devl
> > >
> > > On Tue, 2016-04-05 at 13:09 +0200, Borislav Petkov wrote:
> > > >
> > > > On Fri, Apr 01, 2016 at
On Fri, 2016-04-08 at 18:00 +0100, David Vrabel wrote:
> On 08/04/16 17:34, Toshi Kani wrote:
> >
> > On Tue, 2016-04-05 at 09:24 -0600, Toshi Kani wrote:
> > >
> > > +xen-devl
> > >
> > > On Tue, 2016-04-05 at 13:09 +0200, Borislav Petkov wrote:
> > > >
> > > > On Fri, Apr 01, 2016 at
On 8 April 2016 at 03:19, lipengcheng wrote:
> From: Pengcheng Li
>
> Force ETM idle acknowleghe when CPU enter WFI.
> writel_relaxed(0x2, drvdata->base + TRCAUXCTLR);
>
> Because linux kernel execute on EL1,
> so we just need to open EL1
On 8 April 2016 at 03:19, lipengcheng wrote:
> From: Pengcheng Li
>
> Force ETM idle acknowleghe when CPU enter WFI.
> writel_relaxed(0x2, drvdata->base + TRCAUXCTLR);
>
> Because linux kernel execute on EL1,
> so we just need to open EL1 trace,close EL1 trace.
> drvdata->vinst_ctrl |= BIT(20);
On Fri, Apr 08, 2016 at 04:37:02PM +0100, Suzuki K Poulose wrote:
> On 08/04/16 14:42, Christoffer Dall wrote:
> >On Mon, Apr 04, 2016 at 05:26:13PM +0100, Suzuki K Poulose wrote:
>
> >>
> >>-static void clear_pud_entry(struct kvm *kvm, pud_t *pud, phys_addr_t addr)
> >>+static void
On Fri, Apr 08, 2016 at 04:37:02PM +0100, Suzuki K Poulose wrote:
> On 08/04/16 14:42, Christoffer Dall wrote:
> >On Mon, Apr 04, 2016 at 05:26:13PM +0100, Suzuki K Poulose wrote:
>
> >>
> >>-static void clear_pud_entry(struct kvm *kvm, pud_t *pud, phys_addr_t addr)
> >>+static void
On 08/04/16 17:34, Toshi Kani wrote:
> On Tue, 2016-04-05 at 09:24 -0600, Toshi Kani wrote:
>> +xen-devl
>>
>> On Tue, 2016-04-05 at 13:09 +0200, Borislav Petkov wrote:
>>> On Fri, Apr 01, 2016 at 04:19:45PM -0600, Toshi Kani wrote:
> :
When the system does not have much memory,
On 08/04/16 17:34, Toshi Kani wrote:
> On Tue, 2016-04-05 at 09:24 -0600, Toshi Kani wrote:
>> +xen-devl
>>
>> On Tue, 2016-04-05 at 13:09 +0200, Borislav Petkov wrote:
>>> On Fri, Apr 01, 2016 at 04:19:45PM -0600, Toshi Kani wrote:
> :
When the system does not have much memory,
Hi Alex,
On 04/08/2016 06:41 PM, Alex Williamson wrote:
> On Fri, 8 Apr 2016 17:48:01 +0200
> Eric Auger wrote:
>
> Hi Eric,
>
>> Hi Alex,
>> On 04/07/2016 08:29 PM, Alex Williamson wrote:
>>> On Thu, 7 Apr 2016 15:43:29 +0200
>>> Eric Auger wrote:
Hi Alex,
On 04/08/2016 06:41 PM, Alex Williamson wrote:
> On Fri, 8 Apr 2016 17:48:01 +0200
> Eric Auger wrote:
>
> Hi Eric,
>
>> Hi Alex,
>> On 04/07/2016 08:29 PM, Alex Williamson wrote:
>>> On Thu, 7 Apr 2016 15:43:29 +0200
>>> Eric Auger wrote:
>>>
Hi Alex,
On 04/07/2016 12:07
On Fri, Apr 8, 2016 at 9:50 AM, Paolo Bonzini wrote:
>
>
> On 08/04/2016 18:25, David Matlack wrote:
>> On Thu, Apr 7, 2016 at 12:03 PM, Paolo Bonzini wrote:
Thank you :). Let me know how testing goes.
>>>
>>> It went well.
>>
>> Great! How
On Fri, Apr 8, 2016 at 9:50 AM, Paolo Bonzini wrote:
>
>
> On 08/04/2016 18:25, David Matlack wrote:
>> On Thu, Apr 7, 2016 at 12:03 PM, Paolo Bonzini wrote:
Thank you :). Let me know how testing goes.
>>>
>>> It went well.
>>
>> Great! How should we proceed?
>
> It will appear very
On 08/04/2016 18:25, David Matlack wrote:
> On Thu, Apr 7, 2016 at 12:03 PM, Paolo Bonzini wrote:
>>>
>>> Thank you :). Let me know how testing goes.
>>
>> It went well.
>
> Great! How should we proceed?
It will appear very soon on kvm/next and Radim will send the pull
On Fri, Apr 08, 2016 at 04:23:24PM +0100, Rui Salvaterra wrote:
> Based on Sergey's test patch [1], this fixes zram with lz4 compression on big
> endian cpus. Tested on ppc64 with no regression on x86_64.
Please wrap your text at 72 columns in a changelog comment.
>
> [1]
On Fri, 2016-04-08 at 13:13 +0200, Rafał Miłecki wrote:
> 1) Use pr_fmt to keep messages consistent
> 2) Don't warn if kzalloc fails as it dumps stack on its own
> 3) Use %pR format for displaying whole resource to avoid:
> warning: format ‘%08llx’ expects type ‘long long unsigned int’, but
>
On 08/04/2016 18:25, David Matlack wrote:
> On Thu, Apr 7, 2016 at 12:03 PM, Paolo Bonzini wrote:
>>>
>>> Thank you :). Let me know how testing goes.
>>
>> It went well.
>
> Great! How should we proceed?
It will appear very soon on kvm/next and Radim will send the pull
request to Linus next
On Fri, Apr 08, 2016 at 04:23:24PM +0100, Rui Salvaterra wrote:
> Based on Sergey's test patch [1], this fixes zram with lz4 compression on big
> endian cpus. Tested on ppc64 with no regression on x86_64.
Please wrap your text at 72 columns in a changelog comment.
>
> [1]
On Fri, 2016-04-08 at 13:13 +0200, Rafał Miłecki wrote:
> 1) Use pr_fmt to keep messages consistent
> 2) Don't warn if kzalloc fails as it dumps stack on its own
> 3) Use %pR format for displaying whole resource to avoid:
> warning: format ‘%08llx’ expects type ‘long long unsigned int’, but
>
On 4/8/2016 9:56 AM, Frederic Weisbecker wrote:
On Wed, Mar 09, 2016 at 02:39:28PM -0500, Chris Metcalf wrote:
> TL;DR: Let's make an explicit decision about whether task isolation
> should be "persistent" or "one-shot". Both have some advantages.
> =
>
> An important high-level issue
On 4/8/2016 9:56 AM, Frederic Weisbecker wrote:
On Wed, Mar 09, 2016 at 02:39:28PM -0500, Chris Metcalf wrote:
> TL;DR: Let's make an explicit decision about whether task isolation
> should be "persistent" or "one-shot". Both have some advantages.
> =
>
> An important high-level issue
Will,
On Fri, Apr 8, 2016 at 6:07 AM, Will Deacon wrote:
> On Tue, Apr 05, 2016 at 10:03:32AM -0700, Doug Anderson wrote:
>> On Tue, Mar 29, 2016 at 10:02 AM, Will Deacon wrote:
>> > On Mon, Mar 28, 2016 at 02:32:11PM +0800, Yong Wu wrote:
>> >> @@
On Fri, 2016-04-08 at 16:51 +0200, Sebastian Andrzej Siewior wrote:
> Is there anything you can hand me over?
Sure, I'll send it offline (yup, that proud of my scripting;)
-Mike
On Fri, 2016-04-08 at 16:51 +0200, Sebastian Andrzej Siewior wrote:
> Is there anything you can hand me over?
Sure, I'll send it offline (yup, that proud of my scripting;)
-Mike
Will,
On Fri, Apr 8, 2016 at 6:07 AM, Will Deacon wrote:
> On Tue, Apr 05, 2016 at 10:03:32AM -0700, Doug Anderson wrote:
>> On Tue, Mar 29, 2016 at 10:02 AM, Will Deacon wrote:
>> > On Mon, Mar 28, 2016 at 02:32:11PM +0800, Yong Wu wrote:
>> >> @@ -213,13 +215,16 @@ static struct page
>> >>
Hello, Waiman.
On Fri, Apr 08, 2016 at 12:16:20PM -0400, Waiman Long wrote:
> +/**
> + * __percpu_stats_add - add given count to percpu value
> + * @pcs : Pointer to percpu_stats structure
> + * @stat: The statistics count that needs to be updated
> + * @cnt: The value to be added to the
Hello, Waiman.
On Fri, Apr 08, 2016 at 12:16:20PM -0400, Waiman Long wrote:
> +/**
> + * __percpu_stats_add - add given count to percpu value
> + * @pcs : Pointer to percpu_stats structure
> + * @stat: The statistics count that needs to be updated
> + * @cnt: The value to be added to the
Hi Waiman,
[auto build test ERROR on ext4/dev]
[also build test ERROR on v4.6-rc2 next-20160408]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Waiman-Long/ext4-Improve-parallel-I-O
Hi Waiman,
[auto build test ERROR on ext4/dev]
[also build test ERROR on v4.6-rc2 next-20160408]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Waiman-Long/ext4-Improve-parallel-I-O
On Tue, 2016-04-05 at 09:24 -0600, Toshi Kani wrote:
> +xen-devl
>
> On Tue, 2016-04-05 at 13:09 +0200, Borislav Petkov wrote:
> > On Fri, Apr 01, 2016 at 04:19:45PM -0600, Toshi Kani wrote:
> > >
:
> > >
> > > When the system does not have much memory, 'high_memory' points to
> >
> > What
On Tue, 2016-04-05 at 09:24 -0600, Toshi Kani wrote:
> +xen-devl
>
> On Tue, 2016-04-05 at 13:09 +0200, Borislav Petkov wrote:
> > On Fri, Apr 01, 2016 at 04:19:45PM -0600, Toshi Kani wrote:
> > >
:
> > >
> > > When the system does not have much memory, 'high_memory' points to
> >
> > What
Due to mail server malfunction, this patch was sent twice. Please
ignore this duplicate.
Thanks,
David Daney
On 03/31/2016 06:01 PM, David Daney wrote:
From: David Daney
commit b7d3e3d3d21a ("net: thunderx: Don't leak phy device references
on -EPROBE_DEFER
On Fri, 8 Apr 2016 17:48:01 +0200
Eric Auger wrote:
Hi Eric,
> Hi Alex,
> On 04/07/2016 08:29 PM, Alex Williamson wrote:
> > On Thu, 7 Apr 2016 15:43:29 +0200
> > Eric Auger wrote:
> >
> >> Hi Alex,
> >> On 04/07/2016 12:07 AM, Alex Williamson
Due to mail server malfunction, this patch was sent twice. Please
ignore this duplicate.
Thanks,
David Daney
On 03/31/2016 06:01 PM, David Daney wrote:
From: David Daney
commit b7d3e3d3d21a ("net: thunderx: Don't leak phy device references
on -EPROBE_DEFER condition.") incorrectly moved
On Fri, 8 Apr 2016 17:48:01 +0200
Eric Auger wrote:
Hi Eric,
> Hi Alex,
> On 04/07/2016 08:29 PM, Alex Williamson wrote:
> > On Thu, 7 Apr 2016 15:43:29 +0200
> > Eric Auger wrote:
> >
> >> Hi Alex,
> >> On 04/07/2016 12:07 AM, Alex Williamson wrote:
> >>> On Mon, 4 Apr 2016 08:30:08
On 04/08/2016 06:56 PM, Andy Lutomirski wrote:
On Fri, Apr 8, 2016 at 6:50 AM, Dmitry Safonov wrote:
Hello again,
what do you think about attached patch?
I think it should fix landing problem for i386 vdso mremap.
It does not touch fast syscall path, so there should be
On 04/08/2016 06:56 PM, Andy Lutomirski wrote:
On Fri, Apr 8, 2016 at 6:50 AM, Dmitry Safonov wrote:
Hello again,
what do you think about attached patch?
I think it should fix landing problem for i386 vdso mremap.
It does not touch fast syscall path, so there should be no
speed regression.
Hi,
On 08/04/16 12:54, Peter Zijlstra wrote:
> On Fri, Apr 08, 2016 at 03:31:41AM -0700, Joe Perches wrote:
> > On Fri, 2016-04-08 at 10:07 +0800, Yuyang Du wrote:
> > > __compute_runnable_contrib() uses a loop to compute sum, whereas a
> > > table lookup can do it faster in a constant time.
> >
Hi,
On 08/04/16 12:54, Peter Zijlstra wrote:
> On Fri, Apr 08, 2016 at 03:31:41AM -0700, Joe Perches wrote:
> > On Fri, 2016-04-08 at 10:07 +0800, Yuyang Du wrote:
> > > __compute_runnable_contrib() uses a loop to compute sum, whereas a
> > > table lookup can do it faster in a constant time.
> >
On 4/8/2016 3:20 AM, Paolo Abeni wrote:
> The skb_owned_by hook was added with the commit ca10b9e9a8ca
> ("selinux: add a skb_owned_by() hook") and later removed
> when said commit was reverted.
>
> Later on, when switching to list of hooks, a field named
> 'skb_owned_by' was included into the
From: David Daney
commit b7d3e3d3d21a ("net: thunderx: Don't leak phy device references
on -EPROBE_DEFER condition.") incorrectly moved the call to
of_node_put() outside of the loop. Under normal loop exit, the node
has already had of_node_put() called, so the extra call
On 4/8/2016 3:20 AM, Paolo Abeni wrote:
> The skb_owned_by hook was added with the commit ca10b9e9a8ca
> ("selinux: add a skb_owned_by() hook") and later removed
> when said commit was reverted.
>
> Later on, when switching to list of hooks, a field named
> 'skb_owned_by' was included into the
From: David Daney
commit b7d3e3d3d21a ("net: thunderx: Don't leak phy device references
on -EPROBE_DEFER condition.") incorrectly moved the call to
of_node_put() outside of the loop. Under normal loop exit, the node
has already had of_node_put() called, so the extra call results in:
[
From: David Daney
commit b7d3e3d3d21a ("net: thunderx: Don't leak phy device references
on -EPROBE_DEFER condition.") incorrectly moved the call to
of_node_put() outside of the loop. Under normal loop exit, the node
has already had of_node_put() called, so the extra call
From: David Daney
commit b7d3e3d3d21a ("net: thunderx: Don't leak phy device references
on -EPROBE_DEFER condition.") incorrectly moved the call to
of_node_put() outside of the loop. Under normal loop exit, the node
has already had of_node_put() called, so the extra call results in:
[
[+cc Greg]
On Sun, Mar 20, 2016 at 01:57:20PM +0100, Lukas Wunner wrote:
> Gen 1 and 2 chips use the same ID for NHI, bridges and switch.
> Gen 3 chips and onward use a distinct ID for the NHI.
>
> No functional change intended.
>
> Cc: Andreas Noever
> Signed-off-by:
[+cc Greg]
On Sun, Mar 20, 2016 at 01:57:20PM +0100, Lukas Wunner wrote:
> Gen 1 and 2 chips use the same ID for NHI, bridges and switch.
> Gen 3 chips and onward use a distinct ID for the NHI.
>
> No functional change intended.
>
> Cc: Andreas Noever
> Signed-off-by: Lukas Wunner
> Acked-by:
On Thu, Apr 7, 2016 at 12:03 PM, Paolo Bonzini wrote:
>>
>> Thank you :). Let me know how testing goes.
>
> It went well.
Great! How should we proceed?
On Tue, 5 Apr 2016 11:29:54 +0200
Peter Zijlstra wrote:
> --
> kernel/locking/rtmutex.c | 16 +---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
> index 3e746607abe5..1896baf28e9c
On Thu, Apr 7, 2016 at 12:03 PM, Paolo Bonzini wrote:
>>
>> Thank you :). Let me know how testing goes.
>
> It went well.
Great! How should we proceed?
On Tue, 5 Apr 2016 11:29:54 +0200
Peter Zijlstra wrote:
> --
> kernel/locking/rtmutex.c | 16 +---
> 1 file changed, 13 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/locking/rtmutex.c b/kernel/locking/rtmutex.c
> index 3e746607abe5..1896baf28e9c 100644
> ---
* Sebastian Reichel [160408 09:09]:
> Hi Tony,
>
> On Fri, Apr 08, 2016 at 08:49:07AM -0700, Tony Lindgren wrote:
> > * Rob Herring [160407 10:58]:
> > > On Tue, Apr 05, 2016 at 08:59:34AM +0300, Ivaylo Dimitrov wrote:
> > > > of_map_mode is needed so to be
v1->v2:
- Remove percpu_stats_reset() which is not really needed in this
patchset.
- Move some percpu_stats* functions to the newly created
lib/percpu_stats.c.
- Add a new patch to support 64-bit statistics counts in 32-bit
architectures.
- Rearrange the patches by moving the
* Sebastian Reichel [160408 09:09]:
> Hi Tony,
>
> On Fri, Apr 08, 2016 at 08:49:07AM -0700, Tony Lindgren wrote:
> > * Rob Herring [160407 10:58]:
> > > On Tue, Apr 05, 2016 at 08:59:34AM +0300, Ivaylo Dimitrov wrote:
> > > > of_map_mode is needed so to be possible to set initial regulators
v1->v2:
- Remove percpu_stats_reset() which is not really needed in this
patchset.
- Move some percpu_stats* functions to the newly created
lib/percpu_stats.c.
- Add a new patch to support 64-bit statistics counts in 32-bit
architectures.
- Rearrange the patches by moving the
The unsigned long type in 32-bit architectures is only 32-bit. This may
not be enough from some statistics counts that may well go over 2^32
over time. This patch optionally enables the use of 64-bit counts in
32-bit architecture, though it does add a bit of performance overhead
if enabled.
This
The unsigned long type in 32-bit architectures is only 32-bit. This may
not be enough from some statistics counts that may well go over 2^32
over time. This patch optionally enables the use of 64-bit counts in
32-bit architecture, though it does add a bit of performance overhead
if enabled.
This
When performing direct I/O, the current ext4 code does
not pass in the DIO_SKIP_DIO_COUNT flag to dax_do_io() or
__blockdev_direct_IO() when inode_dio_begin() has, in fact, been
called. This causes dax_do_io()/__blockdev_direct_IO() to invoke
inode_dio_begin()/inode_dio_end() internally. This
This patch changes the es_stats_cache_hits and es_stats_cache_misses
statistics counts to per-cpu variables to reduce cacheline contention
issues whem multiple threads are trying to update those counts
simultaneously. It uses the new per-cpu stats APIs provided by the
percpu_stats.h header file.
When performing direct I/O, the current ext4 code does
not pass in the DIO_SKIP_DIO_COUNT flag to dax_do_io() or
__blockdev_direct_IO() when inode_dio_begin() has, in fact, been
called. This causes dax_do_io()/__blockdev_direct_IO() to invoke
inode_dio_begin()/inode_dio_end() internally. This
This patch changes the es_stats_cache_hits and es_stats_cache_misses
statistics counts to per-cpu variables to reduce cacheline contention
issues whem multiple threads are trying to update those counts
simultaneously. It uses the new per-cpu stats APIs provided by the
percpu_stats.h header file.
This patch introduces a set of simple per-cpu statictics count helper
functions that can be used by other kernel subsystems for keeping
track of the number of events that happens. It is per-cpu based to
reduce overhead and improve accuracy of the counter. Using per-cpu
counter is usually overkill
On 2016/4/8 23:22, Arnaldo Carvalho de Melo wrote:
Em Fri, Apr 08, 2016 at 03:07:22PM +, Wang Nan escreveu:
Before this patch, strange error message is provided if passed a
non-tracepoint event to 'perf trace':
# perf trace -a --ev cycles sleep 1
Failed to set filter "common_pid !=
This patch introduces a set of simple per-cpu statictics count helper
functions that can be used by other kernel subsystems for keeping
track of the number of events that happens. It is per-cpu based to
reduce overhead and improve accuracy of the counter. Using per-cpu
counter is usually overkill
On 2016/4/8 23:22, Arnaldo Carvalho de Melo wrote:
Em Fri, Apr 08, 2016 at 03:07:22PM +, Wang Nan escreveu:
Before this patch, strange error message is provided if passed a
non-tracepoint event to 'perf trace':
# perf trace -a --ev cycles sleep 1
Failed to set filter "common_pid !=
Hi Lars,
On 08-04-2016 16:46, Lars-Peter Clausen wrote:
> On 04/07/2016 06:53 PM, Jose Abreu wrote:
>> This patch adds audio support for the ADV7511 HDMI transmitter
>> using ALSA SoC.
>>
>> The code was ported from Analog Devices linux tree from
>> commit 1770c4a1e32b ("Merge remote-tracking
Hi Lars,
On 08-04-2016 16:46, Lars-Peter Clausen wrote:
> On 04/07/2016 06:53 PM, Jose Abreu wrote:
>> This patch adds audio support for the ADV7511 HDMI transmitter
>> using ALSA SoC.
>>
>> The code was ported from Analog Devices linux tree from
>> commit 1770c4a1e32b ("Merge remote-tracking
Hi Lars,
On 08-04-2016 16:52, Lars-Peter Clausen wrote:
> On 04/08/2016 12:06 PM, Jose Abreu wrote:
>> Hi Mark,
>>
>>
>> On 07-04-2016 18:53, Mark Brown wrote:
>>> On Thu, Apr 07, 2016 at 05:53:59PM +0100, Jose Abreu wrote:
>>>
+ Optional properties:
+ - snps,use-dmaengine: If set the
Hi Lars,
On 08-04-2016 16:52, Lars-Peter Clausen wrote:
> On 04/08/2016 12:06 PM, Jose Abreu wrote:
>> Hi Mark,
>>
>>
>> On 07-04-2016 18:53, Mark Brown wrote:
>>> On Thu, Apr 07, 2016 at 05:53:59PM +0100, Jose Abreu wrote:
>>>
+ Optional properties:
+ - snps,use-dmaengine: If set the
Hi Tony,
On Fri, Apr 08, 2016 at 08:49:07AM -0700, Tony Lindgren wrote:
> * Rob Herring [160407 10:58]:
> > On Tue, Apr 05, 2016 at 08:59:34AM +0300, Ivaylo Dimitrov wrote:
> > > of_map_mode is needed so to be possible to set initial regulators mode
> > > from
> > > the board
Hi Tony,
On Fri, Apr 08, 2016 at 08:49:07AM -0700, Tony Lindgren wrote:
> * Rob Herring [160407 10:58]:
> > On Tue, Apr 05, 2016 at 08:59:34AM +0300, Ivaylo Dimitrov wrote:
> > > of_map_mode is needed so to be possible to set initial regulators mode
> > > from
> > > the board DTS. Otherwise,
Until now, when we connect gdb to the QEMU gdb-server, the
single-step mode is not managed.
This patch adds this, only for kvm-pr:
If KVM_GUESTDBG_SINGLESTEP is set, we enable single-step trace bit in the
MSR (MSR_SE) just before the __kvmppc_vcpu_run(), and disable it just after.
In
Until now, when we connect gdb to the QEMU gdb-server, the
single-step mode is not managed.
This patch adds this, only for kvm-pr:
If KVM_GUESTDBG_SINGLESTEP is set, we enable single-step trace bit in the
MSR (MSR_SE) just before the __kvmppc_vcpu_run(), and disable it just after.
In
On Fri, Apr 8, 2016 at 12:13 AM, Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
>> ARCH_GET_FS and ARCH_GET_GS attempted to figure out the fsbase and
>> gsbase respectively from saved thread state. This was wrong: fsbase
>> and gsbase live in registers
On Fri, Apr 8, 2016 at 12:13 AM, Ingo Molnar wrote:
>
> * Andy Lutomirski wrote:
>
>> ARCH_GET_FS and ARCH_GET_GS attempted to figure out the fsbase and
>> gsbase respectively from saved thread state. This was wrong: fsbase
>> and gsbase live in registers while a thread is running, not in
>>
On Fri, Apr 8, 2016 at 6:34 PM, wrote:
>> On Thu, Apr 7, 2016 at 2:39 PM, Andy Shevchenko
>> wrote:
>> > On Mon, Apr 4, 2016 at 11:26 PM, Martin Brandenburg
>> > wrote:
>> >> From: Martin Brandenburg
>>
On Fri, Apr 8, 2016 at 6:34 PM, wrote:
>> On Thu, Apr 7, 2016 at 2:39 PM, Andy Shevchenko
>> wrote:
>> > On Mon, Apr 4, 2016 at 11:26 PM, Martin Brandenburg
>> > wrote:
>> >> From: Martin Brandenburg
>> >>
>> >> Almost everywhere we use strncpy we should use strlcpy. This affects
>> >> path
On Fri, Apr 08, 2016 at 01:33:28PM +, Gabriele Paoloni wrote:
> Hi Bjorn
>
> Many thanks for your reply
>
> > -Original Message-
> > From: Bjorn Helgaas [mailto:helg...@kernel.org]
> > Sent: 07 April 2016 15:06
> > To: Gabriele Paoloni
> > Cc: Jisheng Zhang; jingooh...@gmail.com;
On Fri, Apr 08, 2016 at 01:33:28PM +, Gabriele Paoloni wrote:
> Hi Bjorn
>
> Many thanks for your reply
>
> > -Original Message-
> > From: Bjorn Helgaas [mailto:helg...@kernel.org]
> > Sent: 07 April 2016 15:06
> > To: Gabriele Paoloni
> > Cc: Jisheng Zhang; jingooh...@gmail.com;
On Fri, Apr 8, 2016 at 1:01 AM, Andrew Cooper wrote:
> On 08/04/2016 01:24, Andy Lutomirski wrote:
>> I can't see any reason that we need the __KERNEL_DS segment at all --
>> I think that everything that uses __KERNEL_DS could use __USER_DS
>> instead. Am I missing
On Fri, Apr 8, 2016 at 1:01 AM, Andrew Cooper wrote:
> On 08/04/2016 01:24, Andy Lutomirski wrote:
>> I can't see any reason that we need the __KERNEL_DS segment at all --
>> I think that everything that uses __KERNEL_DS could use __USER_DS
>> instead. Am I missing anything? This has been
* Keerthy [160403 22:38]:
> This is w.r.t J6/J6eco: 32clk is pseudo (erratum i856) - clock source.
> Errata i856 for the AM572x (DRA7xx) points out that the 32.768KHz external
> crystal is not enabled at power up. Instead the CPU falls back to using
> an emulation for the 32KHz
* Keerthy [160403 22:38]:
> This is w.r.t J6/J6eco: 32clk is pseudo (erratum i856) - clock source.
> Errata i856 for the AM572x (DRA7xx) points out that the 32.768KHz external
> crystal is not enabled at power up. Instead the CPU falls back to using
> an emulation for the 32KHz clock which is
> > maybe a #define to explain the name of register 0
>
> Well this zero is not register nor any kind of command that DS1803 needs to
> send
> back pots values.
> DS1803 only requires the standard R/W bit to be set as read.
> I used _word_ function series to get back a word (16 bits) as this
> > maybe a #define to explain the name of register 0
>
> Well this zero is not register nor any kind of command that DS1803 needs to
> send
> back pots values.
> DS1803 only requires the standard R/W bit to be set as read.
> I used _word_ function series to get back a word (16 bits) as this
Sometimes gcc mysteriously doesn't inline
very small functions we expect to be inlined. See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66122
Arguably, gcc should do better, but gcc people aren't willing
to invest time into it, asking to use __always_inline instead.
With this .config:
Sometimes gcc mysteriously doesn't inline
very small functions we expect to be inlined. See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66122
Arguably, gcc should do better, but gcc people aren't willing
to invest time into it, asking to use __always_inline instead.
With this .config:
401 - 500 of 1176 matches
Mail list logo