Skip to contentSkip to conversation

core-image-weston: bump QB_MEM to 1G in qemuarm64

PATCH Alexander Kanavin 2 participants 5 messages Jun 16, 2021 – Jun 19, 2021 3 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

I'd like to take a deeper look at this, please hold.

Alex

Quoted 27 lines · Alexander Kanavin via lists.openembedded.org

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.

---
 meta/recipes-graphics/images/core-image-weston.bb | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-graphics/images/core-image-weston.bb +0 -0
index 62305cc1ce..e332e19368 100644
@@ -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

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw

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

Quoted 37 lines · Alexander Kanavin via lists.openembedded.org

I'd like to take a deeper look at this, please hold.

Alex

Quoted 27 lines · Alexander Kanavin via lists.openembedded.org

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.

---
 meta/recipes-graphics/images/core-image-weston.bb | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-graphics/images/core-image-weston.bb +0 -0
index 62305cc1ce..e332e19368 100644
@@ -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

A message that is not in the archive (sent off-list or not yet received): [email protected]

#5 lore raw

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

Quoted 49 lines · Alexander Kanavin via lists.openembedded.org

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

Quoted 38 lines · Alexander Kanavin via lists.openembedded.org

I'd like to take a deeper look at this, please hold.

Alex

Quoted 27 lines · Alexander Kanavin via lists.openembedded.org

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.

---
 meta/recipes-graphics/images/core-image-weston.bb | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-graphics/images/core-image-weston.bb +0 -0
index 62305cc1ce..e332e19368 100644
@@ -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

#6 lore raw

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.

Quoted 62 lines · Alexander Kanavin

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

Quoted 43 lines · Alexander Kanavin via lists.openembedded.org

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

Quoted 34 lines · Alexander Kanavin via lists.openembedded.org

I'd like to take a deeper look at this, please hold.

Alex

Quoted 25 lines · Alexander Kanavin via lists.openembedded.org

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.

---
 meta/recipes-graphics/images/core-image-weston.bb | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-graphics/images/core-image-weston.bb +1 -1
index 62305cc1ce..e332e19368 100644
@@ -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

#7 lore raw

Right, I'll adjust to a PACKAGECONFIG. ARM folks should investigate what looks like a copy-on-write breakage.

Alex

Quoted 81 lines · Khem Raj

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.

Quoted 2 lines · Alexander Kanavin

Sadly, I can confirm: weston swelling to double size on qemuarm64 is

caused by this recent change in glibc:

Quoted 4 lines

+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:

Quoted 8 lines

main()

{
   for (int i=0; i<768; i++)
       calloc(1,262368);
   sleep(200);
}
Quoted 5 lines

I'll queue a revert.

Alex

On Wed, 16 Jun 2021 at 16:08, Alexander Kanavin via

lists.openembedded.org <[email protected]>

Quoted 2 lines · wrote:
Quoted 2 lines

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.

Quoted 4 lines
Quoted 4 lines

Alex

On Wed, 16 Jun 2021 at 12:06, Alexander Kanavin via

lists.openembedded.org <[email protected]>

Quoted 6 lines · wrote:
Quoted 6 lines
Quoted 6 lines

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 <[email protected]>

Quoted 11 lines · wrote:
Quoted 11 lines
Quoted 11 lines

Review

Quoted 11 lines

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.

---
 meta/recipes-graphics/images/core-image-weston.bb | 1 +
 1 file changed, 1 insertion(+)
(quoted diff) +0 -0

b/meta/recipes-graphics/images/core-image-weston.bb

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

meta/recipes-graphics/images/core-image-weston.bb CORE_IMAGE_BASE_INSTALL += "gtk+3-demo" · line 10

Quoted 5 lines

index 62305cc1ce..e332e19368 100644

meta/recipes-graphics/images/core-image-weston.bb +0 -0
@@ -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)}"

Quoted 15 lines
Quoted 15 lines
Quoted 12 lines
Quoted 9 lines
meta/recipes-graphics/images/core-image-weston.bb +1 -1
 QB_MEM = "-m 512"
+QB_MEM_qemuarm64 = "-m 1024"
--

2.31.1