On Sun, Dec 01, 2013 at 10:26:18AM +0400, Sergei Ianovich wrote:
> +static struct platform_device lp8x4x_device = {
> + .name = "serial8250",
> + .id = PLAT8250_DEV_ACCENT,
You should not re-use the enum value here. The enum is designed as a
method
ARM_PATCH_PHYS_VIRT and AUTO_ZRELADDR has been enabled as default configs
to integrator platform.
Introduction of PHYS_VIRT config as default would enable phy-to-virt and
virt-to-phy translation function at boot and module loading time
and enforce dynamic reallocation of memory. AUTO_ZRELADDR
On 26/11/13 16:45, Konrad Rzeszutek Wilk wrote:
> On Thu, Nov 21, 2013 at 11:09:52AM +, David Vrabel wrote:
>> On 08/11/13 17:38, Konrad Rzeszutek Wilk wrote:
>>> There is a race case where the user does 'poweroff'
>>> and at the same time the system admin does 'xl shutdown'.
>>
>> This isn't
Using destroy_super() in alloc_super() fail path is bad, because:
* It will trigger WARN_ON(!list_empty(>s_mounts)) since s_mounts is
initialized after several 'goto fail's.
* It will call kfree_rcu() to free the super block although kfree() is
obviously enough there.
* The list_lru structure
This reduces the indentation level of do_try_to_free_pages() and removes
extra loop over all eligible zones counting the number of on-LRU pages.
Signed-off-by: Vladimir Davydov
Cc: Johannes Weiner
Cc: Michal Hocko
Cc: Andrew Morton
Cc: Mel Gorman
Cc: Rik van Riel
---
mm/vmscan.c | 57
From: Glauber Costa
I caught myself doing something like the following outside memcg core:
memcg_id = -1;
if (memcg && memcg_kmem_is_active(memcg))
memcg_id = memcg_cache_id(memcg);
to be able to handle all possible memcgs in a sane manner. In particular, the
I need to move memcg_{stop,resume}_kmem_account() and
memcg_caches_array_size() upper since I am going to use them in
per-memcg lrus implementation introduced by the following patches.
These functions are very simple and do not depend on other kmemcg
bits so it is better to keep them on top
Currently in addition to a shrink_control struct shrink_slab() takes two
arguments, nr_pages_scanned and lru_pages, which are used for balancing
slab reclaim versus page reclaim - roughly speaking, shrink_slab() will
try to scan nr_pages_scanned/lru_pages fraction of all slab objects.
However,
Le 01/12/2013 20:38, Guenter Roeck a écrit :
On 11/30/2013 07:33 AM, Christophe Leroy wrote:
Convert mpc8xxx_wdt.c to the new watchdog API.
Signed-off-by: Christophe Leroy
diff -ur a/drivers/watchdog/mpc8xxx_wdt.c
b/drivers/watchdog/mpc8xxx_wdt.c
--- a/drivers/watchdog/mpc8xxx_wdt.c
Using the per-memcg LRU infrastructure introduced by previous patches,
this patch makes dcache and icache shrinkers memcg-aware. To achieve
that, it converts s_dentry_lru and s_inode_lru from list_lru to
memcg_list_lru and restricts the reclaim to per-memcg parts of the lists
in case of memcg
From: Glauber Costa
When a memcg is destroyed, it won't be imediately released until all
objects are gone. This means that if a memcg is restarted with the very
same workload - a very common case, the objects already cached won't be
billed to the new memcg. This is mostly undesirable since a
Hi,
This is the 12th iteration of Glauber Costa's patchset implementing targeted
shrinking for memory cgroups when kmem limits are present. So far, we've been
accounting kernel objects but failing allocations when short of memory. This is
because our only option would be to call the global
From: Glauber Costa
When we delete kmem-enabled memcgs, they can still be zombieing
around for a while. The reason is that the objects may still be alive,
and we won't be able to delete them at destruction time.
The only entry point for that, though, are the shrinkers. The
shrinker interface,
In very low free kernel memory situations, it may be the case that we
have less objects to free than our initial batch size. If this is the
case, it is better to shrink those, and open space for the new workload
then to keep them and fail the new allocations.
In particular, we are concerned with
FS-shrinkers, which shrink dcaches and icaches, keep dentries and inodes
in list_lru structures in order to evict least recently used objects.
With per-memcg kmem shrinking infrastructure introduced, we have to make
those LRU lists per-memcg in order to allow shrinking FS caches that
belong to
Hi, Johannes
I tried to fix the patchset according to your comments, but there were a
couple of places that after a bit of thinking I found impossible to
amend exactly the way you proposed. Here they go:
+static unsigned long
+zone_nr_reclaimable_pages(struct scan_control *sc, struct zone
Sometimes it can be necessary to iterate over all memcgs' lists of the
same memcg-aware LRU. For example shrink_dcache_sb() should prune all
dentries no matter what memory cgroup they belong to. Current interface
to struct memcg_list_lru, however, only allows per-memcg LRU walks.
This patch adds
If a memory cgroup's kmem limit is less than its user memory limit, we
can run into a situation where our allocation fail, but freeing user
pages will buy us nothing. In such scenarios we would like to call a
specialized reclaimer that only frees kernel memory. This patch adds it.
All the magic
From: Glauber Costa
During the past weeks, it became clear to us that the shrinker interface
we have right now works very well for some particular types of users,
but not that well for others. The latter are usually people interested in
one-shot notifications, that were forced to adapt
There is no need passing on a shrink_control struct from
try_to_free_pages() and friends to do_try_to_free_pages() and then to
shrink_zones(), because it is only used in shrink_zones() and the only
fields initialized on the top level is gfp_mask, which always equals to
scan_control.gfp_mask known
From: Glauber Costa
The userspace memory limit can be freely resized down. Upon attempt,
reclaim will be called to flush the pages away until we either reach the
limit we want or give up.
It wasn't possible so far with the kmem limit, since we had no way to
shrink the kmem buffers other than
On Mon, 2 Dec 2013, Thomas Gleixner wrote:
> On Sat, 30 Nov 2013, Francis Moreau wrote:
> > Hello Thomas,
> >
> > Sorry for the delay.
> >
> > On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
> > > On Fri, 29 Nov 2013, Francis Moreau wrote:
> > >> Since it seems to be related to rtsx driver or its
From: Glauber Costa
Each caller of memcg_cache_id ends up sanitizing its parameters in its own way.
Now that the memcg_cache_id itself is more robust, we can consolidate this.
Also, as suggested by Michal, a special helper memcg_cache_idx is used when the
result is expected to be used directly
This patch makes direct reclaim path shrink slabs not only on global
memory pressure, but also when we reach memory cgroup limit. To achieve
that, it introduces a new per-shrinker flag, SHRINKER_MEMCG_AWARE, which
should be set if the shrinker can handle per-memcg reclaim. For such
shrinkers,
From: Glauber Costa
Those structures are only used for memcgs that are effectively using
kmemcg. However, in a later patch I intend to use scan that list
inconditionally (list empty meaning no kmem caches present), which
simplifies the code a lot.
So move the initialization to early kmem
On Mon, 02 Dec 2013, Alexander Shiyan wrote:
>
>
>
> Понедельник, 2 декабря 2013, 10:56 UTC от Lee Jones :
> > On Sat, 30 Nov 2013, Alexander Shiyan wrote:
> >
> > > > On Sat, Nov 30, 2013 at 08:55:37AM +0400, Alexander Shiyan wrote:
> > > > > If this driver being loaded from devicetree, the
Понедельник, 2 декабря 2013, 10:56 UTC от Lee Jones :
> On Sat, 30 Nov 2013, Alexander Shiyan wrote:
>
> > > On Sat, Nov 30, 2013 at 08:55:37AM +0400, Alexander Shiyan wrote:
> > > > If this driver being loaded from devicetree, the pdata is NULL.
> > > > This cause kernel Oops when
Hi,
On Mon, Dec 02, 2013 at 07:33:35PM +0900, Alex Courbot wrote:
> On 11/29/2013 08:57 PM, Heikki Krogerus wrote:
> >Hi,
> >
> >On Thu, Nov 28, 2013 at 05:46:28PM +0900, Alexandre Courbot wrote:
> >>@@ -88,16 +89,20 @@ Note that GPIO_LOOKUP() is just a shortcut to
> >>GPIO_LOOKUP_IDX() where
> > > > > Since currently nobody uses TWL603x platform data and all new
> > > >
> > > > Hmm... when you say nobody, how did you come to this conclusion?
> > > >
> > > > Without digging into it and probably not that relevant, it
> > > > appears there is some references to it in platform data still:
The FTM PWM device can be found on Vybrid VF610 Tower and
Layerscape LS-1 SoCs.
Signed-off-by: Xiubo Li
Signed-off-by: Alison Wang
Signed-off-by: Jingchang Lu
---
I'm sending the RFC patch about the FTM IP block registers read and write
endian fix for comments and more parcticed ideas.
In
> > +Optional properties:
> > + - st,syscfg : Phandle to boot-device system configuration
> > registers
> > + - st,boot-device-reg : Address of the aforementioned boot-device
> > register(s)
> > + - st,boot-device-spi : Expected boot-device value if booted via this
> > device
> > +
Stephen Warren wrote @ Sun, 1 Dec 2013 20:00:09 +0100:
> On 11/29/2013 04:46 AM, Hiroshi Doyu wrote:
> ...
> > Iterating over a property containing a list of phandles with arguments
> > is a common operation for device drivers. This patch adds a new
> > of_property_for_each_phandle_with_args()
Hi,
On Thu, Nov 28, 2013 at 10:37:19PM +, Thierry Reding wrote:
> On Thu, Nov 28, 2013 at 10:25:11PM +0100, Thierry Reding wrote:
> > On Tue, Nov 12, 2013 at 09:36:55AM +0800, Xiubo Li wrote:
> [...]
> > > +static int fsl_pwm_parse_clk_ps(struct fsl_pwm_chip *fpc)
> > > +{
> > > + int ret;
>
Change the format of the platform GPIO lookup tables to make them less
confusing and improve lookup efficiency.
The previous format was a single linked-list that required to compare
the device name and function ID of every single GPIO defined for each
lookup. Switch that to a list of per-device
On Sat, 30 Nov 2013, Davidlohr Bueso wrote:
> On Thu, 2013-11-28 at 12:59 +0100, Peter Zijlstra wrote:
> > On Wed, Nov 27, 2013 at 11:44:38PM -0800, Davidlohr Bueso wrote:
> > > How about both enlarging the table _and_ aligning the buckets? As you
> > > know, increasing the size of the table also
On Mon, Nov 18, 2013 at 05:13:21PM +0800, Bo Shen wrote:
[...]
> diff --git a/drivers/pwm/pwm-atmel.c b/drivers/pwm/pwm-atmel.c
[...]
> +/* Max value for duty and period
Block comments should be of this form:
/*
* Max value ...
* ...
*/
> +static int
On Sat, 30 Nov 2013, Axel Lin wrote:
> Change the device name of the regulator function to the one chosen for
> MODULE_ALIAS. This fixes kernel auto-module loading for the regulator
> function.
>
> Signed-off-by: Axel Lin
> ---
> Hi,
> I don't have the hardware to test, but I think this needs
On Sat, 30 Nov 2013, Alexander Shiyan wrote:
> > On Sat, Nov 30, 2013 at 08:55:37AM +0400, Alexander Shiyan wrote:
> > > If this driver being loaded from devicetree, the pdata is NULL.
> > > This cause kernel Oops when "fsl,mc13xxx-uses-codec" and/or
> > > "fsl,mc13xxx-uses-touch" properties is
On Sat, 30 Nov 2013, Alexander Shiyan wrote:
> If this driver being loaded from devicetree, the pdata is NULL.
> This cause kernel Oops when "fsl,mc13xxx-uses-codec" and/or
> "fsl,mc13xxx-uses-touch" properties is specified.
The original code is pretty gross. This stuff shouldn't be
Hi Dave,
Do you have any plans to take this series?
Peppe already Acked these series
Please let me know if you want me to rebase these patches on any
particular branch.
Thanks,
srini
On 19/11/13 05:24, Giuseppe CAVALLARO wrote:
> On 11/18/2013 12:30 PM, srinivas.kandaga...@st.com wrote:
>>
On 11/29/2013 12:54 AM, Andy Shevchenko wrote:
On Thu, Nov 28, 2013 at 10:46 AM, Alexandre Courbot wrote:
Change the format of the platform GPIO lookup tables to make them less
confusing and improve lookup efficiency.
The previous format was a single linked-list that required to compare
the
On Sat, 30 Nov 2013, Francis Moreau wrote:
> Hello Thomas,
>
> Sorry for the delay.
>
> On 11/29/2013 10:02 AM, Thomas Gleixner wrote:
> > On Fri, 29 Nov 2013, Francis Moreau wrote:
> >> Since it seems to be related to rtsx driver or its upper layer, could
> >> the folks involved in this area
Gu Zheng writes:
> Hi Kristian, Dave,
>
> Could you please help to check whether the following patch can fix this issue?
> Signed-off-by: Gu Zheng
> ---
> fs/aio.c | 28 ++--
> 1 files changed, 10 insertions(+), 18 deletions(-)
>
Ok. I've applied the patch to
Hi All,
On 11/29/2013 10:37 AM, Linus Walleij wrote:
On Tue, Nov 26, 2013 at 8:40 PM, Grygorii Strashko
wrote:
[1] Depends on patch:
"[PATCH 1/2] gpio: davinci: Fix a check for unbanked gpio"
https://lkml.org/lkml/2013/11/8/22
[2] and depends on series from Prabhakar Lad:
"[PATCH v6 0/6]
Hi Joe,
On 12/02/2013 06:48 AM, Joe Perches wrote:
(Adding Jonas Bonn to list as he added the macro in the first place...)
Thanks... ;)
Actually, I think I submitted an even uglier macro called
DECLARE_PCI_DEVICE_TABLE... might have been the first kernel patch I
ever sent? In any case, it
On Sun, Dec 1, 2013 at 12:41 PM, Axel Lin wrote:
> Fix a trivial typo.
>
> Signed-off-by: Axel Lin
Patch applied for fixes, thanks for spotting this!
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
NULL return of kmem_cache_zalloc should be handled in jffs2_alloc_xattr_datum
and jff2_alloc_xattr_ref.
Signed-off-by: Zhouyi Zhou
---
fs/jffs2/malloc.c |4
1 file changed, 4 insertions(+)
diff --git a/fs/jffs2/malloc.c b/fs/jffs2/malloc.c
index 4f47aa2..b8fd651 100644
---
Hello.
> Le 30/11/2013 06:01, Alexander Shiyan a écrit :
> > Locking is performed by regmap API so no additional locking is
> > needed. Nevertheless, keep locking in the ADC conversion routine.
> > This need for keep proper read ADC sequence when calling from adc &
> > touchscreen drivers.
>
>
On 11/29/2013 08:57 PM, Heikki Krogerus wrote:
Hi,
On Thu, Nov 28, 2013 at 05:46:28PM +0900, Alexandre Courbot wrote:
@@ -88,16 +89,20 @@ Note that GPIO_LOOKUP() is just a shortcut to
GPIO_LOOKUP_IDX() where idx = 0.
A lookup table can then be defined as follows:
- struct
Hi Li,
On Mon, Nov 25, 2013 at 2:20 AM, Li Zefan wrote:
> I'll do this after the patch hits mainline, if Tejun doesn't plan to.
Do you have some news about it?
--
William
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
if iopte is NULL, iopte_free should not be called.
Signed-off-by: Zhouyi Zhou
---
drivers/iommu/omap-iommu.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/iommu/omap-iommu.c b/drivers/iommu/omap-iommu.c
index bcd78a7..5155714 100644
---
This is a follow-up with trivial changes per your comments.
Regarding Documentation/devicetree/bindings/vendor-prefixes.txt,
there's already a patch submitted (Mark Rutland requested this):
https://lkml.org/lkml/2013/10/8/451
Applies to next-20131202
drivers/gpi
Hi Mark,
Sorry for delayed response. I was away for some time.
On Friday 15 November 2013 04:53 PM, Mark Rutland wrote:
> On Thu, Nov 14, 2013 at 04:46:36PM +, Sricharan R wrote:
>> Hi Mark,
>>
>> On Thursday 14 November 2013 07:31 PM, Mark Rutland wrote:
>>> On Thu, Nov 14, 2013 at
On Mon, 2013-12-02 at 11:49 +0200, Heikki Krogerus wrote:
> On Mon, Dec 02, 2013 at 01:23:58PM +0400, Sergei Ianovich wrote:
> > On Mon, 2013-12-02 at 11:02 +0200, Heikki Krogerus wrote:
> > > On Sun, Dec 01, 2013 at 10:26:14AM +0400, Sergei Ianovich wrote:
> > > > PXA serial ports have "standard"
Hello everyone,
We are seeing an L0 crash when running nested VMs with high memory
pressure on the host. Specifically, we see this OOPS:
=
[ 4758.702606] general protection fault: [#1] SMP
[ 4758.703986] Modules linked in: netconsole
Use __weak macro instead of __attribute__((weak)).
Signed-off-by: Kamalesh Babulal
---
kernel/sched/clock.c | 2 +-
kernel/sched/core.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/clock.c b/kernel/sched/clock.c
index c3ae1446461c..08c4ea45fbfd 100644
---
NULL return of kvmppc_mmu_hpte_cache_next should be handled
Signed-off-by: Zhouyi Zhou
---
arch/powerpc/kvm/book3s_32_mmu_host.c |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/powerpc/kvm/book3s_32_mmu_host.c
b/arch/powerpc/kvm/book3s_32_mmu_host.c
index 3a0abd2..5fac89d
Hi Kristian, Dave,
Could you please help to check whether the following patch can fix this issue?
Signed-off-by: Gu Zheng
---
fs/aio.c | 28 ++--
1 files changed, 10 insertions(+), 18 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
index 08159ed..fc1fd0a 100644
---
On 12/02/2013 08:49 AM, James Bottomley wrote:
> On Mon, 2013-12-02 at 08:34 +0800, Chen Gang wrote:
>> On 12/02/2013 12:17 AM, Bart Van Assche wrote:
>>> On 11/27/13 03:29, Chen Gang wrote:
the macro "SP" is too common to make conflict with some architectures,
so recommend to add prefix
Alias was missing for SoC of the at91sam9x5 familly that embed USART3.
Preripheral node and pinctrl declarations are already in the
at91sam9x5_usart3.dtsi file.
Reported-by: Jiri Prchal
Signed-off-by: Nicolas Ferre
---
arch/arm/boot/dts/at91sam9g25.dtsi | 4
socketpair() error paths can be simplified to not call
heavy-weight sys_close().
This patch makes socketpair() use of error paths which do not
rely on heavy-weight call to sys_lose(): it's better to try
to push the file descriptor to userspace before installing
the socket file to the file
On Sun, 01 Dec 2013, Olof Johansson wrote:
> Hi,
>
> On Tue, Nov 19, 2013 at 3:07 AM, Lee Jones wrote:
> > In this patch we do two things. Firstly, instead of open coding the
> > store of DMA data in to the DAI for later use, we use the API provided.
> > Secondly we create and store similar DMA
> From: David Miller
>
> > According to Documentation/networking/driver.txt the ndo_start_xmit
> > method should not return NETDEV_TX_BUSY under normal circumstances.
> > Stop the transmit queue when tx_ring is full.
...
> You should be instead preventing the transmit method from being invoked
>
On Mon, 2013-12-02 at 11:08 +0200, ville.syrj...@linux.intel.com wrote:
> From: Ville Syrjälä
>
> Some lower level things get angry if we don't have modeset locks
> during intel_modeset_setup_hw_state(). Actually the resume and
> lid_notify codepaths alreday hold the locks, but the init codepath
On Mon, 2013-12-02 at 08:33 +0100, Daniel Vetter wrote:
> On Sun, Dec 1, 2013 at 5:57 PM, Paul Bolle wrote:
> > The WARNING is now gone during suspend and resume (having tested that
> > thoroughly - ie, twice). But I still see it at boot. Is there a related
> > fix for that WARNING during boot?
>
On Sun, Dec 01, 2013 at 10:11:47AM +, Alex Ling wrote:
> This patch adds "biu" and "ciu" clock names for exynos4412 dwmmc
> node. Without this patch, dwmmc host driver will skip enabling the
> two clocks and it will break dwmmc host function on exynos4412.
> Tested on FriendlyARM TINY4412
On 02.12.2013, at 04:07, Zhouyi Zhou wrote:
> ping
>> I do a grep for kmem_cache_zalloc and kmem_cache_alloc
>> in kernel tree, and find some code do not handle NULL
>> return of kmem_cache_zalloc correctly
>>
>>
>> Signed-off-by: Zhouyi Zhou
Thanks a lot for the patch. I'd assume we
Hi Roger
On Mon, Dec 2, 2013 at 10:39 AM, Roger Quadros wrote:
> +Benoit, Tony, Paul.
>
> Hi Michael,
>
> On 11/30/2013 06:48 AM, Michael Trimarchi wrote:
>> Hi Roger
>>
>> On Fri, Nov 29, 2013 at 2:01 PM, Roger Quadros wrote:
>>> With u-boot 2013.10, USB devices are sometimes not detected
>>>
Le 30/11/2013 06:01, Alexander Shiyan a écrit :
Locking is performed by regmap API so no additional locking is
needed. Nevertheless, keep locking in the ADC conversion routine.
This need for keep proper read ADC sequence when calling from adc &
touchscreen drivers.
You can't do that so easily
Hi,
On Mon, Dec 02, 2013 at 01:23:58PM +0400, Sergei Ianovich wrote:
> On Mon, 2013-12-02 at 11:02 +0200, Heikki Krogerus wrote:
> > On Sun, Dec 01, 2013 at 10:26:14AM +0400, Sergei Ianovich wrote:
> > > PXA serial ports have "standard" UART names (ttyS[0-3]), major
> > > device number (4) and
Binary was written as binay, probably by mistake. Fix it.
Signed-off-by: Viresh Kumar
---
include/linux/tracepoint.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/tracepoint.h b/include/linux/tracepoint.h
index ebeab36..f0c3e4c 100644
---
On Mon, Dec 02, 2013 at 10:49:15AM +0800, Dave Young wrote:
> All these setup_data passing, remapping etc. is mostly for kexec,
> add a lot of contiditional #if #endif makes the code a mess. I would
> prefer to not do this if you are not strongly object.
Right, having efi_kexec.c could solve all
> -Original Message-
> From: Zoltan Kiss
> Sent: 29 November 2013 20:26
> To: Ian Campbell; Wei Liu; xen-de...@lists.xenproject.org;
> net...@vger.kernel.org; linux-kernel@vger.kernel.org; Jonathan Davies;
> Paul Durrant
> Cc: Zoltan Kiss
> Subject: Re: [PATCH net-next] xen-netback: Fix
Michael,
On 11/29/2013 05:32 PM, Michael Trimarchi wrote:
> Hi Roger
>
> On Fri, Nov 29, 2013 at 2:01 PM, Roger Quadros wrote:
>> With u-boot 2013.10, USB devices are sometimes not detected
>> on OMAP4 Panda. To make us independent of what bootloader does
>> with the USB Host module, we must
On Mon, Dec 02, 2013 at 10:59:42AM +0800, Dave Young wrote:
> They are only called if there's setup_data SETUP_EFI passed in. Yes, I
> think only kexec need that part of code. But I hesitated to mess the
> code with a lot of #if. Will think about it.
Well, the accepted strategy with the efi code
+Benoit, Tony, Paul.
Hi Michael,
On 11/30/2013 06:48 AM, Michael Trimarchi wrote:
> Hi Roger
>
> On Fri, Nov 29, 2013 at 2:01 PM, Roger Quadros wrote:
>> With u-boot 2013.10, USB devices are sometimes not detected
>> on OMAP4 Panda. To make us independent of what bootloader does
>> with the
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Monday, December 02, 2013 4:27 PM
> To: linux-fsde...@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; linux-f2fs-de...@lists.sourceforge.net
> Subject: Re: [f2fs-dev] [PATCH v2] f2fs: refactor bio-related
socketpair() use overly complicated and redundant error paths.
This patch makes socketpair() use a single error path,
which do not rely on heavy-weight call to sys_close():
it's better to try to push the file descriptor to userspace
before installing the socket file to the file descriptor,
so
On Sun, Dec 01, 2013 at 04:59:14PM +0100, Stefan Agner wrote:
[...]
This looks pretty good generally. A few minor nits below...
> diff --git a/drivers/regulator/tps6586x-regulator.c
> b/drivers/regulator/tps6586x-regulator.c
[...]
> +#define tps658623_sm2_voltages tps6586x_ldo4_voltages
>
On 12/02/2013 08:53 AM, Namhyung Kim wrote:
Sometimes users might want to see time information along with the
performance result but the perf cannot provide it currently.
In this patchset, I added such feature using sample->time. When the
perf processes sample events, it calculate time info
This patch series adds support to handle interrupt registration/deregistration
in arm64 pmu driver when pmu interrupt type is percpu.
Changelog:
V6:
* In arm64 pmu driver: Use macro 'IRQ_TYPE_NONE' while passing irq type value
to enable_percpu_irq(). Change 'irqs' etc variables as unsigned,
This patch adds an accessor function for IRQ_PER_CPU flag.
The accessor function is useful to determine whether an IRQ is percpu or not.
This patch is based on an older patch posted by Chris Smith here [1].
There is a minor change w.r.t. Chris's original patch: The accessor function
is renamed as
Add support for irq registration when pmu interrupt is percpu.
Signed-off-by: Vinayak Kale
Signed-off-by: Tuan Phan
---
arch/arm64/kernel/perf_event.c | 116 +---
1 file changed, 86 insertions(+), 30 deletions(-)
diff --git a/arch/arm64/kernel/perf_event.c
On 12/02/2013 02:23 AM, David Ahern wrote:
'perf sched timehist' provides an analysis of scheduling events.
Example usage:
perf sched record -- sleep 1
perf sched timehist
By default it shows the individual schedule events, including the time between
sched-in events for the task, the
On Mon, 2013-12-02 at 11:02 +0200, Heikki Krogerus wrote:
> On Sun, Dec 01, 2013 at 10:26:14AM +0400, Sergei Ianovich wrote:
> > PXA serial ports have "standard" UART names (ttyS[0-3]), major
> > device number (4) and first minor device number (64) by default.
> >
> > If the system has extra 8250
Replace RX51 with N900 (RX-51) in user-visible places.
Fix comment style.
Simplify obvious code.
Add a fixme where error is not checked.
Signed-off-by: Pavel Machek
index e7604e5..64f7aca 100644
--- a/drivers/hsi/clients/cmt_speech.c
+++ b/drivers/hsi/clients/cmt_speech.c
@@ -642,7 +642,7
On Sun, Dec 01, 2013 at 04:59:13PM +0100, Stefan Agner wrote:
> Use the VERSIONCRC to determine the exact device version. According to
> the datasheet this register can be used as device identifier. The
> identification is needed since some tps6586x regulators use a different
> voltage table.
>
>
On Nov 29, 2013, at 2:54 PM, David Turner wrote:
> Is this version good, or should I make some more improvements?
The patch looks good to me (you could add a Reviewed-by: line for me if you
want.
What you need to do now is to add a new test case or two to verify that this is
working correctly.
On Mon, 2013-12-02 at 11:06 +0200, Andy Shevchenko wrote:
> > Anyway, if you think you're going to do a lot of
> > transforms of printk("%x", dma_addr_t) with or without
> > (unsigned long long) or (u64) casts, I'll submit a signed
> > patch to Andrew.
>
> I think it worse to submit even if we
On Fri, 2013-11-29 at 14:10 -0800, Joe Perches wrote:
> On Fri, 2013-11-29 at 14:56 +0200, Andy Shevchenko wrote:
> > On Thu, 2013-11-28 at 10:32 -0800, Joe Perches wrote:
[]
> > > https://lkml.org/lkml/2013/9/12/483
> >
> > Hmm... Still not in kernel. Do you know reason why it so?
>
> It was
From: Ville Syrjälä
Some lower level things get angry if we don't have modeset locks
during intel_modeset_setup_hw_state(). Actually the resume and
lid_notify codepaths alreday hold the locks, but the init codepath
doesn't, so fix that.
Signed-off-by: Ville Syrjälä
---
Totally untested, but
From: Dan Carpenter
If this was called with a NULL "dev" then it lead to a NULL dereference
when we called dev_WARN(). I have changed it to WARN_ON() so that we
get a stack dump and can fix the caller.
The rest of this patch is just cleanup like returning directly instead
of having do-nothing
Hi,
On Sun, Dec 01, 2013 at 10:26:14AM +0400, Sergei Ianovich wrote:
> PXA serial ports have "standard" UART names (ttyS[0-3]), major
> device number (4) and first minor device number (64) by default.
>
> If the system has extra 8250 serial port hardware in addition
> to onboard PXA serial
1. Add new supporting declarations to option.c, to support Huawei new devices
with new bInterfaceProtocol value.
Signed-off-by: fangxiaozhi
--- linux-3.12.1/drivers/usb/serial/option.bk 2013-11-29 14:49:44.528970754
+0800
+++
Hi Kim,
> -Original Message-
> From: Jaegeuk Kim [mailto:jaegeuk@samsung.com]
> Sent: Monday, December 02, 2013 4:15 PM
> To: Chao Yu
> Cc: linux-fsde...@vger.kernel.org; linux-kernel@vger.kernel.org;
> linux-f2fs-de...@lists.sourceforge.net; 谭姝
> Subject: RE: [f2fs-dev] [PATCH]
From: Shaohui Xie
Then other generic phy driver such as generic 10g phy driver can join it.
Signed-off-by: Shaohui Xie
---
v2 changes: add break if find a match in unbind.
drivers/net/phy/phy_device.c | 29 +
1 file changed, 21 insertions(+), 8 deletions(-)
diff
In the following patches, to get/set free objects from the freelist
is changed so that simple casting doesn't work for it. Therefore,
introduce helper functions.
Acked-by: Christoph Lameter
Signed-off-by: Joonsoo Kim
diff --git a/mm/slab.c b/mm/slab.c
index e749f75..77f9eae 100644
---
Hi,
On Sun, Dec 01, 2013 at 10:26:18AM +0400, Sergei Ianovich wrote:
> The patch adds support for 3 additional LP-8x4x built-in serial
> ports.
>
> The device can also host up to 8 extension cards with 4 serial ports
> on each card for a total of 35 ports. However, I don't have
> the hardware to
To prepare to implement byte sized index for managing the freelist
of a slab, we should restrict the number of objects in a slab to be less
or equal to 256, since byte only represent 256 different values.
Setting the size of object to value equal or more than newly introduced
SLAB_OBJ_MIN_SIZE
Now, the size of the freelist for the slab management diminish,
so that the on-slab management structure can waste large space
if the object of the slab is large.
Consider a 128 byte sized slab. If on-slab is used, 31 objects can be
in the slab. The size of the freelist for this case would be 31
1101 - 1200 of 2434 matches
Mail list logo
