Split the device_control callback of the Freescale MXS DMA driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/mxs-dma.c | 59 ---
1 file ch
Split the device_control callback of the SiRF Prima 2 DMA driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/sirf-dma.c | 43 +--
1 file changed, 1
Split the device_control callback of the AMBA PL330 DMA driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/pl330.c | 108 ++--
1 file chang
On Wed, Oct 01, 2014 at 10:38:45AM +0100, Arnd Bergmann wrote:
[...]
> The arm32 implementations of pci_domain_nr/pci_proc_domain can probably be
> removed if we change the arm32 pcibios_init_hw function to call the new
> interfaces that set the domain number.
I wished, but it is a bit more comp
Split the device_control callback of the Hisilicon K3 DMA driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/k3dma.c | 197
1 file cha
On Tue, Oct 14, 2014 at 06:31:09AM +, Romain Perier wrote:
> Several drivers create their own devicetree property when they register
> poweroff capabilities. This is for example the case for mfd, regulator
> or power drivers which define "vendor,system-power-controller" property.
> This patch a
(resending to new documentation maintainer, as the original patch
seemingly got lost)
Jonathan,
Please apply the below patch documenting that hugetlbfs can be sticky-mounted.
Thanks beforehand,
Kirill
On Thu, Sep 04, 2014 at 10:14:31AM -0700, Ken Chen wrote:
> On Thu, Sep 4, 2014 at 6:20 AM,
Split the device_control callback of the NVidia Tegra20 APB DMA driver to make
use of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/tegra20-apb-dma.c | 22 ++
1 file changed, 2 inserti
Split the device_control callback of the NBPF AXI DMA driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/nbpfaxi.c | 93 +--
1 file changed
On Wed, 2014-10-22 at 17:50 +0400, Roman Gushchin wrote:
> Incoming packet is dropped silently by sk_filter(), if the skb was
> allocated from pfmemalloc reserves and the corresponding socket is
> not marked with the SOCK_MEMALLOC flag.
>
> Igb driver allocates pages for DMA with __skb_alloc_page(
Split the device_control callback of the TI EDMA driver to make use of the
newly introduced callbacks, that will eventually be used to retrieve slave
capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/edma.c | 50 +++---
1 file changed, 15 inse
Split the device_control callback of the Broadcom BCM2835 DMA driver to make
use of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
Acked-by: Stephen Warren
---
drivers/dma/bcm2835-dma.c | 31 -
Split the device_control callback of the IPU IDMAC driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/ipu/ipu_idmac.c | 96 -
1 file changed, 5
Nowadays, some drivers don't have anything in there channel allocation
callbacks anymore.
Remove the BUG_ON if those callbacks aren't implemented, in order to allow
drivers to not implement them.
Signed-off-by: Maxime Ripard
---
drivers/dma/dmaengine.c | 18 +++---
1 file changed, 1
Split the device_control callback of the Qualcomm BAM DMA driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/qcom_bam_dma.c | 85 +++---
1 file cha
Split the device_control callback of the Freescale IMX DMA driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/imx-dma.c | 103 +-
1 file ch
All tools/hv daemons do mandatory daemon() on startup. However, no pidfile
is created, this make it difficult for an init system to track such daemons.
Modern linux distros use systemd as their init system. It can handle the
daemonizing by itself, however, it requires a daemon to stay in foreground
Split the device_control callback of the Intel MID DMA driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/intel_mid_dma.c | 25 ++---
1 file changed, 6 insertions(+),
Split the device_control callback of the Cirrus Logic EP93xx driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/ep93xx_dma.c | 41 +++--
1 file changed
On Mon, Oct 20, 2014 at 11:22:12AM -0400, Johannes Weiner wrote:
> pc->mem_cgroup had to be left intact after uncharge for the final LRU
> removal, and !PCG_USED indicated whether the page was uncharged. But
> since 0a31bc97c80c ("mm: memcontrol: rewrite uncharge API") pages are
> uncharged after
Split the device_control callback of the Marvell MMP PDMA driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/mmp_pdma.c | 109 +
1 file cha
Split the device_control callback of the Freescale IMX SDMA driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/imx-sdma.c | 66 +++---
1 file c
Split the device_control callback of the JZ4740 DMA driver to make use of the
newly introduced callbacks, that will eventually be used to retrieve slave
capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/dma-jz4740.c | 20 +++-
1 file changed, 3 insertions(+), 17 deletion
Split the device_control callback of the Marvell MMP TDMA driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/mmp_tdma.c | 82 +++---
1 file cha
dma_slave_caps is very important to the generic layers that might interact with
dmaengine, such as ASoC. Unfortunately, it has been added as yet another
dma_device callback, and most of the existing drivers haven't implemented it,
reducing its reliability.
Introduce a generic behaviour and a flag
Split the device_control callback of the Freescale EDMA driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/fsl-edma.c | 106 +++--
1 file chang
Split the device_control callback of the DesignWare DMA driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/dw/core.c | 82 +++
1 file chang
From: Mathieu Poirier
Some drivers on ARMv7 need 64 bit read and writes.
Signed-off-by: Mathieu Poirier
---
arch/arm/include/asm/io.h | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/include/asm/io.h b/arch/arm/include/asm/io.h
index 1805674..861e52c 100644
-
Split out the pause and resume operations to callbacks of their own. In order
to preserve some backwark compatibility, the dmaengine_pause/dmaengine_resume
are still falling back on dmaengine_device_control.
Eventually, that will allow to get the device capabilities in a generic way,
removing the
We are removing the dmaengine_device_control API, that shouldn't even have been
exposed in the first place. Change the callers to use the proper API.
Signed-off-by: Maxime Ripard
---
drivers/crypto/ux500/cryp/cryp_core.c | 4 ++--
drivers/crypto/ux500/hash/hash_core.c | 2 +-
2 files changed, 3
Split the device_control callback of the Atmel HDMAC driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/at_hdmac.c | 121 +
1 file changed,
The fact that the channel configuration is done in device_control is rather
misleading, since it's not really advertised as such, plus, the fact that the
framework exposes a function of its own makes it not really intuitive, while
we're losing the type checking whenever we pass that unsigned long a
We are removing the dmaengine_device_control API, that shouldn't even have been
exposed in the first place. Change the callers to use the proper API.
Signed-off-by: Maxime Ripard
---
drivers/tty/serial/atmel_serial.c | 10 --
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/
The previous code was relying on the fact that the slave_caps were to be
defined on a per channel basis.
However, this proved to be a bit overkill, since every driver filling these so
far were hardcoding it, disregarding which channel was actually given.
Add these capabilities to the dma_device s
On 10/21/14 20:42, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20141021:
>
on x86_64:
when MEDIA_SUBDRV_AUTOSELECT is not enabled:
when DVB_USB_AZ6027=y and DVB_STB0899=m and DVB_STB6100=m:
drivers/built-in.o: In function `az6027_frontend_attach':
az6027.c:(.text+0x18c50d): undefined
Split the device_control callback of the AMBA PL08x DMA driver to make use
of the newly introduced callbacks, that will eventually be used to retrieve
slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/amba-pl08x.c | 156 +++
1 file chang
On Wed, Oct 22, 2014 at 10:06:23AM -0600, mathieu.poir...@linaro.org wrote:
> @@ -306,10 +324,13 @@ extern void _memset_io(volatile void __iomem *, int,
> size_t);
> __raw_readw(c)); __r; })
> #define readl_relaxed(c) ({ u32 __r = le32_to_cpu((__force __le32)
Split the device_control callback of the ST-Ericsson COH901318 DMA driver to
make use of the newly introduced callbacks, that will eventually be used to
retrieve slave capabilities.
Signed-off-by: Maxime Ripard
---
drivers/dma/coh901318.c | 137 +---
1
On Mon, 13 Oct 2014, Stefano Stabellini wrote:
> On Mon, 13 Oct 2014, Will Deacon wrote:
> > On Mon, Oct 13, 2014 at 12:16:14PM +0100, Stefano Stabellini wrote:
> > > On Fri, 10 Oct 2014, Stefano Stabellini wrote:
> > > > On Fri, 10 Oct 2014, Will Deacon wrote:
> > > > > On Fri, Oct 10, 2014 at 12:
In order to migrate the drivers without triggering a BUG_ON for the converted
drivers, which would cause bisectability issues, we need to remove that check
before removing the device_control function entirely.
Signed-off-by: Maxime Ripard
---
drivers/dma/dmaengine.c | 2 --
1 file changed, 2 del
On Mon 20-10-14 11:22:12, Johannes Weiner wrote:
> pc->mem_cgroup had to be left intact after uncharge for the final LRU
> removal, and !PCG_USED indicated whether the page was uncharged. But
> since 0a31bc97c80c ("mm: memcontrol: rewrite uncharge API") pages are
> uncharged after the final LRU re
dma_chan_get uses a rather interesting error handling and code path.
Change it to something more usual in the kernel.
Signed-off-by: Maxime Ripard
---
drivers/dma/dmaengine.c | 36 +++-
1 file changed, 19 insertions(+), 17 deletions(-)
diff --git a/drivers/dma/d
On Mon, Oct 20, 2014 at 11:22:11AM -0400, Johannes Weiner wrote:
> PCG_MEM is a remnant from an earlier version of 0a31bc97c80c ("mm:
> memcontrol: rewrite uncharge API"), used to tell whether migration
> cleared a charge while leaving pc->mem_cgroup valid and PCG_USED set.
> But in the final versi
Hi,
As we discussed a couple of weeks ago, this is the third attempt at
creating a generic behaviour for slave capabilities retrieval so that
generic layers using dmaengine can actually rely on that.
That has been done mostly through two steps: by moving out the
sub-commands of the device_control
See below ...
On 14-10-22 03:26 PM, Mikulas Patocka wrote:
This is Martin Petersen's xcopy patch
(https://git.kernel.org/cgit/linux/kernel/git/mkp/linux.git/commit/?h=xcopy&id=0bdeed274e16b3038a851552188512071974eea8)
with some bug fixes, ported to the current kernel.
This patch makes it possib
The dmaengine header abbreviates destination as at least two different strings.
Make a coherent use of a single one.
Signed-off-by: Maxime Ripard
Acked-by: Mark Brown
Acked-by: Laurent Pinchart
Acked-by: Stephen Warren
---
drivers/dma/bcm2835-dma.c | 2 +-
drivers/dma/edma.c
Split out the terminate_all command from device_control to a dma_device
callback. In order to preserve backward capability, still rely on
device_control if no such callback has been implemented.
Eventually, this will allow to create a generic dma_slave_caps callback.
Signed-off-by: Maxime Ripard
On Wed, Oct 22, 2014 at 06:39:56AM +, Eunbong Song wrote:
Applying - but:
> + if(regs)
^^^
There should be a blank between if and opening parenthesis.
Ralf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.ke
On 10/22, Peter Zijlstra wrote:
>
> So I worry about cache aliasing (not an issue on x86), so by touching
> 'random' pages that might be freed and reissued to back userspace, we
> could be accessing the one page through multiple virtual mappings which
> therefore result in aliases.
Or this page ca
On Wed, Oct 22, 2014 at 02:29:06PM +0200, Pali Rohár wrote:
> On Tuesday 21 October 2014 06:27:23 Guenter Roeck wrote:
> > On 10/20/2014 09:46 AM, Pali Rohár wrote:
> > > Ok, I will describe my problem. Guenter, maybe you can find
> > > another solution/fix for it.
> > >
> > > Calling i8k_get_temp
Hi,
A question/request came up during our cache to cache analysis. We were
wondering if give an unique mmap2 id (major, minor, inode, inode
generation), if it was possible to determine a cpu socket id that memory
was attached to at the time of the captured perf event?
We ran into a scenario awhi
On 22 October 2014 18:11, Russell King - ARM Linux
wrote:
> On Wed, Oct 22, 2014 at 10:06:23AM -0600, mathieu.poir...@linaro.org wrote:
>> @@ -306,10 +324,13 @@ extern void _memset_io(volatile void __iomem *, int,
>> size_t);
>> __raw_readw(c)); __r; })
>> #
On Wed, Oct 22, 2014 at 08:29:56AM -0700, Tony Lindgren wrote:
> * Johan Hovold [141022 04:12]:
> > On Sat, Oct 11, 2014 at 12:08:18PM -0700, Tony Lindgren wrote:
> > > * Johan Hovold [141011 02:42]:
> > > > On Fri, Oct 10, 2014 at 12:54:22PM -0500, Felipe Balbi wrote:
> > > > >
> > > > > is thi
Traversal of the ACPI device tree was not done right. It should lookup
PPI only under the ACPI device that it is associated. Otherwise, it could
match to a wrong PPI interface if there are two TPM devices in the device
tree.
Removed global ACPI handle and version string from tpm_ppi.c as this
is r
This patch set fixes two race conditions in the TPM subsystem:
* Two-phase initialization for struct tpm_chip so that device can
initialize fully initialize before exposing itself to the user
space. Also, in future TPM2 devices must be flagged before they
can be registered.
* Machines where
Merged transmit_cmd() functions in tpm-interface.c and tpm-sysfs.c.
Added "tpm_" prefix for consistency sake. Changed cmd parameter as
opaque. This enables to use separate command structures for TPM1
and TPM2 commands in future. Loose coupling works fine here.
Signed-off-by: Jarkko Sakkinen
---
On Wed, Oct 22, 2014 at 10:54:26AM -0500, Eric Rost wrote:
> On Wed, 2014-10-22 at 11:10 -0400, Jason Cooper wrote:
> > At some point, Eric Rost wrote:
...
> > > diff --git a/drivers/staging/skein/Makefile
> > > b/drivers/staging/skein/Makefile
> > > index a14aadd..1be01fe 100644
> > > --- a/drive
tpm_register_hardware() and tpm_remove_hardware() are called often
before initializing the device. This is wrong order since it could
be that main TPM driver needs a fully initialized chip to be able to
do its job. For example, now it is impossible to move common startup
functions such as tpm_do_se
With the clock assignment device tree changes, the clocks get
initialized properly but the search for those clocks fails with
errors:
[0.00] i.MX clk 4: register failed with -17
[0.00] i.MX clk 5: register failed with -17
This is because the module can't find those clocks anymore,
This patchset is v2 of "ARM: dts: vf500/vf610: support VF500 SoC",
and grew by some patches. It now also solves some issues uncovered
by the "ARM: vf610m4: Add Vybrid Cortex-M4 support" patchset. The
next Cortex-M4 patchset will then base on this patchset.
I could again not use the -M/-B paramete
Add Colibri VF50 device tree files vf500-colibri.dtsi and
vf500-colibri-eval-v3.dts, in line with the Colibri VF61 device tree
files. However, to minimize dupplication we also add vf-colibri.dtsi
and vf-colibri-eval-v3.dtsi which contain the common device tree
nodes.
Signed-off-by: Stefan Agner
-
On Tue 21-10-14 14:19:10, Johannes Weiner wrote:
> 0a31bc97c80c ("mm: memcontrol: rewrite uncharge API") changed page
> migration to uncharge the old page right away. The page is locked,
> unmapped, truncated, and off the LRU. But it could race with a
> finishing writeback, which then doesn't get
This adds more generic base device trees for Vybrid SoCs. There
are three series of Vybrid SoC commonly available:
- VF3xx series: single core, Cortex-A5 without external memory
- VF5xx series: single core, Cortex-A5
- VF6xx series: dual core, Cortex-A5/Cortex-M4
The second digit represents the pr
The clock controller module (CCM) has several clock inputs, which
are connected to external crystal oscillators. To reflect this,
assign these fixed clocks to the CCM node directly.
This especially resolves initialization order dependencies we had
with the earlier initialization code: When resolvi
On Wed, Oct 22, 2014 at 12:48 AM, Geert Uytterhoeven
wrote:
> Hi Alexei,
>
> On Tue, 21 Oct 2014, Alexei Starovoitov wrote:
>> On Tue, Oct 21, 2014 at 10:30 AM, Geert Uytterhoeven
>> wrote:
>> > Signed-off-by: Geert Uytterhoeven
>> > ---
>> > arch/m68k/include/asm/unistd.h | 2 +-
>
Hi Jarkko,
> Jarkko Sakkinen (3):
> tpm: merge duplicate transmit_cmd() functions
> tpm: two-phase chip management functions
> tpm: fix multiple race conditions in tpm_ppi.c
the patchset introduces a sparse error:
CHECK /home/phuewe/linux-2.6-host/drivers/char/tpm/tpm_tis.c
/home/phuewe/linux
On Wednesday 22 October 2014 18:19:47 Guenter Roeck wrote:
> On Wed, Oct 22, 2014 at 02:29:06PM +0200, Pali Rohár wrote:
> > On Tuesday 21 October 2014 06:27:23 Guenter Roeck wrote:
> > > On 10/20/2014 09:46 AM, Pali Rohár wrote:
> > > > Ok, I will describe my problem. Guenter, maybe you can
> > >
Hi,
On Sun, Oct 19, 2014 at 8:23 PM, Jaehoon Chung wrote:
> Hi.
>
> On 10/17/2014 09:44 PM, Alim Akhtar wrote:
>> Hi Doug,
>>
>> On Thu, Oct 16, 2014 at 9:40 PM, Doug Anderson wrote:
>>> Alim,
>>>
>>> On Thu, Oct 16, 2014 at 5:57 AM, Alim Akhtar wrote:
Hi Doug,
On Tue, Oct 14, 20
On Wed, Oct 22, 2014 at 06:14:50PM +0200, Oleg Nesterov wrote:
> Hmm. so perhaps I misunderstood your concern...
>
> Do you mean that on !x86 a plain LOAD can "corrupt" the memory as it seen
> from another vaddr?
I'm not sure. Stores for sure, loads I'm not sure about.
I suspect loads are OK, th
On Wed, Oct 22, 2014 at 07:23:54PM +0300, Jarkko Sakkinen wrote:
> Merged transmit_cmd() functions in tpm-interface.c and tpm-sysfs.c.
> Added "tpm_" prefix for consistency sake. Changed cmd parameter as
> opaque. This enables to use separate command structures for TPM1
> and TPM2 commands in futur
On Mon, Oct 20, 2014 at 04:47:48PM +0200, Javier Martinez Canillas wrote:
> of_get_regulation_constraints() calls of_get_child_by_name() to find the
> regulator-state-{mem,disk} child nodes for each regulator. This function
> increments the device node reference counter but this is not decremented
On Wed, Oct 22, 2014 at 4:58 PM, Jiri Olsa wrote:
> On Thu, Oct 09, 2014 at 06:34:45PM +0200, Stephane Eranian wrote:
>
> SNIP
>
>> --- a/arch/x86/kernel/cpu/perf_event_intel.c
>> +++ b/arch/x86/kernel/cpu/perf_event_intel.c
>> @@ -12,6 +12,7 @@
>> #include
>> #include
>> #include
>> +#inclu
On Wed, Oct 22, 2014 at 05:06:23PM +0100, mathieu.poir...@linaro.org wrote:
> +#if __LINUX_ARM_ARCH__ >= 5
My old ARMv5 book does not list LDRD/STRD. It looks like they only come
with ARMv5TE. Are there any processors prior to this supported by the
kernel?
> +static inline void __raw_writeq(u64 v
On Wed, Oct 22, 2014 at 12:20:26PM -0400, Don Zickus wrote:
> Hi,
>
> A question/request came up during our cache to cache analysis. We were
> wondering if give an unique mmap2 id (major, minor, inode, inode
> generation), if it was possible to determine a cpu socket id that memory
> was attached
* Johan Hovold [141022 09:25]:
> On Wed, Oct 22, 2014 at 08:29:56AM -0700, Tony Lindgren wrote:
> > * Johan Hovold [141022 04:12]:
> > > On Sat, Oct 11, 2014 at 12:08:18PM -0700, Tony Lindgren wrote:
> > > > * Johan Hovold [141011 02:42]:
> > > > > On Fri, Oct 10, 2014 at 12:54:22PM -0500, Felip
On 2014.10.22 17:19, Éric Piel wrote:
> On the HP laptop I had (with HPQ0004), no fake keys were reported.
I guess this is a new "feature", then.
> It should be noted that on my laptop, the accelerometer is completely
> decoupled from the hard disk. For example, when freefall is detected,
> nothin
On Wed, 2014-10-22 at 15:54 +0200, Antonios Motakis wrote:
> On Tue, Oct 21, 2014 at 6:34 PM, Alex Williamson
> wrote:
> > On Mon, 2014-10-13 at 15:10 +0200, Antonios Motakis wrote:
> >> This patch enables the IOCTLs VFIO_DEVICE_GET_REGION_INFO ioctl call,
> >> which allows the user to learn about
On Mon, Oct 20, 2014 at 04:47:51PM +0200, Javier Martinez Canillas wrote:
> + char *states[PM_SUSPEND_MAX + 1] = {
> + [PM_SUSPEND_MEM] = "regulator-state-mem",
> + [PM_SUSPEND_MAX] = "regulator-state-disk",
> + };
This still has the same problem as your previous p
>> If you are convinced that dropping the null tests is a good idea, then you
>> can submit the patch that makes the change to the relevant maintainers and
>> mailing lists.
Would you like to integrate the following proposal into your source code
repository?
Regards,
Markus
>From e61965bbcb1
On Wed, Oct 22, 2014 at 9:59 AM, Lorenzo Pieralisi
wrote:
> ... I wonder what's the
> best course of action. Putting together all the bits and pieces required
> to remove PCI bios dependency from this patch can take a while, I wonder
> whether we should aim for merging this driver (rebased on top
On Tue, Oct 21, 2014 at 9:11 AM, Sergey wrote:
> Hey everyone,
>
> I'm glad we're having some discussion on this, because we have almost
> exactly the same kernel wishlist internally for elementary OS / Pantheon DE.
>
> I believe I can further elaborate on the VFS monitoring part. We need a file
>
On 10/21/2014 07:47 PM, Bjorn Helgaas wrote:
> [+cc Joerg, Eric, Tom, David, iommu list]
>
> On Wed, Oct 15, 2014 at 2:14 AM, Takao Indoh
> wrote:
>> (2014/10/14 18:34), Li, ZhenHua wrote:
>>> I tested on the latest stable version 3.17, it works well.
>>>
>>> On 10/10/2014 03:13 PM, Li, Zhen-Hua
On Wed, Oct 22, 2014 at 07:38:37AM -0700, Paul E. McKenney wrote:
> On Wed, Oct 22, 2014 at 11:53:49AM +0200, Jiri Kosina wrote:
> > On Tue, 21 Oct 2014, Jiri Kosina wrote:
> >
> > > Hi,
> > >
> > > I am seeing the lockdep report below when resuming from suspend-to-disk
> > > with current Linus'
On Wed, 2014-10-22 at 15:55 +0200, Antonios Motakis wrote:
> On Tue, Oct 21, 2014 at 6:51 PM, Alex Williamson
> wrote:
> > On Mon, 2014-10-13 at 15:10 +0200, Antonios Motakis wrote:
> >> Allow to memory map the MMIO regions of the device so userspace can
> >> directly access them. PIO regions are
Hi,
We've run into a AB/BA deadlock situation involving a driver lock and
the CPU hotplug lock on a 3.10 based kernel. The situation is this:
CPU 0 CPU 1
-
Start CPU hotplug
mutex_lock(&cpu_hotplug.lock)
Run CPU hotplug notifier
On 10/21, Victor Kamensky wrote:
>
> +static int dump_write_last_byte(struct coredump_params *cprm)
> +{
> + char lastbyte = 0;
> + struct file *file = cprm->file;
> +
> + if (file->f_op->llseek && file->f_op->llseek != no_llseek) {
> + if (dump_interrupted() ||
> +
On Wed, 22 Oct 2014 11:53:49 +0200 (CEST)
Jiri Kosina wrote:
> Still, the lockdep stacktrace is bogus and didn't really help
> understanding this. Any idea why it's wrong?
Could possibly be from a tail call?
>
> > ==
> > [ INFO: possible
Arnd, Olof, Kevin,
This is my first batch of fixes for 3.18.
The power/reset driver part is there because it was introduced through arm-soc
and it seems that it's better to continue like that.
The MAINTAINERS entry is better if included the soonest.
Note as well that it's my first pull-request fr
Commit 2ed53c0d6cc9 ("x86/smpboot: Speed up suspend/resume by avoiding
100ms sleep for CPU offline during S3") introduced completions to CPU
offlining process. These completions are not initialized on Xen kernels
causing a panic in play_dead_common().
Move handling of die_complete into common rout
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Wednesday, October 22, 2014 9:07 AM
> To: KY Srinivasan; Haiyang Zhang; de...@linuxdriverproject.org
> Cc: linux-kernel@vger.kernel.org
> Subject: [PATCH] tools: hv: introduce -n/--no-daemon option
>
> All
On Tue, Oct 21, 2014 at 5:12 PM, Kevin Fenzi wrote:
> On Mon, 20 Oct 2014 14:53:59 -0600
> Kevin Fenzi wrote:
>
>> On Mon, 20 Oct 2014 16:43:26 -0400
>> Dave Jones wrote:
>>
>> > I've seen similar soft lockup traces from the sys_unshare path when
>> > running my fuzz tester. It seems that if yo
On 14-10-22 01:22 AM, Arnd Bergmann wrote:
On Tuesday 21 October 2014 17:11:08 Scott Branden wrote:
OK, I will remove the "iProc SoC based Machine types". This was
grouping all iProc based SoCs under one menu and parallels what the
existing "Broadcom Mobile Soc Support" menu does.
I can create
On Wed, Oct 22, 2014 at 06:35:53PM +0200, Pali Rohár wrote:
> On Wednesday 22 October 2014 18:19:47 Guenter Roeck wrote:
> > On Wed, Oct 22, 2014 at 02:29:06PM +0200, Pali Rohár wrote:
> > > On Tuesday 21 October 2014 06:27:23 Guenter Roeck wrote:
> > > > On 10/20/2014 09:46 AM, Pali Rohár wrote:
>
On Wed, 2014-10-22 at 16:25 +0300, Jani Nikula wrote:
> On Wed, 22 Oct 2014, Joe Perches wrote:
> > On Wed, 2014-10-22 at 13:43 +0300, Jani Nikula wrote:
> >> Since commit 66b47b4a9dad00e45c049d79966de9a3a1f4d337
> >> Author: Kees Cook
> >> Date: Mon Oct 13 15:51:57 2014 -0700
> >> checkpat
On Tue, Oct 21, 2014 at 08:09:38PM +0200, Bastien Nocera wrote:
> On Tue, 2014-10-21 at 11:00 -0700, John Stultz wrote:
> > On Tue, Oct 21, 2014 at 10:14 AM, Bastien Nocera wrote:
> > >> As for: 'Export of "wake reason" when the system wakes up (rtc alarm,
> > >> lid open, etc.) and wakealarm (/sy
On Wed, Oct 22, 2014 at 07:23:55PM +0300, Jarkko Sakkinen wrote:
> tpm_register_hardware() and tpm_remove_hardware() are called often
> before initializing the device. This is wrong order since it could
> be that main TPM driver needs a fully initialized chip to be able to
> do its job. For example
Jinkun,
On Wed, Oct 22, 2014 at 12:53 AM, jinkun.hong
wrote:
> +#define to_rockchip_pd(_gpd) container_of(_gpd, struct rockchip_domain, base)
> +
> +static int rockchip_pmu_set_idle_request(struct rockchip_domain *pd,
> +bool idle)
> +{
> + u32 idle_m
On Wed, Oct 22, 2014 at 06:22:09PM +0200, Mathieu Poirier wrote:
> I had this conversation with a colleague who reviewed the work. If
> the architecture is < 5 the __raw_ versions aren't included and the
> compiler won't complain until someone tries to use the macros. We
> achieve the same result
On Wed, Oct 22, 2014 at 10:54 AM, Alexander Duyck
wrote:
> On 10/21/2014 07:47 PM, Bjorn Helgaas wrote:
>> [+cc Joerg, Eric, Tom, David, iommu list]
>>
>> On Wed, Oct 15, 2014 at 2:14 AM, Takao Indoh
>> wrote:
>>> (2014/10/14 18:34), Li, ZhenHua wrote:
I tested on the latest stable version
On Wed, Oct 22, 2014 at 5:07 PM, Jiri Olsa wrote:
> On Thu, Oct 09, 2014 at 06:34:39PM +0200, Stephane Eranian wrote:
>> From: Maria Dimakopoulou
>>
>
> SNIP
>
>> +struct intel_excl_cntrs *allocate_excl_cntrs(int cpu)
>> +{
>> + struct intel_excl_cntrs *c;
>> + int i;
>> +
>> + c = kz
501 - 600 of 972 matches
Mail list logo
