Currently a condition when RCU tree is unable to accommodate
the configured number of CPUs is not permitted and causes
a fall back to compile-time values. However, the code has no
means to exceed the RCU tree capacity neither at compile-time
nor in run-time. Therefore, if the condition is met in ru
This update simplifies rcu_init_geometry() code flow
and makes calculation of the total number of rcu_node
structures more easy to read.
The update relies on the fact num_rcu_lvl[] is never
accessed beyond rcu_num_lvls index by the rest of the
code. Therefore, there is no need initialize the whole
Variable rcu_num_lvls is limited by RCU_NUM_LVLS macro.
In turn, rcu_state::levelcnt[] array is never accessed
beyond rcu_num_lvls. Thus, rcu_state::levelcnt[] is safe
to limit to RCU_NUM_LVLS items.
Since rcu_num_lvls could be changed during boot (as result
of rcutree.rcu_fanout_leaf kernel param
Local variable 'n' mimics 'nr_cpu_ids' while the both are
used within one function. There is no reason for 'n' to
exist whatsoever.
Cc: "Paul E. McKenney"
Signed-off-by: Alexander Gordeev
---
kernel/rcu/tree.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/ke
Although a number of RCU levels may be less than the current
maximum of four, some static data associated with each level
are allocated for all four levels. As result, the extra data
never get accessed and just wast memory. This update limits
count of allocated items to the number of used RCU level
Members rcu_state::levelcnt[] and rcu_state::levelspread[]
are only used at init. There is no reason to keep them
afterwards.
Cc: "Paul E. McKenney"
Signed-off-by: Alexander Gordeev
---
kernel/rcu/tree.c | 27 +++
kernel/rcu/tree.h | 2 --
2 files changed, 15 insertions
Hi Paul,
Here is cleanup of RCU tree initialization rebased on linux-rcu rcu/next
repo, as you requested. Please, note an extra patch #10 that was not
present in the first post.
The series successfully passes kernel build test with CONFIG_RCU_FANOUT
and CONFIG_RCU_FANOUT_LEAF equal to 5.
Cc: "Pa
Current code suggests that introducing the extra level to
rcu_capacity[] array makes some of the arithmetic easier.
Well, in fact it appears rather confusing and unnecessary.
Cc: "Paul E. McKenney"
Signed-off-by: Alexander Gordeev
---
kernel/rcu/tree.c | 16 +++-
1 file changed, 7 i
Number of items in rcu_capacity[] array is defined by macro
MAX_RCU_LVLS. However, that array is never accessed beyond
RCU_NUM_LVLS index. Therefore, we can limit the array to
RCU_NUM_LVLS items and eliminate MAX_RCU_LVLS. As result,
in most cases the memory is conserved.
Cc: "Paul E. McKenney"
S
This update makes arithmetic to calculate number of RCU nodes
more straight and easy to read.
Cc: "Paul E. McKenney"
Signed-off-by: Alexander Gordeev
---
kernel/rcu/tree.h| 17 -
kernel/rcu/tree_plugin.h | 4 ++--
2 files changed, 6 insertions(+), 15 deletions(-)
diff
Field rcu_node::grpnum is used to set rcu_node::grpmask at init
and never accessed afterwards. There is no reason to have it.
Cc: "Paul E. McKenney"
Signed-off-by: Alexander Gordeev
---
kernel/rcu/tree.c | 5 ++---
kernel/rcu/tree.h | 3 +--
2 files changed, 3 insertions(+), 5 deletions(-)
dif
On 03/09/2015 06:23 AM, Jaehoon Chung wrote:
> Hi, Karol.
>
> This patch can't apply. You need to rebase on latest mmc-next.
> Then i will check this patch.
Ok, no problem. Sorry for that.
>
> Best Regards,
> Jaehoon Chung
>
> On 03/06/2015 10:29 PM, Karol Wrona wrote:
>> This patch adds runtim
Hi Jaegeuk,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
> Sent: Monday, March 09, 2015 11:49 AM
> To: Chao Yu
> Cc: 'Changman Lee'; linux-f2fs-de...@lists.sourceforge.net;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] f2fs: fix to truncate inline data past
On Mon, Mar 09, 2015 at 07:42:53AM +, Lad, Prabhakar wrote:
> On Mon, Mar 9, 2015 at 7:35 AM, Sudip Mukherjee
> wrote:
> >
> >
> > this patch will give checkpatch warnings about use of printk.
> > this patch was mainly to fix the build warnings. printk will be
> > converted to pr_* and dev_* i
Hi Wolfram,
On Sat, 2015-03-07 at 01:24 +0100, Wolfram Sang wrote:
> > > Presented like this I wonder if this merits being a dev_err at all.
> > > Wouldn't dev_dbg be more adequate? This might remove the need for the
> > > condition and also avoid bothering everyone if something in the platform
>
On Mon, Mar 09, 2015 at 05:39:20PM +1030, Rusty Russell wrote:
> "Michael S. Tsirkin" writes:
> > virtio spec requires that all drivers set DRIVER_OK
> > before using devices. While rpmsg isn't yet
> > included in the virtio 1 spec, previous spec versions
> > also required this.
> >
> > virtio rpm
The maximum of SW-IOMMU is limited to 2^11*128 = 256K.
And the size of IO_TLB_DEFAULT_SIZE is limited to (64UL<<20) 64M now.
While in different platform and different requirement this seems improper.
So modifing the IO_TLB_SEGSIZE to io_tlb_segsize and IO_TLB_DEFAULT_SIZE
to io_tlb_default_size whi
On 27.02.2015 22:54, Benjamin Herrenschmidt wrote:
On Fri, 2015-02-27 at 09:28 +0200, Purcareata Bogdan wrote:
Ping?
What is the ping for ?
Ben.
Making sure the patches are not lost on the mailing lists :) Didn't
receive any feedback on v4 and just wanted to check if there's anything
more
On Fri, 2015-03-06 at 12:05 +0100, Paul Bolle wrote:
> On Fri, 2015-03-06 at 14:24 +0800, Yingjoe Chen wrote:
> > --- a/drivers/pinctrl/mediatek/Kconfig
> > +++ b/drivers/pinctrl/mediatek/Kconfig
>
> > @@ -8,11 +8,13 @@ config PINCTRL_MTK_COMMON
> > select OF_GPIO
> >
> > config PINCTRL_MT8
On Sun, Mar 08, 2015 at 04:55:24PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> When cycles or instructions do not print anything, as in being,
> --per-socket or --per-core modi, the ratio column was not
> correctly indented for them. This lead to some ratios
> not lining up with the others. A
Ping.
Any opinion?
Thanks,
Boqun Feng
On Wed, Feb 25, 2015 at 8:31 PM, Boqun Feng wrote:
> In the current implementation of getname_flags, filename in the
> user-space will be recopied if it takes more space that
> EMBEDDED_NAME_MAX, however, at this moment, EMBEDDED_NAME_MAX bytes of
> the file
Hi Yong Wu,
On Fri, Mar 6, 2015 at 6:48 PM, wrote:
> From: Yong Wu
>
> This patch adds support for mediatek m4u (MultiMedia Memory Management Unit).
> Currently this only supports m4u gen 2 with 2 levels of page table on mt8173.
>
> Signed-off-by: Yong Wu
> ---
> drivers/iommu/Kconfig
Hi,
On 09-03-15 07:46, Dmitry Torokhov wrote:
On Wed, Feb 25, 2015 at 03:58:20PM +0100, Hans de Goede wrote:
Hi,
On 25-02-15 15:36, Benjamin Tissoires wrote:
On Mon, Feb 16, 2015 at 10:23 PM, Benjamin Tissoires
wrote:
On Fri, Feb 6, 2015 at 3:04 PM, Benjamin Tissoires
wrote:
Hi,
This is
Hi Taeung,
(Please add Jiri to CC when sending a patch for perf tools..)
Thanks for doing this. I left some more description and suggestion
from my understanding, I think other guys will provide more helpful
and clear words on other parts.
On Sat, Mar 07, 2015 at 09:30:05PM +0900, Taeung wrote
On Mon, Mar 09, 2015 at 03:42:30PM +0800, Zhang Zhen wrote:
> drivers/tty/serial/8250/8250_core.c: In function ‘serial8250_console_write’:
> drivers/tty/serial/8250/8250_core.c:3244: warning: ‘flags’ may be used u
> unitialized in this function
>
> Signed-off-by: Zhang Zhen
> ---
> drivers/tty/s
Hi Stephen,
> On Mar 6, 2015, at 8:34 PM, Stephen Boyd wrote:
> On 03/06/15 07:26, Ivan T. Ivanov wrote:
> > Ensure that driver is owner of the GPIO's used for CS signals.
> Why? What happens if we don’t?
We can have wrong DT configuration, which could reconfigure
GPIO’s without any warning or
Change based on Paul's suggestion.
Old patch can be found at:
http://lists.infradead.org/pipermail/linux-mediatek/2015-March/57.html
--
ARM64 maintainer doesn't want to add MACH_* for each SoC.
Adjust mt8173 pinctrl kconfig entry so user can manually select it.
Also make PINCTRL_MT8135 bu
On Sun, Mar 08, 2015 at 04:55:23PM -0700, Andi Kleen wrote:
SNIP
> - update_stats(&runtime_dtlb_cache_stats[ctx][0], count[0]);
> + update_stats(&runtime_dtlb_cache_stats[ctx][cpu], count[0]);
> else if (perf_evsel__match(counter, HW_CACHE, HW_CACHE_ITLB))
> -
This adds the SCPSYS device node to the MT8173 dtsi file.
Signed-off-by: Sascha Hauer
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
index 8554ec3..9fa64ac
Enable support for generic power domains in the config.
Signed-off-by: Sascha Hauer
---
arch/arm64/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 1b8e973..aef77d2 100644
--- a/arch/arm64/Kconfig
+++ b/arch/arm64/Kconfig
@@ -174,6 +174,7
This adds documentation for the MediaTek SCPSYS unit found in MT8173 SoCs.
Signed-off-by: Sascha Hauer
---
.../devicetree/bindings/soc/mediatek/scpsys.txt| 32 ++
1 file changed, 32 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc/mediatek/scpsys.tx
s series adds support for the MediaTek SCPSYS unit.
The SCPSYS unit handles several power management related tasks such
as thermal measurement, DVFS, interrupt filter and low level sleep
control.
The initial support only contains the generic power domain handling.
This is needed to turn on power
Signed-off-by: Sascha Hauer
---
drivers/soc/mediatek/Kconfig | 6 +
drivers/soc/mediatek/Makefile| 1 +
drivers/soc/mediatek/mtk-scpsys.c| 398 +++
include/dt-bindings/power/mt8173-power.h | 15 ++
4 files changed, 420 insertions(+)
Hi Pavel,
On Sun, Mar 8, 2015 at 9:57 PM, Pavel Machek wrote:
> Ok, so I played with RGB LED a bit, and we have quite a gap in
> documentation: what 50% brightness means is non-trivial and very
> important in case we want to do smooth blinking and color transitions.
>
> Signed-off-by: Pavel Mache
On Fri, Feb 20, 2015 at 4:40 PM, Greg Kroah-Hartman
wrote:
> On Wed, Feb 18, 2015 at 05:12:18PM +0100, Linus Walleij wrote:
>> This fixes a regression from the net subsystem:
>> After commit d52fdbb735c36a209f36a628d40ca9185b349ba7
>> "smc91x: retrieve IRQ and trigger flags in a modern way"
>> a r
Hi,
On 08/03/2015 at 02:12:53 +0100, Rafael J. Wysocki wrote :
> > > I think you misunderstood, that is exactly the expected behaviour. This
> > > is hardware defined. Once the watchdog is started, nobody can stop it.
> > > Trying to change the mode register will result in a reset of the
> > > SoC
On Sun, Mar 08, 2015 at 04:55:22PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> Currently in perf IPC and other metrics cannot be directly shown
> separately for both user and kernel in a single run. The problem was
> that the metrics matching code did not check event qualifiers.
>
> With thi
Hi Yong,
On Fri, Mar 6, 2015 at 6:37 PM, wrote:
> From: Yong Wu
>
> This patch add SMI(Smart Multimedia Interface) driver. This driver
> is responsible to enable/disable iommu and control the clocks of each
> local arbiter.
High-level:
Is there more to the smi (or smi-larb) driver, or is i
On Sun, Mar 08, 2015 at 04:55:21PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> The information how much a counter ran in perf stat can be quite
> interesting for other tools to judge how trustworthy a measurement is.
>
> Currently it is only output in non CSV mode.
>
> This patches make per
return type of wait_for_completion_timeout is unsigned long not int. As
leftover is used exclusively for wait_for_completion_timeout its type is
simply changed to unsigned long.
Signed-off-by: Nicholas Mc Guire
---
This was only compile tested for x86_64_defconfig +
CONFIG_SCSI_LOWLEVEL=y, CONFI
On Sun, 08 Mar 2015, Jason Cooper wrote:
> Lee,
>
> On Wed, Feb 18, 2015 at 03:13:56PM +, Lee Jones wrote:
> > Rebased (again) and resending.
> >
> > This driver enables IRQs which are controlled using System Configuration
> > registers. Without it Performance Monitoring, Core Sight Tracin
On Mon, Mar 9, 2015 at 7:35 AM, Sudip Mukherjee
wrote:
> check if it is already defined before defining SM750LE_REVISION_ID
> again and at the same time mention correct data type.
>
> Signed-off-by: Sudip Mukherjee
> ---
>
> v2: removed the redundant cast in sm750_hw.c
>
> drivers/staging/sm750f
drivers/tty/serial/8250/8250_core.c: In function ‘serial8250_console_write’:
drivers/tty/serial/8250/8250_core.c:3244: warning: ‘flags’ may be used u
unitialized in this function
Signed-off-by: Zhang Zhen
---
drivers/tty/serial/8250/8250_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(
Dear maintainers & communities,
This patch introduces DTS thermal driver for Intel Quark X1000.
The code implementation is based on intel_soc_dts_thermal.c.
Intel Quark X1000 has one on-die DTS with two configurable trip points:
critical and hot trip points. However, todate, UEFI BIOS for Quark X
In Intel Quark SoC X1000, there is one on-die digital temperature sensor(DTS).
The DTS offers both hot & critical trip points.
However, in current distribution of UEFI BIOS for Quark platform, only
critical trip point is configured to be 105 degree Celsius (based on Quark
SW ver1.0.1 and hot trip
FAO Mark,
> This patch device tree binding documentation for rt5033 multifunction device.
>
> Cc: Sebastian Reichel
> Cc: Lee Jones
> Cc: Mark Brown
> Cc: Rob Herring
> Cc: Pawel Moll
> Cc: Mark Rutland
> Cc: Ian campbell
> Cc: Kumar Gala
> Signed-off-by: Beomho Seo
> Acked-by: Chanwoo C
On Mon, Mar 9, 2015 at 7:35 AM, Sudip Mukherjee
wrote:
> mention correct format specifier while printing.
> fixes all the build warnings about incorrect argument type while
> printing.
>
> Signed-off-by: Sudip Mukherjee
> ---
>
> V2: Giedrius commented resource_size_t can be either u64 or u32
> d
On Mon, Mar 09, 2015 at 11:27:06AM +0530, Archit Taneja wrote:
> On 03/05/2015 09:14 PM, Daniel Vetter wrote:
> >On Thu, Mar 05, 2015 at 07:10:44AM -0500, Rob Clark wrote:
> >>On Thu, Mar 5, 2015 at 5:06 AM, Archit Taneja
> >>wrote:
> >>>
> >>>On 02/23/2015 09:09 PM, Daniel Vetter wrote:
>
>
If __get_user_pages() is faulting a significant number of hugetlb pages,
usually as the result of mmap(MAP_LOCKED), it can potentially allocate a
very large amount of memory.
If the process has been oom killed, this will cause a lot of memory to
be overcharged to its memcg since it has access to m
From: Xunlei Pang
If there're multiple nodes with the same prio as @node, currently
plist_add() will add @node behind all of them. Now we need to add
@node before all of these nodes for SMP RT scheduler.
This patch adds a common __plist_add() for adding @node before or
after existing nodes with
On 03/08/2015 08:38 PM, Mark Brown wrote:
> On Wed, Mar 04, 2015 at 02:45:00PM +0100, Javier Martinez Canillas wrote:
>
>> The thing is that _regulator_is_enabled() used to return -EINVAL if
>> the rdev didn't have an .is_enabled callback but that changed in
>> commit 9a7f6a4c6edc8 ("regulator: As
From: Xunlei Pang
Currently, SMP RT scheduler has some trouble in dealing with
equal prio cases.
For example, in check_preempt_equal_prio():
When RT1(current task) gets preempted by RT2, if there is a
migratable RT3 with same prio, RT3 will be pushed away instead
of RT1 afterwards, because RT1 w
From: Xunlei Pang
We may suffer from extra rt overload rq due to the affinity,
so when the affinity of any runnable rt task is changed, we
should check to trigger balancing, otherwise it will cause
some unnecessary delayed real-time response. Unfortunately,
current RT global scheduler doesn't tri
kbuild test robot reported that for microblaze-allyesconfig
chan_to_field() and lynxfb_ops_set_par() were not defined. These two
functions were defined under CONFIG_PM, so for any archtecture if
CONFIG_PM is not defined we will have this error.
while moving the lynxfb_suspend() function some very
check if it is already defined before defining SM750LE_REVISION_ID
again and at the same time mention correct data type.
Signed-off-by: Sudip Mukherjee
---
v2: removed the redundant cast in sm750_hw.c
drivers/staging/sm750fb/ddk750_chip.h | 4 +++-
drivers/staging/sm750fb/sm750_hw.c| 2 +-
remove use of #pragma optimize which will usually be ignored by the
compiler.
Signed-off-by: Sudip Mukherjee
---
v2: same as v1
drivers/staging/sm750fb/ddk750_swi2c.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/sm750fb/ddk750_swi2c.c
b/drivers/staging/sm750fb/ddk750_
mention correct format specifier while printing.
fixes all the build warnings about incorrect argument type while
printing.
Signed-off-by: Sudip Mukherjee
---
V2: Giedrius commented resource_size_t can be either u64 or u32
depending on if CONFIG_PHYS_ADDR_T_64BIT. based on his comments i
should
Hello,
Is there a way to get pointer to "struct device" for current module in
kernel driver ?
Thank you,
Ran
--
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-in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 03/08/2015 02:15 PM, Or Gerlitz wrote:
> On Mon, Feb 23, 2015 at 11:14 PM, Jeff Kirsher
> wrote:
> [...]
>> We discussed this during NetConf last week, and Don is correct that a
>> custom sysfs interface is not the way we want to handle this. We
In the function ramoops_probe, the console_size, pmsg_size,
ftrace_size may be update because the value is not the power
of two. We should update the module parameter variables
as well so they are visible through /sys/module/ramoops/parameters
correctly.
Signed-off-by: Wang Long
---
fs/pstore/ra
On 2015年03月09日 15:05, Daniel Kurtz wrote:
On Mon, Mar 9, 2015 at 12:42 PM, Yakir Yang wrote:
- const struct dw_hdmi_mpll_config *mpll_config =
-hdmi->plat_data->mpll_cfg;
- const struct dw_hdmi_curr_ctrl *curr_ctrl = hdmi->plat_data->cur_ctr;
- const str
On 2015年03月09日 14:48, Joe Perches wrote:
On Sun, 2015-03-08 at 21:48 -0700, Joe Perches wrote:
Shouldn't all of these be static?
Don't mind me. These shouldn't be static.
I was a bit mislead by the commit message.
I think it'd be better not to put patch-like
+ and - lines in the commit des
On 2015/3/7 11:01, Tim Kryger wrote:
> You only hit the silicon bug if you bombard the uart with characters
> and simultaneously request a baud rate or framing change.
>
> I'm not sure why you would do either to the uart console. Is it
> possible your host machine is doing something weird?
>
> I
Elements backed by the slab allocator are poisoned when added to a
mempool's reserved pool.
It is also possible to poison elements backed by the page allocator
because the mempool layer knows the allocation order.
This patch extends mempool element poisoning to include memory backed by
the page a
Mempools keep elements in a reserved pool for contexts in which
allocation may not be possible. When an element is allocated from the
reserved pool, its memory contents is the same as when it was added to
the reserved pool.
Because of this, elements lack any free poisoning to detect
use-after-fre
On Mon, 2015-03-09 at 09:07 +0200, Laurent Pinchart wrote:
> Acked-by: Laurent Pinchart
> Should I take the patch in my tree ?
If you want.
Otherwise Andrew will likely pick it up eventually.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
"Michael S. Tsirkin" writes:
> virtio spec requires that all drivers set DRIVER_OK
> before using devices. While rpmsg isn't yet
> included in the virtio 1 spec, previous spec versions
> also required this.
>
> virtio rpmsg violates this rule: is calls kick
> before setting DRIVER_OK.
>
> The fix
"Michael S. Tsirkin" writes:
> On Thu, Mar 05, 2015 at 01:24:47PM +1030, Rusty Russell wrote:
>> "Michael S. Tsirkin" writes:
>> > virtio spec requires that all drivers set DRIVER_OK
>> > before using devices. While balloon isn't yet
>> > included in the virtio 1 spec, previous spec versions
>> >
return type of wait_for_completion_timeout is unsigned long not int. An
appropriately named unsigned long is added and the assignment fixed up.
Signed-off-by: Nicholas Mc Guire
---
This was only compile tested for tegra_defconfig
(implies CONFIG_ARCH_TEGRA_2x_SOC=y)
Patch is against 4.0-rc2 li
On 07/03/15 15:00, Mark Brown wrote:
On Thu, Mar 05, 2015 at 09:45:41AM +, Srinivas Kandagatla wrote:
+
+ return eeprom;
+}
+EXPORT_SYMBOL(eeprom_register);
This framework uses regmap but regmap is EXPORT_SYMBOL_GPL() and this is
using EXPORT_SYMBOL().
Thanks for spotting this,
On Sun, 2015-03-08 at 20:01 +, Mark Brown wrote:
> On Fri, Mar 06, 2015 at 05:45:15PM +0200, Ivan T. Ivanov wrote:
>
> > if (spi->master->setup)
> > status = spi->master->setup(spi);
> > + else
> > + spi_set_cs(spi, false);
>
> Why would this be co
Hi Joe,
Thank you for the patch.
On Sunday 08 March 2015 12:15:56 Joe Perches wrote:
> commit 2378ad1228d2 ("drm: rcar-du: Remove platform data support")
> removed the file, remove the pattern.
>
> Signed-off-by: Joe Perches
> cc: Laurent Pinchart
Acked-by: Laurent Pinchart
Should I take th
On Mon, Mar 9, 2015 at 12:42 PM, Yakir Yang wrote:
> - const struct dw_hdmi_mpll_config *mpll_config =
> -hdmi->plat_data->mpll_cfg;
> - const struct dw_hdmi_curr_ctrl *curr_ctrl = hdmi->plat_data->cur_ctr;
> - const struct dw_hdmi_sym_term *sym_term = hdmi
I am having a PCIe device , it asserts two types if Tx interrupts i.e.
TX Queue count interrupt & TX Queue timer interrupt.
TX Queue count interrupt related to “TX Queue count register” : No. of
TXQ transactions to move from host before asserting TX Queue count
interrupt
TX Queue timer interrupt
1001 - 1074 of 1074 matches
Mail list logo