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 tracki
* Pali Rohár [150226 05:54]:
> Harmattan system on Nokia N9 and N950 devices uses omap crypto support.
> Bootloader on those devices is known that it enables HW crypto support.
> This patch just include omap36xx.dtsi directly, so aes and sham is enabled.
Let's also remove omap36xx-hs.dtsi with th
On Friday 27 February 2015 16:43:20 Tony Lindgren wrote:
> * Pali Rohár [150226 05:54]:
> > Harmattan system on Nokia N9 and N950 devices uses omap
> > crypto support. Bootloader on those devices is known that
> > it enables HW crypto support. This patch just include
> > omap36xx.dtsi directly, so
* Aaro Koskinen [150226 15:06]:
> Hi,
>
> On Thu, Feb 26, 2015 at 11:19:50PM +0100, Pavel Machek wrote:
> > Ok, it seems that new config dependencies broke my kconfig. These will
> > not be enabled if you just to make oldconfig; you want to make sure
> > they are on.
> >
> > OMAP2430 and onward
* Sergei Shtylyov [150227 06:27]:
> Hello.
>
> On 2/27/2015 5:17 PM, Robert Abel wrote:
>
> >>Documentation/kernel-doc-nano-HOWTO.txt requires colons after the
> >>parameter names, doesn't it?
>
> >Jesus Christ, you guys are killing me...
> >I've already spent way more time on this patch se
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. Then,
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, utilizatio
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
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 group
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 patch
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 ex
Signed-off-by: Vincent Guittot
---
kernel/sched/core.c | 12
kernel/sched/fair.c | 13 +++--
kernel/sched/sched.h | 2 +-
3 files changed, 4 insertions(+), 23 deletions(-)
diff --git a/kernel/sched/core.c b/kernel/sched/core.c
index 28e3ec2..29f7037 100644
--- a/kernel/sc
The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
even though the access is defined as asynchronous, and no GPMC_CLK clock
is provided to the external device. Still, GPMCFCLKDIVIDER is used as a divider
for the GPMC clock, so it must be programmed to define the
correct WAITM
The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
even though the access is defined as asynchronous, and no GPMC_CLK clock
is provided to the external device. Still, GPMCFCLKDIVIDER is used as a divider
for the GPMC clock, so it must be programmed to define the
correct WAITM
GPMC_CONFIG1_i parameters CLKACTIVATIONTIME and WAITMONITORINGTIME
have reserved values.
Raise an error if calculated timings try to program reserved values.
GPMC_CONFIG1_i ATTACHEDDEVICEPAGELENGTH and DEVICESIZE were already checked
when parsing the DT.
Explicitly comment invalid values on gpmc_
OMAP2+ GPMC driver undefines DEBUG, which makes it unnecessarily
hard to turn DEBUG on. Remove the offending lines.
Signed-off-by: Robert ABEL
---
drivers/memory/omap-gpmc.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/memory/omap-gpmc.c b/drivers/memory/omap-gpmc.c
index 24696f5
These are the changes I proposed in these patch series: [1], [2], [3], [4]
rebased to 3.19 as well as new changes for little bugs I noticed while
preparing this patch series as well as changes introduced via comments.
1. DEBUG was undefined in source code --> remove offending lines
2. add capabili
The WAITMONITORINGTIME is expressed as a number of GPMC_CLK clock cycles,
even though the access is defined as asynchronous, and no GPMC_CLK clock
is provided to the external device. Still, GPMCFCLKDIVIDER is used as a divider
for the GPMC clock, so it must be programmed to define the
correct WAITM
DTS output was formatted to require additional work when copy-pasting into DTS.
Nano-second timings were replaced with interval of values that produce the same
number of clock ticks.
Signed-off-by: Robert ABEL
---
drivers/memory/omap-gpmc.c | 38 --
1 file cha
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.
It's wo
On Monday 26 January 2015 23:34:34 Andreas Färber wrote:
> Am 26.01.2015 um 20:09 schrieb Pali Rohár:
> > diff --git a/arch/arm/kernel/devtree.c
> > b/arch/arm/kernel/devtree.c index 11c54de..9946c1b 100644
> > --- a/arch/arm/kernel/devtree.c
> > +++ b/arch/arm/kernel/devtree.c
>
> [...]
>
> > @@
This patch adds support for spawning buses as children of the GPMC.
Signed-off-by: Robert ABEL
---
drivers/memory/omap-gpmc.c | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
diff --git a/drivers/memory/omap-gpmc.c b/drivers/memory/omap-gpmc.c
index 5cabac8..74a8c52 1006
With this patch "revision" DT string entry is used to set global system_rev
variable. DT "revision" is expected to be string with one hexadecimal number.
So "Revision" line in /proc/cpuinfo will be same as "revision" DT value.
Signed-off-by: Pali Rohár
---
arch/arm/kernel/devtree.c | 20 ++
GPMC debug output is aligned to 10 characters for field names.
However, some fields have bigger names, screwing up the alignment.
Consequently, alignment was changed to longest field name (17 chars) for now.
Signed-off-by: Robert ABEL
---
drivers/memory/omap-gpmc.c | 2 +-
1 file changed, 1 inse
On Tue, Feb 24, 2015 at 9:27 PM, Murali Karicheri wrote:
> From: Grygorii Strashko
>
> Historically Davinci MDIO driver was created with assumption that
> MDIO is standalone device, but for Keystone 2 it's a part
> of NETCP module and now NETCP driver requests IO range which
> includes MDIO IO r
ATAG_REVISION is unsigned number and revision in DT is stored as hexadecimal
string value. It means that it will be correctly parsed by kernel.
Signed-off-by: Pali Rohár
---
arch/arm/boot/compressed/atags_to_fdt.c | 37 +++
1 file changed, 37 insertions(+)
diff --g
This patch adds support for DT "/revision" and convert ATAG_REVISION to DT.
Pali Rohár (2):
arm: devtree: Set system_rev from DT revision
arm: boot: convert ATAG_REVISION to DT revision field
arch/arm/boot/compressed/atags_to_fdt.c | 37 +++
arch/arm/kernel/devt
> -Original Message-
> From: Justin Piszcz [mailto:jpis...@lucidpixels.com]
> Sent: Friday, February 27, 2015 9:54 AM
> To: linux-kernel@vger.kernel.org
> Subject: 3.19 kernel: BUG: unable to handle kernel NULL pointer
dereference
>
> Hello,
>
> With kernel 3.15, I do not recall having
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 b/kernel/sched/core.
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 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 Fri, Feb 27, 2015 at 04:48:39PM +0100, Valentin Rothberg wrote:
> On Fri, Feb 27, 2015 at 4:24 PM, Felipe Balbi wrote:
> > On Fri, Feb 27, 2015 at 02:29:40PM +0100, Valentin Rothberg wrote:
> >> The IRQF_DISABLED is a NOOP and scheduled to be removed. According to
> >> commit e58aa3d2d0cc (gen
On Fri, Feb 27, 2015 at 4:24 PM, Felipe Balbi wrote:
> On Fri, Feb 27, 2015 at 02:29:40PM +0100, Valentin Rothberg wrote:
>> The IRQF_DISABLED is a NOOP and scheduled to be removed. According to
>> commit e58aa3d2d0cc (genirq: Run irq handlers with interrupts disabled)
>> running IRQ handlers wit
On Friday 30 January 2015 22:03:36 Rob Herring wrote:
> lOn Fri, Jan 30, 2015 at 8:14 AM, Pali Rohár
wrote:
> > On Monday 26 January 2015 21:22:27 Rob Herring wrote:
> >> On Mon, Jan 26, 2015 at 1:09 PM, Pali Rohár
> >
> > wrote:
> >> > Ok, here is patch which set Revision field (global
> >> >
Current code uses args->args[0] as array subscript of phy_drd->phys[].
So the valid value range for args->args[0] is 0 ... EXYNOS5_DRDPHYS_NUM - 1.
Signed-off-by: Axel Lin
---
drivers/phy/phy-exynos5-usbdrd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/phy/phy-exy
Hi Linus,
Two smaller fixes for this cycle:
- A fixup from Keith so that NVMe compiles without BLK_INTEGRITY,
basically just moving the code around appropriately.
- A fixup for shm, fixing an oops in shmem_mapping() for mapping with no
inode. From Sasha.
Please pull!
git://git.kernel.dk
On Fri, 27 Feb 2015 14:48:14 +
Javi Merino wrote:
> +static int alloc_and_process_arg(struct event_format *event, char
> *next_token,
> + struct print_arg **print_arg)
> +{
> + struct print_arg *field;
> + enum event_type type;
> + char *token;
> +
On Tue, Feb 24, 2015 at 02:36:25PM -0800, D. Cooper Stevenson wrote:
> Hello All,
>
> I read the Linus's release for RC1. One of his favorite features in the
> release are, "actually some vm cleanups, where this release is getting rid
> of the largely unused non-linear remapping code (replaced wit
In commit b4eef9b36db4, we started to use hwapic_isr_update() != NULL
instead of kvm_apic_vid_enabled(vcpu->kvm). This didn't work because
SVM had it defined and "apicv" path in apic_{set,clear}_isr() does not
change apic->isr_count, because it should always be 1. The initial
value of apic->isr_c
Em Fri, Feb 27, 2015 at 01:50:24PM +0900, Masami Hiramatsu escreveu:
> Hi,
>
> Here is the 6th version of of perf buildid-cache update.
> This updates the 1st and 2nd patches according to Arnaldo's comment.
>
> Here are the changes in v6.
>
> - [1/3] Add verbose error message if failed to list
On Wed, Feb 11, 2015 at 07:35:29PM -0800, Bjorn Andersson wrote:
> The function regulator_set_optimum_mode() is changing name to
> regulator_set_load(), so update the code accordingly.
>
> Signed-off-by: Bjorn Andersson
since this depends on the rest of the series:
Acked-by: Felipe Balbi
> --
On Wed, Feb 11, 2015 at 07:35:30PM -0800, Bjorn Andersson wrote:
> The function regulator_set_optimum_mode() is changing name to
> regulator_set_load(), so update the code accordingly.
>
> Signed-off-by: Bjorn Andersson
since this depends on the rest of the series:
Acked-by: Felipe Balbi
> --
On Fri, 27 Feb 2015 16:01:30 +0100
Daniel Wagner wrote:
> Sorry for the late response. Got dragged away.
>
> On 02/24/2015 10:06 PM, Jeff Layton wrote:
> > On Tue, 24 Feb 2015 16:58:26 +0100
> > Daniel Wagner wrote:
> >
> >> On 02/20/2015 05:05 PM, Andi Kleen wrote:
> >>> Daniel Wagner writes
Em Fri, Feb 27, 2015 at 06:21:24PM +0800, Yunlong Song escreveu:
> Hi,
> Found some functions to improve and bugs to fix in perf.
>
> This patchset is based on:
> https://git.kernel.org/cgit/linux/kernel/git/acme/linux.git/ perf/core
>
> For [PATCH v3 4/7] and [PATCH v3 5/7], I have ch
On Fri, Feb 27, 2015 at 02:29:40PM +0100, Valentin Rothberg wrote:
> The IRQF_DISABLED is a NOOP and scheduled to be removed. According to
> commit e58aa3d2d0cc (genirq: Run irq handlers with interrupts disabled)
> running IRQ handlers with interrupts enabled can cause stack overflows
> when the i
Em Fri, Feb 27, 2015 at 12:20:46PM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Fri, Feb 27, 2015 at 06:21:28PM +0800, Yunlong Song escreveu:
> > Extend 'perf list --raw-dump' to 'perf list --raw-dump [hw|sw|cache
> > |tracepoint|pmu|event_glob]' in order to show the raw-dump of a
> > certain kin
2015-02-26 19:31-0300, Marcelo Tosatti:
> On Thu, Feb 26, 2015 at 10:49:53AM +0200, Nadav Amit wrote:
> > Marcello, Radim,
> >
> > As you know - I can run some tests on the patches and whether they comply
> > with real hardware. Please let me know which version to test and I’ll try to
> > do next
On 27/02/2015 16:14, Sudip Mukherjee wrote:
>>> I don't understand the change either, I suggest asking the kvmm
>>> developer who accepted it.
> Hi Paolo, We have a small confusion about commit
> bab5bb398273bb37547a185f7b344b37c700d0b9. It looks like the patch
> removed a call to function kvm_m
Em Fri, Feb 27, 2015 at 06:21:28PM +0800, Yunlong Song escreveu:
> Extend 'perf list --raw-dump' to 'perf list --raw-dump [hw|sw|cache
> |tracepoint|pmu|event_glob]' in order to show the raw-dump of a
> certain kind of events rather than all of the events.
>
> Example:
>
> Before this patch:
>
>
The IRQ line connected to the DBGU UART is often shared with a timer device
which request the IRQ with IRQF_NO_SUSPEND.
Since the UART driver is correctly disabling IRQs when entering suspend
we can safely request the IRQ with IRQF_COND_SUSPEND so that irq core
will not complain about mixing IRQF_N
Current approach in handling shadow memory for modules is broken.
Shadow memory could be freed only after memory shadow corresponds
it is no longer used.
vfree() called from interrupt context could use memory its
freeing to store 'struct llist_node' in it:
void vfree(const void *addr)
{
...
The watchdog interrupt (only used when activating software watchdog)
shouldn't be suspended when entering suspend mode, because it is shared
with a timer device (which request the line with IRQF_NO_SUSPEND) and once
the watchdog "Mode Register" has been written, it cannot be changed (which
means we
include/linux/moduleloader.h is more suitable place for this macro.
Also change alignment to PAGE_SIZE for CONFIG_KASAN=n as such
alignment already assumed in several places.
Signed-off-by: Andrey Ryabinin
Cc: Dmitry Vyukov
Cc: Rusty Russell
---
include/linux/kasan.h| 4
include/l
Commit cab303be91dc47942bc25de33dc1140123540800 [1] introduced a WARN_ON
test which triggers a WARNING backtrace on at91 platforms.
While this WARN_ON is absolutely necessary to warn users that they should
not mix request with and without IRQF_NO_SUSPEND flags on shared IRQs,
there is no easy way t
On Thu, Feb 26, 2015 at 08:48:00AM -0800, Greg KH wrote:
> On Thu, Feb 26, 2015 at 10:44:00AM +0530, Sudip Mukherjee wrote:
> > On Wed, Feb 25, 2015 at 08:33:41PM -0800, Greg KH wrote:
> > > On Thu, Feb 26, 2015 at 09:57:31AM +0530, Sudip Mukherjee wrote:
> > >
> > > I suggest updating your person
2015-02-25 22:55-0300, Marcelo Tosatti:
> > 1) when we have no x2APIC ID 0xff00, but send x2APIC message there
>
> 10.7 SYSTEM AND APIC BUS ARBITRATION
>
> Note that except for the SIPI IPI (see Section 10.6.1, “Interrupt
> Command Register (ICR)”), all bus messages that fail to be delivered
The IRQ line used by the RTC device is usually shared with the system timer
(PIT) on at91 platforms.
Since timers are registering their handlers with IRQF_NO_SUSPEND, we should
expect being called in suspended state, and properly wake the system up
when this is the case.
Set IRQF_COND_SUSPEND flag
ADLINK's MS Windows drivers for the PCI-6208/6216 boards include the
following line in the DDInstall secion of the INF file:
%String6208%=DriverInstall6208.NT,PCI\VEN_10B5&DEV_9050&SUBSYS_6208
That's for a PLX PCI 9050/9052 PCI interface chip with custom subvendor
and subdevice ID. The "%Str
The irq line used by the PMC block is shared with several peripherals
including the init timer which is registering its handler with
IRQF_NO_SUSPEND.
Implement the appropriate suspend/resume callback for the PMC irqchip,
and inform irq core that PMC irq handler can be safely called while
the system
The IRQ line used by the RTC device is usually shared with the system
timer (PIT) on at91 platforms.
Since timers are registering their handlers with IRQF_NO_SUSPEND, we
should expect being called in suspended state, and properly wake the
system up when this is the case.
Set IRQF_COND_SUSPEND flag
Export pm_system_wakeup function to allow irq handlers to deal with system
wakeup.
This is needed for shared IRQ lines where one of the handler is registered
with IRQF_NO_SUSPEND, while the other ones want to configure it as a wakeup
source.
In this specific case, irq core does not handle the wakeu
By making use of the restart_handler chain mechanism, the SLCR-based
reset mechanism can be prioritized amongst other mechanisms available on
a particular board.
Choose a default high-ish priority of 192 for this restart mechanism.
Signed-off-by: Josh Cartwright
---
v1 -> v2: Also drop zynq_slcr
This driver module now only supports a single board type, so remove the
infrastructure for describing multiple board types. The comedi
"auto_attach" handler, `pci6208_auto_attach()` doesn't need to set the
comedi device's `board_name` or `board_ptr` members. The former is
automatically pointed to
Hi Roger,
On Fri, Feb 27, 2015 at 11:24 AM, Roger Quadros wrote:
>> + /* is child a common bus? */
>> + if (of_match_node(of_default_bus_match_table, child))
>> + /* create children and other common bus children */
>> + if (of_platform_populate(child, of_default_bu
The driver uses the wrong PCI device ID for the PCI-6216. In reality,
it has the same device ID as the PCI-6208 (and the subdevice ID's don't
help either). This results in only the first 8 digital output channels
of the PCI-6216 being useable.
This series of patches treats the PCI-6208 and PCI-6
This module's PCI device table has separate PCI device IDs for PCI-6208
and PCI-6216, but in reality, both boards and their cPCI and PCIe
variants seem to have the same PCI device ID: 0x6208. The PCI subdevice
ID doesn't seem to help either.
It shouldn't do any harm to claim 16 AO channels for al
Remove bias offset to find probe point by address.
Without this patch, probe points on kernel and executables
are shown correctly, but not work with libraries.
-
# ./perf probe -l
probe:do_fork(on do_fork@kernel/fork.c)
probe_libc:malloc(on malloc in /usr/lib64/libc-2.1
- fix typo
- improve explanation
- add reference to the related document
Signed-off-by: Tomasz Nowicki
---
arch/x86/include/asm/pci_x86.h | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/arch/x86/include/asm/pci_x86.h b/arch/x86/include/asm/pci_x86.h
index 164e3f8..ed
This patch is the first step for MMCONFIG refactoring process.
Code that uses pci_mmcfg_lock will be moved to common file and become
accessible for all architectures. pci_mmconfig_insert() cannot be moved
so easily since it is mixing generic mmconfig code with x86 specific logic
inside of mutual e
MCFG ACPI table and PCI ECAM standard have no arch dependencies so it can be
used across all architectures. Currently MMCONFIG related code resides in
arch/x86 directories. This patch set is going to isolate non-architecure
specific code and make it accessible for all architectures.
v1 -> v2 chang
This commit is consequence of making x86 MMCONFIG code available for all
architectures. Current code has old name fashion so for the sake of
making it more understandable and express where it comes from,
we are changing functions/variables/macros etc. names *mmconfig* -> *ecam*
Signed-off-by: Toma
This kthread is not loop at all due to break at the end of the loop.
Make that function linear, with no while loop.
And remove an unnecessary cast.
Signed-off-by: Jiri Slaby
---
drivers/scsi/bfa/bfad.c | 22 +-
1 file changed, 9 insertions(+), 13 deletions(-)
diff --git a/d
Those two functions are required by ACPI subsystem to make PCI config
space accessible. Generic code assume to do nothing for early init call but
late init call does as follow:
- parse MCFG table and add regions to ECAM resource list
- map regions
- add regions to iomem_resource
Signed-off-by: Tom
Sorry for the late response. Got dragged away.
On 02/24/2015 10:06 PM, Jeff Layton wrote:
> On Tue, 24 Feb 2015 16:58:26 +0100
> Daniel Wagner wrote:
>
>> On 02/20/2015 05:05 PM, Andi Kleen wrote:
>>> Daniel Wagner writes:
I am looking at how to get rid of lglock. Reason being -rt is
>From now on, readb()/writeb()/etc. generic calls are used as default
approach. Special MMIO accessors are registered for AMD Fam10h CPUs only.
Signed-off-by: Tomasz Nowicki
---
arch/x86/include/asm/pci_x86.h | 8 +++
arch/x86/pci/mmconfig-shared.c | 114 +++
mmconfig_64.c version is going to be default implementation for arch
agnostic low-level direct PCI config space accessors for ECAM dirver.
However, now it initialize raw_pci_ext_ops pointer which is x86 specific
code only. Moreover, mmconfig_32.c is doing the same thing at the same time.
Move it t
Architectures which want to take advantage of ECAM generic goodness
should select CONFIG_PCI_ECAM_GENERIC. Otherwise, like x86 32bits machines,
are obligated to provide own low-level ECAM calls.
Signed-off-by: Tomasz Nowicki
---
arch/x86/Kconfig | 1 +
arch/x86/pci/Makefile |
MCFG can be used perfectly for all architectures which support ACPI.
ACPI mandates MCFG to describe PCI config space ranges which means
we should use MMCONFIG accessors by default.
Signed-off-by: Tomasz Nowicki
---
drivers/acpi/mcfg.c | 20
1 file changed, 20 insertions(+)
ECAM standard and MCFG table are architecture independent and it makes
sense to share common code across all architectures. Both are going to
corresponding files - ecam.c and mcfg.c
While we are here, rename pci_parse_mcfg to acpi_parse_mcfg.
We already have acpi_parse_mcfg prototype which is used
On 27/02/15 14:45, Juergen Gross wrote:
> Commit 054954eb051f35e74b75a566a96fe756015352c8 ("xen: switch to
> linear virtual mapped sparse p2m list") introduced an error.
>
> During initialization of the p2m list a p2m identity area mapped by
> a complete identity pmd entry has to be split up into
This effectively unexports set_memory_ro and set_memory_rw functions, and
thus reverts a03352d2c1dc ("x86: export set_memory_ro and set_memory_rw").
They have been introduced for debugging purposes in e1000e, but no module
user is in mainline kernel (anymore?) and we explicitly do not want modules
Hi,
I have the same problem with a Asrock Q1900B-ITX mainboard with
a Intel Celeron J1900 onboard.
I did a bisect and ended up with:
593669c2ac0fe18baee04a3cd5539a148aa48574 is the first bad commit
commit 593669c2ac0fe18baee04a3cd5539a148aa48574
Author: Jiang Liu
Date: Thu Feb 5 13:44:46
This effectively unexports set_memory_ro and set_memory_rw functions from
commit 11d91a770f1f ("arm64: Add CONFIG_DEBUG_SET_MODULE_RONX support").
No module user of those is in mainline kernel and we explicitly do not want
modules to use these functions, as they i.e. protect eBPF (interpreted and
On Thu, Feb 26, 2015 at 11:58:39PM -0300, Alberto Pires de Oliveira Neto wrote:
> very sorry for the html patch. It was my first one.
this should not be your commit message. Your commit message should say about
your patch. This can be written as a comment after ---
regards
sudip
>
> Signed-of
Hello,
With kernel 3.15, I do not recall having any issues, with 3.19, I am getting
a kernel crash when I copy files over NFS from machine A to B.
Is this a known issue?
I suspect it has to do something with this:
Feb 27 09:31:20 remote-host [ 15.745342] dmar: DRHD: handling fault status
reg 2
This patch fix spelling typo in printk messages.
Signed-off-by: Masanari Iida
---
arch/arc/kernel/unwind.c | 2 +-
arch/powerpc/kernel/prom.c| 2 +-
arch/powerpc/platforms/85xx/p1022_rdk.c | 4 ++--
arch/x86/kernel/test_rodata.c
On Fri, Feb 27, 2015 at 02:15:05PM +, Steven Rostedt wrote:
> On Fri, 27 Feb 2015 12:32:32 +
> Javi Merino wrote:
>
> > Hi Steve,
> >
> > On Wed, Jan 28, 2015 at 12:48:55PM +, Javi Merino wrote:
> > > Trace can now generate traces with variable element size arrays. Add
> > > support
Since 6ea22486ba46 ("tracing: Add array printing helper") trace can
traces with variable element size arrays. Add support to parse them.
Cc: Namhyung Kim
Cc: Arnaldo Carvalho de Melo
Cc: Jiri Olsa
Cc: Steven Rostedt
Signed-off-by: Javi Merino
---
tools/lib/traceevent/event-parse.c | 93
The sequence of allocating the print_arg field, calling process_arg()
and verifying that the next event delimiter is repeated twice in
process_hex() and will also be used for process_int_array(). Factor it
out to a function to avoid writing the same code again and again.
Cc: Namhyung Kim
Cc: Arn
On 02/26/2015 04:33 AM, Mark Brown wrote:
> On Tue, Feb 24, 2015 at 06:08:54PM +0200, Stanimir Varbanov wrote:
>
>> yes, there is a potential race between atomic_inc and dma callback. I
>> reordered these calls to save few checks, and now it returns to me.
>
>> I imagine few options here:
>
>>
This series add support to libtraceevent for dynamic arrays in traces.
The kernel learned to create this traces in 6ea22486ba46 ("tracing: Add
array printing helper"), which was merged for v4.0-rc1.
No changes since v5:
http://thread.gmane.org/gmane.linux.kernel/1877410/focus=1877409
Javi Merino
This patch adds bcmgenet_tx_poll for all active tx_rings. It can reduce
the interrupt load and send xmit in upper network stack on time.
The bcmgenet_tx_reclaim of tx_ring[{0,1,2,3}] process only under 18
descriptors is to late reclaiming transmitted skb. Therefore,
performance degradation of xmit
On Fri, Feb 27, 2015 at 10:32:39PM +1030, Rusty Russell wrote:
> Peter Zijlstra writes:
> > One of the users of this is __kernel_text_address() which is employed in
> > many stack unwinders; which in turn are used by perf-callchain (possibly
> > from NMI context).
>
> Um, so the stack unwinders u
On Fri, 27 Feb 2015 10:08:30 +0100
Peter Zijlstra wrote:
> On Thu, Feb 26, 2015 at 11:26:35AM -0500, Steven Rostedt wrote:
> > Index: linux-rt.git/kernel/sched/rt.c
> > ===
> > --- linux-rt.git.orig/kernel/sched/rt.c 2015-02-26 1
Hello.
On 2/27/2015 5:17 PM, Robert Abel wrote:
Documentation/kernel-doc-nano-HOWTO.txt requires colons after the
parameter names, doesn't it?
Jesus Christ, you guys are killing me...
I've already spent way more time on this patch series than I intended
to anyway...
That's what you
Hi Shannon,
On 2015年02月27日 19:22, Shannon Zhao wrote:
On 2015/2/25 16:40, Hanjun Guo wrote:
+Not yet implemented are:
+
+ -- Section 10: power source and power meter devices
+
+ -- Section 11: thermal management
+
+ -- Section 12: embedded controllers interface
+
+ -- Se
On Thu, Feb 26, 2015 at 4:06 PM, Sergei Shtylyov
wrote:
>Documentation/kernel-doc-nano-HOWTO.txt requires colons after the
> parameter names, doesn't it?
Jesus Christ, you guys are killing me...
I've already spent way more time on this patch series than I intended
to anyway...
>> + mas
On Fri, 27 Feb 2015 12:32:32 +
Javi Merino wrote:
> Hi Steve,
>
> On Wed, Jan 28, 2015 at 12:48:55PM +, Javi Merino wrote:
> > Trace can now generate traces with variable element size arrays. Add
> > support to parse them.
> >
> > Cc: Namhyung Kim
> > Cc: Arnaldo Carvalho de Melo
> >
The chipidea driver adds an extra line of spam to the log when a
host-only chipidea instance is left set to the default of a dual role
controller.
[2.010873] ci_hdrc ci_hdrc.1: doesn't support gadget
Set the dr_mode property to host on all the host-only nodes
to avoid this warning.
Signed-of
Hi Roger,
On Fri, Feb 27, 2015 at 11:43 AM, Roger Quadros wrote:
>> time_ns_min = gpmc_ticks_to_ns(l ? l - 1 : 0);
>
> should be
> time_ns_min = l ? gpmc_ticks_to_ns(l - 1) + 1 : 0;
That's a micro-optimization.
>
> + 1ns since we don't want to fall in
401 - 500 of 685 matches
Mail list logo
