On Wed, 4 Feb 2015, Andrew G. Morgan wrote:
> I was thinking more like this:
>
> int override = secure(SECURE_AMBIENT_PRIVS) &&
> cap_isclear(caps->inheritable.cap);
Uhh.. Then processes that require other capabilties would not pass
them through anymore to other stuff that they invoke.
Also
On Mon, Feb 02, 2015 at 12:45:39PM +, Hanjun Guo wrote:
> From: Graeme Gregory
>
> There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set,
> the former signals to the OS that the firmware is PSCI compliant.
> The latter selects the appropriate conduit for PSCI calls by
> toggling betw
On śro, 2015-02-04 at 08:28 -0800, Paul E. McKenney wrote:
> On Wed, Feb 04, 2015 at 05:10:56PM +0100, Krzysztof Kozlowski wrote:
> > On śro, 2015-02-04 at 07:56 -0800, Paul E. McKenney wrote:
> > > On Wed, Feb 04, 2015 at 04:22:28PM +0100, Krzysztof Kozlowski wrote:
> > > >
> > > > Actually the t
On Wed, Feb 04, 2015 at 05:33:36PM +0100, Peter Zijlstra wrote:
> On Wed, Feb 04, 2015 at 03:51:36PM +0100, Jiri Olsa wrote:
> > On Mon, Feb 02, 2015 at 06:32:32PM +0100, Peter Zijlstra wrote:
> > > > That looks like tail recursive fun! An irq work that raises and irq work
> > > > ad infinitum. Lem
Am 04.02.2015 um 17:25 schrieb Lukáš Czerner:
On Wed, 4 Feb 2015, Alexander Holler wrote:
Am 04.02.2015 um 15:52 schrieb Lukáš Czerner:
On Wed, 4 Feb 2015, Alexander Holler wrote:
I'm happy for all the feedback. But it doesn't help me. I'm not going to spend
the necessary time unpaid.
Ri
From: Markus Elfring
Date: Wed, 4 Feb 2015 17:31:00 +0100
Another update suggestion was taken into account after a patch was applied
from static source code analysis.
Markus Elfring (2):
Delete an unnecessary check before the function call "release_firmware"
Less function calls in cw1200_loa
Gets a handle to the system clock, already described in the binding
document, and calls the appropriate common clock framework functions
to mark it prepared/enabled, the common clock framework initially
enables the clock and doesn't disable it at least until the
device/driver is removed.
It's impor
From: Markus Elfring
Date: Wed, 4 Feb 2015 16:32:15 +0100
The release_firmware() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
d
On Wed, Feb 04, 2015 at 03:21:29PM +, Zubair Lutfullah Kakakhel wrote:
> Hi,
>
> This series introduces initial support for the Ingenic jz4780 SoC & the
> MIPS Creator CI20 board which is based upon it.
>
> The jz4780 shares aspects with jz4740. But jz4740 is platform only.
>
> So, the jz474
From: Markus Elfring
Date: Wed, 4 Feb 2015 17:28:41 +0100
The functions kfree() and release_firmware() were called in a few cases
by the cw1200_load_firmware_cw1200() function during error handling even if
the passed variables contained still a null pointer.
Corresponding implementation details
We may optimize __wait_for_common() in case of it's waken up
by complete{,_all}() if we do not take the spinlock.
New function completion_wake_function() is now used to wake
waiters. It a case of successful waking it deletes a waiter
from the task list. The waiter checks wait.task_list and skips
On Wed, Feb 4, 2015 at 9:23 AM, Fabio Estevam wrote:
> Rob,
>
> On Wed, Feb 4, 2015 at 12:55 PM, Rob Herring wrote:
>
>> I'm surprised there are not already compatible strings with
>> OmniVision. There are some examples using "omnivision", but no dts
>> files and examples don't count.
>>
>> The s
Am 04.02.2015 um 17:45 schrieb Alexander Holler:
Am 04.02.2015 um 17:25 schrieb Lukáš Czerner:
On Wed, 4 Feb 2015, Alexander Holler wrote:
Am 04.02.2015 um 15:52 schrieb Lukáš Czerner:
On Wed, 4 Feb 2015, Alexander Holler wrote:
I'm happy for all the feedback. But it doesn't help me. I'm
If permitted is zero (ie., no file capabilities) then I don't think
this will yield any privilege for such an exec. Perhaps I missed
something prior to being included in the thread, but I was under the
impression that this was a case where it was intended that
capabilities would be inherited..?
If
The complete() should not be used on offlined CPU. Rewrite the
wait-complete mechanism with wait_on_bit_timeout().
The CPU triggering hot unplug (e.g. CPU0) will loop until some bit is
cleared. In each iteration schedule_timeout() is used with initial sleep
time of 1 ms. Later it is increased to
On 02/04/2015 02:13 AM, Tomeu Vizoso wrote:
On 02/03/2015 05:35 PM, Stephen Warren wrote:
On 02/03/2015 06:13 AM, Tomeu Vizoso wrote:
On 2 February 2015 at 22:08, Stephen Warren wrote:
On 01/28/2015 03:50 AM, Tomeu Vizoso wrote:
Patches are on its way to add a config file to alsaucm for the
On 02/04/2015 03:00 PM, Michael Kerrisk (man-pages) wrote:
Hello Vlastimil,
On 4 February 2015 at 14:46, Vlastimil Babka wrote:
- that covers mlocking ok, not sure if the rest fits the "shared pages"
case
though. I dont see any check for other kinds of shared pages in the code.
Agreed. "shar
Hi Prabhakar,
Thank you for the patch. Here's a partial review.
On Thursday 15 January 2015 23:39:23 Lad, Prabhakar wrote:
> From: Benoit Parrot
>
> this patch adds support for omnivision's ov2659
> sensor.
>
> Signed-off-by: Benoit Parrot
> Signed-off-by: Lad, Prabhakar
> ---
> .../devicet
Hello.
On 02/04/2015 06:21 PM, Zubair Lutfullah Kakakhel wrote:
From: Paul Burton
Use the generic irqchip_init function to probe irqchip drivers using DT,
and add the appropriate node to the jz4740 devicetree in place of the
call to mips_cpu_irq_init.
Signed-off-by: Paul Burton
Cc: Lars
On 02/04/2015 03:18 AM, Peter Zijlstra wrote:
On Tue, Feb 03, 2015 at 04:24:55PM -0700, Jens Axboe wrote:
Yes, from a cursory look, that seems fine to me. Though I will hold the fact
that you label my code as 'seriously obtuse' against you. Some day.
Hehe, fair enough. I'm sure I've written m
Some utils, like dmidecode and smbios, need to access SMBIOS entry
table area in order to get information like SMBIOS version, size, etc.
Currently it's done via /dev/mem. But for situation when /dev/mem
usage is disabled, the utils have to use dmi sysfs instead, which
doesn't represent SMBIOS entr
Hello,
On Tue, Feb 03, 2015 at 03:30:31PM -0800, Greg Thelen wrote:
> If a machine has several top level memcg trying to get some form of
> isolation (using low, min, soft limit) then a shared libc will be
> moved to the root memcg where it's not protected from global memory
> pressure. At least
needed and, as suggested, the misleading comment is completely removed.
Patch was only compile tested for x86_64_defconfig + CONFIG_STAGING=y
CONFIG_COMEDI=m, COMEDI_ISA_DRIVERS=y, CONFIG_COMEDI_DT282X=m
Patch is against 3.19.0-rc7 (localversion = -next-20150204)
drivers/staging/comedi/drivers
Hello.
On 02/04/2015 06:21 PM, Zubair Lutfullah Kakakhel wrote:
From: Paul Burton
Add binding documentation for the Ingenic jz4740 interrupt controller.
Signed-off-by: Paul Burton
Cc: Lars-Peter Clausen
Cc: devicet...@vger.kernel.org
---
.../interrupt-controller/ingenic,jz4740-intc.t
Hi Rob,
On Wed, Feb 4, 2015 at 5:14 PM, Rob Herring wrote:
> On Fri, Jan 23, 2015 at 10:10 AM, Geert Uytterhoeven
> wrote:
>> This patch series adds tests to detect reference count imbalances.
>> The tests use a fixed list of paths to devices nodes (required device
>> nodes in a minimal DTS, and
On Fri, 30 January 2015 Trond Myklebust wrote:
> On Sun, 2015-01-25 at 16:55 -0500, Trond Myklebust wrote:
> > On Sun, Jan 25, 2015 at 4:06 PM, Bruno Prémont wrote:
> > > On a system running home-brown container (mntns, utsns, pidns, netns)
> > > with NFS mount-point bind-mounted into the container
On Wed, Feb 04, 2015 at 03:17:25PM +, Ding Tianhong wrote:
> bad mode in Synchronous Abort handler detected, code 0x8605
> CPU: 1 PID: 381 Comm: kworker/1:1 Tainted: G O 3.19.0-rc4+ #6
> Hardware name: Hisilicon Board ESL (DT)
> Workqueue: events (null)
> task: ffc
On 02/04/2015 06:21 PM, Zubair Lutfullah Kakakhel wrote:
From: Paul Burton
Add the appropriate DT node to probe the interrupt controller driver
using the devicetree, and remove the call to jz4740_intc_init.
Signed-off-by: Paul Burton
Cc: Lars-Peter Clausen
---
arch/mips/boot/dts/jz474
variable 'done' is only used for true/false in loop.
Signed-off-by: Fabian Frederick
---
fs/udf/super.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/udf/super.c b/fs/udf/super.c
index 3d35a75..f169411 100644
--- a/fs/udf/super.c
+++ b/fs/udf/super.c
@@ -1599,7 +1599
Hello,
On Wed, Feb 04, 2015 at 01:49:08PM +0300, Konstantin Khlebnikov wrote:
> I think important shared data must be handled and protected explicitly.
> That 'catch-all' shared container could be separated into several
I kinda disagree. That'd be a major pain in the ass to use and you
wouldn't
This patchset contains the initial GPIO/PINCONF support for the Broadcom
Cygnus SoC.
Cygnus has 3 GPIO controllers: 1) the ASIU GPIO; 2) the chipCommonG GPIO;
and 3) the ALWAYS-ON GPIO. All 3 types of GPIO controllers are supported by
the this driver.
All 3 Cygnus GPIO controllers support basic P
This enables all 3 GPIO controllers including the ASIU GPIO, the
chipcommonG GPIO, and the ALWAYS-ON GPIO, for Broadcom Cygnus SoC
Signed-off-by: Ray Jui
Reviewed-by: Scott Branden
---
arch/arm/boot/dts/bcm-cygnus.dtsi | 33 +
1 file changed, 33 insertions(+)
This enables GPIO based phone hook detection for Broadcom BCM911360
phone factor board (bcm911360_entphn)
Signed-off-by: Ray Jui
---
arch/arm/boot/dts/bcm911360_entphn.dts | 13 +
1 file changed, 13 insertions(+)
diff --git a/arch/arm/boot/dts/bcm911360_entphn.dts
b/arch/arm/boot
Document the GPIO/PINCONF device tree binding for Broadcom Cygnus SoC
Signed-off-by: Ray Jui
Reviewed-by: Scott Branden
---
.../bindings/pinctrl/brcm,cygnus-gpio.txt | 102
1 file changed, 102 insertions(+)
create mode 100644
Documentation/devicetree/bindings/pi
This adds the initial support of the Broadcom Cygnus GPIO/PINCONF driver
that supports all 3 GPIO controllers on Cygnus including the ASIU GPIO
controller, the chipCommonG GPIO controller, and the always-on GPIO
controller. Basic PINCONF configurations such as bias pull up/down, and
drive strength
Hi Greg,
Here's a big pull request for v3.20. All patches have been around
for quite a while. I have tested everything on AM437x SK, AM437x IDK,
AM335x BeagleBoneBlack and AM57x Beagleboard X15.
Let me know if you want me to change anything.
cheers
The following changes since commit ec6f34e5b55
On Wed, Feb 04, 2015 at 05:09:51PM +, Catalin Marinas wrote:
> On Wed, Feb 04, 2015 at 03:17:25PM +, Ding Tianhong wrote:
> > bad mode in Synchronous Abort handler detected, code 0x8605
> > CPU: 1 PID: 381 Comm: kworker/1:1 Tainted: G O 3.19.0-rc4+ #6
> > Hardware name: Hisi
Fix the following coccinelle warnings:
fs/udf/inode.c:753:2-13: WARNING: Assignment of bool to 0/1
fs/udf/inode.c:795:2-13: WARNING: Assignment of bool to 0/1
Signed-off-by: Fabian Frederick
---
fs/udf/inode.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/udf/inode.
On Wed, Feb 04, 2015 at 01:32:14PM +0100, Paul Bolle wrote:
> Andrey Skvortsov schreef op zo 01-02-2015 om 00:16 [+0300]:
> > this warning exist in v3.19-rc6 and does not in v3.18. Bisection
> > points to the commit 51e31d49c890552 "drm/i915: Use generic vblank wait".
> > I have two machines with i
-, current
crosstool-ng did not seem to build omap2 properly.
Config is omap2plus_defconfig which implies CONFIG_MTD_NAND_OMAP2=y.
Patch is against 3.19.0-rc7 (localversion-next is -next-20150204)
drivers/mtd/nand/omap2.c | 31 +--
1 file changed, 9 insertions(+), 22
On 04/02/15 16:48, Sifan Naeem wrote:
> Gets a handle to the system clock, already described in the binding
> document, and calls the appropriate common clock framework functions
> to mark it prepared/enabled, the common clock framework initially
> enables the clock and doesn't disable it at least
From: "Lad, Prabhakar"
this patch fixes following sparse warning:
ts3a227e.c:222:5: warning: symbol 'ts3a227e_enable_jack_detect' was not
declared. Should it be static?
Signed-off-by: Lad, Prabhakar
---
Found this issue on linux-next (gcc version 4.8.2,
sparse version 0.4.5-rc1)and applies
On 02/03/2015 04:13 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.18.6 release.
> There are 57 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses sh
On 02/03/2015 04:16 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.68 release.
> There are 51 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
On 02/03/2015 04:14 PM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.14.32 release.
> There are 33 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses s
On Tue, Feb 03, 2015 at 11:53:03AM +0100, Peter Zijlstra wrote:
> On Mon, Feb 02, 2015 at 06:53:45PM +0100, Frederic Weisbecker wrote:
> > It looks like preempt_count_add/inc() mostly imply entering a context that
> > we want
> > to be seen right away (thus want barrier() after) and
> > preempt_c
On Wed, Feb 04, 2015 at 01:27:21PM +0100, Geert Uytterhoeven wrote:
> Anyone may call clk_round_rate() with a zero rate value, so we have to
> protect against that.
>
> Signed-off-by: Geert Uytterhoeven
Acked-by: Wolfram Sang
I agree that this should not be fixed in the core because the fixup
Ok this is all sounding too magic for my tastes. My original suggestion
was for an actual new capability set, pA, empty by default. You can
add bits to it using prctl if ns_capable(CAP_SETPCAP) and all the new bits are
in your pE. Once set, they stay until they are removed using prctl. At
exec,
On Wed, 2015-02-04 at 13:06 +0100, Peter Zijlstra wrote:
> On Tue, Feb 03, 2015 at 11:43:36AM -0800, Tim Chen wrote:
> > That's true. We cannot have the lock grabbed by a new write
> > contender as any new writer contender of the lock will be
> > queued by the OSQ logic. Only the
> > thread doin
Three small cifs fixes. One fixes a hang under stress, and the other two are
security related.
The following changes since commit ec6f34e5b552fb0a52e6aae1a5afbbb1605cc6cc:
Linux 3.19-rc5 (2015-01-18 18:02:20 +1200)
are available in the git repository at:
git://git.samba.org/sfrench/cifs-2.
Hello.
On 02/04/2015 08:32 PM, Wolfram Sang wrote:
Anyone may call clk_round_rate() with a zero rate value, so we have to
protect against that.
Signed-off-by: Geert Uytterhoeven
Acked-by: Wolfram Sang
I agree that this should not be fixed in the core because the fixup is
really drive
On Wed, Feb 04, 2015 at 08:23:37AM -0800, Guenter Roeck wrote:
> Large EEPROMS (24c32 and larger) require a two-byte data address
> instead of just a single byte. Implement support for such EEPROMs
> with SMBus commands.
>
> Support has limitations (reads are not multi-master safe) and is slow,
>
2015-02-02 17:36 GMT+01:00 Sudip Mukherjee :
> On Thu, Jan 29, 2015 at 07:46:10PM +0100, Rickard Strandqvist wrote:
>> Fix a possible null pointer dereference, there is
>> otherwise a risk of a possible null pointer dereference.
>>
>> This was found using a static code analysis program called cppch
On Wed, 4 Feb 2015 13:54:31 +0200
"Kirill A. Shutemov" wrote:
> After commit 944d9fec8d7a we can allocate 1G pages runtime if CMA is
> enabled.
>
> Let's register 1G pages into hugetlb even if user hasn't requested them
> explicitly at boot time with hugepagesz=1G.
>
> Signed-off-by: Kirill A.
On Wed, Feb 04, 2015 at 06:31:57PM +0100, Frederic Weisbecker wrote:
> > In any case; if we make __schedule() noinline (I think that might make
> > sense) that function call would itself imply the compiler barrier and
> > something like:
> >
> > __preempt_count_add(PREEMPT_ACTIVE + PREEMPT_CH
On Wed, Feb 4, 2015 at 2:03 AM, Linus Walleij wrote:
> On Fri, Jan 30, 2015 at 5:20 PM, Bjorn Andersson
> wrote:
>> On Fri 30 Jan 02:27 PST 2015, Stanimir Varbanov wrote:
>>
>>> + case PIN_CONFIG_INPUT_ENABLE:
>>> + /* Pin is output */
>>> + if (arg)
>>> +
= -next-20150204)
drivers/staging/comedi/drivers/dt282x.c |9 +
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/drivers/staging/comedi/drivers/dt282x.c
b/drivers/staging/comedi/drivers/dt282x.c
index 051dfb2..db21d21 100644
--- a/drivers/staging/comedi/drivers/dt282x.c
On Tue, Feb 3, 2015 at 9:04 PM, Bjorn Helgaas wrote:
> [+cc Andres, Leigh, Jens because they were involved in 73d2eaac8a3f
> ("CS5536: apply pci quirk for BIOS SMBUS bug")]
>
> [+cc Bill, Martin, Matthew, Greg, Linus because they saw the original
> report and might be interested in the resolution]
From: "Lad, Prabhakar"
this patch fixes following sparse warning:
f_hid.c:572:30: warning: symbol 'f_hidg_fops' was not declared. Should it be
static?
Signed-off-by: Lad, Prabhakar
---
Found this issue on linux-next (gcc version 4.8.2,
sparse version 0.4.5-rc1)and applies on top linux-next
On Wed, Feb 04, 2015 at 04:16:34PM +, Timur Tabi wrote:
> On 02/04/2015 10:08 AM, Mark Salter wrote:
> > acpi_os_remap() is used to map ACPI tables. These tables may be in ram
> > which are already included in the kernel's linear RAM mapping. So we
> > need ioremap_cache to avoid two mappings t
From: Markus Elfring
Date: Wed, 4 Feb 2015 18:48:28 +0100
The relay_close() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
driver
On Wed, Feb 04, 2015 at 04:08:27PM +, Mark Salter wrote:
> On Wed, 2015-02-04 at 11:25 +, Catalin Marinas wrote:
> > On Tue, Feb 03, 2015 at 05:29:36PM +, Mark Salter wrote:
> > > On Mon, 2015-02-02 at 23:14 +0100, Rafael J. Wysocki wrote:
> > > > On Monday, February 02, 2015 08:45:30 P
On Wed, Feb 04, 2015 at 05:53:55PM +0100, Krzysztof Kozlowski wrote:
> The complete() should not be used on offlined CPU. Rewrite the
> wait-complete mechanism with wait_on_bit_timeout().
>
> The CPU triggering hot unplug (e.g. CPU0) will loop until some bit is
> cleared. In each iteration schedul
On 04.02.2015 20:15, Tejun Heo wrote:
Hello,
On Wed, Feb 04, 2015 at 01:49:08PM +0300, Konstantin Khlebnikov wrote:
I think important shared data must be handled and protected explicitly.
That 'catch-all' shared container could be separated into several
I kinda disagree. That'd be a major pa
From: "Lad, Prabhakar"
this patch fixes following sparse warnings:
f_uac2.c:57:12: warning: symbol 'uac2_name' was not declared. Should it be
static?
f_uac2.c:637:36: warning: symbol 'in_clk_src_desc' was not declared. Should it
be static?
f_uac2.c:649:36: warning: symbol 'out_clk_src_desc' was
From: "Lad, Prabhakar"
this patch fixes following sparse warning:
sl811-hcd.c:1804:24: warning: symbol 'sl811h_driver' was not declared. Should
it be static?
Signed-off-by: Lad, Prabhakar
---
drivers/usb/host/sl811-hcd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/driv
Hi Chanwoo,
On 02/02/15 15:23, Chanwoo Choi wrote:
> +/*
> + * ATLAS_PLL & APOLLO_PLL & MEM0_PLL & MEM1_PLL & BUS_PLL & MFC_PLL
> + * & MPHY_PLL & G3D_PLL & DISP_PLL & ISP_PLL
> + */
> +static struct samsung_pll_rate_table exynos5443_pll_rates[] = {
> + PLL_35XX_RATE(25, 625, 6, 0),
>
Hi,
On Wednesday, February 04, 2015 11:27:26 AM Krzysztof Kozlowski wrote:
> The Exynos cpuidle driver has coupled cpuidle built-in so it cannot be
> built without SMP:
>
> arch/arm/mach-exynos/pm.c: In function ‘exynos_cpu0_enter_aftr’:
> arch/arm/mach-exynos/pm.c:246:4: error: implicit declara
resv_lock is only used in reservations.c
Signed-off-by: Fabian Frederick
---
fs/ocfs2/reservations.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ocfs2/reservations.c b/fs/ocfs2/reservations.c
index 41ffd36..6a348b0 100644
--- a/fs/ocfs2/reservations.c
+++ b/fs/ocfs2/re
From: "Lad, Prabhakar"
this patch fixes following sparse warnings:
f_sourcesink.c:347:34: warning: symbol 'ss_int_source_comp_desc' was not
declared. Should it be static?
f_sourcesink.c:365:34: warning: symbol 'ss_int_sink_comp_desc' was not
declared. Should it be static?
Signed-off-by: Lad,
On Wed, 4 Feb 2015, Serge E. Hallyn wrote:
> Ok this is all sounding too magic for my tastes. My original suggestion
> was for an actual new capability set, pA, empty by default. You can
> add bits to it using prctl if ns_capable(CAP_SETPCAP) and all the new bits are
> in your pE. Once set, the
On Tue, Feb 03, 2015 at 05:40:20PM -0700, Al Stone wrote:
> Much removed to cut down the size on this and to highlight a couple of
> specific
> sections pertinent to the ACPI on ARMv8 TODO List.
This is of course good practice when replying to anything!
> > +_DSD 6.2.5 To be
From: "Lad, Prabhakar"
this patch fixes following sparse warning:
vt.c:1240:12: warning: symbol 'rgb_from_256' was not declared. Should it be
static?
Signed-off-by: Lad, Prabhakar
---
Found this issue on linux-next (gcc version 4.8.2,
sparse version 0.4.5-rc1)and applies on top linux-next.
From: "Lad, Prabhakar"
this patch fixes following sparse warnings:
bcm63xx_uart.c:857:43: warning: Using plain integer as NULL pointer
bcm63xx_uart.c:871:35: warning: Using plain integer as NULL pointer
Signed-off-by: Lad, Prabhakar
---
Found this issue on linux-next (gcc version 4.8.2,
spa
From: "Lad, Prabhakar"
this patch fixes following sparse warning:
n_gsm.c:2827:22: warning: symbol 'tty_ldisc_packet' was not declared. Should it
be static?
Signed-off-by: Lad, Prabhakar
---
Found this issue on linux-next (gcc version 4.8.2,
sparse version 0.4.5-rc1)and applies on top lin
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Tuesday, February 3, 2015 9:01 AM
> To: KY Srinivasan; de...@linuxdriverproject.org
> Cc: Haiyang Zhang; linux-kernel@vger.kernel.org; Dexuan Cui; Jason Wang
> Subject: [PATCH 0/4] Drivers: hv: Further prot
From: "Lad, Prabhakar"
this patch fixes following sparse warnings:
sysrq.c:58:16: warning: symbol 'platform_sysrq_reset_seq' was not declared.
Should it be static?
sysrq.c:59:5: warning: symbol 'sysrq_reset_downtime_ms' was not declared.
Should it be static?
Signed-off-by: Lad, Prabhakar
---
On Wed, 2015-02-04 at 10:19AM +0100, Linus Walleij wrote:
> On Thu, Jan 29, 2015 at 6:23 PM, Sören Brinkmann
> wrote:
> > On Mon, 2015-01-19 at 09:54AM +0100, Linus Walleij wrote:
> >> On Mon, Jan 19, 2015 at 5:20 AM, Alexandre Courbot
> >> wrote:
> >> > On Sat, Jan 17, 2015 at 1:49 AM, Sören Br
On Wed, Feb 04, 2015 at 08:58:21PM +0300, Konstantin Khlebnikov wrote:
> >>Generally incidental sharing could be handled as temporary sharing:
> >>default policy (if inode isn't pinned to memory cgroup) after some
> >>time should detect that inode is no longer shared and migrate it into
> >>origina
On Mon, 2015-02-02 at 19:39 +0300, Sergei Shtylyov wrote:
>
> > Hi, is this an open-coded version of PAGE_ALIGN?
>
> Yes, it appears so. :-)
>
> WBR, Sergei
>
Thanks for the suggestion by Jiri. I updated the patch to use PAGE_ALIGN
below.
Regards,
Tim
--->8---
From: Tim Chen
Subject: [
From: Vincent Guittot
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 b
From: Dietmar Eggemann
Skip cpu as a potential src (costliest) in case it has only one task
running and its original capacity is greater than or equal to the
original capacity of the dst cpu.
cc: Ingo Molnar
cc: Peter Zijlstra
Signed-off-by: Dietmar Eggemann
---
kernel/sched/fair.c | 4
cpuidle associates all idle-states with each cpu while the energy model
associates them with the sched_group covering the cpus coordinating
entry to the idle-state. To get idle-state power consumption it is
therefore necessary to translate from cpuidle idle-state index to energy
model index. For th
From: Dietmar Eggemann
Energy-aware load balancing should only happen if the ENERGY_AWARE feature
is turned on and the sched domain on which the load balancing is performed
on contains energy data.
There is also a need during a load balance action to be able to query if we
should continue to load
From: Morten Rasmussen
Implements arch-specific function to provide the scheduler with a
frequency scaling correction factor for more accurate load-tracking. The
factor is:
current_freq(cpu) * SCHED_CAPACITY_SCALE / max_freq(cpu)
This implementation only provides frequency invariance. N
Several techniques for saving energy through various scheduler
modifications have been proposed in the past, however most of the
techniques have not been universally beneficial for all use-cases and
platforms. For example, consolidating tasks on fewer cpus is an
effective way to save energy on some
From: Dietmar Eggemann
Energy-aware load balancing does not rely on env->imbalance but instead it
evaluates the system-wide energy difference for each task on the src rq by
potentially moving it to the dst rq. If this energy difference is lesser
than zero the task is actually moved from src to ds
From: Dietmar Eggemann
In case that after the gathering of sched domain statistics the current
load balancing operation is still in energy-aware mode, just return the
least efficient (costliest) reference. That implies the system is
considered to be balanced in case no least efficient sched group
From: Dietmar Eggemann
We do not want to miss out on the ability to do energy-aware idle load
balancing if the system is only partially loaded since the operational
range of energy-aware scheduling corresponds to a partially loaded
system. We might want to pull a single remaining task from a pote
Add an extra criteria to need_active_balance() to kick off active load
balance if the source cpu is overutilized and has lower capacity than
the destination cpus.
cc: Ingo Molnar
cc: Peter Zijlstra
Signed-off-by: Morten Rasmussen
---
kernel/sched/fair.c | 7 +++
1 file changed, 7 insertio
With energy-aware scheduling enabled nohz_kick_needed() generates many
nohz idle-balance kicks which lead to nothing when multiple tasks get
packed on a single cpu to save energy. This causes unnecessary wake-ups
and hence wastes energy. Make these conditions depend on !energy_aware()
for now until
On Wed, Feb 04, 2015 at 06:27:31PM +, Lad Prabhakar wrote:
> From: "Lad, Prabhakar"
Why put your name in a different order than is normally used? Please
just switch it around, tools don't like ',' all that much.
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe
Let available compute capacity and estimated energy impact select
wake-up target cpu when energy-aware scheduling is enabled.
energy_aware_wake_cpu() attempts to find group of cpus with sufficient
compute capacity to accommodate the task and find a cpu with enough spare
capacity to handle the task
To estimate the energy consumption of a sched_group in
sched_group_energy() it is necessary to know which idle-state the group
is in when it is idle. For now, it is assumed that this is the current
idle-state (though it might be wrong). Based on the individual cpu
idle-states group_idle_state() fin
From: Dietmar Eggemann
Energy-aware load balancing bases on cpu usage so the upper bound of its
operational range is a fully utilized cpu. Above this tipping point it
makes more sense to use weighted_cpuload to preserve smp_nice.
This patch implements the tipping point detection in update_sg_lb_s
From: Markus Elfring
Date: Wed, 4 Feb 2015 19:30:23 +0100
The release_firmware() function tests whether its argument is NULL and then
returns immediately. Thus the test around the call is not needed.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
d
Add another member to the family of per-cpu sched_domain shortcut
pointers. This one, sd_ea, points to the highest level at which energy
model is provided. At this level and all levels below all sched_groups
have energy model data attached.
cc: Ingo Molnar
cc: Peter Zijlstra
Signed-off-by: Mort
The idle-state of each cpu is currently pointed to by rq->idle_state but
there isn't any information in the struct cpuidle_state that can used to
look up the idle-state energy model data stored in struct
sched_group_energy. For this purpose is necessary to store the idle
state index as well. Ideall
From: Dietmar Eggemann
To be able to identify the least efficient (costliest) sched group
introduce group_eff as the efficiency of the sched group into sg_lb_stats.
The group efficiency is defined as the ratio between the group usage and
the group energy consumption.
cc: Ingo Molnar
cc: Peter Z
Extended sched_group_energy() to support energy prediction with usage
(tasks) added/removed from a specific cpu or migrated between a pair of
cpus. Useful for load-balancing decision making.
cc: Ingo Molnar
cc: Peter Zijlstra
Signed-off-by: Morten Rasmussen
---
kernel/sched/fair.c | 90 ++
201 - 300 of 927 matches
Mail list logo
