> -Original Message-
> From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma-
> ow...@vger.kernel.org] On Behalf Of Michael Wang
> Sent: Monday, April 20, 2015 2:08 PM
> To: Roland Dreier; Sean Hefty; linux-r...@vger.kernel.org; linux-
> ker...@vger.kernel.org; h...@dev.mellanox.co.il
On Mon, Apr 20, 2015 at 09:52:30PM +0100, Mark Brown wrote:
> On Mon, Apr 20, 2015 at 06:50:17AM +0200, Sascha Hauer wrote:
> > On Sat, Apr 18, 2015 at 06:37:40PM +0100, Mark Brown wrote:
> > > On Fri, Apr 10, 2015 at 04:14:08PM +0800, Koro Chen wrote:
>
> > > > + [0][0] = { .creg =
+ dma maillist
Best wishes
Qipeng
-Original Message-
From: Zha, Qipeng
Sent: Tuesday, April 21, 2015 7:34 AM
To: linux-kernel@vger.kernel.org
Cc: viresh.li...@gmail.com; andriy.shevche...@linux.intel.com; Westerberg,
Mika; Chen, Jason CJ; Zheng, Qi; Zha, Qipeng; Zhong, Huiquan
Hi Michael,
is there a specific git branch available to pull out all the patches?
-Regards
Devesh
> -Original Message-
> From: linux-rdma-ow...@vger.kernel.org [mailto:linux-rdma-
> ow...@vger.kernel.org] On Behalf Of Michael Wang
> Sent: Monday, April 20, 2015 1:59 PM
> To: Roland
Hi,
On Tuesday 21 April 2015 01:49 AM, Arun Ramamurthy wrote:
On 15-04-15 02:59 AM, Kishon Vijay Abraham I wrote:
Hi,
On Tuesday 14 April 2015 03:40 AM, Arun Ramamurthy wrote:
Some generic drivers, such as ehci, may use multiple phys and for such
drivers referencing phy(s) by name(s) does
Arnd,
On Wednesday 15 April 2015 03:17 AM, Arnd Bergmann wrote:
On Tuesday 14 April 2015 11:05:35 Arun Ramamurthy wrote:
[1] ->
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/Documentation/kbuild/kconfig-language.txt#n111
Kishon,removing select GENERIC_PHY also breaks
Hi Wolfram,
On Mon, 20 Apr 2015 19:36:38 +0200, Wolfram Sang wrote:
> On Fri, Feb 27, 2015 at 05:16:56PM +0100, Wolfram Sang wrote:
> > This tool allows to construct and concat multiple I2C messages into one
> > single transfer. Its aim is to test I2C master controllers, and so there
> > is no
Hi Wang,
On Tue, Apr 21, 2015 at 03:33:10AM +, Wang Nan wrote:
> Before patch ba92732e9808df679ddf75c5ea1c0caae6d7dce2 ('perf kmaps:
> Check kmaps to make code more robust'), perf report and perf annotate
> will segfault if trace data contains kernel module information like
> this:
>
> #
Currently perf kmem shows total (page) allocation stat by default, but
sometimes one might want to see live (total alloc-only) requests/pages
only. The new --live option does this by subtracting freed allocation
from the stat.
Acked-by: Pekka Enberg
Signed-off-by: Namhyung Kim
---
It perf kmem support caller statistics for page. Unlike slab case,
the tracepoints in page allocator don't provide callsite info. So
it records with callchain and extracts callsite info.
Note that the callchain contains several memory allocation functions
which has no meaning for users. So
Add new sort keys for page: page, order, migtype, gfp - existing
'bytes', 'hit' and 'callsite' sort keys also work for page. Note that
-s/--sort option should be preceded by either of --slab or --page
option to determine where the sort keys applies.
Now it properly groups and sorts allocation
Save libtraceevent output and print it in the header.
# perf kmem stat --page --caller
#
# GFP flags
# -
# 0010: NI: GFP_NOIO
# 00d0:K: GFP_KERNEL
# 0200: NWR: GFP_NOWARN
# 84d0:K|R|Z: GFP_KERNEL|GFP_REPEAT|GFP_ZERO
# 000200d2:
Currently perf kmem command will select --slab if neither --slab nor
--page is given for backward compatibility. Add kmem.default config
option to select the default value ('page' or 'slab').
# cat ~/.perfconfig
[kmem]
default = page
# perf kmem stat
SUMMARY (page allocator)
Hello,
Currently perf kmem command only analyzes SLAB memory allocation. And
I'd like to introduce page allocation analysis also. Users can use
--slab and/or --page option to select it. If none of these options
are used, it does slab allocation analysis for backward compatibility.
*
Sometimes one can mistakenly run perf kmem stat without perf kmem
record before or different configuration like recoding --slab and stat
--page. Show a warning message like below to inform user:
# perf kmem stat --page --caller
Not found page events. Have you run 'perf kmem record --page'
On 04/20/2015 05:57 PM, Ulrich Weigand wrote:
> Anshuman Khandual wrote on 13.04.2015
> 10:48:57:
>> On 04/10/2015 04:03 PM, Ulrich Weigand wrote:
>>> - You provide checkpointed FPR and VMX registers, but there doesn't
> seem
>>> to be any way to get at the checkpointed *VSX* registers (i.e.
Richard Guy Briggs writes:
> The purpose is to track namespace instances in use by logged processes from
> the
> perspective of init_*_ns by logging the namespace IDs (device ID and namespace
> inode - offset).
In broad strokes the user interface appears correct.
Things that I see that
FYI, we found changes on `fsmark.files_per_sec' by
78373b7319abdf15050af5b1632c4c8b8b398f33:
> commit 78373b7319abdf15050af5b1632c4c8b8b398f33
> Author: Jaegeuk Kim
> AuthorDate: Fri Mar 13 21:44:36 2015 -0700
> Commit: Jaegeuk Kim
> CommitDate: Fri Apr 10 15:08:45
If multiple soft offline events hit one free page/hugepage concurrently,
soft_offline_page() can handle the free page/hugepage multiple times,
which makes num_poisoned_pages counter increased more than once.
This patch fixes this wrong counting by checking TestSetPageHWPoison for
normal papes and
This set of patches adds support for select accessory detect mode to HPDETL or
HPDETR.
Changes in v2:
- Use the value in pdata instead of hpdet_channel in extcon_info.
- Wrap arizona_extcon_of_get in IS_ENABLED(CONFIG_OF).
- Change hpdet_channel type to unsigned from signed in pdata.
-
This patch add device tree bindings for the pdata needed to configure
the Accessory Detect Mode select when Headphone detection.
Signed-off-by: Inha Song
---
Documentation/devicetree/bindings/mfd/arizona.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git
This patch add support for select accessory detect mode to HPDETL or HPDETR.
Arizona provides a headphone detection circuit on the HPDETL and HPDETR pins
to measure the impedance of an external load connected to the headphone.
Depending on board design, headphone detect pins can change to HPDETR
On 04/20/2015 02:09 PM, Aaro Koskinen wrote:
Hi,
On Mon, Apr 20, 2015 at 12:40:28PM -0700, Guenter Roeck wrote:
the upstream kernel fails to build mips:nlm_xlp_defconfig,
mips:nlm_xlp_defconfig, mips:cavium_octeon_defconfig, and possibly
other targets, with errors such as
X-Gene v1 SoC supports total 256 MSI/MSIX vectors coalesced into
16 HW IRQ lines.
Signed-off-by: Duc Dang
Signed-off-by: Tanmay Inamdar
---
drivers/pci/host/Kconfig | 6 +
drivers/pci/host/Makefile| 1 +
drivers/pci/host/pci-xgene-msi.c | 477
There is single MSI block in X-Gene v1 SOC which serves all 5 PCIe ports.
Signed-off-by: Duc Dang
Signed-off-by: Tanmay Inamdar
---
arch/arm64/boot/dts/apm/apm-storm.dtsi | 27 +++
1 file changed, 27 insertions(+)
diff --git a/arch/arm64/boot/dts/apm/apm-storm.dtsi
This patch adds information of maintainers for APM X-Gene v1 PCIe
MSI/MSIX termination driver
Signed-off-by: Duc Dang
Signed-off-by: Tanmay Inamdar
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index ddc5a8c..a1b119b 100644
---
The driver for this binding is under 'drivers/pci/host/pci-xgene-msi.c'
Signed-off-by: Duc Dang
Signed-off-by: Tanmay Inamdar
---
.../devicetree/bindings/pci/xgene-pci-msi.txt | 63 ++
1 file changed, 63 insertions(+)
create mode 100644
This patch set adds MSI/MSIX termination driver support for APM X-Gene v1 SoC.
APM X-Gene v1 SoC supports its own implementation of MSI, which is not compliant
to GIC V2M specification for MSI Termination.
There is single MSI block in X-Gene v1 SOC which serves all 5 PCIe ports. This
MSI
block
On Mon, 2015-04-20 at 14:21 -0400, Steven Rostedt wrote:
>
> I would argue than every case is different, and only the sysadmin
> would
> know the right value. Thus, just set it to one, and if that's not
> good
> enough, then the sysadmins can change it to their needs.
Agreed. I don't have it
Before patch ba92732e9808df679ddf75c5ea1c0caae6d7dce2 ('perf kmaps:
Check kmaps to make code more robust'), perf report and perf annotate
will segfault if trace data contains kernel module information like
this:
# perf report -D -i ./perf.data
...
0 0 0x188 [0x50]: PERF_RECORD_MMAP -1/0:
This patch fixes the warning found by checkpatch.pl:
ERROR: Macros with complex values should be enclosed in parentheses
Signed-off-by: Jaime Arrocha
---
drivers/staging/gdm72xx/usb_ids.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Mon, 2015-04-20 at 19:32 -0700, Guenter Roeck wrote:
> On 04/20/2015 06:54 PM, Michael Ellerman wrote:
> > On Mon, 2015-04-20 at 12:50 -0400, David Miller wrote:
> >> From: Guenter Roeck
> >> Date: Mon, 20 Apr 2015 09:44:31 -0700
> >>
> >>> On Mon, Apr 20, 2015 at 12:25:19PM -0400, David
> -Original Message-
> From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org]
> Sent: Monday, April 20, 2015 10:43 PM
>
> On Mon, Apr 20, 2015 at 03:28:32AM +, Kweh, Hock Leong wrote:
> > Regarding the 'reboot require' status, is it critical to have a 1 to 1
> > status
> match
The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
tags/clk-for-linus-4.1
for you to fetch changes up to
On 2015/4/2 16:12, Namhyung Kim wrote:
> On Thu, Apr 02, 2015 at 06:04:52AM +, Wang Nan wrote:
>> There is a bug in perf annotate that it doesn't respect user provided
>> '-i'/'--input' option:
>>
>> # perf record ls
>>[ perf record: Woken up 1 times to write data ]
>>[ perf record:
On 2015/3/30 15:03, Jiri Olsa wrote:
> On Mon, Mar 30, 2015 at 02:04:08AM +, Wang Nan wrote:
>> Newest libunwind does support ARM64, and perf is able to utilize it
>> also. This patch enables the missing perf test dwarf unwind for arm64.
>>
>> Test result:
>> # ./perf test unwind
>> 25:
The patch fixes a trailing whitespace and code indenting coding style
errors as reported by checkpatch.pl tool.
Details of the lines where the fixed errors were reported are as follows:
drivers/staging/comedi/drivers/daqboard2000.c:43: ERROR: trailing whitespace
Hi,
On 04/21/15 at 09:39am, Li, ZhenHua wrote:
> Hi Dave,
> I found the old mail:
> http://lkml.iu.edu/hypermail/linux/kernel/1410.2/03584.html
I know and I have read it before.
== quote ===
> > > So with this in mind I would prefer initially taking over the
>
On 20 April 2015 at 16:47, Andy Lutomirski wrote:
> On Mon, Apr 20, 2015 at 4:34 PM, Tyler Baker wrote:
>> On 20 April 2015 at 16:22, Andy Lutomirski wrote:
>>> On Mon, Apr 20, 2015 at 4:15 PM, Tyler Baker wrote:
If the CROSS_COMPILE is set remove all's dependency on all_32 and all_64.
Change kernel version from 3.20 to 4.1
Signed-off-by: Chen Hanxiao
---
Documentation/filesystems/proc.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/filesystems/proc.txt
b/Documentation/filesystems/proc.txt
index c3b6b30..1cc7155 100644
---
On 2015/4/21 5:23, Arnaldo Carvalho de Melo wrote:
> Em Sat, Apr 18, 2015 at 05:50:20PM +0200, Jiri Olsa escreveu:
>> From: Wang Nan
>>
>> When converting int values, perf first extractes it to a ulonglong, then
>> feeds it to babeltrace as a signed value. For negative 32 bit values
>> (for
On 04/20/2015 06:54 PM, Michael Ellerman wrote:
On Mon, 2015-04-20 at 12:50 -0400, David Miller wrote:
From: Guenter Roeck
Date: Mon, 20 Apr 2015 09:44:31 -0700
On Mon, Apr 20, 2015 at 12:25:19PM -0400, David Miller wrote:
From: Guenter Roeck
Date: Sun, 19 Apr 2015 22:17:21 -0700
The
On Mon, 2015-04-20 at 21:55 +0100, Mark Brown wrote:
> On Mon, Apr 20, 2015 at 02:22:24PM +0800, Koro Chen wrote:
> > On Sat, 2015-04-18 at 18:51 +0100, Mark Brown wrote:
> > > On Fri, Apr 10, 2015 at 04:14:09PM +0800, Koro Chen wrote:
>
> > > Ah, so the SRAM is directly memory mappable. Nice.
Hi Christoph,
On Mon, Apr 20, 2015 at 11:40 PM, Christoph Lameter wrote:
> On Sat, 18 Apr 2015, Gavin Guo wrote:
>
>> The slub_debug=PU,kmalloc-xx cannot work because in the
>> create_kmalloc_caches() the s->name is created after the
>> create_kmalloc_cache() is called. The name is NULL in the
On 04/20/2015 08:15 PM, Ming Lei wrote:
On Mon, Apr 13, 2015 at 5:22 PM, Christoph Hellwig wrote:
The series looks fine to me:
Reviewed-by: Christoph Hellwig
Jens, could you share us if you are OK with this patchset?
Looks good to me, I'll queue it up.
--
Jens Axboe
--
To unsubscribe
On Mon, Apr 13, 2015 at 5:22 PM, Christoph Hellwig wrote:
> The series looks fine to me:
>
> Reviewed-by: Christoph Hellwig
Jens, could you share us if you are OK with this patchset?
Thanks,
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
From: Vivien Didelot
Date: Mon, 20 Apr 2015 17:43:26 -0400
> Minor, use the explicit PORT_DEFAULT_VLAN define instead of 0x07.
>
> Signed-off-by: Vivien Didelot
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
From: Andrew Lunn
Date: Tue, 21 Apr 2015 01:05:07 +0200
> On Mon, Apr 20, 2015 at 05:19:23PM -0400, Vivien Didelot wrote:
>> mv88e6xxx_setup_port_common was writing to PORT_DEFAULT_VLAN (port
>> offset 0x07) instead of PORT_CONTROL_1 (port offset 0x05).
>
> Hi Vivien
>
> Good catch.
>
>>
Firstly during CPU hotplug, even queue is freezed, timeout
handler still may come and access hctx->tags, which may cause
use after free, so this patch deactivates timeout handler
inside CPU hotplug notifier.
Secondly, tags can be shared by more than one queues, so we
have to check if the hctx has
hctx->tags has to be set as NULL in case that it is to be unmapped
no matter if set->tags[hctx->queue_num] is NULL or not in blk_mq_map_swqueue()
because shared tags can be freed already from another request queue.
The same situation has to be considered during handling CPU online too.
Unmapped
Hi Guys,
Dongsu Park reported[1] that kernel oops can be triggered easily by
CPU plug when there is pending I/O on virtio-scsi.
Turns out two problems exist in blk-mq core code and both can trigger
oops by CPU plug:
- timeout handling vs CPU hotplug, especially unmapped hw queue tags
Hi Mauro,
Today's linux-next merge of the v4l-dvb tree got a conflict in
include/uapi/linux/media-bus-format.h between various commits from
Linus' tree and various commits from the v4l-dvb tree.
I reported this previously against the drm tree but some fo the numbers
have changed.
I fixed it up
On Mon, 2015-04-20 at 12:50 -0400, David Miller wrote:
> From: Guenter Roeck
> Date: Mon, 20 Apr 2015 09:44:31 -0700
>
> > On Mon, Apr 20, 2015 at 12:25:19PM -0400, David Miller wrote:
> >> From: Guenter Roeck
> >> Date: Sun, 19 Apr 2015 22:17:21 -0700
> >>
> >> > The debug option is intended
Hi Mauro,
Today's linux-next merge of the v4l-dvb tree got a conflict in
Documentation/DocBook/media/v4l/subdev-formats.xml between various
commits from Linus' tree and various commits from the v4l-dvb tree.
I reported this previously against the drm tree, but some of the
numbers have changed
---
include/uapi/linux/nvme.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/uapi/linux/nvme.h b/include/uapi/linux/nvme.h
index aef9a81..5025610 100644
--- a/include/uapi/linux/nvme.h
+++ b/include/uapi/linux/nvme.h
@@ -229,6 +229,8 @@ enum nvme_opcode {
---
drivers/block/nvme-core.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/block/nvme-core.c b/drivers/block/nvme-core.c
index 85b8036..332341a 100644
--- a/drivers/block/nvme-core.c
+++ b/drivers/block/nvme-core.c
@@ -769,6 +769,9 @@ static int nvme_submit_iod(struct nvme_queue
The attached patch set enables basic write with stream ID support.
First patch reads the stream id embedded in the bio and passes to the
device along with the write command.
Second patch adds two new nvme commands to be used with ioctl
such that application can do open/close stream and host
On 2015/4/21 2:23, Yasuaki Ishimatsu wrote:
>
> On Mon, 20 Apr 2015 11:42:10 +0800
> Xishi Qiu wrote:
>
>> On 2015/4/20 11:29, Yasuaki Ishimatsu wrote:
>>
>>>
>>> On Mon, 20 Apr 2015 10:45:45 +0800
>>> Xishi Qiu wrote:
>>>
On 2015/4/20 9:42, Gu Zheng wrote:
> Hi Xishi,
> On
Hi Dave,
I found the old mail:
http://lkml.iu.edu/hypermail/linux/kernel/1410.2/03584.html
Please check this and you will find the discussion.
Regards
Zhenhua
On 04/15/2015 02:48 PM, Dave Young wrote:
On 04/15/15 at 01:47pm, Li, ZhenHua wrote:
On 04/15/2015 08:57 AM, Dave Young wrote:
>> Is there some reason you don't use the simpler singly-linked list
>> construction with the tail being a pointer to a pointer:
> Sure, that would also work.
It's just a convenient simplification, already used in struct hlist_node.
>> +/*
>> + * Queue a task for later wake-up by wake_up_q().
On Fri, Apr 17, 2015 at 08:04:13AM +0200, Heinrich Schuchardt wrote:
> A string written by the user may not be zero terminated.
>
> sscanf may read memory beyond the buffer if no zero byte
> is found.
>
> Signed-off-by: Heinrich Schuchardt
> ---
> drivers/usb/chipidea/debug.c | 6 +-
> 1
On Mon, Apr 20, 2015 at 04:50:07PM -0500, Clark Williams wrote:
> On Mon, 20 Apr 2015 14:15:04 -0700
> "Paul E. McKenney" wrote:
>
> > On Mon, Apr 20, 2015 at 04:40:49PM -0400, Steven Rostedt wrote:
> > > On Mon, Apr 20, 2015 at 10:09:03AM -0700, Paul E. McKenney wrote:
> > > >
> > > > The
Jason,
Could you please review my patch below?
See also arm64 maintainer's comment:
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/313712.html
Thanks,
-Takahiro AKASHI
I tried to verify kgdb in vanilla kernel on fast model, but it seems that
the single stepping with kgdb
Hello Kevin,
On 2015/4/21 5:10, Kevin Hilman wrote:
Bintian Wang writes:
This patch introduces ARCH_HISI to enable Hisilicon SoC family in
Kconfig and defconfig.
Signed-off-by: Bintian Wang
Reviewed-by: Haojian Zhuang
Reviewed-by: Wei Xu
[...]
diff --git
AFAIK the PAPR document which defines the virtual device interface used by
the ibmveth driver doesn't specify a specific maximum MTU. So, in the
ibmveth driver, the maximum allowed MTU is determined by the maximum
allocated buffer size of 64k (corresponding to one page in the common case)
minus
On Tue, 2015-04-21 at 02:36 +0200, Laurent Vivier wrote:
> So, dump config_rom data as big-endian values.
>
> The value given by /sys/bus/firewire/devices/fw0 were correctly
> given on a big-endian host (like powermac) not on a little-endian host
> (like PC), for instance:
[]
> diff --git
On Mon, 2015-04-20 at 13:53 +0300, Purcareata Bogdan wrote:
> On 10.04.2015 02:53, Scott Wood wrote:
> > On Thu, 2015-04-09 at 10:44 +0300, Purcareata Bogdan wrote:
> >> So at this point I was getting kinda frustrated so I decided to measure
> >> the time spend in kvm_mpic_write and kvm_mpic_read.
Alarm interrupt enable register is at offset 0x7, while the time
registers for the alarm follow that. When we program Alarm interrupt
enable prior to programming the time, it is possible that previous
time value could be close or match at the time of alarm enable
resulting in interrupt trigger
Hi Dmitry,
How about the description? Is it looks good for you?
Please let me know if you have any concern.
--
Thank you,
ELAN Duson
✉ Email: duson...@emc.com.tw
--
> duson 於 2015年4月16日 上午9:37 寫道：
>
>
Hi Dmitry,
Is this patch looks good for you?
If you have any advice, please let me know.
--
Thank you
ELAN Duson
✉ Email: duson...@emc.com.tw
--
> duson 於 2015年4月17日 上午9:56 寫道：
>
> When hover event
On POWER, storage caching is usually configured via the MMU - attributes
such as cache-inhibited are stored in the TLB and the hashed page table.
This makes correctly performing cache inhibited IO accesses awkward when
the MMU is turned off (real mode). Some CPU models provide special
registers
I've written these two patches when I was searching why my old iPod
cannot be mounted on my PC.
During my investigations, I've compared the fw0 config_rom I can access from
a powermac and the config_rom I have on a PC. It appears that the big-endian
property of the firewire bus is not respected
So, dump config_rom data as big-endian values.
The value given by /sys/bus/firewire/devices/fw0 were correctly
given on a big-endian host (like powermac) not on a little-endian host
(like PC), for instance:
87 a4 04 04 34 39 33 31 22 a2 00 f0 33 22 11 00 |4931"...3"..|
0010
I was trying to use my old iPod mini firewire (first generation) with
a new firewire card I put in my PC (VIA Technologies, Inc. VT6306/7/8),
but the iPod was not mounted and failed with the following error:
reading config rom failed: no ack
It appears that the configuration rom cannot be read
On 04/20/2015 10:09 AM, Andrew Cooper wrote:
There appears to be no formal statement of what pv_irq_ops.save_fl() is
supposed to return precisely. Native returns the full flags, while lguest and
Xen only return the Interrupt Flag, and both have comments by the
implementations stating that only
On 04/20/2015 06:55 PM, Nishanth Menon wrote:
> Alarm interrupt enable register is at offset 0x7, while the time
> registers for the alarm follow that. When we program Alarm interrupt
> enable prior to programming the time, it is possible that previous
> time value could be close or match at the
On Mon, 2015-04-20 at 03:58 -0500, Liberman Igal-B31950 wrote:
>
> Regards,
> Igal Liberman.
>
> > -Original Message-
> > From: Kumar Gala [mailto:ga...@kernel.crashing.org]
> > Sent: Thursday, March 12, 2015 5:57 PM
> > To: Liberman Igal-B31950
> > Cc: linuxppc-...@lists.ozlabs.org;
Alarm interrupt enable register is at offset 0x7, while the time
registers for the alarm follow that. When we program Alarm interrupt
enable prior to programming the time, it is possible that previous
time value could be close or match at the time of alarm enable
resulting in interrupt trigger
> On Apr 20, 2015, at 1:17 PM, Andrew Morton wrote:
>
>> On Fri, 17 Apr 2015 14:00:04 -0400 Chris Metcalf wrote:
>>
>> bitmap_parselist("", , nmaskbits) will erroneously set bit
>> zero in the mask. The same bug is visible in cpumask_parselist()
>> since it is layered on top of the bitmask
On Mon, Apr 20, 2015 at 4:34 PM, Tyler Baker wrote:
> On 20 April 2015 at 16:22, Andy Lutomirski wrote:
>> On Mon, Apr 20, 2015 at 4:15 PM, Tyler Baker wrote:
>>> If the CROSS_COMPILE is set remove all's dependency on all_32 and all_64.
>>>
>>> Cc: Andy Lutomirski
>>> Signed-off-by: Tyler
Remove EOL whitespaces added by commit 4961772560d2
("infinibad: weird APIs switched to ->write_iter()")
Signed-off-by: Sergei Zviagintsev
---
drivers/infiniband/hw/qib/qib_file_ops.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/infiniband/hw/qib/qib_file_ops.c
On Mon, Apr 20, 2015 at 11:27:11PM +0200, Hagen Paul Pfeifer wrote:
> During some code analysis I realized that atomic_add, atomic_sub and
> friends are not necessarily inlined AND that each function is defined
> multiple times:
>
> atomic_inc: 544 duplicates
> atomic_dec: 215
On Mon, Apr 20, 2015 at 01:48:03PM -0400, Steven Rostedt wrote:
> On Mon, 20 Apr 2015 19:20:48 +0200
> Peter Zijlstra wrote:
>
> > > > +*/
> > > > + if (preempt_count() & PREEMPT_ACTIVE)
> > > > + enqueue_pushable_task_preempted(rq, p);
> > > >
Hi Luis,
You made a spelling mistake:
On Tue, Apr 21, 2015 at 9:30 AM, Luis R. Rodriguez
wrote:
> From: "Luis R. Rodriguez"
>
> This adds a couple of bool module_param_config_*() helpers
> which are designed to let us easily associate a booloean
> module parameter with an associated kernel
On 20 April 2015 at 16:22, Andy Lutomirski wrote:
> On Mon, Apr 20, 2015 at 4:15 PM, Tyler Baker wrote:
>> If the CROSS_COMPILE is set remove all's dependency on all_32 and all_64.
>>
>> Cc: Andy Lutomirski
>> Signed-off-by: Tyler Baker
>> ---
>> tools/testing/selftests/x86/Makefile | 8
From: "Luis R. Rodriguez"
This takes out the bool_enable_only implementation from
the module loading code and generalizes it so that others
can make use of it.
Cc: Rusty Russell
Cc: Jani Nikula
Cc: Christoph Hellwig
Cc: Andrew Morton
Cc: Geert Uytterhoeven
Cc: Hannes Reinecke
Cc: Kees
From: "Luis R. Rodriguez"
We're directly checking and modifying sig_enforce when needed instead
of using the generic helpers. This prevents us from generalizing this
helper so that others can use it. Use indirect helpers to allow us
to generalize this code a bit and to make it a bit more clear
From: "Luis R. Rodriguez"
Cc: Rusty Russell
Cc: Jani Nikula
Cc: Christoph Hellwig
Cc: Andrew Morton
Cc: Geert Uytterhoeven
Cc: Hannes Reinecke
Cc: Kees Cook
Cc: Tejun Heo
Cc: Ingo Molnar
Cc: linux-kernel@vger.kernel.org
Cc: co...@systeme.lip6.fr
Signed-off-by: Luis R. Rodriguez
---
From: "Luis R. Rodriguez"
This adds a couple of bool module_param_config_*() helpers
which are designed to let us easily associate a booloean
module parameter with an associated kernel configuration
option, and to help us remove #ifdef'ery eyesores.
Cc: Rusty Russell
Cc: Jani Nikula
Cc:
Most code already uses consts for the struct kernel_param_ops,
sweep the kernel for the last offending stragglers. Other than
include/linux/moduleparam.h and kernel/params.c all other changes
were generated with the following Coccinelle SmPL patch. Merge
conflicts between trees can be handled with
From: "Luis R. Rodriguez"
Use the new module_param_config_on_off() for setting / disabling of
CONFIG_WQ_POWER_EFFICIENT_DEFAULT.
Cc: Rusty Russell
Cc: Jani Nikula
Cc: Christoph Hellwig
Cc: Andrew Morton
Cc: Geert Uytterhoeven
Cc: Hannes Reinecke
Cc: Kees Cook
Cc: Tejun Heo
Cc: Ingo
o complete other tasks.
All this goes test compiled on x86_64 on:
* allnoconfig
* allmodconfig
* allyesconfig
This series was based on top of linux-next next-20150420.
Luis R. Rodriguez (6):
kernel/params: constify struct kernel_param_ops uses
kernel/module.c: use generic module param
On Mon, Apr 20, 2015 at 4:15 PM, Tyler Baker wrote:
> If the CROSS_COMPILE is set remove all's dependency on all_32 and all_64.
>
> Cc: Andy Lutomirski
> Signed-off-by: Tyler Baker
> ---
> tools/testing/selftests/x86/Makefile | 8 +++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
>
On Mon, Apr 20, 2015 at 4:15 PM, Tyler Baker wrote:
> Using uname with the processor flag option in some cases can yield 'unknown'
> so lets use the machine flag option as it is deterministic. Add a dependency
> for all_32 when building on a x86 64 bit host so that both bitnesses are
> built in
On Tue, Apr 21, 2015 at 06:59:02AM +0800, Wanpeng Li wrote:
>Hi Juri,
>On Mon, Apr 20, 2015 at 11:27:22AM +0100, Juri Lelli wrote:
>>Hi,
>>
>>On 06/04/2015 09:53, Wanpeng Li wrote:
>>> pull_dl_task can drop (and re-acquire) rq->lock, this means a stop task
>>> can slip in, in which case we need
Em Thu, Apr 09, 2015 at 06:53:44PM +0300, Adrian Hunter escreveu:
> Add support for reading from the AUX area
> tracing mmap and synthesizing AUX area
> tracing events.
>
> This patch introduces an abstraction for recording
> AUX area data. Recording is initialized
> by auxtrace_record__init()
Hi Juri,
On Mon, Apr 20, 2015 at 11:27:22AM +0100, Juri Lelli wrote:
>Hi,
>
>On 06/04/2015 09:53, Wanpeng Li wrote:
>> pull_dl_task can drop (and re-acquire) rq->lock, this means a stop task
>> can slip in, in which case we need to reschedule. This patch add the
>> reschedule when the scenario
Remove subdir from DEPS as it is already created at runtime. Without this,
make install fails.
Acked-by: Michael Ellerman
Signed-off-by: Tyler Baker
---
tools/testing/selftests/exec/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Include lib.mk and set TEST_PROGS where appropriate. Skip the install and test
case when CROSS_COMPILE is not set.
Cc: Andy Lutomirski
Signed-off-by: Tyler Baker
---
tools/testing/selftests/x86/Makefile | 9 +
1 file changed, 9 insertions(+)
diff --git
If the CROSS_COMPILE is set remove all's dependency on all_32 and all_64.
Cc: Andy Lutomirski
Signed-off-by: Tyler Baker
---
tools/testing/selftests/x86/Makefile | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/tools/testing/selftests/x86/Makefile
1 - 100 of 1478 matches
Mail list logo
