New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Bringup ARM64 userspace in Chrome OS

Project Member Reported by manojgupta@chromium.org, Aug 28

Issue description

Current ARM64 boards in Chrome OS are still using 32-bit userspace.

Let's bring up a board with ARM64 userspace to find any issues related to performance/stability etc.
 
Current set of issues, using a pseudo kevin64 board:

1. Need to land https://chromium-review.googlesource.com/c/chromiumos/overlays/board-overlays/+/1127790 to add kevin64 overlay

2. Known issues with mali-drivers, login screen doesn't come up. 
When the above patch lands, I'll push a patch to enable building the Mali drivers. This should then get kevin64 to a state where you have a usable ChromeOS device with a 64-bit Arm userspace.
Dave, https://chromium-review.googlesource.com/c/chromiumos/overlays/board-overlays/+/1127790 has landed. Can you submit the mali-drivers patches?

Also,  can you verify if you have access to private-overlays/overlay-kevin64-private ?
Project Member

Comment 4 by bugdroid1@chromium.org, Aug 31

Project Member

Comment 5 by bugdroid1@chromium.org, Sep 1

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/31a17c59a6a00c55665d38a32595099290f22c79

commit 31a17c59a6a00c55665d38a32595099290f22c79
Author: Dave Rodgman <dave.rodgman@arm.com>
Date: Sat Sep 01 02:03:23 2018

gru: use Arm Mali drivers when building for arm64

Use the Arm Mali drivers (available via the kevin64 private overlay)
when building for arm64. This is needed for the prototype 64-bit
userspace for kevin.

BUG=chromium:878565
TEST=emerge-kevin64 media-libs/mali-drivers

Change-Id: Iaf7b1a293b2f7bd4594f0a8dab5533fa1a422778
Signed-off-by: Dave Rodgman <dave.rodgman@arm.com>
Reviewed-on: https://chromium-review.googlesource.com/1199823
Commit-Ready: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>

[modify] https://crrev.com/31a17c59a6a00c55665d38a32595099290f22c79/baseboard-gru/virtual/opengles/opengles-2.ebuild

Dave, my local arm64 builds are broken with the update to opengles CL that depends on mali-drivers. Reason is mali-drivers is not available on public overlay.

Do you have a plan to push a binary similar to mali-drivers-bin something like mali-arm64-drivers-bin to the public overlay? 
Apologies, I expected that everyone inside Google would have access to that repository, so for purposes of prototyping and testing inside Google & Arm, this would be OK for the short term - this is what I suggested to Ting-Yuan.

Agreed it would make sense to set up a publicly accessible mali-drivers-bin. I can start looking into this on Monday.
Internal build is pulling up a lot of other stuff that doesn't build right now :-( and fixing all of that will take a while.
So I am trying to stick with the public manifest.  
OK, I'll take a look at making a mali-arm64-drivers-bin. I don't know where the binary should actually get hosted though? Presumably Google host this for the 32-bit user space, so we can just do the same for 64-bit?
Blockedon: 879846
Labels: cros-arm64
Project Member

Comment 13 by bugdroid1@chromium.org, Sep 2

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/bc8de301b549140f6b4bae23955566488b945dfe

commit bc8de301b549140f6b4bae23955566488b945dfe
Author: Manoj Gupta <manojgupta@google.com>
Date: Sun Sep 02 09:13:49 2018

chromeos-bsp-baseboard-gru: Fix build for arm64.

Install files in /opt/containers/android only with USE=cheets.
This is make Non-ARC++ boards e.g. kevin64 not fail in build_image.

BUG=chromium:878565
TEST=Files not installed in /opt/container/... for kevin64.
TEST=Files were still installed in /opt/container/... for kevin64.

Change-Id: Ie88927b9ed8a1ea98f19a2d4f00fa639ed8939fe
Reviewed-on: https://chromium-review.googlesource.com/1201102
Commit-Ready: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[rename] https://crrev.com/bc8de301b549140f6b4bae23955566488b945dfe/baseboard-gru/chromeos-base/chromeos-bsp-baseboard-gru/chromeos-bsp-baseboard-gru-0.0.3-r12.ebuild
[modify] https://crrev.com/bc8de301b549140f6b4bae23955566488b945dfe/baseboard-gru/chromeos-base/chromeos-bsp-baseboard-gru/chromeos-bsp-baseboard-gru-0.0.3.ebuild

Project Member

Comment 14 by bugdroid1@chromium.org, Sep 2

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/fe593f76959b028befa0adcacb9006bed101e52b

commit fe593f76959b028befa0adcacb9006bed101e52b
Author: Manoj Gupta <manojgupta@google.com>
Date: Sun Sep 02 09:13:47 2018

arm64: Disable pepper_flash.

We don't have a flash build for arm64. So disable it.

BUG=chromium:878565
TEST=build_packages on kevin64 doesn't pick pepper_flash.

Change-Id: I8dcc276158122b39381a1bcdd834d10c29508c63
Reviewed-on: https://chromium-review.googlesource.com/1200922
Commit-Ready: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/fe593f76959b028befa0adcacb9006bed101e52b/profiles/arch/arm64/use.mask

Project Member

Comment 15 by bugdroid1@chromium.org, Sep 2

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/adhd/+/c84149a9cd4aafa998a97738fe5af32fb90f353a

commit c84149a9cd4aafa998a97738fe5af32fb90f353a
Author: Manoj Gupta <manojgupta@google.com>
Date: Sun Sep 02 09:13:50 2018

adhd: Add an arm64 seccomp policy.

Use arm policy as the base but rename 32-bit versions by 64-bit
ones.

BUG=chromium:878565
TEST=emerge-kevin64 adhd

Change-Id: I8a7b116b8a16c5a3bd5fa0a4120bcb5158994205
Reviewed-on: https://chromium-review.googlesource.com/1200902
Commit-Ready: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[add] https://crrev.com/c84149a9cd4aafa998a97738fe5af32fb90f353a/seccomp/cras-seccomp-arm64.policy

I was finally able to create a kevin64 image with internal overlay. However, it didn't boot to login screen (got stuck at Chrome logo).
you disabled Chrome in the build didn't you ?  so what you described is WAI ? :)

frecon/bootsplash show that logo, then it's up to Chrome to transition to something else.
I am sure that I didn't disable Chrome, Just cheets/ARC++ stuff and a few packages that didn't build (drivefs, screensaver).
These changes could affect the boot but I don't know enough about the boot process details to figure out where things went wrong.
ssh in and see why the "ui" job didn't start
Earlier we had issues with the sandbox blocking the mali driver from loading correctly. Can you please try adding '--disable-gpu-sandbox --disable-sandbox' to /etc/chrome-dev.conf? Or if that doesn't help the, then as vapier suggested, you could take a look at '/var/log/ui'.
Sorry, a correction: '--disable-sandbox' -> '--no-sandbox'.
After disabling sandox, ui is still failing to come up.

/var/log/ui is empty but I see this in /var/log/chrome/

[6231:6231:0904/130257.209934:WARNING:install_attributes.cc(163)] Install attributes missing, first sign in
[6231:6231:0904/130257.223425:VERBOSE1:drm_display_host_manager.cc(88)] Failed to get DRM resources for '/dev/dri/card0': Invalid argument (22)
[6231:6231:0904/130258.224958:WARNING:drm_device_handle.cc(83)] Failed to authenticate /dev/dri/card1 within 1000 ms
enable_dev_usb_boot is also failing and I can only do a remote flash.
I've also been getting these errors in recent builds, but so far I haven't been able to look into it in depth. I'm fairly certain it's not an issue with chrome. I'm suspecting it has something to do with a recent change in the kernel, but as of now I have no clue which change caused it.
As a note, it could be worth looking in /var/log/messages to see if there's anything in there related to drm. From poking around, it seems to me that it might be caused by the drm driver, but I cannot check until tomorrow.
Cc: dovizu@google.com uekawa@chromium.org bhthompson@chromium.org kblairh@chromium.org ggranito@chromium.org
Cc: dgreid@chromium.org hoegsberg@chromium.org
Cc: drinkcat@chromium.org
The EINVAL error in #22 is a problem. I'd recommend emerging drm-tests, stop ui and then trying /usr/bin/null_platform_test as a minimal accelerated graphics on KMS test case. If that doesn't work attach strace of it and also do a

dmesg -C; echo 0xff > /sys/modules/drm/parameter/debug; null_platform_test; dmesg > /tmp/dmesg.txt

and attach dmesg.txt.
Blockedon: 881022
Project Member

Comment 31 by bugdroid1@chromium.org, Sep 5

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/d15b2011d9c0ec0dcb683a0456360ae950889e1f

commit d15b2011d9c0ec0dcb683a0456360ae950889e1f
Author: Manoj Gupta <manojgupta@google.com>
Date: Tue Sep 04 22:17:06 2018

chromeos_config: Add kevin64-full builder.

We want to start testing AArch64 userspace in Chrome OS.
So start testing kevin64-full builds.

BUG=chromium:878565
TEST=chromite unit tests pass

Change-Id: Id424b7c349bed433e5984b3f73045f2cc6709dab
Reviewed-on: https://chromium-review.googlesource.com/1200173
Commit-Ready: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mattias Nissler <mnissler@chromium.org>
Reviewed-by: Luis Lozano <llozano@chromium.org>

[modify] https://crrev.com/d15b2011d9c0ec0dcb683a0456360ae950889e1f/config/chromeos_config.py
[modify] https://crrev.com/d15b2011d9c0ec0dcb683a0456360ae950889e1f/config/waterfall_layout_dump.txt
[modify] https://crrev.com/d15b2011d9c0ec0dcb683a0456360ae950889e1f/config/config_dump.json

Project Member

Comment 33 by bugdroid1@chromium.org, Sep 5

Project Member

Comment 34 by bugdroid1@chromium.org, Sep 5

Project Member

Comment 35 by bugdroid1@chromium.org, Sep 5

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/ade4fc3b7683ae45d99025689c77c4c363ffbde2

commit ade4fc3b7683ae45d99025689c77c4c363ffbde2
Author: Manoj Gupta <manojgupta@google.com>
Date: Wed Sep 05 04:04:17 2018

touch_firmware_calibration: Add arm64 seccomp policy.

Fixes installation on arm64 builds.

BUG=chromium:878565
TEST=touch_firmware_calibration builds on kevin64

Change-Id: Ie77521313a3fc9d912aba66c3e09289cbfd2650a
Reviewed-on: https://chromium-review.googlesource.com/1201022
Commit-Ready: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[add] https://crrev.com/ade4fc3b7683ae45d99025689c77c4c363ffbde2/touch_firmware_calibration/seccomp/override-max-pressure-seccomp-arm64.policy

Blockedon: 881489
Blockedon: 881565
Blockedon: 881571
Blockedon: 881573

Comment 40 Deleted

It turns out the drm issues were caused by missing rockchip drivers. I've submitted a fix that sets VIDEO_CARDS in the overlay, and with that the UI seems to start. Although I still need to disable the sandbox, otherwise it blocks the GLES library from getting loaded.

I'm not sure why VIDEO_CARDS is not being inherited from the baseboard, as it is set there. It's possible that we're also missing other things from there like firmwares etc.
Project Member

Comment 43 by bugdroid1@chromium.org, Sep 7

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/a139efb6b50855c34ca09e163884927a5700b818

commit a139efb6b50855c34ca09e163884927a5700b818
Author: Dániel Bátyai <dbatyai@inf.u-szeged.hu>
Date: Fri Sep 07 14:46:56 2018

kevin64: Re-order parents to fix inheritance

The parents were in the wrong order, which caused some variables
to be inherited incorrectly, or not inherited at all. Re-ordered
the parents so that everything is inherited as necessary.

BUG=chromium:878565
TEST=build_packages, build_image, image boots on board

Change-Id: Ief80a558ce97bea817cfb8c6d10559aa7173ea66
Reviewed-on: https://chromium-review.googlesource.com/1213322
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Commit-Queue: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>

[modify] https://crrev.com/a139efb6b50855c34ca09e163884927a5700b818/overlay-kevin64/profiles/base/parent

Project Member

Comment 44 by bugdroid1@chromium.org, Sep 7

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/483ead98a409896d275032c90c90744c30e2055d

commit 483ead98a409896d275032c90c90744c30e2055d
Author: Manoj Gupta <manojgupta@google.com>
Date: Fri Sep 07 15:06:03 2018

kevin64: Inherit chromiumos:features/llvm/arm64 explictily.

CC settings from arm64 overlay were lost because of kevin
inheritance which sets CC to armv7a-.
Fix by inheriting chromiumos:features/llvm/arm64 directly.

BUG=chromium:878565
TEST=build_packages
Change-Id: Icc698659e504706a7d67fc3b6639b74492a88d60
Reviewed-on: https://chromium-review.googlesource.com/1213682
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Commit-Queue: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>

[modify] https://crrev.com/483ead98a409896d275032c90c90744c30e2055d/overlay-kevin64/profiles/base/parent

Project Member

Comment 45 by bugdroid1@chromium.org, Sep 7

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/fd692eaf83670bad6fb473df1a6a07f94a514585

commit fd692eaf83670bad6fb473df1a6a07f94a514585
Author: Manoj Gupta <manojgupta@google.com>
Date: Fri Sep 07 17:35:10 2018

kevin64: revert last 2 commits.

Changing parent order has broken many packages. Even gcc-libs does
not build anymore. In addition, both arm and arm64 use flags are set
at same time.

So, just keep the VIDEO_CARDS setting from CL:1213322 first patchset.

BUG=chromium:878565
TEST=build_packages

Change-Id: I391308b4c9fecfdb2ab74766ef4a478de9ea6380
Reviewed-on: https://chromium-review.googlesource.com/1213772
Commit-Queue: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Trybot-Ready: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>

[modify] https://crrev.com/fd692eaf83670bad6fb473df1a6a07f94a514585/overlay-kevin64/profiles/base/parent
[modify] https://crrev.com/fd692eaf83670bad6fb473df1a6a07f94a514585/overlay-kevin64/profiles/base/make.defaults

Blockedon: 881926
Blockedon: 882033
Project Member

Comment 48 by bugdroid1@chromium.org, Sep 8

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/5471e9608ee317866eb2257c593213f340be4805

commit 5471e9608ee317866eb2257c593213f340be4805
Author: Manoj Gupta <manojgupta@google.com>
Date: Sat Sep 08 01:37:06 2018

chromeos-chrome: Disable quickoffice install for arm64.

Quickoffice binaries are not yet available for arm64.

BUG=chromium:881489
BUG=chromium:878565

TEST=No more quickoffice errors on kevin64 builds.

Change-Id: Id4e70edd80d9c2ca64195794b8c3d36c47a6d62b
Reviewed-on: https://chromium-review.googlesource.com/1211685
Commit-Ready: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/5471e9608ee317866eb2257c593213f340be4805/chromeos-base/chromeos-chrome/chromeos-chrome-9999.ebuild

Blockedon: 882499
Blockedon: 882600
Blockedon: 882987
Project Member

Comment 52 by bugdroid1@chromium.org, Sep 13

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/cd9de4123656d922ba251e0f518b05a828c8991e

commit cd9de4123656d922ba251e0f518b05a828c8991e
Author: Dániel Bátyai <dbatyai@inf.u-szeged.hu>
Date: Thu Sep 13 16:59:34 2018

kevin64: Disable sandbox early init

The early initialization of the sandbox blocks the GPU process from
loading the GLES2 library. Disable it until the issue with the sandbox
is resolved.

BUG= chromium:882033 
BUG=chromium:878565
TEST=build image, ui starts

Change-Id: I2804c5629efd6f920b83728900d17e7673fee4ab
Reviewed-on: https://chromium-review.googlesource.com/1224273
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Daniel Batyai <dbatyai@inf.u-szeged.hu>
Commit-Queue: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>

[modify] https://crrev.com/cd9de4123656d922ba251e0f518b05a828c8991e/overlay-kevin64/profiles/base/make.defaults

Project Member

Comment 53 by bugdroid1@chromium.org, Sep 18

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/mosys/+/2bcf2e064e4e680c2270e739f102a0453f1886b8

commit 2bcf2e064e4e680c2270e739f102a0453f1886b8
Author: Adam Kallai <kadam@inf.u-szeged.hu>
Date: Tue Sep 18 13:42:14 2018

mosys: allows some syscalls for arm64

crossystem cannot obtain system specific information or set
any property because of mosys error (i.e. enable dev_boot_usb).

BUG= chromium:882987 
BUG=chromium:878565
TEST=checks with minijail0 and run crossystem

Change-Id: I06632486f2b68b241c87860a2a317450df8954cc
Reviewed-on: https://chromium-review.googlesource.com/1228134
Commit-Ready: Adam Kallai <kadam@inf.u-szeged.hu>
Tested-by: Adam Kallai <kadam@inf.u-szeged.hu>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/2bcf2e064e4e680c2270e739f102a0453f1886b8/seccomp/mosys-seccomp-arm64.policy

Blockedon: 885270
Project Member

Comment 55 by bugdroid1@chromium.org, Sep 18

Blockedon: 885351
Project Member

Comment 57 by bugdroid1@chromium.org, Sep 21

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/adhd/+/d0ada838bb2e9a31d0d3b9368baba27901469587

commit d0ada838bb2e9a31d0d3b9368baba27901469587
Author: Dániel Bátyai <dbatyai@inf.u-szeged.hu>
Date: Fri Sep 21 17:11:35 2018

adhd: Update arm64 seccomp policy

Previous filter was not compiling. Updated the filter with required
syscalls, removed nonexistent ones, and sorted them based on frequency
of use.

BUG=chromium:878565
TEST=cras service starts, audio works as expected

Change-Id: I7f399ff0daa5922e19dbe30328d26221444c0d2e
Reviewed-on: https://chromium-review.googlesource.com/1230874
Commit-Ready: Daniel Batyai <dbatyai@inf.u-szeged.hu>
Tested-by: Daniel Batyai <dbatyai@inf.u-szeged.hu>
Reviewed-by: Dylan Reid <dgreid@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/d0ada838bb2e9a31d0d3b9368baba27901469587/seccomp/cras-seccomp-arm64.policy

Blockedon: 888682
Blockedon: 888686
Project Member

Comment 60 by bugdroid1@chromium.org, Sep 26

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/558086fb0cf9df1a762e5d1e8fcaea3541de4f91

commit 558086fb0cf9df1a762e5d1e8fcaea3541de4f91
Author: Adam Kallai <kadam@inf.u-szeged.hu>
Date: Wed Sep 26 15:26:38 2018

overlay-kevin64: Re-enable usbguard

It was disabled because of missing seccomp policy.
The seccomp policy has been available since this CL:1162159.

BUG=chromium:878565
TEST='emerge-kevin64 usbguard, test manually with minijail'

Change-Id: Iaa13f92f4a49975c31b98b64cf460e5c77cbe0c4
Reviewed-on: https://chromium-review.googlesource.com/1238582
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>

[modify] https://crrev.com/558086fb0cf9df1a762e5d1e8fcaea3541de4f91/overlay-kevin64/profiles/base/make.defaults

Blockedon: 890331
Project Member

Comment 63 by bugdroid1@chromium.org, Oct 2

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/2f001ef6dd1edc034fbb7147cc5d2ce2eb68347c

commit 2f001ef6dd1edc034fbb7147cc5d2ce2eb68347c
Author: Dániel Bátyai <dbatyai@inf.u-szeged.hu>
Date: Tue Oct 02 20:23:07 2018

crosdns: Add arm64 seccomp policy

BUG=chromium:878565
TEST=service runs, able to add/remove dns entries via dbus

Change-Id: I9c470b13e9413899a5b3e15e8e3f065e0af4b7ea
Reviewed-on: https://chromium-review.googlesource.com/1256843
Commit-Ready: Daniel Batyai <dbatyai@inf.u-szeged.hu>
Tested-by: Daniel Batyai <dbatyai@inf.u-szeged.hu>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[add] https://crrev.com/2f001ef6dd1edc034fbb7147cc5d2ce2eb68347c/crosdns/init/crosdns-seccomp-arm64.policy

Project Member

Comment 64 by bugdroid1@chromium.org, Oct 3

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/0c390e783cd4d9c90ad03c0f0487f1034568c432

commit 0c390e783cd4d9c90ad03c0f0487f1034568c432
Author: Dániel Bátyai <dbatyai@inf.u-szeged.hu>
Date: Wed Oct 03 20:59:06 2018

vm_tools: cicerone: Add arm64 seccomp policy

BUG=chromium:878565
TEST=service runs, dbus messages work

Change-Id: Iace01105a1c2d788656511759da680c24fa6b258
Reviewed-on: https://chromium-review.googlesource.com/1258544
Commit-Ready: Daniel Batyai <dbatyai@inf.u-szeged.hu>
Tested-by: Daniel Batyai <dbatyai@inf.u-szeged.hu>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[add] https://crrev.com/0c390e783cd4d9c90ad03c0f0487f1034568c432/vm_tools/init/vm_cicerone-seccomp-arm64.policy

Project Member

Comment 65 by bugdroid1@chromium.org, Oct 4

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/0ff34787e638fa63a84bd71003c830b1ea5b1740

commit 0ff34787e638fa63a84bd71003c830b1ea5b1740
Author: Dániel Bátyai <dbatyai@inf.u-szeged.hu>
Date: Thu Oct 04 15:55:09 2018

kevin64: Re-enable kvm_host

The required packages have been fixed, it can be re-enabled now.

BUG=chromium:878565
TEST=build_packages

Change-Id: Ib9c60a76145391eab356cdc13e04b8aa3a01296c
Reviewed-on: https://chromium-review.googlesource.com/c/1261695
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Daniel Batyai <dbatyai@inf.u-szeged.hu>

[modify] https://crrev.com/0ff34787e638fa63a84bd71003c830b1ea5b1740/overlay-kevin64/profiles/base/make.defaults

Blockedon: 892278
Blockedon: 892389
Project Member

Comment 68 by bugdroid1@chromium.org, Oct 10

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/7f3660b35ef29a9e6b065b0fee0f946a9f105711

commit 7f3660b35ef29a9e6b065b0fee0f946a9f105711
Author: Dániel Bátyai <dbatyai@inf.u-szeged.hu>
Date: Wed Oct 10 11:32:18 2018

kevin64: Re-enable sandbox early init

BUG= chromium:882033 
BUG=chromium:878565
TEST=ui starts, gpu process is sandboxed

Change-Id: I889291a1efebd6fe7dbf117dcb22c8aa835046d9
Reviewed-on: https://chromium-review.googlesource.com/c/1273017
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>

[modify] https://crrev.com/7f3660b35ef29a9e6b065b0fee0f946a9f105711/overlay-kevin64/profiles/base/make.defaults

Project Member

Comment 69 by bugdroid1@chromium.org, Oct 11

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/40bfb95336cd680ef01b71b96f3b090e82301c8e

commit 40bfb95336cd680ef01b71b96f3b090e82301c8e
Author: Dániel Bátyai <dbatyai@inf.u-szeged.hu>
Date: Thu Oct 11 00:07:53 2018

conntrackd: Update arm64 seccomp policy

Current policy is not compiling, update it with the
appropriate syscalls.

BUG=chromium:878565
TEST=conntrackd starts and runs without issues

Change-Id: I1b67f6afc06349c3110b7a6a6dd4d0434331a93f
Reviewed-on: https://chromium-review.googlesource.com/1273148
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Daniel Batyai <dbatyai@inf.u-szeged.hu>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/40bfb95336cd680ef01b71b96f3b090e82301c8e/net-firewall/conntrack-tools/files/conntrackd-seccomp-arm64.policy
[rename] https://crrev.com/40bfb95336cd680ef01b71b96f3b090e82301c8e/net-firewall/conntrack-tools/conntrack-tools-1.4.4-r10.ebuild

Project Member

Comment 70 by bugdroid1@chromium.org, Oct 11

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/mosys/+/e37be98e53b0627a75f295f9c1d61ab0c6f237d1

commit e37be98e53b0627a75f295f9c1d61ab0c6f237d1
Author: Adam Kallai <kadam@inf.u-szeged.hu>
Date: Thu Oct 11 15:55:58 2018

mosys: Fix the seccomp policy filter on arm64

send is a nonexistent syscall on arm64, use sendto instead.

BUG=chromium:878565
TEST='test mosys manually'

Change-Id: I45dba9feec2d1db0f2c420f9076a87c15fea695e
Reviewed-on: https://chromium-review.googlesource.com/1268375
Commit-Ready: Adam Kallai <kadam@inf.u-szeged.hu>
Tested-by: Adam Kallai <kadam@inf.u-szeged.hu>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/e37be98e53b0627a75f295f9c1d61ab0c6f237d1/seccomp/mosys-seccomp-arm64.policy

Blockedon: 899796
Project Member

Comment 72 by bugdroid1@chromium.org, Nov 20

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/e15bc9c43a515a3cd7e046330485b85ef5e4c4ec

commit e15bc9c43a515a3cd7e046330485b85ef5e4c4ec
Author: Manoj Gupta <manojgupta@google.com>
Date: Tue Nov 20 13:52:37 2018

memd: Add pselect6 to arm64 policy.

Add pselect6 syscall to arm64 to avoid memd getting killed
by sig 31 on kevin64.

BUG=chromium:878565
TEST=No more memd crash logs in /var/spool/crash

Change-Id: I1394ae3543589cd422132274a290824bdd14abd6
Reviewed-on: https://chromium-review.googlesource.com/1338901
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Luigi Semenzato <semenzato@chromium.org>
Reviewed-by: Caroline Tice <cmtice@chromium.org>

[modify] https://crrev.com/e15bc9c43a515a3cd7e046330485b85ef5e4c4ec/metrics/memd/init/memd-seccomp-arm64.policy

Blockedon: 908588
Blockedon: 909017
Project Member

Comment 75 by bugdroid1@chromium.org, Dec 3

Labels: merge-merged-release-R72-11316.B
The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/d5350334f0f9240634fe4ba048e9fae41ffcea1b

commit d5350334f0f9240634fe4ba048e9fae41ffcea1b
Author: Bernie Thompson <bhthompson@chromium.org>
Date: Mon Dec 03 19:50:22 2018

Revert "chromeos_config: Add kevin64-full builder."

This reverts commit d15b2011d9c0ec0dcb683a0456360ae950889e1f.

Reason for revert: crbug.com/911235

Original change's description:
> chromeos_config: Add kevin64-full builder.
> 
> We want to start testing AArch64 userspace in Chrome OS.
> So start testing kevin64-full builds.
> 
> BUG=chromium:878565
> TEST=chromite unit tests pass
> 
> Change-Id: Id424b7c349bed433e5984b3f73045f2cc6709dab
> Reviewed-on: https://chromium-review.googlesource.com/1200173
> Commit-Ready: Manoj Gupta <manojgupta@chromium.org>
> Tested-by: Manoj Gupta <manojgupta@chromium.org>
> Reviewed-by: Mattias Nissler <mnissler@chromium.org>
> Reviewed-by: Luis Lozano <llozano@chromium.org>

Bug: chromium:878565
Change-Id: I9a9fb4957ef1c14ad7a4cd9070182190c73af969
Reviewed-on: https://chromium-review.googlesource.com/c/1359013
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Commit-Queue: Bernie Thompson <bhthompson@chromium.org>
Tested-by: Bernie Thompson <bhthompson@chromium.org>

[modify] https://crrev.com/d5350334f0f9240634fe4ba048e9fae41ffcea1b/config/chromeos_config.py
[modify] https://crrev.com/d5350334f0f9240634fe4ba048e9fae41ffcea1b/config/waterfall_layout_dump.txt
[modify] https://crrev.com/d5350334f0f9240634fe4ba048e9fae41ffcea1b/config/config_dump.json

Blockedon: 908113
Blockedon: 912372
Project Member

Comment 78 by bugdroid1@chromium.org, Dec 6

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/55fbf5947b5c36906b186bed99b4d029f87d4df3

commit 55fbf5947b5c36906b186bed99b4d029f87d4df3
Author: Dániel Bátyai <dbatyai@inf.u-szeged.hu>
Date: Thu Dec 06 11:42:00 2018

Enable gold linker for arm64 linux builds

Arm64 builds for chromeos do not currently use gold when linking.
This change enables gold, which results in smaller binary size.

Bug: 878565
Change-Id: I70f24490ac010ce58bcc6fd1441ade63288147ad
Reviewed-on: https://chromium-review.googlesource.com/c/1341913
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: Peter Gal <pgal.u-szeged@partner.samsung.com>
Cr-Commit-Position: refs/heads/master@{#614317}
[modify] https://crrev.com/55fbf5947b5c36906b186bed99b4d029f87d4df3/build/config/compiler/compiler.gni

Blockedon: 913071
Blockedon: 913088
Blockedon: 913596
Blockedon: 914633
Blockedon: 915558
Blockedon: 917919
Project Member

Comment 85 by bugdroid1@chromium.org, Jan 7

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/45a2fcf1fc36ba611a5665ca011b1712a1564ffa

commit 45a2fcf1fc36ba611a5665ca011b1712a1564ffa
Author: Chris McDonald <cjmcdonald@chromium.org>
Date: Mon Jan 07 22:59:36 2019

chromeos_config: Mark kevin64-full and lakitu-full as unimportant

These builders failing for a month hasn't been a problem, so they
shouldn't be important enough to mark master-full as failng.

BUG=chromium:919630, chromium:878565
TEST=None

Change-Id: Ie982efffa5d1696b7e5e55e00665065bfc0c94dd
Reviewed-on: https://chromium-review.googlesource.com/1399461
Commit-Ready: Chris McDonald <cjmcdonald@chromium.org>
Tested-by: Chris McDonald <cjmcdonald@chromium.org>
Reviewed-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Nichols <mikenichols@chromium.org>

[modify] https://crrev.com/45a2fcf1fc36ba611a5665ca011b1712a1564ffa/config/chromeos_config.py
[modify] https://crrev.com/45a2fcf1fc36ba611a5665ca011b1712a1564ffa/config/config_dump.json

Status: Assigned (was: Untriaged)
This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.

Comment 87 by manojgupta@chromium.org, Today (10 hours ago)

Blockedon: 924361

Comment 88 by manojgupta@chromium.org, Today (8 hours ago)

Blockedon: 924378

Sign in to add a comment