From: Dave Hansen
Same deal as the last one. Lots of code savings using the new
walker function.
Signed-off-by: Dave Hansen
---
b/fs/proc/task_mmu.c | 39 ---
1 file changed, 8 insertions(+), 31 deletions(-)
diff -puN
From: Dave Hansen
The diffstat tells the story here. Using the new walker function
greatly simplifies the code. One side-effect here is that we'll
call cond_resched() more often than we did before. It used to be
called once per pte page, but now it's called on every pte.
Signed-off-by: Dave
From: Dave Hansen
Neither the locking nor the splitting logic needed for
transparent huge pages is trivial. We end up having to teach
each of the page walkers about it individually, and have the same
pattern copied across several of them.
This patch introduces a new handler:
From: Dave Hansen
The walk_page_range() code calls in to the ->hugetlbfs_entry
handler once for each huge page table entry. This means that
addr and end are always within the same huge page. (Well, end is
not technically _within_ it, because it is exclusive.)
The outer while() loop in
Quoting Heiko Stübner (2014-05-18 15:40:07)
> This enables the setting of a custom clock name for the clock provided by
> the hym8563 rtc.
>
> Signed-off-by: Heiko Stuebner
Annoying nitpick: would be nice to see the example updated to use
clock-output-names. But it's not a deal breaker.
On Mon, Jun 02, 2014 at 02:03:12PM -0700, David Miller wrote:
> From: "Michael S. Tsirkin"
> Date: Mon, 2 Jun 2014 23:55:15 +0300
>
> > The following changes since commit 96b2e73c5471542cb9c622c4360716684f8797ed:
> >
> > Revert "net/mlx4_en: Use affinity hint" (2014-06-02 00:18:48 -0700)
> >
Michael Mueller provided a patch to reduce the size of
vhost-net structure as some allocations could fail under
memory pressure/fragmentation. We are still left with
high order allocations though.
This patch is handling the problem at the core level, allowing
vhost structures to use vmalloc() if
All memory accesses are done under some VQ mutex.
So lock/unlock all VQs is a faster equivalent of synchronize_rcu()
for memory access changes.
Some guests cause a lot of these changes, so it's helpful
to make them faster.
Reported-by: "Gonglei (Arei)"
Signed-off-by: Michael S. Tsirkin
---
Reposting with actual patches included.
The following changes since commit 96b2e73c5471542cb9c622c4360716684f8797ed:
Revert "net/mlx4_en: Use affinity hint" (2014-06-02 00:18:48 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git
Wrong address is checked after memory allocation.
Signed-off-by: Rickard Strandqvist
---
drivers/thermal/ti-soc-thermal/ti-bandgap.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/thermal/ti-soc-thermal/ti-bandgap.c
b/drivers/thermal/ti-soc-thermal/ti-bandgap.c
hi,
trying to speedup DWARF unwind report code by factoring
related code:
- caching sample's registers access
- keep dso data file descriptor open for the
life of the dso object
- replace dso cache code by mapping dso data file
directly for the life of the dso object
The speedup is
Add separated structure/namespace for data related
variables. We are going to add mode of them, so this
way they will be clearly separated.
Cc: Arnaldo Carvalho de Melo
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jean Pihet
Cc: Namhyung Kim
Cc: Paul
Adding global count of opened dso objects so we could
properly limit the number of opened dso data file
descriptors.
Cc: Arnaldo Carvalho de Melo
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jean Pihet
Cc: Namhyung Kim
Cc: Paul Mackerras
Cc: Peter Zijlstra
Adding data_fd into dso object so we could handle caching
of opened dso file data descriptors coming int next patches.
Adding dso__data_close interface to keep the data_fd updated
when the descriptor is closed.
Cc: Arnaldo Carvalho de Melo
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic
Adding file size check, because the lseek will succeed for
any offset behind file size and thus succeed when it was
expected to fail.
Factoring the code to check the offset against file size
earlier in the flow.
Cc: Arnaldo Carvalho de Melo
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic
Adding do_open function that tries to close opened
dso objects in case we fail to open the dso due to
to crossing the allowed RLIMIT_NOFILE limit.
Cc: Arnaldo Carvalho de Melo
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jean Pihet
Cc: Namhyung Kim
Cc: Paul
Caching dso data file descriptors to avoid expensive re-opens
especially during DWARF unwind.
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
Adding descriptions/explanations for dso__data_* interface
functions.
Cc: Arnaldo Carvalho de Melo
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jean Pihet
Cc: Namhyung Kim
Cc: Paul Mackerras
Cc: Peter Zijlstra
Signed-off-by: Jiri Olsa
---
In upcoming tests we will setup process limits, which
might affect other tests. Spawning child for each test
to prevent this.
Cc: Arnaldo Carvalho de Melo
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jean Pihet
Cc: Namhyung Kim
Cc: Paul Mackerras
Cc: Peter
Adding test that setup test_dso_data__fd_limit and test
dso data file descriptors are cached appropriately.
Cc: Arnaldo Carvalho de Melo
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jean Pihet
Cc: Namhyung Kim
Cc: Paul Mackerras
Cc: Peter Zijlstra
Testing that perf properly closes opened dso objects
and tries to reopen in case we run out of allowed file
descriptors for dso data.
Cc: Arnaldo Carvalho de Melo
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jean Pihet
Cc: Namhyung Kim
Cc: Paul Mackerras
Making the test_file function to be reusable for
new tests coming in following patches.
Cc: Arnaldo Carvalho de Melo
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jean Pihet
Cc: Namhyung Kim
Cc: Paul Mackerras
Cc: Peter Zijlstra
Signed-off-by: Jiri Olsa
Adding global list of opened dso objects, so we can
track them and use the list for caching dso data file
descriptors.
Cc: Arnaldo Carvalho de Melo
Cc: Corey Ashford
Cc: David Ahern
Cc: Frederic Weisbecker
Cc: Ingo Molnar
Cc: Jean Pihet
Cc: Namhyung Kim
Cc: Paul Mackerras
Cc: Peter
Caching registers value into an array. Got about 4% speed up
of perf_reg_value function for report command processing
dwarf unwind stacks.
Output from report over 1.5 GB data with DWARF unwind stacks:
(TODO fix perf diff)
current code:
5.84% perf perf [.]
On Mon, Jun 2, 2014 at 1:06 PM, Kees Cook wrote:
> On Mon, Jun 2, 2014 at 12:59 PM, Andy Lutomirski wrote:
>> On Mon, Jun 2, 2014 at 12:47 PM, Kees Cook wrote:
>>> Hi Andrew,
>>>
>>> Would you be willing to carry this series? Andy Lutomirski appears
>>> happy with it now. (Thanks again for all
On Mon, 02 Jun 2014 09:12:25 -0700 Dave Hansen wrote:
> On 06/01/2014 10:24 PM, Naoya Horiguchi wrote:
> > -#define PAGECACHE_TAG_DIRTY0
> > -#define PAGECACHE_TAG_WRITEBACK1
> > -#define PAGECACHE_TAG_TOWRITE 2
> > +enum {
> > + PAGECACHE_TAG_DIRTY,
> > +
Hi
Okay, then I make a new patch with only the if() part of the code.
Best regards
Rickard Strandqvist
2014-06-02 19:08 GMT+02:00 Eduardo Valentin :
> On Sun, Jun 01, 2014 at 01:33:51PM +0200, Rickard Strandqvist wrote:
>> There is a risk for memory leak in when something unexpected happens
On Mon, 2 Jun 2014, Linus Torvalds wrote:
> On Mon, Jun 2, 2014 at 1:46 PM, Mikulas Patocka wrote:
> >
> > And what else do you want to do?
> >
> > Peter Zijlstra said "I've been using xchg() and cmpxchg() without such
> > consideration for quite a while." - so it basically implies that the
>
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 Mon, Jun 2, 2014 at 2:02 PM, Paul E. McKenney
wrote:
>
> In the ->qlen case, interrupts are disabled and the current CPU is
> the only one who can write, so the read need not be volatile. In the
> ->n_barrier_done, modifications are done holding ->barrier_mutex, so again
> the read need not
On 6/1/2014 7:56 AM, Fabian Frederick wrote:
replace IS_ERR/PTR_ERR
Cc: Chris Metcalf
Cc: Greg Kroah-Hartman
Signed-off-by: Fabian Frederick
---
This is untested.
drivers/tty/hvc/hvc_tile.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Thanks, taken into the linux-tile tree.
Quoting Alex Elder (2014-05-30 20:46:46)
> On 05/30/2014 06:28 PM, Mike Turquette wrote:
> > Quoting Alex Elder (2014-05-30 13:53:02)
> >> Use a counter rather than a Boolean to track whether write access to
> >> a CCU has been enabled or not. This will allow more than one of
> >> these requests
From: "Michael S. Tsirkin"
Date: Mon, 2 Jun 2014 23:55:15 +0300
> The following changes since commit 96b2e73c5471542cb9c622c4360716684f8797ed:
>
> Revert "net/mlx4_en: Use affinity hint" (2014-06-02 00:18:48 -0700)
>
> are available in the git repository at:
>
>
On Mon, Jun 02, 2014 at 01:22:10PM -0700, Linus Torvalds wrote:
> On Mon, Jun 2, 2014 at 1:05 PM, Peter Zijlstra wrote:
> >
> > So the question is, do you prefer subtly broken code or hard compile
> > fails? Me, I go for the compile fail.
>
> The thing is, parisc has a perfectly fine "cmpxchg"
On Mon, Jun 02, 2014 at 10:09:35AM -0700, Linus Torvalds wrote:
> On Mon, Jun 2, 2014 at 9:25 AM, Peter Zijlstra wrote:
> >
> > And I can't say I'm a particular fan of these ops either, as alternative
> > I'm almost inclined to just exclude parisc from using opt spinning.
>
> Please do.
>
>
On Mon, 2 Jun 2014, Arnd Bergmann wrote:
> Ok. Sorry about missing linux-api, I confused it with linux-arch, which
> may not be as relevant here, except for the one question whether we
> actually want to have the new ABI on all 32-bit architectures or only
> as an opt-in for those that expect to
On Mon, Jun 02, 2014 at 10:01:43AM +0100, Charles Keepax wrote:
> Sometimes MFD children will have interdependancies. For example an MFD
> device might contain a regulator cell and another cell which requires
> that regulator to function. Probe deferral will ensure that these
> devices probe in
On Mon, Jun 02 2014, Tejun Heo wrote:
> Hello,
>
> On Mon, Jun 02, 2014 at 11:46:36AM -0600, Jens Axboe wrote:
> > But blk-mq will potentially drive anything, so it might not be out of
> > the question with a more expensive scheduling variant, if it makes any
> > sense to do of course. At least
The following changes since commit 96b2e73c5471542cb9c622c4360716684f8797ed:
Revert "net/mlx4_en: Use affinity hint" (2014-06-02 00:18:48 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next
for you to fetch changes up to
Hi Matthew and Keith,
Here is an updated patch with the feedback from the previous days. It's against
Jens' for-3.16/core tree. You may use the nvmemq_wip_review branch at:
https://github.com/MatiasBjorling/linux-collab nvmemq_wip_review
and see the changes from v4 to v5 here:
On Tue, May 27, 2014 at 12:55 PM, Kees Cook wrote:
> 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 Mon, Jun 2, 2014 at 1:46 PM, Mikulas Patocka wrote:
>
> And what else do you want to do?
>
> Peter Zijlstra said "I've been using xchg() and cmpxchg() without such
> consideration for quite a while." - so it basically implies that the
> kernel is full of such races, mcs_spinlock is just the
Hi
I mail about this for the first time in early May, but ther were many
other faults in the design of my patch then, had several different
types of errors in the same path etc.
So good that someone was inspired to make a real patch of it even then :)
And i'm getting the linux-next to check
On 02.06.14, 23:41, Kumar Gala wrote:
>
> On May 31, 2014, at 10:45 AM, Georgi Djakov wrote:
>
>> This patch adds the necessary node to probe the global clock
>> controller on APQ8084 platforms.
>>
>> Signed-off-by: Georgi Djakov
>> ---
>> arch/arm/boot/dts/qcom-apq8084.dtsi | 10 ++
On Mon, 2 Jun 2014, Linus Torvalds wrote:
> On Mon, Jun 2, 2014 at 9:25 AM, Peter Zijlstra wrote:
> >
> > And I can't say I'm a particular fan of these ops either, as alternative
> > I'm almost inclined to just exclude parisc from using opt spinning.
>
> Please do.
>
> There is no way in
From: Alexey Brodkin
Date: Mon, 2 Jun 2014 19:14:09 +
> I understand that putting everything in DT is not a way to go.
> But a rationale for this particular patch is as follows: as I may see up
> until now everybody was happy with 100 milliseconds, but on my
> particular board connected to
On Monday 02 June 2014 15:43:02 Kumar Gala wrote:
> Its imx6 and exynos, havent looked to see if dw-pcie is handling
> the parsing or not for them.
Ok, so they are both dw-pcie variants.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Mon, Jun 2, 2014 at 1:42 PM, David Miller wrote:
>
> I'm working through my backlog and you will have this by the end of a
> day via a pull request.
Thanks, and no worries,
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
On Jun 2, 2014, at 2:15 PM, Arnd Bergmann wrote:
> On Monday 02 June 2014 13:09:08 Kumar Gala wrote:
>>> However, what do we do with the 2 cases that exist in upstream that
are using ranges for cfg space?
>>>
>>> Ignore them in the core code? Make the specific host controller handle
>>>
On Mon, Jun 02, 2014 at 12:26:31PM -0700, Paul E. McKenney wrote:
> On Mon, Jun 02, 2014 at 12:05:17PM -0700, Joe Perches wrote:
> > On Mon, 2014-06-02 at 11:55 -0700, j...@joshtriplett.org wrote:
> > > this should go along with a change to
> > > get_maintainer.pl to add those folks to the CC
From: Linus Torvalds
Date: Mon, 2 Jun 2014 12:01:49 -0700
> On Mon, Jun 2, 2014 at 11:54 AM, Andy Lutomirski wrote:
>>
>> AFAIK, Zebra is still broken on 3.15. Should something like this be
>> applied:
>>
>> http://article.gmane.org/gmane.linux.kernel.stable/91782
>
> Ahh, yes. I thought it
On May 31, 2014, at 10:45 AM, Georgi Djakov wrote:
> This patch adds the necessary node to probe the global clock
> controller on APQ8084 platforms.
>
> Signed-off-by: Georgi Djakov
> ---
> arch/arm/boot/dts/qcom-apq8084.dtsi | 10 ++
> 1 file changed, 10 insertions(+)
Can you split
From: Tom Gundersen
Date: Mon, 2 Jun 2014 20:57:02 +0200
> Would this patch be suitable for stable? While it does not fix a
> regression, it appears to fix the intended behaviour of
> MODULE_ALIAS_RTNL_LINK?
It probably is suitable... I'll queue it up, thanks.
--
To unsubscribe from this list:
On 06/02/2014 01:36 PM, Joe Perches wrote:
> On Mon, 2014-06-02 at 13:35 -0700, Andrew Morton wrote:
>> On Mon, 2 Jun 2014 10:00:20 -0700 "Paul E. McKenney"
>> wrote:
>>
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -7321,6 +7321,7 @@ F:kernel/rcu/torture.c
>>>
>>> RCUTORTURE TEST
attr.sched_policy is u32, therefore a comparison against < 0 is never true.
Fix this by casting sched_policy to int.
This issue was reported by coverity CID 1219934.
Cc: Michael Kerrisk
Cc: Peter Zijlstra
Cc: Ingo Molnar
Signed-off-by: Richard Weinberger
---
kernel/sched/core.c | 2 +-
1
--
Mahindra India approve your email, to receive Eight Hundred Thousand Pounds
Sterlings.
Provide:
Name---
Address---
Mobile -
Age-
Occupation-
Thank You
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Mon, 2014-06-02 at 13:35 -0700, Andrew Morton wrote:
> On Mon, 2 Jun 2014 10:00:20 -0700 "Paul E. McKenney"
> wrote:
>
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -7321,6 +7321,7 @@ F:kernel/rcu/torture.c
> >
> > RCUTORTURE TEST FRAMEWORK
> > M: "Paul E. McKenney"
> > +R:
On Mon, 2 Jun 2014 10:00:20 -0700 "Paul E. McKenney"
wrote:
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7321,6 +7321,7 @@ F: kernel/rcu/torture.c
>
> RCUTORTURE TEST FRAMEWORK
> M: "Paul E. McKenney"
> +R: Josh Triplett
> L: linux-kernel@vger.kernel.org
> S: Supported
>
On 06/02/2014 07:15 PM, Stephen Warren wrote:
I think the content in this patch is for 3.17. The issues mentioned
below --- would be worth fixing for 3.16.
It sure is your call. I feared it being too late for 3.16 now with Linus
having opened the merge window presumably one week early.
--
To
On 06/02/2014 02:18 PM, Marcel Ziswiler wrote:
> On 06/02/2014 06:26 PM, Stephen Warren wrote:
>>> +pwmleds {
>>> +compatible = "pwm-leds";
>>> +
>>> +pwm3 {
>>> +label = "PWM3";
>>> +pwms = < 1 19600>;
>>> +max-brightness = <255>;
>>> +
On Mon, 2014-06-02 at 13:08 -0700, Andrew Morton wrote:
> On Thu, 29 May 2014 19:20:15 -0700 Davidlohr Bueso wrote:
>
> > On Thu, 2014-05-22 at 20:33 -0700, Davidlohr Bueso wrote:
> > > This patchset extends the work started by Ingo Molnar in late 2012,
> > > optimizing the anon-vma mutex lock,
On Mon, Jun 02, 2014 at 12:40:38PM -0700, Randy Dunlap wrote:
> On 06/02/2014 12:36 PM, Joe Perches wrote:
> > On Mon, 2014-06-02 at 12:27 -0700, Paul E. McKenney wrote:
> >> On Mon, Jun 02, 2014 at 12:11:55PM -0700, j...@joshtriplett.org wrote:
> >>>
> >>> I'd suggest adding Mathieu Desnoyers,
- Original Message -
> From: "Paul E. McKenney"
> To: j...@joshtriplett.org
> Cc: "Joe Perches" , linux-kernel@vger.kernel.org,
> mi...@kernel.org, la...@cn.fujitsu.com,
> dipan...@in.ibm.com, a...@linux-foundation.org, "mathieu desnoyers"
> ,
> n...@us.ibm.com, t...@linutronix.de,
On Mon, 2014-06-02 at 22:05 +0200, Peter Zijlstra wrote:
> On Mon, Jun 02, 2014 at 01:33:34PM -0400, Waiman Long wrote:
> > On 06/02/2014 12:30 PM, Peter Zijlstra wrote:
> > >On Mon, Jun 02, 2014 at 06:25:25PM +0200, Peter Zijlstra wrote:
> > >>I'm almost inclined to just exclude parisc from using
On 06/02/2014 06:33 PM, Stephen Warren wrote:
I vaguely recall people speaking out against including "spidev" devices
in DT because they don't represent actual HW, but rather a way to
request that the SPI bus be exposed to user-space, which is a pure SW
issue. Wouldn't it be better if the spidev
On Mon, Jun 02, 2014 at 02:13:19AM +, Linux Kernel wrote:
> sched: Disallow sched_attr::sched_policy < 0
>
> The scheduler uses policy=-1 to preserve the current policy state to
> implement sys_sched_setparam(), this got exposed to userspace by
> accident through
On Mon, Jun 2, 2014 at 1:05 PM, Peter Zijlstra wrote:
>
> So the question is, do you prefer subtly broken code or hard compile
> fails? Me, I go for the compile fail.
The thing is, parisc has a perfectly fine "cmpxchg" implementation in
practice, and ACCESS_ONCE() and friends work fine too for
On Sun, 1 Jun 2014 15:53:04 +0200 Rickard Strandqvist
wrote:
> There is a risk that the variable will be used without being initialized.
um, no there isn't.
> --- a/fs/ocfs2/dir.c
> +++ b/fs/ocfs2/dir.c
> @@ -3738,7 +3738,7 @@ static int ocfs2_dx_dir_rebalance(struct ocfs2_super
> *osb,
On 06/02/2014 06:26 PM, Stephen Warren wrote:
+ toradex,colibri_t30
+ toradex,colibri_t30-eval-v3
Those don't seem to be related to Apalis support.
Yes, that's why I mentioned it in the commit message as follows:
>> While at it also add the device tree binding documentation for Apalis
>>
Hi Dan!
Now this is a bad example because there is nothing really wrong, and I
could not find the original error log :-(
But i get for the testing variable:
drivers/staging/rtl8192u/r8192U_core.c : 4747] : (style) Variable
'testing' is assigned a value that is never used.
And for the this
On Mon, 2 Jun 2014, Vlastimil Babka wrote:
> compact_should_abort() returns true instead of false and vice versa
> due to changes between v1 and v2 of the patch. This makes both async
> and sync compaction abort with high probability, and has been reported
> to cause e.g. soft lockups on some ARM
On Thu, 29 May 2014 19:20:15 -0700 Davidlohr Bueso wrote:
> On Thu, 2014-05-22 at 20:33 -0700, Davidlohr Bueso wrote:
> > This patchset extends the work started by Ingo Molnar in late 2012,
> > optimizing the anon-vma mutex lock, converting it from a exclusive mutex
> > to a rwsem, and sharing
On Mon, Jun 02, 2014 at 12:55:50PM -0700, Joe Perches wrote:
> On Mon, 2014-06-02 at 12:50 -0700, Paul E. McKenney wrote:
> > I sometimes review patches in areas where
> > I have no commits.
>
> Lots of people review patches all over the tree.
> That doesn't mean they want to be or should be
On 06/01/2014 08:30 PM, Dave Chinner wrote:
> I get very worried whenever I see locks inside inode->i_lock. In
> general, i_lock is supposed to be the innermost lock that is taken,
> and there are very few exceptions to that - the inode LRU list is
> one of the few.
I generally trust Hirofumi to
On Mon, Jun 2, 2014 at 12:59 PM, Andy Lutomirski wrote:
> On Mon, Jun 2, 2014 at 12:47 PM, Kees Cook wrote:
>> Hi Andrew,
>>
>> Would you be willing to carry this series? Andy Lutomirski appears
>> happy with it now. (Thanks again for all the feedback Andy!) If so, it
>> has a relatively small
On Mon, Jun 02, 2014 at 01:33:34PM -0400, Waiman Long wrote:
> On 06/02/2014 12:30 PM, Peter Zijlstra wrote:
> >On Mon, Jun 02, 2014 at 06:25:25PM +0200, Peter Zijlstra wrote:
> >>I'm almost inclined to just exclude parisc from using opt spinning.
> >>
> >>That said, this patch still doesn't
On 06/01/2014 08:15 PM, Dave Chinner wrote:
> On Sun, Jun 01, 2014 at 02:41:02PM -0700, I wrote:
>> +
>> +/*
>> + * Add inode to writeback dirty list with current time.
>> + */
>> +void inode_writeback_touch(struct inode *inode)
>> +{
>> +struct backing_dev_info *bdi = inode->i_sb->s_bdi;
>>
On Mon, Jun 2, 2014 at 12:47 PM, Kees Cook wrote:
> Hi Andrew,
>
> Would you be willing to carry this series? Andy Lutomirski appears
> happy with it now. (Thanks again for all the feedback Andy!) If so, it
> has a relatively small merge conflict with the bpf changes living in
> net-next. Would
On Sun, 2014-06-01 at 23:30 +0200, Peter Zijlstra wrote:
> On Sun, Jun 01, 2014 at 04:46:26PM -0400, John David Anglin wrote:
> > On 1-Jun-14, at 3:20 PM, Peter Zijlstra wrote:
> >
> > >>If you write to some variable with ACCESS_ONCE and use cmpxchg or xchg
> > >>at
> > >>the same time, you break
> It seems to me that with this patch, there is no way to expose a
> PMU-without-PEBS to the guest if the host has PEBS.
If you clear the CPUIDs then noone would ilikely access it.
But fair enough, I'll add extra checks for CPUID.
> It would be a bigger concern if we expected virtual PMU
On Monday 02 June 2014 12:26:22 H. Peter Anvin wrote:
> On 06/02/2014 12:19 PM, Arnd Bergmann wrote:
> > On Monday 02 June 2014 13:52:19 Joseph S. Myers wrote:
> >> On Fri, 30 May 2014, Arnd Bergmann wrote:
> >>
> >>> a) is this the right approach in general? The previous discussion
> >>>
On Mon, 2014-06-02 at 12:50 -0700, Paul E. McKenney wrote:
> I sometimes review patches in areas where
> I have no commits.
Lots of people review patches all over the tree.
That doesn't mean they want to be or should be cc'd.
--
To unsubscribe from this list: send the line "unsubscribe
Hey Jonathan,
>
> I think we need the naming to explicitly mention north_magnetic instead
> of just north. Whilst it is obvious what north means when you have north
> true alongside it, it won't be so obvious if one just has the north
> attribute
> to see in a particular driver - if anything I'd
On Mon, 2 Jun 2014 18:08:17 +0100
"Javi Merino" wrote:
> tmon fails to build statically with the following error:
>
> $ make LDFLAGS=-static
> gcc -O1 -Wall -Wshadow -W -Wformat -Wimplicit-function-declaration
> -Wimplicit-int -fstack-protector -D VERSION=\"1.0\" -static tmon.o
> tui.o sysfs.o
Larry Bassel writes:
> Implement and enable context tracking for arm64 (which is
> a prerequisite for FULL_NOHZ support). This patchset
> builds upon earlier work by Kevin Hilman and is based on
> Will Deacon's tree.
>
> Changes v6 to v7:
>
> * Rename parameter of ct_user_exit from restore to
On Mon, Jun 02, 2014 at 12:36:22PM -0700, Joe Perches wrote:
> On Mon, 2014-06-02 at 12:27 -0700, Paul E. McKenney wrote:
> > On Mon, Jun 02, 2014 at 12:11:55PM -0700, j...@joshtriplett.org wrote:
> > >
> > > I'd suggest adding Mathieu Desnoyers, Oleg Nesterov, and Lai Jiangshan
> > > as
Hi Andrew,
Would you be willing to carry this series? Andy Lutomirski appears
happy with it now. (Thanks again for all the feedback Andy!) If so, it
has a relatively small merge conflict with the bpf changes living in
net-next. Would you prefer I rebase against net-next, let sfr handle
it, get
On 02.06.14, 22:36, Stephen Boyd wrote:
> On 05/31, Georgi Djakov wrote:
>> +
>> +static const struct qcom_reset_map gcc_apq8084_resets[] = {
>
>> +[GCC_VENUS0_BCR] = { 0x1020 },
>
>> +[GCC_VPU_BCR] = { 0x1400 },
>
>> +[GCC_MDSS_BCR] = { 0x2300 },
>> +[GCC_AVSYNC_BCR] = { 0x2400
Hi
No, regardless if it is a program that cppcheck or myself with limited
experience of kernel programming is not so easy to figure out.
But then I know that there is nothing wrong in this case, and that is
the main thing :-)
Best regards
Rickard Strandqvist
2014-06-02 2:10 GMT+02:00 Olof
On 05/31, Georgi Djakov wrote:
> This patch adds the necessary node to probe the global clock
> controller on APQ8084 platforms.
>
> Signed-off-by: Georgi Djakov
Reviewed-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
On 05/31, Georgi Djakov wrote:
> Add the compatible string for the APQ8084 global clock controller
> to the clock binding documentation.
>
> Signed-off-by: Georgi Djakov
Reviewed-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux
Adding APM X-Gene SoC Ethernet driver.
v5: Address comments from v4 review
* Documentation: Added phy-handle, reg-names and changed mdio part
* dtb: Added reg-names supplemental property
* changed platform_get_resource to platform_get_resource_byname
* added separate tx/rx set_desc/get_desc
On 05/31, Georgi Djakov wrote:
> Add the necessary DT node to probe the serial driver on
> APQ8084 platforms.
>
> Signed-off-by: Georgi Djakov
Reviewed-by: Stephen Boyd
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
To unsubscribe from
This patch adds a MAINTAINERS entry for APM X-Gene SoC
ethernet driver.
Signed-off-by: Iyappan Subramanian
Signed-off-by: Ravi Patel
Signed-off-by: Keyur Chudgar
---
MAINTAINERS |8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index dd33abf..42ca1b9
This patch adds documentation for APM X-Gene SoC ethernet DTS binding.
Signed-off-by: Iyappan Subramanian
Signed-off-by: Ravi Patel
Signed-off-by: Keyur Chudgar
---
.../devicetree/bindings/net/apm-xgene-enet.txt | 72
1 file changed, 72 insertions(+)
create mode
On 06/02/2014 12:36 PM, Joe Perches wrote:
> On Mon, 2014-06-02 at 12:27 -0700, Paul E. McKenney wrote:
>> On Mon, Jun 02, 2014 at 12:11:55PM -0700, j...@joshtriplett.org wrote:
>>>
>>> I'd suggest adding Mathieu Desnoyers, Oleg Nesterov, and Lai Jiangshan
>>> as reviewers as well, with their
On Mon, 2014-06-02 at 19:12 +0200, Fabian Frederick wrote:
> This patch adds a link to init.h to find accurate initcall function
> to replace obsolete __initcall
maybe s/accurate/appropriate/
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -4443,10 +4443,10 @@ sub process {
This patch adds bindings for APM X-Gene SoC ethernet driver.
Signed-off-by: Iyappan Subramanian
Signed-off-by: Ravi Patel
Signed-off-by: Keyur Chudgar
---
arch/arm64/boot/dts/apm-mustang.dts |4
arch/arm64/boot/dts/apm-storm.dtsi | 30 +++---
2 files
On Mon, 2014-06-02 at 12:27 -0700, Paul E. McKenney wrote:
> On Mon, Jun 02, 2014 at 12:11:55PM -0700, j...@joshtriplett.org wrote:
> >
> > I'd suggest adding Mathieu Desnoyers, Oleg Nesterov, and Lai Jiangshan
> > as reviewers as well, with their consent.
>
> Mathieu, Oleg, Lai, any objections?
On 05/31, Georgi Djakov wrote:
> +
> +static const struct qcom_reset_map gcc_apq8084_resets[] = {
> + [GCC_VENUS0_BCR] = { 0x1020 },
> + [GCC_VPU_BCR] = { 0x1400 },
> + [GCC_MDSS_BCR] = { 0x2300 },
> + [GCC_AVSYNC_BCR] = { 0x2400 },
> + [GCC_OXILI_BCR] = { 0x4020 },
> +
201 - 300 of 1712 matches
Mail list logo
