From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ua1-f48.google.com (mail-ua1-f48.google.com [209.85.222.48]) by mx.groups.io with SMTP id smtpd.web10.18738.1624088689435229290 for ; Sat, 19 Jun 2021 00:44:49 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@gmail.com header.s=20161025 header.b=lmphdslB; spf=pass (domain: gmail.com, ip: 209.85.222.48, mailfrom: alex.kanavin@gmail.com) Received: by mail-ua1-f48.google.com with SMTP id x22so4298385uap.0 for ; Sat, 19 Jun 2021 00:44:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xKBewPXHsEgXcf1j/k8zTrMaQF+HLgf2Eb7y9njlvMM=; b=lmphdslBaeR6FvXsfXC2kx1xHu5UO0wUAkwFcKSyD+FM3bkJP8Lk7zzqbShPpsCSmj 3MfelyCXLsA2FSnCCtQFsa91dvMCPOKZH84S9kRN1uBEP55IQQDAlk/HZOGOYS8Lt+kU Hzk3LTnfNT0E9lGRjBoxhugLDzhBuA2cRp5y+WB0lVBGsekYRsDBn0iQW7wS6HDieydG I2G0KqmxM+EgEV/7VtFjkqt8BjeJFtj3Bdba6NHeh1BCzVRUybao/vcYZrYz6ds7bQkA oah/9V9hZApxVbdlnkYVqgni+H5iH7IMqQ2iwGna5ugD0ZHnRtsa1FuNDutXt1ep79ua pRXg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xKBewPXHsEgXcf1j/k8zTrMaQF+HLgf2Eb7y9njlvMM=; b=TGYLrQgxhC65k+79knwcF9G/qGv2MHLHj0tawu7pYX3EY34DDYRUgHGdBRdRcMMZ3F 1hgM0ZInmQoGOi69x1GQaxjdnvVUbjHvFt/t7Y1g8oPKdxnmF7uLf6/okmn9ajS0bcK6 NFUJ3DeM66hv/OX+D7Df+dtNtnCB43RRCsQVlPqCKHczk6TVYYbKv+fUH4Vb5yVU3Kj9 BBA+gf2B+oh60PJZklyobVnwzVXvmMG11ZFJ68gSq74JxYQ9e/2ujqoDtI/LQQQPjnSB FfULSWJfJuNgtcgtjTQgmM8aS78ekz5M2hHQa3p36tuYz5gzHBN4ytB6qJMRr3G40VNj v7XA== X-Gm-Message-State: AOAM530ouH0UyOOHQ8pXWlSn8BYbHhRmKFr4W6IAOtTX+szzMS1AijZ1 MnSMjgvB7XMLNxfk+s9tFRM3g8rO0+T3DEWGsss= X-Google-Smtp-Source: ABdhPJw8+qmJ9IFi91iTON7WMhzAO5GoztaK3l1ar75xQYOkgQg1Agsu/yS4OkT+HAhnjIl9T2Kie4N4JZBo+5ZhbUE= X-Received: by 2002:a9f:31b1:: with SMTP id v46mr15337170uad.22.1624088688645; Sat, 19 Jun 2021 00:44:48 -0700 (PDT) MIME-Version: 1.0 References: <1688B34361FD8BD3.6379@lists.openembedded.org> <16890800366CFBBE.20493@lists.openembedded.org> <1689153CED767CA8.15085@lists.openembedded.org> In-Reply-To: From: "Alexander Kanavin" Date: Sat, 19 Jun 2021 09:44:36 +0200 Message-ID: Subject: Re: [OE-core] [PATCH 01/31] core-image-weston: bump QB_MEM to 1G in qemuarm64 To: Khem Raj Cc: Richard Purdie , Ross Burton , OE-core Content-Type: multipart/alternative; boundary="0000000000005ede8805c5199d5d" --0000000000005ede8805c5199d5d Content-Type: text/plain; charset="UTF-8" Right, I'll adjust to a PACKAGECONFIG. ARM folks should investigate what looks like a copy-on-write breakage. Alex On Sat, 19 Jun 2021 at 00:14, Khem Raj wrote: > I think we should disable this by default, its a good feature during > development though to catch memory bugs. So please turn it into a > PACKAGECONFIG which is disabled > by default instead of revert. > > On Fri, Jun 18, 2021 at 1:49 PM Alexander Kanavin > wrote: > > > > Sadly, I can confirm: weston swelling to double size on qemuarm64 is > caused by this recent change in glibc: > > > > +EXTRA_OECONF_append_aarch64 = " --enable-memory-tagging" > > > > You can verify with this innocent looking program. Run 'free' while it > is running and compare with and without tagging: > > > > main() > > { > > for (int i=0; i<768; i++) > > calloc(1,262368); > > sleep(200); > > } > > > > I'll queue a revert. > > > > Alex > > > > On Wed, 16 Jun 2021 at 16:08, Alexander Kanavin via > lists.openembedded.org > wrote: > >> > >> It seems that mesa, for some reason, allocates a lot more RAM in > qemuarm64 (150 Mb more or so), than it does in qemux86_64. I'll investigate. > >> > >> Alex > >> > >> On Wed, 16 Jun 2021 at 12:06, Alexander Kanavin via > lists.openembedded.org > wrote: > >>> > >>> I'd like to take a deeper look at this, please hold. > >>> > >>> Alex > >>> > >>> On Tue, 15 Jun 2021 at 10:12, Alexander Kanavin via > lists.openembedded.org > wrote: > >>>> > >>>> weston tests start additional compositors, other tests are also > >>>> heavy on RAM, weston itself takes 256M with opengl enabled, > >>>> so 512M causes OOM errors on arm64. > >>>> > >>>> Signed-off-by: Alexander Kanavin > >>>> --- > >>>> meta/recipes-graphics/images/core-image-weston.bb | 1 + > >>>> 1 file changed, 1 insertion(+) > >>>> > >>>> diff --git a/meta/recipes-graphics/images/core-image-weston.bb > b/meta/recipes-graphics/images/core-image-weston.bb > >>>> index 62305cc1ce..e332e19368 100644 > >>>> --- a/meta/recipes-graphics/images/core-image-weston.bb > >>>> +++ b/meta/recipes-graphics/images/core-image-weston.bb > >>>> @@ -10,3 +10,4 @@ CORE_IMAGE_BASE_INSTALL += "gtk+3-demo" > >>>> CORE_IMAGE_BASE_INSTALL += "${@bb.utils.contains('DISTRO_FEATURES', > 'x11', 'weston-xwayland matchbox-terminal', '', d)}" > >>>> > >>>> QB_MEM = "-m 512" > >>>> +QB_MEM_qemuarm64 = "-m 1024" > >>>> -- > >>>> 2.31.1 > >>>> > >>>> > >>>> > >>>> > >>> > >>> > >>> > >> > >> > >> > --0000000000005ede8805c5199d5d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Right, I'll adjust to a PACKAGECONFIG. ARM folks = should investigate what looks like a copy-on-write breakage.

=
Alex

On Sat, 19 Jun 2021 at 00:14, Khem Raj <raj.khem@gmail.com> wrote:
=
I think we should disable= this by default, its a good feature during
development though to catch memory bugs. So please turn it into a
PACKAGECONFIG which is disabled
by default instead of revert.

On Fri, Jun 18, 2021 at 1:49 PM Alexander Kanavin
<alex.kanav= in@gmail.com> wrote:
>
> Sadly, I can confirm: weston swelling to double size on qemuarm64 is = caused by this recent change in glibc:
>
> +EXTRA_OECONF_append_aarch64 =3D " --enable-memory-tagging"=
>
> You can verify with this innocent looking program. Run 'free'= while it is running and compare with and without tagging:
>
> main()
> {
>=C2=A0 =C2=A0 for (int i=3D0; i<768; i++)
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 calloc(1,262368);
>=C2=A0 =C2=A0 sleep(200);
> }
>
> I'll queue a revert.
>
> Alex
>
> On Wed, 16 Jun 2021 at 16:08, Alexander Kanavin via lists.openemb= edded.org <alex.kanavin=3Dgmail.com@lists.openembedded.org> wrote:=
>>
>> It seems that mesa, for some reason, allocates a lot more RAM in = qemuarm64 (150 Mb more or so), than it does in qemux86_64. I'll investi= gate.
>>
>> Alex
>>
>> On Wed, 16 Jun 2021 at 12:06, Alexander Kanavin via lists.ope= nembedded.org <alex.kanavin=3Dgmail.com@lists.openembedded.org> wr= ote:
>>>
>>> I'd like to take a deeper look at this, please hold.
>>>
>>> Alex
>>>
>>> On Tue, 15 Jun 2021 at 10:12, Alexander Kanavin via li= sts.openembedded.org <alex.kanavin=3Dgmail.com@lists.openembedded.org= > wrote:
>>>>
>>>> weston tests start additional compositors, other tests ar= e also
>>>> heavy on RAM, weston itself takes 256M with opengl enable= d,
>>>> so 512M causes OOM errors on arm64.
>>>>
>>>> Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
>>>> ---
>>>>=C2=A0 meta/recipes-graphics/images/core-image-weston.bb= | 1 +
>>>>=C2=A0 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/meta/recipes-graphics/images/core-image-we= ston.bb b/meta/recipes-graphics/images/core-image-weston.bb
>>>> index 62305cc1ce..e332e19368 100644
>>>> --- a/meta/recipes-graphics/images/core-image-weston.bb=
>>>> +++ b/meta/recipes-graphics/images/core-image-weston.bb=
>>>> @@ -10,3 +10,4 @@ CORE_IMAGE_BASE_INSTALL +=3D "gtk+= 3-demo"
>>>>=C2=A0 CORE_IMAGE_BASE_INSTALL +=3D "${@bb.utils.cont= ains('DISTRO_FEATURES', 'x11', 'weston-xwayland matchbo= x-terminal', '', d)}"
>>>>
>>>>=C2=A0 QB_MEM =3D "-m 512"
>>>> +QB_MEM_qemuarm64 =3D "-m 1024"
>>>> --
>>>> 2.31.1
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>>
>>
--0000000000005ede8805c5199d5d--