On Tue, 27 May 2014, Vince Weaver wrote:
> On Tue, 27 May 2014, Vince Weaver wrote:
>
> > OK, the problem is in:
> >
> > kernel/events/core.c find_get_context()
> >
> > retry:
> > perf_lock_task_context() returns NULL.
> > alloc_perf_context()
> > task->perf_event_ctxp[ctxn] is
On Tue, 27 May 2014, Libo Chen wrote:
> On 2014/5/27 17:55, Mike Galbraith wrote:
> > On Tue, 2014-05-27 at 15:56 +0800, Libo Chen wrote:
> >> > On 2014/5/26 22:19, Mike Galbraith wrote:
> >>> > > On Mon, 2014-05-26 at 20:16 +0800, Libo Chen wrote:
> > >> On 2014/5/26 13:11, Mike Galbraith
This one as well would have been easier to review if you folded patches
7-10 together.
regards,
dan carpenter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Tue, 27 May 2014, Eric Dumazet wrote:
> From: Eric Dumazet
>
> zswap_dstmem is a percpu block of memory, which should
> be allocated using kmalloc_node(), to get better NUMA
> locality.
>
> Without it, all the blocks are allocated from a single node.
>
> Signed-off-by: Eric Dumazet
Signed-off-by: Bjorn Andersson
---
Thought I already sent you parts of this previously, sorry about that.
This should apply on your devel branch.
drivers/pinctrl/pinctrl-apq8064.c | 47 +++
1 file changed, 47 insertions(+)
diff --git
On Tue, May 27, 2014 at 01:35:44PM -0700, Tony Lindgren wrote:
> Based on chatting with Paul it seems that we most likely don't have
> bits for sysc_flags for SYSC_HAS_EMUFREE or SYSS_HAS_RESET_STATUS
> either. So applying the updated patch below, and the SSI dts changes
> into
On Mon, Apr 14, 2014 at 12:48:02PM +0200, Jean Delvare wrote:
> This patch set is a proposal to revert most of commit b4028437. This
> would solve a memory leak and also allow to simplify and ultimately
> inline again functions dev_get_drvdata and dev_set_drvdata for smaller
> footprint and
These would have been easier to review if this patch were folded in with
the previous two patches. What I look for in these patches is, "Will
the compile break if you get it wrong?"
For "[PATCH 04/15] staging: rtl8188eu:Assign RTL8188E to
padapter->chip_type directly", you could get it wrong and
On Tue, May 27, 2014 at 01:09:45PM -0700, Chaitanya Hazarey wrote:
> Fixed the following:
>
> ERROR: do not use C99 // comments
> ERROR: space required after that ',' (ctx:VxV)
> ERROR: space required after that ';' (ctx:VxV)
> ERROR: space required before the open brace '{'
> ERROR: spaces
On 27.05.2014 22:17, Tarek Dakhran wrote:
> Hi,
>
> On Tue, May 27, 2014 at 9:44 PM, Kevin Hilman wrote:
>> Kevin Hilman writes:
>>
>>> Tarek Dakhran writes:
>>>
The series of patches represent support of Exynos 5410 SoC
The Exynos 5410 is the first Samsung SoC based on
* Sebastian Reichel [140521 17:06]:
> On Wed, May 21, 2014 at 03:08:07PM -0700, Tony Lindgren wrote:
> > * Sebastian Reichel [140521 14:51]:
> > >
> > > Feel free to add Tested-by/Acked-By to the hwmod patch.
> >
> > OK thanks for testing.
>
> You are welcome.
>
> > I'll apply your dts
On Tue, May 27, 2014 at 09:23:30PM +0100, Benjamin Herrenschmidt wrote:
> On Tue, 2014-05-27 at 20:34 +0100, Will Deacon wrote:
>
> > Do you mean the io{read,write} functions? Funnily enough, they're already
> > relaxed on ARM if you go by the semantics I've proposed. That implies we at
> > least
On Tue, May 27, 2014 at 09:21:38PM +0100, Benjamin Herrenschmidt wrote:
> On Tue, 2014-05-27 at 20:32 +0100, Will Deacon wrote:
>
> > Why would you need two barriers? I would have though an mmiowb() inlined
> > into writel after the store operation would be sufficient. Or is this to
> > ensure a
Am 27.05.2014 22:02, schrieb Grant Likely:
> On Mon, 19 May 2014 14:35:49 +0200, Alexander Holler
> wrote:
>> What's still questionable about the patches for dtc is if dependencies
>> to devices and not just drivers should be included in the new property
>> dependencies too. My current
On Tue, 2014-05-27 at 20:34 +0100, Will Deacon wrote:
> Do you mean the io{read,write} functions? Funnily enough, they're already
> relaxed on ARM if you go by the semantics I've proposed. That implies we at
> least need some Documentation to that effect...
>
> What do you do on ppc?
They are
On Tue, 27 May 2014 20:44:33 +0200, Fabian Frederick said:
> Hello Valdis,
>
> I thought Tejun directly reverted that patch (Joe Perches noticed
> the level problem just after submit).Anyway, problem is solved now :)
Tejun - can you see if that patch in fact got reverted? It made it
into
Hey DaeSeok,
I fixed all of them except -
this "if" condition like below:
if (5 == wrqu->encoding.length || 13 == wrqu->encoding.length)
mask = 0x00;
and this should be outside "for" loop
Can you please elaborate on this?
Thanks,
Chaitanya
On Mon, May 26, 2014 at 11:56 PM, DaeSeok Youn
On Mon, May 12, 2014 at 06:40:44PM +0900, Jungseok Lee wrote:
> This patch adds memory layout and translation lookup information
> about 48-bit address space with 4K pages. The description is based
> on 4 levels of translation tables.
>
> Cc: Catalin Marinas
> Cc: Steve Capper
> Signed-off-by:
On 05/27/14 12:39, Arnd Bergmann wrote:
> On Tuesday 27 May 2014 12:33:38 Stephen Boyd wrote:
>> On 05/27/14 12:27, Arnd Bergmann wrote:
>>> On Tuesday 27 May 2014 11:53:59 Stephen Boyd wrote:
On 05/27/14 11:49, Arnd Bergmann wrote:
> You also commented in that thread about
On Tue, 2014-05-27 at 20:32 +0100, Will Deacon wrote:
> Why would you need two barriers? I would have though an mmiowb() inlined
> into writel after the store operation would be sufficient. Or is this to
> ensure a non-relaxed write is ordered with respect to a relaxed write?
Well, so the
Removal of null pointer checks that could never happen
Signed-off-by: Rickard Strandqvist
---
fs/ocfs2/move_extents.c |3 ---
1 file changed, 3 deletions(-)
diff --git a/fs/ocfs2/move_extents.c b/fs/ocfs2/move_extents.c
index 599eb4c..9ba3a10 100644
--- a/fs/ocfs2/move_extents.c
+++
On Fri, May 23, 2014 at 1:03 AM, Grant Likely wrote:
> On Tue, 20 May 2014 13:42:02 +0300, Grygorii Strashko
> wrote:
>> The commit 9ec36cafe43bf835f8f29273597a5b0cbc8267ef
>> "of/irq: do irq resolution in platform_get_irq" from Rob Herring -
>> moves resolving of the interrupt resources in
On Tue, 27 May 2014 10:36:10 -0700, Florian Fainelli
wrote:
> Hi Grant,
>
> 2014-05-27 4:19 GMT-07:00 Grant Likely :
> > On Fri, 23 May 2014 12:43:11 -0700, Florian Fainelli
> > wrote:
> >> Add an early check for the node argument in
> >> of_get_next_available_child() to avoid dereferencing a
Hi
Ok good, then everything is under control.
The result has been that I've done a number of these types of patches to :)
Sending a new patch of that kind then.
Best regards
Rickard Strandqvist
2014-05-26 5:28 GMT+02:00 Jeff Liu :
> Hi,
>
> On 05/23/2014 04:46 AM, Rickard Strandqvist wrote:
On Tue, 2014-05-27 at 15:52 -0400, Steven Rostedt wrote:
> As Peter Zijlstra told me, we have the following path:
>
> do_exit()
> exit_itimers()
> itimer_delete()
> spin_lock_irqsave(>it_lock, );
> timer_delete_hook(timer);
> kc->timer_del(timer) := posix_cpu_timer_del()
Hi,
On Tue, May 27, 2014 at 9:44 PM, Kevin Hilman wrote:
> Kevin Hilman writes:
>
>> Tarek Dakhran writes:
>>
>>> The series of patches represent support of Exynos 5410 SoC
>>>
>>> The Exynos 5410 is the first Samsung SoC based on big.LITTLE architecture
>>>
>>> Patches add new platform
On 05/27/2014 12:48 PM, Josh Boyer wrote:
> On Tue, May 27, 2014 at 3:40 PM, wrote:
>> From: Eric Ernst
>>
>> Create a kernel cmdline parameter, "version_addendum", which can be
>> used to add text to the kernel version that is reported from
>> /proc/version.
>
> Why?
>
> What is the intended
Cleaned up dead code, added curly {} braces where needed
and fixed the following:
ERROR: do not use C99 // comments
ERROR: else should follow close brace '}'
ERROR: space required after that ',' (ctx:VxV)
ERROR: space required before the open brace '{'
ERROR: spaces required around that
On Tue, 27 May 2014 15:24:35 +0300, Pantelis Antoniou
wrote:
> Hi Grant,
>
> On May 27, 2014, at 3:12 PM, Grant Likely wrote:
>
> > On Mon, 26 May 2014 16:42:44 -0700, Guenter Roeck
> > wrote:
> >> On 05/26/2014 03:36 PM, Sebastian Reichel wrote:
> >>> Hi,
> >>>
> >>> On Mon, May 26, 2014
On Tuesday 27 May 2014 13:08:04 Stephen Boyd wrote:
> @@ -380,7 +382,7 @@ start_critical_timing(unsigned long ip, unsigned long
> parent_ip)
>
> cpu = raw_smp_processor_id();
>
> - if (per_cpu(tracing_cpu, cpu))
> + if (per_cpu(timings_stopped, cpu) || per_cpu(tracing_cpu,
Cleaned up dead code, added curly {} braces where needed
and fixed the following:
ERROR: do not use C99 // comments
ERROR: else should follow close brace '}'
ERROR: space required after that ',' (ctx:VxV)
ERROR: space required before the open brace '{'
ERROR: spaces required around that
Cleaned up dead code, added curly {} braces where needed
and fixed the following:
ERROR: do not use C99 // comments
ERROR: else should follow close brace '}'
ERROR: space required after that ',' (ctx:VxV)
ERROR: space required before the open brace '{'
ERROR: spaces required around that
Cleaned up dead code, added curly {} braces where needed
and fixed the following:
ERROR: do not use C99 // comments
ERROR: else should follow close brace '}'
ERROR: space required after that ',' (ctx:VxV)
ERROR: space required before the open brace '{'
ERROR: spaces required around that
Cleaned up dead code, added curly {} braces where needed
and fixed the following:
ERROR: do not use C99 // comments
ERROR: else should follow close brace '}'
ERROR: space required after that ',' (ctx:VxV)
ERROR: space required before the open brace '{'
ERROR: spaces required around that
Fixed the following:
ERROR: do not use C99 // comments
ERROR: space required after that ',' (ctx:VxV)
ERROR: space required after that ';' (ctx:VxV)
ERROR: space required before the open brace '{'
ERROR: spaces required around that '=' (ctx:VxV)
ERROR: spaces required around that '<' (ctx:VxV)
The idle loop calls stop_critical_timings() in an attempt to stop
the irqsoff tracer from tracing a cpu's idle time. Unfortunately,
stop_critical_timings() doesn't do much besides stop the tracer
until the point that another irqsoff event happens. This
typically happens in rcu_idle_enter() or
On Thu, 15 May 2014, Thomas Gleixner wrote:
> Acked-by me for the general approach.
>
> I don't want to give any unqualified opinion on the mm/vmstat parts of
> this patch.
Thanks. Any other comments? Could we get this into -next?
--
To unsubscribe from this list: send the line "unsubscribe
On Tue, May 27, 2014 at 03:56:00PM -0400, Mikulas Patocka wrote:
>
>
> On Tue, 27 May 2014, Jens Axboe wrote:
>
> > On 2014-05-27 10:26, Mikulas Patocka wrote:
> > > On Tue, 27 May 2014, Jens Axboe wrote:
> > >
> > > > On 2014-05-27 09:23, Mikulas Patocka wrote:
> > > >
> > > > > The patch
On Fri, May 23, 2014 at 04:54:13PM +0200, Michal Hocko wrote:
> On Wed 30-04-14 16:25:42, Johannes Weiner wrote:
> > The memcg charge API charges pages before they are rmapped - i.e. have
> > an actual "type" - and so every callsite needs its own set of charge
> > and uncharge functions to know
Hi Heinrich,
Thanks for looking into this. I've never encountered the aliasing via
wraparound or otherwise, but I've tried to code against unexpected
descriptor reuse anyway through more flexible workarounds. From a user
standpoint, denser descriptor reassignment would be preferable to
facilitate
On Mon, 19 May 2014 14:35:49 +0200, Alexander Holler
wrote:
> Am 17.05.2014 14:16, schrieb Tomasz Figa:
>
> >> References to phandles of parent or child nodes will not be added to this
> >> property, because this information is already contained in the blob (in the
> >> form of the tree
On Tue, 27 May 2014, Peter Zijlstra wrote:
> > What do you mean by shared pages that are not shmem pages? AnonPages that
> > are referenced from multiple processes?
>
> Regular files.. they get allocated through __page_cache_alloc(). AFAIK
> there is nothing stopping people from pinning file
On Tue, May 27, 2014 at 11:14:15AM -0700, Christoph Hellwig wrote:
> On Tue, May 27, 2014 at 11:42:26AM -0600, Jens Axboe wrote:
> > Except such a thing already exists, there are unplug callback
> > chains. All I'm asking is that you look into how feasible it would
> > be to use something like
Jiang,
On Tue, 27 May 2014, Jiang Liu wrote:
> +static int alloc_irq_from_domain(struct irq_domain *domain, u32 gsi, int pin)
> {
> + int irq = -1;
> +
> + if (gsi >= arch_dynirq_lower_bound(0)) {
> + irq = irq_create_mapping(domain, pin);
> + } else if (gsi <
On Tue, 27 May 2014, Vince Weaver wrote:
> OK, the problem is in:
>
> kernel/events/core.c find_get_context()
>
> retry:
> perf_lock_task_context() returns NULL.
> alloc_perf_context()
> task->perf_event_ctxp[ctxn] is *not* NULL
> err == EAGAIN so jump to retry
>
On Tue, May 27, 2014 at 01:33:06PM -0400, Mike Snitzer wrote:
> On Tue, May 27 2014 at 12:26pm -0400,
> Mikulas Patocka wrote:
>
> > On Tue, 27 May 2014, Jens Axboe wrote:
> >
> > > On 2014-05-27 09:23, Mikulas Patocka wrote:
> > >
> > > > The patch adds bio list flushing to the scheduler just
On Tue, 27 May 2014, Jens Axboe wrote:
> On 2014-05-27 10:26, Mikulas Patocka wrote:
> > On Tue, 27 May 2014, Jens Axboe wrote:
> >
> > > On 2014-05-27 09:23, Mikulas Patocka wrote:
> > >
> > > > The patch adds bio list flushing to the scheduler just besides plug
> > > > flushsing.
> > >
> >
On Tue, May 27, 2014 at 12:27 PM, Andy Lutomirski wrote:
> On Tue, May 27, 2014 at 12:23 PM, Kees Cook wrote:
>> On Tue, May 27, 2014 at 12:10 PM, Andy Lutomirski
>> wrote:
>>> On Tue, May 27, 2014 at 11:45 AM, Kees Cook wrote:
On Tue, May 27, 2014 at 11:40 AM, Andy Lutomirski
A check for CONFIG_SA1100_CT6001 was added in v2.6.11. But the related
Kconfig symbol was never added to the tree. Remove this check and do
some related cleaning up.
Signed-off-by: Paul Bolle
---
Entirely untested.
arcnet was new for me (as are a lot of things). So I did a rather wide
search of
On Fri, May 23, 2014 at 03:39:38PM +0200, Michal Hocko wrote:
> I am adding Vladimir to CC
>
> On Wed 30-04-14 16:25:41, Johannes Weiner wrote:
> > Kmem page charging and uncharging is serialized by means of exclusive
> > access to the page. Do not take the page_cgroup lock and don't set
> >
On Tue, May 27, 2014 at 05:27:34PM +0100, Charles Keepax wrote:
> From: Arnd Bergmann
>
> commit 2cce4be9e6b8 "regulator: arizona-ldo1: Add processing of init_data
> from device tree" added a call to of_get_child_by_name() but
> did not add an #include to the header file declaring that function.
As Peter Zijlstra told me, we have the following path:
do_exit()
exit_itimers()
itimer_delete()
spin_lock_irqsave(>it_lock, );
timer_delete_hook(timer);
kc->timer_del(timer) := posix_cpu_timer_del()
put_task_struct()
__put_task_struct()
On Tue, May 27, 2014 at 01:00:32PM -0500, Thor Thayer wrote:
> On Tue, May 27, 2014 at 2:11 AM, Steffen Trumtrar
> wrote:
> > On Wed, May 21, 2014 at 10:38:34AM -0500, Thor Thayer wrote:
> >> On Tue, May 20, 2014 at 9:44 AM, Steffen Trumtrar
> >> wrote:
> >> > Hi!
> >> >
> >> > On Tue, May 20,
On Tue, May 27, 2014 at 11:38:49AM +0200, Boris BREZILLON wrote:
> I'm still waiting for inputs regarding the ipsout regulator representation:
If you've got questions you need an answer to urgently it's possibly
best to highlight them outside of a series like this doing that helps
make it more
On Tue, May 27, 2014 at 3:40 PM, wrote:
> From: Eric Ernst
>
> Create a kernel cmdline parameter, "version_addendum", which can be
> used to add text to the kernel version that is reported from
> /proc/version.
Why?
What is the intended purpose of this and why would someone want to use it?
On Tue, 27 May 2014, Vince Weaver wrote:
> perf_fuzzer-2989 [001] 1994.514398: sys_enter: NR 298 (699f28,
> bad, 0, , 2, 7fff361a3360)
> perf_fuzzer-2989 [001] 1994.514399: bprint:
> SYSC_perf_event_open: VMW: perf_event_open type=1 config=8 period=0
On Fri, May 23, 2014 at 03:20:43PM +0200, Michal Hocko wrote:
> On Wed 30-04-14 16:25:40, Johannes Weiner wrote:
> > There is a write barrier between setting pc->mem_cgroup and
> > PageCgroupUsed, which was added to allow LRU operations to lookup the
> > memcg LRU list of a page without acquiring
On Tue, May 27, 2014 at 02:12:17PM -0500, Alan Tull wrote:
> On Tue, May 27, 2014 at 2:11 AM, Steffen Trumtrar
> wrote:
> > On Wed, May 21, 2014 at 10:38:34AM -0500, Thor Thayer wrote:
> >> On Tue, May 20, 2014 at 9:44 AM, Steffen Trumtrar
> >> wrote:
> >> > Hi!
> >> >
> >> > On Tue, May 20,
On Tue, May 27, 2014 at 03:17:28PM -0400, Steven Rostedt wrote:
> This looks like functionality change to me.
>
> Please make the fix of "==" --> ">=" a separate patch.
Yeah, that's actually a fix for console_loglevel values > 10. I don't
think it is worth the effort of splitting though ...
From: Eric Ernst
Create a kernel cmdline parameter, "version_addendum", which can be
used to add text to the kernel version that is reported from
/proc/version.
Signed-off-by: Eric Ernst
---
fs/proc/version.c | 14 +-
init/version.c|2 +-
2 files changed, 14
On Tuesday 27 May 2014 12:33:38 Stephen Boyd wrote:
> On 05/27/14 12:27, Arnd Bergmann wrote:
> > On Tuesday 27 May 2014 11:53:59 Stephen Boyd wrote:
> >> On 05/27/14 11:49, Arnd Bergmann wrote:
> >>> You also commented in that thread about stop_critical_timings()/
> >>> start_critical_timings().
On 27.05.2014 19:25, Jeff Smith wrote:
inotify's behavior concerning events from removed watches (they do
happen) and watch descriptor reuse (beyond my knowledge) is currently
undocumented.
Although it mimics a standard multiplexing interface in most regards,
writing a robust user-space handler
On 05/27/2014 01:21 PM, Christoph Hellwig wrote:
> On Tue, May 27, 2014 at 01:17:40PM -0600, Jens Axboe wrote:
>> But I think you sent the old one again, not the new variant :-)
>
> Oh well, next try:
This looks good to me. Was trying to think of ways to reduce that to one
list iteration, but I
On Sun, May 25, 2014 at 10:47:50PM +0100, Benjamin Herrenschmidt wrote:
> On Thu, 2014-05-22 at 17:47 +0100, Will Deacon wrote:
> > Hi all,
> >
> > This is version 2 of the series I originally posted here:
> >
> > https://lkml.org/lkml/2014/4/17/269
> >
> > Changes since v1 include:
> >
> >
On 05/27/14 12:27, Arnd Bergmann wrote:
> On Tuesday 27 May 2014 11:53:59 Stephen Boyd wrote:
>> On 05/27/14 11:49, Arnd Bergmann wrote:
>>> You also commented in that thread about stop_critical_timings()/
>>> start_critical_timings(). Corey, can you look at that, too? I
>>> think it's designed to
Hi Ben,
On Sun, May 25, 2014 at 10:46:03PM +0100, Benjamin Herrenschmidt wrote:
> On Thu, 2014-05-22 at 17:47 +0100, Will Deacon wrote:
> > A corollary to this is that mmiowb() probably needs rethinking. As it
> > currently
> > stands, an mmiowb() is required to order MMIO writes to a device
On Tue, May 27, 2014 at 05:37:29PM +0530, Viresh Kumar wrote:
> Liam/Broonie: Please see if this can go through Rafael as 2nd patch is
> dependent
> on it.
Is that likely to happen before the merge window?
> +static inline int regulator_set_voltage_time(struct regulator *regulator,
> +
On Tue, May 27, 2014 at 9:21 PM, Arnaldo Carvalho de Melo
wrote:
> Em Tue, May 27, 2014 at 06:35:17PM +0200, Michael Kerrisk (man-pages)
> escreveu:
>> On 05/26/2014 11:17 PM, Arnaldo Carvalho de Melo wrote:
>> > Can you try the attached patch on top of the first one?
>
>> Patches on patches is
From: Eric Ernst
For Baytrail, you should never set a GPIO set to direct_irq
to output mode. When direct_irq_en is set for a GPIO, it is
tied directly to an APIC internally, and making the pad output
does not make any sense. Assert a WARN() in the event this happens.
Signed-off-by: Eric Ernst
On Tue, May 27, 2014 at 12:23 PM, Kees Cook wrote:
> On Tue, May 27, 2014 at 12:10 PM, Andy Lutomirski wrote:
>> On Tue, May 27, 2014 at 11:45 AM, Kees Cook wrote:
>>> On Tue, May 27, 2014 at 11:40 AM, Andy Lutomirski
>>> wrote:
On Tue, May 27, 2014 at 11:24 AM, Kees Cook wrote:
>
On Tuesday 27 May 2014 11:53:59 Stephen Boyd wrote:
> On 05/27/14 11:49, Arnd Bergmann wrote:
> >
> > You also commented in that thread about stop_critical_timings()/
> > start_critical_timings(). Corey, can you look at that, too? I
> > think it's designed to avoid the issue you are seeing but
> >
On 05/27/14 12:13, Steven Rostedt wrote:
> Hey! I was able to get to this.
Great!
>
> On Mon, 19 May 2014 12:30:47 -0700
> Stephen Boyd wrote:
>
>> +if (!tracer_enabled || !tracing_is_enabled() ||
>> +per_cpu(timings_stopped, cpu))
>> +return;
> Micro
You could also get rid of the separate ret/count variables
and use ssize_t everywhere; that's the declared return type
of rw_copy_check_uvector and __splice_from_pipe, after all.
Hunks after the first two are optional extras to make types
consistent in other functions in that file, although I
From: Amir Vadai
Date: Sun, 25 May 2014 17:47:26 +0300
> This function sets the n'th cpu - local cpu's first.
> For example: in a 16 cores server with even cpu's local, will get the
> following values:
> cpumask_set_cpu_local_first(0, numa, cpumask) => cpu 0 is set
>
On Tue, May 27, 2014 at 12:10 PM, Andy Lutomirski wrote:
> On Tue, May 27, 2014 at 11:45 AM, Kees Cook wrote:
>> On Tue, May 27, 2014 at 11:40 AM, Andy Lutomirski
>> wrote:
>>> On Tue, May 27, 2014 at 11:24 AM, Kees Cook wrote:
On Mon, May 26, 2014 at 12:27 PM, Andy Lutomirski
On Tue, May 27, 2014 at 01:17:40PM -0600, Jens Axboe wrote:
> But I think you sent the old one again, not the new variant :-)
Oh well, next try:
>From ff3685b6052a31fbafc72551cdf7c123cd2b4634 Mon Sep 17 00:00:00 2001
From: Christoph Hellwig
Date: Wed, 21 May 2014 19:37:11 +0200
Subject: blk-mq:
Em Tue, May 27, 2014 at 06:35:17PM +0200, Michael Kerrisk (man-pages) escreveu:
> On 05/26/2014 11:17 PM, Arnaldo Carvalho de Melo wrote:
> > Can you try the attached patch on top of the first one?
> Patches on patches is a way to make your testers work unnecessarily
> harder. Also, it means
On Mon, 19 May 2014 20:27:32 +0200
Borislav Petkov wrote:
> From: Borislav Petkov
>
> There should be no functionality change resulting from this patch.
>
> diff --git a/arch/x86/kernel/head64.c b/arch/x86/kernel/head64.c
> index 068054f4bf20..eda1a865641e 100644
> ---
On 05/27/2014 01:15 PM, Christoph Hellwig wrote:
> On Tue, May 27, 2014 at 12:54:22PM -0600, Jens Axboe wrote:
>> Space is plenty big again now... The down side is that the splice trick
>> wont work, but if we have more than a few requests on the requeue list,
>> we're doing it wrong anyway.
>
On Tue, May 27, 2014 at 12:54:22PM -0600, Jens Axboe wrote:
> Space is plenty big again now... The down side is that the splice trick
> wont work, but if we have more than a few requests on the requeue list,
> we're doing it wrong anyway.
I don't see a problem with the splice. How about this
Hey! I was able to get to this.
On Mon, 19 May 2014 12:30:47 -0700
Stephen Boyd wrote:
> The idle loop calls stop_critical_timings() in an attempt to stop
> the irqsoff tracer from tracing a cpu's idle time. Unfortunately,
> stop_critical_timings() doesn't do much besides stop the tracer
>
On Tue, May 27, 2014 at 2:11 AM, Steffen Trumtrar
wrote:
> On Wed, May 21, 2014 at 10:38:34AM -0500, Thor Thayer wrote:
>> On Tue, May 20, 2014 at 9:44 AM, Steffen Trumtrar
>> wrote:
>> > Hi!
>> >
>> > On Tue, May 20, 2014 at 09:31:06AM -0500, Alan Tull wrote:
>> >> On Mon, May 19, 2014 at 2:37
On Tue, May 27, 2014 at 11:45 AM, Kees Cook wrote:
> On Tue, May 27, 2014 at 11:40 AM, Andy Lutomirski wrote:
>> On Tue, May 27, 2014 at 11:24 AM, Kees Cook wrote:
>>> On Mon, May 26, 2014 at 12:27 PM, Andy Lutomirski
>>> wrote:
On Fri, May 23, 2014 at 10:05 AM, Kees Cook wrote:
>
Hi Kame,
it's been a long time, I hope you're doing well.
On Tue, May 27, 2014 at 04:43:28PM +0900, Kamezawa Hiroyuki wrote:
> (2014/05/01 5:25), Johannes Weiner wrote:
> > The memcg uncharging code that is involved towards the end of a page's
> > lifetime - truncation, reclaim, swapout,
On Tue, May 27, 2014 at 11:52 AM, Greg Kroah-Hartman
wrote:
> On Mon, May 26, 2014 at 07:04:53PM +0900, Heesub Shin wrote:
>> For aesthetics and readability, rename goto labels, remove
>> useless code lines, and clarify function return type.
>>
>> Signed-off-by: Heesub Shin
>> ---
>>
On Tue, May 27, 2014 at 09:05:43PM +0530, navin patidar wrote:
> Signed-off-by: navin patidar
> ---
> drivers/staging/rtl8712/osdep_service.h |6 --
> 1 file changed, 6 deletions(-)
This is the rtl8712 driver, not the rtl8188eu driver.
And this patch causes a build error.
Please
This series streamlines the request allocation path.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
The current logic for blocking tag allocation is rather confusing, as we
first allocated and then free again a tag in blk_mq_wait_for_tags, just
to attempt a non-blocking allocation and then repeat if someone else
managed to grab the tag before us.
Instead change blk_mq_alloc_request_pinned to
Both callers if __blk_mq_alloc_request want to initialize the request, so
lift it into the common path.
Signed-off-by: Christoph Hellwig
---
block/blk-mq.c | 62 +++-
1 file changed, 30 insertions(+), 32 deletions(-)
diff --git
We already do a non-blocking allocation in blk_mq_map_request, no need
to repeat it. Just call __blk_mq_alloc_request to wait directly.
Signed-off-by: Christoph Hellwig
---
block/blk-mq.c |8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/block/blk-mq.c
Instead of having two almost identical copies of the same code just let
the callers pass in the reserved flag directly.
Signed-off-by: Christoph Hellwig
---
block/blk-core.c |2 +-
block/blk-mq.c| 20 +++-
We now only have one caller left and can open code it there in a cleaner
way.
Signed-off-by: Christoph Hellwig
---
block/blk-mq.c | 48
1 file changed, 16 insertions(+), 32 deletions(-)
diff --git a/block/blk-mq.c b/block/blk-mq.c
index
On Mon, May 26, 2014 at 9:04 AM, Borislav Petkov wrote:
> Hi guys,
>
> so I get this with rc7+tip but not with rc6+tip:
>
> ACPI Error: Could not enable RealTimeClock event (20140214/evxfevnt-212)
> ACPI Warning: Could not enable fixed event - RealTimeClock (4)
> (20140214/evxface-628)
Does it
On 05/27/14 11:49, Arnd Bergmann wrote:
>
> You also commented in that thread about stop_critical_timings()/
> start_critical_timings(). Corey, can you look at that, too? I
> think it's designed to avoid the issue you are seeing but
> for some reason doesn't.
I sent a patch last week to "solve"
On Tue, 27 May 2014 14:52:01 -0400
Steven Rostedt wrote:
> Ah crap. I did a search on all the callers of put_task_struct(), and
> somehow missed this one. Yep, I was looking for places that called
> this while holding other irq safe locks.
>
Anyway, this nicely answers Mike's question to
On 2014-05-27 12:53, Christoph Hellwig wrote:
On Tue, May 27, 2014 at 12:38:15PM -0600, Jens Axboe wrote:
On 2014-05-27 12:13, Christoph Hellwig wrote:
Here is my counter proposal that requeues via two lists and a work struct
in the request_queue. I've also tested it with scsi-mq.
I like
So what did I do wrong with this build of 'perf' (other than
trying to do it on a Fedora Rawhide box updated to last night? :)
(The obvious hack fix is to change the '#define _BSD_SOURCE 1' in util/util.h
to use _DEFAULT_SOURCE instead, but not sure how that plays on older
userspaces, as that was
On Tue, May 27, 2014 at 12:38:15PM -0600, Jens Axboe wrote:
> On 2014-05-27 12:13, Christoph Hellwig wrote:
>> Here is my counter proposal that requeues via two lists and a work struct
>> in the request_queue. I've also tested it with scsi-mq.
>>
>
> I like this, moves the state out of the
On Tue, May 27, 2014 at 02:10:19PM +0100, Steven Rostedt wrote:
> Will,
>
> I made a separate branch called ftrace/arm64 as shown below. You can
> pull that branch to base the rest of Akashi-san's patches on top of it.
> The branch is based on top of v3.15-rc5.
Thanks Steve, I'll pull that in.
On Tue, 27 May 2014 20:25:41 +0200
Peter Zijlstra wrote:
> Nope, its really IRQs.
>
> do_exit()
> exit_itimers()
> itimer_delete()
> spin_lock_irqsave(>it_lock, );
> timer_delete_hook(timer);
> kc->timer_del(timer) := posix_cpu_timer_del()
>
201 - 300 of 1648 matches
Mail list logo
