James Morris wrote:
> CONFIG_MODULE_SIG_KEY="signing_key.pem"
>
> This should be 'certs/signing_key.pem', right?
Yeah - it only gets autogenerated if it's that:
ifeq ($(CONFIG_MODULE_SIG_KEY),"certs/signing_key.pem")
from certs/Makefile.
It may have leaked from an earlier version b
> @@ -2579,20 +2612,22 @@ struct page *buffered_rmqueue(struct zone
> *preferred_zone,
> struct list_head *list;
>
> local_irq_save(flags);
> - pcp = &this_cpu_ptr(zone->pageset)->pcp;
> - list = &pcp->lists[migratetype];
> - if (li
On Mon, May 16, 2016 at 9:40 PM, Geert Uytterhoeven
wrote:
> On Mon, May 16, 2016 at 9:27 PM, Pantelis Antoniou
> wrote:
>>> On May 16, 2016, at 22:06 , Geert Uytterhoeven wrote:
>>> On Mon, May 16, 2016 at 6:52 PM, Pantelis Antoniou
>>> wrote:
Insert overlay symbols to the base tree when
This patch provides VIRT_CPU_ACCOUTING to PPC32 architecture.
PPC32 doesn't have the PACA structure, so we use the task_info
structure to store the accounting data.
In order to reuse on PPC32 the PPC64 functions, all u64 data has
been replaced by 'unsigned long' so that it is u32 on PPC32 and
u64
On Mon, May 16, 2016 at 04:07:53PM -0700, Megha Dey wrote:
>
> ok. I tried at my end too using some printk's and nothing seems to be
> broken. Also, if you intend to use the same commit message, I spell my
> name as Megha Dey and not Day :)
Patch applied with the name corrected.
Thanks,
--
Email
Commit-ID: 683ad8092cd262a02d01377dd17a29d492438b90
Gitweb: http://git.kernel.org/tip/683ad8092cd262a02d01377dd17a29d492438b90
Author: Linus Torvalds
AuthorDate: Mon, 16 May 2016 13:05:45 -0700
Committer: Ingo Molnar
CommitDate: Tue, 17 May 2016 08:25:06 +0200
x86/efi: Fix 7-parameter
On Mon, May 16, 2016 at 09:07:27AM -0400, Vivek Goyal wrote:
> So it became clear that we need a check at mount time to make sure
> d_type is supported otherwise error out. This will require users to
> do mkfs.xfs with ftype=1 to make progress.
>
> I think new defaults for mkfs.xfs are such that f
On Mon, May 16, 2016 at 04:53:50PM +0100, Eric Engestrom wrote:
> On Fri, May 13, 2016 at 11:06:40PM +0530, Muhammad Falak R Wani wrote:
> > It is preferred to use ARRAY_SIZE() for size calculation, instead
> > using sizeof(array)/sizeof(*array). It makes the code more readable.
> >
> > Signed-off
On Mon, May 16, 2016 at 08:43:33AM -0700, Linus Torvalds wrote:
> On Sun, May 15, 2016 at 8:32 PM, Al Viro wrote:
> > FWIW, I considered sending that pile in several pull requests, but for some
> > reason git request-pull v4.6 vfs work.lookups spews something very odd into
> > diffstat - files tha
On 2016/5/16 23:40, Peter Hurley wrote:
> On 05/16/2016 04:35 AM, Zhen Lei wrote:
>> Sometimes, we may only use SSH to login, and build 8250 uart driver as a
>> ko(insmod if needed). But the earlycon may still be necessary, because
>> the kernel boot process may take a long time. It's not good to
When the function sb_bread() fails, the return value should
be -EIO, fix it.
Signed-off-by: Heloise
---
fs/efs/super.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/efs/super.c b/fs/efs/super.c
index cb68dac..368f7dd 100644
--- a/fs/efs/super.c
+++ b/fs/efs/super.c
@
On 05/17/2016 02:24 AM, Stephen Rothwell wrote:
Hi all,
Today's linux-next merge of the net-next tree got a conflict in:
arch/arm64/Kconfig
between commit:
8ee708792e1c ("arm64: Kconfig: remove redundant HAVE_ARCH_TRANSPARENT_HUGEPAGE
definition")
from the arm64 tree and commit:
6
Although unbinding a pinctrl driver requires root privileges but it
still might be used theoretically in certain attacks (by triggering NULL
pointer exception or memory corruption).
Samsung pincontrol drivers are essential for system operation so their
removal is not expected. They do not implemen
Am 21.03.2016 um 14:38 schrieb Greg KH:
> On Mon, Mar 21, 2016 at 11:52:23AM +0100, Stefan Priebe - Profihost AG wrote:
>>
>> Am 20.03.2016 um 22:41 schrieb Greg KH:
>>> On Sun, Mar 20, 2016 at 10:27:23PM +0100, Stefan Priebe wrote:
Am 19.03.2016 um 23:26 schrieb Vlastimil Babka:
> On
On Mon, 16 May 2016, Julia Lawall wrote:
> On Mon, 16 May 2016, SF Markus Elfring wrote:
>
> > >> * Change an error message.
> > >
> > > Why? Is dev_err needed?
> >
> > I interpreted Lee's response in this way.
> > https://lkml.org/lkml/2016/1/11/104
>
> OK. He didn't ask for the message to
On Mon, 16 May 2016, Vignesh R wrote:
> From: Grygorii Strashko
>
> It is seen that just enabling the TSC module triggers a HW_PEN IRQ
> without any interaction with touchscreen by user. This results in first
> suspend/resume sequence to fail as system immediately wakes up from
> suspend as soon
On 20 August 2015 at 16:56, Maxime Ripard
wrote:
>> + /* Enable Dedicated DMA requests */
>> + reg = sun4i_spi_read(sspi, SUN4I_CTL_REG);
>> + reg |= SUN4I_CTL_DMAMC_DEDICATED;
>> + sun4i_spi_write(sspi, SUN4I_CTL_REG, reg);
>> + sun4i_s
Hi Linus,
we're not talking about a driver here - we're talking about a new API
lifted from a driver to generic code because it's commonly useful.
It's also in entirely new files and not a modification of existing code,
and it's always been clear how it is. Some of the code has been in
since Lin
Hi,
[auto build test ERROR on next-20160511]
[cannot apply to v4.6-rc7 v4.6-rc6 v4.6-rc5 v4.6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Christoph-Lameter/Do-not-build-vmstat_refresh-if-the
On 05/17/2016 03:06 AM, Wang Xiaoqiang wrote:
>>yes it would. Why that would matter. The checks should be in an order
>>which could give us a more specific reason with later checks. bad_page()
>
> I see, you mean the later "bad_reason" is the superset of the previous one.
Not exactly. It's not po
Update binding example based on new clock binding scheme.
[1] Documentation/devicetree/bindings/clock/microchip,pic32.txt
Signed-off-by: Purna Chandra Mandal
---
Documentation/devicetree/bindings/serial/microchip,pic32-uart.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a
Update binding example based on new clock binding scheme.
[1] Documentation/devicetree/bindings/clock/microchip,pic32.txt
Signed-off-by: Purna Chandra Mandal
---
Documentation/devicetree/bindings/watchdog/microchip,pic32-dmt.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --
From: James Liao
This patch fixed wrong state of parent clocks if they are registered
after critical clocks.
Signed-off-by: James Liao
---
drivers/clk/clk.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/clk/clk.c b/drivers/clk/clk.c
index ce39add..bf80e39
From: Shunli Wang
Dt-binding file about reset controller is used to provide
kinds of definition, which is referenced by dts file and
IC-specified reset controller driver code.
Signed-off-by: Shunli Wang
Signed-off-by: James Liao
Tested-by: John Crispin
Acked-by: Philipp Zabel
---
include/dt
From: James Liao
Add a Kconfig to define clock configuration for each SoC, and
modify the Makefile to build drivers that only selected in config.
Signed-off-by: Shunli Wang
Signed-off-by: James Liao
Tested-by: John Crispin
Reviewed-by: Matthias Brugger
---
drivers/clk/Kconfig | 1
Update binding example based on new clock binding scheme.
[1] Documentation/devicetree/bindings/clock/microchip,pic32.txt
Signed-off-by: Purna Chandra Mandal
---
Documentation/devicetree/bindings/gpio/microchip,pic32-gpio.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/D
Update binding example based on new clock binding scheme.
[1] Documentation/devicetree/bindings/clock/microchip,pic32.txt
Signed-off-by: Purna Chandra Mandal
---
Documentation/devicetree/bindings/watchdog/microchip,pic32-wdt.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --
From: Shunli Wang
Add MT2701 clock support, include topckgen, apmixedsys,
infracfg, pericfg and subsystem clocks.
Signed-off-by: Shunli Wang
Signed-off-by: James Liao
Tested-by: John Crispin
---
drivers/clk/mediatek/Kconfig | 50 ++
drivers/clk/mediatek/Makefile |7 +
From: Shunli Wang
Add MT2701 clock dt-bindings, include topckgen, apmixedsys,
infracfg, pericfg and subsystem clocks.
Signed-off-by: Shunli Wang
Signed-off-by: James Liao
Tested-by: John Crispin
Reviewed-by: Matthias Brugger
---
include/dt-bindings/clock/mt2701-clk.h | 486 +
From: Shunli Wang
In infrasys and perifsys, there are many reset
control bits for kinds of modules. These bits are
used as actual reset controllers to be registered
into kernel's generic reset controller framework.
Signed-off-by: Shunli Wang
Signed-off-by: James Liao
Tested-by: John Crispin
A
From: James Liao
Add clock controller nodes for MT2701, include topckgen, infracfg,
pericfg, apmixedsys, mmsys, imgsys, vdecsys, hifsys, ethsys and
bdpsys. This patch also add two oscillators that provide clocks for
MT2701.
Signed-off-by: James Liao
---
arch/arm/boot/dts/mt2701.dtsi | 42 +
From: James Liao
This patch adds the binding documentation for apmixedsys, bdpsys,
ethsys, hifsys, imgsys, infracfg, mmsys, pericfg, topckgen and
vdecsys for Mediatek MT2701.
Signed-off-by: James Liao
Tested-by: John Crispin
Acked-by: Rob Herring
---
.../bindings/arm/mediatek/mediatek,apmixe
We used to use a fixed rate clock for the UARTs. Now that we have clock
support we can associate the correct clocks to the UARTs and drop the
26MHz fixed rate UART clock.
Signed-off-by: Erin Lo
---
arch/arm/boot/dts/mt2701.dtsi | 18 --
1 file changed, 8 insertions(+), 10 deletio
Update binding example based on new clock binding documentation.
[1] Documentation/devicetree/bindings/clock/microchip,pic32.txt
Signed-off-by: Purna Chandra Mandal
---
Documentation/devicetree/bindings/mmc/microchip,sdhci-pic32.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
Update binding example based on new clock binding scheme.
[1] Documentation/devicetree/bindings/clock/microchip,pic32.txt
Signed-off-by: Purna Chandra Mandal
---
Documentation/devicetree/bindings/pinctrl/microchip,pic32-pinctrl.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --g
PIC32 clock driver is now implemented as platform driver instead of
as part of of_clk_init(). It meants all the clock modules are available
quite late in the boot sequence. So request for CPU clock by clk_get_sys()
and clk_get_rate() to find c0_timer rate fails.
To fix this use PIC32 specific earl
From: Joshua Henderson
The wrong external interrupt bits are being set, offset by 1.
Signed-off-by: Joshua Henderson
Signed-off-by: Purna Chandra Mandal
---
drivers/irqchip/irq-pic32-evic.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/irqchip/irq-pic32-evic.c
From: James Liao
Remove __init from functions that will be used by init functions
that support probe deferral.
Signed-off-by: James Liao
---
drivers/clk/mediatek/clk-gate.c | 2 +-
drivers/clk/mediatek/clk-mtk.c | 12 ++--
drivers/clk/mediatek/clk-pll.c | 2 +-
3 files changed, 8 i
Allocated memory for 'sport->irq_fault_name' is freed twice, first
in error check of 'if(!sport->irq_rx_name)' and other in fallback
handler.
Signed-off-by: Purna Chandra Mandal
---
drivers/tty/serial/pic32_uart.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/tty/serial/pic32_uart
Optional SOSC is an external fixed clock running at 32768HZ.
So Initialize SOSC rate as per PIC32MZDA datasheet.
Signed-off-by: Purna Chandra Mandal
---
Note: Please pull this complete series through the MIPS tree.
---
drivers/clk/microchip/clk-pic32mzda.c | 1 +
1 file changed, 1 insertion(+
pbclk_set_rate() is using readl_poll_timeout_atomic() even
though spinlock is released. Fix it by replacing with
readl_poll_timeout().
Signed-off-by: Purna Chandra Mandal
---
Note: Please pull this complete series through the MIPS tree.
---
drivers/clk/microchip/clk-core.c | 6 +++---
1 file c
This series is based on clk-next, add clock and reset controller support
for Mediatek MT2701.
This series also refined makefile and Kconfig to support configurable
multiple SoC clock support.
There some code borrowed from [2] in clk-mtk.h, and may need to resolve
conflicts while merging these two
Hi all,
Please do not add any v4.8 destined material to your linux-next included
branches until after v4.7-rc1 has been released.
Changes since 20160516:
The vfs tree gained a conflict against the ext4 tree.
The net-next tree gained a conflict against the arm64 tree.
The spi tree lost its
3047a96d7cfcfca1a6d026ecaec526ea4803e9e/linux-headers.cgz"
repeat_to: 2
kernel:
"/pkg/linux/x86_64-rhel/gcc-4.9/23047a96d7cfcfca1a6d026ecaec526ea4803e9e/vmlinuz-4.5.0-00570-g23047a9"
dequeue_time: 2016-05-17 00:25:26.281743408 +08:00
job_state: finished
loadavg: 39.10 58.24 29.31 1/548
On Mon, May 16, 2016 at 12:25:47PM -0600, Jason Gunthorpe wrote:
> Provide some flags in tpm_class_ops to allow drivers to opt-in to the
> common startup sequence. This is the sequence used by tpm_tis and
> tpm_crb.
>
> All drivers should set this flag.
The commit message should be a much much mo
On 05/16/2016 06:14 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.14.70 release.
There are 17 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
Hello Greg KH,
I make patch same like other, I'm new and I nerver see changelog in other
patches.
Where to add changelog? I followed you are tutorial.
Thanks,
Amit Ghadge
On Mon, May 16, 2016 at 08:34:55PM -0700, Greg KH wrote:
>
> A: No.
> Q: Should I include quotations after my reply?
>
> h
commit d1a792f3b407 ("Update imx-sdma cyclic handling to report residue")
moves updating of BD to isr routine, to avoid stop
of cyclic dma, but there is chance 'new' isr comes before the 'old'
tasklet can be fired, thus cause data loss due to missing of one
tasklet. So move updating of BD back to t
Previously for cyclic dma mode, once sdma fails sdma channel status will
be set to DMA_ERROR, unless the transfer is prepared again, sdmac status
will always be kept to DMA_ERROR, even the transfer for following buffers
is successful.
This patch updates sdmac status to the status of current buffer
Previously in cyclic dma mode when sdma transfer fails for one buffer,
it will mask BD_RROR flag for that buffer descriptor (BD). This flag
won't be cleared unless a new cyclic dma transfer is prepared, so if
sdma script next time iterates to the same BD, even this time the
transfer is successful,
On Mon, May 16, 2016 at 10:46:38AM +0100, Matt Fleming wrote:
> > >
> > > - rq->clock_skip_update = 0;
> > > + /* Clear ACT, preserve everything else */
> > > + rq->clock_update_flags ^= RQCF_ACT_SKIP;
> >
> > The comment says "Clear ACT", but this is really xor, and I am not sure
> > this is ev
this patch set contains the following changes
1. fix issues in cyclic dma
2. add support to SYNC DMA termination
3. avoid system hang, when SDMA channel 0 timeouts
4. add lock to prevent race condition
Jiada Wang (10):
dma: imx-sdma: use chn_real_count to report residue for UART
dma: imx-sdma:
Previously when channel0 timeouts to finish its task,
sdma_run_channel0() just returns without disable channel0,
this will cause continuous interrupt later when channel0
finishs its task and set channel0 interrupt bit.
Signed-off-by: Jiada Wang
---
drivers/dma/imx-sdma.c | 43 +++
Implement device_terminate_all(), so that dmaengine_terminate_async()
can work.
Signed-off-by: Jiada Wang
---
drivers/dma/imx-sdma.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c
index ef5d37c..040cbf2 100644
--- a/drivers/dma/imx-sdm
For uart rx dma data may not receive fully, so the number
of data read by sdma script once isn't always equal to period_len,
thus residue returned from sdma_tx_status() isn't valid for uart rx
dma. The old way to use chn_real_count to report residue should be
used for uart rx dma.
Signed-off-by: J
Previously for cyclic dma mode, once sdma fails sdma channel status will
be set to DMA_ERROR, unless the transfer is prepared again, sdmac status
will always be kept to DMA_ERROR, even the transfer for following buffers
is successful.
This patch updates sdmac status to the status of current buffer
There is race between STOP of SDMA channel and finish of
SDMA transfer, so some times, even after sdma_disable_channel()
is called, the bit of 'terminated channel' in INTR may still get
asserted, thus cause an extra sdma tasklet be called.
Add flag 'enabled' to each sdma channel to indicate its sta
Previously in cyclic dma mode when sdma transfer fails for one buffer,
it will mask BD_RROR flag for that buffer descriptor (BD). This flag
won't be cleared unless a new cyclic dma transfer is prepared, so if
sdma script next time iterates to the same BD, even this time the
transfer is successful,
commit d1a792f3b407 ("Update imx-sdma cyclic handling to report residue")
moves updating of BD to isr routine, to avoid stop
of cyclic dma, but there is chance 'new' isr comes before the 'old'
tasklet can be fired, thus cause data loss due to missing of one
tasklet. So move updating of BD back to t
In case the corresponding channel has already been terminated,
then instead of go on updating channel status, driver should abort from
sdma_handle_channel_loop(), otherwise channel status will be updated
incorrecly.
This patch also adds lock to avoid race between terminate of channel,
and updaing
Previously when channel0 timeouts to finish its task,
sdma_run_channel0() just returns without disable channel0,
this will cause continuous interrupt later when channel0
finishs its task and set channel0 interrupt bit.
Signed-off-by: Jiada Wang
---
drivers/dma/imx-sdma.c | 43 +++
When SDMA channel0 timeouts, even it's disabled in error path,
but sometimes we still see its interrupt bit be asserted,
which causes irq routine be triggered continuously because
no one else clears this bit.
This commit clears channel0 interrupt as well in irq routine,
so that even channel0 timeo
Implement the new device_synchronize() callback to allow proper
synchronization when stopping a channel. Since the driver already makes
sure that no new complete callbacks are scheduled after the
device_terminate_all() has been called, all left to do in the
device_synchronize() callback is to wait
Implement device_terminate_all(), so that dmaengine_terminate_async()
can work.
Signed-off-by: Jiada Wang
---
drivers/dma/imx-sdma.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/dma/imx-sdma.c b/drivers/dma/imx-sdma.c
index ef5d37c..040cbf2 100644
--- a/drivers/dma/imx-sdm
this patch set contains the following changes
1. fix issues in cyclic dma
2. add support to SYNC DMA termination
3. avoid system hang, when SDMA channel 0 timeouts
4. add lock to prevent race condition
Jiada Wang (10):
dma: imx-sdma: use chn_real_count to report residue for UART
dma: imx-sdma:
Implement the new device_synchronize() callback to allow proper
synchronization when stopping a channel. Since the driver already makes
sure that no new complete callbacks are scheduled after the
device_terminate_all() has been called, all left to do in the
device_synchronize() callback is to wait
When SDMA channel0 timeouts, even it's disabled in error path,
but sometimes we still see its interrupt bit be asserted,
which causes irq routine be triggered continuously because
no one else clears this bit.
This commit clears channel0 interrupt as well in irq routine,
so that even channel0 timeo
There is race between STOP of SDMA channel and finish of
SDMA transfer, so some times, even after sdma_disable_channel()
is called, the bit of 'terminated channel' in INTR may still get
asserted, thus cause an extra sdma tasklet be called.
Add flag 'enabled' to each sdma channel to indicate its sta
For uart rx dma data may not receive fully, so the number
of data read by sdma script once isn't always equal to period_len,
thus residue returned from sdma_tx_status() isn't valid for uart rx
dma. The old way to use chn_real_count to report residue should be
used for uart rx dma.
Signed-off-by: J
In case the corresponding channel has already been terminated,
then instead of go on updating channel status, driver should abort from
sdma_handle_channel_loop(), otherwise channel status will be updated
incorrecly.
This patch also adds lock to avoid race between terminate of channel,
and updaing
On Mon, May 16, 2016 at 10:28:32PM -0400, James Bottomley wrote:
> On Mon, 2016-05-16 at 19:41 +, Serge Hallyn wrote:
> > Hey James,
> >
> > I probably did something wrong - but i applied your patch onto 4.6,
> > compiled in shiftfs, did
> >
> > mount -t shiftfs -o uidmap=0:10:65536,gidma
In testing with HiKey, we found that since
commit 3f30b158eba5 ("asix: On RX avoid creating bad Ethernet
frames"),
we're seeing lots of noise during network transfers:
[ 239.027993] asix 1-1.1:1.0 eth0: asix_rx_fixup() Data Header synchronisation
was lost, remaining 988
[ 239.037310] asix 1-1.1
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Tue, May 17, 2016 at 08:55:56AM +0530, Amit Ghadge wrote:
> I check with "./scripts/checkpatch.pl --file --terse
> drivers/staging/comedi/drivers/quatech_daqp_cs.c" and show the warning
> message,
There is a rare race when we remove an entry from the global list
hv_context.percpu_list[cpu] in hv_process_channel_removal() ->
percpu_channel_deq() -> list_del(): at this time, if vmbus_on_event() ->
process_chn_event() -> pcpu_relid2channel() is trying to query the list,
we can get the general p
I check with "./scripts/checkpatch.pl --file --terse
drivers/staging/comedi/drivers/quatech_daqp_cs.c" and show the warning message,
"drivers/staging/comedi/drivers/quatech_daqp_cs.c:646: WARNING: Prefer
'unsigned int' to bare use of 'unsigned'"
This patch reduced the warning message.
On Mon,
On Monday 16 May 2016 08:18 PM, Rob Herring wrote:
On Wed, May 11, 2016 at 11:18:05AM +0530, Keerthy wrote:
This updates the device tree according to the preferred way of parsing
the nodes using the regulator framework.
Signed-off-by: Keerthy
---
.../devicetree/bindings/regulator/tps65218.
Hello Rui,
Here is material for 4.7 on thermal SoC. I have rebased this branch on
top of latest linus tree. But this material have been tested and on
linux-next for several weeks.
The following changes since commit b6ae4055f4ab55c05df31cc1b6a7ea8c85eb525d:
Merge tag 'arm64-perf' of
git://git.
On Tue, May 17, 2016 at 10:23:55AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the vfs tree got conflicts in:
>
> fs/ext4/ext4.h
> fs/ext4/indirect.c
> fs/ext4/inode.c
>
> between commit:
>
> 914f82a32d02 ("ext4: refactor direct IO code")
>
> from the ext4
Clean up checkpatch warnings and errors:
* WARNING: Block comments use * on subsequent lines
* WARNING: Missing a blank line after declarations
* WARNING: networking block comments don't use an empty /* line, use /*
* ERROR: code indent should use tabs where possible
* WARNING: please, no space be
On Monday 05/16 at 15:51 -0600, Sathya Prakash Veerichetty wrote:
> Our understanding is the relationship between the SCSI host and SAS end
> devices is a parent-child and before ripping of SCSI host we need to rip of
> all the children.
I know at least HPSA does the opposite, Elliott observes tha
Hi Tomasz
I used the patchset and added "PATCH V6 11/13 specic quirks", tested on
HiSilicon D02 board but met the below problem.
[2.614115] [] hisi_pcie_init+0x6c/0x1ec
[2.619571] [] pci_ecam_create+0x130/0x1ec
[2.625209] [] pci_acpi_scan_root+0x160/0x218
[2.631096] [] acpi_pci_
On 2016/5/16 23:10, Chao Yu wrote:
Hi chao,
Hi Pengyang,
On 2016/5/16 18:40, Hou Pengyang wrote:
When collecting data segment(gc_data_segment), there is a race condition
between evict and phases of gc:
0) ra_node_page(dnode)
1) ra_node_page(inode)
<--- evict the inode
2) f2fs_ig
Matt Fleming reported seeing crashes when enabling and disabling
function profiling which uses function graph tracer. Later Namhyung Kim
hit a similar issue and he found that the issue was due to the jmp to
ftrace_stub in ftrace_graph_call was only two bytes, and when it was
changed to jump to the
> There appears to be no kfifo support for iov_iter though, so I just went
> with a simple buffer.
>
> I haven’t looked at the patch too carefully so this is an RFC rather
> than an actual patch at this point. It does compile at least.
>
> Regardless, the more I thin about it, the more I’m under
From: Masami Hiramatsu
Instead of using a raw string, use DSO__NAME_KALLSYMS and
DSO__NAME_KCORE macros for kallsyms and kcore.
Signed-off-by: Masami Hiramatsu
Cc: Ananth N Mavinakayanahalli
Cc: Brendan Gregg
Cc: Hemant Kumar
Cc: Namhyung Kim
Cc: Peter Zijlstra
Link: http://lkml.kernel.org
From: Arnaldo Carvalho de Melo
So that it can be used for other stack related knobs, such as the
upcoming one to tweak the max number of of contexts per stack sample.
In all those cases we can only change the value if there are no perf
sessions collecting stacks, so they need to grab that mutex,
From: Arnaldo Carvalho de Melo
We will use it to count how many addresses are in the entry->ip[] array,
excluding PERF_CONTEXT_{KERNEL,USER,etc} entries, so that we can really
return the number of entries specified by the user via the relevant
sysctl, kernel.perf_event_max_contexts, or via the pe
From: Namhyung Kim
Currently 'perf stat' always counts task-clock event by default. But
it's somewhat confusing for system-wide targets (especially with 'sleep
N' as the 'sleep' task just sleeps and doesn't use cputime). Changing
to cpu-clock event instead for that case makes more sense IMHO.
From: Namhyung Kim
The commit 140aeadc1fb5 ("perf stat: Abstract stat metrics printing")
changed how shadow metrics are printed, but it missed to update the
width of the stalled backend cycles event to 7.2% like others. This
resulted in misaligned output like below:
Performance counter stats
From: Namhyung Kim
Currently only the task-clock event updates the runtime_nsec so it
cannot show the metric when using cpu-clock events. However cpu clock
works basically same as task-clock, so no need to not update the runtime
IMHO.
Before:
# perf stat -a -e cpu-clock,context-switches,page
From: He Kuang
When unwinding callchains on a different machine, vdso info should be
available so the unwind process won't be interrupted if address falls
into vdso region. But in most cases, the addresses of sample events are
not in vdso range, the buildid of a zero hit vdso won't be stored into
From: Arnaldo Carvalho de Melo
This makes perf_callchain_{user,kernel}() receive the max stack
as context for the perf_callchain_entry, instead of accessing
the global sysctl_perf_event_max_stack.
Cc: Adrian Hunter
Cc: Alexander Shishkin
Cc: Alexei Starovoitov
Cc: Brendan Gregg
Cc: David Ahe
:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git
tags/perf-core-for-mingo-20160516
for you to fetch changes up to a29d5c9b8167dbc21a7ca8c0302e3799f9063b4e:
perf tools: Separate accounting of contexts and real addresses in a stack
trace (2016-05-16 23:11:54 -0300
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Monday, May 16, 2016 1:16
> To: Dexuan Cui
> Cc: gre...@linuxfoundation.org; net...@vger.kernel.org; linux-
> ker...@vger.kernel.org; de...@linuxdriverproject.org; o...@aepfle.de;
> a...@canonical.com; jasow...@redhat.com; cav...@redhat.com
From: Arnaldo Carvalho de Melo
The perf_sample->ip_callchain->nr value includes all the entries in the
ip_callchain->ip[] array, real addresses and PERF_CONTEXT_{KERNEL,USER,etc},
while what the user expects is that what is in the kernel.perf_event_max_stack
sysctl or in the upcoming per event pe
From: Arnaldo Carvalho de Melo
The perf_sample->ip_callchain->nr value includes all the entries in the
ip_callchain->ip[] array, real addresses and PERF_CONTEXT_{KERNEL,USER,etc},
while what the user expects is that what is in the kernel.perf_event_max_stack
sysctl or in the upcoming per event pe
From: Arnaldo Carvalho de Melo
We need have different helpers to account how many contexts we have in
the sample and for real addresses, so do it now as a prep patch, to
ease review.
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Jiri Olsa
Cc: Namhyung Kim
Cc: Peter Zijlstra
Link: http://lkml.
From: Andi Kleen
When the scaling factor is a full integer don't display fractional
digits. This avoids unnecessary .00 output for topdown metrics with
scale factors.
v2: Remove redundant check.
Signed-off-by: Andi Kleen
Acked-by: Jiri Olsa
Cc: Peter Zijlstra
Link:
http://lkml.kernel.org/r/
On Mon, May 16, 2016 at 5:27 AM, Mark Brown wrote:
>
> Mark Brown (26):
> regulator: Deprecate regulator_can_change_voltage()
This needs to be fixed.
It causes a build warning, and it's just not acceptable. We've had
driver subsystems do this before, and then the warning stays around
for y
On Mon, May 16, 2016 at 07:27:28PM -0700, Kees Cook wrote:
> This document attempts to codify the intent around kernel self-protection
> along with discussion of both existing and desired technologies, with
> attention given to the rationale behind them, and the expectations of
> their usage.
>
>
1 - 100 of 816 matches
Mail list logo
