Il 03/06/2014 15:06, Michael Tokarev ha scritto:
03.06.2014 16:04, Paolo Bonzini wrote:
Il 01/06/2014 01:05, Rickard Strandqvist ha scritto:
There is a risk that the variable will be used without being initialized.
This was largely found by using a static code analysis program called
This is loader specific code which can load bzImage and set it up for
64bit entry. This does not take care of 32bit entry or real mode entry.
32bit mode entry can be implemented if somebody needs it.
Signed-off-by: Vivek Goyal vgo...@redhat.com
---
arch/x86/include/asm/kexec-bzimage.h | 11 ++
Previous patch provided the interface definition and this patch prvides
implementation of new syscall.
Previously segment list was prepared in user space. Now user space just
passes kernel fd, initrd fd and command line and kernel will create a
segment list internally.
This patch contains
This patch adds support for loading a kexec on panic (kdump) kernel usning
new system call. Right now this primarily works with bzImage loader only.
But changes to ELF loader should be minimal as all the core infrastrcture
is there.
Only thing preventing making ELF load in crash reseved memory is
Next two patches provide code for purgatory. This is a code which does
not link against the kernel and runs stand alone. This code runs between
two kernels. One of the primary purpose of this code is to verify the
digest of newly loaded kernel and making sure it matches the digest
computed at
On Tue, Jun 03, 2014 at 09:06:49AM -0400, Vivek Goyal wrote:
Hi,
This is V3 of the patchset. Previous versions were posted here.
V1: https://lkml.org/lkml/2013/11/20/540
V2: https://lkml.org/lkml/2014/1/27/331
Changes since v2:
- Took care of most of the review comments from V2.
-
Linus,
Please pull the latest x86-build-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-build-for-linus
# HEAD: a9358bc3531901a15e2f7cd48550c9555fc0288f x86/build: Supress
realmode.bin is up to date message
Two small build related cleanups.
Commit b32e86b430 dropped p-on_rq check, leading to printing tasks which
used to live on runqueues, which is very noisy and highly annoying.
Signed-off-by: Mike Galbraith bitbuc...@online.de
---
kernel/sched/debug.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
---
03.06.2014 16:04, Paolo Bonzini wrote:
Il 01/06/2014 01:05, Rickard Strandqvist ha scritto:
There is a risk that the variable will be used without being initialized.
This was largely found by using a static code analysis program called
cppcheck.
Signed-off-by: Rickard Strandqvist
Linus,
Please pull the latest x86-cleanups-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-cleanups-for-linus
# HEAD: 79a51b25badae79d2da6f7b54530adf56697f669 x86/irq: Clean up
VECTOR_UNDEFINED and VECTOR_RETRIGGERED definition
A single, trivial
On Wed, May 28, 2014 at 07:50:51PM +0100, Mark Brown wrote:
On Wed, May 28, 2014 at 07:11:07PM +0200, Maxime Ripard wrote:
axp_vcore_reg: dcdc2 {
+ vin-supply = axp_ipsout_reg;
axp_ddr_reg: dcdc3 {
+ vin-supply =
On Thu 29-05-14 12:15:56, Johannes Weiner wrote:
Currently, __GFP_NORETRY tries charging once and gives up before even
trying to reclaim. Bring the behavior on par with the page allocator
and reclaim at least once before giving up.
Signed-off-by: Johannes Weiner han...@cmpxchg.org
On Tue, Jun 03, 2014 at 10:47:18AM +0200, Richard Weinberger wrote:
Am 03.06.2014 10:32, schrieb Peter Zijlstra:
On Tue, Jun 03, 2014 at 10:15:44AM +0200, Richard Weinberger wrote:
Once upon a time GCC also did warns like that, but my compiler is silent
:-(
-Wtype-limits is what
This patch adds KEYBOARD_ST_KEYSCAN config
Signed-off-by: Gabriel Fernandez gabriel.fernan...@linaro.org
Acked-by: Lee Jones lee.jo...@linaro.org
---
arch/arm/configs/multi_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/multi_v7_defconfig
On Thu 29-05-14 12:15:55, Johannes Weiner wrote:
There is no reason why oom-disabled and __GFP_NOFAIL charges should
try to reclaim only once when every other charge tries several times
before giving up. Make them all retry the same number of times.
I have mentioned that already with the last
On Tue, Jun 03, 2014 at 11:33:54AM +0100, David Howells wrote:
Miklos Szeredi mik...@szeredi.hu wrote:
Fix now pushed to overlayfs.v22/overlayfs.current.
I ran my testscript, which leaves a clean set up and mounted overlay fs
behind. I then ran:
for ((i=100; i=129; i++)); do mv
On Fri, May 23, 2014 at 04:52:58PM +0100, Vincent Guittot wrote:
power_orig is only changed for system with a SMT sched_domain level in order
to
reflect the lower capacity of CPUs. Heterogenous system also have to reflect
an
original capacity that is different from the default value.
On Thu 29-05-14 12:15:57, Johannes Weiner wrote:
When mem_cgroup_try_charge() returns -EINTR, it bypassed the charge to
the root memcg. But move precharging does not catch this and treats
this case as if no charge had happened, thus leaking a charge against
root. Because of an old
- Original Message -
From: Dave Chinner da...@fromorbit.com
To: Steven Rostedt rost...@goodmis.org
Cc: j...@joshtriplett.org, Joe Perches j...@perches.com,
paul...@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
mi...@kernel.org, la...@cn.fujitsu.com, dipan...@in.ibm.com,
On Tue, Jun 03, 2014 at 07:14:31AM -0400, Mikulas Patocka wrote:
So if we really want to keep supporting these platforms; I would propose
something like:
#ifdef __CHECKER__
#define __atomic__attribute__((address_space(5)))
#else
#define __atomic
#endif
#define store(p, v)
Possibly stupid question: Is it true that any given task can only be
using one wait_queue_t at a time? If so, would it be an idea to put a
wait_queue_t into struct task_struct [maybe union'ed with a struct
wait_bit_queue] and avoid allocating this 40 byte structure repeatedly
on the stack.
E.g.,
On 06/03/2014 08:48 AM, Paolo Bonzini wrote:
Il 02/06/2014 23:58, Eric Dumazet ha scritto:
This looks dubious
What about using kfree_rcu() instead ?
It would lead to unbound allocation from userspace.
translate_desc() still uses rcu_read_lock(), its not clear if the mutex
is really
On 6/2/14, 3:18 PM, Jiri Olsa wrote:
We keep dsos data file descriptors open until their count reaches
the half of the current fd open limit (RLIMIT_NOFILE). In this case
we close file descriptor of the first opened dso object.
We've got overall speedup (24% for my workload) of report:
'perf
Linus,
Please pull the latest x86-microcode-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-microcode-for-linus
# HEAD: 65cef1311d5d212fd3d48a43678536dc878ca288 x86, microcode: Add a
disable chicken bit
A microcode-debugging boot flag plus related
On 6/2/14, 3:18 PM, Jiri Olsa wrote:
+static rlim_t get_fd_limit(void)
+{
+ struct rlimit l;
+ rlim_t limit = 0;
+
+ /* Allow half of the current open fd limit. */
+ if (getrlimit(RLIMIT_NOFILE, l) == 0) {
+ if (l.rlim_cur == RLIM_INFINITY)
+
On Tue, Jun 03, 2014 at 07:36:25AM -0600, David Ahern wrote:
On 6/2/14, 3:18 PM, Jiri Olsa wrote:
We keep dsos data file descriptors open until their count reaches
the half of the current fd open limit (RLIMIT_NOFILE). In this case
we close file descriptor of the first opened dso object.
Linus,
Please pull the latest x86-mm-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-mm-for-linus
# HEAD: c81c8a1eeede61e92a15103748c23d100880cc8a x86, ioremap: Speed up
check for RAM pages
- speed up 256 GB PCI BAR ioremap()s
- speed up PTE
On 6/2/14, 3:18 PM, Jiri Olsa wrote:
Adding descriptions/explanations for dso__data_* interface
functions.
Shouldn't the descriptions be added when the functions are?
David
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
On Tue, Jun 03, 2014 at 07:39:09AM -0600, David Ahern wrote:
On 6/2/14, 3:18 PM, Jiri Olsa wrote:
+static rlim_t get_fd_limit(void)
+{
+struct rlimit l;
+rlim_t limit = 0;
+
+/* Allow half of the current open fd limit. */
+if (getrlimit(RLIMIT_NOFILE, l) == 0) {
+
On 06/03/2014 05:08 AM, Mark Rutland wrote:
Hi Alex,
On Fri, May 30, 2014 at 11:11:54PM +0100, Alex Elder wrote:
The bindings for CPU enable methods are defined in .../arm/cpus.txt. As
additional 32-bit ARM CPUS are converted to use the enable-method CPU
property to imply a particular set
On 6/2/14, 3:18 PM, Jiri Olsa wrote:
In upcoming tests we will setup process limits, which
might affect other tests. Spawning child for each test
to prevent this.
Reviewed-by: David Ahern dsah...@gmail.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of
Linus,
Please pull the latest x86-platform-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-platform-for-linus
# HEAD: 04725ad59474d24553d526fa774179ecd2922342 x86, iosf: Add PCI ID
macros for better readability
IOSF (Intel OnChip System Fabric)
On Tue, 2014-06-03 at 14:54 +0300, Igor Royzis wrote:
Eric, could you please provide a feedback on the suggestion to move
the pointer from skb_shared_info to skbuff? If we must fit
skb_shared_info till the 'frags' field into 1 cache line (I honestly
don't quite understand why (the whole
On 6/2/14, 3:18 PM, Jiri Olsa wrote:
Making the test_file function to be reusable for
new tests coming in following patches.
Cc: Arnaldo Carvalho de Melo a...@kernel.org
Cc: Corey Ashford cjash...@linux.vnet.ibm.com
Cc: David Ahern dsah...@gmail.com
Cc: Frederic Weisbecker fweis...@gmail.com
Linus,
Please pull the latest x86-ras-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-ras-for-linus
# HEAD: 716079f66eacd31d040db9cd0627ca0d625d6126 mce: Panic when a core has
reached a timeout
Improve mcheck device initialization and bootstrap
On Tue, 2014-02-25 at 11:06 -0500, Josh Boyer wrote:
On Tue, Feb 25, 2014 at 10:47 AM, Adam Jackson a...@redhat.com wrote:
From: Peter Jones pjo...@redhat.com
Some systems, such as EFI-based Apple systems, won't necessarily have an
i8042 to initialize. We shouldn't be printing an error
Il 03/06/2014 15:35, Vlad Yasevich ha scritto:
Yes, vhost_get_vq_desc must be called with the vq mutex held.
The rcu_read_lock/unlock in translate_desc is unnecessary.
If that's true, then does dev-memory really needs to be rcu protected?
It appears to always be read under mutex.
It's
On 6/2/14, 3:18 PM, Jiri Olsa wrote:
+static int dsos__create(int cnt, int size)
+{
+ int i;
+
+ dsos = malloc(sizeof(dsos) * cnt);
+ TEST_ASSERT_VAL(failed to alloc dsos array, dsos);
+
+ for (i = 0; i cnt; i++) {
+ char *file;
+
+ file =
On 06/03/2014 01:06 AM, Keith Busch wrote:
Depending on the timing, it might fail in alloc instead of free:
Jun 2 16:45:40 kbgrz1 kernel: [ 265.421243] NULL pointer dereference
at (null)
Jun 2 16:45:40 kbgrz1 kernel: [ 265.434284] PGD 429acf067 PUD
42ce28067 PMD 0
Jun 2 16:45:40
On Tue, Jun 03, 2014 at 03:09:38PM +0200, Maxime Ripard wrote:
On Wed, May 28, 2014 at 07:47:52PM +0100, Mark Brown wrote:
On Wed, May 28, 2014 at 07:11:04PM +0200, Maxime Ripard wrote:
This patchset modifies the regulator core and axp209 regulator driver
to be able to set in each
On 6/2/14, 3:18 PM, Jiri Olsa wrote:
Testing that perf properly closes opened dso objects
and tries to reopen in case we run out of allowed file
descriptors for dso data.
Reviewed by: David Ahern dsah...@gmail.com
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the
Linus,
Please pull the latest x86-uv-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-uv-for-linus
# HEAD: fe455b17de6c881eecf4f9784c3b0483a5e3d19e x86/UV: Fix conditional in
gru_exit()
Continued updates for SGI UV 3 hardware support.
SG pages lists (not to be confused with scatterlists) are a list of 4KB
memory pages used to define a nouveau_mem. Mapping them to a VM that
does not use 4KB apertures resulted in each subsequent 4KB physical page
being mapped into a larger VM aperture, thus creating an incorrect,
overlapping
On Tue, Jun 3, 2014 at 9:53 AM, Adam Jackson a...@redhat.com wrote:
On Tue, 2014-02-25 at 11:06 -0500, Josh Boyer wrote:
On Tue, Feb 25, 2014 at 10:47 AM, Adam Jackson a...@redhat.com wrote:
From: Peter Jones pjo...@redhat.com
Some systems, such as EFI-based Apple systems, won't
On Tue, Jun 03, 2014 at 12:43:47PM +0200, Peter Zijlstra wrote:
We need rq-curr, rq-idle 'sleeps' with polling set and nr clear, but
it obviously has no effect setting that if its not actually the current
task.
Touching rq-curr needs holding rcu_read_lock() though, to make sure the
task
On Tue, 2014-06-03 at 14:48 +0200, Paolo Bonzini wrote:
Il 02/06/2014 23:58, Eric Dumazet ha scritto:
This looks dubious
What about using kfree_rcu() instead ?
It would lead to unbound allocation from userspace.
Look at how we did this in commit
c3059477fce2d956a0bb3e04357324780c5d8eeb
On 3 June 2014 15:22, Morten Rasmussen morten.rasmus...@arm.com wrote:
On Fri, May 23, 2014 at 04:52:58PM +0100, Vincent Guittot wrote:
power_orig is only changed for system with a SMT sched_domain level in order
to
reflect the lower capacity of CPUs. Heterogenous system also have to reflect
Hi,
Qualcomm MSM 8974 is not able to detect [kernel.kallsyms] dso either with
Hardware or Tracepoint events while Exynos do.
Corresponding logs are as:
-Qualcomm MSM 8974--
./perf record -e cycles cal
# Overhead Command Shared Object
On Tue 03-06-14 17:52:09, Dave Chinner wrote:
On Tue, Jun 03, 2014 at 12:01:11AM -0700, Daniel Phillips wrote:
However, we already avoid the VFS writeback lists for certain
filesystems for pure metadata. e.g. XFS does not use the VFS dirty
inode lists for inode metadata changes. They
On Thu 29-05-14 12:15:58, Johannes Weiner wrote:
Due to an old optimization to keep expensive res_counter changes at a
minimum, the root_mem_cgroup res_counter is never charged; there is no
limit at that level anyway, and any statistics can be generated on
demand by summing up the counters of
Hello Greg,
thanks for your reply.
On Tue, Jun 03, 2014 at 10:14:55PM +1000, Greg Ungerer wrote:
I think it would be OK to define TASK_SIZE to 0x for !MMU.
blackfin, frv and m68k also do this. c6x does define it to 0xF000 to
leave space for error codes.
I did that same change
On 6/3/14, 8:02 AM, Prankul Garg wrote:
Qualcomm MSM 8974 is not able to detect [kernel.kallsyms] dso either with
Hardware or Tracepoint events while Exynos do.
Add -v to perf-record and perf-report.
And try:
perf report -D | grep kallsyms
Do you see something like:
0 0 0xd8 [0x58]:
On Tue, Jun 03, 2014 at 04:05:31PM +0200, Jan Kara wrote:
So we currently flush inodes in first dirtied first written back order when
superblock is not specified in writeback work. That completely ignores the
fact to which superblock inode belongs but I don't see per-sb fairness to
actually
On Tue, Jun 03, 2014 at 07:24:38PM +0800, Lai Jiangshan wrote:
Hi, Jason
Could you test again after the following command has done.
(if Peter hasn't asked you test with this command before nor he doesn't stop
you now)
echo NO_TTWU_QUEUE /sys/kernel/debug/sched_features
Thanks a lot.
On Tue, 3 Jun 2014, Peter Zijlstra wrote:
On Tue, Jun 03, 2014 at 07:14:31AM -0400, Mikulas Patocka wrote:
So if we really want to keep supporting these platforms; I would propose
something like:
#ifdef __CHECKER__
#define __atomic __attribute__((address_space(5)))
#else
Il 03/06/2014 15:57, Eric Dumazet ha scritto:
On Tue, 2014-06-03 at 14:48 +0200, Paolo Bonzini wrote:
Il 02/06/2014 23:58, Eric Dumazet ha scritto:
This looks dubious
What about using kfree_rcu() instead ?
It would lead to unbound allocation from userspace.
Look at how we did this in
On Tue, Jun 03, 2014 at 01:07:43PM +0200, Michal Hocko wrote:
On Wed 28-05-14 12:33:35, Johannes Weiner wrote:
On Wed, May 28, 2014 at 05:54:14PM +0200, Michal Hocko wrote:
On Wed 28-05-14 11:28:54, Johannes Weiner wrote:
On Wed, May 28, 2014 at 04:21:44PM +0200, Michal Hocko wrote:
Add the compatible string for the APQ8084 global clock controller
to the clock binding documentation.
Signed-off-by: Georgi Djakov gdja...@mm-sol.com
Reviewed-by: Stephen Boyd sb...@codeaurora.org
---
.../devicetree/bindings/clock/qcom,gcc.txt |1 +
1 file changed, 1 insertion(+)
On Tue, Jun 3, 2014 at 6:55 AM, Peter Zijlstra pet...@infradead.org wrote:
Ah, I think I see what Trond means; so raw_write_seqcount_{begin,end}()
are without lockdep, _however_ raw_seqcount_begin() is with lockdep.
This is inconsistent within the same API (seqcount/seqlock).
Yes, we should
This patchset adds support for the global clock controller found on the
APQ8084 based platforms.
Applies to clk-next.
Changes from v2:
- Removed resets not belonging to gcc. (suggested by Stephen Boyd)
- Split the DT patches into separate patchset. (suggested by Kumar Gala)
Changes from v1:
On Tue, Jun 03, 2014 at 07:14:44AM -0700, Christoph Hellwig wrote:
Honestly I think doing per-bdi writeback has been a major mistake. As
you said it only even matters when we have filesystems on multiple
partitions on a single device, and even then only in a simple setup,
as soon as we use
On Tue, Jun 03, 2014 at 08:45:39PM +0800, Lai Jiangshan wrote:
Hi, Peter,
I rewrote the analyse. (scheduler_ipi() must be called before stopper-task,
so the part for workqueue of the old analyse maybe be wrong.)
But I don't think there is any guarantee we'll do the wakeup before
running
This patch adds the necessary node to probe the global clock
controller on APQ8084 platforms.
Signed-off-by: Georgi Djakov gdja...@mm-sol.com
Reviewed-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/boot/dts/qcom-apq8084.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git
Add the necessary DT node to probe the serial driver on
APQ8084 platforms.
Signed-off-by: Georgi Djakov gdja...@mm-sol.com
Reviewed-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/boot/dts/qcom-apq8084-mtp.dts |6 ++
arch/arm/boot/dts/qcom-apq8084.dtsi|8
2 files
This patchset adds DT nodes for the APQ8084 global clock controller
and serial port.
Should go through qcom/arm-soc tree.
Changes from v2:
- Split the DT patches into separate patchset. (suggested by Kumar Gala)
Changes from v1:
- Moved APQ8084 clocks into a separate file and under separate
On Tue, 3 Jun 2014, Arnd Bergmann wrote:
I think John Stultz and Thomas Gleixner have already started looking
at how the timekeeping code can be updated. Once that is done, we should
be able to add a functional 64-bit gettimeofday/settimeofday syscall
pair. While I definitely agree this is
On Monday 02 June 2014 14:57:26 H. Peter Anvin wrote:
On 06/02/2014 12:55 PM, Arnd Bergmann wrote:
The bit that is really going to hurt is every single ioctl that uses a
timespec.
Honestly, though, I really don't understand the point with struct
inode_time. It seems like the
On Tue, Jun 03, 2014 at 03:14:21PM +0200, Mike Galbraith wrote:
Commit b32e86b430 dropped p-on_rq check, leading to printing tasks which
used to live on runqueues, which is very noisy and highly annoying.
Yes,.. but also useful for the numa cruft :-(
When printing all we can get placement
A full dynticks CPU is allowed to stop its tick when a single task runs.
Meanwhile when a new task gets enqueued, the CPU must be notified so that
it can restart its tick to maintain local fairness and other accounting
details.
This notification is performed by way of an IPI. Then when the target
On 28 May 2014 23:08, Mark Brown broo...@kernel.org wrote:
Whatever - I don't think the particular code makes any practical
difference. We would need to audit existing users who don't have a
REGULATOR dependency for breakage though.
Exactly what kind of drivers are we looking to fix here?
An irq work can be handled from two places: from the tick if the work
carries the lazy flag and the tick is periodic, or from a self IPI.
We merge all these works in a single list and we use some per cpu latch
to avoid raising a self-IPI when one is already pending.
Now we could do away with
irq work currently only supports local callbacks. However its code
is mostly ready to run remote callbacks and we have some potential user.
The full nohz subsystem currently open codes its own remote irq work
on top of the scheduler ipi when it wants a CPU to reevaluate its next
tick. However
Just a small cleanup.
Cc: Andrew Morton a...@linux-foundation.org
Cc: Ingo Molnar mi...@kernel.org
Cc: Kevin Hilman khil...@linaro.org
Cc: Paul E. McKenney paul...@linux.vnet.ibm.com
Cc: Peter Zijlstra pet...@infradead.org
Cc: Thomas Gleixner t...@linutronix.de
Cc: Viresh Kumar
On Tue, 3 Jun 2014 04:36:07 -0400
Chen, Gong gong.c...@linux.intel.com wrote:
On Mon, Jun 02, 2014 at 12:57:48PM -0400, Steven Rostedt wrote:
Also matters how big you expect these events to be. If you get a
christmas tree set of flags, how big will that event grow with all
the descriptions
On Tue, Jun 03, 2014 at 02:48:18PM +0100, Alex Elder wrote:
On 06/03/2014 05:08 AM, Mark Rutland wrote:
Hi Alex,
On Fri, May 30, 2014 at 11:11:54PM +0100, Alex Elder wrote:
The bindings for CPU enable methods are defined in .../arm/cpus.txt. As
additional 32-bit ARM CPUS are converted
On Tue, Jun 03, 2014 at 04:40:15PM +0200, Frederic Weisbecker wrote:
Hi,
This version fixes the following concerns from Peterz:
* Warn _before_ work claim on irq_work_queue_on()
* Warn on in_nmi() while remote queueing
* Only disabled preemption (and not irqs) on local queueing
Thanks.
On Tue, Jun 03, 2014 at 03:12:04PM +0200, Maxime Ripard wrote:
On Wed, May 28, 2014 at 07:50:51PM +0100, Mark Brown wrote:
On Wed, May 28, 2014 at 07:11:07PM +0200, Maxime Ripard wrote:
axp_mic_reg: ldo5 {
+ vin-supply = axp_ipsout_reg;
This is saying that
Hi,
For testing our product we use many virtual machines (KVM, qemu),
created and destroyed automatically. Every couple of days, a host system
(different HP blades) reports a kernel bug:
kernel BUG at
/home/abuild/rpmbuild/BUILD/kernel-default-3.14.2/linux-3.14/mm/memory.c:3797!
After
On Tue 03-06-14 07:01:20, Greg Thelen wrote:
On Jun 3, 2014 4:10 AM, Michal Hocko mho...@suse.cz wrote:
On Wed 28-05-14 09:17:13, Greg Thelen wrote:
[...]
My 2c... The following works for my use cases:
1) introduce memory.low_limit_in_bytes (default=0 thus no default change
Hi,
This version fixes the following concerns from Peterz:
* Warn _before_ work claim on irq_work_queue_on()
* Warn on in_nmi() while remote queueing
* Only disabled preemption (and not irqs) on local queueing
Thanks.
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
Now that the irq work subsystem can queue remote callbacks, it's
a perfect fit to safely queue IPIs when interrupts are disabled
without worrying about concurrent callers.
Lets use it for the full dynticks kick to notify a CPU that it's
exiting single task mode.
This unbloats a bit the scheduler
On Tue, 3 Jun 2014 wei.y...@windriver.com wrote:
From: Yang Wei wei.y...@windriver.com
While loading g_mass_storage module, the following warning is triggered.
In fact, it is more easy to reproduce it with RT kernel.
WARNING: at drivers/usb/gadget/composite.c:
On Tuesday 03 June 2014 14:33:10 Joseph S. Myers wrote:
On Tue, 3 Jun 2014, Arnd Bergmann wrote:
I think John Stultz and Thomas Gleixner have already started looking
at how the timekeeping code can be updated. Once that is done, we should
be able to add a functional 64-bit
On Tue, Jun 03, 2014 at 01:13:05PM +0200, Linus Walleij wrote:
+Clock events
+
+
+Clock events are conceptually orthogonal to clock sources. The same hardware
+and register range may be used for the clock event, but it is essentially
+a different thing.
+
+You will notice that
On Tue, Jun 03, 2014 at 08:10:00PM +0530, Viresh Kumar wrote:
On 28 May 2014 23:08, Mark Brown broo...@kernel.org wrote:
Whatever - I don't think the particular code makes any practical
difference. We would need to audit existing users who don't have a
REGULATOR dependency for breakage
On Tue, Jun 03, 2014 at 04:40:16PM +0200, Frederic Weisbecker wrote:
@@ -90,10 +89,10 @@ EXPORT_SYMBOL_GPL(irq_work_queue);
bool irq_work_needs_cpu(void)
{
- struct llist_head *this_list;
+ struct llist_head *list;
- this_list = __get_cpu_var(irq_work_list);
- if
On Tue, 3 Jun 2014, Vladimir Davydov wrote:
Still, I really want to evict all empty slabs from cache on memcg
offline for sure. Handling failures there means introducing a worker
that will retry shrinking, but that seems to me as an unnecessary
complication, because there's nothing that can
On Tue, Jun 03, 2014 at 04:54:42PM +0200, Peter Zijlstra wrote:
On Tue, Jun 03, 2014 at 04:40:16PM +0200, Frederic Weisbecker wrote:
@@ -90,10 +89,10 @@ EXPORT_SYMBOL_GPL(irq_work_queue);
bool irq_work_needs_cpu(void)
{
- struct llist_head *this_list;
+ struct llist_head
On Thu, May 08, 2014 at 10:12:40AM -0700, John Stultz wrote:
On 04/29/2014 02:21 PM, John Stultz wrote:
Another few weeks and another volatile ranges patchset...
After getting the sense that the a major objection to the earlier
patches was the introduction of a new syscall (and its
On Tue, Jun 03, 2014 at 07:30:32AM +0200, Christian Stroetmann wrote:
In general, I do not believe that the complexity problems of soft updates,
atomic writes, and related techniques can be solved by hand/manually. So my
suggestion is to automatically handle the complexity problem of e.g.
On Tue, Jun 03, 2014 at 09:36:13AM +0200, Peter Zijlstra wrote:
On Mon, Jun 02, 2014 at 05:12:16PM -0400, Mikulas Patocka wrote:
The patch adds atomic_pointer_t for all architectures - it is in the
common code and it is backed by atomic_long_t (that already exists for all
architectures).
On Tue, Jun 03, 2014 at 04:40:18PM +0200, Frederic Weisbecker wrote:
irq work currently only supports local callbacks. However its code
is mostly ready to run remote callbacks and we have some potential user.
The full nohz subsystem currently open codes its own remote irq work
on top of the
On Tue, Jun 03, 2014 at 04:40:19PM +0200, Frederic Weisbecker wrote:
Now that the irq work subsystem can queue remote callbacks, it's
a perfect fit to safely queue IPIs when interrupts are disabled
without worrying about concurrent callers.
Lets use it for the full dynticks kick to notify a
On Mon, 2014-06-02 at 07:55 -0400, Josh Boyer wrote:
On Mon, Jun 02, 2014 at 02:40:28PM +0300, Dmitry Kasatkin wrote:
On 2 June 2014 14:33, Mimi Zohar zo...@linux.vnet.ibm.com wrote:
On Mon, 2014-06-02 at 13:48 +0300, Dmitry Kasatkin wrote:
On 1 June 2014 05:14, Mimi Zohar
On Tue, Jun 03, 2014 at 04:40:20PM +0200, Frederic Weisbecker wrote:
A full dynticks CPU is allowed to stop its tick when a single task runs.
Meanwhile when a new task gets enqueued, the CPU must be notified so that
it can restart its tick to maintain local fairness and other accounting
Hi Jassi,
On 03/06/14 11:21, Jassi Brar wrote:
On 3 June 2014 15:05, Sudeep Holla sudeep.ho...@arm.com wrote:
Hi Jassi,
On Mon, Jun 2, 2014 at 6:11 PM, Jassi Brar jassisinghb...@gmail.com wrote:
On Mon, Jun 2, 2014 at 8:44 PM, Matt Porter mpor...@linaro.org wrote:
On Fri, May 30, 2014 at
On Tue, Jun 03, 2014 at 05:00:08PM +0200, Peter Zijlstra wrote:
On Tue, Jun 03, 2014 at 04:40:18PM +0200, Frederic Weisbecker wrote:
irq work currently only supports local callbacks. However its code
is mostly ready to run remote callbacks and we have some potential user.
The full nohz
On Tue, Jun 03, 2014 at 07:07:27AM -0700, Paul E. McKenney wrote:
On Tue, Jun 03, 2014 at 09:36:13AM +0200, Peter Zijlstra wrote:
#ifdef __CHECKER__
#define __atomic__attribute__((address_space(5)))
#else
#define __atomic
#endif
#define store(p, v) (*(p) = (typeof(*(p))
From: Daniel Walter dwal...@google.com
Subject: [PATCH v2 00/11] replace obsolete strict_strto* calls
Changes since v1:
Removed [arch/tile] (was merged to tile tree)
Added Acked-by
Replace all calls to strict_strto* functions with appropriate
calls to kstrto*.
Remove definition of
On 05/15/2014 02:11 PM, Peter Zijlstra wrote:
On Mon, May 12, 2014 at 11:42:33AM -0400, Sasha Levin wrote:
Hi all,
While fuzzing with trinity inside a KVM tools guest running the latest -next
kernel I've stumbled on the following spew. Maybe related to the very recent
change in freeing on
401 - 500 of 1912 matches
Mail list logo
