On Sun, Apr 3, 2016 at 8:55 AM, Linus Torvalds
wrote:
>
> I'm just about to leave for the airport, so I probably will not get to
> it until tomorrow, but if you still don't see it in 24 hours, ping me
> and call me harebrained.
Ok, it's merged in my tree now, just going through the built tests
et
Hi,
We received a bug report
(https://bugzilla.redhat.com/show_bug.cgi?id=1323440)
WARNING: CPU: 3 PID: 765 at kernel/sched/core.c:7557
__might_sleep+0x75/0x80()
do not call blocking ops when !TASK_RUNNING; state=1 set at
[] lirc_dev_fop_read+0x1e1/0x590 [lirc_dev]
CPU: 3 PID: 765 Comm: lirc
Am 04.04.2016 um 19:25 schrieb Han Xu:
> fix the raw_buffer pointer double free issue found by coverify.
Can you please include the coverity message in you changelog?
> Signed-off-by: Han Xu
> ---
> drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a
On 04/04/2016 08:22 AM, Peter Zijlstra wrote:
This new form allows using hardware assisted waiting.
Requested-by: Will Deacon
Suggested-by: Linus Torvalds
Signed-off-by: Peter Zijlstra (Intel)
---
include/linux/compiler.h | 25 +++--
kernel/locking/qspinlock.c | 12 +
Using this requires software triggers like CONFIG_IIO_HRTIMER_TRIGGER.
The device can be configured to do internal periodic sampling but does not
offer some sort of interrupt on data ready. Interrupts can only trigger when
values get out of a specific range.
Signed-off-by: Crestez Dan Leonard
--
Changes since last version:
* Use struct adcxx1_model in the first patch as well.
* Use VLA buf in adc081c_trigger_handler.
* Rerrange code so the diffs look nicer.
* Fixed other smaller review comments.
I did not add an enum for models because it's not clear how adding another
layer of indire
On Thu, Mar 31, 2016 at 03:12:39PM +0200, Miroslav Benes wrote:
> On Fri, 25 Mar 2016, Josh Poimboeuf wrote:
>
> [...]
>
> > diff --git a/kernel/fork.c b/kernel/fork.c
> > index d277e83..27b181e 100644
> > --- a/kernel/fork.c
> > +++ b/kernel/fork.c
> > @@ -76,6 +76,7 @@
> > #include
> > #incl
pm_runtime_disable is called only in remove it is missed
out in the error path.
Fix the same.
Signed-off-by: Shubhrajyoti Datta
---
drivers/gpio/gpio-zynq.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/drivers/gpio/gpio-zynq.c b/drivers/gpio/gpio-zynq.c
index 66d3d
These chips has an almost identical interface but a deal with a
different number of value bits. Datasheet links for comparison:
* http://www.ti.com/lit/ds/symlink/adc081c021.pdf
* http://www.ti.com/lit/ds/symlink/adc101c021.pdf
* http://www.ti.com/lit/ds/symlink/adc121c021.pdf
Signed-off-by: C
On Sat, Apr 02, 2016 at 10:22:44PM +0200, Takashi Iwai wrote:
> On Sat, 02 Apr 2016 20:05:21 +0200,
> Andy Lutomirski wrote:
> >
> > On Apr 2, 2016 12:07 PM, "Takashi Iwai" wrote:
> > >
> > > On Sat, 02 Apr 2016 14:57:44 +0200,
> > > Andy Lutomirski wrote:
> > > >
> > > > On Fri, Apr 1, 2016 at 1
On Mon, Apr 04, 2016 at 08:27:59PM +0200, Vojtech Pavlik wrote:
> On Mon, Apr 04, 2016 at 01:21:38PM -0500, Josh Poimboeuf wrote:
>
> > Hm, can you explain why it should be copied from the parent?
> >
> > I'm thinking the above code is correct for today, but it should still be
> > changed to be m
Hi Crestez,
[auto build test WARNING on iio/togreg]
[also build test WARNING on v4.6-rc2 next-20160404]
[if your patch is applied to the wrong git tree, please drop us a note to help
improving the system]
url:
https://github.com/0day-ci/linux/commits/Crestez-Dan-Leonard/Add-support-for
On Mon, Apr 04, 2016 at 09:12:28PM +0530, Shyam Saini wrote:
> 'unsigned int gpio' is added in place of 'unsigned gpio'
>
> Signed-off-by: Shyam Saini
> ---
> drivers/staging/android/timed_gpio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
This file is no longer in linux-next, pleas
On Mon, Apr 04, 2016 at 04:02:08PM +0200, Peter Zijlstra wrote:
> This triggered on AMD machines..
>
> ---
> Subject: perf,amd: Do not register a task ctx for uncore PMUs
>
> Uncore PMUs are per node, they cannot have per-task counters.
>
> Reported-by: Borislav Petkov
^
-an
On Mon, Apr 04, 2016 at 09:04:48AM -0700, Mark Brown wrote:
> On Mon, Apr 04, 2016 at 01:47:50PM +0300, Felipe Balbi wrote:
> > Mark Brown writes:
>
> > > It does in this new world order. IIRC on an earlier round of review
> > > there was some code that didn't use a bus but that got complaints t
On Mon, Apr 04, 2016 at 06:16:12PM +0100, Al Viro wrote:
> will see NULL map_data; the ->from_user case is sg_start_req() stuff. IOW,
> SG_IO behaviour for /dev/sg* is different from the generic one...
While we are at it: in bio_map_user_iov() we have
iov_for_each(iov, i, *iter) {
On 29/03/2016 at 08:55:57 +0200, Mylène Josserand wrote :
> This patchset updates the m41t80 driver :
> - update the sysfs entries export to use DEVICE_ATTR_XX
> - remove some unnecessary macro
> - replace old i2c functions to smbus ones
> - use BIT macro
> - remove some warnings
> - re
Hi Linus,
Please pull the following fixes for 4.6-rc3. diff attached.
thanks,
-- Shuah
-
The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
are
of_map_mode is needed so to be possible to set initial regulators mode from
the board DTS. Otherwise, for DT boot, regulators are left in their default
state after reset/reboot. Document device specific modes as well.
Signed-off-by: Ivaylo Dimitrov
---
.../devicetree/bindings/regulator/twl-regul
On Mon, Apr 4, 2016 at 4:29 AM, Ulf Hansson wrote:
>
> The commit that's likely to cause the regression is:
> 520bd7a8b415 ("mmc: core: Optimize boot time by detecting cards
> simultaneously").
Peter, mind testing if you can revert that and get the old behavior
back? It seems to still revert clea
Hi Johannes,
On 2016-04-04 13:13:35 -0400, Johannes Weiner wrote:
> this is a follow-up to http://www.spinics.net/lists/linux-mm/msg101739.html
> where Andres reported his database workingset being pushed out by the
> minimum size enforcement of the inactive file list - currently 50% of cache
> -
On Mon, Apr 04, 2016 at 01:21:38PM -0500, Josh Poimboeuf wrote:
> Hm, can you explain why it should be copied from the parent?
>
> I'm thinking the above code is correct for today, but it should still be
> changed to be more future-proof.
>
> Here's my thinking:
>
> A forked task starts out wit
On Sun, Apr 3, 2016 at 11:25 AM, Russell King - ARM Linux
wrote:
> On Sun, Apr 03, 2016 at 11:39:18PM +0900, Masahiro Yamada wrote:
>> We have growing number of mach-* directories in arch/arm, and I guess
>> it might be a good time to discuss moving them into a sub-directory.
>
> What does it buy
On Mon, 4 Apr 2016, Waiman Long wrote:
> > > + if ((unsigned int)stat>= pcs->nstats)
> > > + return;
> > > + preempt_disable();
> > > + pstat = this_cpu_ptr(&pcs->stats[stat]);
> > > + *pstat += cnt;
> > > + preempt_enable();
> > > +}
> > pstat = get_cpu_ptr(&pcs->stats[stat]);
> > *pstat
On Fri, 2016-04-01 at 15:42 -0400, Chris Metcalf wrote:
> On arm64, when calling enqueue_task_fair() from migration_cpu_stop(),
> we find the nr_running value updated by add_nr_running(), but the
> cfs.nr_running value has not always yet been updated. Accordingly,
> the sched_can_stop_tick() false
On 4 April 2016 21:12:23 CEST, Rik van Riel wrote:
>What is the difference between cfs_rq->h_nr_running,
>and rq->cfs.nr_running?
>
>Why do we have two?
H is for hierarchy. That counts the total of runnable tasks in the entire child
hierarchy. Nr_running is the number of se entities in the
On 04/04/2016 11:59 AM, Linus Torvalds wrote:
> On Mon, Apr 4, 2016 at 4:29 AM, Ulf Hansson wrote:
>>
>> The commit that's likely to cause the regression is:
>> 520bd7a8b415 ("mmc: core: Optimize boot time by detecting cards
>> simultaneously").
>
> Peter, mind testing if you can revert that and
On 4/4/2016 3:12 PM, Rik van Riel wrote:
On Fri, 2016-04-01 at 15:42 -0400, Chris Metcalf wrote:
On arm64, when calling enqueue_task_fair() from migration_cpu_stop(),
we find the nr_running value updated by add_nr_running(), but the
cfs.nr_running value has not always yet been updated. Accordin
On Thu, Mar 31, 2016 at 2:24 PM, Mimi Zohar wrote:
> On Mon, 2016-03-28 at 14:14 -0700, Kees Cook wrote:
>
>> +static const char *id_str[READING_MAX_ID] = {
>> + [READING_FIRMWARE] = "firmware",
>> + [READING_MODULE] = "kernel module",
>> + [READING_KEXEC_IMAGE] = "kexec image",
>> +
On Mon, Apr 4, 2016 at 7:03 PM, Mark Brown wrote:
> On Mon, Apr 04, 2016 at 01:25:56PM +0300, Octavian Purdila wrote:
>> On Sat, Apr 2, 2016 at 7:24 PM, Mark Brown wrote:
>
>> > What I don't understand is why the flow on inital probe isn't simply to
>> > register the controller which then trigger
On Mon, 2016-04-04 at 15:31 -0400, Chris Metcalf wrote:
> On 4/4/2016 3:12 PM, Rik van Riel wrote:
> >
> > On Fri, 2016-04-01 at 15:42 -0400, Chris Metcalf wrote:
> > >
> > > On arm64, when calling enqueue_task_fair() from
> > > migration_cpu_stop(),
> > > we find the nr_running value updated by
Hello, Parav.
Sorry about the delay.
> +struct rdma_cgroup {
> + struct cgroup_subsys_state css;
> +
> + /* protects resource pool list */
> + spinlock_t rpool_list_lock;
Is this lock still being used?
> + /*
> + * head to keep track of all resourc
Hi Dmitry,
On 04/04/2016 01:56 AM, Dmitry Vyukov wrote:
> Hello,
>
> The following program causes a memory leak:
Thanks for the report. This is the same problem fixed in 4.5
There was a merge snafu; Greg has the patch in his queue that
fixes this for 4.6
Regards,
Peter Hurley
> unreferenced o
On Mon, Apr 04, 2016 at 06:00:42PM +0200, Peter Zijlstra wrote:
> On Mon, Apr 04, 2016 at 08:32:21AM -0700, Andy Lutomirski wrote:
>
> > Adding locking would be easy enough, wouldn't it?
>
> See patch in this thread..
>
> > But do any platforms really boot a second CPU before switching to real
>
On Sun, Apr 03, 2016 at 09:36:31PM +0100, Martyn Welch wrote:
>
>
> On 31/03/16 23:53, Clifton Barnes wrote:
> > fix checkpatch.pl warning about 'Prefer 'unsigned int' to bare use of
> > 'unsigned''
> >
> > Signed-off-by: Clifton Barnes
>
> Acked-by: Martyn Welch
>
> Greg: Whilst this patch
On Mon, 2016-04-04 at 15:23 +0200, Peter Zijlstra wrote:
> On Mon, Apr 04, 2016 at 11:38:44AM +0200, Ingo Molnar wrote:
> >
> > We'd upgrade that to O(nr_cpus^2), which is totally unrealistic
> > with 16,000 CPUs
> > even in a slowpath - but it would probably cause problems even with
> > 120 CPUs
- On Apr 4, 2016, at 1:11 PM, H. Peter Anvin h...@zytor.com wrote:
> On 04/04/16 10:01, Mathieu Desnoyers wrote:
>>
>> Changes since v5:
>> - Rename "getcpu_cache" to "thread_local_abi", allowing to extend
>> this system call to cover future features such as restartable critical
>> sectio
On Thu, Mar 31, 2016 at 2:05 AM, Matt Redfearn wrote:
>
> This series adds the ability for the MIPS kernel to relocate itself at
> runtime, optionally to an address determined at random each boot. This
> series is based on v4.4 and has been tested on the Malta, Boston and
> SEAD3 platforms.
>
> He
On Mon, Apr 4, 2016 at 12:29 PM, Peter Hurley wrote:
>
> Yeah, a straight revert of 520bd7a8b415 resumes normal service:
Ok, so we have that as an option.
> Should I send a proper revert?
Let's see if somebody can come up with a better serialization model.
We're only at rc2, and we now have a f
On Mon, Apr 04, 2016 at 07:47:36PM +0100, Al Viro wrote:
> On Mon, Apr 04, 2016 at 06:16:12PM +0100, Al Viro wrote:
>
> > will see NULL map_data; the ->from_user case is sg_start_req() stuff. IOW,
> > SG_IO behaviour for /dev/sg* is different from the generic one...
>
> While we are at it: in bi
[[PATCH] drivers/idle: make intel_idle.c driver more explicitly non-modular] On
27/03/2016 (Sun 13:29) Paul Gortmaker wrote:
> The Kconfig for this driver is currently declared with:
>
> config INTEL_IDLE
> bool "Cpuidle Driver for Intel Processors"
>
> ...meaning that it currently is n
On 04/04/2016 12:49 PM, Linus Torvalds wrote:
> On Mon, Apr 4, 2016 at 12:29 PM, Peter Hurley
> wrote:
>>
>> Yeah, a straight revert of 520bd7a8b415 resumes normal service:
>
> Ok, so we have that as an option.
>
>> Should I send a proper revert?
>
> Let's see if somebody can come up with a be
On Mon, Apr 4, 2016 at 9:37 PM, Peter Hurley wrote:
> Hi Dmitry,
>
> On 04/04/2016 01:56 AM, Dmitry Vyukov wrote:
>> Hello,
>>
>> The following program causes a memory leak:
>
> Thanks for the report. This is the same problem fixed in 4.5
> There was a merge snafu; Greg has the patch in his queue
From: Haishuang Yan
Date: Sun, 3 Apr 2016 22:09:23 +0800
> pskb_may_pull() can change skb->data, so we have to load ptr/optr at the
> right place.
>
> Signed-off-by: Haishuang Yan
Applied and queued up for -stable.
From: Haishuang Yan
Date: Sun, 3 Apr 2016 22:09:24 +0800
> pskb_may_pull() can change skb->data, so we have to load ptr/optr at the
> right place.
>
> Signed-off-by: Haishuang Yan
Applied and queued up for -stable.
On Sun, Apr 3, 2016 at 10:21 PM, Jaegeuk Kim wrote:
>
> Could you please pull the below commits for v4.6-rc3?
Pulled, but..
> git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git
> tags/f2fs-for-linus
.. the above is a tag, but it's not signed, nor even annotated. So it
has no mess
Some ethernet adapter vendors are supplying products which support optional
(payed license) features. On some adapters this includes a hardware iscsi
initiator. The same adapters in a normal (no extra licenses) mode of
operation can be used as a software iscsi initiator. In addition, software
is
From: Bastien Philbert
Date: Sun, 3 Apr 2016 19:04:26 -0400
> This fixes the incorrect variable assignment on error path in
> br_sysfs_addbr for when the call to kobject_create_and_add
> fails to assign the value of -EINVAL to the returned variable of
> err rather then incorrectly return zero ma
On Tue, Mar 22, 2016 at 7:38 PM, kbuild test robot wrote:
> Hi Ming,
>
> [auto build test WARNING on scsi/for-next]
> [also build test WARNING on v4.5 next-20160322]
> [if your patch is applied to the wrong git tree, please drop us a note to
> help improving the system]
>
> url:
> https://git
fix the raw_buffer pointer double free issue found by coverify.
Signed-off-by: Han Xu
---
drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
index 8122c69..dcb60b0 100644
---
From: Moritz Fischer
Date: Tue, 29 Mar 2016 19:11:10 -0700
> resending almost unchanged v2 here:
>
> Changes from v2:
> * Rebased onto net-next
> * Changed 5th patches commit message
> * Added Nicholas' and Michal's Acked-Bys
>
> Changes from v1:
> * Backed out variable scope changes
> * Separa
On 2016-04-04 04:14 PM, David Miller wrote:
> From: Bastien Philbert
> Date: Sun, 3 Apr 2016 19:04:26 -0400
>
>> This fixes the incorrect variable assignment on error path in
>> br_sysfs_addbr for when the call to kobject_create_and_add
>> fails to assign the value of -EINVAL to the returned v
On Mon, Apr 04, 2016 at 01:15:45PM -0700, Ming Lin wrote:
> cleanup_sdb:
> for (i = 0; i < SG_MEMPOOL_NR; i++) {
> struct sg_pool *sgp = sg_pools + i;
> if (sgp->pool)
> mempool_destroy(sgp->pool);
> if (sgp->slab)
>
Calling led_trigger_event may schedule a delayed LED set,
if the LED was being used by a delayed blink trigger when
the kernel paniced.
Therefore, we must use led_trigger_event_nosleep to override
this situation, and set the LED unconditionally.
Signed-off-by: Ezequiel Garcia
---
drivers/leds/t
It's desirable to specify which LEDs are to be blinked on a kernel
panic. Therefore, introduce a devicetree boolean property to mark
which LEDs should be treated this way.
Signed-off-by: Ezequiel Garcia
---
Documentation/devicetree/bindings/leds/common.txt | 2 ++
1 file changed, 2 insertions(+)
GPIO LEDs are relatively cheap, and so are ideal to blink on
a kernel panic. This commit adds support for the new "panic-blink"
firmware property, allowing to mark a given LED to blink on
a kernel panic.
Signed-off-by: Ezequiel Garcia
---
drivers/leds/leds-gpio.c | 4
include/linux/leds.h
As per commit 916fe61995 ("leds: trigger: Introduce a kernel panic LED
trigger"), the kernel now supports a new LED trigger to hook on
the panic blink.
However, the only way of using this is to dedicate a LED device
to this function.
To overcome this limitation, the present series introduces the
This commit adds a new led_cdev flag LED_BLINK_AT_PANIC, which
allows to mark a specific LED to be switched to the "panic"
trigger, on a kernel panic.
This is useful to allow the user to assign a regular trigger
to a given LED, and still blink that LED on a kernel panic.
Signed-off-by: Ezequiel G
Now that we can mark any LED (even those in use by delayed blink
triggers) to trigger on a kernel panic, let's introduce a nosleep
led_trigger_event API.
This API is needed to skip the delayed blink path on
led_trigger_event. LEDs that are switched on a kernel panic,
might be in use by a delayed b
From: Borislav Petkov
Use static_cpu_has() in the timing-sensitive paths in fpstate_init() and
fpu__copy().
While at it, simplify the use in init_cyrix() and get rid of the ternary
operator.
Signed-off-by: Borislav Petkov
---
arch/x86/include/asm/cpufeature.h | 1 -
arch/x86/kernel/cpu/cyrix.
From: Borislav Petkov
Signed-off-by: Borislav Petkov
Cc: linux-cry...@vger.kernel.org
---
arch/x86/crypto/aesni-intel_glue.c | 2 +-
arch/x86/crypto/camellia_aesni_avx2_glue.c | 3 ++-
arch/x86/crypto/camellia_aesni_avx_glue.c | 2 +-
arch/x86/crypto/chacha20_glue.c| 3 ++-
From: Borislav Petkov
Signed-off-by: Borislav Petkov
Cc: k...@vger.kernel.org
---
arch/x86/ia32/ia32_signal.c | 2 +-
arch/x86/include/asm/cpufeature.h | 1 -
arch/x86/kernel/fpu/regset.c | 8
arch/x86/kernel/fpu/xstate.c | 8
arch/x86/kernel/signal.c
From: Borislav Petkov
Signed-off-by: Borislav Petkov
Cc: Dmitry Torokhov
Cc: Thomas Sailer
---
arch/x86/include/asm/cpufeature.h | 1 -
arch/x86/include/asm/tsc.h| 2 +-
arch/x86/kernel/apic/apic.c | 10 +-
arch/x86/kernel/cpu/common.c | 2 +-
arch/x86/kernel/tsc
On Tue, Mar 22, 2016 at 3:03 PM, Ming Lin wrote:
> From: Ming Lin
>
> Rename SCSI_MAX_SG_SEGMENTS to SG_CHUNK_SIZE, which means the amount
> we fit into a single scatterlist chunk.
>
> Rename SCSI_MAX_SG_CHAIN_SEGMENTS to SG_MAX_SEGMENTS.
>
> Will move these 2 generic definitions to scatterlist.h
From: Martin Brandenburg
Almost everywhere we use strncpy we should use strlcpy. This affects
path names (d_name mostly), symlink targets, and server names.
Leave debugfs code as is for now, though it could use a review as well.
Signed-off-by: Martin Brandenburg
---
fs/orangefs/dcache.c
From: Borislav Petkov
Signed-off-by: Borislav Petkov
Cc: linux-cry...@vger.kernel.org
---
arch/x86/crypto/camellia_aesni_avx2_glue.c | 3 ++-
arch/x86/crypto/camellia_aesni_avx_glue.c | 4 +++-
arch/x86/include/asm/cpufeature.h | 1 -
3 files changed, 5 insertions(+), 3 deletions(-)
From: Borislav Petkov
Signed-off-by: Borislav Petkov
Cc:
---
arch/x86/include/asm/cpufeature.h | 6 --
arch/x86/kernel/fpu/xstate.c | 10 +-
arch/x86/kvm/vmx.c| 2 +-
arch/x86/kvm/x86.c| 4 ++--
4 files changed, 8 insertions(+), 14 deletions(
From: Borislav Petkov
Signed-off-by: Borislav Petkov
---
arch/x86/include/asm/cpufeature.h | 1 -
arch/x86/kernel/fpu/core.c| 6 +++---
arch/x86/kernel/fpu/init.c| 6 +++---
arch/x86/kernel/fpu/regset.c | 13 -
4 files changed, 14 insertions(+), 12 deletions(
From: Borislav Petkov
Signed-off-by: Borislav Petkov
Cc: oprofile-l...@lists.sf.net
Cc: io...@lists.linux-foundation.org
Cc: linux...@vger.kernel.org
---
arch/x86/events/core.c | 2 +-
arch/x86/include/asm/cpufeature.h| 1 -
arch/x86/include/asm/irq_work.h |
From: Martin Brandenburg
---
fs/orangefs/dir.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/fs/orangefs/dir.c b/fs/orangefs/dir.c
index ba7dec4..324f0af 100644
--- a/fs/orangefs/dir.c
+++ b/fs/orangefs/dir.c
@@ -153,7 +153,6 @@ static int orangefs_readdir(struct file *f
From: Martin Brandenburg
The ctime and mtime are always updated on a successful ftruncate and
only updated on a successful truncate where the size changed.
We handle the ``if the size changed'' bit.
This matches FUSE's behavior.
Signed-off-by: Martin Brandenburg
---
fs/orangefs/inode.c | 16
From: Borislav Petkov
Signed-off-by: Borislav Petkov
Cc: linux-cry...@vger.kernel.org
---
arch/x86/crypto/camellia_aesni_avx2_glue.c | 2 +-
arch/x86/crypto/chacha20_glue.c| 2 +-
arch/x86/crypto/poly1305_glue.c| 2 +-
arch/x86/crypto/serpent_avx2_glue.c| 2 +-
a
From: Borislav Petkov
Here are the final 10. cpu_has_YYY is gone now. Good riddance.
I have a bunch of misc cleanups on top, will send them tomorrow.
Thanks.
Borislav Petkov (10):
x86/cpufeature: Remove cpu_has_avx2
x86/cpufeature: Remove cpu_has_aes
x86/cpufeature: Remove cpu_has_avx
From: Borislav Petkov
Signed-off-by: Borislav Petkov
---
arch/x86/include/asm/cpufeature.h | 1 -
arch/x86/include/asm/xor_32.h | 2 +-
arch/x86/kernel/fpu/core.c| 2 +-
arch/x86/kernel/fpu/init.c| 2 +-
4 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/arch/x86
From: Kan Liang
The calculation of format value also rely on the continuity of the
format. However, uncore event format is not continuous.
E.g. The bit 21 as qpi event is lost.
perf stat -a -e uncore_qpi_0/event=0x200038,config1=0x1C00,
config2=0x3FE00/ -vvv
-
On Mon, Apr 4, 2016 at 1:17 PM, Christoph Hellwig wrote:
> On Mon, Apr 04, 2016 at 01:15:45PM -0700, Ming Lin wrote:
>> cleanup_sdb:
>> for (i = 0; i < SG_MEMPOOL_NR; i++) {
>> struct sg_pool *sgp = sg_pools + i;
>> if (sgp->pool)
>>
This fixes a locking issue in the function l2cap_connect_cfm for
not locking the mutex lock for channels on the l2cap_conn structure
pointer conn before calling __l2cap_get_chan_by_dcid as all callers
need to lock and unlock this mutex before calling this function due
to issues with either concurre
Roger
I am sorry but this mail chain is unreadable!! I am not able to filter out the
>>>...
Please send me a clean version of the mail if possible...i will be unable to
respond without that..
---Abhishek
-Original Message-
From: Felipe Balbi [mailto:ba...@kernel.org]
Sent: Monday, Apri
From: Andi Kleen
Add a way to show different sysfs events attributes depending on
HyperThreading is on or off. This is difficult to determine
early at boot, so we just do it dynamically when the sysfs
attribute is read.
v2:
Compute HT status only once in CPU online/offline hooks.
Signed-off-by:
From: Andi Kleen
When an event alias is used that the kernel marked as .aggr-per-core, force
--per-core mode (and also require -a and forbid cgroups or per thread mode).
This in term means, --topdown forces --per-core mode.
This is needed for TopDown in SMT mode, because it needs to measure
all
From: Andi Kleen
Now that we have a convenient ht_on flag in x86_pmu use it
to detect the HT workarounds for older CPUs.
Signed-off-by: Andi Kleen
---
arch/x86/events/intel/core.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/arch/x86/events/intel/core.c b/arch/x86/
From: Andi Kleen
When the scaling factor is a full integer don't display fractional
digits. This avoids unnecessary .00 output for topdown metrics
with scale factors.
v2: Remove redundant check.
Signed-off-by: Andi Kleen
---
tools/perf/builtin-stat.c | 7 ---
1 file changed, 4 insertions(+
From: Andi Kleen
Add debug output of raw counter values per CPU when
perf stat -v is specified, together with their cpu numbers.
This is very useful to debug problems with per core counters,
where we can normally only see aggregated values.
Signed-off-by: Andi Kleen
---
tools/perf/builtin-stat
From: Andi Kleen
Add basic plumbing for TopDown in perf stat
Add a new --topdown options to enable events.
When --topdown is specified set up events for all topdown
events supported by the kernel.
Add topdown-* as a special case to the event parser, as is
needed for all events containing -.
The
From: Andi Kleen
Implement the TopDown formulas in perf stat. The topdown basic metrics
reported by the kernel are collected, and the formulas are computed
and output as normal metrics.
See the kernel commit exporting the events for details on the used
metrics.
v2: Always print all metrics, onl
From: Andi Kleen
Add declarations for the events needed for TopDown to the
Intel big core CPUs starting with Sandy Bridge. We need
to report different values if HyperThreading is on or off.
The only thing this patch does is to export some events
in sysfs.
TopDown level 1 uses a set of abstracte
From: Andi Kleen
Add topdown event declarations to Silvermont / Airmont.
These cores do not support the full Top Down metrics, but an useful
subset (FrontendBound, Retiring, Backend Bound/Bad Speculation).
The perf stat tool automatically handles the missing events
and combines the available met
From: Andi Kleen
Scale values by unit before passing them to the metrics printing functions.
This is needed for TopDown, because it needs to scale the slots correctly
by pipeline width / SMTness.
For existing metrics it shouldn't make any difference, as those generally
use events that don't have
Note to reviewers: includes both tools and kernel patches.
The kernel patches are at the beginning.
[v2: Address review feedback.
Metrics are now always printed, but colored when crossing threshold.
--topdown implies --metric-only.
Various smaller fixes, see individual patches]
[v3: Add --single-t
From: Andi Kleen
Add the basic code to parse an .aggr-per-core event attribute.
The attribute means that the event needs to be measured in
per core mode.
v2: Support integer values for aggr-per-core
Signed-off-by: Andi Kleen
---
tools/perf/util/evsel.h| 1 +
tools/perf/util/parse-even
When a vCPU runs on a nohz_full core, the hrtimer used by
the lapic emulation code can be migrated to another core.
When this happens, it's possible to observe milisecond
latency when delivering timer IRQs to KVM guests.
The huge latency is mainly due to the fact that
apic_timer_fn() expects to ru
- On Apr 4, 2016, at 3:46 PM, Mathieu Desnoyers
mathieu.desnoy...@efficios.com wrote:
> - On Apr 4, 2016, at 1:11 PM, H. Peter Anvin h...@zytor.com wrote:
>
>> On 04/04/16 10:01, Mathieu Desnoyers wrote:
>>>
>>> Changes since v5:
>>> - Rename "getcpu_cache" to "thread_local_abi", allowi
fix the raw_buffer pointer double free issue found by coverify.
CID 18344 (#2 of 2): Double free (USE_AFTER_FREE)
3. double_free: Calling gpmi_alloc_dma_buffer frees pointer
this->raw_buffer which has already been freed
Signed-off-by: Han Xu
---
changes in v2:
- add coverity check log
---
dri
On Mon, 2016-04-04 at 16:46 -0400, Luiz Capitulino wrote:
> When a vCPU runs on a nohz_full core, the hrtimer used by
> the lapic emulation code can be migrated to another core.
> When this happens, it's possible to observe milisecond
> latency when delivering timer IRQs to KVM guests.
>
> The hug
This adds the regulator nodes to DK04 device tree to support
Change-Id: I9c1df0e720a330bf6db1889fd2247f6a70ea6faa
Signed-off-by: Sreedhar Sambangi
---
.../bindings/regulator/ipq4019-regulator.txt | 19 +++
arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1.dtsi | 11 ++
From: Kirthik Srinivasan
Add LDO regulator driver to enable SD /MMC card to
switch between 3.0 volts and 1.8 volts
Change-Id: I66f770878570b1f5b1db044ba626e0f6989acc3f
Signed-off-by: Kirthik Srinivasan
Signed-off-by: Rajith Cherian
Signed-off-by: Sreedhar Sambangi
---
drivers/regulator/Kcon
On 03/31/2016 06:40 AM, Aleksey Makarov wrote:
> From: Leif Lindholm
>
> We have multiple "earlycon" early_param handlers - merge the DT one into
> the main earlycon one. It's a cleanup that also will be useful
> to defer setting up DT console until ACPI/DT decision is made.
>
> Rename the expo
On 03/31/2016 06:40 AM, Aleksey Makarov wrote:
> This patch adds function pl011_console_match() that implements
> method match of struct console. It allows to match consoles against
> data specified in a string, for example taken from command line or
> compiled by ACPI SPCR table handler.
Reviewe
On Mon, Apr 04, 2016 at 01:07:11PM -0700, Linus Torvalds wrote:
> On Sun, Apr 3, 2016 at 10:21 PM, Jaegeuk Kim wrote:
> >
> > Could you please pull the below commits for v4.6-rc3?
>
> Pulled, but..
>
> > git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git
> > tags/f2fs-for-linus
>
This function was intended to be exported into the ufshcd
API but after all it is not used outside ufshcd.c
Make it static and drop EXPORT_SYMBOL; this can be restored
when needed.
Fixes
warning: no previous prototype for ‘ufshcd_query_descriptor_retry’
Introduced by
commit a70e91b8bbaa ("scsi: uf
601 - 700 of 889 matches
Mail list logo
