Hi Otavio,
Am Sonntag, 25. November 2018, 22:19:02 CET schrieb Otavio Salvador:
> According to the Rockchip vendor tree the PMU interrupt number is
> 76, so fix it accordingly.
>
> Signed-off-by: Otavio Salvador
> Signed-off-by: Fabio Berton
looks ok, especially as the TRM I have doesn't list
Hi Vinod,
After merging the slave-dma tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/dma/coh901318.c: In function 'coh901318_config':
drivers/dma/coh901318.c:1805:16: warning: unused variable 'flags'
[-Wunused-variable]
unsigned long flags;
Hi Otavio,
Am Sonntag, 25. November 2018, 22:19:02 CET schrieb Otavio Salvador:
> According to the Rockchip vendor tree the PMU interrupt number is
> 76, so fix it accordingly.
>
> Signed-off-by: Otavio Salvador
> Signed-off-by: Fabio Berton
looks ok, especially as the TRM I have doesn't list
Hi Vinod,
After merging the slave-dma tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
drivers/dma/coh901318.c: In function 'coh901318_config':
drivers/dma/coh901318.c:1805:16: warning: unused variable 'flags'
[-Wunused-variable]
unsigned long flags;
On Sun, Nov 25, 2018 at 4:52 PM Stephen Rothwell wrote:
>
> Hi Steve,
>
> On Sun, 25 Nov 2018 18:31:40 -0600 Steve French wrote:
> >
> > Both of those cases are intentional fallthroughs and there are
> > existing comments in the code noting the reasons for them to
> > fallthrough
> >
> > (also
On Sun, Nov 25, 2018 at 4:52 PM Stephen Rothwell wrote:
>
> Hi Steve,
>
> On Sun, 25 Nov 2018 18:31:40 -0600 Steve French wrote:
> >
> > Both of those cases are intentional fallthroughs and there are
> > existing comments in the code noting the reasons for them to
> > fallthrough
> >
> > (also
Hi Russell,
On Thu, Nov 15, 2018 at 9:13 PM Souptick Joarder wrote:
>
> Convert to use vm_insert_range() to map range of kernel
> memory to user vma.
>
> Signed-off-by: Souptick Joarder
Any comment on this patch ?
> ---
> arch/arm/mm/dma-mapping.c | 21 +++--
> 1 file
Hi Russell,
On Thu, Nov 15, 2018 at 9:13 PM Souptick Joarder wrote:
>
> Convert to use vm_insert_range() to map range of kernel
> memory to user vma.
>
> Signed-off-by: Souptick Joarder
Any comment on this patch ?
> ---
> arch/arm/mm/dma-mapping.c | 21 +++--
> 1 file
Commit 67ec1072b053 ("ALSA: pcm: Fix rwsem deadlock for non-atomic PCM stream")
fixes deadlock for non-atomic PCM stream. But, This patch causes antother stuck.
If writer is RT thread and reader is a normal thread, the reader thread will
be difficult to get scheduled. It may not give chance to
Commit 67ec1072b053 ("ALSA: pcm: Fix rwsem deadlock for non-atomic PCM stream")
fixes deadlock for non-atomic PCM stream. But, This patch causes antother stuck.
If writer is RT thread and reader is a normal thread, the reader thread will
be difficult to get scheduled. It may not give chance to
Hi,
Cc-ing Petr and Steven
On (11/25/18 01:13), Joe Perches wrote:
> commit 04b8eb7a4ccd ("symbol lookup: introduce
> dereference_symbol_descriptor()}"
>
> deprecated vsprintf extension %pf and %pF.
>
> There are approximately these total uses of the symbolic
> lookup vsprintf extensions
Hi,
Cc-ing Petr and Steven
On (11/25/18 01:13), Joe Perches wrote:
> commit 04b8eb7a4ccd ("symbol lookup: introduce
> dereference_symbol_descriptor()}"
>
> deprecated vsprintf extension %pf and %pF.
>
> There are approximately these total uses of the symbolic
> lookup vsprintf extensions
-- Forwarded message -
From: Kyungtae Kim
Date: Mon, Nov 26, 2018 at 12:26 AM
Subject: UBSAN: Undefined behaviour in drivers/input/mousedev.c
To:
Cc: Byoungyoung Lee , DaeRyong Jeong
, ,
,
We report a crash found in v4.20-rc2:
kernel config:
-- Forwarded message -
From: Kyungtae Kim
Date: Mon, Nov 26, 2018 at 12:26 AM
Subject: UBSAN: Undefined behaviour in drivers/input/mousedev.c
To:
Cc: Byoungyoung Lee , DaeRyong Jeong
, ,
,
We report a crash found in v4.20-rc2:
kernel config:
Am Sonntag, 25. November 2018, 22:19:01 CET schrieb Otavio Salvador:
> As done in the Rockchip vendor tree and also on other
> "arm,armv7-timer" instances, the correct GIC_CPU_MASK_SIMPLE mask
> is 4 instead of 1.
Nope. That value represents the number of cores in the system.
As the rv1108 only
Am Sonntag, 25. November 2018, 22:19:01 CET schrieb Otavio Salvador:
> As done in the Rockchip vendor tree and also on other
> "arm,armv7-timer" instances, the correct GIC_CPU_MASK_SIMPLE mask
> is 4 instead of 1.
Nope. That value represents the number of cores in the system.
As the rv1108 only
On Mon, Nov 26, 2018 at 02:29:57AM +, k...@linuxonhyperv.com wrote:
From: Dexuan Cui
vmbus_process_offer() mustn't call channel->sc_creation_callback()
directly for sub-channels, because sc_creation_callback() ->
vmbus_open() may never get the host's response to the
OPEN_CHANNEL message
On Mon, Nov 26, 2018 at 02:29:57AM +, k...@linuxonhyperv.com wrote:
From: Dexuan Cui
vmbus_process_offer() mustn't call channel->sc_creation_callback()
directly for sub-channels, because sc_creation_callback() ->
vmbus_open() may never get the host's response to the
OPEN_CHANNEL message
Hi Steve,
This series looks good to me.
Reviewed-by: Masami Hiramatsu
for this series.
Thank you!
# Now I know why sometimes func-graph depth looks broken...
On Wed, 21 Nov 2018 19:28:01 -0500
Steven Rostedt wrote:
> While working on rewriting function graph tracer, I found a design
>
Hi Steve,
This series looks good to me.
Reviewed-by: Masami Hiramatsu
for this series.
Thank you!
# Now I know why sometimes func-graph depth looks broken...
On Wed, 21 Nov 2018 19:28:01 -0500
Steven Rostedt wrote:
> While working on rewriting function graph tracer, I found a design
>
On (11/24/18 17:01), Carmeli Tamir wrote:
> The FAT file system volume label file stored in the root directory should
> match the volume label field in the FAT boot sector. As consequence, the
> max length of these fields ought to be the same. This patch replaces the
> magic '11' usef in the
On (11/24/18 17:01), Carmeli Tamir wrote:
> The FAT file system volume label file stored in the root directory should
> match the volume label field in the FAT boot sector. As consequence, the
> max length of these fields ought to be the same. This patch replaces the
> magic '11' usef in the
On 11/25/18 8:31 PM, Waiman Long wrote:
On 11/25/2018 03:42 PM, Qian Cai wrote:
On 11/23/18 10:01 PM, Qian Cai wrote:
On Nov 22, 2018, at 4:56 PM, Thomas Gleixner
wrote:
On Tue, 20 Nov 2018, Qian Cai wrote:
Looking deeper at that.
diff --git a/lib/debugobjects.c
On 11/25/18 8:31 PM, Waiman Long wrote:
On 11/25/2018 03:42 PM, Qian Cai wrote:
On 11/23/18 10:01 PM, Qian Cai wrote:
On Nov 22, 2018, at 4:56 PM, Thomas Gleixner
wrote:
On Tue, 20 Nov 2018, Qian Cai wrote:
Looking deeper at that.
diff --git a/lib/debugobjects.c
On Sat, Nov 24, 2018 at 01:41:31PM -0500, Steven Rostedt wrote:
> On Sat, 24 Nov 2018 14:49:34 +0900
> Namhyung Kim wrote:
>
> > On Sat, Nov 24, 2018 at 2:37 AM Steven Rostedt wrote:
> > >
> > > On Fri, 23 Nov 2018 09:01:18 +0900
> > > Namhyung Kim wrote:
> > >
> > > > Acked-by: Namhyung Kim
On Sat, Nov 24, 2018 at 01:41:31PM -0500, Steven Rostedt wrote:
> On Sat, 24 Nov 2018 14:49:34 +0900
> Namhyung Kim wrote:
>
> > On Sat, Nov 24, 2018 at 2:37 AM Steven Rostedt wrote:
> > >
> > > On Fri, 23 Nov 2018 09:01:18 +0900
> > > Namhyung Kim wrote:
> > >
> > > > Acked-by: Namhyung Kim
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
arch/x86/kernel/cpu/resctrl/rdtgroup.c
between commit:
16ec1a5d58ea ("kernfs, sysfs, cgroup, intel_rdt: Support fs_context")
(where the file is arch/x86/kernel/cpu/intel_rdt_rdtgroup.c)
from the vfs tree and commit:
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
arch/x86/kernel/cpu/resctrl/rdtgroup.c
between commit:
16ec1a5d58ea ("kernfs, sysfs, cgroup, intel_rdt: Support fs_context")
(where the file is arch/x86/kernel/cpu/intel_rdt_rdtgroup.c)
from the vfs tree and commit:
On (11/24/18 13:10), Tetsuo Handa wrote:
> Subject: [PATCH v2] printk: Make printk_emit() local function.
>
> printk_emit() is called from only devkmsg_write() in the same file.
> Save object size by making it a local function.
>
> Signed-off-by: Tetsuo Handa
Looks good to me,
Reviewed-by:
On (11/24/18 13:10), Tetsuo Handa wrote:
> Subject: [PATCH v2] printk: Make printk_emit() local function.
>
> printk_emit() is called from only devkmsg_write() in the same file.
> Save object size by making it a local function.
>
> Signed-off-by: Tetsuo Handa
Looks good to me,
Reviewed-by:
On (11/24/18 09:24), Tetsuo Handa wrote:
> >> Steven told me on Plumbers conference that even few initial
> >> characters saved him a day few times.
> >
> > Yes, and that has happened more than once. I would reboot and retest
> > code that is crashing, and due to a triple fault, the machine would
On (11/24/18 09:24), Tetsuo Handa wrote:
> >> Steven told me on Plumbers conference that even few initial
> >> characters saved him a day few times.
> >
> > Yes, and that has happened more than once. I would reboot and retest
> > code that is crashing, and due to a triple fault, the machine would
/linux/commits/Tomasz-Duszynski/add-support-for-Sensirion-SPS30-PM-sensor/20181125-172634
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached
/linux/commits/Tomasz-Duszynski/add-support-for-Sensirion-SPS30-PM-sensor/20181125-172634
base: https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git togreg
config: x86_64-allmodconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached
On Fri, 2018-11-23 at 18:07 +0100, Matthias Brugger wrote:
>
> On 12/11/2018 02:28, Ryder Lee wrote:
> > The crash http://termbin.com/zitb is caused by the timer register
> > into system in early pahse during kernel boot, but the clock
> > sources didn't get ready at that time.
> >
> > A better
On Fri, 2018-11-23 at 18:07 +0100, Matthias Brugger wrote:
>
> On 12/11/2018 02:28, Ryder Lee wrote:
> > The crash http://termbin.com/zitb is caused by the timer register
> > into system in early pahse during kernel boot, but the clock
> > sources didn't get ready at that time.
> >
> > A better
This patch adds an option to compile-in a high resolution and large
Terminus (ter16x32) bitmap console font for use with HiDPI and Retina screens.
The font was convereted from standard Terminus ter-i32b.psf (size 16x32)
with the help of psftools and minor hand editing deleting useless characters.
This patch adds an option to compile-in a high resolution and large
Terminus (ter16x32) bitmap console font for use with HiDPI and Retina screens.
The font was convereted from standard Terminus ter-i32b.psf (size 16x32)
with the help of psftools and minor hand editing deleting useless characters.
On 2018/11/18 22:03, Samuel Neves wrote:
> On 11/17/18 12:36 AM, Li, Aubrey wrote:
>> On 2018/11/17 7:10, Dave Hansen wrote:
>>> Just to be clear: there are 3 AVX-512 XSAVE states:
>>>
>>> XFEATURE_OPMASK,
>>> XFEATURE_ZMM_Hi256,
>>> XFEATURE_Hi16_ZMM,
>>>
>>> I honestly
On 2018/11/18 22:03, Samuel Neves wrote:
> On 11/17/18 12:36 AM, Li, Aubrey wrote:
>> On 2018/11/17 7:10, Dave Hansen wrote:
>>> Just to be clear: there are 3 AVX-512 XSAVE states:
>>>
>>> XFEATURE_OPMASK,
>>> XFEATURE_ZMM_Hi256,
>>> XFEATURE_Hi16_ZMM,
>>>
>>> I honestly
On Sun, 25 Nov 2018, Linus Torvalds wrote:
> On Sat, Nov 24, 2018 at 7:21 PM Hugh Dickins wrote:
> >
> > Linus, I'm addressing this patch to you because I see from Tim Chen's
> > thread that it would interest you, and you were disappointed not to
> > root cause the issue back then. I'm not
On Sun, 25 Nov 2018, Linus Torvalds wrote:
> On Sat, Nov 24, 2018 at 7:21 PM Hugh Dickins wrote:
> >
> > Linus, I'm addressing this patch to you because I see from Tim Chen's
> > thread that it would interest you, and you were disappointed not to
> > root cause the issue back then. I'm not
The function frees qf_inode via iput but then pass qf_inode to
lockdep_set_quota_inode on the failure path. This may result in a
use-after-free bug. The patch frees df_inode only when it is never used.
Signed-off-by: Pan Bian
Fixes: daf647d2dd5("ext4: add lockdep annotations for i_data_sem")
---
The function frees qf_inode via iput but then pass qf_inode to
lockdep_set_quota_inode on the failure path. This may result in a
use-after-free bug. The patch frees df_inode only when it is never used.
Signed-off-by: Pan Bian
Fixes: daf647d2dd5("ext4: add lockdep annotations for i_data_sem")
---
On Sat, Nov 24, 2018 at 09:01:19PM +0800, Wei Hu (Xavier) wrote:
>
>
> On 2018/11/24 4:39, Jason Gunthorpe wrote:
> > On Fri, Nov 23, 2018 at 11:14:25PM +0800, Wei Hu (Xavier) wrote:
> >> This patch modifies the name of hns RoCE device's name in order
> >> to ensure that the name is consistent
On Sat, Nov 24, 2018 at 09:01:19PM +0800, Wei Hu (Xavier) wrote:
>
>
> On 2018/11/24 4:39, Jason Gunthorpe wrote:
> > On Fri, Nov 23, 2018 at 11:14:25PM +0800, Wei Hu (Xavier) wrote:
> >> This patch modifies the name of hns RoCE device's name in order
> >> to ensure that the name is consistent
brelse(bh) is called to drop the reference count of bh when the call
to nilfs_dat_translate fails. If the reference count hits 0, bh may be
freed. However, bh->b_page is unlocked and put after that, which may
result in a use-after-free bug. This patch moves the release operation
after unlocking
brelse(bh) is called to drop the reference count of bh when the call
to nilfs_dat_translate fails. If the reference count hits 0, bh may be
freed. However, bh->b_page is unlocked and put after that, which may
result in a use-after-free bug. This patch moves the release operation
after unlocking
On Sun, Nov 25, 2018 at 11:20:50PM +0100, Thomas Gleixner wrote:
> On Sun, 25 Nov 2018, Andi Kleen wrote:
>
> > > The current check whether two tasks belong to the same context is using
> > > the
> > > tasks context id. While correct, it's simpler to use the mm pointer
> > > because
> > > it
On Sun, Nov 25, 2018 at 11:20:50PM +0100, Thomas Gleixner wrote:
> On Sun, 25 Nov 2018, Andi Kleen wrote:
>
> > > The current check whether two tasks belong to the same context is using
> > > the
> > > tasks context id. While correct, it's simpler to use the mm pointer
> > > because
> > > it
Put return value checks of calling imx6ul_opp_check_speed_grading()
into one block to save one condition block for normal case.
Signed-off-by: Anson Huang
---
drivers/cpufreq/imx6q-cpufreq.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/cpufreq/imx6q-cpufreq.c
In voltage scale down path, the return value is NOT
used at all, remove them to simplify the code.
Signed-off-by: Anson Huang
---
drivers/cpufreq/imx6q-cpufreq.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/drivers/cpufreq/imx6q-cpufreq.c
Put return value checks of calling imx6ul_opp_check_speed_grading()
into one block to save one condition block for normal case.
Signed-off-by: Anson Huang
---
drivers/cpufreq/imx6q-cpufreq.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/cpufreq/imx6q-cpufreq.c
In voltage scale down path, the return value is NOT
used at all, remove them to simplify the code.
Signed-off-by: Anson Huang
---
drivers/cpufreq/imx6q-cpufreq.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/drivers/cpufreq/imx6q-cpufreq.c
From: Dexuan Cui
vmbus_process_offer() mustn't call channel->sc_creation_callback()
directly for sub-channels, because sc_creation_callback() ->
vmbus_open() may never get the host's response to the
OPEN_CHANNEL message (the host may rescind a channel at any time,
e.g. in the case of hot
From: Dexuan Cui
vmbus_process_offer() mustn't call channel->sc_creation_callback()
directly for sub-channels, because sc_creation_callback() ->
vmbus_open() may never get the host's response to the
OPEN_CHANNEL message (the host may rescind a channel at any time,
e.g. in the case of hot
From: Dexuan Cui
This is a longstanding issue: if the vmbus upper-layer drivers try to
consume too many GPADLs, the host may return with an error
0xC044 (STATUS_QUOTA_EXCEEDED), but currently we forget to check
the creation_status, and hence we can pass an invalid GPADL handle
into the
From: Dexuan Cui
This is a longstanding issue: if the vmbus upper-layer drivers try to
consume too many GPADLs, the host may return with an error
0xC044 (STATUS_QUOTA_EXCEEDED), but currently we forget to check
the creation_status, and hence we can pass an invalid GPADL handle
into the
On Fri, Nov 23, 2018 at 03:25:33PM +0530, Kishon Vijay Abraham I wrote:
> > +static int qcom_snps_hsphy_por_reset(struct hsphy_priv *priv)
> > +{
> > + int ret;
> > +
> > + ret = reset_control_assert(priv->por_reset);
> > + if (ret)
> > + return ret;
> > +
> > + /*
> > +* The
On Fri, Nov 23, 2018 at 03:25:33PM +0530, Kishon Vijay Abraham I wrote:
> > +static int qcom_snps_hsphy_por_reset(struct hsphy_priv *priv)
> > +{
> > + int ret;
> > +
> > + ret = reset_control_assert(priv->por_reset);
> > + if (ret)
> > + return ret;
> > +
> > + /*
> > +* The
From: "K. Y. Srinivasan"
Miscellaneous fixes.
Dexuan Cui (2):
Drivers: hv: vmbus: check the creation_status in
vmbus_establish_gpadl()
Drivers: hv: vmbus: offload the handling of channels to two workqueues
drivers/hv/channel.c | 8 ++
drivers/hv/channel_mgmt.c | 188
From: "K. Y. Srinivasan"
Miscellaneous fixes.
Dexuan Cui (2):
Drivers: hv: vmbus: check the creation_status in
vmbus_establish_gpadl()
Drivers: hv: vmbus: offload the handling of channels to two workqueues
drivers/hv/channel.c | 8 ++
drivers/hv/channel_mgmt.c | 188
The function qnx6_fill_super drops the reference to bh2 when superblock
1 is activated via brelse, otherwise it drops the reference to bh1 when
superblock 2 is activated. If error occurs after that, it will try to
drop the references to bh1 and bh2 again. This may result in
use-after-free bugs.
The function qnx6_fill_super drops the reference to bh2 when superblock
1 is activated via brelse, otherwise it drops the reference to bh1 when
superblock 2 is activated. If error occurs after that, it will try to
drop the references to bh1 and bh2 again. This may result in
use-after-free bugs.
From: Dexuan Cui
Commit d86adf482b84 ("scsi: storvsc: Enable multi-queue support") removed
the usage of the API in Jan 2017, and the API is not used since then.
netvsc and storvsc have their own algorithms to determine the outgoing
channel, so this API is useless.
And the API is potentially
From: Dexuan Cui
Commit d86adf482b84 ("scsi: storvsc: Enable multi-queue support") removed
the usage of the API in Jan 2017, and the API is not used since then.
netvsc and storvsc have their own algorithms to determine the outgoing
channel, so this API is useless.
And the API is potentially
Commit 7759eb23fd980 ("block: remove bio_rewind_iter()") removes
bio_rewind_iter(), then no one uses bvec_iter_rewind() any more,
so remove it.
Signed-off-by: Ming Lei
---
include/linux/bvec.h | 24
1 file changed, 24 deletions(-)
diff --git a/include/linux/bvec.h
Commit 7759eb23fd980 ("block: remove bio_rewind_iter()") removes
bio_rewind_iter(), then no one uses bvec_iter_rewind() any more,
so remove it.
Signed-off-by: Ming Lei
---
include/linux/bvec.h | 24
1 file changed, 24 deletions(-)
diff --git a/include/linux/bvec.h
Sorry to have contacted you through this medium without a
previous notice; I had to use the email because it is the easiest
and more confidential way of making contact with people around
the world.
This communication is to inform you that we have programmed your
payment of the $10,000.000.00
Sorry to have contacted you through this medium without a
previous notice; I had to use the email because it is the easiest
and more confidential way of making contact with people around
the world.
This communication is to inform you that we have programmed your
payment of the $10,000.000.00
On Mon, Nov 26, 2018 at 07:58:23AM +0800, Yang Yang wrote:
> When si_mem_available() calculates 'available', it takes SWAP
> into account. But if CONFIG_SWAP is N or SWAP is off(some embedded system
> would like to do that), there is no need to consider it.
I don't understand this patch. The
On Mon, Nov 26, 2018 at 07:58:23AM +0800, Yang Yang wrote:
> When si_mem_available() calculates 'available', it takes SWAP
> into account. But if CONFIG_SWAP is N or SWAP is off(some embedded system
> would like to do that), there is no need to consider it.
I don't understand this patch. The
On Tue, Nov 20, 2018 at 10:58 AM zhong jiang wrote:
>
> On 2018/11/17 9:33, Wengang Wang wrote:
> > The this_cpu_cmpxchg makes the do-while loop pass as long as the
> > s->cpu_slab->partial as the same value. It doesn't care what happened to
> > that slab. Interrupt is not disabled, and new
On Tue, Nov 20, 2018 at 10:58 AM zhong jiang wrote:
>
> On 2018/11/17 9:33, Wengang Wang wrote:
> > The this_cpu_cmpxchg makes the do-while loop pass as long as the
> > s->cpu_slab->partial as the same value. It doesn't care what happened to
> > that slab. Interrupt is not disabled, and new
The function autofs_expire_run calls dput(dentry) to drop the reference
count of dentry. However, dentry is read via autofs_dentry_ino(dentry)
after that. This may result in a use-free-bug. The patch drops the
reference count of dentry only when it is never used.
Signed-off-by: Pan Bian
---
The function autofs_expire_run calls dput(dentry) to drop the reference
count of dentry. However, dentry is read via autofs_dentry_ino(dentry)
after that. This may result in a use-free-bug. The patch drops the
reference count of dentry only when it is never used.
Signed-off-by: Pan Bian
---
Support displaying the average IPC and IPC coverage for symbol
in perf report TUI browser. We create a new sort-key 'ipc' for
that.
For example,
$ perf record -g -b ...
$ perf report -s symbol,ipc or
perf report -s ipc
Overhead Symbol IPC [IPC Coverage]
39.60%
Add supporting of displaying the average IPC and IPC coverage
percentage per function.
For example,
$ perf record -g -b ...
$ perf report -s symbol,ipc
Overhead Symbol IPC [IPC Coverage]
39.60% [.] __random 2.30 [ 54.8%]
18.02% [.] main
Add support to perf report annotate view or perf annotate --stdio2 to
aggregate the IPC derived from timed LBRs per symbol. We compute the
average IPC and the IPC coverage percentage.
For example,
$ perf annotate --stdio2
Percent IPC Cycle (Average IPC: 2.30, IPC Coverage: 54.8%)
Support displaying the average IPC and IPC coverage for symbol
in perf report TUI browser. We create a new sort-key 'ipc' for
that.
For example,
$ perf record -g -b ...
$ perf report -s symbol,ipc or
perf report -s ipc
Overhead Symbol IPC [IPC Coverage]
39.60%
Add supporting of displaying the average IPC and IPC coverage
percentage per function.
For example,
$ perf record -g -b ...
$ perf report -s symbol,ipc
Overhead Symbol IPC [IPC Coverage]
39.60% [.] __random 2.30 [ 54.8%]
18.02% [.] main
Add support to perf report annotate view or perf annotate --stdio2 to
aggregate the IPC derived from timed LBRs per symbol. We compute the
average IPC and the IPC coverage percentage.
For example,
$ perf annotate --stdio2
Percent IPC Cycle (Average IPC: 2.30, IPC Coverage: 54.8%)
Greetings
My name is Miss Alizata Aron. It give me a great pleasure to write you, it
attracts me to write to you so that we can be friends if you will have the
desire as me. i will be very happy to be in communication with you so that we
can get to know each other better and see what
Greetings
My name is Miss Alizata Aron. It give me a great pleasure to write you, it
attracts me to write to you so that we can be friends if you will have the
desire as me. i will be very happy to be in communication with you so that we
can get to know each other better and see what
On Sat, 2018-11-24 at 14:56 -0600, Rob Herring wrote:
> On Wed, Nov 21, 2018 at 8:51 PM Miles Chen wrote:
> >
> > On Wed, 2018-11-21 at 10:39 -0600, Rob Herring wrote:
> > > On Wed, Nov 21, 2018 at 2:11 AM wrote:
> > > >
> > > > From: Miles Chen
> > > >
> > > > When we use more than 32 entries
On Sat, 2018-11-24 at 14:56 -0600, Rob Herring wrote:
> On Wed, Nov 21, 2018 at 8:51 PM Miles Chen wrote:
> >
> > On Wed, 2018-11-21 at 10:39 -0600, Rob Herring wrote:
> > > On Wed, Nov 21, 2018 at 2:11 AM wrote:
> > > >
> > > > From: Miles Chen
> > > >
> > > > When we use more than 32 entries
On 11/25/2018 03:42 PM, Qian Cai wrote:
>
>
> On 11/23/18 10:01 PM, Qian Cai wrote:
>>
>>
>>> On Nov 22, 2018, at 4:56 PM, Thomas Gleixner
>>> wrote:
>>>
>>> On Tue, 20 Nov 2018, Qian Cai wrote:
>>>
>>> Looking deeper at that.
>>>
diff --git a/lib/debugobjects.c b/lib/debugobjects.c
On 11/25/2018 03:42 PM, Qian Cai wrote:
>
>
> On 11/23/18 10:01 PM, Qian Cai wrote:
>>
>>
>>> On Nov 22, 2018, at 4:56 PM, Thomas Gleixner
>>> wrote:
>>>
>>> On Tue, 20 Nov 2018, Qian Cai wrote:
>>>
>>> Looking deeper at that.
>>>
diff --git a/lib/debugobjects.c b/lib/debugobjects.c
On Fri, Nov 23, 2018 at 06:53:37PM +0800, David Laight wrote:
> From: Vincent Chen
> > Sent: 22 November 2018 03:15
> >
> > The Andes FPU coprocessor does not support denormalized number handling.
> > According to the specification, FPU generates a denorm input exception
> > that requires the
On Wed, 2018-10-31 at 14:57 +0800, Yuantian Tang wrote:
> From: Scott Wood
>
> The driver retains compatibility with old device trees, but we don't
> want the old nodes lying around to be copied, or used as a reference
> (some of the mux options are incorrect), or even just being clutter.
>
>
On Fri, Nov 23, 2018 at 06:53:37PM +0800, David Laight wrote:
> From: Vincent Chen
> > Sent: 22 November 2018 03:15
> >
> > The Andes FPU coprocessor does not support denormalized number handling.
> > According to the specification, FPU generates a denorm input exception
> > that requires the
On Wed, 2018-10-31 at 14:57 +0800, Yuantian Tang wrote:
> From: Scott Wood
>
> The driver retains compatibility with old device trees, but we don't
> want the old nodes lying around to be copied, or used as a reference
> (some of the mux options are incorrect), or even just being clutter.
>
>
Hi Marc,
Firstly, thanks for reviewing the patch. Then, I am confused to do upstream on
"linux-can" or "linux-can-next" due to I find "linux-can" is more updated than
"linux-can-next".
Best Regards,
Joakim Zhang
> -Original Message-
> From: Marc Kleine-Budde
> Sent: 2018年11月23日
Hi Marc,
Firstly, thanks for reviewing the patch. Then, I am confused to do upstream on
"linux-can" or "linux-can-next" due to I find "linux-can" is more updated than
"linux-can-next".
Best Regards,
Joakim Zhang
> -Original Message-
> From: Marc Kleine-Budde
> Sent: 2018年11月23日
Hi Steve,
On Sun, 25 Nov 2018 18:31:40 -0600 Steve French wrote:
>
> Both of those cases are intentional fallthroughs and there are
> existing comments in the code noting the reasons for them to
> fallthrough
>
> (also can see the reasoning for these in the commits which introduced
> them from
Hi Steve,
On Sun, 25 Nov 2018 18:31:40 -0600 Steve French wrote:
>
> Both of those cases are intentional fallthroughs and there are
> existing comments in the code noting the reasons for them to
> fallthrough
>
> (also can see the reasoning for these in the commits which introduced
> them from
Bah, I hit send on a partially written draft. I’ll try again soon.
--Andy
> On Nov 25, 2018, at 1:59 PM, Andy Lutomirski wrote:
>
>
>
>> On Nov 25, 2018, at 10:55 AM, Dr. Greg wrote:
>>
>
>>
>>
>> The notion of a launch enclave is critical to establishing these
>> guarantees. As soon
Bah, I hit send on a partially written draft. I’ll try again soon.
--Andy
> On Nov 25, 2018, at 1:59 PM, Andy Lutomirski wrote:
>
>
>
>> On Nov 25, 2018, at 10:55 AM, Dr. Greg wrote:
>>
>
>>
>>
>> The notion of a launch enclave is critical to establishing these
>> guarantees. As soon
Both of those cases are intentional fallthroughs and there are
existing comments in the code noting the reasons for them to
fallthrough
(also can see the reasoning for these in the commits which introduced
them from Sachin c369c9a4a7c82) and dde2356c84662)
On Sun, Nov 25, 2018 at 6:14 PM Stephen
Both of those cases are intentional fallthroughs and there are
existing comments in the code noting the reasons for them to
fallthrough
(also can see the reasoning for these in the commits which introduced
them from Sachin c369c9a4a7c82) and dde2356c84662)
On Sun, Nov 25, 2018 at 6:14 PM Stephen
101 - 200 of 574 matches
Mail list logo
