> > Yes, sorry - I applied the last chunk by hand because it was mangled by
> > the web UI, and added ti to a wrong struct.
> >
> > Now I tested it on top of 4.3.0-rc1. COmpiles, rebooted fine 6 times,
> > but now it hangs again, seems to be the same message:
> >
> > [ 107.143910] kobject (000
Signed-off-by: Hui Zhu
---
mm/zsmalloc.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/mm/zsmalloc.c b/mm/zsmalloc.c
index f135b1b..1f66d5b 100644
--- a/mm/zsmalloc.c
+++ b/mm/zsmalloc.c
@@ -38,6 +38,7 @@
* page->lru: links together first pages of various zspages.
* Basi
On Tue, Sep 22, 2015 at 08:38:43AM +0200, Javier Martinez Canillas wrote:
> Hello Sudip,
>
> On 09/22/2015 06:52 AM, Sudip Mukherjee wrote:
> > On Tue, Sep 22, 2015 at 02:39:36AM +0200, Javier Martinez Canillas wrote:
> >> The driver is using -1 instead of the -ENOMEM defined macro to specify
> >>
On Mon, Sep 21, 2015 at 11:04:42PM -0500, Felipe Balbi wrote:
> Hi,
>
> On Mon, Sep 21, 2015 at 10:21:31AM +0100, Felipe Tonello wrote:
> > Hi Balbi,
> >
> > On Fri, Sep 18, 2015 at 6:36 PM, wrote:
> > > From: "Felipe F. Tonello"
> > >
> > > f_midi is not checking whether there is an error on
On Mon, Sep 21, 2015 at 06:23:18PM -0300, Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> We will use the tools/build/ autodetection in the eBPF patchkit
> and it is currently sharing the output directory with perf, that
> also uses the feature detection logic.
>
> As se kee
On 22 September 2015 at 02:39, Rob Herring wrote:
> On Mon, Sep 21, 2015 at 9:02 AM, Tomeu Vizoso
> wrote:
>> When adding platform and AMBA devices, set the device node's device
>> member to point to it.
>>
>> This speeds lookups considerably and is safe because we only create one
>> of these dev
From: Thomas Gleixner
Date: Mon, 21 Sep 2015 11:01:10 +0200
> To deal with this proper, we need to force thread the primary handler
> of such interrupts as well. That means that the primary interrupt
> handler is treated as any other primary interrupt handler which is not
> marked IRQF_NO_THREAD.
I don't find any maintainer in the MAINTAINERS who is in charge of
this document, so I post it to the lkml.
This patch is to fix alignment of one line in Documentation/security/LSM.txt
Signed-off-by: Dongliang Mu
---
diff --git a/Documentation/security/LSM.txt b/Documentation/security/LSM.txt
i
Hi Jacek,
Thanks for the patchset. A few comments below.
Jacek Anaszewski wrote:
> This patch removes SET_BRIGHTNESS_ASYNC and SET_BRIGHTNESS flags.
> led_set_brightness now calls led_set_brightness_nosleep instead of
> choosing between sync and async op basing on the flags defined by the
> drive
Hello Sudip,
On 09/22/2015 06:52 AM, Sudip Mukherjee wrote:
> On Tue, Sep 22, 2015 at 02:39:36AM +0200, Javier Martinez Canillas wrote:
>> The driver is using -1 instead of the -ENOMEM defined macro to specify
>> that a buffer allocation failed. Since the error number is propagated,
>> the caller
Hi Boris,
On 09/21/2015 11:33 AM, Boris Brezillon wrote:
When requested by a user, the PWM is assigned a default period and polarity
extracted from the DT, the platform data or statically set by the driver.
Those default values are currently stored in the period and polarity
fields of the pwm_de
Right now pgd_alloc() uses pgd_ctor(), which copies over the
current swapper_pg_dir[] to a new task's PGD.
This is not necessary, it's enough if we clear it: the PGD will
then be properly updated by arch_pgd_init_late().
Cc: Andrew Morton
Cc: Andy Lutomirski
Cc: Borislav Petkov
Cc: Brian Gerst
So this is the somewhat belated latest iteration of the series.
I (think I) fixed all correctness bugs in the code pointed out by Oleg.
The task list walk is still 'dumb', using for_each_process(), as none of
the call sites are performance critical.
Oleg, can you see any problems with this code?
So when we unmap kernel memory range then we also check whether a PUD
is completely clear, and free it and clear the PGD entry.
This complicates PGD management, so don't do this. We can keep the
PGD mapped and the PUD table all clear - it's only a single 4K page
per 512 GB of memory mapped.
Cc: A
The memory hotplug code uses sync_global_pgds() to synchronize updates
to the global (&init_mm) kernel PGD and the task PGDs. It does this
by iterating over the pgd_list - which list closely tracks task
creation/destruction via fork/clone.
But we want to remove this list, so that it does not have
So when memory hotplug removes a piece of physical memory from pagetable
mappings, it also frees the underlying PGD entry.
This complicates PGD management, so don't do this. We can keep the
PGD mapped and the PUD table all clear - it's only a single 4K page
per 512 GB of memory hotplugged.
Cc: An
Add a late PGD init callback to places that allocate a new MM
with a new PGD: copy_process() and exec().
The purpose of this callback is to allow architectures to implement
lockless initialization of task PGDs, to remove the scalability
limit of pgd_list/pgd_lock.
Architectures can opt in to this
Now that the memory hotplug code does not remove PGD entries anymore,
the only users of sync_global_pgds() use it after extending the
PGD.
So remove the 'removed' parameter and simplify the call sites.
Cc: Andrew Morton
Cc: Andy Lutomirski
Cc: Borislav Petkov
Cc: Brian Gerst
Cc: Denys Vlasenk
The vmalloc() code uses vmalloc_sync_all() to synchronize changes to
the global reference kernel PGD to task PGDs in certain rare cases,
like register_die_notifier().
This use seems to be somewhat questionable, as most other vmalloc
page table fixups are vmalloc_fault() driven, but nevertheless
it
xen_mm_pin_all()/unpin_all() are used to implement full guest instance
suspend/restore. It's a stop-all method that needs to iterate through
all allocated pgds in the system to fix them up for Xen's use.
This code uses pgd_list, probably because it was an easy interface.
But we want to remove the
The 32-bit x86 PAT code uses __set_pmd_pte() to update pmds.
This uses pgd_list currently, but we don't need the global
list as we can walk the task list under RCU.
(This code already holds the pgd_lock.)
Cc: Andrew Morton
Cc: Andy Lutomirski
Cc: Borislav Petkov
Cc: Brian Gerst
Cc: Denys Vla
Nothing uses the pgd_list anymore - remove the list itself and its helpers.
Cc: Andrew Morton
Cc: Andy Lutomirski
Cc: Borislav Petkov
Cc: Brian Gerst
Cc: Denys Vlasenko
Cc: H. Peter Anvin
Cc: Linus Torvalds
Cc: Oleg Nesterov
Cc: Peter Zijlstra
Cc: Rik van Riel
Cc: Thomas Gleixner
Cc: Wa
The fork()/exit() code uses pgd_alloc()/pgd_free() to allocate/deallocate
the PGD, with platform specific code setting up kernel pagetables.
The x86 code uses a global pgd_list with an associated lock to update
all PGDs of all tasks in the system synchronously.
The lock is still kept to synchroni
Add MMC_CAP_RUNTIME_RESUME support to save resume time
Drop unnecessary SDC_ARG write
Signed-off-by: Chaotian Jing
---
drivers/mmc/host/mtk-sd.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mmc/host/mtk-sd.c b/drivers/mmc/host/mtk-sd.c
index 7153500..b2e89d3 100644
On Mon, Sep 21, 2015 at 02:51:48PM -0500, Felipe Balbi wrote:
> Hi Greg,
>
> Here's another pull request for the current -rc cycle. It's based off of
> greg/usb-linus for this cycle because the previous pull request hasn't
> reached v4.3-rc2.
>
> This time I couldn't boot test all patches (specia
On Mon, Sep 21, 2015 at 12:19:03PM -0700, Linus Torvalds wrote:
> On Thu, Sep 17, 2015 at 2:00 AM, Simon Horman
> wrote:
> >
> > Please consider these SH drivers updates for v4.3.
>
> Hmm. This was caught as spam by google, along with the two patches you
> sent separately.
>
> I'm not quite sure
David Rientjes wrote:
> Your proposal, which I mostly agree with, tries to kill additional
> processes so that they allocate and drop the lock that the original victim
> depends on. My approach, from
> http://marc.info/?l=linux-kernel&m=144010444913702, is the same, but
> without the killing.
Doug Ledford will be handling all the patches related to
drivers/staging/rdma/. Patches for those files are not to be sent to
Greg and devel mailing list.
Signed-off-by: Sudip Mukherjee
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index cf1a98d..9
On Tue, 2015-09-15 at 07:38 +0530, Raghavendra K T wrote:
>
> ... nothing
Sure this patch looks obvious, but please give me a changelog that proves
you've thought about it thoroughly.
For example is it OK to use for_each_node() at this point in boot? Is there any
historical reason why we did it w
Hi Russell,
2015-09-22 4:38 GMT+09:00 Russell King - ARM Linux :
> On Fri, Sep 18, 2015 at 01:37:32PM +0900, Masahiro Yamada wrote:
>> +/**
>> + * __uniphier_cache_maint_common - run a queue operation for a particular
>> level
>> + *
>> + * @data: cache controller specific data
>> + * @start: st
On 09/21/2015 09:14 PM, Jarod Wilson wrote:
Alexander Duyck wrote:
On 09/21/2015 10:11 AM, Jarod Wilson wrote:
Some pci changes upcoming in 4.3 seem to cause additional disconnects,
which can happen at unfortuitous times for igb, leading to issues
such as
this, where the disconnect happened jus
On 9/21/15 9:14 PM, Jarod Wilson wrote:
> Just switching to adapter->io_addr everywhere seems to not work as
> noted above. :\ Note that I'm also chasing this from the other end
> with the author of the pci patches that seem to have triggered this,
> so the real bug might be over in pci-land, bu
On Tue, Sep 22, 2015 at 02:39:36AM +0200, Javier Martinez Canillas wrote:
> The driver is using -1 instead of the -ENOMEM defined macro to specify
> that a buffer allocation failed. Since the error number is propagated,
> the caller will get a -EPERM which is the wrong error condition.
Just a littl
On 09/21/2015 07:49 AM, Juergen Gross wrote:
On 09/15/2015 06:50 PM, Dario Faggioli wrote:
On Thu, 2015-08-20 at 20:16 +0200, Juergen Groß wrote:
On 08/18/2015 05:55 PM, Dario Faggioli wrote:
Hey everyone,
So, as a followup of what we were discussing in this thread:
[Xen-devel] PV-vNUMA i
Hi Richard,
On Tue, Sep 22, 2015 at 12:09 AM, Richard Cochran
wrote:
> On Mon, Sep 21, 2015 at 11:19:32PM +0530, Harini Katakam wrote:
>> Ping
>
> 1) trim your replies
>
> 2) put the PTP maintainer on PTP patches for review
>
I'm sorry I missed that. Will do so in the future.
Regards,
Harini
--
Alexander Duyck wrote:
On 09/21/2015 10:11 AM, Jarod Wilson wrote:
Some pci changes upcoming in 4.3 seem to cause additional disconnects,
which can happen at unfortuitous times for igb, leading to issues such as
this, where the disconnect happened just before igb_configure_tx_ring():
[ 414.4401
Hi all,
Changes since 20150921:
I used the h8300 tree from next-20150828 since the current tree has been
rebased onto something very old :-(
The sound-asoc tree lost its build failure.
The net-next tree inherited the bluetooth tree build failure.
Non-merge commits (relative to Linus'
> -Original Message-
> From: Wood Scott-B07421
> Sent: Tuesday, September 22, 2015 11:25 AM
> To: Zhao Qiang-B45475
> Cc: linux-kernel@vger.kernel.org; linuxppc-...@lists.ozlabs.org;
> lau...@codeaurora.org; Xie Xiaobo-R63061; b...@kernel.crashing.org; Li
> Yang-Leo-R58472; pau...@samba.or
Hi,
On Mon, Sep 21, 2015 at 10:21:31AM +0100, Felipe Tonello wrote:
> Hi Balbi,
>
> On Fri, Sep 18, 2015 at 6:36 PM, wrote:
> > From: "Felipe F. Tonello"
> >
> > f_midi is not checking whether there is an error on usb_ep_queue
> > request, ignoring potential problems, such as memory leaks.
> >
From: Stephen Rothwell
Date: Tue, 22 Sep 2015 11:20:15 +1000
> From: Stephen Rothwell
> Subject: drivers/net/ieee802154/at86rf230.c: seq_printf() now returns NULL
>
> Signed-off-by: Stephen Rothwell
> Cc: Alexander Aring
> Cc: Stefan Schmidt
> Cc: Marcel Holtmann
> Signed-off-by: Andrew Mor
On Mon, Sep 21, 2015 at 02:20:22PM -0400, Tejun Heo wrote:
>
> store_release and load_acquire are different from the usual memory
> barriers and can't be paired this way. You have to pair store_release
> and load_acquire. Besides, it isn't a particularly good idea to
OK I've decided to drop the
On Mon, Sep 21, 2015 at 7:43 PM, Meelis Roos wrote:
>
>
> Yes, sorry - I applied the last chunk by hand because it was mangled by
> the web UI, and added ti to a wrong struct.
>
> Now I tested it on top of 4.3.0-rc1. COmpiles, rebooted fine 6 times,
> but now it hangs again, seems to be the same m
After commit 3d39ac538629e4f00a6e1c38d46346f1b8e69505 ("perf machine:
No need to have two DSOs lists"), perf probe with module short name doesn't
work again. For example:
# lsmod | grep e1000e
e1000e233472 0
# cat /proc/modules | grep e1000e
e1000e 233472 0 - Live 0xa
On 9/21/15 9:16 PM, Yunlong Song wrote:
[Problem Background]
We want to run perf in daemon mode and collect the traces when the exception
(e.g., machine crashes, app performance goes down) appears. Perf may run for a
long time (from days to weeks or even months), since we do not know when the
ex
On Mon, 2015-09-21 at 22:22 -0500, Zhao Qiang-B45475 wrote:
> On Tue, Sep 22, 2015 at 11:08AM +0800, Wood Scott-B07421 wrote:
>
> > -Original Message-
> > From: Wood Scott-B07421
> > Sent: Tuesday, September 22, 2015 11:08 AM
> > To: Zhao Qiang-B45475
> > Cc: linux-kernel@vger.kernel.org;
On Tue, Sep 22, 2015 at 11:08AM +0800, Wood Scott-B07421 wrote:
> -Original Message-
> From: Wood Scott-B07421
> Sent: Tuesday, September 22, 2015 11:08 AM
> To: Zhao Qiang-B45475
> Cc: linux-kernel@vger.kernel.org; linuxppc-...@lists.ozlabs.org;
> lau...@codeaurora.org; Xie Xiaobo-R63061;
[Problem Background]
We want to run perf in daemon mode and collect the traces when the exception
(e.g., machine crashes, app performance goes down) appears. Perf may run for a
long time (from days to weeks or even months), since we do not know when the
exception will appear at all, however it wil
On 09/22/2015 05:36 AM, Jacob Pan wrote:
On Mon, 21 Sep 2015 11:48:14 +0800
Pengyu Ma wrote:
On 09/18/2015 11:43 PM, Jacob Pan wrote:
On Fri, 18 Sep 2015 02:09:55 +0200
"Rafael J. Wysocki" wrote:
On Thursday, September 17, 2015 03:31:41 PM Pengyu Ma wrote:
iosf_mbi is supported on Quar
On Fri, Sep 18, 2015 at 12:14:02AM +0200, Luis de Bethencourt wrote:
> This platform driver has a OF device ID table but the OF module
> alias information is not created so module autoloading won't work.
>
> Signed-off-by: Luis de Bethencourt
Acked-by: Andrew Lunn
Thanks
Andrew
> ---
Hi folks,
I'm seeing hangs like this when using DAX on XFS on 4.3-rc1 running
xfstests generic/075 (fsx test):
# echo w > /proc/sysrq-trigger
[71628.984872] sysrq: SysRq : Show Blocked State
[71628.985988] taskPC stack pid father
[71628.987635] fsx D 88
On Mon, 2015-09-21 at 22:06 -0500, Zhao Qiang-B45475 wrote:
> On Tue, Sep 22, 2015 at 10:26AM +0800, Wood Scott-B07421 wrote:
>
> > -Original Message-
> > From: Wood Scott-B07421
> > Sent: Tuesday, September 22, 2015 10:26 AM
> > To: Zhao Qiang-B45475
> > Cc: linux-kernel@vger.kernel.org;
On Tue, Sep 22, 2015 at 10:26AM +0800, Wood Scott-B07421 wrote:
> -Original Message-
> From: Wood Scott-B07421
> Sent: Tuesday, September 22, 2015 10:26 AM
> To: Zhao Qiang-B45475
> Cc: linux-kernel@vger.kernel.org; linuxppc-...@lists.ozlabs.org;
> lau...@codeaurora.org; Xie Xiaobo-R63061;
This patch fix typos found in Documentation/filesystems.xml,
DocBook/filesystems/API-eventfd-signal.html, and
DocBook/filesystems.aux.xml
These files are generated from comments within the source,
so I had to fix typos in fs/eventfd.c
Signed-off-by: Masanari Iida
---
fs/eventfd.c | 4 ++--
1 fi
Signed-off-by: Shrikrishna Khare
Signed-off-by: Bhavesh Davda
Acked-by: Srividya Murali
---
drivers/net/vmxnet3/vmxnet3_ethtool.c | 118 ++
drivers/net/vmxnet3/vmxnet3_int.h | 4 +-
2 files changed, 92 insertions(+), 30 deletions(-)
diff --git a/drivers/ne
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Monday, September 21, 2015 1:45 PM
> To: KY Srinivasan
> Cc: o...@aepfle.de; jasow...@redhat.com; linux-kernel@vger.kernel.org;
> Jake Oshins ; a...@canonical.com;
> de...@linuxdriverproject.org
> Subject: R
On Mon, 2015-09-21 at 21:23 -0500, Zhao Qiang-B45475 wrote:
> On Tue, Sep 22, 2015 at 06:54AM +0800, Wood Scott-B07421 wrote:
> > -Original Message-
> > From: Wood Scott-B07421
> > Sent: Tuesday, September 22, 2015 6:54 AM
> > To: Zhao Qiang-B45475
> > Cc: linux-kernel@vger.kernel.org; linu
On Tue, Sep 22, 2015 at 06:54AM +0800, Wood Scott-B07421 wrote:
> -Original Message-
> From: Wood Scott-B07421
> Sent: Tuesday, September 22, 2015 6:54 AM
> To: Zhao Qiang-B45475
> Cc: linux-kernel@vger.kernel.org; linuxppc-...@lists.ozlabs.org;
> lau...@codeaurora.org; Xie Xiaobo-R63061; b
On 09/10/2015 03:22 PM, Eric Anholt wrote:
> These will be used for enabling UART1, SPI1, and SPI2.
> diff --git a/arch/arm/boot/dts/bcm2835.dtsi b/arch/arm/boot/dts/bcm2835.dtsi
> + aux_clocks: aux-clocks@0x7e215004 {
> + compatible = "brcm,bcm2835-aux-clock";
> +
On 09/10/2015 03:22 PM, Eric Anholt wrote:
> These will be used for enabling UART1, SPI1, and SPI2.
Patches 1, 3,
Acked-by: Stephen Warren
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http:
On 09/10/2015 03:22 PM, Eric Anholt wrote:
> There are a pair of SPI masters and a mini UART that were last minute
> additions. As a result, they didn't get integrated in the same way as
> the other gates off of the VPU clock in CPRMAN.
> diff --git a/drivers/clk/bcm/clk-bcm2835-aux.c
> b/driver
FYI, we noticed the below changes on
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 50a2a3b246149d041065a67ccb3e98145f780a2f ("sched/fair: Have
task_move_group_fair() unconditionally add the entity load to the runqueue")
===
On 09/10/2015 02:58 PM, Eric Anholt wrote:
> This will give us the ability to set the pixel and HDMI state machine
> clocks for the VC4 KMS driver, change the CPU frequency, and
> potentially gate clocks in the future (once we also write a power
> domain driver). It also gives the uart an explicit
On 09/10/2015 02:58 PM, Eric Anholt wrote:
> Previously we've only supported a few fixed clocks based on
> assumptions about how the firmware sets up the clocks, but this
> binding will let us control the actual (audio power domain) clock
> manager.
Patches 1 and 2,
Acked-by: Stephen Warren
--
To
On 09/10/2015 02:58 PM, Eric Anholt wrote:
> This adds support for enabling, disabling, and setting the rate of the
> audio domain clocks. It will be necessary for setting the pixel clock
> for HDMI in the VC4 driver and let us write a cpufreq driver. It will
> also improve compatibility with use
On Mon, Sep 21, 2015 at 11:43:16PM +0200, Andreas Gruenbacher wrote:
> 2015-09-18 21:35 GMT+02:00 J. Bruce Fields :
> > On Sat, Sep 05, 2015 at 12:27:16PM +0200, Andreas Gruenbacher wrote:
> >> The POSIX standard puts processes which are not the owner or a member in
> >> the owning group or which m
On Mon, Sep 21, 2015 at 11:19:59PM +0200, Andreas Gruenbacher wrote:
> 2015-09-18 20:40 GMT+02:00 J. Bruce Fields :
> > On Sat, Sep 05, 2015 at 12:27:10PM +0200, Andreas Gruenbacher wrote:
> >> Automatic Inheritance (AI) allows changes to the acl of a directory to
> > In the above "file" sometimes
This patch add MMC_TIMING_UHS_SDR12 and MMC_TIMING_UHS_SDR25
for mmc_ios_show to show the ios->timing if mmc card runs under
these two mode.
Signed-off-by: Shawn Lin
---
drivers/mmc/core/debugfs.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/mmc/core/debugfs.c b/drivers/mmc
On 2015/9/22 9:29, trick wong wrote:
In the correct path,this buf will used later.why freed?
right.
sorry for this noise, withdraw this patch[1/3].
2015-09-22 9:18 GMT+08:00 Shawn Lin mailto:shawn@rock-chips.com>>:
buf allocated isn't been freed before return, so we fix it.
Fix
This patch add ios->drv_type for mmc_ios_show to show the
card's driver type.
Signed-off-by: Shawn Lin
---
drivers/mmc/core/debugfs.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/drivers/mmc/core/debugfs.c b/drivers/mmc/core/debugfs.c
index 31155e8..5243e5f 100644
--
On Tue, 22 Sep 2015, Rafael J. Wysocki wrote:
> On Monday, September 21, 2015 10:34:54 AM Alan Stern wrote:
> > On Mon, 21 Sep 2015, Thierry Reding wrote:
> >
> > > > > Force-removing drivers that depend on a device that's being unbound
> > > > > would be a possibility to solve the problem where
buf allocated isn't been freed before return, so we fix it.
Fixes: 736bb6bb01a ("mmc: Add Extended CSD register to debugfs")
Signed-off-by: Shawn Lin
---
drivers/mmc/core/debugfs.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mmc/core/debugfs.c b/drivers/mmc/core/debugfs.c
index
Hi Gustavo,
On Mon, 14 Sep 2015 10:22:34 +1000 Stephen Rothwell
wrote:
>
> On Mon, 14 Sep 2015 10:14:28 +1000 Stephen Rothwell
> wrote:
> >
> > I applied the patches that Andrew has had in his post merge series
> > (but I think you were sent a rolled up version):
>
> Actually it was sent by A
On 09/21/2015 08:34 AM, Kirill A. Shutemov wrote:
Guenter Roeck wrote:
On 09/18/2015 07:53 AM, Jesper Nilsson wrote:
On Fri, Sep 18, 2015 at 05:25:07PM +0300, Kirill A. Shutemov wrote:
On Thu, Sep 17, 2015 at 09:29:27AM -0700, Guenter Roeck wrote:
Hi,
my crisv32 qemu test fails with next-201
hout any indication of the request being truncated...
@Andy, I presume this is only on your -next, can you update the commit?
Or do you want a patch for it?
With this tiny change what we have on next-20150921 seems to work fine.
Regards,
Bjorn
--
To unsubscribe from this list: sen
On Mon, Sep 21, 2015 at 4:21 PM, Lee Jones wrote:
> The $SUBJECT is not correct.
>
>> The driver handles wakeup irq correctly using irq_set_irq_wake. There's
>> no need to use IRQF_NO_SUSPEND while registering the interrupt.
>>
>> This patch removes the use of IRQF_NO_SUSPEND flag.
>>
>> Cc: Samue
> So either:
>
> Proceed with guest solution:
> -> Make sure the overflow can't happen (and write down why not in the
> code). Don't assume a small delta between kvmclock values of vcpus.
> -> Handle stable -> non-stable kvmclock transition.
> -> kvmclock counts from zero should not depend on stab
On Mon, Sep 21, 2015 at 9:02 AM, Tomeu Vizoso
wrote:
> When adding platform and AMBA devices, set the device node's device
> member to point to it.
>
> This speeds lookups considerably and is safe because we only create one
> of these devices for any given device node.
>
> Signed-off-by: Tomeu Viz
The driver is using -1 instead of the -ENOMEM defined macro to specify
that a buffer allocation failed. Since the error number is propagated,
the caller will get a -EPERM which is the wrong error condition.
Also, the smatch tool complains with the following warning:
dgap_parsefile() warn: returni
When perf creates a new child to profile, the events are enabled on
exec(). And in this case, it doesn't synthesize any event for the
child since they'll be generated during exec(). But there's an window
between the enabling and the event generation.
It used to be overcome since samples are only
Hi,
On Mon, Sep 21, 2015 at 10:51 AM, Thierry Reding
wrote:
> On Sat, Sep 19, 2015 at 01:07:56AM +0200, Rafael J. Wysocki wrote:
>> On Fri, Sep 18, 2015 at 5:55 PM, Thierry Reding
>> wrote:
> [...]
>> > Of course there's still the matter of some types of devices physically
>> > disappearing (US
Thank you Paul! That's exactly the issue I met. I've read the whole
thread and got a general idea of the issue.
I try to summarize it and please correct me if I'm wrong:
1. The issue is the result of kill_bdev() when connection has been cut
when IO is still flying.
2. Other block devices driver d
On Mon, Sep 21, 2015 at 2:24 PM, Constantine Shulyupin
wrote:
> On Mon, Sep 21, 2015 at 4:51 AM, Rob Herring wrote:
>> On Fri, Sep 18, 2015 at 5:36 PM, Constantine Shulyupin
>> wrote:
>>> Hi,
>>>
>>> I am designing DT support for a hwmon chip.
>>> It has some sensors, each of them can be:
>>> -
On Mon, Sep 14, 2015 at 11:59 PM, tip-bot for Jiri Olsa
wrote:
> Commit-ID: 60a1133a5b39738671eff1e4d77bedc1ee3fa528
> Gitweb: http://git.kernel.org/tip/60a1133a5b39738671eff1e4d77bedc1ee3fa528
> Author: Jiri Olsa
> AuthorDate: Wed, 2 Sep 2015 09:56:44 +0200
> Committer: Arnaldo Carvalh
Hi Arnaldo,
On Mon, Sep 21, 2015 at 04:39:26PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Sep 21, 2015 at 09:26:49AM +0900, Namhyung Kim escreveu:
> > When perf creates a new child to profile, the events are enabled on
> > exec(). And in this case, it doesn't synthesize any event for the
>
On Thu, 17 Sep 2015, Sasha Levin wrote:
> Hi all,
>
> I've observed the following warning while fuzzing with trinity inside a KVM
> tools
> guest running -next:
>
> [1385507.811807] Out of memory (oom_kill_allocating_task): Kill process 22593
> (ksm04) score 0 or sacrifice child
> [1385507.815
On Sun, Sep 13, 2015 at 02:14:54PM +0200, Julia Lawall wrote:
> Remove unneeded NULL test.
>
> The semantic patch that makes this change is as follows:
> (http://coccinelle.lip6.fr/)
>
> //
> @@ expression x; @@
> -if (x != NULL)
> \(kmem_cache_destroy\|mempool_destroy\|dma_pool_destroy\)(x);
On Mon, Sep 21, 2015 at 11:07:20AM -0400, Murali Karicheri wrote:
> On 09/19/2015 08:53 AM, Kyle McMartin wrote:
> >On Fri, Sep 18, 2015 at 11:43:02AM -0400, Murali Karicheri wrote:> >>+
> >>Dear firmware maintainer,
> >>
> >>Could you please review this patch and comment if it requires any change?
On Sat, Sep 19, 2015 at 05:08:55AM +0200, Marek Vasut wrote:
> On Friday, September 18, 2015 at 05:49:25 PM, Cyrille Pitchen wrote:
> > struct spi_nor_xfer_cfg and read_xfer/write_xfer hooks were never used by
> > any driver. Do some cleanup by removing them.
> >
> > Signed-off-by: Cyrille Pitchen
On Monday, September 21, 2015 10:34:54 AM Alan Stern wrote:
> On Mon, 21 Sep 2015, Thierry Reding wrote:
>
> > > > Force-removing drivers that depend on a device that's being unbound
> > > > would be a possibility to solve the problem where consumers depend on a
> > > > device that could physicall
On Mon, 21 Sep 2015, Kirill A. Shutemov wrote:
> On Mon, Sep 21, 2015 at 01:46:00PM +0900, Sergey Senozhatsky wrote:
> > Hi,
> >
> > 4.3.0-rc1-next-20150918
> >
> > [18344.236625] =
> > [18344.236628] [ INFO: inconsistent lock state ]
> > [18344.236633] 4.3.0-rc1-n
On 9/21/2015 4:05 PM, David Miller wrote:
From: Santosh Shilimkar
Date: Sat, 19 Sep 2015 19:04:42 -0400
Even with per bucket locking scheme, in a massive parallel
system with active rds sockets which could be in excess of multiple
of 10K, rds_bin_lookup() workload is siginificant because of sm
From: Andi Kleen
Abstract the printing of shadow metrics. Instead of every
metric calling fprintf directly and taking care of indentation,
use two call backs: one to print metrics and another to
start a new line.
This will allow adding metrics to CSV mode and also
using them for other purposes.
From: Andi Kleen
Instead of every caller deciding whether to call abs or nsec printout
do it all in a single central function. No functional changes.
Signed-off-by: Andi Kleen
---
tools/perf/builtin-stat.c | 50 +++
1 file changed, 20 insertions(+),
From: Andi Kleen
Now that we can modify the metrics printout functions easily,
it's straight forward to support metric printing for interval mode.
All that is needed is to print the time stamp on every new line.
Pass the prefix into the context and print it out.
v2: Move wrong hunk to here.
Sign
From: Andi Kleen
Enable metrics printing in --per-core / --per-socket mode. We need
to save the shadow metrics in a unique place. Always use the first
CPU in the aggregation. Then use the same CPU to retrieve the
shadow value later.
Example output:
% perf stat --per-core -a ./BC1s
Performance
[v4: Addressed all review feedback.]
[v3: Addressed all review feedback. Update manpage for CSV. Various changes
(see individual patches). Remove some more redundant code
in printout callers.]
[v2: Addressed (near) all review feedback. No manpage updates so far.
Add support for --pe
From: Andi Kleen
Now support CSV output for metrics. With the new output callbacks
this is relatively straight forward by creating new callbacks.
The new line callback needs to know the number of fields to skip them
correctly
v2: Split out function argument changes
v3: Reenable metrics for real
On Mon, Sep 21, 2015 at 10:36:40PM +0100, Mark Salyzyn wrote:
> On 09/21/2015 02:09 PM, Will Deacon wrote:
> > On Mon, Sep 21, 2015 at 09:39:50PM +0100, Mark Salyzyn wrote:
> >> Description from commit 45cac65b0fcd
> >> ("readahead: fault retry breaks mmap file read random detection")
> >> . .
From: Andi Kleen
With all the recently added fields in the perf stat CSV output
we should finally document them in the man page. Do this here.
Signed-off-by: Andi Kleen
---
tools/perf/Documentation/perf-stat.txt | 19 +++
1 file changed, 19 insertions(+)
diff --git a/tools/per
From: Andi Kleen
Move the running/noise printing into printout to avoid
duplicated code in the callers.
v2: Merged with other patches. Remove unnecessary hunk.
Readd hunk that ended in earlier patch.
Signed-off-by: Andi Kleen
---
tools/perf/builtin-stat.c | 53 ++---
1 - 100 of 883 matches
Mail list logo
