Re: [RFC PATCH 2/7] ALSA: ac97: add an ac97 bus

On Sun, 15 May 2016 23:29:27 +0200, Robert Jarzmik wrote: > > Takashi Iwai writes: > > > On Sat, 14 May 2016 11:50:50 +0200, > > Robert Jarzmik wrote: > >> >> +unsigned int ac97_bus_scan_one(struct ac97_controller *ac97, > >> >> + int

Re: [RFC PATCH 2/7] ALSA: ac97: add an ac97 bus

On Sun, 15 May 2016 23:29:27 +0200, Robert Jarzmik wrote: > > Takashi Iwai writes: > > > On Sat, 14 May 2016 11:50:50 +0200, > > Robert Jarzmik wrote: > >> >> +unsigned int ac97_bus_scan_one(struct ac97_controller *ac97, > >> >> + int codec_num) > >> >> +{ >

Re: [PATCH] ixgbe: take online CPU number as MQ max limit when alloc_etherdev_mq()

Thanks for your reviewing. Ethan On 2016/5/13 20:52, Sergei Shtylyov wrote: Hello. On 5/13/2016 8:56 AM, Ethan Zhao wrote: Allocating 64 Tx/Rx as default doesn't benefit perfomrnace when less Performance. CPUs were assigned. especially when DCB is enabled, so we should take

Re: [PATCH] ixgbe: take online CPU number as MQ max limit when alloc_etherdev_mq()

Thanks for your reviewing. Ethan On 2016/5/13 20:52, Sergei Shtylyov wrote: Hello. On 5/13/2016 8:56 AM, Ethan Zhao wrote: Allocating 64 Tx/Rx as default doesn't benefit perfomrnace when less Performance. CPUs were assigned. especially when DCB is enabled, so we should take

RE: [PATCH 2/2] serial: 8250_mid: Read RX buffer on RX DMA timeout for DNV

>-Original Message- >From: Andy Shevchenko [mailto:andriy.shevche...@linux.intel.com] >Sent: Friday, May 13, 2016 7:28 PM >To: lkp ; Chuah, Kim Tatt ; Peter >Hurley >Cc: kbuild-...@01.org; gre...@linuxfoundation.org;

RE: [PATCH 2/2] serial: 8250_mid: Read RX buffer on RX DMA timeout for DNV

>-Original Message- >From: Andy Shevchenko [mailto:andriy.shevche...@linux.intel.com] >Sent: Friday, May 13, 2016 7:28 PM >To: lkp ; Chuah, Kim Tatt ; Peter >Hurley >Cc: kbuild-...@01.org; gre...@linuxfoundation.org; Koul, Vinod >; heikki.kroge...@linux.intel.com;

[PATCH] ARM: DRA7: hwmod: Remove QSPI address space entry from hwmod

QSPI address space information is passed from device tree. Therefore remove legacy way of passing address space via hwmod data. Signed-off-by: Vignesh R --- arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 10 -- 1 file changed, 10 deletions(-) diff --git

[PATCH] ARM: DRA7: hwmod: Remove QSPI address space entry from hwmod

QSPI address space information is passed from device tree. Therefore remove legacy way of passing address space via hwmod data. Signed-off-by: Vignesh R --- arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 10 -- 1 file changed, 10 deletions(-) diff --git

RE: [PATCH V2 1/2] drivers: i2c: qup: Fix broken dma when CONFIG_DEBUG_SG is enabled

Hi, > > With CONFIG_DEBUG_SG is enabled and when dma mode is used, below > dump > > is seen, > > > > [ cut here ] > > kernel BUG at include/linux/scatterlist.h:140! > > Internal error: Oops - BUG: 0 [#1] PREEMPT SMP Modules linked in: > > CPU: 0 PID: 1 Comm: swapper/0 Not

RE: [PATCH V2 1/2] drivers: i2c: qup: Fix broken dma when CONFIG_DEBUG_SG is enabled

Hi, > > With CONFIG_DEBUG_SG is enabled and when dma mode is used, below > dump > > is seen, > > > > [ cut here ] > > kernel BUG at include/linux/scatterlist.h:140! > > Internal error: Oops - BUG: 0 [#1] PREEMPT SMP Modules linked in: > > CPU: 0 PID: 1 Comm: swapper/0 Not

RE: [PATCH V2 0/2] drivers: i2c: qup: Some misc fixes

Hi, > > One for fixing the bug with CONFIG_DEBUG_SG enabled and another to > > suspend the transfer for all errors instead of just for nack. > > You haven't stated what was changed in V2. ah, sorry, will resend.. Regards, Sricharan

RE: [PATCH V2 0/2] drivers: i2c: qup: Some misc fixes

Hi, > > One for fixing the bug with CONFIG_DEBUG_SG enabled and another to > > suspend the transfer for all errors instead of just for nack. > > You haven't stated what was changed in V2. ah, sorry, will resend.. Regards, Sricharan

[PATCH] gpu:drm:radeon:fix array out fo bouds

From: tom will When the initial value of i is greater than zero, it may cause endless loop, resulting in array out of bouds, fix it. Signed-off-by: tom will --- drivers/gpu/drm/radeon/kv_dpm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH] gpu:drm:radeon:fix array out fo bouds

From: tom will When the initial value of i is greater than zero, it may cause endless loop, resulting in array out of bouds, fix it. Signed-off-by: tom will --- drivers/gpu/drm/radeon/kv_dpm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/radeon/kv_dpm.c

Re: [Patch v5 5/8] firmware: qcom: scm: Convert to streaming DMA APIS

On Fri, May 13, 2016 at 04:48:52PM -0700, Bjorn Andersson wrote: > > + cmd->len = cpu_to_le32(alloc_len); > > + cmd->buf_offset = cpu_to_le32(sizeof(*cmd)); > > + cmd->resp_hdr_offset = cpu_to_le32(sizeof(*cmd) + cmd_len); > > + > > cmd->id = cpu_to_le32((svc_id << 10) | cmd_id); > >

Re: [Patch v5 5/8] firmware: qcom: scm: Convert to streaming DMA APIS

On Fri, May 13, 2016 at 04:48:52PM -0700, Bjorn Andersson wrote: > > + cmd->len = cpu_to_le32(alloc_len); > > + cmd->buf_offset = cpu_to_le32(sizeof(*cmd)); > > + cmd->resp_hdr_offset = cpu_to_le32(sizeof(*cmd) + cmd_len); > > + > > cmd->id = cpu_to_le32((svc_id << 10) | cmd_id); > >

Re: linux-next: Tree for May 16

Hi all, I forgot to say: Please do not add any v4.8 destined material to your linux-next included branches until after v4.7-rc1 has been released. -- Cheers, Stephen Rothwell

Re: linux-next: Tree for May 16

Hi all, I forgot to say: Please do not add any v4.8 destined material to your linux-next included branches until after v4.7-rc1 has been released. -- Cheers, Stephen Rothwell

linux-next: Tree for May 16

Hi all, Changes since 20160513: Undropped tree: rdma-leon The wireless-drivers-next tree gained a conflict aaginst the net-next tree. The rdma-leon tree lost its build failure. The spi tree gained a build failure so I used the version from next-20160513. The clk tree gained a conflict

linux-next: Tree for May 16

Hi all, Changes since 20160513: Undropped tree: rdma-leon The wireless-drivers-next tree gained a conflict aaginst the net-next tree. The rdma-leon tree lost its build failure. The spi tree gained a build failure so I used the version from next-20160513. The clk tree gained a conflict

Re: [PATCH 0/5] cpufreq: governor: Rework API to use callbacks instead of events

On 14-05-16, 00:58, Rafael J. Wysocki wrote: > Hi, > > This series is on top of the current linux-next witn the following two patches > applied: > > https://patchwork.kernel.org/patch/9080801/ > https://patchwork.kernel.org/patch/9080791/ > > It cleans up a few things and then reworks the

Re: [PATCH 0/5] cpufreq: governor: Rework API to use callbacks instead of events

On 14-05-16, 00:58, Rafael J. Wysocki wrote: > Hi, > > This series is on top of the current linux-next witn the following two patches > applied: > > https://patchwork.kernel.org/patch/9080801/ > https://patchwork.kernel.org/patch/9080791/ > > It cleans up a few things and then reworks the

Re: [PATCH 5/5] cpufreq: governor: Get rid of governor events

On 14-05-16, 01:02, Rafael J. Wysocki wrote: > --- linux-pm.orig/drivers/cpufreq/cpufreq_governor.c > -int cpufreq_governor_dbs(struct cpufreq_policy *policy, unsigned int event) > -{ > - if (event == CPUFREQ_GOV_POLICY_INIT) { > - return cpufreq_governor_init(policy); > - }

Re: [PATCH 5/5] cpufreq: governor: Get rid of governor events

On 14-05-16, 01:02, Rafael J. Wysocki wrote: > --- linux-pm.orig/drivers/cpufreq/cpufreq_governor.c > -int cpufreq_governor_dbs(struct cpufreq_policy *policy, unsigned int event) > -{ > - if (event == CPUFREQ_GOV_POLICY_INIT) { > - return cpufreq_governor_init(policy); > - }

[PATCH] perf script: Fix display inconsitency when call-graph config is used

There's a display inconsistency when 'call-graph' config event appears in different position. The problem can be reproduced like this: We record signal_deliver with call-graph and signal_generate without it. $ perf record -g -a -e signal:signal_deliver -e signal:signal_generate/call-graph=no/

[PATCH] perf script: Fix display inconsitency when call-graph config is used

There's a display inconsistency when 'call-graph' config event appears in different position. The problem can be reproduced like this: We record signal_deliver with call-graph and signal_generate without it. $ perf record -g -a -e signal:signal_deliver -e signal:signal_generate/call-graph=no/

Re: [rcu_sched stall] regression/miss-config ?

On 5/15/16 2:18 PM, Santosh Shilimkar wrote: Hi Paul, I was asking Sasha about [1] since other folks in Oracle also stumbled upon similar RCU stalls with v4.1 kernel in different workloads. I was reported similar issue with RDS as well and looking at [1], [2], [3] and [4], thought of reaching

Re: [rcu_sched stall] regression/miss-config ?

On 5/15/16 2:18 PM, Santosh Shilimkar wrote: Hi Paul, I was asking Sasha about [1] since other folks in Oracle also stumbled upon similar RCU stalls with v4.1 kernel in different workloads. I was reported similar issue with RDS as well and looking at [1], [2], [3] and [4], thought of reaching

Re: [PATCH net-next] tuntap: introduce tx skb ring

On Mon, May 16, 2016 at 09:17:01AM +0800, Jason Wang wrote: > We used to queue tx packets in sk_receive_queue, this is less > efficient since it requires spinlocks to synchronize between producer > and consumer. > > This patch tries to address this by using circular buffer which allows > lockless

Re: [PATCH net-next] tuntap: introduce tx skb ring

On Mon, May 16, 2016 at 09:17:01AM +0800, Jason Wang wrote: > We used to queue tx packets in sk_receive_queue, this is less > efficient since it requires spinlocks to synchronize between producer > and consumer. > > This patch tries to address this by using circular buffer which allows > lockless

Re: [PATCH 3/4] phy: rockchip-emmc: configure default output tap delay

Hi Doug, On 2016/5/14 6:25, Doug Anderson wrote: Hi, On Thu, May 12, 2016 at 3:43 PM, Brian Norris wrote: The output tap delay controls helps maintain the hold requirements for eMMC. The exact value is dependent on the SoC and other factors, though it isn't really

Re: [PATCH 3/4] phy: rockchip-emmc: configure default output tap delay

Hi Doug, On 2016/5/14 6:25, Doug Anderson wrote: Hi, On Thu, May 12, 2016 at 3:43 PM, Brian Norris wrote: The output tap delay controls helps maintain the hold requirements for eMMC. The exact value is dependent on the SoC and other factors, though it isn't really an exact science. But the

Re: [PATCH net-next] tuntap: introduce tx skb ring

On Mon, 2016-05-16 at 09:17 +0800, Jason Wang wrote: > We used to queue tx packets in sk_receive_queue, this is less > efficient since it requires spinlocks to synchronize between producer > and consumer. ... > struct tun_struct *detached; > + /* reader lock */ > + spinlock_t

Re: [PATCH net-next] tuntap: introduce tx skb ring

On Mon, 2016-05-16 at 09:17 +0800, Jason Wang wrote: > We used to queue tx packets in sk_receive_queue, this is less > efficient since it requires spinlocks to synchronize between producer > and consumer. ... > struct tun_struct *detached; > + /* reader lock */ > + spinlock_t

Linux v4.6 does not work with Centos 7 (Radeon) but works with Linux v4.5

A lot of breakage for Building v4.6 on Centos 7. The following error occurs after booting Linux v4.6 on Centos 7 with a Radeon Adapter: R600_cp: Failed to load Firmware "Radeon/R600_rlc.bin FATAL Error during GPU init. Linux v4.5 works fine. Also of note, someone moved some scripts around

Linux v4.6 does not work with Centos 7 (Radeon) but works with Linux v4.5

A lot of breakage for Building v4.6 on Centos 7. The following error occurs after booting Linux v4.6 on Centos 7 with a Radeon Adapter: R600_cp: Failed to load Firmware "Radeon/R600_rlc.bin FATAL Error during GPU init. Linux v4.5 works fine. Also of note, someone moved some scripts around

linux-next: manual merge of the clk tree with the mips tree

Hi all, Today's linux-next merge of the clk tree got a conflict in: drivers/clk/Kconfig between commit: ce6e11884659 ("CLK: microchip: Add Microchip PIC32 clock driver.") from the mips tree and commit: 0bbd72b4c64f ("clk: Add Oxford Semiconductor OXNAS Standard Clocks") from the clk

linux-next: manual merge of the clk tree with the mips tree

Hi all, Today's linux-next merge of the clk tree got a conflict in: drivers/clk/Kconfig between commit: ce6e11884659 ("CLK: microchip: Add Microchip PIC32 clock driver.") from the mips tree and commit: 0bbd72b4c64f ("clk: Add Oxford Semiconductor OXNAS Standard Clocks") from the clk

[git pull] vfs.git

FWIW, I considered sending that pile in several pull requests, but for some reason git request-pull v4.6 vfs work.lookups spews something very odd into diffstat - files that have never been touched by it and, in fact, doing merge with mainline does *not* end up with those files anywhere in the

[git pull] vfs.git

FWIW, I considered sending that pile in several pull requests, but for some reason git request-pull v4.6 vfs work.lookups spews something very odd into diffstat - files that have never been touched by it and, in fact, doing merge with mainline does *not* end up with those files anywhere in the

Re: [PATCH 08/17] perf record: Don't poll on overwrite channel

On 2016/5/13 21:12, Arnaldo Carvalho de Melo wrote: Em Fri, May 13, 2016 at 07:56:05AM +, Wang Nan escreveu: There's no need to receive events from overwritable ring buffer. Instead, perf should make them run background until something happen. This patch makes normal events from overwrite

Re: [PATCH 08/17] perf record: Don't poll on overwrite channel

On 2016/5/13 21:12, Arnaldo Carvalho de Melo wrote: Em Fri, May 13, 2016 at 07:56:05AM +, Wang Nan escreveu: There's no need to receive events from overwritable ring buffer. Instead, perf should make them run background until something happen. This patch makes normal events from overwrite

Re: [PATCH v5 09/12] zsmalloc: separate free_zspage from putback_zspage

On (05/09/16 11:20), Minchan Kim wrote: > Currently, putback_zspage does free zspage under class->lock > if fullness become ZS_EMPTY but it makes trouble to implement > locking scheme for new zspage migration. > So, this patch is to separate free_zspage from putback_zspage > and free zspage out of

Re: [PATCH v5 09/12] zsmalloc: separate free_zspage from putback_zspage

On (05/09/16 11:20), Minchan Kim wrote: > Currently, putback_zspage does free zspage under class->lock > if fullness become ZS_EMPTY but it makes trouble to implement > locking scheme for new zspage migration. > So, this patch is to separate free_zspage from putback_zspage > and free zspage out of

Re: [PATCH v5 08/12] zsmalloc: introduce zspage structure

On (05/09/16 11:20), Minchan Kim wrote: > We have squeezed meta data of zspage into first page's descriptor. > So, to get meta data from subpage, we should get first page first > of all. But it makes trouble to implment page migration feature > of zsmalloc because any place where to get first page

Re: [PATCH v5 08/12] zsmalloc: introduce zspage structure

On (05/09/16 11:20), Minchan Kim wrote: > We have squeezed meta data of zspage into first page's descriptor. > So, to get meta data from subpage, we should get first page first > of all. But it makes trouble to implment page migration feature > of zsmalloc because any place where to get first page

RE: [PATCH] ACPI: Execute the _PTS method when system reboot

To whom may concern, A Lenovo feature depends on _PTS method execution when reboot. And after check the ACPI spec, I think _PTS should be exectued when reboo. This patch could fix the problem. Any comments of this patch? Many thanks! Ocean He / 何海洋 SW Development Dept. Beijing Design Center

RE: [PATCH] ACPI: Execute the _PTS method when system reboot

To whom may concern, A Lenovo feature depends on _PTS method execution when reboot. And after check the ACPI spec, I think _PTS should be exectued when reboo. This patch could fix the problem. Any comments of this patch? Many thanks! Ocean He / 何海洋 SW Development Dept. Beijing Design Center

Re: [PATCH] ixgbe: take online CPU number as MQ max limit when alloc_etherdev_mq()

Alexander, On 2016/5/14 0:46, Alexander Duyck wrote: On Thu, May 12, 2016 at 10:56 PM, Ethan Zhao wrote: Allocating 64 Tx/Rx as default doesn't benefit perfomrnace when less CPUs were assigned. especially when DCB is enabled, so we should take num_online_cpus() as top

Re: [PATCH] ixgbe: take online CPU number as MQ max limit when alloc_etherdev_mq()

Alexander, On 2016/5/14 0:46, Alexander Duyck wrote: On Thu, May 12, 2016 at 10:56 PM, Ethan Zhao wrote: Allocating 64 Tx/Rx as default doesn't benefit perfomrnace when less CPUs were assigned. especially when DCB is enabled, so we should take num_online_cpus() as top limit, and aslo to make

Building older mips kernels with different versions of binutils; possible patch for 3.2 and 3.4

Hi folks, building mips images with a consistent infrastructure is becoming more and more difficult. Current state is as follows. Binutils/ 2.222.242.25 Kernel 3.2 X - - 3.4 X - - 3.10X X - 3.14X

Building older mips kernels with different versions of binutils; possible patch for 3.2 and 3.4

Hi folks, building mips images with a consistent infrastructure is becoming more and more difficult. Current state is as follows. Binutils/ 2.222.242.25 Kernel 3.2 X - - 3.4 X - - 3.10X X - 3.14X

Re: [PATCH v3 3/7 UPDATE] perf tools: Add option for the path of buildid dsos under symfs

On 5/15/16 7:30 PM, Hekuang wrote: In previous patch, I use 'perf buildid-cache -a' to add vdso binary into the HOST buildid dir. So 'perf buildid-cache' needs the symfs option?

Re: [PATCH v3 3/7 UPDATE] perf tools: Add option for the path of buildid dsos under symfs

On 5/15/16 7:30 PM, Hekuang wrote: In previous patch, I use 'perf buildid-cache -a' to add vdso binary into the HOST buildid dir. So 'perf buildid-cache' needs the symfs option?

[PATCH] audit: fixup: log on errors from filter user rules

In commit 724e4fcc the intention was to pass any errors back from audit_filter_user_rules() to audit_filter_user(). Add that code. Signed-off-by: Richard Guy Briggs --- kernel/auditfilter.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH] audit: fixup: log on errors from filter user rules

In commit 724e4fcc the intention was to pass any errors back from audit_filter_user_rules() to audit_filter_user(). Add that code. Signed-off-by: Richard Guy Briggs --- kernel/auditfilter.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/auditfilter.c

[RFC PATCH 7/9] sched/fair: Optimize __update_sched_avg()

__update_sched_avg() has these steps: 1. add the remainder of the last incomplete period 2. decay old sum 3. accumulate new sum in full periods since last_update_time 4. add the current incomplete period 5. update averages Previously, we separately computed steps 1, 3, and 4, leading

[RFC PATCH 2/9] documentation: Add scheduler/sched-avg.txt

This doc file has the program to generate the constants to compute sched averages. Signed-off-by: Yuyang Du --- Documentation/scheduler/sched-avg.txt | 94 + 1 file changed, 94 insertions(+) create mode 100644

[RFC PATCH 7/9] sched/fair: Optimize __update_sched_avg()

__update_sched_avg() has these steps: 1. add the remainder of the last incomplete period 2. decay old sum 3. accumulate new sum in full periods since last_update_time 4. add the current incomplete period 5. update averages Previously, we separately computed steps 1, 3, and 4, leading

[RFC PATCH 2/9] documentation: Add scheduler/sched-avg.txt

This doc file has the program to generate the constants to compute sched averages. Signed-off-by: Yuyang Du --- Documentation/scheduler/sched-avg.txt | 94 + 1 file changed, 94 insertions(+) create mode 100644 Documentation/scheduler/sched-avg.txt diff --git

[RFC PATCH 3/9] sched/fair: Add static to remove_entity_load_avg()

remove_entity_load_avg() is only called in fair.c, so add static to it. Signed-off-by: Yuyang Du --- kernel/sched/fair.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 2635561..66fba3f 100644 ---

[RFC PATCH 5/9] sched/fair: Change the variable to hold the number of periods to 32-bit

In sched average update, a period is about 1ms, so a 32-bit unsigned integer can approximately hold a maximum of 49 (=2^32/1000/3600/24) days. For usual cases, 32-bit is big enough and 64-bit is needless. But if a task sleeps longer than it, there can be two outcomes: Consider a task sleeps m

[RFC PATCH 3/9] sched/fair: Add static to remove_entity_load_avg()

remove_entity_load_avg() is only called in fair.c, so add static to it. Signed-off-by: Yuyang Du --- kernel/sched/fair.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c index 2635561..66fba3f 100644 --- a/kernel/sched/fair.c +++

[RFC PATCH 5/9] sched/fair: Change the variable to hold the number of periods to 32-bit

In sched average update, a period is about 1ms, so a 32-bit unsigned integer can approximately hold a maximum of 49 (=2^32/1000/3600/24) days. For usual cases, 32-bit is big enough and 64-bit is needless. But if a task sleeps longer than it, there can be two outcomes: Consider a task sleeps m

[RFC PATCH 9/9] sched/fair: Rename scale_load() and scale_load_down()

Rename scale_load() and scale_load_down() to user_to_kernel_load() and kernel_to_user_load() respectively. This helps us tag them clearly and avoid confusion. Signed-off-by: Yuyang Du --- kernel/sched/core.c |8 kernel/sched/fair.c | 11 ---

[RFC PATCH 4/9] sched/fair: Rename variable names for sched averages

The names of sched averages (including load_avg and util_avg) have been changed and added in the past a couple of years, some of the names are a bit confusing especially to people who first read them. This patch attempts to make the names more self-explaining. And some comments are updated too.

[RFC PATCH 8/9] sched/fair: Remove scale_load_down() for load_avg

Currently, load_avg = scale_load_down(load) * runnable%. The extra scaling down of load does not make much sense, because load_avg is primarily THE load and on top of that, we take runnable time into account. We therefore remove scale_load_down() for load_avg. But we need to carefully consider

[RFC PATCH 9/9] sched/fair: Rename scale_load() and scale_load_down()

Rename scale_load() and scale_load_down() to user_to_kernel_load() and kernel_to_user_load() respectively. This helps us tag them clearly and avoid confusion. Signed-off-by: Yuyang Du --- kernel/sched/core.c |8 kernel/sched/fair.c | 11 --- kernel/sched/sched.h | 16

[RFC PATCH 4/9] sched/fair: Rename variable names for sched averages

The names of sched averages (including load_avg and util_avg) have been changed and added in the past a couple of years, some of the names are a bit confusing especially to people who first read them. This patch attempts to make the names more self-explaining. And some comments are updated too.

[RFC PATCH 8/9] sched/fair: Remove scale_load_down() for load_avg

Currently, load_avg = scale_load_down(load) * runnable%. The extra scaling down of load does not make much sense, because load_avg is primarily THE load and on top of that, we take runnable time into account. We therefore remove scale_load_down() for load_avg. But we need to carefully consider

[RFC PATCH 1/9] sched/fair: Chance LOAD_AVG_MAX_N from 345 to 347

In commit 5b51f2f80b3b906ce59bd4dce6eca3c7f34cb1b9 Author: Paul Turner Date: Thu Oct 4 13:18:32 2012 +0200 sched: Make __update_entity_runnable_avg() fast Paul has a program to compute LOAD_AVG_MAX_N, which basically means how many periods (at least) are needed for

[RFC PATCH 1/9] sched/fair: Chance LOAD_AVG_MAX_N from 345 to 347

In commit 5b51f2f80b3b906ce59bd4dce6eca3c7f34cb1b9 Author: Paul Turner Date: Thu Oct 4 13:18:32 2012 +0200 sched: Make __update_entity_runnable_avg() fast Paul has a program to compute LOAD_AVG_MAX_N, which basically means how many periods (at least) are needed for LOAD_AVG_MAX, and the

[RFC PATCH 0/9] Clean up and optimize sched averages

Hi Peter, Continue the left patches in this series. I realized some patches should need thorough discussion (finally), so this post is marked RFC. - For LOAD_AVG_MAX_N, I am OK to stick to the old value, but it is worthwhile to get it cleared to the true value. - About the renames, I

[RFC PATCH 6/9] sched/fair: Add __always_inline compiler attribute to __accumulate_sum()

__accumulate_sum()'s caller and sibling functions are all inlined. And it will be called almost every time in its caller. It does not make sense if only it is not inlined. Signed-off-by: Yuyang Du --- kernel/sched/fair.c |2 +- 1 file changed, 1 insertion(+), 1

[RFC PATCH 0/9] Clean up and optimize sched averages

Hi Peter, Continue the left patches in this series. I realized some patches should need thorough discussion (finally), so this post is marked RFC. - For LOAD_AVG_MAX_N, I am OK to stick to the old value, but it is worthwhile to get it cleared to the true value. - About the renames, I

[RFC PATCH 6/9] sched/fair: Add __always_inline compiler attribute to __accumulate_sum()

__accumulate_sum()'s caller and sibling functions are all inlined. And it will be called almost every time in its caller. It does not make sense if only it is not inlined. Signed-off-by: Yuyang Du --- kernel/sched/fair.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH v7 10/14] usb: otg: add hcd companion support

On Thu, May 12, 2016 at 03:13:48PM +0300, Roger Quadros wrote: > Hi, > > On 12/05/16 13:31, Yoshihiro Shimoda wrote: > > Hi, > > > >> From: Roger Quadros > >> Sent: Thursday, May 12, 2016 6:32 PM > >> > >> Hi, > >> > >> On 12/05/16 11:34, Roger Quadros wrote: > >>> On 12/05/16 07:00, Yoshihiro

Re: [PATCH v7 10/14] usb: otg: add hcd companion support

On Thu, May 12, 2016 at 03:13:48PM +0300, Roger Quadros wrote: > Hi, > > On 12/05/16 13:31, Yoshihiro Shimoda wrote: > > Hi, > > > >> From: Roger Quadros > >> Sent: Thursday, May 12, 2016 6:32 PM > >> > >> Hi, > >> > >> On 12/05/16 11:34, Roger Quadros wrote: > >>> On 12/05/16 07:00, Yoshihiro

[PATCH V5 3/6] vfio: platform: determine reset capability

Creating a new function to determine if this driver supports reset function or not. This is an attempt to abstract device tree calls from the rest of the code. Signed-off-by: Sinan Kaya --- drivers/vfio/platform/vfio_platform_common.c | 7 ++- 1 file changed, 6

[PATCH V5 3/6] vfio: platform: determine reset capability

Creating a new function to determine if this driver supports reset function or not. This is an attempt to abstract device tree calls from the rest of the code. Signed-off-by: Sinan Kaya --- drivers/vfio/platform/vfio_platform_common.c | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-)

[PATCH V5 1/6] vfio: platform: rename reset function

Renaming the reset function to of_reset as it is only used by the device tree based platforms. Signed-off-by: Sinan Kaya --- drivers/vfio/platform/vfio_platform_common.c | 30 +-- drivers/vfio/platform/vfio_platform_private.h | 6 +++--- 2 files

[PATCH V5 2/6] vfio: platform: move reset call to a common function

The reset call sequence seems to replicate itself multiple times across the file. Grouping them together for maintenance reasons. Signed-off-by: Sinan Kaya --- drivers/vfio/platform/vfio_platform_common.c | 31 ++-- 1 file changed, 15 insertions(+),

[PATCH V5 4/6] vfio: platform: add support for ACPI probe

The code is using the compatible DT string to associate a reset driver with the actual device itself. The compatible string does not exist on ACPI based systems. HID is the unique identifier for a device driver instead. Signed-off-by: Sinan Kaya ---

[PATCH V5 1/6] vfio: platform: rename reset function

Renaming the reset function to of_reset as it is only used by the device tree based platforms. Signed-off-by: Sinan Kaya --- drivers/vfio/platform/vfio_platform_common.c | 30 +-- drivers/vfio/platform/vfio_platform_private.h | 6 +++--- 2 files changed, 18

[PATCH V5 2/6] vfio: platform: move reset call to a common function

The reset call sequence seems to replicate itself multiple times across the file. Grouping them together for maintenance reasons. Signed-off-by: Sinan Kaya --- drivers/vfio/platform/vfio_platform_common.c | 31 ++-- 1 file changed, 15 insertions(+), 16 deletions(-) diff

[PATCH V5 4/6] vfio: platform: add support for ACPI probe

The code is using the compatible DT string to associate a reset driver with the actual device itself. The compatible string does not exist on ACPI based systems. HID is the unique identifier for a device driver instead. Signed-off-by: Sinan Kaya --- drivers/vfio/platform/vfio_platform_common.c

[PATCH V5 5/6] vfio: platform: call _RST method when using ACPI

The device tree code checks for the presence of a reset driver and calls the of_reset function pointer by looking up the reset driver as a module. ACPI defines _RST method to perform device level reset. After the _RST method is executed, the OS can resume using the device. This patch checks the

Re: [PATCH v5 07/12] zsmalloc: factor page chain functionality out

On (05/09/16 11:20), Minchan Kim wrote: > For page migration, we need to create page chain of zspage dynamically > so this patch factors it out from alloc_zspage. > > Cc: Sergey Senozhatsky > Signed-off-by: Minchan Kim Reviewed-by: Sergey

[PATCH V5 6/6] vfio, platform: make reset driver a requirement by default

The code was allowing platform devices to be used without a supporting VFIO reset driver. The hardware can be left in some inconsistent state after a guest machine abort. The reset driver will put the hardware back to safe state and disable interrupts before returning the control back to the host

[PATCH V5 6/6] vfio, platform: make reset driver a requirement by default

The code was allowing platform devices to be used without a supporting VFIO reset driver. The hardware can be left in some inconsistent state after a guest machine abort. The reset driver will put the hardware back to safe state and disable interrupts before returning the control back to the host

[PATCH V5 5/6] vfio: platform: call _RST method when using ACPI

The device tree code checks for the presence of a reset driver and calls the of_reset function pointer by looking up the reset driver as a module. ACPI defines _RST method to perform device level reset. After the _RST method is executed, the OS can resume using the device. This patch checks the

Re: [PATCH v5 07/12] zsmalloc: factor page chain functionality out

On (05/09/16 11:20), Minchan Kim wrote: > For page migration, we need to create page chain of zspage dynamically > so this patch factors it out from alloc_zspage. > > Cc: Sergey Senozhatsky > Signed-off-by: Minchan Kim Reviewed-by: Sergey Senozhatsky [..] > + page =

Re: [patch net-next 07/11] net: hns: dsaf adds support of acpi

On 2016/5/13 21:12, Andy Shevchenko wrote: > On Fri, 2016-05-13 at 16:19 +0800, Yisen Zhuang wrote: >> From: Kejian Yan >> >> Dsaf needs to get configuration parameter by ACPI, so this patch add >> support of ACPI. >> > Looks like at some point better to split driver to

linux-next: build failure after merge of the spi tree

Hi Mark, After merging the spi tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/spi/spi-orion.c: In function 'orion_spi_write_read': drivers/spi/spi-orion.c:407:3: error: implicit declaration of function 'writesl' [-Werror=implicit-function-declaration]

Re: [patch net-next 07/11] net: hns: dsaf adds support of acpi

On 2016/5/13 21:12, Andy Shevchenko wrote: > On Fri, 2016-05-13 at 16:19 +0800, Yisen Zhuang wrote: >> From: Kejian Yan >> >> Dsaf needs to get configuration parameter by ACPI, so this patch add >> support of ACPI. >> > Looks like at some point better to split driver to core part, and PCI > and

linux-next: build failure after merge of the spi tree

Hi Mark, After merging the spi tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/spi/spi-orion.c: In function 'orion_spi_write_read': drivers/spi/spi-orion.c:407:3: error: implicit declaration of function 'writesl' [-Werror=implicit-function-declaration]

Re: [patch net-next 06/11] ACPI: bus: move acpi_match_device_ids() to linux/acpi.h

On 2016/5/13 21:15, Andy Shevchenko wrote: > On Fri, 2016-05-13 at 16:19 +0800, Yisen Zhuang wrote: >> From: Hanjun Guo >> >> acpi_match_device_ids() will be used for drivers to match >> different hardware versions, it will be compiled in non-ACPI >> case, but

Re: [patch net-next 06/11] ACPI: bus: move acpi_match_device_ids() to linux/acpi.h

On 2016/5/13 21:15, Andy Shevchenko wrote: > On Fri, 2016-05-13 at 16:19 +0800, Yisen Zhuang wrote: >> From: Hanjun Guo >> >> acpi_match_device_ids() will be used for drivers to match >> different hardware versions, it will be compiled in non-ACPI >> case, but acpi_match_device_ids() in

Re: [PATCH v5 06/12] zsmalloc: use accessor

On (05/09/16 11:20), Minchan Kim wrote: > Upcoming patch will change how to encode zspage meta so for easy review, > this patch wraps code to access metadata as accessor. > > Cc: Sergey Senozhatsky > Signed-off-by: Minchan Kim Reviewed-by:

Re: [PATCH v5 06/12] zsmalloc: use accessor

On (05/09/16 11:20), Minchan Kim wrote: > Upcoming patch will change how to encode zspage meta so for easy review, > this patch wraps code to access metadata as accessor. > > Cc: Sergey Senozhatsky > Signed-off-by: Minchan Kim Reviewed-by: Sergey Senozhatsky -ss

  1   2   3   >