The real question is if we care that sysret and iter don't match. On 32 bits
the situation is even more complex.
On June 26, 2014 1:00:22 PM PDT, Andy Lutomirski wrote:
>On Thu, Jun 26, 2014 at 12:59 PM, Andy Lutomirski
>wrote:
>> On Thu, Jun 26, 2014 at 12:56 PM, Andi Kleen
>wrote:
Historically, we exported shared pages to userspace via sysinfo(2) sharedram
and /proc/meminfo's "MemShared" fields. With the advent of tmpfs, from kernel
v2.4 onward, that old way for accounting shared mem was deemed inaccurate and
we started to export a hard-coded 0 for sysinfo.sharedram. Later
Hi Florian,
On 26/06/2014 20:15, Florian Fainelli wrote:
> Hi Boris,
>
> 2014-06-26 3:13 GMT-07:00 Boris BREZILLON
> :
>> Add ethernet-phy node and specify phy interrupt (connected to pin PB25).
>>
>> The PHY address is not specified here because atmel have 2 different
>> designs
>> for its CPU
On Thu, Jun 26, 2014 at 12:59 PM, Andy Lutomirski wrote:
> On Thu, Jun 26, 2014 at 12:56 PM, Andi Kleen wrote:
>>> show RCX == RIP even under strace.
>>
>> If you think it's really worth the extra instruction?
>
> Hard to say. That extra instruction only happens on slow paths, so I
> suspect
On 06/25/2014 04:25 PM, Andrew Bresticker wrote:
> Thanks for the review Stephen!
>
> On Wed, Jun 25, 2014 at 2:46 PM, Stephen Warren wrote:
>> On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
>>> Add new bindings used for USB support by the Tegra XUSB pad controller.
>>> This includes
On Thu, Jun 26, 2014 at 12:56 PM, Andi Kleen wrote:
>> show RCX == RIP even under strace.
>
> If you think it's really worth the extra instruction?
Hard to say. That extra instruction only happens on slow paths, so I
suspect the slowdown is negligible. On the other hand, having syscall
show a
From: Jeff Layton
Open file description locks have been merged into the Linux kernel for
v3.15. Add the appropriate command-value definitions and an update to
the manual that describes their usage.
ChangeLog:
2014-04-24 Jeff Layton
[BZ#16839]
* manual/llio.texi: add
On Thu, 26 Jun 2014 15:50:36 -0400 Naoya Horiguchi
wrote:
> > index 90002ea..e277726a 100644
> > --- a/mm/memory-failure.c
> > +++ b/mm/memory-failure.c
> > @@ -1143,6 +1143,22 @@ int memory_failure(unsigned long pfn, int trapno,
> > int flags)
> > lock_page(hpage);
> >
> > /*
> > +
> show RCX == RIP even under strace.
If you think it's really worth the extra instruction?
It's not wrong, but it's not clear if it's useful.
-Andi
>
> Signed-off-by: Andy Lutomirski
> ---
> arch/x86/kernel/entry_64.S | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git
Thank you for testing/reporting.
On Thu, Jun 26, 2014 at 11:22:52AM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> While running the mcelog test suite on 3.14 I hit the following VM_BUG_ON:
>
> soft_offline: 0x56d4: unknown non LRU page type 388000
This line comes from error path in
On Wed, May 21, 2014 at 12:33 AM, Richard Weinberger
wrote:
> CC'ing RT folks
>
> On Wed, May 21, 2014 at 8:23 AM, Austin Schuh wrote:
>> On Tue, May 13, 2014 at 7:29 PM, Austin Schuh
>> wrote:
>>> Hi,
>>>
>>> I am observing a filesystem lockup with XFS on a CONFIG_PREEMPT_RT
>>> patched
On 2014-06-27 01:11:59, Himangi Saraogi wrote:
> This patch does away with cast on void * and the if as it is unnecessary.
>
> The following Coccinelle semantic patch was used for making the change:
>
> @r@
> expression x;
> void* e;
> type T;
> identifier f;
> @@
>
> (
> *((T *)e)
> |
>
On 06/26, Paul E. McKenney wrote:
>
> On Thu, Jun 26, 2014 at 08:36:57PM +0200, Oleg Nesterov wrote:
>
> > > +static void rcu_release_map(struct lockdep_map *map, unsigned long ip)
> > > +{
> > > + rcu_lockdep_assert_watching();
> > > + __rcu_lock_release(, ip);
> >
> > "map", not "". I fixed this
I'm announcing the release of the 3.15.2 kernel.
All users of the 3.15 kernel series must upgrade.
The updated 3.15.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.15.y
and can be browsed at the normal kernel.org git web browser:
This patch does away with cast on void * and the if as it is unnecessary.
The following Coccinelle semantic patch was used for making the change:
@r@
expression x;
void* e;
type T;
identifier f;
@@
(
*((T *)e)
|
((T *)x)[...]
|
((T *)x)->f
|
- (T *)
e
)
Signed-off-by: Himangi Saraogi
Em Thu, Jun 26, 2014 at 08:14:27PM +0400, Stanislav Fomichev escreveu:
> 'perf trace' can show summary of events using -S option. This commit
> also reports number of major/minor pagefault events in this summary.
>
> Signed-off-by: Stanislav Fomichev
Where is it?
[root@zoo /]# perf trace -S -F
On Wed, Jun 11, 2014 at 04:39:41PM -0400, Pranith Kumar wrote:
> kernel/rcu/tree_plugin.h:990:13: warning: context imbalance in
> 'rcu_report_unblock_qs_rnp' - unexpected unlock
>
> by annotating the function with __releases()
>
> Signed-off-by: Pranith Kumar
Hearing no objections, I have
On Wed, Jun 11, 2014 at 04:39:40PM -0400, Pranith Kumar wrote:
> kernel/rcu/tree_plugin.h:1494:13: warning: context imbalance in
> 'rcu_initiate_boost' - unexpected unlock
>
> by annotating the function with releases()
>
> Signed-off-by: Pranith Kumar
Hearing no objections, I have queued this
On Thu, 2014-06-26 at 19:10 +, Chalamarla, Tirumalesh wrote:
> Thanks for the clarification Alex, That’s exactly my point, why are we
> relying on QEMU or something else to emulate the MSI space when we can
> directly give access to devices using ITS (of course with a small emulation
>
I'm announcing the release of the 3.14.9 kernel.
All users of the 3.14 kernel series must upgrade.
The updated 3.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.14.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 0864af4a683b..fda1dab589be 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 4
-SUBLEVEL = 94
+SUBLEVEL = 95
EXTRAVERSION =
NAME = Saber-toothed Squirrel
diff --git a/drivers/net/ethernet/mellanox/mlx4/main.c
I'm announcing the release of the 3.10.45 kernel.
All users of the 3.10 kernel series must upgrade.
The updated 3.10.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.10.y
and can be browsed at the normal kernel.org git web
On Mon, Jun 23, 2014 at 10:38:07AM -0700, David Cohen wrote:
> Hi Jiang,
>
> On Mon, Jun 23, 2014 at 10:30:35AM +0800, Jiang Liu wrote:
> > Commit 9f354b0252b8 "x86, irq: Clean up unused IOAPIC interface" kills
> > interface io_apic_set_pci_routing(), so change arch/x86/platform/
> >
I'm announcing the release of the 3.4.95 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
On Thu, 26 Jun 2014 15:25:31 -0400
Mike Frysinger wrote:
> On Thu 26 Jun 2014 12:52:45 Steven Rostedt wrote:
> > From: "Steven Rostedt (Red Hat)"
> >
> > Nothing sets function_trace_stop to disable function tracing anymore.
> > Remove the check for it in the arch code.
> >
> > [ Please test
On Thu 26 Jun 2014 12:52:45 Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Nothing sets function_trace_stop to disable function tracing anymore.
> Remove the check for it in the arch code.
>
> [ Please test this on your arch ]
i haven't tested, but the asm looks correct -- it's
On Thu, Jun 26, 2014 at 05:37:27PM +0200, Sebastian Andrzej Siewior wrote:
> On 06/12/2014 02:01 PM, tip-bot for Namhyung Kim wrote:
>
> > Commit-ID: e646fe730a324098a718f1c9b2f349efb99d5457
> > Gitweb:
> > http://git.kernel.org/tip/e646fe730a324098a718f1c9b2f349efb99d5457
> > Author:
On Thu, Jun 26, 2014 at 06:18:05PM +0200, Takashi Iwai wrote:
> At Tue, 24 Jun 2014 15:39:40 -0700,
> Luis R. Rodriguez wrote:
> >
> > From: "Luis R. Rodriguez"
> >
> > Takashi added request_firmware_direct() via bba3a87e9 through v3.14-rc1
> > which avoids the unnecessary delay introduced by
On Thu, Jun 26, 2014 at 08:36:57PM +0200, Oleg Nesterov wrote:
> On 06/26, Oleg Nesterov wrote:
> >
> > On 06/26, Oleg Nesterov wrote:
> > >
> > > +static void rcu_release_map(struct lockdep_map *map, unsigned long ip)
> > > +{
> > > + rcu_lockdep_assert_watching();
> > > +
Thanks for the clarification Alex, That’s exactly my point, why are we relying
on QEMU or something else to emulate the MSI space when we can directly give
access to devices using ITS (of course with a small emulation code).
This way we are also benefited from all ITS services like VCPU
On Wed, Jun 25, 2014 at 10:20:43AM -0400, Benjamin LaHaise wrote:
> Hi Greg,
>
> On Tue, Jun 24, 2014 at 11:50:43AM -0400, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.15.2 release.
> > There are 61 patches in this series, all will be posted as a response
>
On Wed, Jun 25, 2014 at 06:00:54PM +0900, Satoru Takeuchi wrote:
> At Tue, 24 Jun 2014 13:50:54 -0600,
> Shuah Khan wrote:
> >
> > On 06/24/2014 09:50 AM, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 3.15.2 release.
> > > There are 61 patches in this
On Tue, Jun 24, 2014 at 04:31:00PM -0700, Guenter Roeck wrote:
> On 06/24/2014 08:50 AM, Greg Kroah-Hartman wrote:
> >This is the start of the stable review cycle for the 3.15.2 release.
> >There are 61 patches in this series, all will be posted as a response
> >to this one. If anyone has any
The int_ret_from_sys_call and syscall tracing code disagrees with
the sysret path as to the value of RCX.
The Intel SDM, the AMD APM, and my laptop all agree that sysret
returns with RCX == RIP. The syscall tracing code does not respect
this property.
For example, this program:
int main()
{
This patch defines maximum block number to 2^31.
It also converts bitmap_size and array_size to
unsigned int in omfs_get_imap.
Suggested-By: Linus Torvalds
Suggested-By: Bob Copeland
Cc: Linus Torvalds
Cc: Bob Copeland
Cc: Andrew Morton
Signed-off-by: Fabian Frederick
---
This is untested.
Hello.
On 06/26/2014 12:10 AM, Marcel Ziswiler wrote:
This migration is required for continued PCIe operation after commit:
d3c7e24b84fcb62f96fa9a585a41f1829f326878
Please also specify that commit's summary line in parens.
Signed-off-by: Marcel Ziswiler
WBR, Sergei
--
To
From: Thierry Reding
This structure is read-only data and should never be modified.
Signed-off-by: Thierry Reding
---
drivers/iommu/amd_iommu.c | 4 ++--
drivers/iommu/arm-smmu.c| 2 +-
drivers/iommu/exynos-iommu.c| 2 +-
drivers/iommu/fsl_pamu_domain.c | 2 +-
On 26/06/14 19:50, Russell King - ARM Linux wrote:
On Thu, Jun 26, 2014 at 07:41:32PM +0100, Sudeep Holla wrote:
Hi,
On 25/06/14 23:23, Russell King - ARM Linux wrote:
On Wed, Jun 25, 2014 at 06:30:37PM +0100, Sudeep Holla wrote:
+ coherency_line_size: the minimum amount of
On Thu, 2014-06-26 at 18:41 +, Chalamarla, Tirumalesh wrote:
> Sorry there was a type,
>
> The question is:
>
> How is VFIO restricting software from writing to MSI/MSI-X
> vectors of the device.
All interrupts are configured via ioctl, not MSI config space or the
MSI-X
On Fri, 2014-06-27 at 00:12 +0530, Himangi Saraogi wrote:
> This patch does away with casts on void * as they are unnecessary.
[]
> diff --git a/fs/ecryptfs/inode.c b/fs/ecryptfs/inode.c
[]
> @@ -53,7 +53,7 @@ static void unlock_dir(struct dentry *dir)
>
> static int ecryptfs_inode_test(struct
After following recent cleanups by Bjorn:
http://git.kernel.org/cgit/linux/kernel/git/helgaas/pci.git/log/?h=pci/hotplug
2cc56f3 PCI: pciehp: Remove assumptions about which commands cause
40b9608 PCI: pciehp: Compute timeout from hotplug command start time
3461a06 PCI: pciehp: Wait for hotplug
On Thu, Jun 26, 2014 at 07:41:32PM +0100, Sudeep Holla wrote:
> Hi,
>
> On 25/06/14 23:23, Russell King - ARM Linux wrote:
>> On Wed, Jun 25, 2014 at 06:30:37PM +0100, Sudeep Holla wrote:
>>> + coherency_line_size: the minimum amount of data that gets
>>> transferred
>>
>> So, what
On 06/26/14 04:36, Sudeep Holla wrote:
> Hi Stephen,
>
> On 26/06/14 01:19, Stephen Boyd wrote:
>> On 06/25/14 10:30, Sudeep Holla wrote:
>>> +
>>> +/*
>>> + * Which cache CCSIDR represents depends on CSSELR value
>>> + * Make sure no one else changes CSSELR during this
>>> + *
On Thu, 26 Jun 2014 11:35:57 -0700
Linus Torvalds wrote:
> On Jun 26, 2014 11:28 AM, "Fabian Frederick" wrote:
> >
> >Sorry but I don't see a problem with 2^31 value.
>
> It's not really 2^31.
>
> It's *negative* 2^31.
>
> 1 is "int", so it's a signed number. With the shift it ends up
This patch does away with casts on void * as they are unnecessary.
The following Coccinelle semantic patch was used for making the change:
@r@
expression x;
void* e;
type T;
identifier f;
@@
(
*((T *)e)
|
((T *)x)[...]
|
((T *)x)->f
|
- (T *)
e
)
Signed-off-by: Himangi Saraogi
Sorry there was a type,
The question is:
How is VFIO restricting software from writing to MSI/MSI-X vectors
of the device.
-Original Message-
From: Chalamarla, Tirumalesh
Sent: Thursday, June 26, 2014 11:16 AM
To: Chalamarla, Tirumalesh; Joerg Roedel; Will Deacon
Cc:
Hi,
On 25/06/14 23:23, Russell King - ARM Linux wrote:
On Wed, Jun 25, 2014 at 06:30:37PM +0100, Sudeep Holla wrote:
+ coherency_line_size: the minimum amount of data that gets
transferred
So, what value to do envision this taking for a CPU where the cache
line size is 32
On 06/26, Oleg Nesterov wrote:
>
> On 06/26, Oleg Nesterov wrote:
> >
> > +static void rcu_release_map(struct lockdep_map *map, unsigned long ip)
> > +{
> > + rcu_lockdep_assert_watching();
> > + __rcu_lock_release(_lock_map, ip);
>
> OOPS. This should
Hi Steve,
Can the modified test program reproduce the problem in your test setup?
Thanks,
--Martin
On Tue, Jun 10, 2014 at 10:58:14PM -0700, Martin Lau wrote:
> Hi Steve,
>
> Attached is the modified test program. Here is the sample output:
>
> localhost ~ # ./ftrace-test-epoll-kafai
>
Hello.
On 06/26/2014 07:48 PM, Peter De Schrijver wrote:
When writing a module for testing or debugging purposes, there is no way to
get hold of clk handles. This patch solves this by exposing all valid clocks
as clkdev's for the virtual device tegra-clk-debug.
Signed-off-by: Peter De
We use regmap regulator ops to enable/disable and check if regulator
is enabled for various SMPS. However, these depend on valid
enable_reg, enable_mask and enable_value in regulator descriptor.
So, similar to fix we did in commit 318dbb02b50c
("regulator: palmas: Fix SMPS
On Thu, 26 Jun 2014 10:08:04 -0700
Linus Torvalds wrote:
> On Jun 26, 2014 10:05 AM, "Fabian Frederick" wrote:
> >
> > +#define OMFS_MAX_BLOCKS (1 << 31)
>
> This is wrong. Think about the types, and what value this has...
>
Hello Linus,
Sorry but I don't see a problem with 2^31 value.
From: Andi Kleen
While running the mcelog test suite on 3.14 I hit the following VM_BUG_ON:
soft_offline: 0x56d4: unknown non LRU page type 388000
page:ea15b400 count:3 mapcount:2097169 mapping: (null)
index:0x8800056d7000
page flags:
When I say emulating ITS, I mean translating guest ITS commands to physical ITS
commands and placing them in physical queue.
Regards,
Tirumalesh.
-Original Message-
From: kvmarm-boun...@lists.cs.columbia.edu
[mailto:kvmarm-boun...@lists.cs.columbia.edu] On Behalf Of Chalamarla,
MAX77802 is a PMIC that contains 10 high efficiency Buck regulators,
32 Low-dropout (LDO) regulators, two 32kHz buffered clock outputs,
a Real-Time-Clock (RTC) and a I2C interface to program the individual
regulators, clocks and the RTC.
This fifth version of the patch-set addresses several
From: Doug Anderson
The max77686 includes an RTC that keeps power during suspend. It's
convenient to be able to use it as a wakeup source.
NOTE: due to wakeup ordering problems this patch alone doesn't work so
well on exynos5250-snow. You also need something that brings the i2c
bus up before
Like most clock drivers, the Maxim 77686 PMIC clock binding
follows the convention that the "#clock-cells" property is
used to specify the number of cells in a clock provider.
But the binding document is not clear enough that it shall
be set to 1 since the PMIC support multiple clocks outputs.
This patch adds a dt-binding include for Maxim 77686
PMIC clock IDs that can be to be shared between the
clk-max77686 clock driver and DeviceTree source files.
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Krzysztof Kozlowski
---
Changes since v4: None
Changes since v3: None
Add Device Tree binding documentation for the clocks
outputs in the Maxim 77802 Power Management IC.
Signed-off-by: Javier Martinez Canillas
---
Changes since v4: None
Changes since v3:
- Don't use the same clock driver name in clock-names since it's a consumer
concept and most probably
Some device drivers using the register map API need to copy the
value from one register to another. Even though it can be done
with a combination of regmap_read() and regmap_write(), it is
better to have a function to avoid code duplication and also it
sanity check and do it atomically by holding
Maxim Integrated Power Management ICs are very similar with
regard to their clock outputs. Most of the clock drivers for
these chips are duplicating code and are simpler enough that
can be converted to use a generic driver to consolidate code
and avoid duplication.
Signed-off-by: Javier Martinez
Peach pit and pi boards uses a Maxim 77802 power management
IC to drive regulators and its Real Time Clock. This patch
adds support for this chip.
These are the device nodes and pinctrl configuration that
are present on the Peach pit DeviceTree source file in the
the Chrome OS kernel 3.8 tree.
Add Device Tree binding documentation for Maxim 77802 PMIC.
Signed-off-by: Javier Martinez Canillas
---
Changes since v4: None
Changes since v3: None
Changes since v2:
- Explain better the Dynamic Voltage Scaling (DVS) support in some Buck
regulators and the
The MAX77802 PMIC has 10 high-efficiency Buck and 32 Low-dropout
(LDO) regulators. This patch adds support for all these regulators
found on the MAX77802 PMIC and is based on a driver added by Simon
Glass to the Chrome OS kernel 3.8 tree.
Signed-off-by: Javier Martinez Canillas
Tested-by: Naveen
The MAX77802 PMIC has two 32.768kHz Buffered Clock Outputs with
Low Jitter Mode. This patch adds support for these two clocks.
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Krzysztof Kozlowski
---
Changes since v4: None
Changes since v3: None
Changes since v2: None
Changes since v1:
The MAX7802 PMIC has a Real-Time-Clock (RTC) with two alarms.
This patch adds support for the RTC and is based on a driver
added by Simon Glass to the Chrome OS kernel 3.8 tree.
Signed-off-by: Javier Martinez Canillas
---
Changes since v4: None
Changes since v3: None
drivers/rtc/Kconfig
Maxim MAX77802 is a power management chip that contains 10 high
efficiency Buck regulators, 32 Low-dropout (LDO) regulators used
to power up application processors and peripherals, a 2-channel
32kHz clock outputs, a Real-Time-Clock (RTC) and a I2C interface
to program the individual regulators,
Clocks drivers for Maxim PMIC are very similar so they can
be converted to use the generic Maxim clock driver.
Also, while being there use module_platform_driver() helper
macro to eliminate more boilerplate code.
Signed-off-by: Javier Martinez Canillas
Reviewed-by: Krzysztof Kozlowski
---
By using the generic IRQ support in the Register map API, it
is possible to get rid max77686-irq.c and simplify the code.
Suggested-by: Krzysztof Kozlowski
Signed-off-by: Javier Martinez Canillas
Acked-by: Lee Jones
Reviewed-by: Doug Anderson
Tested-by: Doug Anderson
---
Changes since v4:
Hi Boris,
2014-06-26 3:13 GMT-07:00 Boris BREZILLON :
> Add ethernet-phy node and specify phy interrupt (connected to pin PB25).
>
> The PHY address is not specified here because atmel have 2 different
> designs
> for its CPU modules: one is connecting PHYAD[0-2] pins to pull up resistors
>
On 06/25/2014 05:30 PM, Andrew Bresticker wrote:
> On Wed, Jun 25, 2014 at 3:12 PM, Stephen Warren wrote:
>> On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
>>> In addition to the PCIe and SATA PHYs, the XUSB pad controller also
>>> supports 3 UTMI, 2 HSIC, and 2 USB3 PHYs. Each USB3 PHY uses a
Forgive me if this discussion is not relative here, but I thought it is.
How is VFIO restricting devices from writing to MSI/MSI-X,
Is all the vector area is mapped by VFIO to trap the accesses. I am asking
this because we might need to emulate ITS somewhere either in KVM or VFIO to
provide
On 06/25/2014 06:06 PM, Andrew Bresticker wrote:
> On Wed, Jun 25, 2014 at 3:37 PM, Stephen Warren wrote:
>> On 06/18/2014 12:16 AM, Andrew Bresticker wrote:
>>> Add support for the on-chip XHCI host controller present on Tegra SoCs.
>>>
>>> The driver is currently very basic: it loads the
Mel Gorman writes:
>> And we should probably run our standard set of I/O exercisers at the
>> very least. But, like I said, it seems like wasted effort.
>>
>
> Out of curiousity, what do you consider to be the standard set of I/O
> exercisers?
Yes, that was vague, sorry. I was referring to
Signed-off-by: Pranith Kumar
---
Documentation/atomic_ops.txt | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/Documentation/atomic_ops.txt b/Documentation/atomic_ops.txt
index 68542fe..d3ad657 100644
--- a/Documentation/atomic_ops.txt
+++
Hello,
2014-06-25 0:24 GMT-07:00 Bo Shen :
> If the fixups parameters get from dtb, it won't set has_fixups
> parameters, so when read phy_has_fixups attribute, it always
> present as 0.
> Add this patch to make phy_has_fixups attribute read correctly.
I am not entirely sure whether loading
On 06/24/14 01:51, Linus Walleij wrote:
> This adds some documentation about clock sources, clock events,
> the weak sched_clock() function and delay timers that answers
> questions that repeatedly arise on the mailing lists.
>
> Cc: Thomas Gleixner
> Cc: Nicolas Pitre
> Cc: Colin Cross
> Cc:
On Tue, 24 Jun 2014 15:55:41 +0900
Namhyung Kim wrote:
> Hi Steve,
>
> On Fri, 20 Jun 2014 06:45:19 -0400, Steven Rostedt wrote:
> > From: Oleg Nesterov
> >
> > syscall_regfunc() and syscall_unregfunc() should set/clear
> > TIF_SYSCALL_TRACEPOINT system-wide, but do_each_thread() can race
> >
On Thu, Jun 26, 2014 at 12:50:32PM -0400, Jeff Moyer wrote:
> Mel Gorman writes:
>
> > On Thu, Jun 26, 2014 at 11:36:50AM -0400, Jeff Moyer wrote:
> >> Right, and I guess I hadn't considered that case as I thought folks used
> >> more than one spinning disk for such workloads.
> >>
> >
> > They
On Thu, 26 Jun 2014 19:14:31 +0200
Fabian Frederick wrote:
> This fixes checkpatch warning:
>
> "WARNING: debugfs_remove(NULL) is safe this check is probably not required"
Thanks, applied to my 3.17 queue.
-- Steve
>
> Cc: Steven Rostedt
> Cc: Frederic Weisbecker
> Signed-off-by: Fabian
Fix checkpatch warning:
"WARNING: Prefer pr_warn(... to pr_warning(..."
+ coalesce formats.
Cc: Stefan Weinhuber
Cc: Stefan Haberland
Signed-off-by: Fabian Frederick
---
drivers/s390/block/dasd.c | 28
1 file changed, 12 insertions(+), 16 deletions(-)
diff --git
Fix checkpatch warnings:
"WARNING: EXPORT_SYMBOL(foo); should immediately follow its function/variable"
Cc: Stefan Weinhuber
Cc: Stefan Haberland
Signed-off-by: Fabian Frederick
---
drivers/s390/block/dasd.c | 69 +++
1 file changed, 33
Fix checkpatch warnings:
"WARNING: Prefer seq_puts to seq_printf"
Cc: Stefan Weinhuber
Cc: Stefan Haberland
Signed-off-by: Fabian Frederick
---
drivers/s390/block/dasd.c | 34 +-
1 file changed, 17 insertions(+), 17 deletions(-)
diff --git
This is an untested patchset to address some checkpatch warnings in dasd.c
Fabian Frederick (4):
drivers/s390/block/dasd.c: remove unnecessary null test before
debugfs_remove
drivers/s390/block/dasd.c: Move EXPORT_SYMBOL after function/variable
drivers/s390/block/dasd.c: replace
This fixes checkpatch warning:
"WARNING: debugfs_remove(NULL) is safe this check is probably not required"
Cc: Stefan Weinhuber
Cc: Stefan Haberland
Signed-off-by: Fabian Frederick
---
drivers/s390/block/dasd.c | 25 -
1 file changed, 8 insertions(+), 17 deletions(-)
On Thu, 26 Jun 2014 12:52:47 -0400
Steven Rostedt wrote:
> From: Heiko Carstens
>
> Remove check of obsolete variable function_trace_stop as requested by
> Steven Rostedt.
>From the cover letter, you were not Cc'd on.
Anyway, as there is no more reason to set function_trace_stop it is time
On Thu, 26 Jun 2014 12:52:45 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Nothing sets function_trace_stop to disable function tracing anymore.
> Remove the check for it in the arch code.
>
> [ Please test this on your arch ]
>From the cover letter, you were not Cc'd
v4->v5:
- Add patch 2 to update the locking selftest code to handle recursive
read_lock correctly. Patch 1 has no change.
v3->v4:
- Document the new read state and move the conditional compilation code
to lockdep.h.
v2->v3:
- Add a new read mode (3) for rwlock (used in
Unlike the original unfair rwlock implementation, queued rwlock
will grant lock according to the chronological sequence of the lock
requests except when the lock requester is in the interrupt context.
Consequently, recursive read_lock calls will now hang the process if
there is a write_lock call
On Thu, 26 Jun 2014 12:52:46 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Nothing sets function_trace_stop to disable function tracing anymore.
> Remove the check for it in the arch code.
>
> arm64 was broken anyway, as it had an ifdef testing
>
The queue rwlock does not support the use of recursive read-lock in
the process context. With changes in the lockdep code to check and
disallow recursive read-lock when queue rwlock is configured, it
is also necessary for the locking selftest to be updated to change
the process context recursive
On Thu, 26 Jun 2014 12:52:44 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Nothing sets function_trace_stop to disable function tracing anymore.
> Remove the check for it in the arch code.
>
> [ Please test this on your arch ]
>From the cover letter, you were not Cc'd
On Thu, 26 Jun 2014 12:52:43 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Nothing sets function_trace_stop to disable function tracing anymore.
> Remove the check for it in the arch code.
>
> [ Please test this on your arch ]
>From the cover letter, you were not Cc'd
On Thu, 2014-06-26 at 22:58 +0530, Himangi Saraogi wrote:
> This patch removes the cast on data of type void* as it is not needed.
Hi Himangi
The cast of a const void * to a void * was odd.
Maybe a mechanism to verify appropriateness of
loss of constness for any pointer might be useful.
--
To
On Thu, 26 Jun 2014 12:52:42 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Nothing sets function_trace_stop to disable function tracing anymore.
> Remove the check for it in the arch code.
>
> [ Please test this on your arch ]
>
Bah! I forgot to add you to the Cc of
On Thu, Jun 26, 2014 at 01:45:13PM +0200, Petr Mládek wrote:
> On Thu 2014-06-26 10:29:40, Luis R. Rodriguez wrote:
> > On Thu, Jun 26, 2014 at 04:22:57PM +1000, Stephen Rothwell wrote:
> > > Hi Andrew,
> > >
> > > After merging the akpm tree, today's linux-next build (powerpc
> > >
On Thu, 26 Jun 2014 12:52:40 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Nothing sets function_trace_stop to disable function tracing anymore.
> Remove the check for it in the arch code.
>
> [ Please test this on your arch ]
>From the cover letter, you were not Cc'd
On Thu, 26 Jun 2014 12:52:41 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Nothing sets function_trace_stop to disable function tracing anymore.
> Remove the check for it in the arch code.
>From the cover letter, you were not Cc'd on.
Anyway, as there is no more reason
On 06/26, Oleg Nesterov wrote:
>
> +static void rcu_release_map(struct lockdep_map *map, unsigned long ip)
> +{
> + rcu_lockdep_assert_watching();
> + __rcu_lock_release(_lock_map, ip);
OOPS. This should be "map". Please see v2 below.
On Thu, 26 Jun 2014 12:52:39 -0400
Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Nothing sets function_trace_stop to disable function tracing anymore.
> Remove the check for it in the arch code.
>
> [ Please test this on your arch ]
>From the cover letter, you were not Cc'd
201 - 300 of 1288 matches
Mail list logo
