Hi Greg,
On Friday 03 April 2015 09:56 PM, Kishon Vijay Abraham I wrote:
Hi Greg,
Please find the pull request for 4.1 merge window. This includes two new PHY
driver, bug fixes and few cleanups.
A patch to add MAINTAINER for miphy PHY drivers has also been included.
There is also a patch that
Commit 779c88c94c34 ("ARM: 8321/1: asm-generic: introduce .text.fixup
input section") introduced a new .text.fixup section which is merged
with .text at link time. This causes xtensa builds to fail with lots
of error messages similar to the following.
lib/lib.a(kobject.o): In function
On 2015/4/7 8:28, Rafael J. Wysocki wrote:
> On Friday, April 03, 2015 10:04:11 PM Bjorn Helgaas wrote:
>> Hi Jiang,
>>> Currently acpi_dev_filter_resource_type() is only used by ACPI pci
>>> host bridge and IOAPIC driver, so it shouldn't affect other drivers.
>>
>> We should assume it will
Hi Chris,
There are no corresponding mpt2sas driver's patches, The last phase
for mpt2sas drivers is Phase20 and this phase driver is already exits
in the upstream kernel. Also mpt2sas driver is completely in maintains
mode and there won't be any new features.
Whereas mpt3sas is at its initial
From: Hiroshi Shimamoto
Add netlink directives and ndo entry to allow VF multicast promiscuous mode.
This controls the permission to enter VF multicast promiscuous mode.
The administrator will dedicatedly allow multicast promiscuous per VF.
When the VF is under multicast promiscuous mode, all
From: Hiroshi Shimamoto
Implements the new netdev op to allow VF multicast promiscuous mode.
The multicast promiscuous mode is not allowed for all VFs by default.
The administrator can allow to VF multicast promiscuous mode for only
trusted VM. After allowing multicast promiscuous mode from
From: Hiroshi Shimamoto
The limitation of the number of multicast address for VF is not enough
for the large scale server with SR-IOV feature.
IPv6 requires the multicast MAC address for each IP address to handle
the Neighbor Solicitation message.
We couldn't assign over 30 IPv6 addresses to a
On Tue, Apr 7, 2015 at 8:49 PM, Benjamin Herrenschmidt
wrote:
> On Tue, 2015-04-07 at 17:24 -0700, Yinghai Lu wrote:
>> For device resource PREF bit setting under bridge 64-bit pref resource,
>> we need to make sure only set PREF for 64bit resource, so set
>> IORESOUCE_MEM_64
>> for 64bit
Hello Tomasz,
On 04/07/2015 11:28 PM, Tomasz Figa wrote:
>
> Looks good to me. You can consider this Acked-by, as long as Sylwester
> is not opposed to this approach.
>
Thanks a lot, I've posted it as a proper patch now.
> Best regards,
> Tomasz
>
Best regards,
Javier
--
To unsubscribe from
Currently, userspace has no way to know which subvolume is mounted. But,
now that we're guaranteed to have a meaningful root dentry, we can just
export and use seq_dentry() in btrfs_show_options(). The subvolume ID is
easy to get, so put that in there, too.
Signed-off-by: Omar Sandoval
---
So this is something that has bothered me as a Btrfs user for some time
and that came up in discussing a separate bug here:
https://lkml.org/lkml/2015/4/2/447.
It turns out that getting the name of a subvolume reliably is a bit
trickier than it would seem because of how mounting subvolumes by ID
Commit ae43b3289186 ("ARM: 8202/1: dmaengine: pl330: Add runtime Power
Management support v12") added pm support for the pl330 dma driver but
it makes the clock for the Exynos5420 MDMA0 DMA controller to be gated
during suspend and this in turn makes its parent clock aclk266_g2d to
be gated. But
Since commit 0723a0473fb4 ("btrfs: allow mounting btrfs subvolumes with
different ro/rw options"), when mounting a subvolume read/write when
another subvolume has previously been mounted read-only, we first do a
remount. However, this should be done with the superblock locked, as per
Currently, mounting a subvolume with subvolid= takes a different code
path than mounting with subvol=. This isn't really a big deal except for
the fact that mounts done with subvolid= or the default subvolume don't
have a dentry that's connected to the dentry tree like in the subvol=
case. To
Hi Andy,
> -Original Message-
> From: linux-arm-kernel [mailto:linux-arm-kernel-
> boun...@lists.infradead.org] On Behalf Of Andy Gross
> Sent: Tuesday, April 07, 2015 10:37 AM
> To: Sricharan R
> Cc: srich...@qti.qualcomm.com; devicet...@vger.kernel.org; linux-arm-
>
On 04/07, Lee Jones wrote:
> Lots of platforms contain clocks which if turned off would prove fatal.
> The only way to recover from these catastrophic failures is to restart
> the board(s). Now, when a clock provider is registered with the
> framework it is possible for a list of always-on clocks
On 2015/4/8 0:49, Jim Bos wrote:
> On 04/07/2015 04:34 PM, Jiang Liu wrote:
>> Hi Jim,
>> Could you please help to test this patch against v4.0-rc6?
>> Thanks!
>> Gerry
>>
>> Signed-off-by: Jiang Liu
>> ---
>> arch/x86/kernel/acpi/boot.c | 10 +++---
>> 1 file changed, 7
On 04/07, Lee Jones wrote:
> Signed-off-by: Lee Jones
> ---
Can you please add some commit text here? Why did we make this
change?
> .../devicetree/bindings/clock/clock-bindings.txt | 38
> ++
> 1 file changed, 38 insertions(+)
>
> diff --git
On 04/07, Lee Jones wrote:
> Lots of platforms contain clocks which if turned off would prove fatal.
> The only way to recover from these catastrophic failures is to restart
> the board(s). Now, when a clock provider is registered with the
> framework it is possible for a list of always-on clocks
Hi all,
On Tue, 07 Apr 2015 21:54:05 +0200 Daniel Borkmann wrote:
>
> On 04/07/2015 06:18 PM, Alexei Starovoitov wrote:
> > On 4/7/15 4:13 AM, Daniel Borkmann wrote:
> >> [ Cc'ing Dave, fyi ]
> >>
> >> On 04/07/2015 11:05 AM, Stephen Rothwell wrote:
> >>> On Tue, 07 Apr 2015 10:56:13 +0200
Show message when errors occurred during ctf conversion setup.
Before this patch:
$ ./perf data convert --to-ctf=ctf
$ echo $?
255
After this patch:
$ ./perf data convert --to-ctf=ctf
Error during CTF convert setup.
Signed-off-by: He Kuang
---
tools/perf/util/data-convert-bt.c | 8
Due to babeltrace commit:
7f800dc7c2a1 ("ir: make trace environment use bt_object")
The trace->frozen flag is set in bt_ctf_trace_create_stream(), this flag
is checked before adding environment field to trace, and causes
ctf_writer__setup_env() failed. Fix this by setting all environment
fields
Hi,
If you turn off a PCI device whose driver has set affinity_hint,
you will get warning message which does _not_ explain the reason
why it appeared from the user's point of view.
# echo 0 > /sys/bus/pci/slots/65/power
Apr 28 20:29:39 localhost kernel: [ cut here ]
On Tue, Apr 7, 2015 at 8:42 PM, Michael Ellerman wrote:
> On Mon, 2015-04-06 at 23:11 -0700, Andy Lutomirski wrote:
>> On Mon, Apr 6, 2015 at 8:39 PM, Michael Ellerman wrote:
>> > On Mon, 2015-04-06 at 19:01 -0700, Andy Lutomirski wrote:
>> >> This is my sigreturn test, added mostly unchanged
On Tue, Apr 07, 2015 at 02:25:39PM +, Dhere, Chaitanya (C.) wrote:
> This change was detected with the help of coccinelle tool.
> It performs the same function as kzalloc amd memcpy.
>
> Signed-off-by: Chaitanya Dhere
your From: name and this name does not match.
regards
sudip
--
To
On Tue, Mar 31, 2015 at 10:37:51AM -0600, Shuah Khan wrote:
> On 03/31/2015 10:24 AM, Darren Hart wrote:
> > On 3/31/15, 8:32 AM, "Shuah Khan" wrote:
> >
> >> Hi Daren,
> >>
> >> On 03/27/2015 04:17 PM, Darren Hart wrote:
> >>> Hi Shuah,
> >>>
> >>> This series begins the process of migrating my
On Sun, Apr 05, 2015 at 11:11:49PM +0200, Pali Rohár wrote:
> On Thursday 02 April 2015 07:10:27 Darren Hart wrote:
> > On Sun, Mar 29, 2015 at 03:38:50PM +0200, Pali Rohár wrote:
> >
> > Please include why. No empty commit messages please.
> >
> > For example, you've written nearly a third of
On Thu, 2015-04-02 at 11:02 -0700, John Stultz wrote:
> On Thu, Apr 2, 2015 at 3:18 AM, Prarit Bhargava wrote:
> > On 03/26/2015 01:33 PM, Tyler Baker wrote:
> >> I realize this may be a good amount of work, so I'd like to help out.
> >> Perhaps working John to convert his timer tests to use TAP
Commit 31a9883106cc ("perf record: Add clockid parameter") used
CLOCK_MONOTONIC_RAW in the struct clockid_map clockids[], but the
CLOCK_MONOTONIC_RAW macro is not defined in older releases (e.g., SLES
11 SP2), thus there is a building error when making perf:
builtin-record.c:738: error:
perf report and perf annotate are easy to trigger segfault if trace data
contain kernel module information like this:
# perf report -D -i ./perf.data
...
0 0 0x188 [0x50]: PERF_RECORD_MMAP -1/0: [0xffbff1018000(0xf068000) @ 0]:
x [test_module]
...
# perf report -i ./perf.data
On Thu, Apr 02, 2015 at 07:26:19PM -0600, Azael Avalos wrote:
> This patch fixes the USB Sleep & Charge charging mode on certain
> models, fixes pr_* messages and also adds the missing entries in the
> documentation file.
>
> Changes since v2:
> - Check for TOS_SUCCESS to initialize and flag as
On 2015/4/7 23:13, Arnaldo Carvalho de Melo wrote:
> Em Tue, Apr 07, 2015 at 08:22:46AM +, Wang Nan escreveu:
>> perf report and perf annotate are easy to trigger segfault if trace data
>> contain kernel module information like this:
>>
>> # perf report -D -i ./perf.data
>> ...
>> 0 0 0x188
On Mon, 2015-04-06 at 23:11 -0700, Andy Lutomirski wrote:
> On Mon, Apr 6, 2015 at 8:39 PM, Michael Ellerman wrote:
> > On Mon, 2015-04-06 at 19:01 -0700, Andy Lutomirski wrote:
> >> This is my sigreturn test, added mostly unchanged from its old home.
> >> It exercises the sigreturn(2) syscall,
On 04/07/15 at 05:55pm, Li, ZhenHua wrote:
> On 04/07/2015 05:08 PM, Dave Young wrote:
> >On 04/07/15 at 11:46am, Dave Young wrote:
> >>On 04/05/15 at 09:54am, Baoquan He wrote:
> >>>On 04/03/15 at 05:21pm, Dave Young wrote:
> On 04/03/15 at 05:01pm, Li, ZhenHua wrote:
> >Hi Dave,
> >
|
e164ade07b | next-20150407 |
+--+++---+
| boot_successes | 0 | 0
| 0 |
| boot_failures| 80
On Fri, 2015-03-20 at 18:52 -0500, Scott Wood wrote:
> On Fri, Dec 05, 2014 at 12:20:20PM +0100, LEROY Christophe wrote:
> > include/linux/mm.h: In function 'is_vmalloc_addr':
> > include/linux/mm.h:367:14: warning: comparison between signed and unsigned
> > integer expressions [-Wsign-compare]
>
On Tue, Apr 07, 2015 at 09:02:14AM +0200, Christoph Hellwig wrote:
> FYI, the ext4 tree seems to have the crypto support, which I don't think is
> ready for 4.1 with all the implications of it..
What sort of implications are you concerned about? We're no longer
exposing anything via the xattr
On Tue, Apr 07, 2015 at 01:32:12PM +0200, Peter Zijlstra wrote:
> > I propose to send all this stuff though the trivial tree such that
> > maintainers
> > of other subsystems have less workload and newbies (which are supposed
> > to send such patches) know which tree they have to work against.
>
On 04/03/2015 07:50 AM, Alex Williamson wrote:
Should have sent this with the other comments, but found it hiding on my
desktop...
On Sat, 2015-03-28 at 01:55 +1100, Alexey Kardashevskiy wrote:
In order to support memory pre-registration, we need a way to track
the use of every registered
nimisolo,
在 4/8/2015 10:10 AM, nimisolo 写道:
Hi Jens,
In blk_mq_map_swqueue(), all the blk_mq_hw_ctx's nr_ctx are set
to zero, and then each blk_mq_ctx's index_hw is set to nr_ctx.
I think the index_hw means the index of the hardware queue that map
to this software queue, so maybe index_hw
Hi, Arnaldo
On 2015/4/7 20:36, Arnaldo Carvalho de Melo wrote:
Em Tue, Apr 07, 2015 at 05:31:11PM +0800, He Kuang escreveu:
After perf_evlist__filter_pollfd() filters out fds and releases
perf_mmap by using perf_evlist__mmap_put(), refcnt of perf_mmap hits 1
then perf_evlist__mmap_consume()
On Fri, 3 Apr 2015 08:44:47 +0800 Gu Zheng wrote:
> Simon reported the md io stats accounting issue:
> "
> I'm seeing "iostat -x -k 1" print this after a RAID1 rebuild on 4.0-rc5.
> It's not abnormal other than it's 3-disk, with one being SSD (sdc) and
> the other two being write-mostly:
>
>
On 04/08/15 at 10:41am, Xishi Qiu wrote:
> On 2015/4/8 10:18, Baoquan He wrote:
>
> > On 04/08/15 at 09:59am, Xishi Qiu wrote:
> >> On 2015/4/8 9:46, Dave Young wrote:
> >>
> >
> > - /* Mark all kernel nodes. */
> > + /*
> > +* Mark all kernel nodes.
> >
On 2015/4/8 10:18, Baoquan He wrote:
> On 04/08/15 at 09:59am, Xishi Qiu wrote:
>> On 2015/4/8 9:46, Dave Young wrote:
>>
>
> - /* Mark all kernel nodes. */
> + /*
> + * Mark all kernel nodes.
> + *
> + * In case booting with mem=nn[kMG] or in kdump kernel,
On Mon, Apr 06, 2015 at 01:31:41PM -0600, Jun He wrote:
> This patch addresses the tail allocation problem found at paper "Reducing
> File System Tail Latencies with Chopper".
> https://www.usenix.org/system/files/conference/fast15/fast15-paper-he.pdf .
> The paper refers the tail allocation
On Tue, Apr 7, 2015 at 4:43 PM, Denys Vlasenko wrote:
> The change which affected how execve clears EXTRA_REGS missed
> 32-bit execve syscalls.
>
> Fix this by using 64-bit execve stub epilogue for them too.
>
> Run-tested.
>
> Signed-off-by: Denys Vlasenko
> CC: Linus Torvalds
> CC: Steven
(2015/04/08 11:14), Wang Nan wrote:
> Commit 9b118acae310f57baee770b5db402500d8695e50 ("perf probe: Fix to
> handle aliased symbols in glibc") uses an absolute format '%lx' to
> print u64 argument, which causes compiling error on ARM 32.
>
> This patch replaces it with PRIx64.
Good catch! :)
On 15-04-06 09:19 AM, Mark Brown wrote:
On Thu, Apr 02, 2015 at 11:47:18AM -0700, Lori Hikichi wrote:
On 15-03-30 11:42 PM, Mark Brown wrote:
+config SND_SOC_CYGNUS
+ tristate "SoC platform audio for Broadcom Cygnus chips"
+ depends on ARCH_BCM_CYGNUS || COMPILE_TEST
+
On 15-04-06 02:58 AM, Mark Brown wrote:
On Fri, Apr 03, 2015 at 12:33:12PM -0700, Scott Branden wrote:
On 15-03-30 11:43 PM, Mark Brown wrote:
On Mon, Mar 30, 2015 at 08:16:22PM -0700, Scott Branden wrote:
The audio PLL is embedded in the audio block and only used
by the audio block. The
On 04/08/15 at 09:59am, Xishi Qiu wrote:
> On 2015/4/8 9:46, Dave Young wrote:
>
> >>>
> >>> - /* Mark all kernel nodes. */
> >>> + /*
> >>> + * Mark all kernel nodes.
> >>> + *
> >>> + * In case booting with mem=nn[kMG] or in kdump kernel, numa_meminfo
> >>
> >> Hi Dave,
> >>
> >> It should
Commit 9b118acae310f57baee770b5db402500d8695e50 ("perf probe: Fix to
handle aliased symbols in glibc") uses an absolute format '%lx' to
print u64 argument, which causes compiling error on ARM 32.
This patch replaces it with PRIx64.
Signed-off-by: Wang Nan
---
tools/perf/util/probe-event.c | 3
Hi Jens,
In blk_mq_map_swqueue(), all the blk_mq_hw_ctx's nr_ctx are set
to zero, and then each blk_mq_ctx's index_hw is set to nr_ctx.
I think the index_hw means the index of the hardware queue that map
to this software queue, so maybe index_hw should be set to
blk_mq_hw_ctx's
On 2015/4/8 9:46, Dave Young wrote:
>>>
>>> - /* Mark all kernel nodes. */
>>> + /*
>>> +* Mark all kernel nodes.
>>> +*
>>> +* In case booting with mem=nn[kMG] or in kdump kernel, numa_meminfo
>>
>> Hi Dave,
>>
>> It should both set mem=xx and numa=off, then numa_meminfo may
On 04/07/2015 08:56 AM, Konrad Rzeszutek Wilk wrote:
Hey Jens,
Please git pull the following tree:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
stable/for-jens-4.1
which is based on your for-4.1/drivers branch. Specifically
commit de9ad6d4edb63e0ba5d5aae365fb3565064fc00d
On Tue, Mar 31, 2015 at 2:37 AM, Ivan T. Ivanov wrote:
> Add compatible string definitions and supported pin functions.
>
> Signed-off-by: Ivan T. Ivanov
> ---
[..]
> diff --git a/include/dt-bindings/pinctrl/qcom,pmic-gpio.h
> b/include/dt-bindings/pinctrl/qcom,pmic-gpio.h
[..]
>
> +#define
show detailed free pages per each migrate type in show_free_areas.
Signed-off-by: Neil Zhang
---
mm/internal.h |2 ++
mm/page_alloc.c | 55 ++-
mm/vmstat.c | 13 -
3 files changed, 28 insertions(+), 42 deletions(-)
On Tue, Apr 07, 2015 at 07:05:30PM +0800, Xie XiuQi wrote:
> Export 'outcome' and 'page_type' to mm.h, so we could use this emnus
> outside.
>
> This patch is preparation for adding trace events for memory-failure
> recovery action.
>
> Signed-off-by: Xie XiuQi
I made some update on
Hi Javier,
On Tue, Apr 7, 2015 at 8:30 PM, Javier Martinez Canillas
wrote:
> Hello Abhilash,
>
> On 04/07/2015 04:38 PM, Abhilash Kesavan wrote:
>>>
>>> [0]
>>> From 78aa551ebcb9a4a7ae9d5581c33e0c0f19fe5ad6 Mon Sep 17 00:00:00 2001
>>> From: Javier Martinez Canillas
>>> Date: Tue, 7 Apr 2015
> >
> > - /* Mark all kernel nodes. */
> > + /*
> > +* Mark all kernel nodes.
> > +*
> > +* In case booting with mem=nn[kMG] or in kdump kernel, numa_meminfo
>
> Hi Dave,
>
> It should both set mem=xx and numa=off, then numa_meminfo may not include all
> the memblock.reserved
On Tue, Apr 07, 2015 at 07:05:31PM +0800, Xie XiuQi wrote:
> RAS user space tools like rasdaemon which base on trace event, could
> receive mce error event, but no memory recovery result event. So, I
> want to add this event to make this scenario complete.
>
> This patch add a event at ras group
On 2015/4/7 21:41, Dave Young wrote:
> I got below kernel panic during kdump test on Thinkpad T420 laptop:
>
> [0.00] No NUMA configuration found
>
> [0.00] Faking a node at [mem 0x-0x37ba4fff]
>
> [
Hi Brian,
Can you help me to review this patch of mine?
Thanks,
Nga
On Mon, Mar 16, 2015 at 4:16 PM, wrote:
> From: VIET NGA DAO
>
> Altera Quad SPI Controller is a soft IP which enables access to Altera EPCQ
> and
> EPCS flash chips. This patch adds driver for these devices.
>
>
On Tue, Apr 07, 2015 at 03:09:46PM +0200, Linus Walleij wrote:
> On Mon, Mar 30, 2015 at 3:05 PM, Thierry Reding wrote:
> > On Sun, Mar 29, 2015 at 03:49:20PM +0800, kbuild test robot wrote:
> >> drivers/pinctrl/pinctrl-max77620.c:472:3-8: No need to set .owner here.
> >> The core will do it.
>
>> +/*
>> + * If support CONFIG_PCI_DOMAINS_GENERIC, use
>> + * pci_host_assign_domain_nr() to update domain
>> + * number.
>> + */
>> +host->domain = domain;
>> +pci_host_assign_domain_nr(host);
>
> I think it's a bit confusing that there's another "host->domain ="
>
Hajime Tazaki writes:
> is it the following ? it's really cool stuff !
>
> https://github.com/rustyrussell/pettycoin/blob/master/test/mockup.sh
Yep. It's ugly, but it Works For Me(TM).
Cheers,
Rusty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Linus Torvalds writes:
> Alternatively, we could just limit module loading size to some (fairly
> arbitrary) big number.
Yeah, we used to do that because vmalloc would BUG rather than
returning NULL.
But you're already CAP_SYS_MODULE in this path, which kind of makes it
hard to care very much
Yes; reverting the patch does fix the problem.
On Wed, 2015-04-08 at 01:56 +0300, Dan Carpenter wrote:
> So it's 03ad6a8c93b6df2 ('ALSA: hda - Fix "PCM" name being used on > one
> DAC when there are two DACs') which causes the problem? Have you
> tried
> to just revert that patch?
>
> git show
On Tue, Apr 07, 2015 at 03:56:35PM +0100, Russell King - ARM Linux wrote:
> On Mon, Apr 06, 2015 at 01:24:13PM -0700, Stephen Boyd wrote:
> > Writes to /sys/.../cpuX/online fail if we determine the platform
> > doesn't support hotplug for that CPU. Furthermore, if the cpu_die
> > op isn't
Could you please provide some examples that I can investigate?
Thanks!
2015-04-08 2:05 GMT+08:00 Austin S Hemmelgarn :
> On 2015-04-07 06:09, Mike Galbraith wrote:
>> On Tue, 2015-04-07 at 15:56 +0800, Pengfei Yuan wrote:
>>> I am trying legacy GCC versions.
>>> But I am not able to try different
On 04/06/2015 07:59 PM, Steven Rostedt wrote:
>
Thanks for the comments.
> Hmm, why is it not allowed?
>
> If we just let it boost it, it will cut down on the code changes and
> checks that add to the hot paths.
>
There is a WARN_ON() at line 3150 in sched/core.c to warn against
boosting
This change makes it so that instead of using smp_wmb/rmb which varies
depending on the kernel configuration we can can use dma_wmb/rmb which for
most architectures should be equal to or slightly more strict than
smp_wmb/rmb.
The advantage to this is that these barriers are available to
On Tue, Apr 07, 2015 at 03:16:54PM +0200, Geert Uytterhoeven wrote:
> On Mon, Apr 6, 2015 at 2:40 AM, Simon Horman wrote:
> > On Fri, Apr 03, 2015 at 02:41:58PM +0200, Geert Uytterhoeven wrote:
> >> This reverts commit d13778d537a0ed6115d2a79a942af999cfb8eec6.
> >>
> >> Commit 13c11072536f2613
Currently, the PMU interface allows reading only one counter at a time.
But some PMUs like the 24x7 counters in Power, support reading several
counters at once. To leveage this functionality, extend the transaction
interface to support a "transaction type".
The first type, PERF_PMU_TXN_ADD,
Define a new PERF_PMU_TXN_READ interface to read a group of counters
at once. Note that we use this interface with all PMUs.
PMUs that implement this interface will queue the counters to be read
in ->read() and read them all at once in ->commit_txn().
PMUs that don't implement PERF_PMU_TXN_READ
Please disregard this, I messed up on the indexing. Will resubmit after fixing.
On Tue, Apr 7, 2015 at 4:34 PM, Feng Kan wrote:
> This will add support for ACPI parsing of the mboxes attribute
> when booting with ACPI table. The client will have a attribute
> mimic the dts call "mboxes". In the
The 24x7 counters in Powerpc allow monitoring a large number of counters
simultaneously. They also allow reading several counters in a single
HCALL so we can get a more consistent snapshot of the system.
Use the PMU's transaction interface to monitor and read several event
counters at once. The
perf_event_read_value() is mostly computing the event count and enabled/
running times. Move the perf_event_read() into caller and rename
perf_event_read_value() to perf_event_compute_values().
Changelog[v2]
Export symbol perf_event_read() since x86/kvm needs it now.
Signed-off-by:
Unlike normal hardware PMCs, the 24x7 counters[1] in Power8 are stored in
memory and accessed via a hypervisor call (HCALL). A major aspect of the
HCALL is that it allows retireving _SEVERAL_ counters at once (unlike
regular PMCs, which are read one at a time). By reading several counters
at
perf_event_read() does two things:
- call the PMU to read/update the counter value
- and compute the total count of the event and its children
perf_event_reset() needs the first piece but doesn't need the second.
Similarly, when we implement the ability to read a group of events
This change allows atmel_mxt_ts to bind to ACPI-enumerated devices in
Google Pixel 2 (2015).
While newer version of ACPI standard allow use of device-tree-like
properties in device descriptions, the version of ACPI implemented in
Google BIOS does not support them, and we have to resort to DMI
Atmel controolers are very flexible and to function optimally require
device-specific configuration to be loaded. While the configuration is
stored in NVRAM and is normally persistent, sometimes it gets corrupted
and needs to be reloaded.
Instead of using the same name, maxtouch.cfg, for all
Andrew Morton writes:
> On Tue, 07 Apr 2015 16:27:44 -0700 Kevin Hilman wrote:
>
>> >> > It should all be there today?
>> >>
>> >> Nope.
>> >
>> > huh, I swear I did an mmotm yesterday.
>>
>> Well, based on the timestamp of the mmotm dir on ozlabs, it appears you
>> did. That's why I was
On Tue, 2015-04-07 at 16:28 -0700, Jason Low wrote:
> Okay, so perhaps we can also try continuing nohz load balancing if we
> find that there are overloaded CPUs in the system.
Something like the following.
---
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index fdae26e..d636bf7 100644
This is a refresh of a David Daney's patch set to implement MIPS support
for perf. It has been posted before but not received any comments or
(N)Acks.
This series depends on
http://patchwork.linux-mips.org/patch/5246/
which currently is pending for 4.1 in the MIPS tree so I'd like to
From: David Daney
Define a new symbol (ARCH_SUPPORTS_LIBUNWIND) in config/Makefile.
Use this from x86 and MIPS to gate testing of libunwind.
Signed-off-by: David Daney
Cc: linux-m...@linux-mips.org
Cc: Jiri Olsa
Cc: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra
Cc: Paul Mackerras
Cc: Ingo
From: David Daney
Hack up the Makefile and add support code for mips unwinding
and dwarf-regs.
Signed-off-by: David Daney
Cc: linux-m...@linux-mips.org
Cc: Jiri Olsa
Cc: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra
Cc: Paul Mackerras
Cc: Ingo Molnar
Cc: Arnaldo Carvalho de Melo
On Tue, 2015-04-07 at 16:33 -0700, Eric Dumazet wrote:
> On Tue, 2015-04-07 at 15:57 -0700, Tuan Bui wrote:
> > Hi all,
> >
> > I am consistently seeing this kernel panic on a 16 sockets machine
> > running Spark PageRank workload using Docker. I am running RHEL 7.0
> > stock kernel which is
On 4/7/15 5:41 PM, David Ahern wrote:
what happened to this patch? not in your core or urgent branches and
perf-script is still bombing
d'oh. never mind; user error.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
3.13.11-ckt19 -stable review patch. If anyone has any objections, please let
me know.
--
From: Paolo Bonzini
commit 4ff6f8e61eb7f96d3ca535c6d240f863ccd6fb7d upstream.
This has been broken for a long time: it broke first in 2.6.35, then was
almost fixed in 2.6.36 but this
3.13.11-ckt19 -stable review patch. If anyone has any objections, please let
me know.
--
From: Mathias Nyman
commit 6596a926b0b6c80b730a1dd2fa91908e0a539c37 upstream.
Include the high order bit fields for Max scratchpad buffers when
calculating how many scratchpad buffers
3.13.11-ckt19 -stable review patch. If anyone has any objections, please let
me know.
--
From: =?UTF-8?q?Kristina=20Mart=C5=A1enko?=
commit 89bb35e200bee745c539a9e0792301ca40f1 upstream.
Using the touchscreen while running buffered capture results in the
buffer reporting
3.13.11-ckt19 -stable review patch. If anyone has any objections, please let
me know.
--
From: =?UTF-8?q?Urs=20F=C3=A4ssler?=
commit da019f59cb16570e78feaf10380ac65a3a06861e upstream.
When not using the "_optional" function, a dummy regulator is returned
and the driver fails
3.13.11-ckt19 -stable review patch. If anyone has any objections, please let
me know.
--
From: Rasmus Villemoes
commit 19e353f2b344ad86cea6ebbc0002e5f903480a90 upstream.
The intention is obviously to sign-extend a 12 bit quantity. But
because of C's promotion rules, the
3.13.11-ckt19 -stable review patch. If anyone has any objections, please let
me know.
--
From: George Cherian
commit 96e5d31244c5542f5b2ea81d76f14ba4b8a7d440 upstream.
In the wrapper the IRQ disable should be done by writing 1's to the
IRQ*_CLR register. Existing code is
3.13.11-ckt19 -stable review patch. If anyone has any objections, please let
me know.
--
From: =?UTF-8?q?Kristina=20Mart=C5=A1enko?=
commit f81197b8a31b8fb287ae57f597b5b6841e1ece92 upstream.
The touchscreen was initially designed [1] to map all of its physical
channels to
3.13.11-ckt19 -stable review patch. If anyone has any objections, please let
me know.
--
From: Alan Stern
commit f0c2b68198589249afd2b1f2c4e8de8c03e19c16 upstream.
When a signal is delivered, the information in the siginfo structure
is copied to userspace. Good security
what happened to this patch? not in your core or urgent branches and
perf-script is still bombing
On 3/31/15 7:36 AM, David Ahern wrote:
On 3/31/15 6:59 AM, Arnaldo Carvalho de Melo wrote:
Em Mon, Mar 30, 2015 at 08:45:33PM -0300, Arnaldo Carvalho de Melo
escreveu:
Em Mon, Mar 30, 2015 at
3.13.11-ckt19 -stable review patch. If anyone has any objections, please let
me know.
--
From: Yinghai Lu
commit 7ed620bb343f434f8a85f830020c04988df2a140 upstream.
While adding support loading kernel and initrd above 4G to grub2 in legacy
mode, I was referring to
3.13.11-ckt19 -stable review patch. If anyone has any objections, please let
me know.
--
From: Mark Glover
commit f6950344d3cf4a1e231b5828b50c4ac168db3886 upstream.
These product identifiers (PID) all deal with marine NMEA format data
used on motor boats and yachts. We
3.13.11-ckt19 -stable review patch. If anyone has any objections, please let
me know.
--
From: Johan Hovold
commit 07fdfc5e9f1c966be8722e8fa927e5ea140df5ce upstream.
Fix return value in probe error path, which could end up returning
success (0) on errors. This could in turn
1 - 100 of 2338 matches
Mail list logo
