Direct reclaim iterates over all zones in the zonelist and shrinking them
but this is in conflict with node-based reclaim. In the default case,
only shrink once per node.
Signed-off-by: Mel Gorman
Acked-by: Johannes Weiner
Acked-by: Vlastimil Babka
---
mm/vmscan.c | 20 +++-
1
The balance gap was introduced to apply equal pressure to all zones when
reclaiming for a higher zone. With node-based LRU, the need for the balance
gap is removed and the code is dead so remove it.
[vba...@suse.cz: Also remove KSWAPD_ZONE_BALANCE_GAP_RATIO]
Signed-off-by: Mel Gorman
Acked-by: Vl
This patch makes reclaim decisions on a per-node basis. A reclaimer knows
what zone is required by the allocation request and skips pages from
higher zones. In many cases this will be ok because it's a GFP_HIGHMEM
request of some description. On 64-bit, ZONE_DMA32 requests will cause
some problems
kswapd checks all eligible zones to see if they need balancing even if it was
woken for a lower zone. This made sense when we reclaimed on a per-zone basis
because we wanted to shrink zones fairly so avoid age-inversion problems.
Ideally this is completely unnecessary when reclaiming on a per-node
kswapd goes through some complex steps trying to figure out if it
should stay awake based on the classzone_idx and the requested order.
It is unnecessarily complex and passes in an invalid classzone_idx to
balance_pgdat(). What matters most of all is whether a larger order has
been requsted and wh
Patch "mm: vmscan: Begin reclaiming pages on a per-node basis" started
thinking of reclaim in terms of nodes but kswapd is still zone-centric. This
patch gets rid of many of the node-based versus zone-based decisions.
o A node is considered balanced when any eligible lower zone is balanced.
This
Node-based reclaim requires node-based LRUs and locking. This is a
preparation patch that just moves the lru_lock to the node so later patches
are easier to review. It is a mechanical change but note this patch makes
contention worse because the LRU lock is hotter and direct reclaim and kswapd
can
This moves the LRU lists from the zone to the node and related data
such as counters, tracing, congestion tracking and writeback tracking.
Unfortunately, due to reclaim and compaction retry logic, it is necessary
to account for the number of LRU pages on both zone and node logic. Most
reclaim logic
From: zhong jiang
with great pressure, I run some test cases. As a result, I found
that the THP is not freed, it is detected by check_mm().
BUG: Bad rss-counter state mm:8827edb7 idx:1 val:512
Consider the following race :
CPU0 CPU1
__handle_mm_f
VM statistic counters for reclaim decisions are zone-based. If the kernel
is to reclaim on a per-node basis then we need to track per-node statistics
but there is no infrastructure for that. The most notable change is that
the old node_page_state is renamed to sum_zone_node_page_state. The new
nod
(sorry for resend, the previous attempt didn't go through fully for
some reason)
The bulk of the updates are in response to review from Vlastimil Babka
and received a lot more testing than v6.
Changelog since v6
o Correct reclaim_idx when direct reclaiming for memcg
o Also account LRU pages per z
On Mon, Jun 20, 2016 at 08:41:19PM +0200, Emese Revfy wrote:
> --- /dev/null
> +++ b/scripts/gcc-plugins/latent_entropy_plugin.c
> @@ -0,0 +1,639 @@
> +/*
> + * Copyright 2012-2016 by the PaX Team
> + * Copyright 2016 by Emese Revfy
> + * Licensed under the GPL v2
> + *
> + * Note: the choice of
On Tue, Jun 21, 2016 at 10:41:19AM +0200, Peter Zijlstra wrote:
> On Mon, Jun 20, 2016 at 03:49:34PM +0100, Dietmar Eggemann wrote:
> > On 20/06/16 13:35, Vincent Guittot wrote:
>
> > > It will go through wake_up_new_task and post_init_entity_util_avg
> > > during its fork which is enough to set l
On Tue, Jun 21, 2016 at 04:04:08PM +0200, Peter Zijlstra wrote:
> > I'm not sure who builds the toolchains, but tilepro is in upstream
> > gcc/binutils/etc
> > so should be easy enough to include. There's also a cross-toolchain for
> > x64 I put
> > up a while ago [1] that you could grab if you
Hi Tejun,
On Thu, Jun 16, 2016 at 03:35:04PM -0400, Tejun Heo wrote:
> Hello,
>
> So, the issue of the initial worker not having its affinity set
> correctly wasn't caused by the order of the operations. Reordering
> just made set_cpus_allowed tried one more time late enough so that it
> hides th
On 21/06/2016 15:18, Dmitry Vyukov wrote:
> [] kvm_lapic_set_tpr+0x5e/0xe0 arch/x86/kvm/lapic.c:1648
> [] kvm_set_cr8.part.135+0x2c/0xb0 arch/x86/kvm/x86.c:809
> [] kvm_set_cr8+0x32/0x50 arch/x86/kvm/x86.c:806
> [] vmx_vcpu_reset+0x114/0xb60 arch/x86/kvm/vmx.c:4996
> [] kvm_vcpu_reset+0x410/
On Tue, Jun 21, 2016 at 07:22:38AM -0600, David Ahern wrote:
> On 6/21/16 7:13 AM, Peter Zijlstra wrote:
> >But if you're really annoyed by it all, disable DEBUG_LOCKDEP for a
> >while and rest assured that its not more broken than it was before --
> >just louder :-)
> >
>
> Not really an option i
On Tue, Jun 21, 2016 at 03:18:49PM +0200, Heiko Stübner wrote:
> Am Dienstag, 21. Juni 2016, 14:54:35 schrieb Joerg Roedel:
> > Hi Tomasz,
> >
> > On Tue, Jun 21, 2016 at 09:42:16PM +0900, Tomasz Figa wrote:
> > > In simple words, DRM patches depend on IOMMU patches.
> > >
> > > More precisely: T
Peter/Ingo:
I have this hit many times over the past few weeks, but I do not have a
reliable reproducer to attempt a git bisect. There 2 dumps below I hit
last night within a few minutes of each other (reboot in between). First
dump is for ipv4 (first login to VM after boot) and second dump is
On Mon, Jun 20, 2016 at 01:05:56PM -0700, Davidlohr Bueso wrote:
> Now that we have fetch_inc() we can stop using inc_return() - 1.
>
> These are very similar to the existing OP-RETURN primitives we already
> have, except they return the value of the atomic variable _before_
> modification.
>
> C
Hi Paolo,
2016-06-21 18:24 GMT+08:00 Wanpeng Li :
> 2016-06-21 18:10 GMT+08:00 Paolo Bonzini :
>>
>>
>> On 21/06/2016 08:08, Wanpeng Li wrote:
>>> Cc KVM ML, Paolo, Radim,
> FYI, raw QEMU command line is:
>
> qemu-system-x86_64 -enable-kvm -cpu SandyBridge -kernel
> /pkg/li
On Tue, Jun 21, 2016 at 03:08:52PM +0200, Oliver Neukum wrote:
> On Thu, 2016-05-19 at 15:44 +0300, Heikki Krogerus wrote:
> > The purpose of this class is to provide unified interface for user
> > space to get the status and basic information about USB Type-C
> > Connectors in the system, control
On 21/06/16 07:52, Horng-Shyang Liao wrote:
On Fri, 2016-06-17 at 17:57 +0200, Matthias Brugger wrote:
On 17/06/16 10:28, Horng-Shyang Liao wrote:
Hi Matthias,
On Tue, 2016-06-14 at 20:07 +0800, Horng-Shyang Liao wrote:
Hi Matthias,
On Tue, 2016-06-14 at 12:17 +0200, Matthias Brugger wrot
On Sat, Jun 18, 2016 at 07:15:43PM -0700, Stefan Agner wrote:
> Commit 7566e247672d ("drm/fsl-dcu: handle initialization errors properly")
> introduced error handling during initialization, but with a wrong cleanup
> order.
>
> Replace the error handling with the generic cleanup function
> drm_mod
On 6/14/2016 5:15 PM, Yakir Yang wrote:
RK3399 and RK3288 shared the same eDP IP controller, only some light
difference with VOP configure and GRF configure.
Also same misc fix to analogix_dp driver:
- Hotplug invalid which report by Dan Carpenter
- Make panel detect to an optional action
- co
On Mon, Jun 13, 2016 at 05:06:40PM -0500, Suravee Suthikulpanit wrote:
> Suravee Suthikulpanit (10):
> iommu/amd: Detect and enable guest vAPIC support
> iommu/amd: Add support for 128-bit IRTE
> iommu/amd: Detect and initialize guest vAPIC log
> iommu/amd: Adding GALOG interrupt handler
>
Am Dienstag, 21. Juni 2016, 14:54:35 schrieb Joerg Roedel:
> Hi Tomasz,
>
> On Tue, Jun 21, 2016 at 09:42:16PM +0900, Tomasz Figa wrote:
> > In simple words, DRM patches depend on IOMMU patches.
> >
> > More precisely: The IOMMU patches alone are supposed to not break
> > anything. Same goes for
The current ipq4019 clock driver does not have the node for
PCNOC so this patch adds and registers the PCNOC clock nodes.
Signed-off-by: Abhishek Sahu
---
drivers/clk/qcom/gcc-ipq4019.c | 37
include/dt-bindings/clock/qcom,gcc-ipq4019.h | 1 +
2 files
The current ipq4019 clock driver does not have support for all
the frequency supported by APPS CPU. APPS CPU frequency is
provided with APSS CPU PLL divider which divides down the VCO
frequency. This divider is nonlinear and specific to IPQ4019
so the standard divider code cannot be used for this.
The current ipq4019 clock driver registered the PLL clocks and
dividers as fixed clock. These fixed clock needs to be removed
from driver probe function and same need to be registered with
clock framework. These PLL clocks should be programmed only
once and the same are being programmed already by
The current driver code gives the crash or gets hang while switching
the CPU frequency some time. The APSS CPU Clock divider is not glitch
free so it the APPS clock need to be switched for stable clock during
the change.
This patch adds the frequency change notifier for APSS CPU clock. It
changes
These patches are related to Qualcomm IPQ4019 GCC (Global Clock
Controller) driver code mainly adding the nodes for clock marked
as fixed in current IPQ4019 clock driver and support for multiple
CPU frequencies.
[V2]
1. Removed the fixed clock references and add the same as clock nodes
with
The APPS CPU clock does not contain all the frequencies in its
frequency table so this patch adds the same.
Signed-off-by: Abhishek Sahu
---
drivers/clk/qcom/gcc-ipq4019.c | 20 +++-
1 file changed, 15 insertions(+), 5 deletions(-)
diff --git a/drivers/clk/qcom/gcc-ipq4019.c b/d
On 16.06.2016 15:57, Konstantin Khlebnikov wrote:
Hierarchy could be already throttled at this point. Throttled next
buddy could trigger null pointer dereference in pick_next_task_fair().
trivial debug in set_next_buddy
@@ -4755,8 +4758,11 @@ static void set_next_buddy(struct sched_entity *se)
> The fix in the DKMS package you referenced was not written by
> Canonical but by ALPS, as it came from them I think it is reasonable
> they send it to upstream, isn't it? As you can see the patch is non-trivial.
You published it on to milliosn of users, you'd think also mentioning its
existence
On Mon, Jun 20 2016 at 6:22pm -0400,
Mike Snitzer wrote:
> On Mon, Jun 20 2016 at 5:28pm -0400,
> Kani, Toshimitsu wrote:
>
> >
> > Hi Mike,
> >
> > Can you fold the following patch to the dm-linear patch?
> >
> > Thanks,
> > -Tsohi
> >
> > --
> > Subject: [PATCH] dm-linear: Fix parti
Hi!
> 6. You have a significant lack of data regarding embedded systems, which is
> one of the two biggest segments of Linux's market share. You list no
> results for any pre-ARMv6 systems (Linux still runs on and is regularly used
> on ARMv4 CPU's, and it's worth also pointing out that the value
On Sat, Jun 18, 2016 at 06:09:26PM -0700, Andrey Smirnov wrote:
> Andrey Smirnov (5):
> i.MX: system.c: Convert goto to if statement
> i.MX: system.c: Remove redundant errata 752271 code
> i.MX: system.c: Replace magic numbers
> i.MX: system.c: Tweak prefetch settings for performance
> i.
On 16.06.2016 15:57, Konstantin Khlebnikov wrote:
Cgroup created inside throttled group must inherit current throttle_count.
Broken throttle_count allows to nominate throttled entries as a next buddy,
later this leads to null pointer dereference in pick_next_task_fair().
example of kernel oops
On Tue, Jun 21, 2016 at 07:03:58AM -0600, David Ahern wrote:
> Peter/Ingo:
>
> I have this hit many times over the past few weeks, but I do not have a
> reliable reproducer to attempt a git bisect. There 2 dumps below I hit last
> night within a few minutes of each other (reboot in between). First
On 6/21/2016 8:47 AM, Wim Osterholt wrote:
>> Can you try the following and see if it makes any difference?
>>
>>
>> --- a/drivers/acpi/pci_link.c
>> +++ b/drivers/acpi/pci_link.c
>> @@ -500,7 +500,7 @@ static int acpi_irq_get_penalty(int irq)
>> int penalty = 0;
>>
>> if (irq < ACP
On Tue, Jun 21, 2016 at 10:44:00AM +0900, Masahiro Yamada wrote:
> I fixed boot image dependencies for arch/arm in commit 3939f3345050
> ("ARM: 8418/1: add boot image dependencies to not generate invalid
> images").
>
> I see a similar problem for arch/arm64; "make -jN Image Image.gz"
> would some
On 21 June 2016 at 15:17, Peter Zijlstra wrote:
> On Tue, Jun 21, 2016 at 10:41:19AM +0200, Peter Zijlstra wrote:
>> On Mon, Jun 20, 2016 at 03:49:34PM +0100, Dietmar Eggemann wrote:
>> > On 20/06/16 13:35, Vincent Guittot wrote:
>>
>> > > It will go through wake_up_new_task and post_init_entity_u
On Tue, Jun 21, 2016 at 11:32:17AM +0100, Catalin Marinas wrote:
> On Tue, Jun 21, 2016 at 10:44:00AM +0900, Masahiro Yamada wrote:
> > I fixed boot image dependencies for arch/arm in commit 3939f3345050
> > ("ARM: 8418/1: add boot image dependencies to not generate invalid
> > images").
> >
> > I
On Thu, 2016-05-19 at 15:44 +0300, Heikki Krogerus wrote:
> The purpose of this class is to provide unified interface for user
> space to get the status and basic information about USB Type-C
> Connectors in the system, control data role swapping, and when USB PD
> is available, also power role swa
On Mon, Jun 20, 2016 at 09:50:49AM -0500, ttha...@opensource.altera.com wrote:
> From: Thor Thayer
>
> Add the device tree bindings needed to support the Altera Ethernet
> FIFO buffers on the Arria10 chip.
>
> Signed-off-by: Thor Thayer
> ---
> v2 No Change
> v3 Change to common compatible st
Hi Jan,
> On Jun 21, 2016, at 16:12 , Jan Kiszka wrote:
>
> On 2016-06-21 13:59, Jan Kiszka wrote:
>> On 2016-06-21 13:45, Pantelis Antoniou wrote:
>>> Hi Jan,
>>>
On Jun 21, 2016, at 14:43 , Jan Kiszka wrote:
On 2016-06-21 13:35, Pantelis Antoniou wrote:
> Hi Jan,
>
>
On Mon, Jun 20, 2016 at 06:20:05PM +0200, M'boumba Cedric Madianga wrote:
> This patch adds documentation of device tree bindings for the STM32 I2C
> controller.
>
> Signed-off-by: M'boumba Cedric Madianga
> ---
> .../devicetree/bindings/i2c/i2c-stm32.txt | 33
> ++
On Mon, Jun 20, 2016 at 10:33:59AM +0300, Yigal Korman wrote:
> Before this patch, passing a range that is beyond the physical memory
> range will succeed, the user will see a /dev/pmem0 and will be able to
> access it. Reads will always return 0 and writes will be silently
> ignored.
>
> I've got
With the inclusion of atomic FETCH-OP variants, many places in the
kernel can make use of atomic_fetch_$op() to avoid the hacky callers
that need to compute the value/state _before_ the operation. Peter
laid out the machinery but we are still missing the simpler dec,inc
calls (which future patches
On Tue, Jun 21, 2016 at 02:02:44AM -0700, Duc Dang wrote:
> Hi Rob,
>
> I got warning on unit_address_vs_reg similar to this
> https://lkml.org/lkml/2016/3/7/43 when using v4.7-rc2 dtc to build dtb
> for X-Gene Mustang:
>
> dhdang@xgene-next=>./scripts/dtc/dtc -O dtb -R 16 -o mustang.dtb
> arch/a
On 2016-06-21 13:59, Jan Kiszka wrote:
> On 2016-06-21 13:45, Pantelis Antoniou wrote:
>> Hi Jan,
>>
>>> On Jun 21, 2016, at 14:43 , Jan Kiszka wrote:
>>>
>>> On 2016-06-21 13:35, Pantelis Antoniou wrote:
Hi Jan,
> On Jun 21, 2016, at 14:22 , Jan Kiszka wrote:
>
> On 2016-06
On Wed, May 11, 2016 at 10:15:20PM +0200, Arnd Bergmann wrote:
> On Wednesday 11 May 2016 22:11:07 Arnd Bergmann wrote:
> > We get a harmless build warning when trying to use the mediatek
> > DRM driver with IOMMU support disabled:
> >
> > warning: (DRM_MEDIATEK) selects IOMMU_DMA which has unmet
On Út, 2016-06-21 at 09:05 -0400, Austin S. Hemmelgarn wrote:
> On 2016-06-20 14:32, Stephan Mueller wrote:
> >
> > [1] http://www.chronox.de/jent/doc/CPU-Jitter-NPTRNG.pdf
> Specific things I notice about this:
> 1. QEMU systems are reporting higher values than almost anything
> else
> with the
Hi,
> > + mmiowb();
> > +}
>
> What is the barrier for? Same question for all the other instances
No idea. Removed them all, seems to work fine still.
Guess writel() & friends have the needed barriers on arm?
> > +
> > +static void bcm2835_sdhost_reset(struct mmc_host *mmc)
> > +{
> > +
On Fri, 17 Jun 2016 10:38:27 +0800
Peter Pan wrote:
> >>
> >> Again, I'm sorry that you had to be the one supporting this transition,
> >> but I don't want to introduce any more quick-and-dirty hacks that we'll
> >> have to maintain until someone decides to tackle the real problem.
> >
> > No s
On Tue 21-06-16 13:46:43, Michal Hocko wrote:
> On Tue 21-06-16 20:03:17, Tetsuo Handa wrote:
> > Michal Hocko wrote:
> > > On Mon 13-06-16 13:19:43, Michal Hocko wrote:
> > > [...]
> > > > I am trying to remember why we are disabling oom killer before kernel
> > > > threads are frozen but not real
On 21/06/2016 15:24, Christian Borntraeger wrote:
> Series looks sane and does work on s390.
> It has a minor conflict with my vsie pull request (so either add vsie.c
> to this patch set or fixup my pull request in the merge commit to replace
> kvm_guest_exit/enter with the new functions.
It sho
Hello.
On 6/21/2016 6:56 AM, Yisen Zhuang wrote:
From: Jun He
When hns_nic_poll_rx_skb alloc skb fail, it will break receive cycle and
read new fbd_num to start new receive cycle. It recomputes cycle num is
fbd_num minus clean_count, actually this cycle num is too big because
it drop out rece
Hello,
The following program triggers GPF in kvm_lapic_set_tpr:
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: [#1] SMP DEBUG_PAGEALLOC KASAN
Modules linked in:
CPU: 0 PID: 7683 Comm: syz-executor Not tainted 4.
On 06/21/2016 06:08 AM, Oliver Neukum wrote:
On Thu, 2016-05-19 at 15:44 +0300, Heikki Krogerus wrote:
The purpose of this class is to provide unified interface for user
space to get the status and basic information about USB Type-C
Connectors in the system, control data role swapping, and when
On 06/20/2016 04:58 PM, Paolo Bonzini wrote:
> The first patches are the two optimizations I posted on May 30th
> for the system call entry/exit code. The only change is in the
> function names, which use the user_{enter,exit}_irqoff favored
> by Andy and Ingo. The first patch matches what commit
This fixes up a line over 80 characters issues found by
the checkpatch.pl tool.
Signed-off-by: Ravishankar Karkala Mallikarjunayya
---
Change log v1->v2
- No Change
---
drivers/staging/comedi/drivers/s626.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/sta
Hi Peter,
I have an update for this performance issue. I have tested several
kernels, I'm not at the parent of
2159197d6677 sched/core: Enable increased load resolution on 64-bit kernels
and I still see the performance regression for multithreaded workloads.
There are only 27 commits remainin
Hello,
The following program triggers use-after-free in kvm_irqfd_release:
BUG: KASAN: use-after-free in do_raw_spin_lock+0x281/0x2b0 at addr
880060888c64
Read of size 4 by task a.out/7084
page:ea0001822200 count:0 mapcount:-127 mapping: (null) index:0x0
flags: 0x4fffe00(
Am Dienstag, 21. Juni 2016, 09:05:55 schrieb Austin S. Hemmelgarn:
Hi Austin,
> On 2016-06-20 14:32, Stephan Mueller wrote:
> > Am Montag, 20. Juni 2016, 13:07:32 schrieb Austin S. Hemmelgarn:
> >
> > Hi Austin,
> >
> >> On 2016-06-18 12:31, Stephan Mueller wrote:
> >>> Am Samstag, 18. Juni 201
> Finally we got a Datasheet which we can release and share with you.
> Thanks for the feedback, we tried to integrate most of the feedback in
> the driver. Some proprietary API is still present as all features of the
> chip should be reachable. If there are any features we could use from
> th
On 6/21/16 7:13 AM, Peter Zijlstra wrote:
Plz as to not wrap dmesg output when pasting
not wrapped on my end -- the copy in Send folder in or the ouptut in
your response.
IPv4 one:
[ 189.171084] ==
[ 189.171555] [chain_key collision ]
[ 189.172020] 4.7.0-rc2+ #31
On Tue, Jun 21, 2016 at 03:35:00PM +0300, Felipe Balbi wrote:
>
> Hi,
>
> Peter Chen writes:
> >> >> >> >>> + * @otg_dev: OTG controller device, if needs to be used with
> >> >> >> >>> OTG core.
> >> >> >> >>
> >> >> >> >> do you really know of any platform which has a separate OTG
> >> >> >>
On 19 May 2016 at 10:47, Chaotian Jing wrote:
> with CONFIG_HZ=100, the precision of jiffies is 10ms, and the
> generic_cmd6_time of some card is also 10ms. then, may be current
> time is only 5ms, but already timed out caused by jiffies precision.
>
> Signed-off-by: Chaotian Jing
Thanks, applie
On 19 May 2016 at 10:47, Chaotian Jing wrote:
> some MMC host do not support MMC_CAP_WAIT_WHILE_BUSY but provides
> ops->card_busy(), So, add this method to check card status after
> switch command.
>
> Signed-off-by: Chaotian Jing
Thanks, applied for next! (With some minor updates to the change
Hi,
Felipe Balbi writes:
> Can't you just tie a charger to a UDC and avoid the charger class
> completely?
Yeah, I also hope so. But we really want something to manage the
charger devices, do you have any good suggestion to avoid the 'class'
bu
On 19 May 2016 at 10:47, Chaotian Jing wrote:
> Per JEDEC spec, it is not recommended to use CMD13 to get card status
> after speed mode switch. below are two reason about this:
> 1. CMD13 cannot be guaranteed due to the asynchronous operation.
> Therefore it is not recommended to use CMD13 to che
On 06/21/2016 01:48 PM, Andrew F. Davis wrote:
On 06/21/2016 02:09 AM, Jacek Anaszewski wrote:
Hi Andrew,
This patch doesn't apply, please rebase onto recent LED tree.
On 06/21/2016 12:13 AM, Andrew F. Davis wrote:
Some systems use 'gpio_led_register_device' to make an in-memory copy of
their
On Mon, Jun 20, 2016 at 01:25:46PM -0700, Megha Dey wrote:
>
> - desc->tfm = child;
> - desc->flags = CRYPTO_TFM_REQ_MAY_SLEEP; /* check this again */
> + ahash_request_set_tfm(desc, child);
> + ahash_request_set_callback(desc, CRYPTO_TFM_REQ_MAY_SLEEP, NULL, NULL);
The callback f
On Tue, Jun 21, 2016 at 09:43:53AM +0200, Jan Kara wrote:
> On Mon 20-06-16 22:53:26, Dan Carpenter wrote:
> > On Mon, Jun 20, 2016 at 06:02:04PM +0200, Jan Kara wrote:
> > > On Thu 16-06-16 10:07:09, Dan Carpenter wrote:
> > > > My static checker complains that this can underflow if arg is negativ
On 2016-06-20 14:32, Stephan Mueller wrote:
Am Montag, 20. Juni 2016, 13:07:32 schrieb Austin S. Hemmelgarn:
Hi Austin,
On 2016-06-18 12:31, Stephan Mueller wrote:
Am Samstag, 18. Juni 2016, 10:44:08 schrieb Theodore Ts'o:
Hi Theodore,
At the end of the day, with these devices you really b
On 2016/6/21 19:28, Leon Romanovsky wrote:
On Tue, Jun 21, 2016 at 06:50:51PM +0800, Wei Hu (Xavier) wrote:
On 2016/6/20 21:33, Leon Romanovsky wrote:
On Thu, Jun 16, 2016 at 10:35:14PM +0800, Lijun Ou wrote:
This patch added the operation for cmd, and added some functions
for initializing
On Mon, Jun 20, 2016 at 7:40 PM, Tejun Heo wrote:
> Hello,
>
> On Mon, Jun 20, 2016 at 03:38:41PM +0200, Dmitry Vyukov wrote:
>> > Sorry for the late reply but now when thinking about the patch I don't
>> > think it is quite right. Writeback can happen from other contexts than just
>> > the worker
On 21 June 2016 at 14:47, Peter Zijlstra wrote:
> On Tue, Jun 21, 2016 at 02:36:46PM +0200, Vincent Guittot wrote:
>> On 21 June 2016 at 13:43, Peter Zijlstra wrote:
>> > On Mon, Jun 20, 2016 at 11:23:39AM +0200, Vincent Guittot wrote:
>> >
>> >> Don't we have to do a complete attach with attach_
Hi Tomasz,
On Tue, Jun 21, 2016 at 09:42:16PM +0900, Tomasz Figa wrote:
> In simple words, DRM patches depend on IOMMU patches.
>
> More precisely: The IOMMU patches alone are supposed to not break
> anything. Same goes for the first DRM patch (7/8). Only second DRM
> patch (8/8) depends on chang
Hi,
Baolin Wang writes:
Can't you just tie a charger to a UDC and avoid the charger class
completely?
>>>
>>> Yeah, I also hope so. But we really want something to manage the
>>> charger devices, do you have any good suggestion to avoid the 'class'
>>> but also
On Tue, Jun 21, 2016 at 03:43:02PM +0900, Joonsoo Kim wrote:
> On Mon, Jun 20, 2016 at 06:12:54AM -0700, Paul E. McKenney wrote:
> > On Mon, Jun 20, 2016 at 03:39:43PM +0900, Joonsoo Kim wrote:
> > > CCing Paul to ask some question.
> > >
> > > On Wed, Jun 15, 2016 at 10:39:47AM +0200, Geert Uytte
Hello guys.
First of all - thank you for your great work in ftrace, and in general in the
Linux tracing infrastructure. I am a newbie: so I am not able to use it at it's
full power, still I find it's capabilities impressive.
I am asking for help, since I am encountering some problems in using
The 100c08 scratch page is mapped using dma_map_page() before the TTM
layer has had a chance to set the DMA mask. This means we are still
running with the default of 32 when this code executes, and this causes
problems for platforms with no memory below 4 GB (such as AMD Seattle)
So move the dma_m
On 21 June 2016 at 20:36, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>>> Baolin Wang writes:
> Baolin Wang writes:
>>> Can't you just tie a charger to a UDC and avoid the charger class
>>> completely?
>>
>> Yeah, I also hope so. But we really want something to manag
> Can you try the following and see if it makes any difference?
>
>
> --- a/drivers/acpi/pci_link.c
> +++ b/drivers/acpi/pci_link.c
> @@ -500,7 +500,7 @@ static int acpi_irq_get_penalty(int irq)
> int penalty = 0;
>
> if (irq < ACPI_MAX_ISA_IRQS)
> - penalty += acpi
On 21/06/16 13:01, Jiancheng Xue wrote:
>
>
> On 2016/6/21 19:30, Jiancheng Xue wrote:
>> Hi Marc，
>>
>> On 2016/6/21 18:36, Marc Zyngier wrote:
>>> On 21/06/16 10:26, Jiancheng Xue wrote:
This patch fixes the compiling error caused when
config HISILICON_IRQ_MBIGEN is selected but
Hi,
Baolin Wang writes:
>> Baolin Wang writes:
Baolin Wang writes:
>> Can't you just tie a charger to a UDC and avoid the charger class
>> completely?
>
> Yeah, I also hope so. But we really want something to manage the
> charger devices, do you have any good suggestio
On Tue, Jun 21, 2016 at 08:00:05AM +, Vineet Gupta wrote:
> Hi Heiko,
>
> On Tuesday 21 June 2016 01:10 PM, Heiko Carstens wrote:
> > commit b21e91c305bc "scripts/bloat-o-meter: print percent change"
> > introduced an additional line to the output of the bloat-a-meter
> > script which shows th
On Tue, Jun 21, 2016 at 10:41:19AM +0200, Peter Zijlstra wrote:
> On Mon, Jun 20, 2016 at 03:49:34PM +0100, Dietmar Eggemann wrote:
> > On 20/06/16 13:35, Vincent Guittot wrote:
>
> > > It will go through wake_up_new_task and post_init_entity_util_avg
> > > during its fork which is enough to set l
On 21/06/16 12:03, Sebastian Frias wrote:
> Hi Marc,
>
> On 06/21/2016 12:18 PM, Marc Zyngier wrote:
>>> Since irq-tango_v2.c is similar to irq-crossbar.c from TI (since it
>>> is based on it), I was wondering what is the policy or recommendation
>>> in such cases?
>>> Should I attempt to merge th
On Tue, Jun 21, 2016 at 02:36:46PM +0200, Vincent Guittot wrote:
> On 21 June 2016 at 13:43, Peter Zijlstra wrote:
> > On Mon, Jun 20, 2016 at 11:23:39AM +0200, Vincent Guittot wrote:
> >
> >> Don't we have to do a complete attach with attach_task_cfs_rq instead
> >> of just the load_avg ? to set
On Mon, Jun 06, 2016 at 12:57:23PM +0900, Magnus Damm wrote:
> Developed on top of next-20160602 and:
> [PATCH v3 00/06] iommu/ipmmu-vmsa: IPMMU multi-arch update V3
>
> drivers/iommu/ipmmu-vmsa.c | 318
> +---
> 1 file changed, 269 insertions(+), 49 de
Hi Dmitry,
-Original Message-
From: Dmitry Torokhov [mailto:dmitry.torok...@gmail.com]
Sent: Tuesday, June 21, 2016 1:43 AM
To: Chris Chiu; kt.l...@emc.com.tw
Cc: Charlie Mooney; Michele Curti; Krzysztof Kozlowski; Benson Leung;
linux-in...@vger.kernel.org; linux-kernel@vger.kernel.org;
l
On Tue, Jun 21, 2016 at 08:08:29AM -0400, Chris Metcalf wrote:
>
> On inspection, I note that the arch/tile/include/atomic_32.h header has
>
> ATOMIC64_OP(and)
> ATOMIC64_OP(or)
> ATOMIC64_OP(xor)
>
> but these should be ATOMIC64_OPS, plural.
Bugger, I'll go fix. Clearly nobody has tilepro tool
Hi Joerg,
On Tue, Jun 21, 2016 at 6:17 PM, Joerg Roedel wrote:
>
> On Tue, Jun 21, 2016 at 01:34:33PM +0900, Tomasz Figa wrote:
> > This series intends mostly to enable support for ARM64 architecture
> > in the rockchip-iommu driver. On the way to do so, some bugs are also
> > fixed.
> >
> > The
Hi Andy,
On 06/21/2016 12:39 AM, Andy Lutomirski wrote:
> Suppose a 64-bit task A traces a 32-bit task B.
I gave your x86/ptrace branch a try:
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/log/?h=x86/ptrace
(this looks to be the same patch set.)
Unfortunately, with gdb git maste
Hi,
[auto build test ERROR on tip/perf/core]
[also build test ERROR on v4.7-rc4 next-20160621]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Chunyu-Hu/tracing-Fix-oops-caused-by-graph-notrace
On 21 June 2016 at 13:43, Peter Zijlstra wrote:
> On Mon, Jun 20, 2016 at 11:23:39AM +0200, Vincent Guittot wrote:
>
>> Don't we have to do a complete attach with attach_task_cfs_rq instead
>> of just the load_avg ? to set also depth ?
>
> Hmm, yes, your sched_set_group() change seems to have mung
701 - 800 of 1171 matches
Mail list logo
