From: Luca Abeni
Hi all,
here is yet another version of the patchset implementing CPU reclaiming
(using the GRUB algorithm[1]) for SCHED_DEADLINE.
Basically, this feature allows SCHED_DEADLINE tasks to consume more
than their reserved runtime, up to a maximum fraction of the CPU time
(so that ot
From: Luca Abeni
Original GRUB tends to reclaim 100% of the CPU time... And this
allows a CPU hog to starve non-deadline tasks.
To address this issue, allow the scheduler to reclaim only a
specified fraction of CPU time.
Signed-off-by: Luca Abeni
Tested-by: Daniel Bristot de Oliveira
---
kern
From: Luca Abeni
The total rq utilization is defined as the sum of the utilisations of
tasks that are "assigned" to a runqueue, independently from their state
(TASK_RUNNING or blocked)
Signed-off-by: Luca Abeni
Signed-off-by: Claudio Scordino
Tested-by: Daniel Bristot de Oliveira
---
kernel/
From: Luca Abeni
Instead of decreasing the runtime as "dq = -Uact dt" (eventually
divided by the maximum utilization available for deadline tasks),
decrease it as "dq = -(1 - Uinact) dt", where Uinact is the "inactive
utilization".
In this way, the maximum fraction of CPU time that can be reclaim
From: Luca Abeni
Active utilization is defined as the total utilization of active
(TASK_RUNNING) tasks queued on a runqueue. Hence, it is increased
when a task wakes up and is decreased when a task blocks.
When a task is migrated from CPUi to CPUj, immediately subtract the
task's utilization fro
From: Luca Abeni
According to the GRUB (Greedy Reclaimation of Unused Bandwidth)
reclaiming algorithm, the runtime is not decreased as "dq = -dt",
but as "dq = -Uact dt" (where Uact is the per-runqueue active
utilization).
Hence, this commit modifies the runtime accounting rule in
update_curr_dl(
From: Luca Abeni
Signed-off-by: Luca Abeni
Tested-by: Daniel Bristot de Oliveira
---
include/uapi/linux/sched.h | 1 +
kernel/sched/core.c| 3 ++-
kernel/sched/deadline.c| 3 ++-
3 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/include/uapi/linux/sched.h b/include/uap
On Thu, Mar 23, 2017 at 08:10:20PM +0100, Uwe Kleine-König wrote:
> On Thu, Mar 23, 2017 at 08:44:41AM -0700, Dmitry Torokhov wrote:
> > On Thu, Mar 23, 2017 at 07:43:25AM -0700, Dmitry Torokhov wrote:
> > > On Thu, Mar 23, 2017 at 02:41:53PM +0100, Linus Walleij wrote:
> > > > On Thu, Mar 23, 2017
On Thu, Mar 23, 2017 at 08:38:08PM +0100, Stephen Mueller wrote:
> Apologies, I should have started this on linux-raid...
>
>
> stephen@fred> sudo gdisk -l /dev/sdc
> GPT fdisk (gdisk) version 1.0.1
>
> Partition table scan:
> MBR: protective
> BSD: not present
> APM: not present
> GPT:
Am Donnerstag, 23. März 2017, 13:29:10 CET schrieb Julia Cartwright:
> On Thu, Mar 23, 2017 at 06:55:50PM +0100, Heiko St?bner wrote:
> > Am Donnerstag, 23. März 2017, 17:51:53 CET schrieb John Keeping:
> > > On Thu, 23 Mar 2017 11:10:20 -0500, Julia Cartwright wrote:
> [..]
>
> > > > [..]
> > > >
David Miller writes:
>> Dave: Since you queued the firmware patch, mind taking this fix through
>> your tree?
>
> Ok, applied to net-next, thanks.
Great, thanks!
--
Martin K. Petersen Oracle Linux Engineering
OK, I used gdisk to remove the GPT and MBR from each disk.
mdadm --assemble still doesn't work... says it can't find the
superblock. The mdadm --examine commands also say that no
superblock is detected.
I guess I'll go ahead with --create...
On 3/23/2017 20:59, Lennart Sorensen wrote:
On Thu,
On Thu, Mar 23, 2017 at 11:56:56AM +, Jon Hunter wrote:
> Enable the Tegra BPMP I2C adapter by default if the Tegra BPMP itself
> is enabled. This adapter is used as the I2C interface for the PMIC on
> the Tegra186 Jetson-TX2 platform.
>
> Signed-off-by: Jon Hunter
> Acked-by: Thierry Reding
On Thu, Mar 23, 2017 at 09:46:14PM +0200, Andy Shevchenko wrote:
> The commit 10cf4899f8af ("gpiolib: tighten up ACPI legacy gpio lookups")
> prevents to getting same resource twice if the driver asks twice using same
s/same/different/
> connection ID.
>
> But the whole idea of fallback might br
On Thu, Mar 23, 2017 at 09:46:12PM +0200, Andy Shevchenko wrote:
> By some reason acpi_find_gpio() and acpi_gpio_count() have compared connection
> ID to "gpios" when tries to check if suffix is needed or not.
>
> Don't do any assumptions about what connection ID can be and, when defined,
> use
>
On Thu, Mar 23, 2017 at 10:25 AM, Thomas Garnier wrote:
> This patch ensures a syscall does not return to user-mode with a kernel
> address limit. If that happened, a process can corrupt kernel-mode
> memory and elevate privileges.
>
> For example, it would mitigation this bug:
>
> - https://bugs.
Hi Neil,
On Thu, Mar 23, 2017 at 5:27 PM, Neil Armstrong wrote:
> When trying to add a gpio-hog, we enter a weird loop where the gpio-ranges
> is needed when gpiochip_add_data() is called but in the current implementation
> the ranges are added from the driver afterwards.
>
> A simple solution is
On Fri, Mar 17, 2017 at 10:58:56AM +0100, M'boumba Cedric Madianga wrote:
> This patch adds initial support for the STM32F7 I2C controller.
>
> Signed-off-by: M'boumba Cedric Madianga
So, the STM32F7 has a new I2C IP core compared to STM32F4?
signature.asc
Description: PGP signature
On Thu, Mar 23, 2017 at 09:46:13PM +0200, Andy Shevchenko wrote:
> Check that we don't ask for output direction on GpioInt resource in cases with
> or without _DSD defined.
>
> Signed-off-by: Andy Shevchenko
Reviewed-by: Dmitry Torokhov
> ---
> drivers/gpio/gpiolib-acpi.c | 10 +-
> 1
If, while locating GPIOs by name, we get probe deferral, we should
immediately report it to caller rather than trying to fall back to parsing
unnamed GPIOs from _CRS block.
Signed-off-by: Dmitry Torokhov
---
drivers/gpio/gpiolib-acpi.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
di
On Sun, Jan 15, 2017 at 9:56 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sat, 14 Jan 2017 10:48:28 +0100
>
> * A multiplication for the size determination of a memory allocation
> indicated that an array data structure should be processed.
> Thus use the corresponding function
On Thu, Mar 23, 2017 at 04:03:11PM +0100, Arnd Bergmann wrote:
> The latest gcc-7 snapshot adds a warning to point out that when
> atk_read_value_old or atk_read_value_new fails, we copy
> uninitialized data into sensor->cached_value:
>
> drivers/hwmon/asus_atk0110.c: In function 'atk_input_show':
On Sun, Jan 15, 2017 at 9:58 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sat, 14 Jan 2017 11:00:23 +0100
>
> The script "checkpatch.pl" pointed information out like the following.
>
> WARNING: void function return statements are not generally useful
>
> Thus remove such a statemen
Hi Willy,
On Thu, Mar 23, 2017 at 8:03 PM, Willy TARREAU wrote:
> On Thu, Mar 23, 2017 at 07:49:53PM +0100, Geert Uytterhoeven wrote:
>> I take it you're using v1 of the patchset?
>>
>> v2 had this change:
>>
>> - Move backlight mutex initialization before call to
>> charlcd_init_display(),
On Thu, Mar 23, 2017 at 09:46:16PM +0200, Andy Shevchenko wrote:
> Documentation lacks of explanation how we actually use device properties
> for GPIO resources.
>
> Add a section to the documentation about that.
>
> Suggested-by: Mika Westerberg
> Signed-off-by: Andy Shevchenko
> ---
> Docume
On Sun, Jan 15, 2017 at 10:00 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sat, 14 Jan 2017 11:22:12 +0100
>
> Replace the specification of data structures by pointer dereferences
> as the parameter for the operator "sizeof" to make the corresponding size
> determination a bit safe
On Thu, Mar 23, 2017 at 11:25:49AM -0700, kan.li...@intel.com wrote:
> From: Kan Liang
>
> When setting FREEZE_WHILE_SMM bit in IA32_DEBUGCTL, all performance
> counters will be effected. There is no way to do per-counter freeze
> on smi. So it should not use the per-event interface (e.g. ioctl o
This adds CORRUPT_USER_DS to check that the get_fs() test on syscall return
still sees USER_DS during the new VERIFY_PRE_USERMODE_STATE checks.
Signed-off-by: Kees Cook
---
drivers/misc/lkdtm.h | 1 +
drivers/misc/lkdtm_bugs.c | 20
drivers/misc/lkdtm_core.c | 1 +
3
On 03/23/2017 06:49 AM, Tetsuo Handa wrote:
> Dmitry Vyukov wrote:
>> On Thu, Mar 23, 2017 at 2:06 PM, Dmitry Vyukov wrote:
>>> Hello,
>>>
>>> I've got the following report while running syzkaller fuzzer on
>>> 093b995e3b55a0ae0670226ddfcb05bfbf0099ae. Note the preceding injected
>>> kmalloc failu
On Thu, Mar 23, 2017 at 10:25 AM, Thomas Garnier wrote:
> Implement specific usage of verify_pre_usermode_state for user-mode
> returns for x86.
Signed-off-by: Thomas Garnier
Not sure why it was not there anymore.
--
Thomas
On Thu, Mar 23, 2017 at 10:25 AM, Thomas Garnier wrote:
> Implement specific usage of verify_pre_usermode_state for user-mode
> returns for arm64.
Signed-off-by: Thomas Garnier
Not sure why it was not there anymore.
--
Thomas
Hi!
> The Light Pulse Generator (LPG) is a PWM-block found in a wide range of
> PMICs from Qualcomm. It can operate on fixed parameters or based on a
> lookup-table, altering the duty cycle over time - which provides the
> means for e.g. hardware assisted transitions of LED brightness.
Ok, this i
On Thu, Mar 23, 2017 at 10:25 AM, Thomas Garnier wrote:
> Implement specific usage of verify_pre_usermode_state for user-mode
> returns for arm.
Signed-off-by: Thomas Garnier
Not sure why it was not there anymore.
--
Thomas
On Sun, Jan 15, 2017 at 10:02 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sat, 14 Jan 2017 12:36:59 +0100
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
> The script "checkpatch.pl" pointed information out like the following.
>
>
Hi Dmitry,
On Thu, Mar 23, 2017 at 11:51:30AM +0100, Dmitry Vyukov wrote:
> Hello,
>
> I've got the following report while running syzkaller fuzzer.
> init_crypt ignores kmalloc failure, which later leads to out-of-bounds
> writes in ptr_crypt. On commit
> 093b995e3b55a0ae0670226ddfcb05bfbf0099ae
On Sun, Jan 15, 2017 at 10:01 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sat, 14 Jan 2017 12:06:13 +0100
>
> A multiplication for the size determination of a memory allocation
> indicated that an array data structure should be processed.
> Thus use the corresponding function "kma
On Thu, Mar 23, 2017 at 11:25:49AM -0700, kan.li...@intel.com wrote:
> + for_each_possible_cpu(cpu) {
> + rdmsrl_on_cpu(cpu, MSR_IA32_DEBUGCTLMSR, &debugctlmsr);
> + if (val)
> + wrmsrl_on_cpu(cpu, MSR_IA32_DEBUGCTLMSR, debugctlmsr |
> DEBUGCTLMSR_FR
Hi Wolfram,
Yes the STM32F7 has a new I2C IP core compared to STM32F4.
The engine, the machine state are very different.
I tried few months ago to write a common driver but it was very very
difficilcut as the 2 IP are not so much things in common.
BR,
Cedric
2017-03-23 21:17 GMT+01:00 Wolfram Sa
On Mar 22, 2017, at 09:53, Arushi Singhal
wrote:
>
> This patch replaces bit shifting on 1 with the BIT(x) macro.
> This was done with coccinelle:
> @@
> constant c;
> @@
>
> -1 << c
> +BIT(c)
>
> Signed-off-by: Arushi Singhal
Reviewed-by: Andreas Dilger
> ---
> changes in v2
> - remove th
On Wed, Mar 15, 2017 at 12:31:34PM +0100, Philipp Zabel wrote:
> As of commit bb475230b8e5 ("reset: make optional functions really
> optional"), the reset framework API calls use NULL pointers to describe
> optional, non-present reset controls.
>
> This allows to return errors from devm_reset_cont
> Yes the STM32F7 has a new I2C IP core compared to STM32F4.
> The engine, the machine state are very different.
> I tried few months ago to write a common driver but it was very very
> difficilcut as the 2 IP are not so much things in common.
Good, thanks for the heads up!
signature.asc
Descr
From: Eric Biggers
In the generic XTS and LRW algorithms, for input data > 128 bytes, a
temporary buffer is allocated to hold the values to be XOR'ed with the
data before and after encryption or decryption. If the allocation
fails, the fixed-size buffer embedded in the request buffer is meant to
On Thu, Mar 23, 2017 at 06:24:19PM +0100, David Hildenbrand wrote:
> No caller currently checks the return value of
> kvm_io_bus_unregister_dev(). This is evil, as all callers silently go on
> freeing their device. A stale reference will remain in the io_bus,
> getting at least used again, when the
On Thu, Mar 23, 2017 at 09:01:43PM +0100, Heiko St?bner wrote:
> Am Donnerstag, 23. März 2017, 13:29:10 CET schrieb Julia Cartwright:
> > On Thu, Mar 23, 2017 at 06:55:50PM +0100, Heiko St?bner wrote:
> > > Am Donnerstag, 23. März 2017, 17:51:53 CET schrieb John Keeping:
> > > > On Thu, 23 Mar 2017
On Mar 22, 2017, at 06:12, Dilger, Andreas wrote:
>
> On Mar 21, 2017, at 22:39, Arushi Singhal
> wrote:
>>
>> This patch replaces bit shifting on 1 with the BIT(x) macro.
>> This was done with coccinelle:
[snip]
>> diff --git a/drivers/staging/lustre/lnet/lnet/net_fault.c
>> b/drivers/stagin
On Thu, Mar 23, 2017 at 01:19:43PM -0500, Larry Finger wrote:
> Since kernel 4.11-rc1, my desktop (Plasma5/KDE) has encountered
> intermittent hangs with the following information in the logs:
>
> linux-4v1g.suse kernel: [drm] GPU HANG: ecode 7:0:0xf3ce, in
> plasmashell [1283], reason: Hang o
On Thu, Mar 23, 2017 at 07:15:38PM +0530, Arushi Singhal wrote:
> Fix checkpatch issues: "CHECK: Alignment should match open parenthesis".
>
> Signed-off-by: Arushi Singhal
I can't take patches sent in html format :(
please fix your email client.
thanks,
greg k-h
> On Thu, Mar 23, 2017 at 11:25:49AM -0700, kan.li...@intel.com wrote:
> > From: Kan Liang
> >
> > When setting FREEZE_WHILE_SMM bit in IA32_DEBUGCTL, all
> performance
> > counters will be effected. There is no way to do per-counter freeze on
> > smi. So it should not use the per-event interface
On Thu, Mar 02, 2017 at 11:34:07AM +0100, Jan Glauber wrote:
> Add support for reading the system clock and the TWSI clock
> frequency from ACPI DSDT.
>
> TWSI clock was already covered by using device_property_read().
>
> Signed-off-by: Jan Glauber
Applied to for-next, thanks!
signature.asc
On 03/23/2017 12:26 PM, Sai Gurrappadi wrote:
>
> Hm, sorry I am a bit confused perhaps you could help me understand the
> problem/solution better :)
>
> Say we have the this simple case of only a single periodic task running on
> one CPU, wouldn't the PELT update on wakeup cause a frequency
On Thu, Mar 23, 2017 at 10:26:49AM +, Lee Jones wrote:
> On Thu, 23 Mar 2017, Lionel DEBIEVE wrote:
>
> > On 03/22/2017 07:47 PM, Julia Cartwright wrote:
> > > On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
> > >> On 03/22/2017 01:01 PM, Steven Rostedt wrote:
> > >>> On Wed
On Thu, Mar 23, 2017 at 02:02:58PM +, Zhang, Shile (Nokia - CN/Hangzhou)
wrote:
> Correct patch for the typo.
> Sorry for I sent first patch w/o commit log and second patch with incorrect
> fix.
> Thanks!
>
Notes like this go below the --- line, if they are above, they end up in
the cha
* Keerthy [170321 20:45]:
>
>
> On Thursday 09 March 2017 01:35 PM, Keerthy wrote:
> > Currently the slope and offset values for calculating the
> > hot spot temperature of a particular thermal zone is part
> > of driver data. Pass them here instead and obtain the values
> > while of node parsin
When there are two or more tasks executing in user-space and
taking 100% of a nohz_full CPU, top reports 70% system time
and 30% user time utilization. Sometimes I'm even able to get
100% system time and 0% user time.
This was reproduced with latest Linus tree (093b995), but I
don't believe it's
On 03/23/2017 05:58 AM, Punit Agrawal wrote:
> On architectures that support hugepages composed of contiguous pte as
> well as block entries at the same level in the page table,
> huge_pte_offset() is not able to determine the right offset to return
> when it encounters a swap entry (which is used
Ping? Any feedback on this patch?
Is this in someone's queue for review?
thanks,
grant
On Tue, Mar 14, 2017 at 12:40 PM, Matthias Kaehlcke wrote:
> jiffies_64 is defined in kernel/time/timer.c with
> cacheline_aligned_in_smp,
> however this macro is not part of the declaration of jiffies an
On Thu, Mar 23, 2017 at 10:51 AM, Josef Bacik wrote:
> Yeah I think this is ok, I’ll throw it on my queue for fixes for this cycle.
> Thanks,
Great. Thanks.
>
> Josef
* Roger Quadros [170317 02:00]:
> From fe0a37d5e53381c3f79c6b6cf7915e44789f516f Mon Sep 17 00:00:00 2001
> From: Roger Quadros
> Date: Tue, 7 Feb 2017 16:52:57 +0530
> Subject: [PATCH 2/4] ARM: OMAP2+ hwmod: Allow modules to disable HW_AUTO
>
> Introduce HWMOD_CLKDM_NOAUTO flag that allows the h
* Bartosz Golaszewski [170314 04:16]:
> This series implements support for the on-board SATA controller
> on the dm8168-evm board.
>
> The first patch adds the clock domain and hwmod entries for the
> SATA module.
>
> The second patch models the external reference clock used by SATA.
>
> The th
* Franklin S Cooper Jr [170307 14:01]:
> This patch set adds support for the on board SPI NOR flash on TI's AM335x
> Industrial Communication Engine rev 2.x board.
>
> Franklin S Cooper Jr (1):
> ARM: dts: am335x-icev2: Add SPI based NOR
>
> Sekhar Nori (1):
> doc: dt: mtd: add w25q64 to lis
On Thu, Mar 23, 2017 at 09:09:39PM +0100, Stephen Mueller wrote:
> OK, I used gdisk to remove the GPT and MBR from each disk.
> mdadm --assemble still doesn't work... says it can't find the
> superblock. The mdadm --examine commands also say that no
> superblock is detected.
Yes the GPT overwrite
Looks like it worked! Thanks!
I used:
sudo mdadm --create /dev/md0 --assume-clean --verbose --level-10
--raid-devices=4 /dev/sdc /dev/sdd /dev/sde /dev/sdf
And I got my instructions for creating the array here, and they
also don't use partitions...
https://www.digitalocean.com/community/tuto
On 3/17/2017 5:58 PM, Elliott, Robert (Persistent Memory) wrote:
-Original Message-
From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
ow...@vger.kernel.org] On Behalf Of Tom Lendacky
Sent: Thursday, February 16, 2017 9:45 AM
Subject: [RFC PATCH v4 15/28] Add support to acc
On Tue, Mar 07, 2017 at 12:43:52PM +0100, Tobias Regnery wrote:
> I see the following build error with COMPILE_TEST on randconfig builds:
>
> divers/built-in.o: In function `nsp_usb3_phy_init':
> phy-bcm-nsp-usb3.c:(.text+0x4050): undefined reference to `mdiobus_write'
> phy-bcm-nsp-usb3.c:(.text+
This adds a new dynamic PMU to the Perf Events framework to program
and control the L3 cache PMUs in some Qualcomm Technologies SOCs.
The driver supports a distributed cache architecture where the overall
cache for a socket is comprised of multiple slices each with its own PMU.
Access to each indi
Coreboot (http://www.coreboot.org) allows to save the firmware console
output in a memory buffer. With this patch, the address of this memory
buffer is obtained from coreboot tables on x86 chromebook devices
declaring an ACPI device with name matching GOOGCB00 or BOOT.
If the memconsole-corebo
This patch expands the Google firmware memory console driver to also
work on certain tree based platforms running coreboot, such as ARM/ARM64
Chromebooks. This patch now adds another path to find the coreboot table
through the device tree. In order to find that, a second level
bootloader must have
From: Julius Werner
This patch adds documentation describing a device tree binding for the
coreboot firmware. It is meant to be dynamically added during boot and
contains address definitions for the coreboot table (a list of
variable-sized descriptors providing information about various compile-
Hi,
This series extends the Google memory console driver to work on x86 and
ARM platforms running coreboot.
The legacy x86 memconsole driver is now named memconsole-x86-legacy and
a new driver named memconsole-coreboot is added.
On coreboot devices and depending on the device architecture, the d
On Wed, Mar 22, 2017 at 08:30:32PM +0530, Kishon Vijay Abraham I wrote:
> Hi Greg,
>
> Please find the pull request for this -rc cycle below.
>
> The major change is removing USB3 PHY driver for Broadcom NSP merged
> during the last merge window. It is found there already exists a PHY
> driver (u
From: Eric Biggers
Date: Thu, 23 Mar 2017 13:39:46 -0700
> From: Eric Biggers
>
> In the generic XTS and LRW algorithms, for input data > 128 bytes, a
> temporary buffer is allocated to hold the values to be XOR'ed with the
> data before and after encryption or decryption. If the allocation
>
This patch removes the "Google Firmware Drivers" menu containing a
menuconfig entry with the exact same name. The menuconfig is now
directly under the "Firmware Drivers" entry.
Signed-off-by: Thierry Escande
---
drivers/firmware/google/Kconfig | 7 +++
1 file changed, 3 insertions(+), 4 dele
This patch splits memconsole.c in 2 parts. One containing the
architecture-independent part and the other one containing the EBDA
specific part. This prepares the integration of coreboot support for the
memconsole.
The memconsole driver is now named as memconsole-x86-legacy.
Signed-off-by: Thierr
On Thu, Mar 23, 2017 at 10:02:23PM +0100, Stephen Mueller wrote:
> Looks like it worked! Thanks!
Well at least you could backup the data, just in case.
> I used:
>
> sudo mdadm --create /dev/md0 --assume-clean --verbose --level-10
> --raid-devices=4 /dev/sdc /dev/sdd /dev/sde /dev/sdf
I wonder
First I'm getting the data off the RAID... then I'm going to delete the
whole thing again... create a new RAID using partitions... follow every
step carefully... then once the new RAID array is there, I'll throw a
bit of data on it, and then reboot and see if it's still there...
if so, I'll repo
can you add bps here too?
On Tue, Mar 21, 2017 at 6:53 PM, Chris Zhong wrote:
> Support Innolux P079ZCA 7.85" 768x1024 TFT LCD panel, it is a MIPI DSI
> panel.
>
> Signed-off-by: Chris Zhong
> Reviewed-by: Sean Paul
> Tested-by: Brian Norris
> ---
>
> Changes in v3:
> - printk err after regula
On Wed, Mar 22, 2017 at 7:55 PM, Eddie Kovsky wrote:
> Implement a mechanism to check if a module's address is in
> the rodata or ro_after_init sections. It mimics the exsiting functions
> that test if an address is inside a module's text section.
>
> Functions that take a module as an argument wi
On 03/22/2017 07:21 PM, Geert Uytterhoeven wrote:
Commit 7613c922315e308a ("backlight: pwm_bl: Move the checks for initial
power state to a separate function") not just moved some code, but made
slight changes in semantics.
If a gpiochip doesn't implement the optional .get_direction() callback,
On Sun, Jan 15, 2017 at 10:03 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sat, 14 Jan 2017 13:08:59 +0100
>
> Multiplications for the size determination of memory allocations
> indicated that array data structures should be processed.
> Thus use the corresponding function "kcalloc
On Thu, 23 Mar 2017, Nicolas Pitre wrote:
> Is there a need for 64 bits of relative time stamps?
> And 32 bits of IRQ number?
No.
> I'd say that 48 bit time stamp and 16 bit IRQ number is way sufficient.
> Who cares if we mispredict an IRQ after 78 hours of idle time?
>
> Hence:
>
> u64 v
This is a minimal TTY layer replacement for embedded systems with limited
capabilities. This supports only serial ports, supports only a subset of
the default line discipline, and dispense with anything that is of no use
for a small embedded system.
Signed-off-by: Nicolas Pitre
---
drivers/tty/K
All the console driver handling code lives in printk.c.
Move console_init() there as well so console support can still be used
when the TTY code is configured out.
Signed-off-by: Nicolas Pitre
---
drivers/tty/tty_io.c| 24
include/linux/console.h | 2 ++
include/lin
Many embedded systems don't need the full TTY layer support. Most of the
time, the TTY layer is only a conduit for outputting debugging messages
over a serial port. The TTY layer also implements many features that are
very unlikely to ever be used in such a setup. There is great potential
for both
To allow reuse without the rest of the tty_ioctl code.
Signed-off-by: Nicolas Pitre
---
drivers/tty/Makefile | 2 +-
drivers/tty/tty_baudrate.c | 232 +
drivers/tty/tty_ioctl.c| 222 ---
3 files chang
On Wed, Mar 22, 2017 at 7:55 PM, Eddie Kovsky wrote:
> Provide a mechanism to check if the address of a variable is
> const or ro_after_init. It mimics the existing functions that test if an
> address is inside the kernel's text section.
>
> Other functions inside the kernel could then use this ca
On Sun, Jan 15, 2017 at 10:04 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sat, 14 Jan 2017 13:40:25 +0100
>
> The local variable "rc" was reset with an error code up to five times
> before a memory allocation failure was detected.
>
> Add a jump target so that this assignment will
On Thu, Mar 23, 2017 at 11:57:22AM -0500, Rob Herring wrote:
> On Thu, Mar 23, 2017 at 08:46:03AM -0500, Rob Herring wrote:
> > On Thu, Mar 23, 2017 at 12:30:18AM -0700, l...@pengaru.com wrote:
> > > On Wed, Mar 22, 2017 at 11:44:18PM -0700, l...@pengaru.com wrote:
> > > > On Wed, Mar 22, 2017 at 0
> Also could you refresh my mind to expose why these patchse were not
> apply the first time and why we should apply them now?
Hi Gregory
Because i got busy with other things, and never spent the time needed
to address the comments. Ralph has addressed all the comments from the
original posting.
On Sun, Jan 15, 2017 at 10:06 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sat, 14 Jan 2017 14:00:02 +0100
>
> The script "checkpatch.pl" pointed information out like the following.
>
> WARNING: void function return statements are not generally useful
>
> Thus remove such a stateme
On 03/23/2017 03:44 PM, Chris Wilson wrote:
On Thu, Mar 23, 2017 at 01:19:43PM -0500, Larry Finger wrote:
Since kernel 4.11-rc1, my desktop (Plasma5/KDE) has encountered
intermittent hangs with the following information in the logs:
linux-4v1g.suse kernel: [drm] GPU HANG: ecode 7:0:0xf3ce,
From: Zach Brown
Date: Wed, 22 Mar 2017 15:27:01 -0500
> From: Nathan Sullivan
>
> If the PHY is halted on stop, then do not set the state to PHY_UP. This
> ensures the phy will be restarted later in phy_start when the machine is
> started again.
>
> Signed-off-by: Nathan Sullivan
> Signed-o
On Sun, Jan 15, 2017 at 10:07 AM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Sat, 14 Jan 2017 14:20:41 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> Link:
> http://events.linuxfoundation.org/sites/events/files/slides/LCJ16-Refactor_Strings-WSa
On Wed, Mar 22, 2017 at 01:13:19PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the char-misc tree got a conflict in:
>
> drivers/char/tpm/tpm-chip.c
>
> between commit:
>
> d7a97c3e6592 ("tpm: Use the right clean up after cdev_add completes")
I don't think this
This is my second pass at trying to add support for busy polling when using
epoll. It is pretty much a full rewrite as I have made serious changes to
most of the patches.
In the v1 series I had submitted we only allowed epoll to make use of busy
poll when all NAPI IDs were the same. I gave this so
From: Alexander Duyck
While working on some recent busy poll changes we found that child sockets
were being instantiated without NAPI ID being set. In our first attempt to
fix it, it was suggested that we should just pull programming the NAPI ID
into the function itself since all callers will ne
From: Alexander Duyck
This patch is a cleanup/fix for NAPI IDs following the changes that made it
so that sender_cpu and napi_id were doing a better job of sharing the same
location in the sk_buff.
One issue I found is that we weren't validating the napi_id as being valid
before we started tryin
From: Alexander Duyck
>From what I can tell there is only a couple spots where we are actually
checking the return value of sk_busy_loop. As there are only a few
consumers of that data, and the data being checked for can be replaced
with a check for !skb_queue_empty() we might as well just pull t
From: Alexander Duyck
Instead of defining two versions of skb_mark_napi_id I think it is more
readable to just match the format of the sk_mark_napi_id functions and just
wrap the contents of the function instead of defining two versions of the
function. This way we can save a few lines of code s
From: Alexander Duyck
This patch flips the logic we were using to determine if the busy polling
has timed out. The main motivation for this is that we will need to
support two different possible timeout values in the future and by
recording the start time rather than when we would want to end we
From: Sridhar Samudrala
This socket option returns the NAPI ID associated with the queue on which
the last frame is received. This information can be used by the apps to
split the incoming flows among the threads based on the Rx queue on which
they are received.
If the NAPI ID actually represent
701 - 800 of 1018 matches
Mail list logo
