Currently only test for local libunwind. We should check all supported
platforms so we can use them to parse perf.data with callchain info on
different machines.
Signed-off-by: He Kuang
---
tools/build/Makefile.feature | 4
tools/build/feature/Makefile
From: Dom Cote
Change the read_u16 function so it accepts both 'str' and 'byte'
as type for the arguments.
When calling read_memory() from gdb API, depending on if
it was built with 2.7 or 3.X, the format used to return the
data will differ ( 'str' for 2.7, and 'byte'
From: Kieran Bingham
The recent fixes to lx-dmesg, now allow the command to print
successfully on Python3, however the python interpreter wraps the bytes
for each line with a b'' marker.
To remove this, we need to decode the line, where .decode() will default
to 'UTF-8'
From: Kieran Bingham
Walk the VFS entries, pre-pending the iname strings to generate a full
VFS path name from a dentry.
Signed-off-by: Kieran Bingham
Signed-off-by: Jan Kiszka
---
scripts/gdb/linux/utils.py | 8
Dear Felipe & Doug,
Thanks for your proposal. It's a good idea to sort the list.
I'll fix it next patch version.
On 05/10/2016 03:14 PM, Felipe Balbi wrote:
Hi,
Doug Anderson writes:
William,
On Mon, May 9, 2016 at 4:46 AM, William Wu
On Tue, 2016-05-10 at 07:26 +0800, Yuyang Du wrote:
> By cpu reservation, you mean the various averages in select_task_rq_fair?
> It does seem a lot of cleanup should be done.
Nah, I meant claiming an idle cpu with cmpxchg(). It's mostly the
average load business that leads to premature
The retry loop in __alloc_pages_slowpath is supposed to keep trying reclaim
and compaction (and OOM), until either the allocation succeeds, or returns
with failure. Success here is more probable when reclaim precedes compaction,
as certain watermarks have to be met for compaction to even try, and
This is mostly a followup to Michal's oom detection rework, which highlighted
the need for direct compaction to provide better feedback in reclaim/compaction
loop, so that it can reliably recognize when compaction cannot make further
progress, and allocation should invoke OOM killer or fail. We've
From: Kieran Bingham
Linux makes use of the Radix Tree data structure to store pointers indexed
by integer values. This structure is utilised across many structures in
the kernel including the IRQ descriptor tables, and several filesystems.
This module provides a
This takes the MODULE_REF_BASE into account.
Signed-off-by: Jan Kiszka
---
scripts/gdb/linux/modules.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/gdb/linux/modules.py b/scripts/gdb/linux/modules.py
index 0a35d6d..38f5d17 100644
---
We won't see more than 2 billion CPUs any time soon, and having cpu_list
return long makes the output of lx-cpus a bit ugly.
Signed-off-by: Jan Kiszka
---
scripts/gdb/linux/cpus.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
2016-05-10 16:09 GMT+09:00 Vlastimil Babka :
> On 05/10/2016 08:41 AM, Joonsoo Kim wrote:
>>
>> You applied band-aid for CONFIG_COMPACTION and fixed some reported
>> problem but it is also fragile. Assume almost pageblock's skipbit are
>> set. In this case, compaction easily
We intended to test "usb2->phy" here instead of "dev".
Fixes: d3feb4067335 ('phy: bcm-ns-usb2: new driver for USB 2.0 PHY on
Northstar')
Signed-off-by: Dan Carpenter
diff --git a/drivers/phy/phy-bcm-ns-usb2.c b/drivers/phy/phy-bcm-ns-usb2.c
index 95ab6b2..58dff80
On Thu, Apr 21, 2016 at 02:04:45PM +0100, Paul Burton wrote:
> The conditions for branching when emulating the BC1EQZ & BC1NEZ
> instructions were backwards, leading to each of those instructions being
> treated as the other. Fix this by reversing the conditions, and clear up
> the code a little
Hi,
Roger Quadros writes:
> On 10/05/16 06:14, Peter Chen wrote:
>> On Mon, May 09, 2016 at 12:45:38PM +0300, Roger Quadros wrote:
>>> On 06/05/16 12:41, Peter Chen wrote:
On Mon, May 02, 2016 at 03:18:46PM +0300, Roger Quadros wrote:
> The OTG core will use struct
Dear Felipe and Brian,
On 05/10/2016 03:15 PM, Felipe Balbi wrote:
Hi,
Brian Norris writes:
Hi William,
Did you leave off linux-rockc...@lists.infradead.org intentionally? IMO,
it's nice to have that list in CC, so interested parties can follow your
work, even if
Hi William,
William Wu writes:
> Dear Felipe & Doug,
> Thanks for your proposal. It's a good idea to sort the list.
> I'll fix it next patch version.
cool, thanks.
ps: top-posting is frowned upon here. Please avoid it ;-)
--
balbi
On 10/05/16 10:40, He Kuang wrote:
> 32-bit programs can be run on 64-bit machines, so we should choose
> unwind methods according to 'thread->map' instead of the host
> architecture.
>
> This patch adds methods to test whether a dso is 64-bit or 32-bit by
> the class info in elf.
What about
On Tue, May 10, 2016 at 10:11:50AM +0200, Jeremy Allison wrote:
> +1 from me. This is something that many vendors need
> and have needed for a very long time. Getting this
> in will allow *large* amounts of existing storage to
> be migrated to Linux.
ZFS has NFSv4 richacls, and people seem to
On 10-05-16, 10:17, Geert Uytterhoeven wrote:
> Hi Viresh,
>
> On Tue, May 10, 2016 at 7:07 AM, Viresh Kumar wrote:
> > On 10-05-16, 11:57, Khiem Nguyen wrote:
> >> After the commit "a399dc9fc50 cpufreq: shmobile: Use generic platdev
> >> driver", will use
Some resources, such as IPPC register etc, shared with device
driver are moved into common glue layer when xHCI driver is the
host side of dual-role mode and they should be changed as optional
properties if they are required ones before. For clarity, add
a new part of binding to support host side
Sorry too late reply.
On Mon, 02 May 2016 05:48:28 +0900,
Geert Uytterhoeven wrote:
>
> Hi Sato-san,
>
> On Sun, May 1, 2016 at 7:08 AM, Yoshinori Sato
> wrote:
> > Signed-off-by: Yoshinori Sato
> > ---
> >
Dear Felipe,
On 05/10/2016 04:11 PM, Felipe Balbi wrote:
Hi William,
William Wu writes:
Dear Felipe & Doug,
Thanks for your proposal. It's a good idea to sort the list.
I'll fix it next patch version.
cool, thanks.
ps: top-posting is frowned
add a DT binding doc for MediaTek USB3 DRD driver
Signed-off-by: Chunfeng Yun
---
Documentation/devicetree/bindings/usb/mtu3.txt | 86
1 file changed, 86 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/mtu3.txt
diff
Hi Al,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-next
This fixes two issues with overlayfs.
Thanks,
Miklos
---
Miklos Szeredi (3):
vfs: rename: check backing inode being equal
vfs: export lookup_hash() to modules
ovl: ignore
On Tuesday 10 May 2016 15:42:07 Zhangjian wrote:
> On 2016/5/6 20:37, Yury Norov wrote:
> > On Fri, May 06, 2016 at 08:16:48PM +0800, Zhangjian (Bamvor) wrote:
> >
> > AFAIR, here we don't shift offset, as it's 64-bit both in user-
> > and kernel-space,
> In your ilp32-2.22 branch, you wrapper
On 2016/5/9 19:56, Adrian Hunter wrote:
On 29/04/16 05:47, Shawn Lin wrote:
Controllers use data strobe line to latch data from devices
under hs400 mode, but not for cmd line. So since emmc 5.1, JEDEC
introduces enhanced strobe mode for latching cmd response from
emmc devices to host
Commit-ID: 434a6c9f90f7ab5ade619455df01ef5ebea533ee
Gitweb: http://git.kernel.org/tip/434a6c9f90f7ab5ade619455df01ef5ebea533ee
Author: Kees Cook
AuthorDate: Mon, 9 May 2016 13:22:04 -0700
Committer: Ingo Molnar
CommitDate: Tue, 10 May 2016
Why not. See patch as attachment.
Thanks,
Jérémy
>From 8a9b07e2d7242fa8a36157f1025202a96c3c7c9a Mon Sep 17 00:00:00 2001
From: Jeremy Compostella
Date: Tue, 10 May 2016 10:34:21 +0200
Subject: [PATCH] efibc: report the EFI variable name in the error messages
Commit-ID: c401cf1524153f9c2ede7ab8ece403513925770a
Gitweb: http://git.kernel.org/tip/c401cf1524153f9c2ede7ab8ece403513925770a
Author: Baoquan He
AuthorDate: Mon, 9 May 2016 13:22:06 -0700
Committer: Ingo Molnar
CommitDate: Tue, 10 May 2016 10:12:04
Commit-ID: cb18ef0da259db611fbf52806592fde5f469ae67
Gitweb: http://git.kernel.org/tip/cb18ef0da259db611fbf52806592fde5f469ae67
Author: Kees Cook
AuthorDate: Mon, 9 May 2016 13:22:05 -0700
Committer: Ingo Molnar
CommitDate: Tue, 10 May 2016
On Thu 05-05-16 17:19:52, Andrew Morton wrote:
[...]
> A git tree which contains the memory management portion of this tree is
> maintained at git://git.kernel.org/pub/scm/linux/kernel/git/mhocko/mm.git
> by Michal Hocko. It contains the patches which are between the
> "#NEXT_PATCHES_START mm"
On Tue, May 10, 2016 at 05:25:36PM +0900, Yoshinori Sato wrote:
> On Wed, 04 May 2016 12:10:05 +0900,
> Rich Felker wrote:
> >
> > On Sun, May 01, 2016 at 02:08:29PM +0900, Yoshinori Sato wrote:
> > > Changes bellow
> > > - FDT setup timing fix.
> > > - chosen/bootargs support.
> > > - zImage
On Tue, May 10, 2016 at 09:07:49AM -0700, Andy Lutomirski wrote:
> Hi all-
>
> I'm trying to get rid of x86's dynamic TASK_SIZE and just redefine it
> to TASK_SIZE_MAX. So far, these are the TASK_SIZE users that actually
> seem to care about the task in question:
>
> get_unmapped_area. This is
>> (3) Also we may not want to count at every sched_in and sched_out
>> because the MSR reads involve quite a bit of overhead.
>
> Every single other PMU driver just does this; why are you special?
They just have to read a register. We have to write the IA32_EM_EVT_SEL MSR
and then read
For ethernet devices, net_device.name will be eth%d before
register_netdev() is called. Don't print the net_device name until
the format string is replaced.
Cc: Robert Jarzmik
Cc: Barry Song
Cc: Marcel Ziswiler
Cc:
On Tue, 2016-05-10 at 12:30 -0400, Tejun Heo wrote:
> Hello,
>
> On Tue, May 10, 2016 at 11:34:40AM +0530, Vinod Koul wrote:
> >
> > >
> > > slave-dma [1], branch topic/dw. But I think Vinod can tell us
> > > which
> > > tag/branch will be immutable. Vinod?
> > Please use branch topic/dw. I
On 10/05/16 16:51, Shyam Saini wrote:
Fixed following checkpatch.pl warnings
WARNING: Prefer WRITE_ONCE(, ) over ACCESS_ONCE() =
WARNING: Prefer READ_ONCE() over ACCESS_ONCE()
Signed-off-by: Shyam Saini
---
drivers/staging/comedi/comedi_fops.c | 12 ++--
1
From: Borislav Petkov
Date: Wed, 4 May 2016 18:52:09 +0200
Subject: [PATCH -v2] x86/hweight: Get rid of the special calling convention
People complained about ARCH_HWEIGHT_CFLAGS and how it throws a wrench
into kcov, lto, etc, experimentation.
And its not like we absolutely need
On 10/05/2016 18:24, Borislav Petkov wrote:
> Sure but how can one even read that?
>
> AVIC_PHYSICAL_ID_ENTRY_HOST_PHYSICAL_ID_MASK
>
> AVIC's physical ID entry's host's physical ID's mask?
>
> That sucks in any language :-)
If you read it backwards, that's the
Mask
for the
On Tue, May 10, 2016 at 09:45:34AM -0700, Andy Lutomirski wrote:
> On Tue, May 10, 2016 at 9:30 AM, Cyrill Gorcunov wrote:
> > On Tue, May 10, 2016 at 09:07:49AM -0700, Andy Lutomirski wrote:
> >> Hi all-
> >>
> >> I'm trying to get rid of x86's dynamic TASK_SIZE and just
On 09/05/2016 18:23, Cornelia Huck wrote:
> On Mon, 09 May 2016 18:13:37 +0200
> Greg Kurz wrote:
>
>> The KVM_MAX_VCPUS define provides the maximum number of vCPUs per guest, and
>> also the upper limit for vCPU ids. This is okay for all archs except PowerPC
>> which
On 10/05/16 17:34, Stephen Warren wrote:
> On 05/10/2016 10:13 AM, Jon Hunter wrote:
[snip]
>> Stephen, for your u-boot testing, do you are set the bit in the vendor
>> misc register to enable version 3.0 support for sdhci on tegra30? This
>> is what the above quirk is doing (and has done so
On Tue, May 10, 2016 at 08:59:43AM -0700, Yu-cheng Yu wrote:
> This is actually a patch of Fenghua's, but I re-based it.
> I will fix it.
Then please take a look at Documentation/SubmittingPatches too.
Also, please snip the mail text you're quoting if you're not going to
refer to it. Like I just
Hello,
On Tue, May 10, 2016 at 11:34:40AM +0530, Vinod Koul wrote:
> > slave-dma [1], branch topic/dw. But I think Vinod can tell us which
> > tag/branch will be immutable. Vinod?
>
> Please use branch topic/dw. I will not rebase this before sending to Linus.
Okay, pulled topic/dw into
On May 10 2016 or thereabouts, Fabio Estevam wrote:
> On Tue, May 10, 2016 at 12:37 PM, Benjamin Tissoires
> wrote:
>
> > @@ -92,7 +93,7 @@ soc_button_device_create(struct platform_device *pdev,
> > continue;
> >
> > gpio =
When a partition is not aligned by 4KB, mount -o dax succeeds,
but any read/write access to the filesystem fails, except for
metadata update.
Call bdev_dax_supported() to perform proper precondition checks
which includes this partition alignment check.
Signed-off-by: Toshi Kani
blkdev_dax_capable() is similar to bdev_dax_supported(), but needs
to remain as a separate interface for checking dax capability of
a raw block device.
Rename and relocate blkdev_dax_capable() to keep them maintained
consistently, and call bdev_direct_access() for the dax capability
check.
There
On 10.05.2016 11:21, Konstantin Khlebnikov wrote:
I've got plenty warnings, bugs and oops around trivial use of mod_delayed_work
in drivers/infiniband/core/addr.c
Looks like problem in mod_delayed_work_on was hidden because add_timer is equal
to mod_timer
but Sasha accidentally backported
When a partition is not aligned by 4KB, mount -o dax succeeds,
but any read/write access to the filesystem fails, except for
metadata update.
Call bdev_dax_supported() to perform proper precondition checks
which includes this partition alignment check.
Signed-off-by: Toshi Kani
Hi Alex,
On 05/10/2016 12:49 AM, Alex Williamson wrote:
> On Wed, 4 May 2016 11:54:18 +
> Eric Auger wrote:
>
>> This patch allows the user-space to retrieve the MSI geometry. The
>> implementation is based on capability chains, now also added to
>>
On 05/10/2016 06:26 AM, Sergei Shtylyov wrote:
On 5/10/2016 2:46 AM, David Lechner wrote:
The CFGCHIP registers are used by a number of devices, so using a syscon
device to share them. The first consumer of this will by the
phy-da8xx-usb
driver.
Signed-off-by: David Lechner
On Mon, 9 May 2016 12:53:37 -0500
Reza Arbab wrote:
> Add move_pfn_range(), a wrapper to call move_pfn_range_left() or
> move_pfn_range_right().
>
> No functional change. This will be utilized by a later patch.
>
> Signed-off-by: Reza Arbab
On Mon, May 09, 2016 at 01:45:59PM -0700, Yu-cheng Yu wrote:
> User space uses standard format xsave area. fpstate in signal frame should
> have standard format size.
>
> To explicitly distinguish between xstate size in kernel space and the one
> in user space, we rename xstate_size to
DAX imposes additional requirements to a device. Add
bdev_dax_supported() which performs all the precondition checks
necessary for filesystem to mount the device with dax option.
Also add a new check to verify if a partition is aligned by 4KB.
When a partition is unaligned, any dax read/write
When a partition is not aligned by 4KB, mount -o dax succeeds,
but any read/write access to the filesystem fails, except for
metadata update.
Call bdev_dax_supported() to perform proper precondition checks
which includes this partition alignment check.
Reported-by: Micah Parrish
When a partition is not aligned by 4KB, mount -o dax succeeds,
but any read/write access to the filesystem fails, except for
metadata update. Add alignment check to ext4, ext2, and xfs.
- Patch 1-2 add bdev_dax_supported() which performs all the checks
necessary for dax mount.
- Patch 3-5
On Tue, May 10, 2016 at 06:29:00PM +0200, Borislav Petkov wrote:
> Also, please snip the mail text you're quoting if you're not going to
> refer to it. Like I just did.
Ok :-)
On 05/10/2016 10:13 AM, Jon Hunter wrote:
On 09/05/16 16:15, Jon Hunter wrote:
Support for SD cards is not working on the Tegra30 Beaver board and on
boot the following error message is seen if an SD card is present:
mmc0: error -110 whilst initialising SD card
In addition to this, Tegra30
In preparation of moving DAX capability checks to the block layer
from filesystem code, add a VFS message interface that aligns with
filesystem's message format.
For instance, a vfs_msg() message followed by XFS messages in case
of a dax mount error may look like:
VFS (pmem0p1): error:
Hello,
On Tue, May 10, 2016 at 07:28:08PM +0300, Konstantin Khlebnikov wrote:
> On 10.05.2016 11:21, Konstantin Khlebnikov wrote:
> >I've got plenty warnings, bugs and oops around trivial use of
> >mod_delayed_work in drivers/infiniband/core/addr.c
>
> Looks like problem in mod_delayed_work_on
On Tue, May 10, 2016 at 9:30 AM, Cyrill Gorcunov wrote:
> On Tue, May 10, 2016 at 09:07:49AM -0700, Andy Lutomirski wrote:
>> Hi all-
>>
>> I'm trying to get rid of x86's dynamic TASK_SIZE and just redefine it
>> to TASK_SIZE_MAX. So far, these are the TASK_SIZE users that
Neither APICv nor AVIC actually need the first argument of
hwapic_isr_update, but the vCPU makes more sense than passing the
pointer to the whole virtual machine! In fact in the APICv case it's
just because the vCPU is used implicitly, through the loaded VMCS.
The second argument instead is
On 05/10/2016 01:03 AM, Alex Williamson wrote:
> On Wed, 4 May 2016 14:06:19 +0200
> Eric Auger wrote:
>
>> Hi Alex,
>> On 05/04/2016 01:54 PM, Eric Auger wrote:
>>> This patch allows the user-space to retrieve the MSI geometry. The
>>> implementation is based on
On 05/05/2016 02:15 PM, Arnd Bergmann wrote:
>> +Required properties:
>> +- compatible: must be one of: "brcm,bcm7425-pcie"
>> + "brcm,bcm7435-pcie"
>> + "brcm,bcm7445-pcie"
>> +
>> +- reg: specifies the physical base address of the controller
On Tue, May 10, 2016 at 07:00:43PM +0200, Paolo Bonzini wrote:
> If you read it backwards, that's the
>
> Mask
> for the host physical id
> in entries of
> the physical ID table
> (an AVIC thing).
Note to self: defines in arch/x86/kvm/ should be read backwards.
> Quite a
Robert Foss writes:
> On 2016-05-03 03:22 PM, Eric Anholt wrote:
>> robert.f...@collabora.com writes:
>>
>>> From: Robert Foss
>>>
>>> As per the documentation in drm_crtc.h, atomic_commit should return
>>> -EBUSY if an asycnhronous update
Il 10/05/2016 18:12, Jeff Moyer ha scritto:
Paolo Valente writes:
When a bio is split, the newly created bio must be associated with the
same blkcg as the original bio (if BLK_CGROUP is enabled). If this
operation is not performed, then the new bio is not associated
On 05/10/2016 10:01 AM, Borislav Petkov wrote:
>> >pr_info("x86/fpu: Enabled xstate features 0x%llx, context size is %d
>> > bytes, using '%s' format.\n",
>> >xfeatures_mask,
>> > - xstate_size,
>> > + kernel_xstate_size,
>> >cpu_has_xsaves ?
On Tue, May 10, 2016 at 5:39 PM, Andrey Ryabinin wrote:
> 2016-03-15 13:10 GMT+03:00 Alexander Potapenko :
>
>>
>> static inline int kasan_module_alloc(void *addr, size_t size) { return 0; }
>> static inline void kasan_free_shadow(const struct
From: Baoquan He
The current KASLR implementation randomizes the physical and virtual
addresses of the kernel together (both are offset by the same amount). It
calculates the delta of the physical address where vmlinux was linked
to load and where it is finally loaded. If the
This extracts the call to prepare_level4() into a top-level function
that the user of the pagetable.c interface must call to initialize
the new page tables. For clarity and to match the "finalize" function,
it has been renamed to initialize_identity_maps(). This function also
gains the
Thanks Eric!
On 2016-05-10 01:06 PM, Eric Anholt wrote:
Robert Foss writes:
On 2016-05-03 03:22 PM, Eric Anholt wrote:
robert.f...@collabora.com writes:
From: Robert Foss
As per the documentation in drm_crtc.h, atomic_commit should
This patch exchanges the prior slots[] array for the new slot_areas[]
array, and lifts the limitation of KERNEL_IMAGE_SIZE on the physical
address offset for 64-bit. As before, process_e820_entry() walks
memory and populates slot_areas[], splitting on any detected mem_avoid
collisions.
Finally,
From: Yinghai Lu
Currently the physical randomization's lower boundary is the original
kernel load address. For bootloaders that load kernels into very high
memory (e.g. kexec), this means randomization takes place in a very small
window at the top of memory, ignoring the
This is v8 of the last 3 patches from v7, with an additional clean-up for
the pagetable.c code. The rest of the series has landed in -tip.
The patches are:
- 1: Further clean up on pagetable.c.
- 2: Last part of Baoquan's decoupling the physical address and virtual
address randomization of
On 10/05/16 16:14, Jon Hunter wrote:
> When setting the IRQ type we don't check the return value to see if it
> is set correctly. Due to this, failures to set the IRQ type have gone
> unnoticed and because these failures were not catastrophic have not had
> an impact on the system.
>
> Ideally,
On 09/05/2016 10:14, Thomas Huth wrote:
>> > Tested-by: Thomas Huth
> Ping!
>
> Alex, Paul, could you please pick up this patch? This patch is required
> to get the kvm-unit-tests working properly with kvm-pr, so I'd be glad
> if we could get this included finally...
I have
Hi Linus,
Since v4.5, we've WARNed during resume if a PCI device, including a
Thunderbolt device, was added while we were suspended. A change we merged
for v4.6-rc1 turned that warning into a system hang. These patches from
Lukas fix this issue.
Bjorn
The following changes since commit
On 05/10/2016 10:26 AM, Borislav Petkov wrote:
>> > It's nice to dump out interesting data in dmesg, but I'm curious why you
>> > think it's interesting.
> I think it would be interesting to know what the kernel's idea
> is of user_xstate_size. I know, I know, one can follow the code
> and figure
On Mon, May 09, 2016 at 10:55:24PM +0100, Matt Fleming wrote:
> On Mon, 02 May, at 04:39:31PM, Alex Thorlton wrote:
> >
> > If you think we're violating EFI rules by accessing these registers from
> > both sides of the fence, please let me know. I'd like to make sure that
> > we get everything
Replace custom approach by %*ph specifier to dump small buffers in hex format.
Unfortunately we can't use print_hex_dump_bytes() here since tha gap is
present, though one familiar with the code may change this.
Signed-off-by: Andy Shevchenko
---
In v2:
- use
On 05/10/2016 05:44 AM, Ralf Baechle wrote:
> On Fri, Apr 15, 2016 at 11:36:48AM +0100, Paul Burton wrote:
>
>> This series fixes up a number of issues introduced by commit
>> c5b367835cfc ("MIPS: Add support for XPA."), including breakage of the
>> MIPS32 with 36 bit physical addressing case &
These two types have similar function.
No need to separate them.
Signed-off-by: Zhao Lei
---
kernel/sched/cpuacct.c | 47 ---
1 file changed, 20 insertions(+), 27 deletions(-)
diff --git a/kernel/sched/cpuacct.c
Mike reported that the recent commit 3a47d5124a95 ("sched/fair: Fix
fairness issue on migration") broke interactivity and the signal
starve test.
The problem is that I assumed ENQUEUE_WAKING was only set when we do a
cross-cpu wakeup (migration), which isn't true. This means we now
destroy the
With sched_class::task_waking being called only when we do
set_task_cpu(), we can make sched_class::migrate_task_rq() do the work
and eliminate sched_class::task_waking entirely.
Cc: Pavan Kondeti
Cc: Ben Segall
Cc: Matt Fleming
On 05/10/2016 11:16 AM, Jon Hunter wrote:
On 10/05/16 17:34, Stephen Warren wrote:
On 05/10/2016 10:13 AM, Jon Hunter wrote:
[snip]
Stephen, for your u-boot testing, do you are set the bit in the vendor
misc register to enable version 3.0 support for sdhci on tegra30? This
is what the
This fixes two issues with the arm64 brk randomziation. First, the
STACK_RND_MASK was being used incorrectly. The original code was:
unsigned long range_end = base + (STACK_RND_MASK << PAGE_SHIFT) + 1;
STACK_RND_MASK is 0x7ff (32-bit) or 0x3 (64-bit), with 4K pages where
PAGE_SHIFT
On Mon, May 09, 2016 at 12:24:33PM +0100, John Keeping wrote:
> - SND_SOC_DAPM_SUPPLY("Mic Bias", ES8328_ADCPOWER,
> - ES8328_ADCPOWER_MIC_BIAS_OFF, 1, NULL, 0),
> + SND_SOC_DAPM_MICBIAS("Mic Bias", ES8328_ADCPOWER,
> + ES8328_ADCPOWER_MIC_BIAS_OFF,
On 10.05.2016 19:36, Tejun Heo wrote:
Hello,
On Tue, May 10, 2016 at 07:28:08PM +0300, Konstantin Khlebnikov wrote:
On 10.05.2016 11:21, Konstantin Khlebnikov wrote:
I've got plenty warnings, bugs and oops around trivial use of mod_delayed_work
in drivers/infiniband/core/addr.c
Looks like
On Tue, May 10, 2016 at 06:53:18PM +0200, Borislav Petkov wrote:
> static __always_inline unsigned int __arch_hweight32(unsigned int w)
> {
> - unsigned int res = 0;
> + unsigned int res;
>
> - asm (ALTERNATIVE("call __sw_hweight32", POPCNT32, X86_FEATURE_POPCNT)
> -
Hi Eric,
On 10/05/16 17:10, Eric Auger wrote:
Hi Alex,
On 05/10/2016 12:49 AM, Alex Williamson wrote:
On Wed, 4 May 2016 11:54:16 +
Eric Auger wrote:
On x86 IRQ remapping is abstracted by the IOMMU. On ARM this is abstracted
by the msi controller.
On Tue, May 10, 2016 at 10:08:44AM -0700, Dave Hansen wrote:
> But the kernel never actually stores "user_xstate_size" anywhere or
> really ever even cares about it except when copying in/out of userspace.
Sounds like a reason enough to me.
> "user_xstate_size" is also entirely enumerable in
On Tue, May 10, 2016 at 10:05 AM, Cyrill Gorcunov wrote:
> On Tue, May 10, 2016 at 09:45:34AM -0700, Andy Lutomirski wrote:
>> On Tue, May 10, 2016 at 9:30 AM, Cyrill Gorcunov wrote:
>> > On Tue, May 10, 2016 at 09:07:49AM -0700, Andy Lutomirski wrote:
>>
Martin Sperl writes:
> On 10.05.2016 03:01, Eric Anholt wrote:
>> With the new patch 2 inserted between my previous pair, I think this
>> should cover Martin's bugs with clock disabling.
>>
>> I tested patch 2 to be important on the downstream kernel: with the
>> DPI
When check for capabilities recognize slave support by either DMA_SLAVE or
DMA_CYCLIC bit set. If we don't do that the user can't get a normally worked
DMA support for engines that doesn't have one of the mentioned bits set.
Signed-off-by: Andy Shevchenko
---
On Tue, May 10, 2016 at 10:19:12AM -0700, Kees Cook wrote:
> This extracts the call to prepare_level4() into a top-level function
> that the user of the pagetable.c interface must call to initialize
> the new page tables. For clarity and to match the "finalize" function,
> it has been renamed to
Merge code for each cpustat(system/user) into a loop,
to avoid clone of code blocks.
Only a little cleanup.
Signed-off-by: Zhao Lei
---
kernel/sched/cpuacct.c | 29 ++---
1 file changed, 14 insertions(+), 15 deletions(-)
diff --git
In current code, we can get cpuacct data from severial files,
but each file have its lilmit.
For example:
we can get cpu usage in user and kernel mode by cpuacct.stat,
but we can't get detail data of each cpu in above file.
we can get each cpu's kernel mode usage in cpuacct.usage_percpu_sys,
but
In current code, we can get cpuacct data from severial files,
but each file have its lilmit.
For example:
we can get cpu usage in user and kernel mode by cpuacct.stat,
but we can't get detail data of each cpu in above file.
we can get each cpu's kernel mode usage in cpuacct.usage_percpu_sys,
but
701 - 800 of 1974 matches
Mail list logo