With recent patches to Kernel, open-dice supports ACPI device
configuration, this CL flips the flag for enabling it.
Bug: 510177847
Test: build
Change-Id: If9db8e6084883eae2c25370aafeadb624485c5bd
Signed-off-by: Song Guo <songguo@google.com>
Upstream added a new backtrace-suppression kunit test module that builds
by default with CONFIG_KUNIT_TEST, so add it to the list of kunit common
modules.
Fixes: bbc960d009 ("kunit: Add backtrace suppression self-tests")
Change-Id: I954b297b363b229d7458aabb553077df5cfbe28b
Signed-off-by: Carlos Llamas <cmllamas@google.com>
Update the GKI compiler version to r596125.
Bug: 524750479
Test: tools/bazel run //common:kernel_aarch64_dist
Assisted-by: Antigravity:Gemini-Next
Change-Id: Ibb1a89bea6909e309f6945536130a833c147b594
Signed-off-by: HONG Yifan <elsk@google.com>
This adds the Android Wonder Wi-Fi virtual device driver as a GKI
module.
Bug: 505327866
Change-Id: I015c1ff183805701d02495f8e4f45ddf84175282
Signed-off-by: Will McVicker <willmcvicker@google.com>
get_kunit_modules_superset() returns the full superset of KUnit module
paths as a plain list (no select()), making it safe to call at Bazel
load time. Re-export it from the public modules.bzl so downstream
can use it to auto-derive KUnit module lists without duplicating
or manually syncing the list.
Bug: 519179681
Change-Id: Ibe0b2cc88fb421a7ac1e43cecd6d38ababce52b8
Signed-off-by: Satya Durga Srinivasu Prabhala <satyap@qti.qualcomm.com>
(cherry picked from commit 73860a1ea8361064ec22303e318cb240d018b722)
Enable support for BBR (Bottleneck Bandwidth and RTT) TCP congestion
control algorithm, which maximizes network utilization under certain
scenarios. Note this still maintains CUBIC as the default algorithm.
Bug: 362198193
Change-Id: I2885893e565f91d14cb2c139d975e4abfee80daf
Signed-off-by: wuwei1 <11150500@vivo.corp-partner.google.com>
Signed-off-by: Carlos Llamas <cmllamas@google.com>
(cherry picked from commit ee7395c4cb9b2e56e8f2dae5ac4a9f9cb9d78192)
(cherry picked from commit eadaba3bbc28dff77f64d21aec830b72f4e235de)
Update the rustc version used for Linux to 1.95.0.
Bug: 519669611
Change-Id: I48670fe60f50ee8980d2934e69ecd989e7f6ba02
Signed-off-by: Alice Ryhl <aliceryhl@google.com>
CRYPTO_LIB_SHA3 is no longer implicitly enabled for non-FIPS kernels
after commit 4061bc8c03 ("crypto: rng - Don't pull in DRBG when
CRYPTO_FIPS=n"). Since this library is no longer built for GKI, let's
also disable its corresponding kunit testing module as its dependencies
are no longer met:
| ERROR: CONFIG_CRYPTO_LIB_SHA3_KUNIT_TEST: actual '', expected 'm'
Cc: Eric Biggers <ebiggers@google.com>
Fixes: 4061bc8c03 ("crypto: rng - Don't pull in DRBG when CRYPTO_FIPS=n")
Change-Id: I38be6547adf6703dae6616fe9322d8481bcd4383
Signed-off-by: Carlos Llamas <cmllamas@google.com>
This reverts commit 803c55fa56 to pull in
the cfg/mac80211 modules to GKI.
Bug: 505327866
Signed-off-by: Will McVicker <willmcvicker@google.com>
[willmcvicker: resolve trivial merge conflicts]
Change-Id: Icbaec0963cf0f7430c1f79e6b04df717789519d8
The ext4-inode-test.ko module has been renamed upstream to ext4-test.ko
so update our bazel and tradefed files accordingly.
Fixes: 519b76ac0b ("ext4: fix mballoc-test.c is not compiled when EXT4_KUNIT_TESTS=M"
Change-Id: I42c7ca1d7d0d280d90cac669dbd5deae19668e54
Signed-off-by: Carlos Llamas <cmllamas@google.com>
Upstream now selects POWER_SEQUENCING indirectly through PCIE_QCOM ->
PCI_PWRCTRL_SLOT -> POWER_SEQUENCING, so we no longer need to enable
this option explicitly. However, PCIE_QCOM is a built-in option only,
which forces the other tristate options to also be built-in.
Cc: Todd Kjos <tkjos@google.com>
Fixes: 9cb64f61ec ("PCI/pwrctrl: Add PCIe M.2 connector support")
Change-Id: I0cd66aa0d65ca2ec3ef549e6dce9aadc0c749d6d
Signed-off-by: Carlos Llamas <cmllamas@google.com>
* The current issue is that unsafe headers is a target build on demand
when the `allow_ddk_unsafe_headers` flag is set, for this reason this
test uses a transition to force that flag to be set.
* This introduces a new Bazel sub-package bazel/test which could be used
later for more tests if needed.
Tested: tools/bazel test //common/bazel/test
Bug: 325638347
Change-Id: I47236bb625e5d114c0c383035b0e4da809b0ff31
Signed-off-by: Ulises Mendez Martinez <umendez@google.com>
When --kasan, --kasan_sw_tags or --kasan_generic is specified, do not
build rust modules.
This change alone has no effect, but it is created so that it can be
easily cherry-picked to other branches.
Bug: 485668317
Change-Id: I59d4c983a4adbd759fdc0de04a17b6a31d2cb386
Signed-off-by: HONG Yifan <elsk@google.com>
The COMMON_GKI_MODULES_LIST is not used anywhere. This is ensured
by visibility private of modules_private.bzl.
Bug: 485668317
Change-Id: I035497f7efb3d67e7f05d831daf11eee13399d12
Signed-off-by: HONG Yifan <elsk@google.com>
The kernel's crypto library now has KUnit tests. Enable them as modules
in gki_defconfig for both arm64 and x86_64, and add them to the Tradefed
test config.
Specifically, enable the tests for algorithms that are already enabled
in the kconfig. However, that just means all the tests, since all
algorithms with KUnit tests are already enabled in gki_defconfig.
Bug: 486247481
Test: kernel/tests/tools/run_test_only.sh -s 0.0.0.0:6520 \
-t kunit:blake2b_kunit \
-t kunit:blake2s_kunit \
-t kunit:curve25519_kunit \
-t kunit:md5_kunit \
-t kunit:poly1305_kunit \
-t kunit:polyval_kunit \
-t kunit:sha1_kunit \
-t kunit:sha224_kunit \
-t kunit:sha256_kunit \
-t kunit:sha3_kunit \
-t kunit:sha384_kunit \
-t kunit:sha512_kunit \
-td ~/src/android-mainline/out/virtual_device_x86_64/dist/tests.zip
Test: same as above but with arm64 cuttlefish instead of x86_64 cuttlefish
Change-Id: Ie9af6c77deead6b9d6add82fff901cff56641ff7
Signed-off-by: Eric Biggers <ebiggers@google.com>
This reverts commit 1b5a5cb71d.
CONFIG_TLS introduces and unacceptable attack surface. Since it was
enabled in December 2024, we have received an influx of security reports
which have been directly attributable to the aforementioned commit. To
ensure a greater level of system integrity going forward, we are
disabling its use completely.
BoringSSL remains the sole approved implementation of TLS in Android.
Current users of CONFIG_TLS should convert their workflows back over to
BoringSSL immediately.
Bug: 459542688
Change-Id: Ifb828e6fcb7f8fda75a50a3338dbdafe6c9de4a7
Signed-off-by: Lee Jones <joneslee@google.com>
This is Rust part of the compiler pair the toolchain team has matched
LLVM revisions of and produced a release branch for.
For cross-lang helper inlining to work, this needs to be paired with
r584948, but updating clang to that revision tickles several other bugs
at the moment.
This does not include an update to r584948 because that requires further
updates elsewhere.
Bug: 457798339
Change-Id: I629aaea4643720b2327eff7dd7f1807eaebd6fbc
Signed-off-by: Matthew Maurer <mmaurer@google.com>
This is the old build.config.constants, with quotes added. It is
preferred for Bazel rules to load bazel/constants.scl directly.
During the migration phase, we keep the build.config.constants symlink.
Once all users have been moved, we can delete the symlink.
Bug: 448148817
Change-Id: I3f9a66d3795b4a542a8ffd4d53aac1e39345c162
Signed-off-by: HONG Yifan <elsk@google.com>
Move most bazel files, like abi.bzl and modules.bzl, to the
bazel/ folder. This is so that our top-level directory
is clean from Android-specific files.
Re-export some symbols in the top-level modules.bzl file. This is
so that we still allow mixed builds to use it.
Bug: 448148817
Change-Id: Id6b7565c4de57fb8951d98896e027657d456a75f
Signed-off-by: HONG Yifan <elsk@google.com>
Song Guo
Carlos Llamas
HONG Yifan
Will McVicker
Satya Durga Srinivasu Prabhala
wuwei1
Eric Biggers
Alice Ryhl
Ulises Mendez Martinez
Lee Jones
Matthew Maurer