[RFC v4 1/6] sched/deadline: track the active utilization

From: Luca Abeni Active utilization is defined as the total utilization of active (TASK_RUNNING) tasks queued on a runqueue. Hence, it is increased when a task wakes up and is decreased when a task blocks. When a task is migrated from CPUi to CPUj, immediately subtract the task's utilization

[RFC v4 0/6] CPU reclaiming for SCHED_DEADLINE

From: Luca Abeni Hi all, here is a new version of the patchset implementing CPU reclaiming (using the GRUB algorithm[1]) for SCHED_DEADLINE. Basically, this feature allows SCHED_DEADLINE tasks to consume more than their reserved runtime, up to a maximum fraction of the CPU time (so that other

[RFC v4 5/6] sched/deadline: do not reclaim the whole CPU bandwidth

From: Luca Abeni Original GRUB tends to reclaim 100% of the CPU time... And this allows a CPU hog to starve non-deadline tasks. To address this issue, allow the scheduler to reclaim only a specified fraction of CPU time. Signed-off-by: Luca Abeni ---

[RFC v4 4/6] sched/deadline: implement GRUB accounting

From: Luca Abeni According to the GRUB (Greedy Reclaimation of Unused Bandwidth) reclaiming algorithm, the runtime is not decreased as "dq = -dt", but as "dq = -Uact dt" (where Uact is the per-runqueue active utilization). Hence, this commit modifies the runtime accounting

[RFC v4 5/6] sched/deadline: do not reclaim the whole CPU bandwidth

From: Luca Abeni Original GRUB tends to reclaim 100% of the CPU time... And this allows a CPU hog to starve non-deadline tasks. To address this issue, allow the scheduler to reclaim only a specified fraction of CPU time. Signed-off-by: Luca Abeni --- kernel/sched/core.c | 4

[RFC v4 4/6] sched/deadline: implement GRUB accounting

From: Luca Abeni According to the GRUB (Greedy Reclaimation of Unused Bandwidth) reclaiming algorithm, the runtime is not decreased as "dq = -dt", but as "dq = -Uact dt" (where Uact is the per-runqueue active utilization). Hence, this commit modifies the runtime accounting rule in

[RFC PATCH 3/3] mmc: sdhci: Add more debug info in case of data error

print error log message and dump sdhc registers for debugging purpose in case of data errors (except when tuning commands generate CRC/timeout/end bit errors). Signed-off-by: Ritesh Harjani --- drivers/mmc/host/sdhci.c | 21 +++-- 1 file changed, 19

[RFC PATCH 1/3] mmc: sdhci: Add platform_dumpregs callback support to sdhci_ops.

From: Sahitya Tummala Add new host operation ->platform_dumpregs to provide a mechanism through which host drivers can dump platform specific registers in addition to SDHC registers during error conditions. Signed-off-by: Sahitya Tummala

[RFC PATCH 3/3] mmc: sdhci: Add more debug info in case of data error

print error log message and dump sdhc registers for debugging purpose in case of data errors (except when tuning commands generate CRC/timeout/end bit errors). Signed-off-by: Ritesh Harjani --- drivers/mmc/host/sdhci.c | 21 +++-- 1 file changed, 19 insertions(+), 2 deletions(-)

[RFC PATCH 1/3] mmc: sdhci: Add platform_dumpregs callback support to sdhci_ops.

From: Sahitya Tummala Add new host operation ->platform_dumpregs to provide a mechanism through which host drivers can dump platform specific registers in addition to SDHC registers during error conditions. Signed-off-by: Sahitya Tummala Signed-off-by: Ritesh Harjani ---

[RFC PATCH 0/3] mmc: sdhci: sdhci-msm: Add more debug logs

Below is a small set of patches which provide useful info for debugging issues. Patch 1 :- This provide callback mechanism for platform drivers to dump their necessary register info at the time of sdhci_dumpregs. Patch 2 :- This implements this callback (->platform_dumpregs) for sdhci-msm.

dmaengine: dw-dmac: Custom cyclic API (Why?)

Hi All, I am going to work with dw-dmac AHB controller and I wanted to use SND_DMAENGINE_PCM. In order to use this, a standard DMA driver with cyclic support is needed. I found out that dw-dmac is capable of cyclic transfers but instead of using the DMA engine standard cyclic API it uses a

[RFC PATCH 0/3] mmc: sdhci: sdhci-msm: Add more debug logs

Below is a small set of patches which provide useful info for debugging issues. Patch 1 :- This provide callback mechanism for platform drivers to dump their necessary register info at the time of sdhci_dumpregs. Patch 2 :- This implements this callback (->platform_dumpregs) for sdhci-msm.

dmaengine: dw-dmac: Custom cyclic API (Why?)

Hi All, I am going to work with dw-dmac AHB controller and I wanted to use SND_DMAENGINE_PCM. In order to use this, a standard DMA driver with cyclic support is needed. I found out that dw-dmac is capable of cyclic transfers but instead of using the DMA engine standard cyclic API it uses a

[RFC PATCH 2/3] mmc: sdhci-msm: Implement platform_dumpregs callback in sdhci-msm

From: Sahitya Tummala Implement ->platform_dumpregs host operation to print the platform specific registers in addition to standard SDHC register during error conditions. Signed-off-by: Sahitya Tummala Signed-off-by: Ritesh Harjani

[RFC PATCH 2/3] mmc: sdhci-msm: Implement platform_dumpregs callback in sdhci-msm

From: Sahitya Tummala Implement ->platform_dumpregs host operation to print the platform specific registers in addition to standard SDHC register during error conditions. Signed-off-by: Sahitya Tummala Signed-off-by: Ritesh Harjani --- drivers/mmc/host/sdhci-msm.c | 34

Re: [PATCH 1/5] [media] ir-rx51: port to rc-core

Hi, On 20.12.2016 19:50, Sean Young wrote: This driver was written using lirc since rc-core did not support transmitter-only hardware at that time. Now that it does, port this driver. Compile tested only. I guess after that change, there will be no more /dev/lircN device, right? Neither

Re: [PATCH 1/5] [media] ir-rx51: port to rc-core

Hi, On 20.12.2016 19:50, Sean Young wrote: This driver was written using lirc since rc-core did not support transmitter-only hardware at that time. Now that it does, port this driver. Compile tested only. I guess after that change, there will be no more /dev/lircN device, right? Neither

[PATCH 5/5] Staging: comedi: proc: Warn if unable to create proc entry

The proc entry is not essential for the comedi system as evident by the support for !CONFIG_PROC_FS. So for failure to create, just warn and continue loading. Signed-off-by: Cheah Kok Cheong --- drivers/staging/comedi/proc.c | 3 ++- 1 file changed, 2 insertions(+), 1

[PATCH 5/5] Staging: comedi: proc: Warn if unable to create proc entry

The proc entry is not essential for the comedi system as evident by the support for !CONFIG_PROC_FS. So for failure to create, just warn and continue loading. Signed-off-by: Cheah Kok Cheong --- drivers/staging/comedi/proc.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH 3/5] Staging: comedi: proc: Add __init prefix

Add __init prefix so that symbol will be discarded after module loading. Signed-off-by: Cheah Kok Cheong --- drivers/staging/comedi/proc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/comedi/proc.c b/drivers/staging/comedi/proc.c index

[PATCH 3/5] Staging: comedi: proc: Add __init prefix

Add __init prefix so that symbol will be discarded after module loading. Signed-off-by: Cheah Kok Cheong --- drivers/staging/comedi/proc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/comedi/proc.c b/drivers/staging/comedi/proc.c index 3513f4c..6d13b51

[PATCH 4/5] Staging: comedi: proc: Add module owner

Since this is a loadable kernel module, add module ownership to follow LKM semantics. Signed-off-by: Cheah Kok Cheong --- drivers/staging/comedi/proc.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/comedi/proc.c b/drivers/staging/comedi/proc.c index

[PATCH 4/5] Staging: comedi: proc: Add module owner

Since this is a loadable kernel module, add module ownership to follow LKM semantics. Signed-off-by: Cheah Kok Cheong --- drivers/staging/comedi/proc.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/staging/comedi/proc.c b/drivers/staging/comedi/proc.c index 6d13b51..99b23b2e

[PATCH 1/5] Staging: comedi: comedi_fops: Avoid orphaned proc entry

Move comedi_proc_init to the end to avoid orphaned proc entry if module loading failed. Signed-off-by: Cheah Kok Cheong --- drivers/staging/comedi/comedi_fops.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/comedi/comedi_fops.c

[PATCH 1/5] Staging: comedi: comedi_fops: Avoid orphaned proc entry

Move comedi_proc_init to the end to avoid orphaned proc entry if module loading failed. Signed-off-by: Cheah Kok Cheong --- drivers/staging/comedi/comedi_fops.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/staging/comedi/comedi_fops.c

[PATCH 2/5] Staging: comedi: proc: Change file permission to read only

As there's no write operation, change to read only. Was inadvertantly switched to 0644 in commit 1f817b86d5e6 ("comedi: Don't use create_proc_read_entry()"). Signed-off-by: Cheah Kok Cheong --- drivers/staging/comedi/proc.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 2/5] Staging: comedi: proc: Change file permission to read only

As there's no write operation, change to read only. Was inadvertantly switched to 0644 in commit 1f817b86d5e6 ("comedi: Don't use create_proc_read_entry()"). Signed-off-by: Cheah Kok Cheong --- drivers/staging/comedi/proc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 0/5] Staging: comedi: Proc FS related cleanup

This series does trivial cleanup for COMEDI proc fs related stuff. Cheah Kok Cheong (5): Staging: comedi: comedi_fops: Avoid orphaned proc entry Staging: comedi: proc: Change file permission to read only Staging: comedi: proc: Add __init prefix Staging: comedi: proc: Add module owner

[PATCH 0/5] Staging: comedi: Proc FS related cleanup

This series does trivial cleanup for COMEDI proc fs related stuff. Cheah Kok Cheong (5): Staging: comedi: comedi_fops: Avoid orphaned proc entry Staging: comedi: proc: Change file permission to read only Staging: comedi: proc: Add __init prefix Staging: comedi: proc: Add module owner

Re: [Linux v4.10.0-rc1] call-traces after suspend-resume (pm? i915? cpu/hotplug?)

On Thu, Dec 29, 2016 at 12:58 PM, Mika Kuoppala wrote: > Sedat Dilek writes: > >> On Wed, Dec 28, 2016 at 11:32 PM, Rafael J. Wysocki >> wrote: >>> On Wed, Dec 28, 2016 at 11:00 AM, Sedat Dilek

Re: [Linux v4.10.0-rc1] call-traces after suspend-resume (pm? i915? cpu/hotplug?)

On Thu, Dec 29, 2016 at 12:58 PM, Mika Kuoppala wrote: > Sedat Dilek writes: > >> On Wed, Dec 28, 2016 at 11:32 PM, Rafael J. Wysocki >> wrote: >>> On Wed, Dec 28, 2016 at 11:00 AM, Sedat Dilek wrote: On Wed, Dec 28, 2016 at 9:29 AM, Jani Nikula wrote: > On Wed, 28 Dec 2016, Sedat

Re: Bug 4.9 and memorymanagement

On Tue 27-12-16 12:28:44, Michal Hocko wrote: > On Mon 26-12-16 12:00:53, Michal Hocko wrote: > > [CCing linux-mm] > > > > On Sun 25-12-16 21:52:52, Klaus Ethgen wrote: > > > Hello, > > > > > > The last days I compiled version 4.9 for my i386 laptop. (Lenovo x61s) > > > > Do you have memory

Re: Bug 4.9 and memorymanagement

On Tue 27-12-16 12:28:44, Michal Hocko wrote: > On Mon 26-12-16 12:00:53, Michal Hocko wrote: > > [CCing linux-mm] > > > > On Sun 25-12-16 21:52:52, Klaus Ethgen wrote: > > > Hello, > > > > > > The last days I compiled version 4.9 for my i386 laptop. (Lenovo x61s) > > > > Do you have memory

Re: [PATCH v1 08/54] block: comment on bio_alloc_pages()

On 2016/12/27 下午11:55, Ming Lei wrote: > This patch adds comment on usage of bio_alloc_pages(), > also comments on one special case of bch_data_verify(). > > Signed-off-by: Ming Lei > --- > block/bio.c | 4 +++- > drivers/md/bcache/debug.c | 6 ++ > 2

Re: [PATCH v1 08/54] block: comment on bio_alloc_pages()

On 2016/12/27 下午11:55, Ming Lei wrote: > This patch adds comment on usage of bio_alloc_pages(), > also comments on one special case of bch_data_verify(). > > Signed-off-by: Ming Lei > --- > block/bio.c | 4 +++- > drivers/md/bcache/debug.c | 6 ++ > 2 files changed, 9

Re: [RFC PATCH] mm, memcg: fix (Re: OOM: Better, but still there on)

On Fri 30-12-16 10:19:26, Mel Gorman wrote: > On Mon, Dec 26, 2016 at 01:48:40PM +0100, Michal Hocko wrote: > > On Fri 23-12-16 23:26:00, Nils Holland wrote: > > > On Fri, Dec 23, 2016 at 03:47:39PM +0100, Michal Hocko wrote: > > > > > > > > Nils, even though this is still highly experimental,

Re: [RFC PATCH] mm, memcg: fix (Re: OOM: Better, but still there on)

On Fri 30-12-16 10:19:26, Mel Gorman wrote: > On Mon, Dec 26, 2016 at 01:48:40PM +0100, Michal Hocko wrote: > > On Fri 23-12-16 23:26:00, Nils Holland wrote: > > > On Fri, Dec 23, 2016 at 03:47:39PM +0100, Michal Hocko wrote: > > > > > > > > Nils, even though this is still highly experimental,

Re: [PATCH v5 3/7] remoteproc: qcom: Add and initialize proxy and active regulators.

On 12/23/2016 3:16 AM, Bjorn Andersson wrote: On Thu 15 Dec 04:21 PST 2016, Avaneesh Kumar Dwivedi wrote: -static int q6v5_regulator_init(struct q6v5 *qproc) +static int q6v5_regulator_init(struct device *dev, struct reg_info *regs, + const struct

Re: [PATCH v5 3/7] remoteproc: qcom: Add and initialize proxy and active regulators.

On 12/23/2016 3:16 AM, Bjorn Andersson wrote: On Thu 15 Dec 04:21 PST 2016, Avaneesh Kumar Dwivedi wrote: -static int q6v5_regulator_init(struct q6v5 *qproc) +static int q6v5_regulator_init(struct device *dev, struct reg_info *regs, + const struct

Re: [PATCH v1 23/54] bcache: handle bio_clone() & bvec updating for multipage bvecs

On 2016/12/27 下午11:56, Ming Lei wrote: > The incoming bio may be too big to be cloned into > one singlepage bvecs bio, so split the bio and > check the splitted bio one by one. > > Signed-off-by: Ming Lei > --- > drivers/md/bcache/debug.c | 24 ++-- >

Re: [PATCH v1 23/54] bcache: handle bio_clone() & bvec updating for multipage bvecs

On 2016/12/27 下午11:56, Ming Lei wrote: > The incoming bio may be too big to be cloned into > one singlepage bvecs bio, so split the bio and > check the splitted bio one by one. > > Signed-off-by: Ming Lei > --- > drivers/md/bcache/debug.c | 24 ++-- > 1 file changed, 22

[PATCH v3] IB/umem: Release pid in error and ODP flow

There are two bugfixes in this patch: Fixes: 87773dd56d54 ("IB: ib_umem_release() should decrement mm->pinned_vm from ib_umem_get") This patch introduce the get_task_pid but not put it back on all error path Fixes: 8ada2c1c0c1d ("IB/core: Add support for on demand paging

[PATCH v3] IB/umem: Release pid in error and ODP flow

There are two bugfixes in this patch: Fixes: 87773dd56d54 ("IB: ib_umem_release() should decrement mm->pinned_vm from ib_umem_get") This patch introduce the get_task_pid but not put it back on all error path Fixes: 8ada2c1c0c1d ("IB/core: Add support for on demand paging

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

On Thu 29-12-16 23:22:20, Michal Nazarewicz wrote: > On Thu, Dec 29 2016, Eric Anholt wrote: > > Michal Hocko writes: > > > >> This has been already brought up > >> http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there > >> was a proposed patch for that which

Re: [PATCH] mm: Drop "PFNs busy" printk in an expected path.

On Thu 29-12-16 23:22:20, Michal Nazarewicz wrote: > On Thu, Dec 29 2016, Eric Anholt wrote: > > Michal Hocko writes: > > > >> This has been already brought up > >> http://lkml.kernel.org/r/20161130092239.gd18...@dhcp22.suse.cz and there > >> was a proposed patch for that which ratelimited the

Re: [PATCH v5 2/7] remoteproc: qcom: Add and initialize proxy and active clocks.

On 12/23/2016 3:12 AM, Bjorn Andersson wrote: On Thu 15 Dec 04:21 PST 2016, Avaneesh Kumar Dwivedi wrote: Certain regulators and clocks need voting by rproc on behalf of hexagon only during restart operation but certain clocks and voltage need to be voted till hexagon is up, these regulators

Re: [PATCH v5 2/7] remoteproc: qcom: Add and initialize proxy and active clocks.

On 12/23/2016 3:12 AM, Bjorn Andersson wrote: On Thu 15 Dec 04:21 PST 2016, Avaneesh Kumar Dwivedi wrote: Certain regulators and clocks need voting by rproc on behalf of hexagon only during restart operation but certain clocks and voltage need to be voted till hexagon is up, these regulators

Re: [PATCH v5 09/14] ACPI: platform: setup MSI domain for ACPI based platform device

On 2016/12/29 22:44, Sinan Kaya wrote: > On 12/25/2016 8:31 PM, Hanjun Guo wrote: >>> A type->setup() would be somewhat cleaner I think, but then it's more >>> code. Whichever works better I guess. :-) >> Agree, I will demo the type->setup() way and send out the patch for review, >> also I find

Re: [PATCH v5 09/14] ACPI: platform: setup MSI domain for ACPI based platform device

On 2016/12/29 22:44, Sinan Kaya wrote: > On 12/25/2016 8:31 PM, Hanjun Guo wrote: >>> A type->setup() would be somewhat cleaner I think, but then it's more >>> code. Whichever works better I guess. :-) >> Agree, I will demo the type->setup() way and send out the patch for review, >> also I find

Re: [PATCH v1 08/54] block: comment on bio_alloc_pages()

On 2016/12/27 下午11:55, Ming Lei wrote: > This patch adds comment on usage of bio_alloc_pages(), > also comments on one special case of bch_data_verify(). > > Signed-off-by: Ming Lei > --- > block/bio.c | 4 +++- > drivers/md/bcache/debug.c | 6 ++ > 2

Re: [PATCH v1 08/54] block: comment on bio_alloc_pages()

On 2016/12/27 下午11:55, Ming Lei wrote: > This patch adds comment on usage of bio_alloc_pages(), > also comments on one special case of bch_data_verify(). > > Signed-off-by: Ming Lei > --- > block/bio.c | 4 +++- > drivers/md/bcache/debug.c | 6 ++ > 2 files changed, 9

Re: [RFC PATCH] mm, memcg: fix (Re: OOM: Better, but still there on)

On Fri 30-12-16 11:05:22, Minchan Kim wrote: > On Thu, Dec 29, 2016 at 10:04:32AM +0100, Michal Hocko wrote: > > On Thu 29-12-16 10:20:26, Minchan Kim wrote: > > > On Tue, Dec 27, 2016 at 04:55:33PM +0100, Michal Hocko wrote: [...] > > > > + * given zone_idx > > > > + */ > > > > +static unsigned

Re: [RFC PATCH] mm, memcg: fix (Re: OOM: Better, but still there on)

On Fri 30-12-16 11:05:22, Minchan Kim wrote: > On Thu, Dec 29, 2016 at 10:04:32AM +0100, Michal Hocko wrote: > > On Thu 29-12-16 10:20:26, Minchan Kim wrote: > > > On Tue, Dec 27, 2016 at 04:55:33PM +0100, Michal Hocko wrote: [...] > > > > + * given zone_idx > > > > + */ > > > > +static unsigned

Re: [PATCH v2 5/8] PM / devfreq: Fix the checkpatch warnings

On Wed, Dec 28, 2016 at 8:56 PM, Chanwoo Choi wrote: > This patch just fixes the checkpatch warnings. > > Signed-off-by: Chanwoo Choi > --- > drivers/devfreq/devfreq.c | 13 +++-- > 1 file changed, 7 insertions(+), 6 deletions(-) > > diff

Re: [PATCH v2 5/8] PM / devfreq: Fix the checkpatch warnings

On Wed, Dec 28, 2016 at 8:56 PM, Chanwoo Choi wrote: > This patch just fixes the checkpatch warnings. > > Signed-off-by: Chanwoo Choi > --- > drivers/devfreq/devfreq.c | 13 +++-- > 1 file changed, 7 insertions(+), 6 deletions(-) > > diff --git a/drivers/devfreq/devfreq.c

Re: [PATCH v2 4/8] PM / devfreq: exynos-ppmu: Show the registred device for ppmu device

On Wed, Dec 28, 2016 at 8:56 PM, Chanwoo Choi wrote: > This patch just adds the simple log to show the PPMU device's registration > during the kernel booting. > > Cc: Kukjin Kim > Cc: Krzysztof Kozlowski > Cc: Javier Martinez Canillas

Re: [PATCH v2 4/8] PM / devfreq: exynos-ppmu: Show the registred device for ppmu device

On Wed, Dec 28, 2016 at 8:56 PM, Chanwoo Choi wrote: > This patch just adds the simple log to show the PPMU device's registration > during the kernel booting. > > Cc: Kukjin Kim > Cc: Krzysztof Kozlowski > Cc: Javier Martinez Canillas > Cc: linux-samsung-...@vger.kernel.org > Signed-off-by:

Re: [PATCH v2 3/8] PM / devfreq: exynos-bus: Print the real clock rate of bus

On Wed, Dec 28, 2016 at 8:56 PM, Chanwoo Choi wrote: > This patch shows the real clock rate after calling clk_set_rate() > to debug it. > > Cc: Kukjin Kim > Cc: Krzysztof Kozlowski > Cc: Javier Martinez Canillas

Re: [PATCH v2 3/8] PM / devfreq: exynos-bus: Print the real clock rate of bus

On Wed, Dec 28, 2016 at 8:56 PM, Chanwoo Choi wrote: > This patch shows the real clock rate after calling clk_set_rate() > to debug it. > > Cc: Kukjin Kim > Cc: Krzysztof Kozlowski > Cc: Javier Martinez Canillas > Cc: linux-samsung-...@vger.kernel.org > Signed-off-by: Chanwoo Choi Acked-by:

Re: [RFC PATCH v2] crypto: Add IV generation algorithms

On Thu, Dec 29, 2016 at 02:53:25PM +0530, Binoy Jayan wrote: > > When we keep these in dm-crypt and if more than one key is used > (it is actually more than one parts of the original key), > there are more than one cipher instance created - one for each > unique part of the key. Since the crypto

Re: [RFC PATCH v2] crypto: Add IV generation algorithms

On Thu, Dec 29, 2016 at 02:53:25PM +0530, Binoy Jayan wrote: > > When we keep these in dm-crypt and if more than one key is used > (it is actually more than one parts of the original key), > there are more than one cipher instance created - one for each > unique part of the key. Since the crypto

Re: [PATCH v2 2/8] PM / devfreq: exynos-ppmu: Use the regmap interface to handle the registers

On Wed, Dec 28, 2016 at 8:56 PM, Chanwoo Choi wrote: > This patch uses the regmap interface to read and write the registers for > exynos > PPMU device instead of the legacy memory map functions. > > Cc: Kukjin Kim > Cc: Krzysztof Kozlowski

Re: [PATCH v2 2/8] PM / devfreq: exynos-ppmu: Use the regmap interface to handle the registers

On Wed, Dec 28, 2016 at 8:56 PM, Chanwoo Choi wrote: > This patch uses the regmap interface to read and write the registers for > exynos > PPMU device instead of the legacy memory map functions. > > Cc: Kukjin Kim > Cc: Krzysztof Kozlowski > Cc: Javier Martinez Canillas > Cc:

Re: [PATCH 0/7] vm, vmscan: enahance vmscan tracepoints

On Fri, Dec 30, 2016 at 10:36:55AM +0100, Michal Hocko wrote: > On Fri 30-12-16 09:11:17, Mel Gorman wrote: > > On Wed, Dec 28, 2016 at 04:30:25PM +0100, Michal Hocko wrote: > > > Hi, > > > while debugging [1] I've realized that there is some room for > > > improvements in the tracepoints set we

Re: [PATCH 0/7] vm, vmscan: enahance vmscan tracepoints

On Fri, Dec 30, 2016 at 10:36:55AM +0100, Michal Hocko wrote: > On Fri 30-12-16 09:11:17, Mel Gorman wrote: > > On Wed, Dec 28, 2016 at 04:30:25PM +0100, Michal Hocko wrote: > > > Hi, > > > while debugging [1] I've realized that there is some room for > > > improvements in the tracepoints set we

Crypto Fixes for 4.10

Hi Linus: This push fixes a boot failure on some platforms when crypto self test is enabled along with the new acomp interface. Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus Laura Abbott (1): crypto: testmgr - Use heap buffer for acomp test

Crypto Fixes for 4.10

Hi Linus: This push fixes a boot failure on some platforms when crypto self test is enabled along with the new acomp interface. Please pull from git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus Laura Abbott (1): crypto: testmgr - Use heap buffer for acomp test

Re: [RFC PATCH] mm, memcg: fix (Re: OOM: Better, but still there on)

On Mon, Dec 26, 2016 at 01:48:40PM +0100, Michal Hocko wrote: > On Fri 23-12-16 23:26:00, Nils Holland wrote: > > On Fri, Dec 23, 2016 at 03:47:39PM +0100, Michal Hocko wrote: > > > > > > Nils, even though this is still highly experimental, could you give it a > > > try please? > > > > Yes, no

Re: [RFC PATCH] mm, memcg: fix (Re: OOM: Better, but still there on)

On Mon, Dec 26, 2016 at 01:48:40PM +0100, Michal Hocko wrote: > On Fri 23-12-16 23:26:00, Nils Holland wrote: > > On Fri, Dec 23, 2016 at 03:47:39PM +0100, Michal Hocko wrote: > > > > > > Nils, even though this is still highly experimental, could you give it a > > > try please? > > > > Yes, no

Re: [PATCH v5 6/7] remoteproc: qcom: Implement Hexagon core specific changes.

On 12/23/2016 6:34 AM, Bjorn Andersson wrote: On Thu 15 Dec 04:21 PST 2016, Avaneesh Kumar Dwivedi wrote: +/* QDSP6v56 parameters */ +#define QDSP6v56_LDO_BYPBIT(25) +#define QDSP6v56_BHS_ON BIT(24) +#define QDSP6v56_CLAMP_WL BIT(21) +#define

Re: [PATCH v5 6/7] remoteproc: qcom: Implement Hexagon core specific changes.

On 12/23/2016 6:34 AM, Bjorn Andersson wrote: On Thu 15 Dec 04:21 PST 2016, Avaneesh Kumar Dwivedi wrote: +/* QDSP6v56 parameters */ +#define QDSP6v56_LDO_BYPBIT(25) +#define QDSP6v56_BHS_ON BIT(24) +#define QDSP6v56_CLAMP_WL BIT(21) +#define

Re: [PATCH 1/2] arm64: dma_mapping: allow PCI host driver to limit DMA mask

On 12/30/2016 12:46 PM, Sergei Shtylyov wrote: It is possible that PCI device supports 64-bit DMA addressing, and thus it's driver sets device's dma_mask to DMA_BIT_MASK(64), however PCI host Its. bridge has limitations on inbound transactions addressing. Example of such setup is NVME

Re: [PATCH 1/2] arm64: dma_mapping: allow PCI host driver to limit DMA mask

On 12/30/2016 12:46 PM, Sergei Shtylyov wrote: It is possible that PCI device supports 64-bit DMA addressing, and thus it's driver sets device's dma_mask to DMA_BIT_MASK(64), however PCI host Its. bridge has limitations on inbound transactions addressing. Example of such setup is NVME

Re: [PATCH v2] ib umem: bugfix: mixed put_pid()s in ib_umem_get()

On Fri, Dec 30, 2016 at 08:55:10AM +0200, Leon Romanovsky wrote: > Date: Fri, 30 Dec 2016 08:55:10 +0200 > From: Leon Romanovsky > To: Kenneth Lee > CC: dledf...@redhat.com, sean.he...@intel.com, hal.rosenst...@gmail.com, > robin.mur...@arm.com,

Re: [PATCH v2] ib umem: bugfix: mixed put_pid()s in ib_umem_get()

On Fri, Dec 30, 2016 at 08:55:10AM +0200, Leon Romanovsky wrote: > Date: Fri, 30 Dec 2016 08:55:10 +0200 > From: Leon Romanovsky > To: Kenneth Lee > CC: dledf...@redhat.com, sean.he...@intel.com, hal.rosenst...@gmail.com, > robin.mur...@arm.com, jroe...@suse.de, egtv...@samfundet.no, >

[PATCH v2 1/3] PCI: dra7xx: simplify the probe code

No functional change. Use the new devm_gpiod_get_optional() to simplify the probe code. Signed-off-by: Kishon Vijay Abraham I Signed-off-by: Sekhar Nori --- drivers/pci/controller/pci-dra7xx.c | 21 + 1 file changed, 5 insertions(+), 16

[PATCH v2 2/3] PCI: dra7xx: Add support to force RC to work in GEN1 mode

PCIe in AM57x/DRA7x devices is by default configured to work in GEN2 mode. However there may be situations when working in GEN1 mode is desired. One example is limitation i925 (PCIe GEN2 mode not supported at junction temperatures < 0C). Add support to force Root Complex to work in GEN1 mode if

[PATCH v2 3/3] PCI: dra7xx: Enable MSI and legacy interrupts simultaneously

dra7xx driver had a bug in that if CONFIG_PCI_MSI config is enabled, it doesn't support legacy interrupt. Fix it here so that both MSI and legacy interrupts can be enabled simultaneously and one of them will be used based on the connected device. Signed-off-by: Kishon Vijay Abraham I

[PATCH v2 0/3] PCI: designware/dra7xx: misc fixes and cleanups

This series contains *) a patch to cleanup dra7xx probe *) a patch to force DRA7xx controller to work in GEN1 mode *) a patch to fix dra7xx driver so that even if CONFIG_PCI_MSI is enabled, dra7xx driver can service legacy interrupts (provided the

[PATCH v2 1/3] PCI: dra7xx: simplify the probe code

No functional change. Use the new devm_gpiod_get_optional() to simplify the probe code. Signed-off-by: Kishon Vijay Abraham I Signed-off-by: Sekhar Nori --- drivers/pci/controller/pci-dra7xx.c | 21 + 1 file changed, 5 insertions(+), 16 deletions(-) diff --git

[PATCH v2 2/3] PCI: dra7xx: Add support to force RC to work in GEN1 mode

PCIe in AM57x/DRA7x devices is by default configured to work in GEN2 mode. However there may be situations when working in GEN1 mode is desired. One example is limitation i925 (PCIe GEN2 mode not supported at junction temperatures < 0C). Add support to force Root Complex to work in GEN1 mode if

[PATCH v2 3/3] PCI: dra7xx: Enable MSI and legacy interrupts simultaneously

dra7xx driver had a bug in that if CONFIG_PCI_MSI config is enabled, it doesn't support legacy interrupt. Fix it here so that both MSI and legacy interrupts can be enabled simultaneously and one of them will be used based on the connected device. Signed-off-by: Kishon Vijay Abraham I ---

[PATCH v2 0/3] PCI: designware/dra7xx: misc fixes and cleanups

This series contains *) a patch to cleanup dra7xx probe *) a patch to force DRA7xx controller to work in GEN1 mode *) a patch to fix dra7xx driver so that even if CONFIG_PCI_MSI is enabled, dra7xx driver can service legacy interrupts (provided the

Re: [PATCH v5 06/14] irqchip: gicv3-its: platform-msi: refactor its_pmsi_init() to prepare for ACPI

On 2016/12/22 13:35, Hanjun Guo wrote: From: Hanjun Guo Introduce its_pmsi_init_one() to refactor the code to isolate ACPI common code to prepare for ACPI later. Signed-off-by: Hanjun Guo Tested-by: Sinan Kaya Cc: Marc

Re: [PATCH v5 06/14] irqchip: gicv3-its: platform-msi: refactor its_pmsi_init() to prepare for ACPI

On 2016/12/22 13:35, Hanjun Guo wrote: From: Hanjun Guo Introduce its_pmsi_init_one() to refactor the code to isolate ACPI common code to prepare for ACPI later. Signed-off-by: Hanjun Guo Tested-by: Sinan Kaya Cc: Marc Zyngier Cc: Tomasz Nowicki Cc: Thomas Gleixner ---

Re: [PATCH v5 11/14] msi: platform: make platform_msi_create_device_domain() ACPI aware

On 2016/12/22 13:35, Hanjun Guo wrote: From: Hanjun Guo With the platform msi domain created for ITS, irqchip such as mbi-gen connecting ITS, which needs ctreate its own irqdomain. Fortunately with the platform msi support upstreamed by Marc, we just need to add minor

Re: [PATCH v5 11/14] msi: platform: make platform_msi_create_device_domain() ACPI aware

On 2016/12/22 13:35, Hanjun Guo wrote: From: Hanjun Guo With the platform msi domain created for ITS, irqchip such as mbi-gen connecting ITS, which needs ctreate its own irqdomain. Fortunately with the platform msi support upstreamed by Marc, we just need to add minor code to make it run

Re: [PATCH v5 09/14] ACPI: platform: setup MSI domain for ACPI based platform device

On 2016/12/22 13:35, Hanjun Guo wrote: From: Hanjun Guo With the platform msi domain created, we can set up the msi domain for a platform device when it's probed. In order to do that, we need to get the domain that the platform device connecting to, so the

Re: [PATCH v5 09/14] ACPI: platform: setup MSI domain for ACPI based platform device

On 2016/12/22 13:35, Hanjun Guo wrote: From: Hanjun Guo With the platform msi domain created, we can set up the msi domain for a platform device when it's probed. In order to do that, we need to get the domain that the platform device connecting to, so the iort_get_platform_device_domain() is

Re: [PATCH v5 13/14] irqchip: mbigen: introduce mbigen_of_create_domain()

On 2016/12/22 13:35, Hanjun Guo wrote: From: Kefeng Wang Introduce mbigen_of_create_domain() to consolidate OF related code and prepare for ACPI later, no funtional change. Signed-off-by: Kefeng Wang Signed-off-by: Hanjun Guo

Re: [PATCH v5 13/14] irqchip: mbigen: introduce mbigen_of_create_domain()

On 2016/12/22 13:35, Hanjun Guo wrote: From: Kefeng Wang Introduce mbigen_of_create_domain() to consolidate OF related code and prepare for ACPI later, no funtional change. Signed-off-by: Kefeng Wang Signed-off-by: Hanjun Guo Cc: Marc Zyngier Cc: Thomas Gleixner Cc: Ma Jun ---

Re: [PATCH 1/2] arm64: dma_mapping: allow PCI host driver to limit DMA mask

Hello! On 12/29/2016 11:45 PM, Nikita Yushchenko wrote: It is possible that PCI device supports 64-bit DMA addressing, and thus it's driver sets device's dma_mask to DMA_BIT_MASK(64), however PCI host Its. bridge has limitations on inbound transactions addressing. Example of such setup

Re: [PATCH 1/2] arm64: dma_mapping: allow PCI host driver to limit DMA mask

Hello! On 12/29/2016 11:45 PM, Nikita Yushchenko wrote: It is possible that PCI device supports 64-bit DMA addressing, and thus it's driver sets device's dma_mask to DMA_BIT_MASK(64), however PCI host Its. bridge has limitations on inbound transactions addressing. Example of such setup

Re: [BUG] ARM64: amlogic: gxbb: unhandled level 2 translation fault (11)

On 12/30/2016 09:51 AM, Neil Armstrong wrote: > On 12/29/2016 10:18 PM, Heinrich Schuchardt wrote: >> On 12/29/2016 10:07 AM, Neil Armstrong wrote: >>> On 12/24/2016 03:00 PM, Heinrich Schuchardt wrote: When trying to run sddm on an Hardkernel Odroid C2 I invariably run into the

Re: [BUG] ARM64: amlogic: gxbb: unhandled level 2 translation fault (11)

On 12/30/2016 09:51 AM, Neil Armstrong wrote: > On 12/29/2016 10:18 PM, Heinrich Schuchardt wrote: >> On 12/29/2016 10:07 AM, Neil Armstrong wrote: >>> On 12/24/2016 03:00 PM, Heinrich Schuchardt wrote: When trying to run sddm on an Hardkernel Odroid C2 I invariably run into the

Re: [PATCH 2/7] mm, vmscan: add active list aging tracepoint

On Friday, December 30, 2016 5:27 PM Michal Hocko wrote: > Anyway, what do you think about this updated patch? I have kept Hillf's > A-b so please let me know if it is no longer valid. > My mind is not changed:) Happy new year folks! Hillf

Re: [PATCH 2/7] mm, vmscan: add active list aging tracepoint

On Friday, December 30, 2016 5:27 PM Michal Hocko wrote: > Anyway, what do you think about this updated patch? I have kept Hillf's > A-b so please let me know if it is no longer valid. > My mind is not changed:) Happy new year folks! Hillf

Re: [PATCH] mm: cma: print allocation failure reason and bitmap status

On Fri 30-12-16 16:24:46, Jaewon Kim wrote: [...] > >From 7577cc94da3af27907aa6eec590d2ef51e4b9d80 Mon Sep 17 00:00:00 2001 > From: Jaewon Kim > Date: Thu, 29 Dec 2016 11:00:16 +0900 > Subject: [PATCH] mm: cma: print allocation failure reason and bitmap status > > There

Re: [PATCH] mm: cma: print allocation failure reason and bitmap status

On Fri 30-12-16 16:24:46, Jaewon Kim wrote: [...] > >From 7577cc94da3af27907aa6eec590d2ef51e4b9d80 Mon Sep 17 00:00:00 2001 > From: Jaewon Kim > Date: Thu, 29 Dec 2016 11:00:16 +0900 > Subject: [PATCH] mm: cma: print allocation failure reason and bitmap status > > There are many reasons of CMA

<    1   2   3   4   5   6   7   >