Again, these tests could be more complicated but at least it gets
the very basics covered.
Signed-off-by: Olof Johansson
---
.../merge_config_test/12-cmdline-success.sh| 13 +
.../merge_config_test/13-cmdline-failure.sh| 13 +
Treat CONFIG_FOO=.. on the command line the same way as a single-entry file
would.
Signed-off-by: Olof Johansson
---
scripts/kconfig/merge_config.sh | 29 -
1 file changed, 24 insertions(+), 5 deletions(-)
diff --git a/scripts/kconfig/merge_config.sh
On Wed, May 20, 2015 at 12:57 PM, Malte Schröder wrote:
> On 05/20/15 17:37, Alex Deucher wrote:
>> On Tue, May 19, 2015 at 6:03 PM, Malte Schröder wrote:
>>> Hi,
>>> with 4.1-rc display-port on my Tahiti XT stopped working. I used the
>>> firmware from
Exit with non-0 value in cases where there was a failure to set an option.
Also, add a '-e' during which the conflict warnings are considered failures
(-e -r will result in these being failures, -r will result in them just being
reported).
Signed-off-by: Olof Johansson
---
Kconfig knows how to handle CONFIG_FOO=n just fine, but it'll always
use "# CONFIG FOO is not set" in the resulting config. Mangle the input
accordingly so we don't report this as a failure when it isn't.
Signed-off-by: Olof Johansson
---
scripts/kconfig/merge_config.sh |2 +-
1 file
Okay, let's go with it. that also let us merge this constant with the length of
the array in the C header file.
On May 20, 2015 2:47:10 PM PDT, Andy Lutomirski wrote:
>On Wed, May 20, 2015 at 1:59 PM, H. Peter Anvin wrote:
>> On 05/20/2015 01:53 PM, Andy Lutomirski wrote:
>>> Egads. Now I
Regulator stuff copied from imx6qdl-tx6.dtsi, pin configuration
taken from Boundary Devices linux kernel tree ([1] and [2]).
[1]
https://github.com/boundarydevices/linux-imx6/blob/boundary-imx_3.10.17_1.0.2_ga/arch/arm/boot/dts/imx6qdl-nitrogen6x.dts
[2]
On Wed, May 20, 2015 at 6:20 PM, Russell King - ARM Linux
wrote:
> On Wed, May 20, 2015 at 02:57:36PM +0200, Lorenzo Nava wrote:
>> so probably currently is impossible to allocate a contiguous cachable
>> DMA memory. You can't use CMA, and the only functions which allow you
>> to use it are not
On Wed, May 20, 2015 at 1:59 PM, H. Peter Anvin wrote:
> On 05/20/2015 01:53 PM, Andy Lutomirski wrote:
>> Egads. Now I understand what that code is. I don't like the balign,
>> since this has nothing to do with alignment -- we're creating an array
>> of functions.
>
> Actually it does... we
From: Bjorn Helgaas [mailto:bhelg...@google.com]
> Please run "git log --oneline drivers/ntb" and make your subject lines
> consistent. The convention I use in PCI (and what was used in NTB
> until recently) is
>
> - Acronyms and initialisms are capitalized
> - Subject line is a subsystem
On Wed, May 20, 2015 at 10:03:45PM +0200, Stephan Mueller wrote:
>> @@ -1487,6 +1514,7 @@ unlock:
> */
> static int drbg_uninstantiate(struct drbg_state *drbg)
> {
> + cancel_work_sync(>seed_work);
This will just block until the work is done, i.e., until the
pool is ready. It's no
When trying to configure the settings for PHY1, using commands
like 'ethtool -s eth0 phyad 1 speed 100', the 'ethtool' seems to
modify other settings apart from the speed of the PHY1, in the
above case.
The ethtool seems to query the settings for PHY0, and use this
as the base to apply the new
Hi,
This patch fixes an issue while using the 'ethtool' to query/set PHY's
configurations. The 'ethtool' interface in the Kernel seem to always
query settings for PHY0, irrespective of the PHY specified, while
issuing the 'ethtool' command.
For example when issueing 'ethtool -s eth0 phyad 1
On Tue, May 19, 2015 at 09:27:50AM +0200, Rafał Miłecki wrote:
> On 19 May 2015 at 03:34, Brian Norris wrote:
> > So how about the following patch? It seems like we'll need to be able to
> > ignore useless 'modalias' values in cases like this:
> >
> > // modalias = "shinynewdevice"
> >
On Wed, May 20, 2015 at 4:57 PM, Mika Westerberg wrote:
> On Wed, May 20, 2015 at 04:07:00PM +0300, Robert Dolca wrote:
>> On Wed, May 20, 2015 at 1:57 PM, Mika Westerberg wrote:
>> > On Wed, May 20, 2015 at 01:49:02PM +0300, Robert Dolca wrote:
>> >> On Wed, May 20, 2015 at 12:48 PM, Mika
On 5/20/2015 5:28 AM, Will Deacon wrote:
On Fri, May 15, 2015 at 10:23:12PM +0100, Suravee Suthikulpanit wrote:
Currently, device drivers, which support both OF and ACPI,
need to call two separate APIs, of_dma_is_coherent() and
acpi_dma_is_coherent()) to determine device coherency attribute.
On 20/05/2015 at 07:59:10 -0700, Kevin Hilman wrote :
> > Hum, I'm pretty sure you see the heartbeat led blinking ;)
>
> I don't see anything because this is automated testing. ;)
>
I was thinking that your job was looking at those boards with blinking
LEDs while attending conference calls ;)
On Wednesday 20 May 2015 00:42:21 Stefan Agner wrote:
> On 2015-05-20 00:03, Stefan Agner wrote:
> > This is the soc part of the splitted patchset which enables Cortex-M4
> > support on Vybrid, as discussed in the thread of patchset v7.
>
> Arnd, forgot to mention that this depends on the irqchip
From: linux-...@googlegroups.com [mailto:linux-...@googlegroups.com] On Behalf
Of Jiang, Dave
> On Wed, 2015-05-20 at 16:11 -0500, Bjorn Helgaas wrote:
> > On Wed, May 20, 2015 at 10:41 AM, Allen Hubbe
> wrote:
> > > From: Dave Jiang
> > >
> > > Signed-off-by: Dave Jiang
> >
> > Needs a topic
On Wednesday 20 May 2015 00:06:22 Stefan Agner wrote:
> Add defconfig for Linux on Vybrid (vf610) on the secondary Cortex-
> M4 CPU. The use of a XIP image has been tested which needs to be
> loaded (e.g. using the custom m4boot loader) to the end of the
> available RAM at address 0x8f00. The
Similar to enable_event/disable_event triggers, these triggers enable
and disable the aggregation of events into maps rather than enabling
and disabling their writing into the trace buffer.
They can be used to automatically start and stop hist triggers based
on a matching filter condition.
If
On Tue, 2015-05-19 at 16:08 -0500, Ashley Lai wrote:
> Thank you Vicky and Joy for the clarification. This patch mainly
> converts the fields in the tcpa_event structure. I see the code converts
> everytime it accesses the event fields. Would it be more efficient if you
> do the conversion
Add tracing_map, a special-purpose lock-free map for tracing.
tracing_map is designed to aggregate or 'sum' one or more values
associated with a specific object of type tracing_map_elt, which
is associated by the map to a given key.
It provides various hooks allowing per-tracer customization and
Some triggers may need access to the trace event, so pass it in. Also
fix up the existing trigger funcs and their callers.
Signed-off-by: Tom Zanussi
---
include/linux/ftrace_event.h| 7 ---
kernel/trace/trace.h| 6 --
kernel/trace/trace_events_trigger.c | 35
This is v5 of the 'hist triggers' patchset, following feedback from
v4.
Changes from v4:
This version addresses some problems and suggestions made by Daniel
Wagner - a lot of the code was reworked to get rid of the distinction
between keys and values, and as a result, both keys and values can be
or all the
> >> sama5d[34] boards in kernelci.org have failed to boot.
> >>
> >> http://kernelci.org/boot/all/job/next/kernel/next-20150520/
> >>
> >
> > Hum, I'm pretty sure you see the heartbeat led blinking ;)
> >
> > I think I told you
Please run "git log --oneline drivers/ntb" and make your subject lines
consistent. The convention I use in PCI (and what was used in NTB
until recently) is
- Acronyms and initialisms are capitalized
- Subject line is a subsystem prefix ("PCI:", "NTB:", etc.) followed
by a complete sentence
Make is_string_field() and is_function_field() accessible outside of
trace_event_filters.c for other users of ftrace_event_fields.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace.h | 12
kernel/trace/trace_events_filter.c | 12
2 files changed, 12
Add documentation and usage examples for 'hist' triggers.
Signed-off-by: Tom Zanussi
---
Documentation/trace/events.txt | 872 +
1 file changed, 872 insertions(+)
diff --git a/Documentation/trace/events.txt b/Documentation/trace/events.txt
index
Add a simple per-trigger 'paused' flag, allowing individual triggers
to pause. We could leave it to individual triggers that need this
functionality to do it themselves, but we also want to allow other
events to control pausing, so add it to the trigger data.
Signed-off-by: Tom Zanussi
---
Add a utility function to grab the syscall name from the syscall
metadata, given a syscall id.
Signed-off-by: Tom Zanussi
---
kernel/trace/trace.h | 5 +
kernel/trace/trace_syscalls.c | 11 +++
2 files changed, 16 insertions(+)
diff --git a/kernel/trace/trace.h
Add a new tracer named function_hist:
# cat /sys/kernel/debug/tracing/available_tracers
blk mmiotrace function_hist function_graph wakeup_dl wakeup_rt wakeup
irqsoff function nop
# echo function_hist > /sys/kernel/debug/tracing/current_tracer
# cat
'hist' triggers allow users to continually aggregate trace events,
which can then be viewed afterwards by simply reading a 'hist' file
containing the aggregation in a human-readable format.
The basic idea is very simple and boils down to a mechanism whereby
trace events, rather than being
Hi,
On Wed, May 20, 2015 at 03:33:26PM -0400, Sasha Levin wrote:
> ULPI registers it's bus at module_init so if the bus fails to register, the
A minor comment: s/it's/its/
> module will fail to load and all will be well in the world.
>
> However, if the ULPI code is built-in rather than a
When a trigger is enabled, the cond flag should be set beforehand,
otherwise a trigger that's expecting to process a trace record
(e.g. one with post_trigger set) could be invoked without one.
Likewise a trigger's cond flag should be reset after it's disabled,
not before.
Signed-off-by: Tom
On Wed, May 20, 2015 at 11:00:55AM +0200, Paul Bolle wrote:
> On Wed, 2015-05-20 at 10:49 +0800, Herbert Xu wrote:
> > On Tue, May 19, 2015 at 04:05:43PM -0700, Luis R. Rodriguez wrote:
> > > Well that's be true if FW_LOADER was easy to disable, but its not. You
> > > really gotta try hard to
On Wed, 2015-05-20 at 16:11 -0500, Bjorn Helgaas wrote:
> On Wed, May 20, 2015 at 10:41 AM, Allen Hubbe wrote:
> > From: Dave Jiang
> >
> > Signed-off-by: Dave Jiang
>
> Needs a topic in the subject line and a changelog.
>
> It also seems to do a lot more than just checking device ID (I
On Wed, 20 May 2015, Vikas Shivappa wrote:
> On Wed, 20 May 2015, Thomas Gleixner wrote:
>
> > On Wed, 20 May 2015, Vikas Shivappa wrote:
> > > On Fri, 15 May 2015, Thomas Gleixner wrote:
> > > > > -static DEFINE_PER_CPU(struct intel_cqm_state, cqm_state);
> > > > > +DEFINE_PER_CPU(struct
Hey everyone,
tl;dr; pure python generic netlink library with simple clients for ipvs
and taskstats here: https://github.com/facebook/gnlpy
At Facebook we rely upon ipvs for most of our layer-4 load balancing
needs. It's mostly worked pretty great for us. The standard way to
interact with
On Wed, May 20, 2015 at 10:41 AM, Allen Hubbe wrote:
> From: Dave Jiang
>
> Signed-off-by: Dave Jiang
Needs a topic in the subject line and a changelog.
It also seems to do a lot more than just checking device ID (I assume
that's what "DID" means), so this should probably be split into
After 'uuid', 'size', and optionally 'alt_name' have been set to valid
values the labels on the dimms can be updated.
Write procedure is:
1/ Allocate and write new labels in the "next" index
2/ Free the old labels in the working copy
3/ Write the bitmap and the label space on the dimm
4/ Write
From: Ross Zwisler
The libnd implementation handles allocating dimm address space (DPA)
between PMEM and BLK mode interfaces. After DPA has been allocated from
a BLK-region to a BLK-namespace the nd_blk driver attaches to handle I/O
as a struct bio based block device. Unlike PMEM, BLK is
On Wednesday 20 May 2015 00:05:18 Stefan Agner wrote:
> This adds an initial device tree to run Linux on the Cortex-M4 on
> the Vybrid based Colibri VF61 module.
>
> Signed-off-by: Stefan Agner
Pulled into next/dt, thanks!
Arnd
--
To unsubscribe from this list: send the line
The arch independent uart8250 early console driver has good
support for memory mapped and io port based 8250 uarts. Since
pci is arch independent so it's natural to extend uart8250 to
support mem, io and pci. Hence pci uart early console in
arch/x86/kernel_printk.c by the following commit:
'commit
A libnd bus is the anchor device for registering nvdimm resources and
interfaces, for example, a character control device, nvdimm devices,
and I/O region devices. The ACPI NFIT (NVDIMM Firmware Interface Table)
is one possible platform description for such non-volatile memory
resources in a
On Wed, May 20, 2015 at 2:02 PM, Bjorn Helgaas wrote:
> On Tue, Apr 21, 2015 at 01:20:31PM -0700, Luis R. Rodriguez wrote:
>> From: "Luis R. Rodriguez"
>>
>> This lets drivers take advantage of PAT when available. This
>> should help with the transition of converting video drivers over
>> to
The control device for a libnd bus is registered as an "nd" class
device. The expectation is that there will usually only be one "nd" bus
registered under /sys/class/nd. However, we allow for the possibility
of multiple buses and they will listed in discovery order as
ndctl0...ndctlN. This
On some Intel Atom SoCs, the legacy IO port UART(0x3F8) is not available.
Instead, a 8250 compatible PCI uart can be used as early console.
This patch adds pci support to the 8250 early console driver uart8250.
For example, to enable pci uart(00:21.3) as early console on these
platforms, append
Enable dimm devices to be registered on a libnd bus. The kernel
assigned device id for dimms is dynamic. If userspace needs a more
static identifier it should consult a provider-specific attribute. In
the case where NFIT is the provider, the 'nmemX/nfit/handle' or
'nmemX/nfit/serial' attributes
On Wed, May 20, 2015 at 07:50:12PM +0200, Paul Bolle wrote:
> That makes more sense. So v4 will put HAVE_EARLY_PCI in a Kconfig under
> drivers/pci/?
>
Yes.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
nd_pmem attaches to persistent memory regions and namespaces emitted by
the libnd subsystem, and, same as the original pmem driver, presents the
system-physical-address range as a block device.
The existing e820-type-12 to pmem setup is converted to a full libnd bus
that emits an nd_namespace_io
* Implement the device-model infrastructure for loading modules and
attaching drivers to nd devices. This is a simple association of a
nd-device-type number with a driver that has a bitmask of supported
device types. To facilitate userspace bind/unbind operations 'modalias'
and
On 05/20/2015 01:53 PM, Andy Lutomirski wrote:
> Egads. Now I understand what that code is. I don't like the balign,
> since this has nothing to do with alignment -- we're creating an array
> of functions.
Actually it does... we align to the beginning of each slot. If .balign
could be
A complete label set is a PMEM-label per-dimm per-interleave-set where
all the UUIDs match and the interleave set cookie matches the hosting
interleave set.
Present sysfs attributes for manipulation of a PMEM-namespace's
'alt_name', 'uuid', and 'size' attributes. A later patch will make
these
Manually create and register NFITs to describe 2 topologies. Topology1
is an advanced plausible configuration for BLK/PMEM aliased NVDIMMs.
Topology2 is an example configuration for current platforms that only
ship with a persistent address range.
Kernel provider "nfit_test.0" produces an NFIT
On Tue, Apr 21, 2015 at 01:20:31PM -0700, Luis R. Rodriguez wrote:
> From: "Luis R. Rodriguez"
>
> This lets drivers take advantage of PAT when available. This
> should help with the transition of converting video drivers over
> to ioremap_wc() to help with the goal of eventually using
>
From: Vishal Verma
BTT stands for Block Translation Table, and is a way to provide power
fail sector atomicity semantics for block devices that have the ability
to perform byte granularity IO. It relies on the ->rw_bytes() capability
of libnd namespace devices.
The BTT works as a stacked
Block devices from an nd bus, in addition to accepting "struct bio"
based requests, also have the capability to perform byte-aligned
accesses. By default only the bio/block interface is used. However, if
another driver can make effective use of the byte-aligned capability it
can claim/disable
Maintainer information and documentation for drivers/block/nd/
Cc: Andy Lutomirski
Cc: Boaz Harrosh
Cc: H. Peter Anvin
Cc: Jens Axboe
Cc: Ingo Molnar
Cc: Christoph Hellwig
Cc: Neil Brown
Cc: Greg KH
Signed-off-by: Dan Williams
---
Documentation/blockdev/libnd.txt | 804
A blk label set describes a namespace comprised of one or more
discontiguous dpa ranges on a single dimm. They may alias with one or
more pmem interleave sets that include the given dimm.
This is the runtime/volatile configuration infrastructure for sysfs
manipulation of 'alt_name', 'uuid',
On Thu, May 21, 2015 at 02:08:09AM +0530, Afzal Mohammed wrote:
> Hi,
>
> On Sun, May 17, 2015 at 07:30:50AM +0200, Mike Galbraith wrote:
>
> > Yeah, tying nohz_full set to isolcpus set up an initial condition that
> > you have to tear down with cpusets if you want those cpus returned to
> > the
After 'uuid', 'size', 'sector_size', and optionally 'alt_name' have been
set to valid values the labels on the dimm can be updated. The
difference with the pmem case is that blk namespaces are limited to one
dimm and can cover discontiguous ranges in dpa space.
Also, after allocating label
On platforms that have firmware support for reading/writing per-dimm
label space, a portion of the dimm may be accessible via an interleave
set PMEM mapping in addition to the dimm's BLK (block-data-window
aperture(s)) interface. A label, stored in a "configuration data
region" on the dimm,
The libnd region driver is an intermediary driver that translates
non-volatile "region"s into "namespace" sub-devices that are surfaced by
persistent memory block-device drivers (PMEM and BLK).
ACPI 6 introduces the concept that a given nvdimm may simultaneously
offer multiple access modes to its
This on media label format [1] consists of two index blocks followed by
an array of labels. None of these structures are ever updated in place.
A sequence number tracks the current active index and the next one to
write, while labels are written to free slots.
++
|
From: Ross Zwisler
Dynamically allocate minor numbers for partitions instead of statically
preallocating them.
It gives us a simpler minors scheme, and makes it so we get a consistent
major when moving past partition 16. Here's what happens with the
current code:
pmem0 249:00 63.5G
A "region" device represents the maximum capacity of a BLK range (mmio
block-data-window(s)), or a PMEM range (DAX-capable persistent memory or
volatile memory), without regard for aliasing. Aliasing, in the
dimm-local address space (DPA), is resolved by metadata on a dimm to
designate which
Most discovery/configuration of the libnd-subsystem is done via sysfs
attributes. However, some libnd buses, particularly the ACPI.NFIT bus,
define a small set of messages that can be passed to the platform. For
convenience we derive the initial libnd-ioctl command formats directly
from the NFIT
Changes since v2 [1]:
1/ Rebase on the ACPICA enabling for the NFIT data structures. The
ACPICA project owns the definition of ACPI data structures in
include/acpi/. This release incorporates the NFIT and UUID definitions
from ACPICA release R05_15_15 [2]. (Rafael, Bob)
2/ Move the
ACPI 6.0 formalizes e820-type-7 and efi-type-14 as persistent memory.
Mark it "reserved" and allow it to be claimed by a persistent memory
device driver.
This definition is in addition to the Linux kernel's existing type-12
definition that was recently added in support of shipping platforms with
On Wed, May 20, 2015 at 12:53 PM, Luis R. Rodriguez wrote:
> Tomi,
>
> the new required ioremap_uc() which was added in the initial patch set here is
> now merged on linux-next but I just noticed a small issue with this atyfb
> specific patch, I'll fix that and respin and send to you as v5.
On Wed, May 20, 2015 at 03:05:41PM +0200, Enrico Weigelt, metux IT consult
wrote:
> I've rebased the IPUv3 patches from ptx folks onto 4.0.4,
> working good for me. (now gst plays h264 @25fps on imx53)
>
> https://github.com/metux/linux/commits/submit-4.0-imx53-ipuv3
>
> (Haven't 4.1rc* yet, as
* Nicholas Krause [150520 12:33]:
> This removes the deprecacted marco, PTR_RET and changes the
> functions that use this marco in their return statement to
> instead use the non deprecacted function, PTR_ERR_OR_ZERO
> for the file devices.c.
>
> Signed-off-by: Nicholas Krause
Applying into
Michal Marek writes:
> Dne 20.5.2015 v 13:19 Rusty Russell napsal(a):
>> Joe Perches writes:
>>> On Tue, 2015-05-19 at 16:56 +0100, One Thousand Gnomes wrote:
On Tue, 19 May 2015 07:46:58 +0100 David Woodhouse
wrote:
> On Mon, 2015-05-18 at 17:07 -0700, Joe Perches wrote:
>>
On Wed, May 20, 2015 at 1:32 PM, H. Peter Anvin wrote:
> On 05/20/2015 01:02 PM, Andy Lutomirski wrote:
>>>
>>> I got
>>>
>>> [hjl@gnu-tools-1 kernel.org]$ readelf -r old/vmlinux.o | head -5
>>>
>>> Relocation section '.rela.text' at offset 0xafea2f0 contains 205717 entries:
>>> Offset
On Mon, May 18, 2015 at 1:34 PM, H. Peter Anvin wrote:
> On 05/18/2015 01:28 PM, H. Peter Anvin wrote:
>>
>> OK, that is probably too recent. The simplest answer I think is just to
>> .balign 16 each vector. This is init space... some extra padding really
>> doesn't matter.
>>
>> Patch attached
On Wed, May 20, 2015 at 1:39 PM, Bjorn Helgaas wrote:
> On Tue, May 19, 2015 at 04:45:30PM -0700, Luis R. Rodriguez wrote:
>> On Tue, May 19, 2015 at 4:29 PM, David Airlie wrote:
>> >
>> >> On Tue, May 19, 2015 at 4:02 PM, Bjorn Helgaas
>> >> wrote:
>> >> > [-cc Venkatesh (bouncing)
>> >> >
>>
On Tue, May 19, 2015 at 07:19:17PM +0530, Punnaiah Choudary Kalluri wrote:
> Added the basic driver for Arasan Nand Flash Controller used in
> Zynq UltraScale+ MPSoC. It supports only Hw Ecc and upto 24bit
> correction.
>
> Signed-off-by: Punnaiah Choudary Kalluri
> Tested-by: Michal Simek
>
On Wed, May 20, 2015 at 07:00:25AM -0500, Suravee Suthikulanit wrote:
> On 5/20/2015 4:34 AM, Catalin Marinas wrote:
> >We have a dummy of_dma_configure() already when !CONFIG_OF, otherwise
> >we would need #ifndef here. I already replied, I think for other
> >architectures we need this check to
Hi Hanjun,
On 05/18/2015 02:59 PM, Hanjun Guo wrote:
Move GICv2 ACPI related init code in irq-gic.c to irq-gic-acpi.c,
this can make the ACPI related GIC init code slef-contained.
Introduce set_acpi_core_irqdomain() to set acpi_irqdomain then
it will be no need to make gic_data[] as a global
The same message "qp%d: Link Down\n" was printed at two locations in
ntb_transport. Change the messages so they are distinct.
Signed-off-by: Allen Hubbe
---
drivers/ntb/ntb_transport.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/ntb/ntb_transport.c
From: Dave Jiang
Link training for RP should be enabled in the driver probe. We should
not have to wait for transport loaded for this to hapen. Otherwise the
device will not show up on the transparent bridge side.
Signed-off-by: Dave Jiang
---
drivers/ntb/hw/intel/ntb_hw_intel.c | 10
On link down, don't advance RX index to the next entry. The next entry
should never be valid after receiving the link down flag.
Signed-off-by: Allen Hubbe
---
drivers/ntb/ntb_transport.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/ntb/ntb_transport.c
On Wed, 20 May 2015, Thomas Gleixner wrote:
On Wed, 20 May 2015, Vikas Shivappa wrote:
On Fri, 15 May 2015, Thomas Gleixner wrote:
-static DEFINE_PER_CPU(struct intel_cqm_state, cqm_state);
+DEFINE_PER_CPU(struct intel_pqr_state, pqr_state);
With CONFIG_PERF=n and CONFIG_CGROUP_RDT=y the
Allocate memory for the numa node of the ntb device.
Signed-off-by: Allen Hubbe
---
drivers/ntb/hw/intel/ntb_hw_intel.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/drivers/ntb/hw/intel/ntb_hw_intel.c
b/drivers/ntb/hw/intel/ntb_hw_intel.c
index
When the ntb transport is connecting and waiting for the peer, the debug
console receives lots of debug level messages about the remote qp link
status being down. Rate limit those messages.
Signed-off-by: Allen Hubbe
---
drivers/ntb/ntb_transport.c | 2 +-
1 file changed, 1 insertion(+), 1
Reset the link stats when the link goes down. In particular, the tx and
rx index and count must be reset, or else the tx side will be sending
packets to the rx side, where the rx side is not expecting them. Reset
all the stats, to be consistent.
Signed-off-by: Allen Hubbe
---
Allocate memory and request the dma channel for the same numa node as
the ntb device.
Signed-off-by: Allen Hubbe
---
drivers/ntb/ntb_transport.c | 46 +++--
1 file changed, 32 insertions(+), 14 deletions(-)
diff --git a/drivers/ntb/ntb_transport.c
From: Dave Jiang
Changing the memory window BAR mappings to write combining significantly
boosts the performance. We will also use memcpy that utilizies
non-temporal store which showed performance improement when doing
non-cached memcpys.
Signed-off-by: Dave Jiang
---
This is a simple pingpong driver that exercises the scratchpads and
doorbells of the ntb hardware. This driver may be used to test that
your ntb hardware and drivers are functioning at a basic level.
Signed-off-by: Allen Hubbe
---
Documentation/ntb.txt | 27 +
MAINTAINERS
Fix code format issues detected by checkpatch.pl. Fix one spelling
error, and some unnecessary whitespace after cast operators. I did not
add the comments for spinlocks, which checkpatch still reports as
missing.
Signed-off-by: Allen Hubbe
---
drivers/ntb/ntb_transport.c | 12 ++--
1
From: Dave Jiang
Disable DMA usage by default, since the CPU provides much better
performance with write combining. Provide a module parameter to enable
DMA usage when offloading the memcpy is preferred.
Signed-off-by: Dave Jiang
Signed-off-by: Allen Hubbe
---
drivers/ntb/ntb_transport.c |
This is a simple debugging driver that enables the doorbell and
scratchpad registers to be read and written from the debugfs. This
tool enables more complicated debugging to be scripted from user space.
This driver may be used to test that your ntb hardware and drivers are
functioning at a basic
This patch only serves the purpose to move files to their new locations,
before applying the next patch adding the NTB Abstraction layer.
Splitting this patch from the next is intended make distinct the which
code is changed only due to moving the files, versus which are
substantial code changes
Add module parameters for the addresses to be used in b2b topology.
Signed-off-by: Allen Hubbe
---
Documentation/ntb.txt | 10 +
drivers/ntb/hw/intel/ntb_hw_intel.c | 77 -
2 files changed, 68 insertions(+), 19 deletions(-)
diff --git
From: Dave Jiang
Signed-off-by: Dave Jiang
---
drivers/ntb/hw/intel/ntb_hw_intel.c | 196 +++-
drivers/ntb/hw/intel/ntb_hw_intel.h | 24 -
drivers/ntb/ntb_transport.c | 16 +--
3 files changed, 133 insertions(+), 103 deletions(-)
diff --git
On Wed, 20 May 2015 20:12:31 + (UTC)
Holger Kiehl wrote:
> The kernel I was running when I discovered the
> problem was 4.0.2 from kernel.org. However, after reinstalling from DVD
> I updated to Fedora's lattest kernel, which was 3.19.? (I do not remember
> the last numbers). So that kernel
The NTB drivers currently support only one hardware driver, and one client
type. This patch set adds an abstraction layer, enabling different hardware
drivers by other vendors, and clients other than ntb_transport.
The commits in this set may also be pulled from:
github.com/allenbh/linux
in the
On Tue, May 19, 2015 at 04:45:30PM -0700, Luis R. Rodriguez wrote:
> On Tue, May 19, 2015 at 4:29 PM, David Airlie wrote:
> >
> >> On Tue, May 19, 2015 at 4:02 PM, Bjorn Helgaas wrote:
> >> > [-cc Venkatesh (bouncing)
> >> >
> >> > On Tue, May 19, 2015 at 5:46 PM, Luis R. Rodriguez
> >> >
Hi,
On Sun, May 17, 2015 at 07:30:50AM +0200, Mike Galbraith wrote:
> Yeah, tying nohz_full set to isolcpus set up an initial condition that
> you have to tear down with cpusets if you want those cpus returned to
> the general purpose pool. I had considered the kernel setting initial
> state to
201 - 300 of 2350 matches
Mail list logo
