On Wed, Jun 10, 2015 at 03:21:35PM +0200, Pavel Machek wrote:
> On Wed 2015-06-10 07:06:15, Josh Poimboeuf wrote:
> > Fix the following asmvalidate warnings:
> >
> >asmvalidate: arch/x86/kernel/acpi/wakeup_64.o: wakeup_long64()+0x15:
> > unsupported jump to outside of function
> >
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
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
The NTB drivers currently support only one hardware driver, and one
client type. This patch set adds an abstraction layer, enabling
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
tagged ntb-abh-v4
This is a simple debugging driver that enables the doorbell and
scratch pad 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 is a simple ping pong driver that exercises the scratch pads 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
From: Dave Jiang
Instead of using the platform code names, use the correct platform names
to identify the respective Intel NTB hardware.
Signed-off-by: Dave Jiang
---
Documentation/ntb.txt | 20 +-
drivers/ntb/hw/intel/ntb_hw_intel.c | 620 ++--
Hi
On Tue, Jun 9, 2015 at 10:59 PM, Sergei Zviagintsev wrote:
> Fix type conversion and style issues in item macros.
>
> First submission was in 2 separate emails:
> https://lkml.kernel.org/g/1433414370-17557-1-git-send-email-ser...@s15v.net
>
Hi
On Tue, Jun 9, 2015 at 11:00 PM, Sergei Zviagintsev wrote:
> Enclose all arguments into parentheses to stay consistent across the
> whole macro.
>
> Signed-off-by: Sergei Zviagintsev
> ---
> samples/kdbus/kdbus-api.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by:
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
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
earlyprintk messages are not appearing on the terminal
emulator during a big endian kernel boot. If we
byte swap the sending data it comes properly.
Signed-off-by: Arun Chandran
---
---
This can be tested by adding 'early_print("early print test\n");'
to setup_arch() in arch/arm/kernel/setup.c
From: Dave Jiang
Set errata flags for the specific device IDs to which they apply,
instead of the whole Xeon hardware class.
Signed-off-by: Dave Jiang
---
drivers/ntb/hw/intel/ntb_hw_intel.c | 49 +
1 file changed, 44 insertions(+), 5 deletions(-)
diff
From: Dave Jiang
Link training should be enabled in the driver probe for root port mode.
We should not have to wait for transport to be loaded for this to
happen. Otherwise the ntb device will not show up on the transparent
bridge side of the link.
Signed-off-by: Dave Jiang
---
Hi
On Tue, Jun 9, 2015 at 11:00 PM, Sergei Zviagintsev wrote:
> `item' argument in KDBUS_ITEM_NEXT macro is not enclosed into
> parentheses when the cast operator is applied, which leads to improper
> type conversion if `item' is supplied as a complex expression, e.g.
>
>
From: Dave Jiang
The transport was writing and then reading the peer scratch pad,
essentially reading what it just wrote instead of exchanging any
information with the peer. The transport expects the peer values to be
the same as the local values, so this issue was not obvious.
Signed-off-by:
This patch only moves files to their new locations, before applying the
next two patches adding the NTB Abstraction layer. Splitting this patch
from the next is intended make distinct which code is changed only due
to moving the files, versus which are substantial code changes in adding
the NTB
tsin2 channel can be configured for either serial or parallel data
transfer. This patch adds the pinctrl config for both possibilities.
Signed-off-by: Peter Griffin
---
arch/arm/boot/dts/stih407-pinctrl.dtsi | 28
1 file changed, 28 insertions(+)
diff --git
On Wed, Jun 10, 2015 at 03:19:14PM +0200, Pavel Machek wrote:
> Hi!
>
> > Fix the following asmvalidate warnings:
> >
> >asmvalidate: arch/x86/kernel/acpi/wakeup_64.o: wakeup_long64()+0x15:
> > unsupported jump to outside of function
> >asmvalidate: arch/x86/kernel/acpi/wakeup_64.o:
tsin1 channel can be configured for either serial or parallel data
transfer. This patch adds the pinctrl config for both possibilities.
Signed-off-by: Peter Griffin
---
arch/arm/boot/dts/stih407-pinctrl.dtsi | 28
1 file changed, 28 insertions(+)
diff --git
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
On Wed, 10 Jun 2015 11:07:24 +0200
Peter Zijlstra wrote:
> > Not to mention, tasks in TASK_UNINTERRUPTIBLE state for too long will
> > trigger hung task detection.
>
> Right, and I had not considered that, but it turns out the hung_task
> detector checks p->state == TASK_UNINTERRUPTIBLE, so
Hi
On Tue, Jun 9, 2015 at 11:00 PM, Sergei Zviagintsev wrote:
> Signed-off-by: Sergei Zviagintsev
> ---
> samples/kdbus/kdbus-api.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: David Herrmann
Thanks
David
> diff --git a/samples/kdbus/kdbus-api.h
Hi
On Tue, Jun 9, 2015 at 11:00 PM, Sergei Zviagintsev wrote:
> `item' argument in KDBUS_ITEM_NEXT macro is not enclosed into
> parentheses when the cast operator is applied, which leads to improper
> type conversion if `item' is supplied as a complex expression, e.g.
>
>
From: Dave Jiang
Changing the memory window BAR mappings to write combining significantly
boosts the performance. We will also use memcpy that uses non-temporal
store, which showed performance improvement when doing non-cached
memcpys.
Signed-off-by: Dave Jiang
---
Added #ifdef
Hi Daniel,
On 9 June 2015 at 19:37, Daniel Thompson wrote:
> On 09/06/15 16:01, Russell King - ARM Linux wrote:
>>
>> On Tue, Jun 09, 2015 at 12:41:50PM +0100, Daniel Thompson wrote:
>>>
>>> Does the following patch, which makes the arch_irqs_disabled()
>>> implementation from asm-generic
tsin3 channel can only be configured for serial data transfer.
On B2120 reference design tsin3 is brought out as TSB on the NIMB
slot of the B2004A daughter board.
Signed-off-by: Peter Griffin
---
arch/arm/boot/dts/stih407-pinctrl.dtsi | 12
1 file changed, 12 insertions(+)
diff
Hi
On Tue, Jun 9, 2015 at 11:00 PM, Sergei Zviagintsev wrote:
> Enclose all arguments into parentheses in KDBUS_ITEM_FOREACH and
> KDBUS_FOREACH macros to stay consistent across the whole macro.
>
> Signed-off-by: Sergei Zviagintsev
> ---
> tools/testing/selftests/kdbus/kdbus-util.h | 8
+Tony
On Wed, Jun 10, 2015 at 2:11 AM, Ricardo Ribalda Delgado
wrote:
> Hi Kevin, Hi Grant, Hi Greg
>
> Although I do not agree with everything exposed by Grant, I understand
> his concerns as a Maintainer with future support of the code. Also
> there is no point in wasting more energy in
tsin4 can only be configured for serial data transfer. However
depending on board design, two alternate pin configurations
are available. One in pin-controller-front0 and the other in
pin-controller-front1.
pinctrl_tsin4_serial_alt3 is brought out on B2120 reference
design as TSC on NIMA slot of
Hi
On Tue, Jun 9, 2015 at 11:00 PM, Sergei Zviagintsev wrote:
> Signed-off-by: Sergei Zviagintsev
> ---
> tools/testing/selftests/kdbus/kdbus-enum.h | 1 +
> tools/testing/selftests/kdbus/kdbus-util.c | 2 +-
> tools/testing/selftests/kdbus/kdbus-util.h | 21 +
> 3 files
tsout1 channel can only be configured for serial data tranfer.
Signed-off-by: Peter Griffin
---
arch/arm/boot/dts/stih407-pinctrl.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/stih407-pinctrl.dtsi
b/arch/arm/boot/dts/stih407-pinctrl.dtsi
index
On Wed, 2015-06-10 at 02:08 +0200, Rafael J. Wysocki wrote:
> On Tuesday, June 09, 2015 01:42:00 AM Rafael J. Wysocki wrote:
> > On Monday, June 01, 2015 05:47:57 PM Andy Shevchenko wrote:
> > > From: Heikki Krogerus
> > >
> > > If the parent is still suspended when driver probe is
> > >
tsout0 channel can be configured for either serial or parallel
data transfer. Both pin configurations are provided.
Signed-off-by: Peter Griffin
---
arch/arm/boot/dts/stih407-pinctrl.dtsi | 28
1 file changed, 28 insertions(+)
diff --git
Hi,
On Mon, Jun 08, 2015 at 11:53:45AM +0200, Uwe Kleine-König wrote:
> Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions)
> which appeared in v3.17-rc1, the gpiod_get* functions take an additional
> parameter that allows to specify direction and initial value for output.
>
tsin5 can only be configured for serial data transfer. However
depending on board design, two alternate tsin5 pin configurations
are available, both in pin-controller-front0.
pinctrl_tsin5_serial_alt1 is brought out on B2120 reference
design as TSD on NIMB slot of the B2004A daughter board.
mtsin0 channel can only be configured for parallel data transfer.
Signed-off-by: Peter Griffin
---
arch/arm/boot/dts/stih407-pinctrl.dtsi | 19 +++
1 file changed, 19 insertions(+)
diff --git a/arch/arm/boot/dts/stih407-pinctrl.dtsi
b/arch/arm/boot/dts/stih407-pinctrl.dtsi
On 06/10/2015 12:44 AM, Romain Francoise wrote:
Hi,
On Tue, Jun 09, 2015 at 11:42:29AM -0600, Jens Axboe wrote:
There are a few options to handle this. The attached might work, not
tested at all. Basically it adds an io sched registration hook, that is
called when we are adding the disk on the
Hi folks,
This set adds in the necessary DT pinctrl configuration for the transport stream
input channels, transport stream output channels and merged transport stream
input
channels for STiH407 family silicon.
Some of these channels have alternate pinctrl configurations depending on the
board
tsin0 and be configured as either serial or parallel. This patch
adds the pinctrl config for both possiblities. On B2120 reference
design tsin0 is brought out as TSA on the NIMA slot of the B2004A
daughter board.
Signed-off-by: Peter Griffin
---
arch/arm/boot/dts/stih407-pinctrl.dtsi | 28
Hi
On Tue, Jun 9, 2015 at 11:00 PM, Sergei Zviagintsev wrote:
> Enclose all arguments into parentheses to stay consistent across the
> whole macro.
>
> Signed-off-by: Sergei Zviagintsev
> ---
> Documentation/kdbus/kdbus.item.xml | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>
Hi
On Tue, Jun 9, 2015 at 11:00 PM, Sergei Zviagintsev wrote:
> `item' argument in KDBUS_ITEM_NEXT macro example is not enclosed into
> parentheses when the cast operator is applied, which leads to improper
> type conversion if `item' is supplied as a complex expression, e.g.
>
>
On 06/10/2015 03:00 AM, Richard Weinberger wrote:
On Wed, Jun 10, 2015 at 5:33 AM, Goldwyn Rodrigues wrote:
David Lang has already responded: The idea is to use a RAID device
(currently only level 1 mirroring is supported) with multiple nodes of the
cluster.
Here is a description on how to
Hi Nicolas,
On Wed, 10 Jun 2015 15:42:44 +0200
Nicolas Ferre wrote:
> As some more information is added to the PCR register, we'd better use
> a copy of its content and modify just the peripheral-related bits.
> Implement a read-modify-write for the enable() and disable() callbacks.
>
> Header
From: Fu Wei
This driver adds support for parsing SBSA Generic Watchdog
Structure in GTDT, and creating a platform device with that
information. This allows the operating system to obtain device
data from the resource of platform device.
The platform device named "sbsa-gwdt" can be used by the
On Wed, Jun 10, 2015 at 03:08:14PM +0200, Andi Kleen wrote:
>
> > 2. Each callable function must never leave its own bounds (i.e. with a
> >jump to outside the function) except when returning.
>
> That prevents a lot of optimizations with out of line code.
In most cases there are ways to
When aborting volatile_writes, let's drop its flag and give up any further
volatile_writes.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/file.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index 096e08c..53c1b74 100644
--- a/fs/f2fs/file.c
On 06/03/2015 07:05 PM, Kirill A. Shutemov wrote:
We're going to allow mapping of individual 4k pages of THP compound.
It means we need to track mapcount on per small page basis.
Straight-forward approach is to use ->_mapcount in all subpages to track
how many time this subpage is mapped with
Hi
On Tue, Jun 9, 2015 at 11:00 PM, Sergei Zviagintsev wrote:
> Enclose all arguments into parentheses to stay consistent across the
> whole macro.
>
> Signed-off-by: Sergei Zviagintsev
> ---
> ipc/kdbus/item.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: David
Hi
On Tue, Jun 9, 2015 at 10:59 PM, Sergei Zviagintsev wrote:
> `_i' argument in KDBUS_ITEM_NEXT and KDBUS_ITEMS_END macros is not
> enclosed into parentheses when the cast operator is applied, which
> leads to improper type conversion if `_i' is supplied as a complex
> expression, e.g.
>
>
From: Fu Wei
The patch update arm_arch_timer driver to use the function
provided by the new GTDT driver of ACPI.
By this way, arm_arch_timer.c can be simplified, and separate
all the ACPI GTDT knowledge from this timer driver.
Signed-off-by: Fu Wei
Signed-off-by: Hanjun Guo
---
From: Fu Wei
Also update Documentation/watchdog/watchdog-kernel-api.txt to
introduce:
(1)the new elements in the watchdog_device and watchdog_ops struct;
(2)the new API "watchdog_init_timeouts"
Reasons:
(1)kernel already has two watchdog drivers are using "pretimeout":
From: Fu Wei
This patch enables ACPI GTDT support for ARM SBSA
watchdog driver automatically, if ACPI support is enabled.
Signed-off-by: Fu Wei
---
drivers/watchdog/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/watchdog/Kconfig b/drivers/watchdog/Kconfig
index
From: Fu Wei
This driver bases on linux kernel watchdog framework, and
use "pretimeout" in the framework. It supports getting timeout and
pretimeout from parameter and FDT at the driver init stage.
In first timeout, the interrupt routine run panic to save
system context.
Signed-off-by: Fu Wei
From: Fu Wei
This can be a example of adding SBSA Generic Watchdog device node
into some dts files for the Soc which contains SBSA Generic Watchdog.
Acked-by: Arnd Bergmann
Acked-by: Suravee Suthikulpanit
Tested-by: Suravee Suthikulpanit
Signed-off-by: Fu Wei
---
As some more information is added to the PCR register, we'd better use
a copy of its content and modify just the peripheral-related bits.
Implement a read-modify-write for the enable() and disable() callbacks.
Header file is also modified to have the PCR_DIV mask.
Signed-off-by: Nicolas Ferre
On Wed 2015-06-10 07:06:08, Josh Poimboeuf wrote:
> The previous version of this patch set was named "Compile-time stack
> frame pointer validation". I changed the subject from "frame pointer
> validation" to "asm code validation" because the focus of the patch set
> has changed to be less frame
From: Fu Wei
This can be a example of adding SBSA Generic Watchdog device node
into some dts files for the Soc which contains SBSA Generic Watchdog.
Acked-by: Arnd Bergmann
Signed-off-by: Fu Wei
---
arch/arm64/boot/dts/arm/foundation-v8.dts | 10 ++
1 file changed, 10 insertions(+)
From: Fu Wei
The sbsa-gwdt.txt documentation in devicetree/bindings/watchdog is for
introducing SBSA(Server Base System Architecture) Generic Watchdog
device node info into FDT.
Acked-by: Arnd Bergmann
Signed-off-by: Fu Wei
---
.../devicetree/bindings/watchdog/sbsa-gwdt.txt | 36
From: Fu Wei
This patchset:
(1)Introduce Documentation/devicetree/bindings/watchdog/sbsa-gwdt.txt
for FDT info of SBSA Generic Watchdog, and give two examples of
adding SBSA Generic Watchdog device node into the dts files:
foundation-v8.dts and amd-seattle-soc.dtsi.
Found this on serial console this morning. The machine had rebooted itself
shortly
afterwards (surprising, given I don't have panic-on-oops or similar set).
Dave
page:ea0002b0a040 count:4 mapcount:0 mapping:8800abf76ad0 index:0x0
flags:
Hi,
On Wed, Jun 10, 2015 at 10:10 PM, Javier Martinez Canillas
wrote:
> The Exynos interrupt combiner IP looses its state when the SoC enters
> into a low power state during a Suspend-to-RAM. This means that if a
> IRQ is used as a source, the interrupts for the devices are disabled
> when the
On Wed, Jun 10, 2015 at 11:12 AM, Hanjun Guo wrote:
> acpi_gpiochip_request(free)_interrupts can be used for modules,
> so export them. This also fixs a compile error when xgene-sb
> configured as kernel module.
>
> Fixes: 733cf014f020 "gpio: xgene: add ACPI support for APM X-Gene GPIO
>
On Wed, Jun 10, 2015 at 7:10 AM, Javier Martinez Canillas
wrote:
> The Exynos interrupt combiner IP looses its state when the SoC enters
> into a low power state during a Suspend-to-RAM. This means that if a
> IRQ is used as a source, the interrupts for the devices are disabled
> when the system
Be more verbose and also report ->backend_cra_name when
crypto_alloc_shash() or crypto_alloc_cipher() fail in
drbg_init_hash_kernel() or drbg_init_sym_kernel()
correspondingly.
Example
DRBG: could not allocate digest TFM handle: hmac(sha256)
Signed-off-by: Sergey Senozhatsky
---
crypto/drbg.c
mlock() allows a user to control page out of program memory, but this
comes at the cost of faulting in the entire mapping when it is
allocated. For large mappings where the entire area is not necessary
this is not ideal.
This series introduces new flags for mmap() and mlockall() that allow a
Hello,
A trivial patch.
My wifi stopped working recently, and the error message was not too
informative (at least to me):
kernel: wlp2s0: authenticate with 64:e5:99:74:dc:44
kernel: wlp2s0: send auth to 64:e5:99:74:dc:44 (try 1/3)
kernel: wlp2s0: authenticated
kernel: wlp2s0: associate with
The cost of faulting in all memory to be locked can be very high when
working with large mappings. If only portions of the mapping will be
used this can incur a high penalty for locking.
For the example of a large file, this is the usage pattern for a large
statical language model (probably
Building on the previous patch, extend mlockall() to give a process a
way to specify that pages should be locked when they are faulted in, but
that pre-faulting is not needed.
MCL_ONFAULT is preferrable to MCL_FUTURE for the use cases enumerated
in the previous patch becuase MCL_FUTURE will
Test the mmap() flag, the mlockall() flag, and ensure that mlock limits
are respected. Note that the limit test needs to be run a normal user.
Signed-off-by: Eric B Munson
Cc: Shuah Khan
Cc: Michal Hocko
Cc: linux...@kvack.org
Cc: linux-kernel@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
From: Nicholas Mc Guire
This patch has been added to the 3.12 stable tree. If you have any
objections, please let us know.
===
commit ed9244e6c534612d2b5ae47feab2f55a0d4b4ced upstream.
Fix possible unintended sign extension in unsigned MMIO loads by casting
to uint16_t in the case
Hi Miklós, Al,
Any thoughts on taking this upstream?
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
On Wed 2015-06-10 07:06:15, Josh Poimboeuf wrote:
> Fix the following asmvalidate warnings:
>
>asmvalidate: arch/x86/kernel/acpi/wakeup_64.o: wakeup_long64()+0x15:
> unsupported jump to outside of function
>asmvalidate: arch/x86/kernel/acpi/wakeup_64.o: wakeup_long64()+0x55:
>
Hi!
> Fix the following asmvalidate warnings:
>
>asmvalidate: arch/x86/kernel/acpi/wakeup_64.o: wakeup_long64()+0x15:
> unsupported jump to outside of function
>asmvalidate: arch/x86/kernel/acpi/wakeup_64.o: wakeup_long64()+0x55:
> unsupported jump to outside of function
>
I looked into switching to div64_s64() instead of the 32-bit version in
div_fp(), however, this would result in sample_ratio and core_busy returning
0 which is something we don't want.
P.
---8<---
The kernel may delay interrupts for a long time which can result in timers
being delayed. If this
On Thu, Jun 4, 2015 at 6:13 AM, Jiang Liu wrote:
> Change irq flow handler to prepare for killing the first parameter 'irq'
> of irq_flow_handler_t.
>
> Signed-off-by: Jiang Liu
Acked-by: Linus Walleij
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe
On Tue, Jun 09, 2015 at 02:54:01PM -0700, Linus Torvalds wrote:
> On Tue, Jun 9, 2015 at 2:14 PM, Dave Hansen wrote:
> >
> > The 0 cycle TLB miss was also interesting. It goes back up to something
> > reasonable if I put the mb()/mfence's back.
>
> So I've said it before, and I'll say it again:
The Exynos interrupt combiner IP looses its state when the SoC enters
into a low power state during a Suspend-to-RAM. This means that if a
IRQ is used as a source, the interrupts for the devices are disabled
when the system is resumed from a sleep state so are not triggered.
Save the interrupt
> After fixing the version string in patch 5 as mentioned there, and added
> the acks from Ludovic for the previous version.
>
> Applied to for-next, thanks!
And unrelated to your series, just in case you feel like it, my code checkers
say:
drivers/i2c/busses/i2c-at91.c:213: style: Checking if
On Sun, May 31, 2015 at 6:06 AM, Greg Kroah-Hartman
wrote:
> On Thu, May 28, 2015 at 03:06:57PM +0300, Dmitry Kalinkin wrote:
>> The first item in this submission documents previously introduced
>> vme_master_mmap() call. Following, there are three fixes for the tsi148
>> driver's DMA. There was
On a large system with many cores, massive creation or destruction
of processes/threads can sometime cause a fair amount of spinlock
contention in the pgd_lock used by the pgd_alloc() and pgd_free()
functions. This patch tries to reduce false cacheline sharing by
putting the pgd_lock in its own
> 2. Each callable function must never leave its own bounds (i.e. with a
>jump to outside the function) except when returning.
That prevents a lot of optimizations with out of line code.
In fact even gcc with the right options can generate code that violates
this. Standard Linux
ire
---
Can't really determine what the right fix for this would be - someone
that knows this driver would need to check - in any case the current
code seems broken.
Patch was compile tested with x86_64_defconfig + CONFIG_DRM_I2C_SIL164=m
Patch is against 4.1-rc7 (localversion-next is -next-20150
If a driver requests a GPIO described in its _CRS but the GPIO host
controller (gpiochip) driver providing the GPIO has not been loaded yet
acpi_get_gpiod() returns -ENODEV which causes the calling driver to fail.
If the gpiochip driver is loaded afterwards the driver requesting the GPIO
will not
On Wed, Jun 10, 2015 at 11:58:40AM +0100, Peter Zijlstra wrote:
> On Wed, Jun 10, 2015 at 09:34:18AM +, Vineet Gupta wrote:
> > On Tuesday 09 June 2015 06:10 PM, Peter Zijlstra wrote:
> I think the most interesting part is the device side.
>
> > >> +/*
> > >> + * DSYNC:
> > >> + * - Waits
On Mon, Jun 8, 2015 at 11:53 AM, Uwe Kleine-König
wrote:
> Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions)
> which appeared in v3.17-rc1, the gpiod_get* functions take an additional
> parameter that allows to specify direction and initial value for output.
>
> Use this to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/08/2015, 10:33 AM, James Hogan wrote:
> Hi stable folk,
>
> On 08/05/15 15:16, James Hogan wrote:
>> On 07/05/15 13:47, Nicholas Mc Guire wrote:
>>> Fix possible unintended sign extension in unsigned MMIO loads
>>> by casting to uint16_t in
On Tue, Jun 09, 2015 at 06:22:13PM +0200, Cyrille Pitchen wrote:
> ChangeLog
>
> v6:
> - replace "at91sama5d2" by "sama5d2".
>
> v5:
> - print I2C controller version in an already existing dev_info() instead of
> adding a new one.
>
> v4:
> - replace 0x%x by %#x when printing I2C controller
Hi,
I just stumbled upon:
a9edc8809328 ("x86/nmi: Perform a safe NMI stack trace on all CPUs")
Which is not dissimilar to what I've proposed in the past. Except its
squirreled away in some far and dark corner of one arch.
Lets fix that.
---
arch/Kconfig | 4 ++
Check for being stuck in a loop. That can happen if a
decoder error results in the decoder erroneously setting
the ip to an address that is itself in an infinite loop
that consumes no packets. The only way to be in a loop
that consumes no packets is if it consists of unconditional
branches. So
To help synchronize trace data with sideband events
the timestamp when returning to userspace is estimated.
That was not always being done if switch information
was not available, but it is still useful for sync'ing
to mmap changes, so simplify by doing it always when
TSC is available. Also add
Hi
Here are a couple more patches for Intel PT. They
apply on top of the patches already sent. The
whole lot can be found here:
http://git.infradead.org/users/ahunter/linux-perf.git
Adrian Hunter (2):
perf tools: Improve Intel PT sync to sideband events
perf tools: Fix
At Wed, 10 Jun 2015 14:33:42 +0200,
Takashi Iwai wrote:
>
> At Wed, 10 Jun 2015 14:45:51 +0300,
> Mihai Donțu wrote:
> >
> > On Wed, 10 Jun 2015 12:50:22 +0200 Takashi Iwai wrote:
> > > At Wed, 10 Jun 2015 13:41:35 +0300, Mihai Donțu wrote:
> > > > On Wed, 10 Jun 2015 12:22:53 +0200 Takashi Iwai
Greetings,
Like so...
#include
#include
#include
#include
int sys_futex(void *addr1, int op, int val1, struct timespec *timeout, void
*addr2, int val3)
{
return syscall(SYS_futex, addr1, op, val1, timeout, addr2, val3);
}
int main()
{
struct timespec t;
int f =
On Tue, Jun 9, 2015 at 8:26 PM, Rob Herring wrote:
> set_irq_flags is ARM specific with custom flags which have genirq
> equivalents. Convert drivers to use the genirq interfaces directly, so we
> can kill off set_irq_flags. The translation of flags is as follows:
>
> IRQF_VALID ->
On Tue, Jun 9, 2015 at 8:26 PM, Rob Herring wrote:
> set_irq_flags is ARM specific with custom flags which have genirq
> equivalents. Convert drivers to use the genirq interfaces directly, so we
> can kill off set_irq_flags. The translation of flags is as follows:
>
> IRQF_VALID ->
On Tue, Jun 9, 2015 at 8:26 PM, Rob Herring wrote:
> set_irq_flags is ARM specific with custom flags which have genirq
> equivalents. Convert drivers to use the genirq interfaces directly, so we
> can kill off set_irq_flags. The translation of flags is as follows:
>
> IRQF_VALID ->
Please read the attached letter and immediately contact the bank for your
draft/cheque claim.
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
United Nations Compensation Unit.pdf
Description: Adobe PDF document
From: Corey Minyard
The IPMI SI driver was using direct PNP, but that was not really
ideal because the IPMI device is a platform device. There was
some special handling in the acpi_pnp.c code for making this work,
but that was breaking ACPI handling for the IPMI SSIF driver.
So use a platform
On Wed, Jun 10, 2015 at 12:25:54PM -, vigne...@codeaurora.org wrote:
> Gentle reminder for review comments.
I don't see anything wrong with the patch... but it needs to find its
way into the patch system to be applied, so it doesn't get forgotten.
Please add it there along with Laura's
701 - 800 of 2166 matches
Mail list logo
