crosvm/seccomp/x86_64/battery.policy

# Copyright 2020 The Chromium OS Authors. All rights reserved.
# Use of this source code is governed by a BSD-style license that can be
# found in the LICENSE file.

@include /usr/share/policy/crosvm/common_device.policy

# Syscalls used by power_monitor's powerd implementation.
clock_getres: 1
connect: 1
getegid: 1
geteuid: 1
getrandom: 1
getresgid: 1
getresuid: 1
getsockname: 1
openat: 1
socket: arg0 == AF_UNIX
tgkill: 1
prctl: arg0 == PR_SET_NAME
Goldfish battery: create a irq thread The goldfish battery irq will be used to notify the guest driver that battery/ac status changed. And the status changing will be done through external crosvm commands. So the irq injection needs to be done in a seperate thread which can receive these commands. BUG=chromium:1050432 BUG=b:137890633 TEST=create VM with parameter "--battery" or "--battery=type=goldfish" and boot linux guest with goldfish_battery driver enabled. The sysfs created by the goldfish_battery driver have no issue observed. TEST=goldfish_battery driver is loaded on ARCVM and interrupts are enabled Change-Id: Icc902dd8c00bdcf6cb271b20d928a4081533dde6 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2119573 Commit-Queue: Alex Lau <alexlau@chromium.org> Tested-by: Alex Lau <alexlau@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> 2020-04-27 08:37:10 +00:00			`# Copyright 2020 The Chromium OS Authors. All rights reserved.`
			`# Use of this source code is governed by a BSD-style license that can be`
			`# found in the LICENSE file.`

			`@include /usr/share/policy/crosvm/common_device.policy`
devices: Use PowerMonitor trait objects as a data source for GoldfishBattery. This CL wires up the powerd D-Bus PowerMonitor implementation to GoldfishBattery. BUG=b:137890633 TEST=observe updated power data in ARCVM's /sys/class/power_supply after crrev.com/c/2550102 Change-Id: I38c613f13d3f7601435532213c7733558cb5f83f Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2560276 Commit-Queue: Alex Lau <alexlau@chromium.org> Tested-by: Alex Lau <alexlau@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> 2020-11-10 09:24:04 +00:00
			`# Syscalls used by power_monitor's powerd implementation.`
			`clock_getres: 1`
			`connect: 1`
			`getegid: 1`
			`geteuid: 1`
			`getrandom: 1`
			`getresgid: 1`
			`getresuid: 1`
			`getsockname: 1`
			`openat: 1`
			`socket: arg0 == AF_UNIX`
			`tgkill: 1`
Specify prctl's policy only once per device The libminijail version in AOSP complains when there are multiple entries for the same system call, which was the case for virtio-fs's policy. BUG=b/185811304 Change-Id: I389c07c86e7d79f16e4f47a893abad598033352a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2837307 Commit-Queue: Jorge Moreira Broche <jemoreira@google.com> Tested-by: Jorge Moreira Broche <jemoreira@google.com> Reviewed-by: Dylan Reid <dgreid@chromium.org> 2021-04-19 19:59:38 +00:00			`prctl: arg0 == PR_SET_NAME`