On Tue, Oct 30, Pasi Kärkkäinen wrote:
> On Tue, Oct 30, 2012 at 05:05:05PM +0100, Olaf Hering wrote:
> > The XenPVHVM extensions have not been tested much on very old
> > hypervisors. At least Xen 3.4 gets some testing with the pvops kernel.
> IIRC upstream Linux PVonHVM drivers do work OK today
> return (TX_RING_SIZE - (bp->tx_head - bp->tx_tail) & (TX_RING_SIZE -
> 1));
Is equivalent to:
return (bp->tx_tail - bp->tx_head) & (TX_RING_SIZE - 1));
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord.
> > > On Tue, Oct 30, 2012 at 02:45:57PM -0400, Sasha Levin wrote:
> > >> +/* Use hash_32 when possible to allow for fast 32bit hashing in 64bit
> > >> kernels. */
> > >> +#define hash_min(val, bits)
> > >> \
> > >> +({
Paul Bolle writes:
> On Wed, 2012-10-31 at 09:49 +0900, OGAWA Hirofumi wrote:
>> This bug is known as the inotify bug. I recall I talked about this,
>> maybe years ago.
>
> Would that be this thread: https://lkml.org/lkml/2011/6/10/155 ?
Sure, exactly.
--
OGAWA Hirofumi
--
To unsubscribe from
Pekka Enberg a écrit :
> Hi,
>
> (Adding more people to CC.)
>
> On Tue, Oct 16, 2012 at 2:17 PM, Matthieu CASTET
> wrote:
>> From: Matthieu CASTET
>>
>> on cortexA8 (omap3) ralign is 64 and __alignof__(unsigned long long) is 8.
>> So we always disable debug.
>>
>> This patch is based on 5c5e3b
On 2012년 10월 31일 15:47, Jonghwan Choi wrote:
> TMU urgently sends active-high signal (thermal trip) to PMU,
> and thermal tripping by hardware logic i.e PMU is performed.
> Thermal tripping means that PMU cut off the whole power of SoC
> by controlling external voltage regulator.
>
> Signed-off-by:
On 2012年10月31日 07:11, Anton Vorontsov wrote:
On Tue, Oct 30, 2012 at 05:30:00PM +0800, yongd wrote:
Sorry for my so late. And eventually these updated patches are here for your
review. Thanks in advance.
For patch 1, add SDHCI_QUIRK_BROKEN_CARD_DETECTION setting for ESDHC_CD_GPIO
type,
or the h
As the synaptics device may not respond to the first command in psmouse_probe
when a machine is booting up, the patch gives a second probe if the first
one fails.
Signed-off-by: Chung-yih Wang
---
drivers/input/mouse/psmouse-base.c | 13 +++--
1 files changed, 11 insertions(+), 2 delet
The kernel doesn't use decimals though.
Joe Perches (3):
checkpatch: Find hex constants as a single IDENT
checkpatch: Add support for decimal constants
checkpatch: Emit a warning when decimal values are used
scripts/checkpatch.pl | 10 +-
1 files changed, 9 insertions(+), 1 delet
Hexadecimal values are currently found in 2 parts.
A hex constant like 0x123456abcdef is found as
0 and then x123456abcdef and later coalesced.
Instead, reverse the order of the 2 searches in
$Constant to find 0x first, then 0 so that the
entire hex constant is found all at once.
Signed-off-by: J
Even though the kernel doesn't support using decimal constants,
add a regex for them.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 099a0ad..3e727c5 100755
--- a/
Linux kernel doesn't like decimals, say so.
Signed-off-by: Joe Perches
---
scripts/checkpatch.pl |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index 3e727c5..3339ecf 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/ch
vpr_info_dq should be a function and vpr_info should have
a do {} while (0)
Add missing newlines to pr_s.
Miscellaneous neatening too.
braces, coalescing formats, alignments, etc...
Signed-off-by: Joe Perches
---
lib/dynamic_debug.c | 118 +++
1
On 2012年10月31日 07:11, Anton Vorontsov wrote:
On Tue, Oct 30, 2012 at 05:30:00PM +0800, yongd wrote:
Sorry for my so late. And eventually these updated patches are here for your
review. Thanks in advance.
For patch 1, add SDHCI_QUIRK_BROKEN_CARD_DETECTION setting for ESDHC_CD_GPIO
type,
or the h
On Tue, 2012-10-30 at 20:52 +0100, Krzysztof Mazur wrote:
>
> --- a/net/atm/pppoatm.c
> +++ b/net/atm/pppoatm.c
> @@ -306,12 +306,9 @@ static int pppoatm_send(struct ppp_channel *chan, struct
> sk_buff *skb)
>
> /*
> * It's not clear that we need to bother with using atm_may_se
Hi Avinash,
On 10/30/2012 10:41 AM, Philip, Avinash wrote:
> On Mon, Oct 29, 2012 at 14:40:02, Philip, Avinash wrote:
>> On Thu, Oct 18, 2012 at 18:56:55, Porter, Matt wrote:
>>> Adds AM33XX SPI support for am335x-bone and am335x-evm.
>
> Matt,
>
> Can you build SPI DT patch with DMA support on
On Wed, Oct 31, 2012 at 10:29:25AM +0100, Olaf Hering wrote:
> On Wed, Oct 31, Ian Campbell wrote:
>
> > If I understand correctly this requirements comes from the need to
> > support moving the shared info page in order to support kexec?
> >
> > So could we do something more fine grained and lim
On Wed, Oct 31, 2012 at 10:41:47AM +0100, Krzysztof Mazur wrote:
>
> I think that we should add a wrapper to vcc->send(), based on
> fixed pppoatm_send(), that performs required checks and takes the ATM socket
> lock.
>
I'm sending initial version of such wrapper and update to pppoatm.
Untested
On Wed, 31 Oct 2012, Paul Gortmaker wrote:
> [[ANNOUNCE] 3.6.4-rt11] On 31/10/2012 (Wed 02:19) Thomas Gleixner wrote:
>
> > Dear RT Folks,
> >
> > I'm pleased to announce the 3.6.4-rt11 release.
>
> The rt11 content is present on master in the 3.6-rt patch repo:
> http://git.kernel.org/?p=lin
On Tue, Oct 30, 2012 at 05:33:56PM -0700, Andi Kleen wrote:
> From: Andi Kleen
>
> This is not arch perfmon, but older CPUs will just ignore it. This makes
> it possible to do at least some TSX measurements from a KVM guest
>
You are ignoring my reviews.
> Cc: a...@redhat.com
> Cc: g...@redhat.
On Wed, 2012-10-31 at 09:29 +, Olaf Hering wrote:
> On Wed, Oct 31, Ian Campbell wrote:
>
> > If I understand correctly this requirements comes from the need to
> > support moving the shared info page in order to support kexec?
> >
> > So could we do something more fine grained and limit only
Even if skb is marked for zero copy, net core might still decide
to copy it later which is somewhat slower than a copy in user context:
besides copying the data we need to pin/unpin the pages.
Add a parameter reporting such cases through zero copy callback:
if this happens a lot, device can take t
Orphaning frags for zero copy skbs needs to allocate data in atomic
context so is has a chance to fail. If it does we currently discard
the skb which is safe, but we don't report anything to the caller,
so it can not recover by e.g. disabling zero copy.
Add an API to free skb reporting such errors
This will be used to disable zerocopy when error rate
is high.
Signed-off-by: Michael S. Tsirkin
---
drivers/vhost/vhost.c | 7 ---
drivers/vhost/vhost.h | 4
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
index 906fd9f..5aff
When tun transmits a zero copy skb, it orphans the frags
which might need to allocate extra memory, in atomic context.
If that fails, notify ubufs callback before freeing the skb
as a hint that device should disable zerocopy mode.
Signed-off-by: Michael S. Tsirkin
---
drivers/net/tun.c | 1 +
1
Better document macros for DMA tracking. Add an
explicit one for DMA in progress instead of
relying on user supplying len != 1.
Signed-off-by: Michael S. Tsirkin
---
drivers/vhost/net.c | 3 ++-
drivers/vhost/vhost.c | 2 +-
drivers/vhost/vhost.h | 12 +---
3 files changed, 12 insert
Zerocopy handling code is vhost-net specific.
Move it from vhost.c/vhost.h out to net.c
Signed-off-by: Michael S. Tsirkin
---
drivers/vhost/net.c | 45
drivers/vhost/tcm_vhost.c | 1 +
drivers/vhost/vhost.c | 53 +++-
Some driver uses tasklet_disable in device remove/close process,
tasklet_disable will inc tasklet->count and return. If the tasklet
is not handled yet because some softirq pressure, the tasklet will
placed on the tasklet_vec, never have a chance to excute. This might
lead to ksoftirqd heavy loaded,
Even when vhost-net is in zero-copy transmit mode,
net core might still decide to copy the skb later
which is somewhat slower than a copy in user
context: data copy overhead is added to the cost of
page pin/unpin. The result is that enabling tx zero copy
option leads to higher CPU utilization for g
On 10/31/2012 03:05 AM, Rick Jones wrote:
On 10/30/2012 03:03 AM, Jason Wang wrote:
Hi all:
This series is an update version of multiqueue virtio-net driver
based on
Krishna Kumar's work to let virtio-net use multiple rx/tx queues to
do the
packets reception and transmission. Please review a
It seems that to avoid deadlocks it is enough to poll vq before
we are going to use the last buffer. This is faster than
c70aa540c7a9f67add11ad3161096fb95233aa2e.
Signed-off-by: Michael S. Tsirkin
---
drivers/vhost/net.c | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
di
tun supports zero copy transmit since 0690899b4d4501b3505be069b9a687e68ccbe15b,
however you can only enable this mode if you know your workload does not
trigger heavy guest to host/host to guest traffic - otherwise you
get a (minor) performance regression.
This patchset addresses this problem by n
On Wed, Oct 31, 2012 at 12:27:01PM +0200, Gleb Natapov wrote:
> On Tue, Oct 30, 2012 at 05:33:56PM -0700, Andi Kleen wrote:
> > From: Andi Kleen
> >
> > This is not arch perfmon, but older CPUs will just ignore it. This makes
> > it possible to do at least some TSX measurements from a KVM guest
>
Some driver uses tasklet_disable in device remove/release process,
tasklet_disable will inc tasklet->count and return. If the tasklet
is not handled yet under some softirq pressure, the tasklet will be
placed on the tasklet_vec, never have a chance to be excuted. This might
lead to a heavy loaded k
On Monday 29 October 2012 09:44 PM, Mark Brown wrote:
* PGP Signed by an unknown key
On Mon, Oct 29, 2012 at 09:33:33AM +, Charles Keepax wrote:
regulator_put function was called whilst holding the
regulator_list_mutex, which is also locked from regulator_put. This
causes deadlock when fail
On 10/31/2012 11:16 AM, Benoit Cousson wrote:
> Hi Avinash,
>
> On 10/30/2012 10:41 AM, Philip, Avinash wrote:
>> On Mon, Oct 29, 2012 at 14:40:02, Philip, Avinash wrote:
>>> On Thu, Oct 18, 2012 at 18:56:55, Porter, Matt wrote:
Adds AM33XX SPI support for am335x-bone and am335x-evm.
>>
>> M
On 10/22/2012 08:57 AM, Kirill A. Shutemov wrote:
> From: "Kirill A. Shutemov"
>
> It's non-sense to use tristate for the option, it's bool.
>
Good point.
Applied to fixes-togreg branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
Thanks,
Jonathan
> Signed-off-by: Kirill A
Hi!
> Linux kernel doesn't like decimals, say so.
?!
Linux surely supports decimal constants, like "100". Did you mean
"octal"?
If you wanted to add warning for something... I never want to see
#define CRAPPY_EMBEDDED_REGISTER ((0x1) << (0))
again
On Wed, Oct 31, 2012 at 11:32:48AM +0100, Andi Kleen wrote:
> On Wed, Oct 31, 2012 at 12:27:01PM +0200, Gleb Natapov wrote:
> > On Tue, Oct 30, 2012 at 05:33:56PM -0700, Andi Kleen wrote:
> > > From: Andi Kleen
> > >
> > > This is not arch perfmon, but older CPUs will just ignore it. This makes
>
Some driver uses tasklet_disable in device remove/release process,
tasklet_disable will inc tasklet->count and return. If the tasklet
is not handled yet under some softirq pressure, the tasklet will be
placed on the tasklet_vec, never have a chance to be excuted. This might
lead to a heavy loaded k
2012/10/31 Dongsheng Song :
> Hi,
Hi, friend
>
> There have some misleading in the translation:
>
> origin
> User space is expected to bypass those helpers and implement those things
> inline (either in the code emitted directly by
Some driver uses tasklet_disable in device remove/release process,
tasklet_disable will inc tasklet->count and return. If the tasklet
is not handled yet under some softirq pressure, the tasklet will be
placed on the tasklet_vec, never have a chance to be excuted. This might
lead to a heavy loaded k
Some driver uses tasklet_disable in device remove/release process,
tasklet_disable will inc tasklet->count and return. If the tasklet
is not handled yet under some softirq pressure, the tasklet will be
placed on the tasklet_vec, never have a chance to be excuted. This might
lead to a heavy loaded k
Some driver uses tasklet_disable in device remove/release process,
tasklet_disable will inc tasklet->count and return. If the tasklet
is not handled yet under some softirq pressure, the tasklet will be
placed on the tasklet_vec, never have a chance to be excuted. This might
lead to a heavy loaded k
Hi Greg,
2012/10/27 0:25, Greg Kroah-Hartman wrote:
On Fri, Oct 26, 2012 at 04:33:49PM +0900, Yasuaki Ishimatsu wrote:
Hi Greg,
Sorry for late reply.
2012/10/20 2:59, Greg Kroah-Hartman wrote:
On Fri, Oct 19, 2012 at 06:29:52AM +0200, Rafael J. Wysocki wrote:
On Thursday 11 of October 2012
Some driver uses tasklet_disable in device remove/release process,
tasklet_disable will inc tasklet->count and return. If the tasklet
is not handled yet under some softirq pressure, the tasklet will be
placed on the tasklet_vec, never have a chance to be excuted. This might
lead to a heavy loaded k
On Wed, Oct 31, 2012 at 12:20:04AM +0800, Tekkaman Ninja wrote:
> This is a Chinese translated version of
> Documentation/arm/kernel_user_helpers.txt
>
> Signed-off-by: Fu Wei
[...]
> +If you have any comment or update to the content, please contact the
> +original document maintainer directly.
On Tue, Oct 30, 2012 at 03:03:49PM -0400, Theodore Ts'o wrote:
> On Wed, Oct 31, 2012 at 12:20:04AM +0800, Tekkaman Ninja wrote:
> > This is a Chinese translated version of
> > Documentation/arm/kernel_user_helpers.txt
> >
> > Signed-off-by: Fu Wei
>
> I wonder if it woiuld be a good idea to not
On Wed, Oct 31, 2012 at 16:05:13, Cousson, Benoit wrote:
>
> On 10/31/2012 11:16 AM, Benoit Cousson wrote:
> > Hi Avinash,
> >
> > On 10/30/2012 10:41 AM, Philip, Avinash wrote:
> >> On Mon, Oct 29, 2012 at 14:40:02, Philip, Avinash wrote:
> >>> On Thu, Oct 18, 2012 at 18:56:55, Porter, Matt wrot
On Wed, Oct 31, 2012 at 12:34:45AM -0500, Daniel Santos wrote:
> Yes, the __build_bug_on_failed message is much more informative. This
> will only increase with these patches. For example, the line
>
> BUILD_BUG_ON(sizeof(*c) != 4);
>
> emits this error:
>
> arch/x86/kernel/cpu/amd.c: In funct
Add McSPI data node to AM33XX device tree file. The McSPI module (and so
as the driver) is reused from OMAP4.
Signed-off-by: Philip, Avinash
Tested-by: Matt Porter
---
Changes since v2:
- Commit message corrected.
- Rebase on top of for_3.8/dts
Changes since v1:
- Correc
Hi Afzal,
On 10/30/2012 10:34 AM, Afzal Mohammed wrote:
> Add am33xx rtc node.
>
> Signed-off-by: Afzal Mohammed
> ---
> Hi Benoit,
>
> This is based on your for_3.8/dts branch.
I've just applied it in the branch with a slight change in the subject.
Thanks,
Benoit
>
> This has been tested o
Hi Tang,
2012/10/31 16:27, Tang Chen wrote:
> Hi,
>
> The container hotplug handler container_notify_cb() didn't implement
> the hot-remove functionality. So, these 3 patches implement it like
> the following way:
>
> patch 1. Do not use kacpid_wq/kacpid_notify_wq to handle container hotplug
>
On Wed, 31 Oct 2012 10:11:06 +0200 Janne Kulmala wrote:
> On 10/31/2012 08:52 AM, Andrew Morton wrote:
> > On Wed, 31 Oct 2012 07:30:33 +0100 Stefani Seibold
> > wrote:
> >
> >>> Yes, and I guess the same to give them a 64-element one.
> >>>
>
> If there's absolutely no prospect that
On Tue, 2012-10-30 at 22:23 -0400, Steven Rostedt wrote:
> On Wed, 2012-10-31 at 01:36 +0100, Frederic Weisbecker wrote:
> > 2012/10/30 anish kumar :
> > > As I understand without the memory barrier proposed by you the situation
> > > would be as below:
> > > CPU 0 C
On Tue, 2012-10-30 at 14:45 -0400, Steven Rostedt wrote:
> On Wed, 2012-10-31 at 03:33 +0900, anish kumar wrote:
>
> > > CPU 0 CPU 1
> > >
> > > data = something flags = IRQ_WORK_BUSY
> > > smp_mb() (implicit with cmpxchg smp_mb()
> > >
Hi Pekka,
On Wed, Oct 31, 2012 at 4:04 AM, Pekka Enberg wrote:
> Hi Ezequiel,
>
> On Thu, Sep 27, 2012 at 8:49 AM, tip-bot for Ezequiel Garcia
> wrote:
>> Commit-ID: 8781915ad2716adcd8cd5cc52cee791fc8b00fdf
>> Gitweb:
>> http://git.kernel.org/tip/8781915ad2716adcd8cd5cc52cee791fc8b00fdf
>>
From: Jan-Simon Möller
The use of variable length arrays in structs (VLAIS) in the Linux Kernel code
precludes the use of compilers which don't implement VLAIS (for instance the
Clang compiler). This patch instead allocates the appropriate amount of memory
using an char array.
Patch from series
From: Jan-Simon Möller
The use of variable length arrays in structs (VLAIS) in the Linux Kernel code
precludes the use of compilers which don't implement VLAIS (for instance the
Clang compiler). This patch instead allocates the appropriate amount of memory
using an char array.
Patch from series
this_cpu_ptr is faster than per_cpu_ptr(p, smp_processor_id()).
The latter helper needs to find the offset for current cpu,
and needs more assembler instructions which objdump shows in following.
per_cpu_ptr(p, smp_processor_id())：
1e: 65 8b 04 25 00 00 00 00 mov%gs:0x0,%eax
26
From: Shan Wei
Signed-off-by: Shan Wei
---
net/core/flow.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/net/core/flow.c b/net/core/flow.c
index e318c7e..3bad824 100644
--- a/net/core/flow.c
+++ b/net/core/flow.c
@@ -327,11 +327,9 @@ static void flow_cache_flush_ta
From: Shan Wei
Signed-off-by: Shan Wei
---
net/rds/ib_recv.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net/rds/ib_recv.c b/net/rds/ib_recv.c
index 8d19491..a4a5064 100644
--- a/net/rds/ib_recv.c
+++ b/net/rds/ib_recv.c
@@ -423,7 +423,7 @@ static void rds_ib_recv
From: Shan Wei
Signed-off-by: Shan Wei
---
net/xfrm/xfrm_ipcomp.c |7 +++
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/net/xfrm/xfrm_ipcomp.c b/net/xfrm/xfrm_ipcomp.c
index e5246fb..af6c78a 100644
--- a/net/xfrm/xfrm_ipcomp.c
+++ b/net/xfrm/xfrm_ipcomp.c
@@ -276,14 +2
From: Jan-Simon Möller
The use of variable length arrays in structs (VLAIS) in the Linux Kernel code
precludes the use of compilers which don't implement VLAIS (for instance the
Clang compiler). This patch instead allocates the appropriate amount of memory
using an char array.
Patch from series
From: Shan Wei
Signed-off-by: Shan Wei
---
net/openvswitch/datapath.c |4 ++--
net/openvswitch/vport.c|5 ++---
2 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/net/openvswitch/datapath.c b/net/openvswitch/datapath.c
index 4c4b62c..77d16a5 100644
--- a/net/openvswitch/
From: Shan Wei
Signed-off-by: Shan Wei
---
include/trace/ftrace.h |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/include/trace/ftrace.h b/include/trace/ftrace.h
index a763888..7c9fde7 100644
--- a/include/trace/ftrace.h
+++ b/include/trace/ftrace.h
@@ -638,7 +638,6
From: Shan Wei
Signed-off-by: Shan Wei
---
kernel/padata.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/padata.c b/kernel/padata.c
index 89fe3d1..70dffe8 100644
--- a/kernel/padata.c
+++ b/kernel/padata.c
@@ -204,7 +204,7 @@ static struct padata_priv *padata
From: Shan Wei
Signed-off-by: Shan Wei
---
kernel/trace/blktrace.c |2 +-
kernel/trace/trace.c|2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/trace/blktrace.c b/kernel/trace/blktrace.c
index c0bd030..71259e2 100644
--- a/kernel/trace/blktrace.c
+++ b/ke
From: Shan Wei
Signed-off-by: Shan Wei
---
drivers/clocksource/arm_generic.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/clocksource/arm_generic.c
b/drivers/clocksource/arm_generic.c
index c4d9f95..cb445ab 100644
--- a/drivers/clocksource/arm_generic.c
++
From: Shan Wei
smp_processor_id is defined as raw_smp_processor_id.
replace per_cpu_ptr(p, raw_smp_processor_id()) is also ok.
Signed-off-by: Shan Wei
---
kernel/rcutree.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/rcutree.c b/kernel/rcutree.c
index 74df86
On Wed, Oct 31, 2012 at 6:41 PM, Xiaotian Feng wrote:
> Some driver uses tasklet_disable in device remove/release process,
> tasklet_disable will inc tasklet->count and return. If the tasklet
> is not handled yet under some softirq pressure, the tasklet will be
> placed on the tasklet_vec, never h
On 30.10.2012 20:18, Mel Gorman wrote:
On Mon, Oct 29, 2012 at 11:52:03AM +0100, Thorsten Leemhuis wrote:
On 15.10.2012 13:09, Mel Gorman wrote:
On Mon, Oct 15, 2012 at 11:54:13AM +0200, Jiri Slaby wrote:
On 10/12/2012 03:57 PM, Mel Gorman wrote:
mm: vmscan: scale number of pages reclaimed by
At 10/31/2012 07:23 PM, Wen Congyang Wrote:
> The last version is here:
> https://lkml.org/lkml/2012/10/19/56
>
> Note: patch 1-3 are in -mm tree and I don't touch them. The other patches
> except patch6 are also in mm tree. Patch 6 is not touched.
>
> Changes from v3 to v4:
> Patch4: use d
On Wed, Oct 31, 2012 at 10:16:18AM +, David Woodhouse wrote:
>
> Does this break the pvcc->blocked handling that coordinates with
> pppoatm_pop()?
>
> If we have one packet in flight, so pppoatm_may_send() permits a new one
> to be queued... but they're *large* packets to sk_wmem_alloc doesn'
On Wed, Oct 31, 2012 at 08:43:35AM +, Michal Simek wrote:
>
>
> > -Original Message-
> > From: Arnd Bergmann [mailto:a...@arndb.de]
> > Sent: Tuesday, October 30, 2012 11:22 PM
> > To: Michal Simek
> > Cc: Josh Cartwright; a...@kernel.org; linux-kernel@vger.kernel.org;
> > linux-arm-
On Wednesday 31 October 2012 04:37 PM, Benoit Cousson wrote:
I've just applied it in the branch with a slight change in the subject.
Thanks Benoit
Regards
Afzal
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On 10/31/2012 11:51 AM, Philip, Avinash wrote:
> Add McSPI data node to AM33XX device tree file. The McSPI module (and so
> as the driver) is reused from OMAP4.
>
> Signed-off-by: Philip, Avinash
> Tested-by: Matt Porter
> ---
Applied in for_3.8/dts
Thanks,
Benoit
> Changes since v2:
>
On Wed, Oct 31, 2012 at 12:21:28PM +0200, Pasi Kärkkäinen wrote:
> On Wed, Oct 31, 2012 at 10:29:25AM +0100, Olaf Hering wrote:
> > On Wed, Oct 31, Ian Campbell wrote:
> >
> > > If I understand correctly this requirements comes from the need to
> > > support moving the shared info page in order to
From: Yasuaki Ishimatsu
When calling remove_memory_block(), the function shows following message
at device_release().
"Device 'memory528' does not have a release() function, it is broken and
must be fixed."
The reason is memory_block's device struct does not have a release()
function.
So the p
The last version is here:
https://lkml.org/lkml/2012/10/19/56
Note: patch 1-3 are in -mm tree and I don't touch them. The other patches
except patch6 are also in mm tree. Patch 6 is not touched.
Changes from v3 to v4:
Patch4: use dynamically allocated memory instead of static array.
Patch
From: Yasuaki Ishimatsu
When calling unregister_node(), the function shows following message at
device_release().
"Device 'node2' does not have a release() function, it is broken and must
be fixed."
The reason is node's device struct does not have a release() function.
So the patch registers n
If sparse memory vmemmap is enabled, we can't free the memory to store
struct page when a memory device is hotremoved, because we may store
struct page in the memory to manage the memory which doesn't belong
to this memory device. When we hotadded this memory device again, we
will reuse this memory
NR_FREE_PAGES will be wrong after offlining pages. We add/dec
NR_FREE_PAGES like this now:
1. move all pages in buddy system to MIGRATE_ISOLATE, and dec NR_FREE_PAGES
2. don't add NR_FREE_PAGES when it is freed and the migratetype is
MIGRATE_ISOLATE
3. dec NR_FREE_PAGES when offlining isolat
hwpoisoned may be set when we offline a page by the sysfs interface
/sys/devices/system/memory/soft_offline_page or
/sys/devices/system/memory/hard_offline_page.
If a page is hwpisoned page, we may meet the following problems
when we offlining/removing the memory:
1. the pages can't be offlined.
We use __free_page() to put a page to buddy system when onlining pages.
__free_page() will store NR_FREE_PAGES in zone's pcp.vm_stat_diff, so we
should allocate zone's pcp before onlining pages, otherwise we will lose
some free pages.
Cc: David Rientjes
Cc: Jiang Liu
Cc: Len Brown
Cc: Benjamin
We use a static array to store struct node. In many cases, we don't have too
many nodes, and some memory will be unused. Convert it to per-device
dynamically allocated memory.
CC: David Rientjes
CC: Jiang Liu
Cc: Minchan Kim
CC: Andrew Morton
CC: KOSAKI Motohiro
CC: Yasuaki Ishimatsu
Signed-
On Wed, Oct 31, 2012 at 07:23:03PM +0800, Shan Wei wrote:
> From: Shan Wei
>
> smp_processor_id is defined as raw_smp_processor_id.
> replace per_cpu_ptr(p, raw_smp_processor_id()) is also ok.
>
> Signed-off-by: Shan Wei
Hello, Shan Wei,
There are several definitions of this_cpu_ptr():
0 per
On Wed, 2012-10-31 at 12:30 +0100, Krzysztof Mazur wrote:
> Yes, original patch had also the same problem with sock_owned_by_user(),
> so I just incorrectly assumed that we can do "goto nospace" after
> pppoatm_may_send(), but ppooatm_may_send() must be the last test.
>
> So I just moved all other
Hi Rusty,
On Wed, 31 Oct 2012 13:58:15 +1030 Rusty Russell wrote:
>
> Stephen Rothwell writes:
> >
> > On Tue, 02 Oct 2012 15:56:56 +0930 Rusty Russell
> > wrote:
> >>
> >> Please remove my quilt tree
> >> http://ozlabs.org/~rusty/kernel/rr-latest/ from linux-next, and use my
> >> git
2012/10/31 Theodore Ts'o :
> On Tue, Oct 30, 2012 at 08:12:39PM +0900, Akinobu Mita wrote:
>> >>
>> >> How about prandom32_get_bytes_state() and prandom32_get_bytes() instead?
>> >
>> > I agree with your suggestion. I'll rename them and try again.
>> >
>> > By the way, should we also rename the ex
When a memory block is onlined, we will try allocate memory on that node
to store page_cgroup. If onlining the memory block failed, we don't
offline the page cgroup, and we have no chance to offline this page cgroup
unless the memory block is onlined successfully again. It will cause that
we can'
On Wed, Oct 31, 2012 at 04:03:59PM +0530, Laxman Dewangan wrote:
> On Monday 29 October 2012 09:44 PM, Mark Brown wrote:
>> * PGP Signed by an unknown key
>>
>> On Mon, Oct 29, 2012 at 09:33:33AM +, Charles Keepax wrote:
>>> regulator_put function was called whilst holding the
>>> regulator_lis
On Wed, Oct 31, 2012 at 01:55:29PM +0800, Daniel J Blueman wrote:
> Fix the handling of memory controller detection to index the array
> of detected Northbridges, allowing memory controllers over multiple
> PCI domains in federated systems eg using Numascale's NumaConnect/
> NumaChip.
>
> v4: Gene
Hello,
On Tue 23-10-12 11:43:51, Nikola Ciprich wrote:
> while trying to create consistent backups of KVM guest, I've discovered
> that fsfreeze always hangs.. deeper investigation revealed psacct to be the
> culprit.
> When psacct is disabled, fsfreeze works fine, when enabled, the command nev
On 10/30/2012 02:37 PM, Andrew Jones wrote:
On Tue, Oct 30, 2012 at 01:01:54PM +0530, Raghavendra K T wrote:
On 10/30/2012 12:04 PM, Andrew Jones wrote:
On Tue, Oct 30, 2012 at 11:27:52AM +0530, Raghavendra K T wrote:
On 10/29/2012 11:24 PM, Peter Zijlstra wrote:
On Mon, 2012-10-29 at 19:37 +
Hi,
cgroups that use css_id only have this number assigned after ->create()
returns. This means it is not possible to use this number for anything during
cgroup initialization.
There are situations in which it may come handy: in the kmemcg-slab patchset,
for instance, each memcg that has a limit
Initialization in post_create can theoretically fail (although it won't
in cpuset). The comment in cgroup.c even seem to indicate that the
possibility of failure was the intention.
It is not terribly complicated, so let us just allow it to fail.
Signed-off-by: Glauber Costa
CC: Tejun Heo
CC: Mi
When we call create_cgroup(), the css_ids are not yet initialized. The
only creation-time hook that is called with everything already setup is
post_clone().
However, post_clone is too fragile, in the sense that whether or not it
will be called depends on flag that can be switched on or off at
user
Hi Murali,
On 10/25/2012 9:41 PM, Murali Karicheri wrote:
> This is the driver for the main PLL clock hardware found on DM SoCs.
> This driver borrowed code from arch/arm/mach-davinci/clock.c and
> implemented the driver as per common clock provider API. The main PLL
> hardware typically has a mul
Kees Cook wrote:
> Which means this loop will walk past the end of the memory (loop is
> bounded by n_sections, so secs[loop] can go past datalen). While
> data_addr and raw_data_size will stay bounded, the read of sec->name
> can be out of bounds.
Assuming n_sections is checked, sec->name can't
1 - 100 of 789 matches
Mail list logo
