2014-10-22 12:29 GMT+02:00 Joe.C :
> From: "Joe.C"
>
> This adds a basic dtsi for MT8135 based SoC.
>
> Signed-off-by: Joe.C
> ---
> arch/arm/boot/dts/mt8135.dtsi | 115
> ++
> arch/arm/mach-mediatek/mediatek.c | 1 +
> 2 files changed, 116
Hi,
On Mon, Oct 27, 2014 at 08:55:07AM -0700, Guenter Roeck wrote:
> Various drivers implement architecture and/or device specific means to
> remove power from the system. For the most part, those drivers set the
> global variable pm_power_off to point to a function within the driver.
>
> This
On Mon, Oct 27, 2014 at 08:55:23AM -0700, Guenter Roeck wrote:
> Register with kernel power-off handler instead of setting pm_power_off
> directly. Register with low priority to reflect that the original code
> only sets pm_power_off if it was not already set.
>
> Cc: Samuel Ortiz
> Cc: Lee
2014-10-22 12:29 GMT+02:00 Joe.C :
> From: "Joe.C"
>
> Evbp1 is a tablet evaluation board based on MT8135 SoC.
>
> Signed-off-by: Joe.C
> ---
> arch/arm/boot/dts/mt8135-evbp1.dts | 24
> 1 file changed, 24 insertions(+)
> create mode 100644
On Mon, Oct 27, 2014 at 08:55:24AM -0700, Guenter Roeck wrote:
> Register with kernel power-off handler instead of setting pm_power_off
> directly. Register with low priority to reflect that the original code
> only sets pm_power_off if it was not already set.
>
> Cc: Samuel Ortiz
> Cc: Lee
On Mon, 27 Oct 2014, Guenter Roeck wrote:
> Register with kernel power-off handler instead of setting pm_power_off
> directly. Register with low priority to reflect that the original code
> only sets pm_power_off if it was not already set.
>
> Cc: Lee Jones
> Cc: Samuel Ortiz
> Signed-off-by:
Hi,
On Mon, Nov 03, 2014 at 05:54:27PM +, Lee Jones wrote:
> On Mon, 27 Oct 2014, Guenter Roeck wrote:
>
> > Register with kernel power-off handler instead of setting pm_power_off
> > directly. Register with low priority to reflect that the original code
> > only sets pm_power_off if it was
On Mon, 27 Oct 2014, Guenter Roeck wrote:
> Register with kernel power-off handler instead of setting pm_power_off
> directly. Register with a low priority value of 64 to reflect that
> the original code only sets pm_power_off if it was not already set.
>
> Cc: Lee Jones
> Cc: Samuel Ortiz
>
On Sat, Nov 01, 2014 at 05:01:30PM +, Linus Torvalds wrote:
> On Wed, Oct 29, 2014 at 2:27 PM, Benjamin Herrenschmidt
> wrote:
> >
> > TLB flushing is only me I think, I'll engage my brain after breakfast
> > and see if is all good
>
> Ping? Breakfast is either long over, of you're starting
On Mon, 27 Oct 2014, Guenter Roeck wrote:
> Register with kernel power-off handler instead of setting pm_power_off
> directly. Register with low priority to reflect that the original code
> only sets pm_power_off if it was not already set.
>
> sysctrl_dev is set prior to power-off handler
On Mon, 27 Oct 2014, Guenter Roeck wrote:
> Register with kernel power-off handler instead of setting pm_power_off
> directly. Register with low priority to reflect that the original code
> only sets pm_power_off if it was not already set.
>
> Note that this patch fixes a problem on driver
On Mon, 27 Oct 2014, Guenter Roeck wrote:
> Register with kernel power-off handler instead of setting pm_power_off
> directly. Register with low priority to reflect that the original code
> only sets pm_power_off if it was not already set.
>
> Cc: Samuel Ortiz
> Cc: Lee Jones
> Signed-off-by:
On Mon, 27 Oct 2014, Guenter Roeck wrote:
> Register with kernel power-off handler instead of setting pm_power_off
> directly. Register with low priority to reflect that the original code
> only sets pm_power_off if it was not already set.
>
> Cc: Samuel Ortiz
> Cc: Lee Jones
> Signed-off-by:
2014-10-22 12:29 GMT+02:00 Joe.C :
> From: "Joe.C"
>
> Moose is a tablet evalutation board based on MT8127 SoC.
>
> Signed-off-by: Joe.C
> ---
> arch/arm/boot/dts/mt8127-moose.dts | 24
> 1 file changed, 24 insertions(+)
> create mode 100644
On Mon, 27 Oct 2014, Guenter Roeck wrote:
> Register with kernel power-off handler instead of setting pm_power_off
> directly. Register with low priority to reflect that the original code
> only sets pm_power_off if it was not already set.
>
> Cc: Samuel Ortiz
> Cc: Lee Jones
> Signed-off-by:
On Mon, 27 Oct 2014, Guenter Roeck wrote:
> Register with kernel power-off handler instead of setting pm_power_off
> directly. Register with low priority to reflect that the original code
> only sets pm_power_off if it was not already set.
>
> Make twl4030_power_off static as it is only called
On Mon, 27 Oct 2014, Guenter Roeck wrote:
> Register with kernel power-off handler instead of setting pm_power_off
> directly. Register with low priority to reflect that the original code
> only sets pm_power_off if it was not already set.
>
> Cc: Beniamino Galvani
> Signed-off-by: Guenter
On Mon, 27 Oct 2014, Guenter Roeck wrote:
> Register with kernel power-off handler instead of setting pm_power_off
> directly. Register with low priority to reflect that the original code
> only sets pm_power_off if it was not already set.
>
> Cc: Samuel Ortiz
> Cc: Lee Jones
> Signed-off-by:
Arnd, Olof, Kevin,
The pull-request that was sent late for 3.18. It was removing the old
!MMU at91x40 and 2 board files plus the whole code in at91sam9g45 & at91sam9rl
files for implementing this deprecated method. For these particular ones, the
EK were the only one to use this code.
We can use
On Mon, 27 Oct 2014, Guenter Roeck wrote:
> Register with kernel power-off handler instead of setting pm_power_off
> directly. Register with low priority to reflect that the original code
> only sets pm_power_off if it was not already set.
>
> Cc: Samuel Ortiz
> Cc: Lee Jones
> Signed-off-by:
On Mon, 27 Oct 2014, Guenter Roeck wrote:
> Register with kernel power-off handler instead of setting pm_power_off
> directly. Register with low priority to reflect that the original code
> only sets pm_power_off if it was not already set.
>
> Cc: Chris Zhong
> Cc: Zhang Qing
> Signed-off-by:
2014-10-22 12:29 GMT+02:00 Joe.C :
> From: "Joe.C"
>
> This adds a basic dtsi for MT8127 SoC.
>
> Signed-off-by: Joe.C
> ---
> arch/arm/boot/dts/mt8127.dtsi | 93
> +++
> arch/arm/mach-mediatek/mediatek.c | 1 +
> 2 files changed, 94 insertions(+)
>
On 11/3/2014 11:05 AM, Aravind Gopalakrishnan wrote:
There are three ways that have been used to report machine check event.
And they are MCE, CMCI/Threshold Interrupt, and POLL. On the Intel
platform, CMCI/Threshold Interrupt and POLL share the same event handler
- machine_check_poll().
2014-10-31 15:53 GMT+01:00 Matthias Brugger :
> Hi Joe,
>
> 2014-10-31 2:37 GMT+01:00 Yingjoe Chen :
>> Hi Matthias,
>>
>> Is this series + this new 8/8 patch OK?
>> Anything else that I should change?
>>
>
> I checked the patches on my mt8135 board and they work for me. So from
> my site
On Mon, 2014-11-03 at 11:46 -0500, Jonathan Corbet wrote:
> On Wed, 29 Oct 2014 11:15:17 -0700
> Josh Triplett wrote:
>
> > Document several common practices and conventions regarding conditional
> > compilation, most notably the preference for ifdefs in headers rather
> > than .c files.
>
>
On 3-11-2014 16:10, Mark Brown wrote:
On Mon, Nov 03, 2014 at 03:48:56PM +0100, Mike Looijmans wrote:
On 11/03/2014 01:09 PM, Mark Brown wrote:
No function calls, just use regulators_node. What is unclear about the
functionality?
I don't understand what you mean by "regulators_node".
W dniu 2014-09-27 o 22:01, Mike Turquette pisze:
Quoting Thierry Reding (2014-09-23 01:51:31)
On Wed, Sep 10, 2014 at 10:05:17PM +0200, Janusz Użycki wrote:
Hi,
http://patchwork.ozlabs.org/patch/359069/
https://lkml.org/lkml/2014/6/12/186
Will the patch ever included to linux-next?
I've
On Mon, Nov 03, 2014 at 11:11:18AM +0100, Andre' Bauer wrote:
> Hi Guys,
>
> whats the status of the inclusion of this patch?
>
> Regards
>
> Andr? Bauer
>
> Am 15.02.2013 um 07:02 schrieb OS Engineering:
Responding to an almost 2 year old email?
Heck, I have no idea what happened yesterday,
On 03/11/2014 13:33, Maxime Ripard :
> Hi Nicolas,
>
> On Mon, Nov 03, 2014 at 12:12:44PM +0100, Nicolas Ferre wrote:
>> On 28/10/2014 22:25, Maxime Ripard :
>>> We are removing the dmaengine_device_control API, that shouldn't even have
>>> been
>>> exposed in the first place. Change the callers
Hi Thomas,
On 24/10/2014 13:59, Thomas Petazzoni wrote:
> This commit adds a set of suspend/resume syscore_ops to respectively
> save and restore a number of timer registers, in order to make sure
> the clockevent and clocksource devices continue to work properly
> accross a suspend/resume cycle.
On Mon, 2014-11-03 at 22:22 +0530, Sudip Mukherjee wrote:
> On Mon, Nov 03, 2014 at 07:08:08AM -0800, Joe Perches wrote:
[]
> > ftrace exists and is generic.
> >
> > Several of these seem to be function tracing
> > style uses and should just be deleted instead.
>
> function tracing style uses
Arnd, Olof, Kevin,
Very little DT update for AT91. More will come but I want to send this first
batch soon so it doesn't get in the way of larger modifications.
Thanks, best regards,
The following changes since commit cac7f2429872d3733dc3f9915857b1691da2eb2f:
Linux 3.18-rc2 (2014-10-26
> If you can benchmark the code and the new code is faster then, yes, this
> patch is good and we will apply it.
I guess that I do not have enough resources myself to measure different run time
effects in a S390 environment.
> If you have no benchmarks then do not send the patch.
Are other
On some 32 bits architectures, including x86, GENMASK(31, 0) returns 0
instead of the expected ~0UL.
This is the same on some 64 bits architectures with GENMASK_ULL(63, 0).
This is due to an overflow in the shift operand, 1 << 32 for GENMASK,
1 << 64 for GENMASK_ULL.
Fixes:
On Mon, Nov 03, 2014 at 12:12:18PM -0500, Vince Weaver wrote:
> I don't know if having an offset/mask helps much. Knowing your EINVAL
> comes from ->config is nice to know, but if there's 30 different ways
> to get an EINVAL from an improper config then you still can waste a lot
> of time
Hi Thomas,
On 24/10/2014 13:59, Thomas Petazzoni wrote:
> This commit adds suspend/resume support to the irqchip driver used on
> Armada XP platforms (amongst others). It does so by adding a set of
> suspend/resume syscore_ops, that will respectively save and restore
> the necessary registers to
On Mon, Nov 3, 2014 at 3:42 PM, Andy Lutomirski wrote:
> On Mon, Nov 3, 2014 at 7:20 AM, Al Viro wrote:
>> On Mon, Nov 03, 2014 at 11:48:23AM +, David Drysdale wrote:
>>> Add a new O_BENEATH flag for openat(2) which restricts the
>>> provided path, rejecting (with -EACCES) paths that are not
MFD core already cares about failing registration. It will remove successfully
registered devices in case of error. Thus, no need to repeatedly call
mfd_remove_devices().
Fixes: 5829e9b64e65 (mfd: lpc_sch: Accomodate partial population of the MFD
devices)
Signed-off-by: Andy Shevchenko
---
On Sat, Nov 01, 2014 at 11:15:56PM -0400, Johannes Weiner wrote:
> Now that the external page_cgroup data structure and its lookup is
> gone, let the generic bad_page() check for page->mem_cgroup sanity.
>
> Signed-off-by: Johannes Weiner
Acked-by: Vladimir Davydov
--
To unsubscribe from this
On Sat, Nov 01, 2014 at 11:15:55PM -0400, Johannes Weiner wrote:
> Now that the external page_cgroup data structure and its lookup is
> gone, the only code remaining in there is swap slot accounting.
>
> Rename it and move the conditional compilation into mm/Makefile.
>
> Signed-off-by: Johannes
On Sat, Nov 01, 2014 at 11:15:54PM -0400, Johannes Weiner wrote:
> Memory cgroups used to have 5 per-page pointers. To allow users to
> disable that amount of overhead during runtime, those pointers were
> allocated in a separate array, with a translation layer between them
> and struct page.
>
On November 3, 2014 7:42:58 AM PST, Andy Lutomirski wrote:
>On Mon, Nov 3, 2014 at 7:20 AM, Al Viro
>wrote:
>> On Mon, Nov 03, 2014 at 11:48:23AM +, David Drysdale wrote:
>>> Add a new O_BENEATH flag for openat(2) which restricts the
>>> provided path, rejecting (with -EACCES) paths that
Hi Thomas,
On 24/10/2014 13:59, Thomas Petazzoni wrote:
> The ->set_affinity() hook of 'struct irq_chip' is supposed to return
> one of IRQ_SET_MASK_OK or IRQ_SET_MASK_OK_NOCOPY. However, the code
> currently simply returns 0. This patch fixes that by using
> IRQ_SET_MASK_OK, which tells the IRQ
On Mon, Nov 3, 2014 at 9:15 AM, Seth Forshee wrote:
> On Wed, Oct 22, 2014 at 04:24:16PM -0500, Seth Forshee wrote:
>> Here's another update to the patches to enable userns mounts in fuse.
>> The changes this time around center on xattrs and allow_other. I'm
>> considering the following patch to
Russell King - ARM Linux writes:
[...]
> Would another possible solution be to remember the irq-safeness in the
> suspend handler, and use that in the resume handler? Resume should
> /always/ undo what the suspend handler previously did wrt clk API stuff.
This seems more reasonable to me.
On Mon, Nov 03, 2014 at 05:50:48PM +0100, SF Markus Elfring wrote:
> > After your patch then it will print warning messages.
>
> To which messages do you refer to?
>
Open your eyeballs up and read the code.
>
> > The truth is I think that all these patches are bad and they make the
> > code
Documentation/cgroups/memory.txt is outdate even more hopelessly than
before. It deserves a complete rewrite but I guess something like the
following should be added in the meantime to prepare potential readers
about the trap.
---
diff --git a/Documentation/cgroups/memory.txt
On Wed, 29 Oct 2014, Heiko Stübner wrote:
> Drivers may want to search for an optional backlight even when the backlight
> class is disabled. In this case the linker would miss the function referenced
> in the backlight header.
>
> Therefore use the stub function also when the backlight class is
Hi,
Am 03.11.2014 um 15:43 schrieb Kamil Debski:
> Add pwm-fan node to the Odroid-U3 board file to enable PWM control of the
> cooling fan.
>
> Signed-off-by: Kamil Debski
> ---
> arch/arm/boot/dts/exynos4412-odroidu3.dts | 13 +
> 1 file changed, 13 insertions(+)
>
> diff --git
On Fri, 31 Oct 2014, gyun...@gmail.com wrote:
> From: Gyungoh Yoo
>
> Signed-off-by: Gyungoh Yoo
> ---
> Changes v6:
> Added new line character at the end of line of dev_err()
>
> Changes v5:
> Move sky81452-backlight.h to include/linux/platform_data
>
> Changes v4:
> Removed
On Mon, 27 Oct 2014, Toshi Kani wrote:
> + } else {
> + /*
> + * PAT full support. WT is set to slot 7, which minimizes
> + * the risk of using the PAT bit as slot 3 is UC and is
> + * currently unused. Slot 4 should remain as reserved.
This
On Wed, Oct 22, 2014 at 04:24:16PM -0500, Seth Forshee wrote:
> Here's another update to the patches to enable userns mounts in fuse.
> The changes this time around center on xattrs and allow_other. I'm
> considering the following patch to be a prerequisite for this series:
>
>
Boris Ostrovsky writes:
> On 11/03/2014 07:22 AM, Laszlo Ersek wrote:
>> On 10/27/14 14:44, Vitaly Kuznetsov wrote:
>>> Guard against issuing unsupported REQ_FUA and REQ_FLUSH was introduced
>>> in d11e61583 and was factored out into blkif_request_flush_valid() in
>>> 0f1ca65ee. However:
>>> 1)
On 10/30/2014 06:35 AM, Russell King - ARM Linux wrote:
> On Thu, Oct 30, 2014 at 07:30:28AM -0400, Steven Rostedt wrote:
>> On Thu, 30 Oct 2014 11:14:41 +
>> Russell King - ARM Linux wrote:
>>
>>
>>> We have always had syscall number range of 0x90 or so. The tracing
>>> design does not
On Mon, 3 Nov 2014, Arnaldo Carvalho de Melo wrote:
> Em Mon, Nov 03, 2014 at 05:50:19PM +0100, Peter Zijlstra escreveu:
> > On Mon, Nov 03, 2014 at 02:25:48PM -0200, Arnaldo Carvalho de Melo wrote:
>
> > > The way that peterz suggested, i.e. returning information about which
> > >
On Mon, Nov 3, 2014 at 3:15 AM, Mark Rutland wrote:
> On Sat, Nov 01, 2014 at 11:35:31PM +, Bjorn Helgaas wrote:
>> a9ecdc0fdc54 ("of/irq: Fix lookup to use 'interrupts-extended' property
>> first") updated the description to say that:
>>
>> - Both 'interrupts' and 'interrupts-extended' may
On Fri, 31 Oct 2014, gyun...@gmail.com wrote:
> From: Gyungoh Yoo
>
> Signed-off-by: Gyungoh Yoo
> ---
> Changes v6:
> Nothing
>
> Changes v5:
> Nothing
>
> Changes v4:
> Nothing
>
> Changes v3:
> Nothing
>
> Changes v2:
> Added vendor prefix for Skyworks Solutions, Inc.
>
>
On Mon, Nov 3, 2014 at 4:00 AM, Simon McVittie
wrote:
> On 01/11/14 16:19, Andy Lutomirski wrote:
>> You can't justify logging fundamentally unverifiable things like the
>> command line by saying that you want to know if someone tries to play
>> (impossible-to-reliably-detect) games to obscure
Having test_pages_isolated failure message as a warning confuses
users into thinking that it is more serious than it really is. In
reality, if called via CMA, allocation will be retried so a single
test_pages_isolated failure does not prevent allocation from
succeeding.
Demote the warning
On Nov 3, 2014 12:34 AM, "Christoph Hellwig" wrote:
>
> On Fri, Oct 31, 2014 at 11:53:09AM -0700, Linus Torvalds wrote:
> > On Fri, Oct 31, 2014 at 11:44 AM, Andy Lutomirski
> > wrote:
> > >
> > > Does the patch in this thread not fix that?
> >
> > It should. Modulo the glibc problem that makes
Kever,
On Sat, Nov 1, 2014 at 5:44 AM, Kever Yang wrote:
> - COMPOSITE(SCLK_EMMC, "sclk_emmc", mux_mmc_src_p, 0,
> + COMPOSITE(SCLK_EMMC, "sclk_emmc", mux_mmc_src_p, CLK_IGNORE_UNUSED,
Is there a reason why this is needed? I took it out (AKA let eMMC get
disabled when unused) and
On Mon, Nov 3, 2014 at 12:34 AM, Christoph Hellwig wrote:
>
> That doesn't help because we explicitly reject O_RDONLY when combined
> with O_TMPFILE.
You obviously cannot actually have a read-only file descriptor with
O_TMPFILE, unless all you care about is a zero-sized file with no
contents.
On Fri, 31 Oct 2014, gyun...@gmail.com wrote:
> From: Gyungoh Yoo
>
> Signed-off-by: Gyungoh Yoo
> ---
> Changes v6:
> Nothing
>
> Changes v5:
> Changed DT for regulator : 'lout' node should be defined under 'regulator'
> Removed compatible string from sky81452-regulator driver
>
> Changes
On Mon, Nov 03, 2014 at 09:57:28PM +0530, Vinod Koul wrote:
> On Sat, Nov 01, 2014 at 02:29:42AM +0200, Laurent Pinchart wrote:
> > Many other drivers suffer from the same problem. While I won't reject your
> > proposed fix, I would prefer a more generic approach.
> >
> > One option that has
Em Mon, Nov 03, 2014 at 05:50:19PM +0100, Peter Zijlstra escreveu:
> On Mon, Nov 03, 2014 at 02:25:48PM -0200, Arnaldo Carvalho de Melo wrote:
> > The way that peterz suggested, i.e. returning information about which
> > perf_event_attr and which of the parameters was invalid/had issues could
>
From: Morten Rasmussen
Apply frequency scale-invariance correction factor to usage tracking.
Each segment of the running_load_avg geometric series is now scaled by the
current frequency so the utilization_avg_contrib of each entity will be
invariant with frequency scaling. As a result,
On Thu, 30 Oct 2014, Krzysztof Kozlowski wrote:
> The driver is used only on Exynos based boards with DTS support.
> Convert the driver to DTS-only version. This simplifies a little the
> code:
> 1. No dead (unused) entries in platform_data structure.
> 2. More code removed.
> 3. Regulator driver
Building with the attached random configuration file,
ERROR: "spi_setup" [sound/soc/codecs/snd-soc-tlv320aic23-spi.ko] undefined!
ERROR: "devm_regmap_init_spi"
[sound/soc/codecs/snd-soc-tlv320aic23-spi.ko] undefined!
ERROR: "spi_register_driver"
[sound/soc/codecs/snd-soc-tlv320aic23-spi.ko]
On Mon 03-11-14 10:09:42, Johannes Weiner wrote:
> Hi Joonsoo,
>
> On Mon, Nov 03, 2014 at 05:02:08PM +0900, Joonsoo Kim wrote:
> > On Sat, Nov 01, 2014 at 11:15:54PM -0400, Johannes Weiner wrote:
> > > Memory cgroups used to have 5 per-page pointers. To allow users to
> > > disable that amount
> > After your patch then it will print warning messages.
> > After: You have to remember that rtw_free_netdev() accepts NULL
> > pointers but free_netdev() does not accept NULL pointers.
>
> Are any improvements needed for the corresponding documentation to make it
> better accessible
The scheduler tries to compute how many tasks a group of CPUs can handle by
assuming that a task's load is SCHED_LOAD_SCALE and a CPU's capacity is
SCHED_CAPACITY_SCALE. group_capacity_factor divides the capacity of the group
by SCHED_LOAD_SCALE to estimate how many task can run in the group.
On Thu, 30 Oct 2014, Krzysztof Kozlowski wrote:
> Document new required property for regulator driver: of_compatible. The
> property allows MFD core to bind the driver to node with regulators and
> this simplifies parsing regulators init data from DTS
>
> Signed-off-by: Krzysztof Kozlowski
>
Hi Vinod,
On Monday 03 November 2014 21:57:28 Vinod Koul wrote:
> On Sat, Nov 01, 2014 at 02:29:42AM +0200, Laurent Pinchart wrote:
> > On Friday 31 October 2014 15:40:16 Krzysztof Kozlowski wrote:
> >> On pią, 2014-10-31 at 15:22 +0100, Pavel Machek wrote:
> >>> On Fri 2014-10-31 10:14:55,
From: Morten Rasmussen
Adds usage contribution tracking for group entities. Unlike
se->avg.load_avg_contrib, se->avg.utilization_avg_contrib for group
entities is the sum of se->avg.utilization_avg_contrib for all entities on the
group runqueue. It is _not_ influenced in any way by the task
On Sat 01-11-14 23:15:56, Johannes Weiner wrote:
> Now that the external page_cgroup data structure and its lookup is
> gone, let the generic bad_page() check for page->mem_cgroup sanity.
>
> Signed-off-by: Johannes Weiner
Acked-by: Michal Hocko
> ---
> include/linux/memcontrol.h | 4
>
On Sat 01-11-14 23:15:55, Johannes Weiner wrote:
> Now that the external page_cgroup data structure and its lookup is
> gone, the only code remaining in there is swap slot accounting.
>
> Rename it and move the conditional compilation into mm/Makefile.
>
> Signed-off-by: Johannes Weiner
Now that arch_scale_cpu_capacity has been introduced to scale the original
capacity, the arch_scale_freq_capacity is no longer used (it was
previously used by ARM arch). Remove arch_scale_freq_capacity from the
computation of cpu_capacity. The frequency invariance will be handled in the
load
When a CPU is used to handle a lot of IRQs or some RT tasks, the remaining
capacity for CFS tasks can be significantly reduced. Once we detect such
situation by comparing cpu_capacity_orig and cpu_capacity, we trig an idle
load balance to check if it's worth moving its tasks on an idle CPU.
Once
On Mon, 2014-11-03 at 14:01 +0100, Juergen Gross wrote:
> The x86 architecture offers via the PAT (Page Attribute Table) a way to
> specify different caching modes in page table entries. The PAT MSR contains
> 8 entries each specifying one of 6 possible cache modes. A pte references one
> of those
Add the SD_PREFER_SIBLING flag for SMT level in order to ensure that
the scheduler will put at least 1 task per core.
Signed-off-by: Vincent Guittot
Reviewed-by: Preeti U. Murthy
---
kernel/sched/core.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/sched/core.c
Monitor the usage level of each group of each sched_domain level. The usage is
the portion of cpu_capacity_orig that is currently used on a CPU or group of
CPUs. We use the utilization_load_avg to evaluate the usage level of each
group.
The utilization_load_avg only takes into account the running
This new field cpu_capacity_orig reflects the original capacity of a CPU
before being altered by rt tasks and/or IRQ
The cpu_capacity_orig will be used:
- to detect when the capacity of a CPU has been noticeably reduced so we can
trig load balance to look for a CPU with better capacity. As an
The average running time of RT tasks is used to estimate the remaining compute
capacity for CFS tasks. This remaining capacity is the original capacity scaled
down by a factor (aka scale_rt_capacity). This estimation of available capacity
must also be invariant with frequency scaling.
A frequency
Add new statistics which reflect the average time a task is running on the CPU
and the sum of these running time of the tasks on a runqueue. The latter is
named utilization_load_avg.
This patch is based on the usage metric that was proposed in the 1st
versions of the per-entity load tracking
This patchset consolidates several changes in the capacity and the usage
tracking of the CPU. It provides a frequency invariant metric of the usage of
CPUs and generally improves the accuracy of load/usage tracking in the
scheduler. The frequency invariant metric is the foundation required for the
On Wed, 22 Oct 2014 08:36:07 +0900
Masanari Iida wrote:
> This patch fix a typo in Documentation/mailbox.txt
> "bool async" is defined in struct demo_client.
>
> Signed-off-by: Masanari Iida
I've (finally) applied this one, thanks.
jon
--
To unsubscribe from this list: send the line
On Mon, Nov 03, 2014 at 07:08:08AM -0800, Joe Perches wrote:
> On Mon, 2014-11-03 at 15:17 +0100, Takashi Iwai wrote:
> > At Mon, 3 Nov 2014 16:04:12 +0530,
> > Sudip Mukherjee wrote:
> > >
> > > added reference of struct echoaudio to free_firmware function.
> > > this structure will be later
On Sat 01-11-14 23:15:54, Johannes Weiner wrote:
> Memory cgroups used to have 5 per-page pointers. To allow users to
> disable that amount of overhead during runtime, those pointers were
> allocated in a separate array, with a translation layer between them
> and struct page.
>
> There is now
> After your patch then it will print warning messages.
To which messages do you refer to?
> The truth is I think that all these patches are bad and they make the
> code harder to read.
>
> Before: The code is clear and there is no NULL dereference.
Where do you stumble on a null pointer
On Mon, 03 Nov 2014, Fabio Estevam wrote:
> On Mon, Nov 3, 2014 at 2:15 PM, Lee Jones wrote:
>
> > /* Clean up the mailbox interrupts after pre-kernel code. */
> > @@ -3179,15 +3179,14 @@ static int db8500_prcmu_probe(struct
> > platform_device *pdev)
> > irq =
On Mon, Nov 03, 2014 at 02:25:48PM -0200, Arnaldo Carvalho de Melo wrote:
> The way that peterz suggested, i.e. returning information about which
> perf_event_attr and which of the parameters was invalid/had issues could
> help with fallbacking/capability querying, i.e. tooling may want to use
>
Hi Jason,
On 01/11/2014 23:46, Jason Cooper wrote:
> Gregory,
>
> On Fri, Oct 24, 2014 at 05:24:08PM +0200, Gregory CLEMENT wrote:
>> Hello,
>>
>> this is the second version of a series I initially submitted in May:
>> https://lkml.org/lkml/2014/5/16/743
>>
>> This series adds support for the
On Wed, 29 Oct 2014 11:15:17 -0700
Josh Triplett wrote:
> Document several common practices and conventions regarding conditional
> compilation, most notably the preference for ifdefs in headers rather
> than .c files.
OK, I've picked this one up for my 3.19 docs pull.
Thanks,
jon
--
To
On Mon, Nov 03, 2014 at 03:27:48PM +, One Thousand Gnomes wrote:
> > > This isn't unreasonable but there are drivers with userspace helpers that
> > > use iopl/ioperm type functionality where you should be doing a SELECT of
> > > X86_IOPORT. The one that comes to mind is the uvesa driver. From
On Mon, 03 Nov 2014, Lee Jones wrote:
> On Thu, 30 Oct 2014, Pramod Gurav wrote:
>
> > Error check around return value of devm_ioremap is missing. Add the same
> > to avoid NULL pointer dereference.
> >
> > Cc: Linus Walleij
> > Cc: Samuel Ortiz
> > Cc: Lee Jones
> > Signed-off-by: Pramod
On Fri, Oct 31 2014, Florian Fainelli wrote:
> I agree that the CMA allocation should not be allowed to succeed, but
> the dma_alloc_coherent() allocation should succeed. If we look at the
> sysport driver, there are kmalloc() calls to initialize private
> structures, those will succeed (except
On Mon, 3 Nov 2014, Juergen Gross wrote:
> When modifying page attributes via change_page_attr_set_clr() don't
> test for setting _PAGE_PAT_LARGE, as this is
> - never done
> - PAT support for large pages is not included in the kernel up to now
>
> Signed-off-by: Juergen Gross
Reviewed-by:
On Mon, 03 Nov 2014 15:18:29 +0100
Stephan Mueller wrote:
> > These are all useful. But I wonder if it would be worth the effort to turn
> > this inti a proper docbook document that automatically has everything
> > together in one place?
>
> How do you suggest that is done?
See
Add support for Google devices that export simple serial
interfaces using the vendor specific SubClass/Protocol pair
0x50/0x01.
Signed-off-by: Anton Staaf
---
drivers/usb/serial/usb-serial-simple.c | 10 ++
1 file changed, 10 insertions(+)
diff --git
From: Johannes Weiner
Date: Mon, 3 Nov 2014 10:09:42 -0500
> Please re-introduce this code when your new usecase is ready to be
> upstreamed. There is little reason to burden an unrelated feature
> with a sizable chunk of dead code for a vague future user.
+1
--
To unsubscribe from this list:
501 - 600 of 2138 matches
Mail list logo
