Re: [systemd-devel] [RFC v2 3/6] kthread: warn on kill signal if not OOM

11.09.2014 03:10, Luis R. Rodriguez wrote: Tom, thanks for reviewing this! My reply below! On Tue, Sep 9, 2014 at 11:46 PM, Tom Gundersen wrote: On Tue, Sep 9, 2014 at 10:45 PM, Luis R. Rodriguez wrote: On Tue, Sep 9, 2014 at 12:35 PM, James Bottomley wrote: On Tue, 2014-09-09 at 12:16

Re: [PATCH] mm: softdirty: unmapped addresses between VMAs are clean

On Wed, Sep 10, 2014 at 04:36:28PM -0700, Andrew Morton wrote: > On Wed, 10 Sep 2014 16:24:46 -0700 Peter Feiner wrote: > > @@ -1048,32 +1048,51 @@ static int pagemap_pte_range(pmd_t *pmd, unsigned > > long addr, unsigned long end, > > + while (1) { > > + unsigned long vm_start =

[PATCH V2] ASoC: fsl_ssi: refine ipg clock usage in this module

Move the ipg clock enable and disable operation to startup and shutdown, that is only enable ipg clock when ssi is working. Keep clock is disabled when ssi is in idle. otherwise, _fsl_ssi_set_dai_fmt function need to be called in probe, so add ipg clock control for it. Signed-off-by: Shengjiu

[PATCH v5 3/7] kvm: Make init_rmode_identity_map() return 0 on success.

In init_rmode_identity_map(), there two variables indicating the return value, r and ret, and it return 0 on error, 1 on success. The function is only called by vmx_create_vcpu(), and r is redundant. This patch removes the redundant variable r, and make init_rmode_identity_map() return 0 on

Re: [RFC/PATCH v2 02/10] x86_64: add KASan support

On 09/11/2014 08:01 AM, H. Peter Anvin wrote: > On 09/10/2014 07:31 AM, Andrey Ryabinin wrote: >> This patch add arch specific code for kernel address sanitizer. >> >> 16TB of virtual addressed used for shadow memory. >> It's located in range [0x8000 - 0x9000] >> Therefore

[PATCH v5 7/7] kvm, mem-hotplug: Unpin and remove nested_vmx->apic_access_page.

Just like we removed kvm_arch->apic_access_page, nested_vmx->apic_access_page becomes useless for the same reason. This patch removes nested_vmx->apic_access_page, and use gfn_to_page() to pin it in memory when we need it, and unpin it after then. Signed-off-by: Tang Chen ---

Re: [PATCH] f2fs: Fix recover when nid of non-inode dnode < nid of inode

On Wed, Sep 10, 2014 at 07:08:32PM +0800, huang ying wrote: > On Wed, Sep 10, 2014 at 3:21 PM, Jaegeuk Kim wrote: > > > On Tue, Sep 09, 2014 at 07:31:49PM +0800, huang ying wrote: > > > On Tue, Sep 9, 2014 at 3:09 PM, Jaegeuk Kim wrote: > > > > > > > Hi, > > > > > > > > On Tue, Sep 09, 2014 at

[PATCH v5 2/7] kvm: Remove ept_identity_pagetable from struct kvm_arch.

kvm_arch->ept_identity_pagetable holds the ept identity pagetable page. But it is never used to refer to the page at all. In vcpu initialization, it indicates two things: 1. indicates if ept page is allocated 2. indicates if a memory slot for identity page is initialized Actually,

[PATCH v5 1/7] kvm: Use APIC_DEFAULT_PHYS_BASE macro as the apic access page address.

We have APIC_DEFAULT_PHYS_BASE defined as 0xfee0, which is also the address of apic access page. So use this macro. Signed-off-by: Tang Chen Reviewed-by: Gleb Natapov --- arch/x86/kvm/svm.c | 3 ++- arch/x86/kvm/vmx.c | 6 +++--- 2 files changed, 5 insertions(+), 4 deletions(-) diff

[PATCH v5 0/7] kvm, mem-hotplug: Do not pin ept identity pagetable and apic access page.

ept identity pagetable and apic access page in kvm are pinned in memory. As a result, they cannot be migrated/hot-removed. But actually they don't need to be pinned in memory. [For ept identity page] Just do not pin it. When it is migrated, guest will be able to find the new page in the next ept

[PATCH v5 4/7] kvm, mem-hotplug: Reload L1' apic access page on migration in vcpu_enter_guest().

apic access page is pinned in memory. As a result, it cannot be migrated/hot-removed. Actually, it is not necessary to be pinned. The hpa of apic access page is stored in VMCS APIC_ACCESS_ADDR pointer. When the page is migrated, kvm_mmu_notifier_invalidate_page() will invalidate the

[PATCH v5 5/7] kvm, mem-hotplug: Reload L1's apic access page on migration when L2 is running.

This patch only handle "L1 and L2 vm share one apic access page" situation. When L1 vm is running, if the shared apic access page is migrated, mmu_notifier will request all vcpus to exit to L0, and reload apic access page physical address for all the vcpus' vmcs (which is done by patch 5/6).

[PATCH v5 6/7] kvm, mem-hotplug: Unpin and remove kvm_arch->apic_access_page.

To make apic access page migratable, we do not pin it in memory now. When it is migrated, we should reload its physical address for all vmcses. But when we tried to do this, all vcpu will access kvm_arch->apic_access_page without any locking. This is not safe. Actually, we do not need

Re: [RFC/PATCH v2 02/10] x86_64: add KASan support

On 09/11/2014 08:46 AM, Andi Kleen wrote: > On Wed, Sep 10, 2014 at 09:33:11PM -0700, H. Peter Anvin wrote: >> On 09/10/2014 09:29 PM, Sasha Levin wrote: >>> On 09/11/2014 12:26 AM, H. Peter Anvin wrote: Except you just broke PVop kernels. >>> >>> So is this why v2 refuses to boot on my KVM

Re: BUG uncore_assign_events

On Wed, 10 Sep 2014 23:59:08 +0200 Andi Kleen wrote: > > # addr2line -i -e ivb-ep-build/vmlinux 81025f18 > > > > arch/x86/include/asm/bitops.h:318 > > arch/x86/kernel/cpu/perf_event_intel_uncore.c:3339 > > i == zero (ok) > c points to some kernel looking address > hwc->idx is 64 > >

Re: [PATCH v2.2 2/2] dt-bindings: Adding compatible attribute for SKY81452 regulator

On Sat, Sep 06, 2014 at 03:38:28PM +0100, Mark Brown wrote: > On Fri, Sep 05, 2014 at 10:55:07AM +0900, Gyungoh Yoo wrote: > > On Mon, Sep 01, 2014 at 11:31:58AM +0100, Mark Brown wrote: > > > > Why is this a good idea - can this driver be used for anything other > > > than a sky81452? > > >

Re: [RFC v2 0/9] KVM-VFIO IRQ forward control

On Thu, 2014-09-11 at 05:10 +0200, Christoffer Dall wrote: > On Tue, Sep 02, 2014 at 03:05:41PM -0600, Alex Williamson wrote: > > On Mon, 2014-09-01 at 14:52 +0200, Eric Auger wrote: > > > This RFC proposes an integration of "ARM: Forwarding physical > > > interrupts to a guest VM"

Re: [RFC v2 8/9] KVM: KVM-VFIO: generic KVM_DEV_VFIO_DEVICE command and IRQ forwarding control

On Thu, 2014-09-11 at 05:10 +0200, Christoffer Dall wrote: > On Mon, Sep 01, 2014 at 02:52:47PM +0200, Eric Auger wrote: > > This patch introduces a new KVM_DEV_VFIO_DEVICE attribute. > > > > This is a new control channel which enables KVM to cooperate with > > viable VFIO devices. > > > > The

Re: [RFC/PATCH v2 02/10] x86_64: add KASan support

On 09/10/2014 09:46 PM, Andi Kleen wrote: > On Wed, Sep 10, 2014 at 09:33:11PM -0700, H. Peter Anvin wrote: >> On 09/10/2014 09:29 PM, Sasha Levin wrote: >>> On 09/11/2014 12:26 AM, H. Peter Anvin wrote: Except you just broke PVop kernels. >>> >>> So is this why v2 refuses to boot on my KVM

Re: [RFC/PATCH v2 02/10] x86_64: add KASan support

On Wed, Sep 10, 2014 at 09:33:11PM -0700, H. Peter Anvin wrote: > On 09/10/2014 09:29 PM, Sasha Levin wrote: > > On 09/11/2014 12:26 AM, H. Peter Anvin wrote: > >> Except you just broke PVop kernels. > > > > So is this why v2 refuses to boot on my KVM guest? (was digging > > into that before I

Re: [PATCH] mmc: dw_mmc: add support for ARM64

Hi, Alim. On 09/11/2014 11:35 AM, Alim Akhtar wrote: > Hi Jaehoon, > On Sep 11, 2014 11:18 AM, "Jaehoon Chung" > wrote: >> >> On 09/09/2014 08:31 PM, Alim Akhtar wrote: >> > Hi Ulf, >> > >> > On Tue, Sep 9, 2014 at 12:21 PM, Ulf Hansson > >

Re: [PATCH v10 20/21] ext4: Add DAX functionality

On Wed, Sep 10, 2014 at 07:49:40PM +0300, Boaz Harrosh wrote: > On 09/03/2014 02:13 PM, Dave Chinner wrote: > <> > > > > When direct IO fails ext4 falls back to buffered IO, right? And > > dax_do_io() can return partial writes, yes? > > > > There is no buffered writes with DAX. .I.E buffered

Re: [PATCH] cpufreq, release policy->rwsem on error

On 10 September 2014 19:42, Prarit Bhargava wrote: > I have not been able to reliably reproduce the hardware failure that caused > the warning. In order to reproduce this I resorted to (sorry for the > cut-and-paste) > > diff --git a/drivers/cpufreq/pcc-cpufreq.c >

Re: [RFC/PATCH v2 02/10] x86_64: add KASan support

On 09/10/2014 09:29 PM, Sasha Levin wrote: > On 09/11/2014 12:26 AM, H. Peter Anvin wrote: >> Except you just broke PVop kernels. > > So is this why v2 refuses to boot on my KVM guest? (was digging > into that before I send a mail out). > No, KVM should be fine. It is Xen PV which ends up as a

Re: [RFC/PATCH v2 02/10] x86_64: add KASan support

On 09/10/2014 09:29 PM, Sasha Levin wrote: > On 09/11/2014 12:26 AM, H. Peter Anvin wrote: >> Except you just broke PVop kernels. > > So is this why v2 refuses to boot on my KVM guest? (was digging > into that before I send a mail out). > No, KVM should be fine. It is Xen PV which ends up as a

[PATCH] ARM: dts: Switch i2c0 to 400kHz on rk3288-evb-rk808

We should be able to talk to the PMIC at 400kHz. No need to talk at the slow 100kHz. As measured by ftrace (with a bunch of extra patches, since cpufreq for rk808 hasn't landed yet): before this change: cpu0_set_target() => ~500us after this change: cpu0_set_target() => ~300us

Re: [RFC/PATCH v2 02/10] x86_64: add KASan support

On 09/11/2014 12:26 AM, H. Peter Anvin wrote: > Except you just broke PVop kernels. So is this why v2 refuses to boot on my KVM guest? (was digging into that before I send a mail out). Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

Re: linux-3.16.2 queue (3.16.1+)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/6/14, 11:18 PM, Greg KH wrote: > On Sun, Sep 07, 2014 at 02:47:55AM +0200, Matt wrote: >> On Thu, Aug 28, 2014 at 9:18 PM, Matt >> wrote: >>> On Thu, Aug 28, 2014 at 5:32 PM, Greg KH >>> wrote: On Thu, Aug 28, 2014 at 05:27:27PM +0200,

Re: [RFC/PATCH v2 02/10] x86_64: add KASan support

Except you just broke PVop kernels. Sent from my tablet, pardon any formatting problems. > On Sep 10, 2014, at 15:45, Dave Hansen wrote: > >> On 09/10/2014 01:30 PM, Andrey Ryabinin wrote: >> Yes, there is a reason for this. For inline instrumentation we need to >> catch access to userspace

RE: [PATCH v2] sgi-xp: Do not use BUG_ON(!spin_is_locked())

-Original Message- From: Sanjeev Sharma [mailto:sanjeev_sha...@mentor.com] Sent: Wednesday, August 20, 2014 11:06 AM To: c...@sgi.com; robinmh...@gmail.com Cc: linux-kernel@vger.kernel.org; Sharma, Sanjeev; Sharma, Sanjeev Subject: [PATCH v2] sgi-xp: Do not use BUG_ON(!spin_is_locked())

Fwd:

http://jackson.com.sg/_cool-video.avi?nylyn108655 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH] RTC: RK808: remove tm_def structure

Chris, On Wed, Sep 10, 2014 at 7:04 PM, Chris Zhong wrote: > Signed-off-by: Chris Zhong It's good to add a description, like: If the date/time is invalid at bootup, there's no reason to set it to a bogus value. We can just let the data and time be invalid until someone makes it valid. > ---

Re: [RFC/PATCH v2 02/10] x86_64: add KASan support

On 09/10/2014 07:31 AM, Andrey Ryabinin wrote: > This patch add arch specific code for kernel address sanitizer. > > 16TB of virtual addressed used for shadow memory. > It's located in range [0x8000 - 0x9000] > Therefore PAGE_OFFSET has to be changed from

RE: [PATCH] zd1211rw: replace ZD_ASSERT with lockdep_assert_held()

-Original Message- From: Johannes Berg [mailto:johan...@sipsolutions.net] Sent: Friday, August 22, 2014 5:01 PM To: Sharma, Sanjeev Cc: d...@gentoo.org; k...@deine-taler.de; linvi...@tuxdriver.com; linux-wirel...@vger.kernel.org; net...@vger.kernel.org; linux-kernel@vger.kernel.org

Re: [RFC/PATCH v2 02/10] x86_64: add KASan support

On 09/10/2014 07:31 AM, Andrey Ryabinin wrote: > This patch add arch specific code for kernel address sanitizer. > > 16TB of virtual addressed used for shadow memory. > It's located in range [0x8000 - 0x9000] > Therefore PAGE_OFFSET has to be changed from

Re: [PATCH v3 16/17] arcmsr: support new adapter ARC12x4 series

On Wed, 2014-09-10 at 11:58 +0200, Tomas Henzl wrote: > On 09/09/2014 06:30 PM, Christoph Hellwig wrote: > > Ching, > > > > do you have a chance to address Thomas second concern below? As > > far as I can tell (Thomas, please correct me) that's the last > > outstanding concern, and I'd really

Re: [RFC/PATCH v2 01/10] Add kernel address sanitizer infrastructure.

On 09/10/2014 10:31 AM, Andrey Ryabinin wrote: > +ifdef CONFIG_KASAN > + ifeq ($(call cc-option, $(CFLAGS_KASAN)),) > +$(warning Cannot use CONFIG_KASAN: \ > + -fsanitize=kernel-address not supported by compiler) > + endif > +endif This seems to always indicate that my gcc doesn't

Re: [PATCH] mfd: RK808: Add register caching

On 09/10/2014 07:06 AM, Doug Anderson wrote: Let's define the voltatile registers (those that can't be cached) and enable caching. The rk808 is accessed almost constantly with cpufreq so this is really nice. As measured by ftrace: before this change: cpu0_set_target() => ~2200us after

Re: [PATCH v6 4/4] phy: exynos5-usbdrd: Calibrate LOS levels for exynos5420/5800

Hi, On Thursday, September 11, 2014 1:52 AM, "Julius Werner" wrote right, use that to call phy_init() at the right time, then you need to add a new ->calibrate() method which, likely, will only be used by you ;-) so you mean, the xhci should itself call phy_init() at a time suitable,

Re: [RFC v2 4/9] VFIO: platform: handler tests whether the IRQ is forwarded

On Mon, Sep 01, 2014 at 02:52:43PM +0200, Eric Auger wrote: > In case the IRQ is forwarded, the VFIO platform IRQ handler does not > need to disable the IRQ anymore. In that mode, when the handler completes add a comma after completes > the IRQ is not deactivated but only its priority is

Re: [PATCH v10 09/21] Replace the XIP page fault handler with the DAX page fault handler

On Wed, Sep 10, 2014 at 11:23:37AM -0400, Matthew Wilcox wrote: > On Wed, Sep 03, 2014 at 05:47:24PM +1000, Dave Chinner wrote: > > > + error = get_block(inode, block, , 0); > > > + if (!error && (bh.b_size < PAGE_SIZE)) > > > + error = -EIO; > > > + if (error) > > > + goto

Re: [RFC v2 0/9] KVM-VFIO IRQ forward control

On Tue, Sep 02, 2014 at 03:05:41PM -0600, Alex Williamson wrote: > On Mon, 2014-09-01 at 14:52 +0200, Eric Auger wrote: > > This RFC proposes an integration of "ARM: Forwarding physical > > interrupts to a guest VM" (http://lwn.net/Articles/603514/) in > > KVM. > > > > It enables to transform a

Re: [RFC v2 6/9] VFIO: Extend external user API

On Mon, Sep 01, 2014 at 02:52:45PM +0200, Eric Auger wrote: > New functions are added to be called from ARM KVM-VFIO device. This commit message seems somewhat random. This patch doesn't deal with anything ARM specific, it introduces some generic functions that allows users external to vfio

Re: [RFC v2 7/9] KVM: KVM-VFIO: add new VFIO external API hooks

On Mon, Sep 01, 2014 at 02:52:46PM +0200, Eric Auger wrote: > add functions that implement the gateway to the extended Capital letter when beginning a new sentence. Also the reference to 'the extended VFIO API' feels a bit weird. Can't you make your commit message a little more descriptive of

Re: [RFC v2 9/9] KVM: KVM-VFIO: ARM forwarding control

On Mon, Sep 01, 2014 at 02:52:48PM +0200, Eric Auger wrote: > Enables forwarding control for ARM. By defining > __KVM_HAVE_ARCH_KVM_VFIO_FORWARD the patch enables > KVM_DEV_VFIO_DEVICE_FORWARD/UNFORWARD_IRQ command on ARM. As a > result it brings an optimized injection/completion handling for >

Re: [RFC v2 8/9] KVM: KVM-VFIO: generic KVM_DEV_VFIO_DEVICE command and IRQ forwarding control

On Mon, Sep 01, 2014 at 02:52:47PM +0200, Eric Auger wrote: > This patch introduces a new KVM_DEV_VFIO_DEVICE attribute. > > This is a new control channel which enables KVM to cooperate with > viable VFIO devices. > > The kvm-vfio device now holds a list of devices (kvm_vfio_device) > in

Re: [RFC v2 2/9] KVM: ARM: VGIC: add forwarded irq rbtree lock

On Mon, Sep 01, 2014 at 02:52:41PM +0200, Eric Auger wrote: > add a lock related to the rb tree manipulation. The rb tree can be Ok, I can't hold myself back any longer. Please begin sentences with a capital letter. You don't do this in French? :) > searched in one thread (irqfd handler for

Re: [RFC v2 1/9] KVM: ARM: VGIC: fix multiple injection of level sensitive forwarded IRQ

On Mon, Sep 01, 2014 at 02:52:40PM +0200, Eric Auger wrote: > Fix multiple injection of level sensitive forwarded IRQs. > With current code, the second injection fails since the state bitmaps > are not reset (process_maintenance is not called anymore). > New implementation consists in fully

Re: [PATCH v3] ARM: KVM: add irqfd support

On Mon, Sep 01, 2014 at 10:53:04AM +0200, Eric Auger wrote: > This patch enables irqfd on ARM. > > irqfd framework enables to inject a virtual IRQ into a guest upon an > eventfd trigger. User-side uses KVM_IRQFD VM ioctl to provide KVM with > a kvm_irqfd struct that associates a VM, an eventfd, a

Re: [RFC v2 5/9] KVM: KVM-VFIO: update user API to program forwarded IRQ

On Mon, Sep 01, 2014 at 02:52:44PM +0200, Eric Auger wrote: > add new device group commands: > - KVM_DEV_VFIO_DEVICE_FORWARD_IRQ and > KVM_DEV_VFIO_DEVICE_UNFORWARD_IRQ > > which enable to turn forwarded IRQ mode on/off. > > the kvm_arch_forwarded_irq struct embodies a forwarded IRQ > >

Re: [PATCH] KVM: EVENTFD: remove inclusion of irq.h

On Mon, Sep 01, 2014 at 12:11:19PM +0200, Paolo Bonzini wrote: > Il 01/09/2014 10:36, Eric Auger ha scritto: > > No more needed. irq.h would be void on ARM. > > > > Signed-off-by: Eric Auger > > > > --- > > > > I don't think irq.h is needed anymore since Paul Mackerras' work. However > > I did

[PATCH v2 5/5] toshiba_acpi: Change touchpad store to check for invalid values

The function toshiba_touchpad_store is not checking for invalid values and simply returns silently. This patch checks for invalid values and returns accordingly. Signed-off-by: Azael Avalos --- drivers/platform/x86/toshiba_acpi.c | 14 ++ 1 file changed, 10 insertions(+), 4

[PATCH v2 4/5] toshiba_acpi: Support new keyboard backlight type

Newer Toshiba models now come with a new (and different) keyboard backlight implementation with three modes of operation: TIMER, ON and OFF, and the LED is controlled internally by the firmware. This patch adds support for that type of backlight, changing the existing code to accomodate the new

Re: mm: BUG in unmap_page_range

120 anon_vma 880bc858a200 vm_ops (null) [ 4018.870776] pgoff 41bc8 file (null) private_data (null) [ 4018.879731] flags: 0x8100070(mayread|maywrite|mayexec|account) [ 4018.881324] [ cut here ] [ 4018.882612] kernel BUG at mm/migrate.c:155! [ 40

Re: [PATCH] mmc: Add delay between CMD6 and CMD13 for Sandisk eMMC cards

Hi, On 09/09/2014 09:26 PM, Jean-Michel Hautbois wrote: > Tested on a i.MX6 board, with Sandisk SDIN5D1-2G. > Without this patch, I/O errors occur. > This eMMC seems to have a different Manufacturer ID as it reads 0x45 > and not 0x2 as specified in datasheet. I think this patch don't merge into

Re: [PATCH v4 2/4] dt-bindings: document Rockchip thermal

On Wed, 2014-09-10 at 09:24 +0200, Heiko Stübner wrote: > Am Dienstag, 9. September 2014, 21:14:18 schrieb edubez...@gmail.com: > > Hello, > > > > On Tue, Sep 9, 2014 at 9:02 PM, Zhang Rui wrote: > > > On Tue, 2014-09-09 at 11:09 -0400, Eduardo Valentin wrote: > > >> Hello > > >> > > >> On Tue,

RE: [PATCH] clocksource: Add BE/LE APIs support for clocksource counter reading.

> Cc: daniel.lezc...@linaro.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH] clocksource: Add BE/LE APIs support for clocksource > counter reading. > > On Wed, 10 Sep 2014, Xiubo Li wrote: > > So you add BE/LE APIs according to the subject line, but you fail > again to tell WHY. If that

[PATCH v6] spi: spi-imx: add DMA support

Enable DMA support on i.mx6. The read speed can increase from 600KB/s to 1.2MB/s on i.mx6q. You can disable or enable dma function in dts. If not set "dma-names" in dts, spi will use PIO mode. This patch only validate on i.mx6, not i.mx5, but encourage ones to apply this patch on i.mx5 since they

[PATCH 1/2] dmaengine: Add QCOM ADM DMA driver

Add the DMA engine driver for the QCOM Application Data Mover (ADM) DMA controller found in the MSM8960 and IPQ/APQ8064 platforms. The ADM supports both memory to memory transactions and memory to/from peripheral device transactions. The controller also provides flow control capabilities for

Re: [PATCH] mmc: dw_mmc: add support for ARM64

On 09/09/2014 08:31 PM, Alim Akhtar wrote: > Hi Ulf, > > On Tue, Sep 9, 2014 at 12:21 PM, Ulf Hansson wrote: >> On 29 August 2014 12:24, Alim Akhtar wrote: >>> There are upcoming ARM64 SoCs with dw_mmc host controller. >>> >>> Signed-off-by: Alim Akhtar >>> --- >>> drivers/mmc/host/Kconfig |

[PATCH 2/2] dmaengine: qcom_adm: Add device tree binding

Add device tree binding support for the QCOM ADM DMA driver. Signed-off-by: Andy Gross --- Documentation/devicetree/bindings/dma/qcom_adm.txt | 62 1 file changed, 62 insertions(+) create mode 100644 Documentation/devicetree/bindings/dma/qcom_adm.txt diff --git

[RESEND PATCH 0/2] Add Qualcomm ADM dmaengine driver

I am resending this patch set at the request of the maintainer. The original text is shown below. This patch set introduces the dmaengine driver for the Qualcomm Application Data Mover (ADM) DMA controller present on MSM8960, APQ8064, and IPQ8064 devices. The initial version of this driver will

linux-next: manual merge of the arm64 tree with the net tree

Hi Catalin, Today's linux-next merge of the arm64 tree got a conflict in Documentation/networking/filter.txt between commit 1d7efe9dfaa6 ("Documentation: filter: Add MIPS to architectures with BPF JIT") from the net tree and commit e54bcde3d69d ("arm64: eBPF JIT compiler") from the arm64 tree. I

Re: [PATCH] fix mmc hang during boot on socfpga

Hi, Pavel. On 09/10/2014 05:56 AM, Pavel Machek wrote: > On Tue 2014-09-09 10:32:14, Olof Johansson wrote: >> On Tue, Sep 9, 2014 at 5:19 AM, Pavel Machek wrote: >>> >>> Without this patch, boot hangs when trying to mount root filesystem on >>> socfpga platform in about 50% cases. >> >> I think

Re: [PATCH v2] checkpatch: look for common misspellings

On Wed, 2014-09-10 at 15:52 -0700, Andrew Morton wrote: > Have a kernel joke: [] > @@ -553,6 +553,7 @@ jeffies||jiffies > +kubys|linus Gimmu Smftre/// -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo

[PATCH] RTC: RK808: remove tm_def structure

Signed-off-by: Chris Zhong --- drivers/rtc/rtc-rk808.c | 17 ++--- 1 file changed, 2 insertions(+), 15 deletions(-) diff --git a/drivers/rtc/rtc-rk808.c b/drivers/rtc/rtc-rk808.c index 22c8514..df42257 100644 --- a/drivers/rtc/rtc-rk808.c +++ b/drivers/rtc/rtc-rk808.c @@ -325,17

Re: [RFC] memory cgroup: my thoughts on memsw

(2014/09/09 19:39), Vladimir Davydov wrote: For your purpose, you need to implement your method in system-wide way. It seems crazy to set per-cgroup-anon-limit for avoding system-wide-oom. You'll need help of system-wide-cgroup-configuration-middleware even if you have a method in a cgroup. If

Re: [PATCH v2 1/2] ARM: dts: dra7: Add CPSW and MDIO module nodes for dra7

On Wed, Sep 10, 2014 at 07:07:26PM +0530, Mugunthan V N wrote: > Add CPSW and MDIO related device tree data for DRA7XX and made as status > disabled. Phy-id, pinmux for active and sleep state needs to be added in > board dts files and enable the CPSW device. > > Signed-off-by: Mugunthan V N >

Re: [PATCH v5] spi: spi-imx: add DMA support

On Wed, Sep 10, 2014 at 04:52:16PM +0100, Mark Brown wrote: > On Wed, Sep 10, 2014 at 11:18:01PM +0800, Robin Gong wrote: > > On Wed, Sep 10, 2014 at 12:45:30PM +0100, Mark Brown wrote: > > > > > Yes, you're right. I should use "transfer->tx_sg->sgl == NULL" or > > > > "transfer->rx_sg->sgl ==

Re: [PATCH 3.2 00/94] 3.2.62-rc1 review

On Mon, 2014-08-04 at 13:45 -0700, Guenter Roeck wrote: > On Mon, Aug 04, 2014 at 08:49:39PM +0100, Ben Hutchings wrote: > > On Mon, 2014-08-04 at 10:55 -0700, Guenter Roeck wrote: > > > On Mon, Aug 04, 2014 at 05:48:31PM +0100, Ben Hutchings wrote: > > > > This is the start of the stable review

Re: [RFC] memory cgroup: my thoughts on memsw

(2014/09/10 21:01), Vladimir Davydov wrote: On Mon, Sep 08, 2014 at 10:53:48PM +0900, Kamezawa Hiroyuki wrote: (2014/09/08 20:01), Vladimir Davydov wrote: On Sat, Sep 06, 2014 at 08:15:44AM +0900, Kamezawa Hiroyuki wrote: As you noticed, hitting anon+swap limit just means oom-kill. My point

[PATCH v2] HID: rmi: check sanity of the incoming report

From: Benjamin Tissoires In the Dell XPS 13 9333, it appears that sometimes the bus get confused and corrupts the incoming data. It fills the input report with the sentinel value "ff". Synaptics told us that such behavior does not comes from the touchpad itself, so we filter out such reports

Re: [PATCH v4 08/12] Documentation: bindings: add doc for the USB2 ChipIdea USB driver

On Wed, Sep 03, 2014 at 09:48:27AM +0200, Antoine Tenart wrote: > Document the USB2 ChipIdea driver (ci13xxx) bindings. > > Signed-off-by: Antoine Tenart > --- > .../devicetree/bindings/usb/ci-hdrc-usb2.txt | 22 > ++ > 1 file changed, 22 insertions(+) > create mode

Re: [PATCH v4 9/9] usb: chipidea: add support to the generic PHY framework in ChipIdea

On Wed, Sep 03, 2014 at 09:40:40AM +0200, Antoine Tenart wrote: > This patch adds support of the PHY framework for ChipIdea drivers. > Changes are done in both the ChipIdea common code and in the drivers > accessing the PHY. This is done by adding a new PHY member in > ChipIdea's structures and by

RE: [Bug] 3.16 fwdownload failure on Marvell 88SE9125 sata controller

Got it. I just followed your step but it did not work. I will try something else to get 3.16 install on redhat. Thanks, Gaurav Patel Email: gspa...@hp.com Cell # 832-382-5550 -Original Message- From: Ming Lei [mailto:ming@canonical.com] Sent: Wednesday, September 10, 2014 8:00 PM

Re: [PATCH v4 07/12] usb: chipidea: add a usb2 driver for ci13xxx

On Wed, Sep 03, 2014 at 09:48:26AM +0200, Antoine Tenart wrote: > Add a USB2 ChipIdea driver for ci13xxx, with optional PHY, clock > and DMA mask, to support USB2 ChipIdea controllers that don't need > specific functions. > > Tested on the Marvell Berlin SoCs USB controllers. > > Signed-off-by:

Re: [PATCH] intel_pstate: track and export frequency residency stats via sysfs.

On Wed, Sep 10, 2014 at 5:04 PM, Rafael J. Wysocki wrote: > On Wednesday, September 10, 2014 04:39:05 PM Anup Chenthamarakshan wrote: >> On Thu, Sep 11, 2014 at 12:49:48AM +0200, Rafael J. Wysocki wrote: >> > On Wednesday, September 10, 2014 03:15:08 PM Anup Chenthamarakshan wrote: >> > > >> > >

Rusty away 18th September -- 11th October

Hi all, Probably won't read mail. Linus, I'll have pull requests early next week; if there's anything needed I'm sure Michael Tsirkin can handle it. Cheers, Rusty. PS. England and Italy for a holiday; my daughter chose them (somehow I forgot to inform her of the existence of Euro

Re: [PATCH v4 8/9] usb: chipidea: move usb_otg into struct ci_hdrc

On Wed, Sep 03, 2014 at 09:40:39AM +0200, Antoine Tenart wrote: > Move the usb_otg member from struct usb_phy to struct ci_hdrc. Rework > its initialization taking in account this modification. > > Signed-off-by: Antoine Tenart > --- > drivers/usb/chipidea/ci.h | 1 + >

Re: [Bug] 3.16 fwdownload failure on Marvell 88SE9125 sata controller

On Thu, Sep 11, 2014 at 8:45 AM, Patel, Gaurav wrote: > I will try to update kernel on Ubuntu to 2.6.32 and run the test. > > I was not able to install 3.16 ubuntu kernel on RrdHat. I didn't ask you to install 3.16 ubuntu kernel on Redhat, and you just need to install upstream 3.16 kernel, :-)

[PATCH 2/3] virtio_ring: assume sgs are always well-formed.

We used to have several callers which just used arrays. They're gone, so we can use sg_next() everywhere, simplifying the code. On my laptop, this slowed down vring_bench by 15%: vring_bench before: 936153354-967745359(9.44739e+08+/-6.1e+06)ns vring_bench after:

[PATCH 0/3] virtio_net/virtio_ring.

Mainly for DaveM and MST to ack the first one, so I can apply the second two. Initializing the entire sg table is naive, but with cache effects it only seems to help, so I didn't get fancy. Cheers, Rusty. Rusty Russell (3): virtio_net: pass well-formed sgs to virtqueue_add_*() virtio_ring:

[RFC PATCH v8] tpm_tis: verify interrupt during init

On Mon, 8 Sep 2014, Jason Gunthorpe wrote: > On Tue, Sep 02, 2014 at 08:22:58PM +, Scot Doyle wrote: > >> It's spending that time (now 3 seconds) in tpm_tis_send_data. > > Due to request_locality? The first command transmitted (TPM_CAP_PROP) in tpm_get_timeouts goes through tpm_tis_send

[PATCH 3/3] virtio_ring: unify direct/indirect code paths.

virtqueue_add() populates the virtqueue descriptor table from the sgs given. If it uses an indirect descriptor table, then it puts a single descriptor in the descriptor table pointing to the kmalloc'ed indirect table where the sg is populated. Previously vring_add_indirect() did the allocation

[PATCH 1/3] virtio_net: pass well-formed sgs to virtqueue_add_*()

This is the only driver which doesn't hand virtqueue_add_inbuf and virtqueue_add_outbuf a well-formed, well-terminated sg. Fix it, so we can make virtio_add_* simpler. pktgen results: modprobe pktgen echo 'add_device eth0' > /proc/net/pktgen/kpktgend_0 echo nowait 1 >

[RFC][PATCH] signal: replace !likely with unlikely!

From: Li RongQing !likely() is hard to be understood, and I do not know if compiler can optimise this condition, but unlikely(!()) is clear Signed-off-by: Li RongQing --- kernel/signal.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/signal.c b/kernel/signal.c

RE: [Bug] 3.16 fwdownload failure on Marvell 88SE9125 sata controller

I will try to update kernel on Ubuntu to 2.6.32 and run the test. I was not able to install 3.16 ubuntu kernel on RrdHat. Thanks, Gaurav Patel Email: gspa...@hp.com Cell # 832-382-5550 -Original Message- From: Ming Lei [mailto:ming@canonical.com] Sent: Wednesday, September 10, 2014

RE: [PATCH 1/4 v3] GPIO: gpio-dwapb: Enable platform driver binding to MFD driver

> > > > Hi Alvin, > > > > I did a quick test and this looks like it works for me (with device tree). > > I had a couple of small fixes below. > It is very appreciated to help testing. > > > > Alan > > > > > > > > - port->bgc.gc.ngpio = ngpio; > > > - port->bgc.gc.of_node = port_np; > > > +#ifdef

Re: [RFC] tty: Always allow tcflow(TCOON) to unwedge terminal

On 09/10/2014 08:24 PM, Greg Kroah-Hartman wrote: > On Wed, Sep 10, 2014 at 08:11:14PM -0400, Peter Hurley wrote: >> On 09/10/2014 08:03 PM, Greg Kroah-Hartman wrote: >>> On Wed, Sep 10, 2014 at 05:28:19PM -0400, Peter Hurley wrote: This patch changes user-space behavior (for the better) but

Re: [PATCH v4 7/9] usb: rename transceiver and phy to usb_phy in ChipIdea

On Wed, Sep 03, 2014 at 09:40:38AM +0200, Antoine Tenart wrote: > This patch prepares the introduction of the generic PHY support in the > USB ChipIdea common functions. The USB PHY member of the ChipIdea > structure ('transceiver') is renamed to 'usb_phy', the 'phy' member of > the ChipIdea pdata

RE: [PATCH 1/4 v3] GPIO: gpio-dwapb: Enable platform driver binding to MFD driver

> > Hi Alvin, > > I did a quick test and this looks like it works for me (with device tree). > I had a couple of small fixes below. It is very appreciated to help testing. > Alan > > > > > - port->bgc.gc.ngpio = ngpio; > > - port->bgc.gc.of_node = port_np; > > +#ifdef CONFIG_OF_GPIO > > +

Re: [RFC] tty: Always allow tcflow(TCOON) to unwedge terminal

On Wed, Sep 10, 2014 at 08:11:14PM -0400, Peter Hurley wrote: > On 09/10/2014 08:03 PM, Greg Kroah-Hartman wrote: > > On Wed, Sep 10, 2014 at 05:28:19PM -0400, Peter Hurley wrote: > >> This patch changes user-space behavior (for the better) but I'm not sure > >> that it's consequence-free. Also,

Здарово! Хочу по секрету с тобой кое чем поделиться , нашел тему в которой можно заработать несколько тысяч $, описание курса по заработку, пока в в сети

http://wecare2serve.com/money_order_locations.php

Re: [RFC] tty: Always allow tcflow(TCOON) to unwedge terminal

On 09/10/2014 08:03 PM, Greg Kroah-Hartman wrote: > On Wed, Sep 10, 2014 at 05:28:19PM -0400, Peter Hurley wrote: >> This patch changes user-space behavior (for the better) but I'm not sure >> that it's consequence-free. Also, it might not be enough to unwedge the >> terminal if the driver got its

Re: [PATCH v10 1/3] RTC: RK808: add RTC driver for RK808

Andrew, On Wed, Sep 10, 2014 at 3:08 PM, Andrew Morton wrote: > On Wed, 10 Sep 2014 14:37:13 -0700 Doug Anderson > wrote: > >> Andrew, >> >> On Wed, Sep 10, 2014 at 1:44 PM, Andrew Morton >> wrote: >> > On Wed, 10 Sep 2014 09:18:04 +0800 Chris Zhong wrote: >> > >> >> Adding RTC driver for

Re: [RFC] tty: Always allow tcflow(TCOON) to unwedge terminal

On Wed, Sep 10, 2014 at 05:28:19PM -0400, Peter Hurley wrote: > This patch changes user-space behavior (for the better) but I'm not sure > that it's consequence-free. Also, it might not be enough to unwedge the > terminal if the driver got its own flow control state mangled. > > Thoughts? > >

Re: [PATCH 0/3 v3] mmu_notifier: Allow to manage CPU external TLBs

On Wed, Sep 10, 2014 at 03:01:25PM -0700, Andrew Morton wrote: > On Tue, 9 Sep 2014 17:43:51 +0200 Joerg Roedel wrote: > > > here is a patch-set to extend the mmu_notifiers in the Linux > > kernel to allow managing CPU external TLBs. Those TLBs may > > be implemented in IOMMUs or any other

Re: [PATCH] blk-merge: fix blk_recount_segments

On Thu, Sep 11, 2014 at 7:38 AM, Rusty Russell wrote: > Rusty Russell writes: >> Rusty Russell writes: >> Here's what I have. It seems to work as expected, but I haven't >> benchmarked it. > > Hi Ming, > > Any chance you can run your benchmarks against this patch? I can run the

Re: [PATCH 8/8] blk-mq: support per-distpatch_queue flush machinery

On Thu, Sep 11, 2014 at 3:02 AM, Christoph Hellwig wrote: > On Wed, Sep 10, 2014 at 09:40:11AM +0800, Ming Lei wrote: >> I am wondering we can do that because lifetime is totally different >> between flush requests and tag_set requests which are initialized >> before request queue is created. > >

Re: bit fields && data tearing

On 09/10/2014 05:48 PM, James Bottomley wrote: > On Tue, 2014-09-09 at 06:40 -0400, Peter Hurley wrote: >> On 09/08/2014 10:56 PM, James Bottomley wrote: >>> On Mon, 2014-09-08 at 19:30 -0400, Peter Hurley wrote: On 09/08/2014 01:50 AM, James Bottomley wrote: >> But additionally, even if

  1   2   3   4   5   6   7   8   9   10   >