Reset dapswjdp is controlled by JTAG_TRSTN, if the iomux of this pin is
not "jtag_trstn". the AP would think this pin is always high, so it can
not reset before resume. When system resume, but the dapswjdp is not in
a default state, it may Access some illegal address, it cause system
crash during
Thanks, that gives me hope, I'll wait patiently then.
BTW, if you want any reference for how this is written, see this:
http://en.wikipedia.org/wiki/Qt_%28software%29
Thanks,
Diego
On Wed, Apr 15, 2015 at 2:36 AM, Jiri Kosina wrote:
> On Wed, 15 Apr 2015, Diego Viola wrote:
>
>> I apologize
On 04/15/2015 08:57 AM, Dave Young wrote:
Again, I think it is bad to use old page table, below issues need consider:
1) make sure old page table are reliable across crash
2) do not allow writing oldmem after crash
Please correct me if I'm wrong, or if above is not doable I think I will vote
On 4/14/2015 11:41 PM, Jason Gunthorpe wrote:
Erez, you basically rewrote this, please make a proper patch with the Fixes and
Reported-By credit for Honggang. Lets merge this through Dave M's tree right
away.
Agree, Erez, add proper Fixes: XXX note and send a patch to netdev
against
The SDMA on imx6sx has a few DMA event remapping configurations
inside the GPR (General Purpose Register) of that SoC. When users
want to use a non-default DMA event, they need to configure the
GPR register. So this patch gives an interface of the GPR and
implements it in the SDMA driver so as to
On Wed, 15 Apr 2015, Diego Viola wrote:
> I apologize for being impatient, but I sent my first patch a week ago
> and then I sent another after a week.
>
> I realize the patch is trivial, but I still want to see it merged
> regardless, and this is my first contribution to the mailing list, so
>
> Hi Hannes,
Hi Vignesh,
thanks for answer.
> >>
> >> would it be possible to add some more channel-specific settings ?
> >>
> >> It would be nice to have allmost full control to the STEPCONFIGx
> > register.
> >>
> >> At least we need to write the bits
> >>
> >> SEL_RFM_SWC_1_0
> >>
> From: Matwey V. Kornilov [mailto:matwey.korni...@gmail.com]
> mach-dependent stuff has been removed by
> 2eb2478d471e45e1d0c8bb3defbf82bf7204e13d
> So, there is no need to keep
> depends on ARCH_DAVINCI_DA850
>
> Signed-off-by: Matwey V. Kornilov
> ---
> drivers/uio/Kconfig | 1 -
>
Acked-by: Eli Cohen
On Wed, Apr 15, 2015 at 11:19:17AM +0800, Honggang Li wrote:
> If CONFIG_ARCH_DMA_ADDR_T_64BIT enabled for x86 systems and physical
> memory is more than 4GB, dma_map_page may return a valid memory
> address which greater than 0x. As a result, the mlx5 device page
>
Hi all,
On Mon, 13 Apr 2015 16:36:58 +0800 Bob Liu wrote:
>
> On 04/13/2015 04:09 PM, Stephen Rothwell wrote:
> >
> > After merging the xen-tip tree, today's linux-next build (x86_64
> > allmodconfig)
> > failed like this:
> >
> > drivers/char/tpm/xen-tpmfront.c: In function 'setup_ring':
> >
Since the table is about to be freed, there is no reason to set file
pointer to NULL on closing.
At this point open_fd map is supposed to indicate whether a file is
installed, so NULL-checking it is unnecessary.
Signed-off-by: Mateusz Guzik
---
fs/file.c | 7 ++-
1 file changed, 2
Peter Zijlstra writes:
> On Tue, Apr 14, 2015 at 12:27:05PM +0930, Rusty Russell wrote:
>
>> I was tempted to sneak in those module rcu fixes for 4.1, but seeing
>> Ingo's comments I'll wait for 4.2.
>
> I can get you a new version of that if you want. See below. The fixups
> are unmodified of
Hi Dave,
On Wed, 15 Apr 2015 00:16:50 -0400 (EDT) David Miller
wrote:
>
> The first has to do with Stephen Rothwells movement of trace entries
> into individual files while meanwhile the wireless folks were adding
> new ones or changing the signature of existing ones.
Umm, it wasn't me moving
I apologize for being impatient, but I sent my first patch a week ago
and then I sent another after a week.
I realize the patch is trivial, but I still want to see it merged
regardless, and this is my first contribution to the mailing list, so
I apologize for any inconvenience.
I thought my
On Fri, Apr 3, 2015 at 2:36 AM, Ivan.khoronzhuk
wrote:
>
>
> On 02.04.15 15:57, Ivan Khoronzhuk wrote:
>>
>> Some utils, like dmidecode and smbios, need to access SMBIOS entry
>> table area in order to get information like SMBIOS version, size, etc.
>> Currently it's done via /dev/mem. But for
On Tue, Apr 14, 2015 at 08:19:57PM -0700, Linus Torvalds wrote:
> On Tue, Apr 14, 2015 at 7:55 PM, Paul E. McKenney
> wrote:
> >
> > Does the (currently being tested) patch below fix things up? If not,
> > please fill me in on the further error of my ways.
>
> Looks ok.
>
> That said, couldn't
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in
include/uapi/linux/media-bus-format.h between commits 7b0fd4568bee
("[media] v4l: Add RBG and RGB 8:8:8 media bus formats on 24 and 32 bit
busses"), e8b2d7a565ae ("[media] v4l: Sort YUV formats of
v4l2_mbus_pixelcode") and
Hi Linus:
Here is the crypto update for 4.1:
* Added user-space interface for AEAD.
* Added user-space interface for RNG (i.e., pseudo RNG).
* Prevent internal helper algos from being exposed to user-space.
* Merged common code from assembly/C SHA implementations .
* Added ARMv8 SHA1/256.
*
"Michael S. Tsirkin" writes:
> On Tue, Apr 14, 2015 at 11:50:53AM +0200, Cornelia Huck wrote:
>> On Tue, 14 Apr 2015 11:21:11 +0200
>> "Michael S. Tsirkin" wrote:
>>
>> > diff --git a/include/uapi/linux/virtio_balloon.h
>> > b/include/uapi/linux/virtio_balloon.h
>> > index f81b220..164e0c2
Hi Dave,
Today's linux-next merge of the drm tree got a conflict in
Documentation/DocBook/media/v4l/subdev-formats.xml between commit
7b0fd4568bee ("[media] v4l: Add RBG and RGB 8:8:8 media bus formats on
24 and 32 bit busses") and e8b2d7a565ae ("[media] v4l: Sort YUV formats
of
Cornelia Huck writes:
> On Tue, 14 Apr 2015 12:01:13 +0200
> "Michael S. Tsirkin" wrote:
>
>> Looks like we are better off sticking with the misaligned stat struct,
>> to reduce the amount of virtio 1 specific code in balloon. So let's do
>> it.
>>
>> Add a detailed comment to reduce the
Quentin Casasnovas writes:
> On Tue, Apr 14, 2015 at 02:14:14PM +0200, Thierry Reding wrote:
>> On Tue, Mar 17, 2015 at 01:40:02PM +0100, Quentin Casasnovas wrote:
>> > If one of these addresses point to a non-executable section, something is
>> > seriously wrong since it either means the kernel
Arthur Gautier writes:
> On Wed, Apr 08, 2015 at 03:29:43PM +0930, Rusty Russell wrote:
>> Arthur Gautier writes:
>> > When starting kernel with arguments like:
>> > init=/bin/sh -c "echo arguments"
>> > the trailing double quote is not removed which results in following command
>> > being
On Tue, Apr 14, 2015 at 08:29:34PM +0900, Chanwoo Choi wrote:
> On 04/14/2015 07:38 PM, Roger Quadros wrote:
> > On 14/04/15 13:31, Chanwoo Choi wrote:
> >> On 04/14/2015 07:02 PM, Roger Quadros wrote:
> >>> Fixed Kishon's id.
> >>>
> >>> On 14/04/15 13:01, Roger Quadros wrote:
> On 10/04/15
From: Steven Rostedt
Date: Tue, 14 Apr 2015 23:06:29 -0400
> I also noted this coming conflict in my pull request. So Linus should
> be very well aware of it.
>
> https://lkml.org/lkml/2015/4/13/652
>
> "Also there's a conflict with commit 7e1223b50089 ("iwlwifi: mvm: new
> Alive / error
Fix:
drivers/i2c/busses/i2c-jz4780.c: In function 'jz4780_i2c_readw':
drivers/i2c/busses/i2c-jz4780.c:181:2: error:
implicit declaration of function 'readw'
drivers/i2c/busses/i2c-jz4780.c: In function 'jz4780_i2c_writew':
drivers/i2c/busses/i2c-jz4780.c:187:2: error:
On Tue, Apr 14, 2015 at 7:55 PM, Paul E. McKenney
wrote:
>
> Does the (currently being tested) patch below fix things up? If not,
> please fill me in on the further error of my ways.
Looks ok.
That said, couldn't that last dummy gp_init_delay variable:
> +/* Delay in jiffies for grace-period
If CONFIG_ARCH_DMA_ADDR_T_64BIT enabled for x86 systems and physical
memory is more than 4GB, dma_map_page may return a valid memory
address which greater than 0x. As a result, the mlx5 device page
allocator RB tree will be initialized with valid addresses greater than
0xfff.
However,
On Tue, Apr 14, 2015 at 10:23:16PM +0300, Eli Cohen wrote:
> On Mon, Apr 13, 2015 at 05:21:58PM +0800, Honggang Li wrote:
> > @@ -241,7 +243,7 @@ static void free_4k(struct mlx5_core_dev *dev, u64 addr)
> > static int alloc_system_page(struct mlx5_core_dev *dev, u16 func_id)
> > {
> > struct
On Wed, 15 Apr 2015 11:23:23 +1000
Stephen Rothwell wrote:
> Hi all,
>
> On Mon, 13 Apr 2015 17:52:24 +1000 Stephen Rothwell
> wrote:
> >
> > Today's linux-next merge of the ftrace tree got a conflict in
> > drivers/net/wireless/iwlwifi/iwl-devtrace.h between commit 7e1223b50089
> >
On 14 April 2015 at 19:40, Mark Brown wrote:
> On Tue, Apr 14, 2015 at 11:22:41AM +1000, Stephen Rothwell wrote:
>> On Mon, 13 Apr 2015 18:07:06 -0700 Bjorn Andersson
>> wrote:
>
>> > Your patch looks correct and should preferrably be added to the drm
>> > tree, or the last patch in my series
On Tue, Apr 14, 2015 at 05:25:12PM -0700, Linus Torvalds wrote:
> On Tue, Apr 14, 2015 at 5:22 PM, Linus Torvalds
> wrote:
> >
> >depends on RCU_TORTURE_TEST_SLOW_INIT
> >
> > would seem to be called for.
>
> Side note, you'll obviously also need to fix the actual bogus
> 'gp_init_delay'
Hi Andy,
On 14 April 2015 at 17:33, Andy Lutomirski wrote:
> On 04/14/2015 03:52 PM, Tyler Baker wrote:
>>
>> x86 tests should not be built when ARCH != x86. Reused the logic from
>> breakpoints to determine when it's appropriate to build.
>
>
> In the future, please cc the author of
As Andres pointed out:
| I don't understand the value of this check here. Are we looking for a
| broken memslot? Shouldn't this be a BUG_ON? Is this the place to care
| about these things? npages is capped to KVM_MEM_MAX_NR_PAGES, i.e.
| 2^31. A 64 bit overflow would be caused by a gigantic
On Tue, 14 Apr 2015 19:12:33 -0700
Jason Low wrote:
> Hi Steven,
>
> On Tue, 2015-04-14 at 19:59 -0400, Steven Rostedt wrote:
> > On Tue, 14 Apr 2015 16:09:44 -0700
> > Jason Low wrote:
> >
> >
> > > @@ -2088,7 +2088,7 @@ void task_numa_fault(int last_cpupid, int mem_node,
> > > int pages,
From: Stephen Rothwell
Date: Wed, 15 Apr 2015 11:23:23 +1000
> This patch is now needed when the net-next tree is merged with Linus'
> tree ...
Yeah I noticed this while working on test merges into Linus's tree,
thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
>>> + pgd = __pgd(__pa(kasan_zero_pmd) | PAGE_KERNEL);
>>> +#else
>>> + pgd = __pgd(__pa(kasan_zero_pte) | PAGE_KERNEL);
>>> +#endif
>>> +
>>> + for (i = pgd_index(start); start < end; i++) {
>>> + set_pgd([i], pgd);
>>> + start += PGDIR_SIZE;
>>> + }
>>> +}
>>
>> Same
Hi Len,
On Mon, 13 Apr 2015 14:24:42 +1000 Stephen Rothwell
wrote:
>
> Hi Rafael,
>
> After merging the pm tree, today's linux-next build (x86_64 allmodconfig)
> failed like this:
>
> In file included from arch/x86/include/asm/msr.h:131:0,
> from
On 2015/4/15 3:42, Thomas Gleixner wrote:
> The code sets the expiry value of the timer to a relative value and
> starts it with hrtimer_start_expires. That's fine, but that only works
> once. The timer is started in relative mode, so the expiry value gets
> overwritten with the absolut expiry
On Tue, Apr 14, 2015 at 3:31 PM, Yong Wu wrote:
>> >>
>> >> > +
>> >> > + piommu->protect_va = devm_kmalloc(piommu->dev,
>> >> > MTK_PROTECT_PA_ALIGN*2,
>> >>
>> >> style: Operators like * should have space on both sides.
>> >>
>> >> > + GFP_KERNEL);
On Wed, 2015-04-15 at 07:32 +1000, Anton Blanchard wrote:
> gcc has recently bumped its major version and this is causing kernel
> build errors. Create include/linux/compiler-gcc6.h which is a copy
> of compiler-gcc5.h, minus a few comments that no longer apply.
I still think it'd be better to
On 04/14/15 at 08:41pm, Petr Mladek wrote:
> On Wed 2015-04-15 01:01:39, Minfei Huang wrote:
> > On 04/14/15 at 06:27pm, Petr Mladek wrote:
> > > On Tue 2015-04-14 23:55:36, Minfei Huang wrote:
> > > > On 04/14/15 at 10:11P, Josh Poimboeuf wrote:
> > > > > On Tue, Apr 14, 2015 at 01:45:49PM +0800,
Hi Steven,
On Tue, 2015-04-14 at 19:59 -0400, Steven Rostedt wrote:
> On Tue, 14 Apr 2015 16:09:44 -0700
> Jason Low wrote:
>
>
> > @@ -2088,7 +2088,7 @@ void task_numa_fault(int last_cpupid, int mem_node,
> > int pages, int flags)
> >
> > static void reset_ptenuma_scan(struct task_struct
Dear maintainers & communities,
This patch introduces DTS thermal driver for Intel Quark X1000.
The code implementation is based on intel_soc_dts_thermal.c.
Intel Quark X1000 has one on-die DTS with two configurable trip points:
critical and hot trip points. However, todate, UEFI BIOS for Quark
In Intel Quark SoC X1000, there is one on-die digital temperature sensor(DTS).
The DTS offers both hot & critical trip points.
However, in current distribution of UEFI BIOS for Quark platform, only
critical trip point is configured to be 105 degree Celsius (based on Quark
SW ver1.0.1 and hot trip
Hi,
Could you please help me to review this patch?
Thanks
On Mon, Mar 16, 2015 at 4:40 PM, Viet Nga Dao wrote:
> On Mon, Mar 16, 2015 at 4:35 PM, Rafał Miłecki wrote:
>> On 16 March 2015 at 09:16, wrote:
>>> +static struct flash_device flash_devices[] = {
>>> +
The trace number does not need to subtract 1 now.
Signed-off-by: Duson Lin
---
drivers/input/mouse/elan_i2c_i2c.c |4 ++--
drivers/input/mouse/elan_i2c_smbus.c |4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/input/mouse/elan_i2c_i2c.c
On Saturday, April 11, 2015 09:20 AM Rafael J. Wysocki worte:
On Wednesday, March 25, 2015 01:49:36 AM Yeon, JeHyeon wrote:
From 6cb5fffc41911a29212be52d4ce7e481f5077ccf Mon Sep 17 00:00:00 2001
From: "Tom(JeHyeon) Yeon"
Date: Thu, 19 Mar 2015 17:10:45 +0900
Subject: [PATCH] PM / Hiberante :
On Mon, Apr 13, 2015 at 1:22 PM, Al Viro wrote:
> On Mon, Apr 13, 2015 at 09:42:17PM +0200, Greg Kroah-Hartman wrote:
>> > I remain opposed to this half thought out trash of an ABI for the
>> > meta-data.
>>
>> You don't have to enable the metadata if you don't want to use it, it's
>> an option
Hi Al,
Today's linux-next merge of the vfs tree got a conflict in
fs/ext4/symlink.c between commit 48e72c7a0127 ("ext4 crypto: Add
symlink encryption") from the ext4 tree and commit 5dd3dc06371a ("VFS:
normal filesystems (and lustre): d_inode() annotations") from the vfs
tree.
[The ext4 tree
On Tue, Apr 7, 2015 at 2:23 PM, Pantelis Antoniou
wrote:
> During the course of the overlay selftests some of them remain
> applied. While this does not pose a real problem, make sure you track
> them and destroy them at the end of the test.
>
> Signed-off-by: Pantelis Antoniou
I've applied
On Tue, Mar 17, 2015 at 06:41:51PM -0700, Tony Lindgren wrote:
> Yeah agreed. I suggest discussing the binding and the generic
> parsing code for it first :)
>
> It seems with the generic binding the actual driver should be
> just the hardware specific code hopefully.
Did this thread go
Ping?
On 2015/4/10 11:53, Wang Nan wrote:
> perf report and perf annotate are easy to trigger segfault if trace data
> contain kernel module information like this:
>
> # perf report -D -i ./perf.data
> ...
> 0 0 0x188 [0x50]: PERF_RECORD_MMAP -1/0: [0xffbff1018000(0xf068000) @
> 0]: x
On Tue, Apr 7, 2015 at 2:23 PM, Pantelis Antoniou
wrote:
> Implement a number of sysfs attributes for overlays.
>
> * A throw once master enable switch to protect against any
> further overlay applications if the administrator desires so.
This one should be a separate patch.
> * A per overlay
Hi all,
On Wed, 8 Apr 2015 15:03:27 +1000 Stephen Rothwell
wrote:
>
> Hi all,
>
> On Tue, 07 Apr 2015 21:54:05 +0200 Daniel Borkmann
> wrote:
> >
> > On 04/07/2015 06:18 PM, Alexei Starovoitov wrote:
> > > On 4/7/15 4:13 AM, Daniel Borkmann wrote:
> > >> [ Cc'ing Dave, fyi ]
> > >>
> > >> On
Hi all,
On Mon, 13 Apr 2015 17:52:24 +1000 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the ftrace tree got a conflict in
> drivers/net/wireless/iwlwifi/iwl-devtrace.h between commit 7e1223b50089
> ("iwlwifi: mvm: new Alive / error table API") from the net-next tree
> and commit
An oops exists in the flow of stmmac_release().
phy_ethtool_get_wol() depends on phydev->drv.
phydev->drv will be null after stmmac_mdio_unreg() completes.
Steps to reproduce on Quark X1000:
1. ifconfig eth0 192.168.0.1
2. rmmod stmmac_pci
To fix this stmmac_mdio_unreg() should be run after
We have an oops with stmmac on Quark X1000/Galileo, triggered by rmmod after
ifconfig. Fix for issue contained in next mail.
root@clanton:~# ifconfig eth0 192.168.0.1
root@clanton:~# rmmod stmmac_pci
[ 39.257871] stmmac_dvr_remove:
removing driver
[ 39.263618] BUG: unable to handle
On Tue, Apr 14, 2015 at 7:57 AM, Linus Walleij wrote:
> Hi Linus,
>
> here is the big pull request for v4.1 pin control changes.
It is very clearly broken:
warning: (PINCTRL_AT91 && PINCTRL_MESON && PINCTRL_NOMADIK &&
PINCTRL_MTK_COMMON && GPIO_TB10X) selects OF_GPIO which has unmet
direct
On Wednesday, April 15, 2015 02:56:27 AM Rafael J. Wysocki wrote:
> Hi Linus,
>
> Please pull from
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
> pm+acpi-4.1-rc1
>
> to receive the first batch of power management and ACPI material for
> v4.1-rc1 with top-most commit
On 04/10/15 at 04:42pm, Li, Zhen-Hua wrote:
> This patchset is an update of Bill Sumner's patchset, implements a fix for:
> If a kernel boots with intel_iommu=on on a system that supports intel vt-d,
> when a panic happens, the kdump kernel will boot with these faults:
>
> dmar: DRHD:
Hi Linus,
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm+acpi-4.1-rc1
to receive the first batch of power management and ACPI material for
v4.1-rc1 with top-most commit b5e82233cab43c25fc0a1c28d9136a086db4aa52
Merge branches 'powercap' and
On Tue, 2015-04-14 at 00:19 +0200, leroy christophe wrote:
>
> Le 13/04/2015 22:26, Scott Wood a écrit :
> > On Sun, 2015-04-12 at 18:16 +0200, leroy christophe wrote:
> >> Le 26/03/2015 22:32, Scott Wood a écrit :
> >>> On Tue, Feb 03, 2015 at 12:38:16PM +0100, LEROY Christophe wrote:
>
The boot_params structure has a 32 bit field for storing the address of
the kernel command line. When the EFI stub allocates memory for the command
line, it allocates at as low and address as possible, but does not ensure
that the address of memory allocated is below 4G.
This patch enforces this
On Tuesday, April 14, 2015 12:28:12 PM Henrique de Moraes Holschuh wrote:
> On Mon, Apr 13, 2015, at 11:23, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> >
> > Refine the mechanism introduced by commit f244d8b623da (ACPIPHP / radeon
> > / nouveau: Fix VGA switcheroo problem related to
On 04/14/2015 12:13 PM, Peter Zijlstra wrote:
> On Mon, Apr 13, 2015 at 09:38:01PM -0500, Suresh E. Warrier wrote:
>> +static u64 *get_write_timestamp(struct ring_buffer_per_cpu *cpu_buffer,
>> +unsigned long *flags)
>> +{
>> +if (rb_precise_nested_write_ts()) {
>>
On 04/14/2015 03:52 PM, Tyler Baker wrote:
x86 tests should not be built when ARCH != x86. Reused the logic from
breakpoints to determine when it's appropriate to build.
In the future, please cc the author of recently-written code that you're
fixing :)
This patch is really weird. You're
On 04/14/2015 06:16 AM, Alexander Kuleshov wrote:
Hello All,
I'm reading x86_64 source code and trying to understand where are
fixmaps space in the virtual memory space. If I understand correctly
(but i'm really not sure about it), fixmap space is after vsyscall
space. As
On Tue, Apr 14, 2015 at 5:22 PM, Linus Torvalds
wrote:
>
>depends on RCU_TORTURE_TEST_SLOW_INIT
>
> would seem to be called for.
Side note, you'll obviously also need to fix the actual bogus
'gp_init_delay' use in kernel/rcu/tree.c.
That code is horrible.
Linus
On Mon, Apr 13, 2015 at 5:14 AM, Ingo Molnar wrote:
>
> Please pull the latest core-rcu-for-linus git tree from:
This is very annoying:
...
torture tests for RCU (RCU_TORTURE_TEST) [N/m/y/?] n
How much to slow down RCU grace-period initialization
(RCU_TORTURE_TEST_SLOW_INIT_DELAY) [3]
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive updates for the input subsystem. You will get the following
new drivers: Qualcomm PM8941 power key drver, ChipOne icn8318
touchscreen controller driver, Broadcom iProc
Hi Linus,
Highlights for this window:
o Improved AVC hashing for SELinux by John Brooks and Stephen Smalley
o Addition of an unconfined label to Smack
o Smack documentation update
o TPM driver updates
Please pull.
---
The following changes since commit
On Tue, 14 Apr 2015 16:09:44 -0700
Jason Low wrote:
> @@ -2088,7 +2088,7 @@ void task_numa_fault(int last_cpupid, int mem_node, int
> pages, int flags)
>
> static void reset_ptenuma_scan(struct task_struct *p)
> {
> - ACCESS_ONCE(p->mm->numa_scan_seq)++;
> +
On Tue, 14 Apr 2015, Richard Guy Briggs wrote:
> When task->comm is passed directly to audit_log_untrustedstring() without
> getting a copy or using the task_lock, there is a race that could happen that
> would output a NULL (\0) in the middle of the output string that would
> effectively
On Tue, Apr 14, 2015 at 4:09 PM, Jason Low wrote:
> This patchset improves the scalability of itimers, thread_group_cputimer
> and addresses a performance issue we found while running a database
> workload where more than 30% of total time is spent in the kernel
> trying to acquire the
Hi all,
Just to let you all know that I will not be releasing linux-next trees
on Thursday or Friday (nor probably over the weekend as usual). Sorry
about that.
--
Cheers,
Stephen Rothwells...@canb.auug.org.au
pgp7cE909e8di.pgp
Description: OpenPGP digital signature
Ping Juri for this patchset, :)
On Mon, Apr 06, 2015 at 04:53:13PM +0800, Wanpeng Li wrote:
>Function pick_next_earliest_dl_task is used to pick earliest and pushable
>dl task from overloaded cpus in pull algorithm, however, it traverses
>runqueue rbtree instead of pushable task rbtree which is
On Tue, Apr 14, 2015 at 10:47 AM, Bob Peterson wrote:
>
> 12 files changed, 184 insertions(+), 95 deletions(-)
Oh, and this was incorrect. You had apparently limited the statistics
to the fs/gfs2 directory, and thus missed the changes to the
MAINTAINERS file. Don't do that - include all the
On Tue, Apr 14, 2015 at 10:47 AM, Bob Peterson wrote:
>
> There's another that adds me as a GFS2 co-maintainer [...]
So generally, when I start getting pull requests from different
people, I'd like to see a previous separate heads-up or confirmation
from the previous person just so that I'm not
On Tue, 31 Mar 2015, Viresh Kumar wrote:
> @@ -1189,12 +1195,41 @@ static inline void __run_timers(struct tvec_base
> *base)
> cascade(base, >tv5, INDEX(3));
> ++base->timer_jiffies;
> list_replace_init(base->tv1.vec + index, head);
> +
> +again:
Note: The chance that the race which this patch addresses seems very
unlikely to occur, especially after the change in patch 2 which sets
the running field after calling this update_gt_cputimer().
However, I am including this patch if we want to be completely safe
from concurrent updates.
ACCESS_ONCE doesn't work reliably on non-scalar types. This patch removes
the rest of the existing usages of ACCESS_ONCE in the scheduler, and use
the new READ_ONCE and WRITE_ONCE APIs.
Signed-off-by: Jason Low
---
include/linux/sched.h |4 ++--
kernel/fork.c |
This patchset improves the scalability of itimers, thread_group_cputimer
and addresses a performance issue we found while running a database
workload where more than 30% of total time is spent in the kernel
trying to acquire the thread_group_cputimer spinlock.
While we're modifying sched and
While running a database workload, we found a scalability issue with itimers.
Much of the problem was caused by the thread_group_cputimer spinlock.
Each time we account for group system/user time, we need to obtain a
thread_group_cputimer's spinlock to update the timers. On larger systems
(such
Set TEST_PROGS so that the required binaries are installed. Skip the install
and test case when ARCH != x86.
Signed-off-by: Tyler Baker
---
tools/testing/selftests/x86/Makefile | 10 ++
1 file changed, 10 insertions(+)
diff --git a/tools/testing/selftests/x86/Makefile
x86 tests should not be built when ARCH != x86. Reused the logic from
breakpoints to determine when it's appropriate to build.
Signed-off-by: Tyler Baker
---
tools/testing/selftests/x86/Makefile | 35 +++
1 file changed, 23 insertions(+), 12 deletions(-)
diff
On 04/14/2015 10:29 AM, Mark Rutland wrote:
>> diff --git a/Documentation/devicetree/bindings/arm/cpus.txt
>> b/Documentation/devicetree/bindings/arm/cpus.txt
>> index 8b9e0a9..35cabe5 100644
>> --- a/Documentation/devicetree/bindings/arm/cpus.txt
>> +++
Em Tue, Apr 14, 2015 at 01:49:33PM -0400, David Ahern escreveu:
> 0d68bc92c48 breaks compiles on RHEL6/OL6:
> cc1: warnings being treated as errors
> builtin-kmem.c: In function ‘search_page_alloc_stat’:
> builtin-kmem.c:322: error: declaration of ‘stat’ shadows a global
> declaration
Remove subdir from DEPS as it is already created at runtime. Without this,
make install fails.
Signed-off-by: Tyler Baker
---
tools/testing/selftests/exec/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/exec/Makefile
On Tue, 2015-04-14 at 14:58 +0200, Ingo Molnar wrote:
> * Michael Ellerman wrote:
>
> > On Tue, 2015-04-14 at 10:55 +0200, Ingo Molnar wrote:
> > > * Sukadev Bhattiprolu wrote:
> > >
> > > > This is another attempt to resurrect Andi Kleen's patchset so users
> > > > can specify perf events by
The ftrace test requires the directory test.d and all of it's contents to be
present during execution. Use TEST_DIRS to ensure this is copied to the
INSTALL_PATH.
Signed-off-by: Tyler Baker
---
tools/testing/selftests/ftrace/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git
Loop over all TEST_DIRS and recursively copy them to the INSTALL_PATH. Tests
such as ftrace require a directory and all of it's contents to execute the
test properly, thus these directories and files need to be copied when we
perform an install.
Signed-off-by: Tyler Baker
---
The breakpoints test should only should be executed on x86 targets, so lets
emit a skip and omit the installation when ARCH != x86.
Signed-off-by: Tyler Baker
---
tools/testing/selftests/breakpoints/Makefile | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git
Set TEST_PROGS so that kdbus-test is installed.
Cc: Greg Kroah-Hartman
Signed-off-by: Tyler Baker
---
tools/testing/selftests/kdbus/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/testing/selftests/kdbus/Makefile
b/tools/testing/selftests/kdbus/Makefile
index
this series by building, installing and deploying all selftests
to x86, arm and arm64 targets.
This series is based on next-20150414
Tyler Baker (7):
selftests: copy TEST_DIRS to INSTALL_PATH
selftests/ftrace: install test.d
selftests/breakpoints: emit skip and omit installation when tests
On Tue, 14 Apr 2015, Greg Kroah-Hartman wrote:
> I don't understand. You can not like the D-Bus model (and accordingly
> the X11 model),
I thought that the general hatred level of the X11 "model" and the
protocol lead to al the efforts to reimplement this properly ... in
userspace (for
On Tue, 14 Apr 2015, Greg Kroah-Hartman wrote:
> Yes, it's an unfortunate design, but one that we are all stuck with
> (think of it as having to implement code for horrid hardware that you
> have to get to work properly.)
Greg, I personally consider this a rather defunct analogy. Broken
On Tue, Apr 14, 2015 at 03:21:17PM +0100, Kumar Gala wrote:
[...]
> > Looking beyond this set of patches, I can foresee that you won't care
> > about the generic arm64 cpuidle driver either, or more precisely the
> > separation between cpuidle subsystem+driver and the SoC-specific
> > back-end
On Tuesday 14 April 2015 16:00:34 Catalin Marinas wrote:
> On Tue, Apr 14, 2015 at 04:07:36PM +0200, Arnd Bergmann wrote:
> > For completeness, there is yet another option, which would be to use the
> > exact system call table from arm64 and do all the emulation in user space
> > rather than the
On Mon, Apr 13, 2015 at 2:02 PM, Thomas Gleixner wrote:
>
> perf_event_mux_interval_ms_store() tries to apply an updated
> hrtimer_interval to all possible cpus in a completely unsafe way. The
> changelog of the offending commit says:
>
> "In the 5th version, we handle the reprogramming of the
1 - 100 of 1314 matches
Mail list logo
