Segher Boessenkool writes:
> On Thu, Aug 23, 2018 at 11:32:16PM +1000, Andrew Donnellan wrote:
>> On 23/08/18 21:56, Michael Ellerman wrote:
>> >Christophe LEROY writes:
>> >
>> >>Le 23/08/2018 à 12:36, Segher Boessenkool a écrit :
>> >>>On Thu, Aug 23, 2018 at 11:40:22AM +0200, Christophe LEROY
Le 23/08/2018 à 16:41, Segher Boessenkool a écrit :
On Thu, Aug 23, 2018 at 11:32:16PM +1000, Andrew Donnellan wrote:
On 23/08/18 21:56, Michael Ellerman wrote:
Christophe LEROY writes:
Le 23/08/2018 à 12:36, Segher Boessenkool a écrit :
On Thu, Aug 23, 2018 at 11:40:22AM +0200, Christop
On Thu, Aug 23, 2018 at 11:32:16PM +1000, Andrew Donnellan wrote:
> On 23/08/18 21:56, Michael Ellerman wrote:
> >Christophe LEROY writes:
> >
> >>Le 23/08/2018 à 12:36, Segher Boessenkool a écrit :
> >>>On Thu, Aug 23, 2018 at 11:40:22AM +0200, Christophe LEROY wrote:
> The only small problèm
On 23/08/18 21:56, Michael Ellerman wrote:
Christophe LEROY writes:
Le 23/08/2018 à 12:36, Segher Boessenkool a écrit :
On Thu, Aug 23, 2018 at 11:40:22AM +0200, Christophe LEROY wrote:
The only small problème I have is that some version of GCC seems to
complain about big memset() (132k and
Christophe LEROY writes:
> Le 23/08/2018 à 12:36, Segher Boessenkool a écrit :
>> On Thu, Aug 23, 2018 at 11:40:22AM +0200, Christophe LEROY wrote:
>>> The only small problème I have is that some version of GCC seems to
>>> complain about big memset() (132k and 256k ones). Is there a way to tell
Le 23/08/2018 à 12:36, Segher Boessenkool a écrit :
On Thu, Aug 23, 2018 at 11:40:22AM +0200, Christophe LEROY wrote:
The only small problème I have is that some version of GCC seems to
complain about big memset() (132k and 256k ones). Is there a way to tell
GCC we really want to do it ?
I'
On Thu, Aug 23, 2018 at 11:40:22AM +0200, Christophe LEROY wrote:
> The only small problème I have is that some version of GCC seems to
> complain about big memset() (132k and 256k ones). Is there a way to tell
> GCC we really want to do it ?
I'm not sure what you mean. Complain, is that a warn
Le 22/08/2018 à 16:20, Aneesh Kumar K.V a écrit :
On 08/17/2018 04:14 PM, Christophe LEROY wrote:
Le 17/08/2018 à 05:32, Aneesh Kumar K.V a écrit :
On 08/14/2018 08:24 PM, Christophe Leroy wrote:
While implementing TLB miss HW assistance on the 8xx, the following
warning was encountered:
On 08/17/2018 04:14 PM, Christophe LEROY wrote:
Le 17/08/2018 à 05:32, Aneesh Kumar K.V a écrit :
On 08/14/2018 08:24 PM, Christophe Leroy wrote:
While implementing TLB miss HW assistance on the 8xx, the following
warning was encountered:
[ 423.732965] WARNING: CPU: 0 PID: 345 at mm/slub.c:
Aneesh,
Le 17/08/2018 à 12:44, Christophe LEROY a écrit :
Le 17/08/2018 à 05:32, Aneesh Kumar K.V a écrit :
On 08/14/2018 08:24 PM, Christophe Leroy wrote:
While implementing TLB miss HW assistance on the 8xx, the following
warning was encountered:
[ 423.732965] WARNING: CPU: 0 PID: 345 at
Le 17/08/2018 à 05:32, Aneesh Kumar K.V a écrit :
On 08/14/2018 08:24 PM, Christophe Leroy wrote:
While implementing TLB miss HW assistance on the 8xx, the following
warning was encountered:
[ 423.732965] WARNING: CPU: 0 PID: 345 at mm/slub.c:2412
___slab_alloc.constprop.30+0x26c/0x46c
[
On 08/14/2018 08:24 PM, Christophe Leroy wrote:
While implementing TLB miss HW assistance on the 8xx, the following
warning was encountered:
[ 423.732965] WARNING: CPU: 0 PID: 345 at mm/slub.c:2412
___slab_alloc.constprop.30+0x26c/0x46c
[ 423.733033] CPU: 0 PID: 345 Comm: mmap Not tainted
4.
While implementing TLB miss HW assistance on the 8xx, the following
warning was encountered:
[ 423.732965] WARNING: CPU: 0 PID: 345 at mm/slub.c:2412
___slab_alloc.constprop.30+0x26c/0x46c
[ 423.733033] CPU: 0 PID: 345 Comm: mmap Not tainted
4.18.0-rc8-00664-g2dfff9121c55 #671
[ 423.733075] N
13 matches
Mail list logo
