blob: 2c05c88faa33f9c709cc631ea29b4a753225859d [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?><manifest revision="96f33d2d835a8a62abda3e56b69711b7bedb7d50">
<notice>Your sources have been sync'd successfully.</notice>
<remote fetch="https://android.googlesource.com" name="aosp" review="https://android-review.googlesource.com"/>
<remote alias="cros" fetch="https://chromium.googlesource.com/" name="chromium"/>
<remote fetch="https://chromium.googlesource.com" name="cros" review="https://chromium-review.googlesource.com"/>
<default remote="cros" revision="refs/heads/master" sync-j="8"/>
<project name="aosp/platform/external/libchrome" path="src/aosp/external/libchrome" revision="536f6cb9217032dfd1d4cdbfc35b5d1c316cec27" upstream="refs/heads/master"/>
<project name="aosp/platform/external/modp_b64" path="src/third_party/modp_b64" revision="99dc13926931cedfd2e4e582c33ef657d0645c5c" upstream="refs/heads/master"/>
<project name="aosp/platform/system/core/libsync" path="src/aosp/system/libsync" revision="f4f4387b6bf2387efbcfd1453af4892e8982faf6" upstream="refs/heads/master"/>
<project groups="devserver" name="aosp/platform/system/update_engine" path="src/aosp/system/update_engine" revision="6600a5670fb9cfc7ad6a01b926b301d63fa2504c" upstream="refs/heads/master"/>
<project name="apps/libapps" path="src/third_party/libapps" revision="add574af97220eb1b2636478d013d993d755ab13" upstream="refs/heads/master">
<annotation name="branch-mode" value="pin"/>
</project>
<project groups="minilayout,buildtools,labtools" name="chromium/buildtools" path="chromium/src/buildtools" remote="chromium" revision="2dff9c9c74e9d732e6fe57c84ef7fd044cc45d96" upstream="refs/heads/master"/>
<project name="chromium/deps/libmtp" path="chromium/src/third_party/libmtp" remote="chromium" revision="4f4fad584e9c2735af5131f15b697376a3327de5" upstream="refs/heads/master"/>
<project groups="minilayout,buildtools,labtools" name="chromium/llvm-project/cfe/tools/clang-format" path="chromium/src/buildtools/clang_format/script" remote="chromium" revision="e863ca54661220d08584387b537cec1d327c9bb7" upstream="refs/heads/master"/>
<project name="chromium/src/third_party/Python-Markdown" remote="chromium" revision="b08af21eb795e522e1b972cb85bff59edb1ae209" upstream="refs/heads/master"/>
<project name="chromium/src/tools/md_browser" remote="chromium" revision="e9462696241f3ca832890473173e03e7bcfe6adc" upstream="refs/heads/master"/>
<project groups="minilayout,firmware,buildtools,labtools" name="chromium/tools/depot_tools" remote="chromium" revision="b56a43a9064c35e81be989f5e86a19d9159d5edf"/>
<project groups="minilayout,firmware,buildtools,chromeos-admin,labtools,sysmon,devserver" name="chromiumos/chromite" path="chromite" revision="84f3a15fd9dbacfcf36c396f5817cfd0e81948b3" upstream="refs/heads/master">
<copyfile dest="AUTHORS" src="AUTHORS"/>
<copyfile dest="LICENSE" src="LICENSE"/>
</project>
<project name="chromiumos/containers/cros-container-guest-tools" path="src/platform/container-guest-tools" revision="65a0aa2c4ebbeac041efdca62548a37d06bc8500" upstream="refs/heads/master"/>
<project name="chromiumos/docs" path="docs" revision="7a60959b83de5fef032a7418c30264b3db28c81a" upstream="refs/heads/master"/>
<project name="chromiumos/graphyte" path="src/platform/graphyte" revision="7ea5c995be1ba3ff1a39e5e63fdee4b57c6434e5" upstream="refs/heads/master"/>
<project name="chromiumos/infra/bad_cl_detector" path="infra/bad_cl_detector" revision="a6bade48153992dc3d91697c45db9d36231e3bfc" upstream="refs/heads/master"/>
<project groups="chromeos-admin" name="chromiumos/infra/ci_results_archiver" path="infra/ci_results_archiver" revision="99eedf2be93b1541372aab49f215e9a2121ccb4f" upstream="refs/heads/master"/>
<project name="chromiumos/infra/cl_exonerator" path="infra/cl_exonerator" revision="55604ba5f4656c70f961b3f7b2a70f5237e7f524" upstream="refs/heads/master"/>
<project name="chromiumos/infra/cl_status_viewer" path="infra/cl_status_viewer" revision="34e08efb0d563250219a4013cfdd9a732a43281c" upstream="refs/heads/master"/>
<project name="chromiumos/infra/distfiles_updater" path="infra/distfiles_updater" revision="2d1aa33972b2028d19a288baaacee9b2cd8644f7" upstream="refs/heads/master"/>
<project name="chromiumos/infra/dummies/general-sandbox" path="infra/dummies/general-sandbox" revision="ab009ffebb68a58f37779bddfba5f1a08ef174ae" upstream="refs/heads/master"/>
<project name="chromiumos/infra/dummies/merge-sandbox" path="infra/dummies/merge-sandbox" revision="651c1f3b89c112222f5dae2f79091421543dd4ee" upstream="refs/heads/master"/>
<project name="chromiumos/infra/logstock" path="infra/logstock" revision="ef7fe408b9feee9a3664b36f0176fcacd27bf703" upstream="refs/heads/master"/>
<project name="chromiumos/infra/lucifer" path="infra/lucifer" revision="2acc418e29fd37c496a27fb76a1cc21155be07c9" upstream="refs/heads/master"/>
<project groups="chromeos-admin,labtools" name="chromiumos/infra/skylab_inventory" path="infra/skylab_inventory" revision="b59294416a54db235bdb232f501fd4331a3d2f38" upstream="refs/heads/master"/>
<project name="chromiumos/infra/suite_scheduler" path="infra/suite_scheduler" revision="e58fa2b39a63fc1ae6eecbd836ac98a0e21b3bdf" upstream="refs/heads/master"/>
<project name="chromiumos/infra/test_analyzer" path="infra/test_analyzer" revision="7b0a71303075b11ce506fe6c34477a139c02236e" upstream="refs/heads/master"/>
<project groups="minilayout,firmware,buildtools,chromeos-admin,labtools,sysmon,devserver" name="chromiumos/infra_virtualenv" path="infra_virtualenv" revision="bd33427afb37ec05127792091ffc87bfefb48121" upstream="refs/heads/master"/>
<project name="chromiumos/manifest" path="manifest" revision="6fd39756ec4507b864fb1c87a056cf576d4a1418" upstream="refs/heads/master"/>
<project groups="minilayout,firmware" name="chromiumos/overlays/board-overlays" path="src/overlays" revision="6737faa47ffa8800eac042c0c2449c626ba6ee63" upstream="refs/heads/master"/>
<project groups="minilayout,firmware,labtools" name="chromiumos/overlays/chromiumos-overlay" path="src/third_party/chromiumos-overlay" revision="c5109d8831c8ffb588e75394ee52cb933986efe3" sync-c="true" upstream="refs/heads/master"/>
<project groups="minilayout,firmware,labtools" name="chromiumos/overlays/eclass-overlay" path="src/third_party/eclass-overlay" revision="2487b54a23e982d72e8dfcedfc72231c0c26f751" upstream="refs/heads/master"/>
<project groups="minilayout,firmware,labtools" name="chromiumos/overlays/portage-stable" path="src/third_party/portage-stable" revision="3aa0af160b9f55f20bf0362ae9dd6d9c6dc7fd77" upstream="refs/heads/master"/>
<project name="chromiumos/platform/arc-camera" path="src/platform/arc-camera" revision="343213b1bbf6e8ca3d5f2feac876e81d3e890763" upstream="refs/heads/master"/>
<project name="chromiumos/platform/assets" path="src/platform/assets" revision="0f7239e3a5b58ad794f43cdc484dc7a788612707" upstream="refs/heads/master"/>
<project name="chromiumos/platform/audiotest" path="src/platform/audiotest" revision="d3425a28229eadfe4b8dfb0b34f2ea19b83262fd" upstream="refs/heads/master"/>
<project name="chromiumos/platform/battery_updater" path="src/platform/battery_updater" revision="32463c6de8e8c98d4b1711937bc7678afc121a85" upstream="refs/heads/master"/>
<project name="chromiumos/platform/bisect-kit" path="src/platform/bisect-kit" revision="41e8b59d6c07784c80fb4bcc916fb1dc1628f756" upstream="refs/heads/master"/>
<project name="chromiumos/platform/bmpblk" path="src/platform/bmpblk" revision="df73851087be0b359a9424dbcedcfaefe9161643" upstream="refs/heads/master"/>
<project name="chromiumos/platform/bootcache" path="src/platform/bootcache" revision="ebe3a0995e90026433ffc62b7aeed6cad1f28694" upstream="refs/heads/master"/>
<project name="chromiumos/platform/btsocket" path="src/platform/btsocket" revision="300354e5d74418c8e03737ca9029c64d9297a28d" upstream="refs/heads/master"/>
<project name="chromiumos/platform/cfm-device-monitor" path="src/platform/cfm-device-monitor" revision="a5510e1f1d06e09f905a5077e573cc610f191eeb" upstream="refs/heads/master"/>
<project name="chromiumos/platform/chameleon" path="src/platform/chameleon" revision="8eba23f5419f5e491692eed20fb3edb69f5b0c4e" upstream="refs/heads/master"/>
<project name="chromiumos/platform/chromiumos-assets" path="src/platform/chromiumos-assets" revision="fd4e8eef335ceaca7adf53a83f5e13e00e09101c" upstream="refs/heads/master"/>
<project name="chromiumos/platform/cobble" path="src/platform/cobble" revision="85e6e13ae4e3ba22f1970ebfe66610866e89132d" upstream="refs/heads/master"/>
<project groups="minilayout,firmware,buildtools" name="chromiumos/platform/crostestutils" path="src/platform/crostestutils" revision="64c3e18bc6ada35fdde8dfe24c248a53f16d3cb5" upstream="refs/heads/master"/>
<project groups="minilayout,firmware,buildtools,labtools" name="chromiumos/platform/crosutils" path="src/scripts" revision="04dc2ed7f855093c3864c796ec610f6f6ea80bca" upstream="refs/heads/master"/>
<project name="chromiumos/platform/crosvm" path="src/platform/crosvm" revision="b605850bce94e476539a0843cae2092d91daff5a" upstream="refs/heads/master"/>
<project groups="firmware" name="chromiumos/platform/depthcharge" path="src/platform/depthcharge" revision="4e7824a910004e7267c0b9ab45c5b784e5fae735" upstream="refs/heads/master"/>
<project groups="minilayout,firmware,buildtools,devserver" name="chromiumos/platform/dev-util" path="src/platform/dev" revision="2a76af0a6100c62b2a6064cd673ba0a83dbd3c9f" upstream="refs/heads/master"/>
<project name="chromiumos/platform/dm-verity" path="src/platform/verity" revision="e4d233306d0a67b2527fbaff03a9d912922a56cd" upstream="refs/heads/master"/>
<project name="chromiumos/platform/drm-tests" path="src/platform/drm-tests" revision="c7f04e45df9df08b96413d5ac128fd1ded034b9e" upstream="refs/heads/master"/>
<project groups="firmware" name="chromiumos/platform/ec" path="src/platform/ec" revision="c06af8d8c2326a3ebc096dfaa4a2640c1ded1333" upstream="refs/heads/master"/>
<project name="chromiumos/platform/experimental" path="src/platform/experimental" revision="bcc00ca58726d9cf774c56005715a5ee330da045" upstream="refs/heads/master"/>
<project name="chromiumos/platform/factory" path="src/platform/factory" revision="a20766e2e40929c0bb96af340163deb5229bceb3" upstream="refs/heads/master"/>
<project name="chromiumos/platform/factory_installer" path="src/platform/factory_installer" revision="d796f89a8d5c960864ce77c3c6c782cce6d0da4d" upstream="refs/heads/master"/>
<project groups="firmware" name="chromiumos/platform/firmware" path="src/platform/firmware" revision="324e7866a0e6d2f3a5387c408af2013480a2e301" upstream="refs/heads/master"/>
<project name="chromiumos/platform/frecon" path="src/platform/frecon" revision="fbd668b02214a81e304732e1703ae9909271e04e" upstream="refs/heads/master"/>
<project name="chromiumos/platform/gestures" path="src/platform/gestures" revision="00b09c9f8f54be25711bcac0e332906266a713cb" upstream="refs/heads/master"/>
<project name="chromiumos/platform/go-seccomp" path="src/platform/go-seccomp" revision="613458c0e3c589e52e7f093288ef1d2ba57a9ff7" upstream="refs/heads/master"/>
<project name="chromiumos/platform/google-breakpad" path="src/third_party/breakpad" revision="54fa71efbe50fb2b58096d871575b59e12edba6d" upstream="refs/heads/master"/>
<project name="chromiumos/platform/initramfs" path="src/platform/initramfs" revision="56404ffa5f2e43e2ef7df00fd7fb2b99d84dd9f9" upstream="refs/heads/master"/>
<project name="chromiumos/platform/inputcontrol" path="src/platform/inputcontrol" revision="8826acba1c4e13b6318ae6d1d4b49633d1b55aba" upstream="refs/heads/master"/>
<project name="chromiumos/platform/jabra_vold" path="src/platform/jabra_vold" revision="8830911158ae632b7626d0ebe33248e66ffaeef3" upstream="refs/heads/master"/>
<project name="chromiumos/platform/libevdev" path="src/platform/libevdev" revision="23f8ea74685ea0a03be8649ca33d5664bc789393" upstream="refs/heads/master"/>
<project name="chromiumos/platform/microbenchmarks" path="src/platform/microbenchmarks" revision="518003bc070970f25b9ab97c0560d762846c5e65" upstream="refs/heads/master"/>
<project name="chromiumos/platform/minigbm" path="src/platform/minigbm" revision="617ee71c986e3a261a272e4e09d3e5b5ae908cd3" upstream="refs/heads/master"/>
<project name="chromiumos/platform/moblab" path="src/platform/moblab" revision="439a5487f9070864a879ff553282e7fad912679a" upstream="refs/heads/master"/>
<project name="chromiumos/platform/mosys" path="src/platform/mosys" revision="cccc704e262d33b3465d174a7d2d86680093e84f" upstream="refs/heads/master"/>
<project name="chromiumos/platform/mttools" path="src/platform/mttools" revision="146a68465feb9039602bcaa508ef3fea8e8f926a" upstream="refs/heads/master"/>
<project name="chromiumos/platform/newblue" path="src/platform/newblue" revision="26a590ae6bf01f25a336da849dde93ed005c0169" upstream="refs/heads/master"/>
<project name="chromiumos/platform/punybench" path="src/platform/punybench" revision="16bc496a97c027147453e7d675ae2f9147352b31" upstream="refs/heads/master"/>
<project name="chromiumos/platform/system_api" path="src/platform/system_api" revision="f63dc2e08f0c619b185cd48de3dcf758bcd9d109" upstream="refs/heads/master"/>
<project name="chromiumos/platform/tast" path="src/platform/tast" revision="0028613a1272a3f70b498770ef2348bf4fbf1c97" upstream="refs/heads/master"/>
<project name="chromiumos/platform/tast-tests" path="src/platform/tast-tests" revision="2f05c69330879c875332b1b816dc0125251a4835" upstream="refs/heads/master"/>
<project groups="firmware" name="chromiumos/platform/touch_firmware_test" path="src/platform/touch_firmware_test" revision="bafba938ff65099158b04ca718b1e77a0e43c5c4" upstream="refs/heads/master"/>
<project name="chromiumos/platform/touch_updater" path="src/platform/touch_updater" revision="5bc80f22a8cadf400e796f585278bc04f18201af" upstream="refs/heads/master"/>
<project name="chromiumos/platform/touchbot" path="src/platform/touchbot" revision="9546ffbb37d5fef191ad1607eeb0b76a6f3a9872" upstream="refs/heads/master"/>
<project name="chromiumos/platform/touchpad-tests" path="src/platform/touchpad-tests" revision="f3e4d3bca41b674e89583d74dfb7e538fe58ff18" upstream="refs/heads/master"/>
<project groups="firmware" name="chromiumos/platform/tpm" path="src/third_party/tpm" revision="0cba6cadd1bea1ce3717779201d594c4c9131dc2" upstream="refs/heads/master"/>
<project name="chromiumos/platform/tpm_lite" path="src/platform/tpm_lite" revision="db50af69b91bc1cffde13740c23aed72883fbc45" upstream="refs/heads/master"/>
<project name="chromiumos/platform/tremplin" path="src/platform/tremplin" revision="97641e724229dd199a9f5242482e73730eb76080" upstream="refs/heads/master"/>
<project name="chromiumos/platform/uboot-env" path="src/platform/uboot-env" revision="ab10366ee27959666b94a638858032c91c3c5e10" upstream="refs/heads/master"/>
<project groups="firmware,buildtools" name="chromiumos/platform/vboot_reference" path="src/platform/vboot_reference" revision="cf6b7a9c522a5b62714dee304ee4e6bec8a45ab8" upstream="refs/heads/master"/>
<project name="chromiumos/platform/vpd" path="src/platform/vpd" revision="4649d42d10a7fa32f18da7e77e019891d1d7d940" upstream="refs/heads/master"/>
<project name="chromiumos/platform/webplot" path="src/platform/webplot" revision="bbd5ea22ef9f8e109e363b26958d9a2fc8921f0f" upstream="refs/heads/master"/>
<project name="chromiumos/platform/xorg-conf" path="src/platform/xorg-conf" revision="f33e0c49f9be3224c3b02dee2c40638c5013f911" upstream="refs/heads/master"/>
<project name="chromiumos/platform2" path="src/platform2" revision="086ac8c78c91c3b64c2dcaab9a776a7ea9ac2889" upstream="refs/heads/master"/>
<project groups="minilayout,firmware,buildtools,labtools" name="chromiumos/repohooks" path="src/repohooks" revision="68838dd0d1932b1c0be3bab077ff0676deba33ce" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/adhd" path="src/third_party/adhd" revision="d08e1f54eb1b5d50d223643d98d757eb5703fb27" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/android_mtdutils" path="src/third_party/android_mtdutils" revision="9bcfc3ee238f16925e9aaa4573129784ebb397e7" upstream="chromeos"/>
<project name="chromiumos/third_party/arm-trusted-firmware" path="src/third_party/arm-trusted-firmware" revision="b8dc3f146d9bf647c98c695b3a23f294d2aa7eb2" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/atheros" path="src/third_party/atheros" revision="52a5bdaa8930c14ee42518354de3e5ec09911c6b" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/atrusctl" path="src/third_party/atrusctl" revision="f2f9d8df9f307aea2f0c269c81ab7f104b8a4a20" upstream="refs/heads/master"/>
<project groups="buildtools,labtools,devserver" name="chromiumos/third_party/autotest" path="src/third_party/autotest/files" revision="b3dd6c3aafeb2c379299d1f205833d5114baa74d" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/aver-updater" path="src/third_party/aver-updater" revision="cf3337b0918e15755782d8f3b11691e04f1ddc40" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/bluez" path="src/third_party/bluez" revision="cf693389d597515b46e465bed91e06576c22baf9" upstream="refs/heads/chromeos-5.44"/>
<project groups="firmware" name="chromiumos/third_party/bootstub" path="src/third_party/bootstub" revision="6697fe6404055443d7c754b365907a0604f14111" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/broadcom" path="src/third_party/broadcom" revision="4070e7161f2f1a1a22027a744eb868500688f0b6" upstream="refs/heads/master"/>
<project groups="firmware" name="chromiumos/third_party/cbootimage" path="src/third_party/cbootimage" revision="b7d5b2d6a6dd05874d86ee900ff441d261f9034c" upstream="refs/heads/master"/>
<project groups="firmware" name="chromiumos/third_party/coreboot" path="src/third_party/coreboot" revision="149b30032fa779762e69aad5fb6643145871a003" upstream="refs/heads/chromeos-2016.05"/>
<project groups="firmware" name="chromiumos/third_party/coreboot/blobs" path="src/third_party/coreboot/3rdparty/blobs" revision="c2851026e72dcb7b8c1d19e750c0416a6abf41ce" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/cros-adapta" path="src/third_party/cros-adapta" revision="f4dee350b50e18c20a2e7fb6f08ecde4f21f8f16" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/cryptoc" path="src/third_party/cryptoc" revision="6283eeeaf5ccebcca982d5318b36d49e7b32cb6d" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/cups" path="src/third_party/cups" revision="49a182a4c42d95c998d97071bba57257090b63ec" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/cypress-tools" path="src/third_party/cypress-tools" revision="043fba1c35f89cce95f804bf6d4f01cfc23a6c21" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/daisydog" path="src/third_party/daisydog" revision="5f4302621d8e011edbd83858b0c3183e29f842b5" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/dbus-cplusplus" path="src/third_party/dbus-c++" revision="907f6244dc1c4c3f58a809147d348eccbb932631" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/dbus-spy" path="src/third_party/dbus-spy" revision="0e04421c73b24536de7fcc1886da469d8b7a2a41" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/displaylink-updater" path="src/third_party/displaylink-updater" revision="a52808b5995fe2ed481269c8f089358d4b451d5c" upstream="refs/heads/master"/>
<project groups="firmware" name="chromiumos/third_party/edk2" path="src/third_party/edk2" revision="ab586ccd21556108662fbd80ab5a429143eac264" upstream="refs/heads/chromeos-2017.08"/>
<project groups="firmware" name="chromiumos/third_party/edk2" path="src/third_party/fsp/cnl/edk2" revision="f71a70e7a4c93a6143d7bad8ab0220a947679697" upstream="refs/heads/chromeos-cnl"/>
<project groups="firmware" name="chromiumos/third_party/edk2" path="src/third_party/fsp/glk/edk2" revision="f71a70e7a4c93a6143d7bad8ab0220a947679697" upstream="refs/heads/chromeos-glk"/>
<project groups="firmware" name="chromiumos/third_party/edk2" path="src/third_party/fsp/icl/edk2" revision="8df83bf3e30ada89fc0799859e3de25017dc93ac" upstream="refs/heads/chromeos-icl"/>
<project groups="firmware" name="chromiumos/third_party/em100" path="src/third_party/em100" revision="6e60dbae5bf62cd0ffffb9fc5ca9ba93e831ee88" upstream="refs/heads/master"/>
<project groups="firmware" name="chromiumos/third_party/flashmap" path="src/third_party/flashmap" revision="9108393752ffd93b133037add1f7b484de09bdbc" upstream="refs/heads/master"/>
<project groups="firmware" name="chromiumos/third_party/flashrom" path="src/third_party/flashrom" revision="6d2cb21d9532f407c2dd5ed5a5e625cb2fefc6a8" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/fwupd" path="src/third_party/fwupd" revision="8fa99b87bc6420d0cd2884ce7ced03c623d7d4ad" upstream="refs/heads/fwupd-1.0.6"/>
<project name="chromiumos/third_party/gdmwimax" path="src/third_party/gdmwimax" revision="e8236b4b2d66b1972e4f84955a238134acd7f6a1" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/gobi3k-sdk" path="src/third_party/gobi3k-sdk" revision="5e5d1a65cbf855609e4d7c9c425615090a834704" upstream="refs/heads/master"/>
<project groups="labtools" name="chromiumos/third_party/hdctools" path="src/third_party/hdctools" revision="e08c4ab196c5375cbd9af6aae2df06e8af6075bb" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/hostap" path="src/third_party/wpa_supplicant" revision="77fe549abeffa773a50f1786313728c176bfdedb" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/hostap" path="src/third_party/wpa_supplicant-2.6" revision="3552549f4a9ce929f45bbeef6f75cb1d77879015" upstream="refs/heads/wpa_supplicant-2.6"/>
<project name="chromiumos/third_party/huddly-updater" path="src/third_party/huddly-updater" revision="98010d4e0c0d1ed95b2b08d9e2b51dcde3d18fe3" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.8" revision="2e98414e6f0294268b61f5e7092c6903a93480f3" upstream="refs/heads/chromeos-3.8"/>
<project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.10" revision="c1a2234c618b383d0ce186d12edea40606eeb9a9" upstream="refs/heads/chromeos-3.10"/>
<project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.14" revision="f28e5fd9555b60454f9cc5ee5c6e02e0a4b1a39a" upstream="refs/heads/chromeos-3.14"/>
<project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.18" revision="551174b127d8084421a88c8a7b890b54cb4d99f2" upstream="refs/heads/chromeos-3.18"/>
<project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v4.4" revision="6463912595d0a66543375d4c5dbc615fa325fa11" upstream="refs/heads/chromeos-4.4"/>
<project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v4.14" revision="7cd688d49857d7941d78a65eb76de4fe75567cd1" upstream="refs/heads/chromeos-4.14"/>
<project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v4.14-mistral" revision="56bea55d9c1d4fb6be12e3b81319cfee010ee205" upstream="refs/heads/chromeos-4.14-mistral"/>
<project name="chromiumos/third_party/kernel" path="src/third_party/kernel/next" revision="874d35a953e406fd27d0f0c16110541c5534d2ab" upstream="refs/heads/next/chromeos-next"/>
<project name="chromiumos/third_party/kernel" path="src/third_party/kernel/experimental" revision="adccdc52dd0f57494637c9274ca260eae2f9c6e0" upstream="refs/heads/next/chromeos-experimental"/>
<project name="chromiumos/third_party/khronos" path="src/third_party/khronos" revision="d41e9e578eef76ebd804f3361eb67fce1009c2b4" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/kvmtool" path="src/third_party/kvmtool" revision="1b159b990afd33c0c2e3b47ebda6dd5cc793dd92" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/libc-bench" path="src/third_party/libc-bench" revision="76793dd4b09191a78a78180012718e72d792717f" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/libdrm" path="src/third_party/libdrm" revision="28328298ca94344538a0d7f41350810f086900ee" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/libmbim" path="src/third_party/libmbim" revision="a828a5b8d61b4a278e67589a080faf4ac79b9605" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/libqmi" path="src/third_party/libqmi" revision="c92163a9e4cb8da6c9f695b771c97555ee8b5c9f" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/libqrtr" path="src/third_party/libqrtr" revision="d3895b9156bf963b92ba568c94d68eb6f7be26d5" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/libscrypt" path="src/third_party/libscrypt" revision="b45c53f9418a6eff2c8ed98703a55f96029304b1" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/libsigrok" path="src/third_party/libsigrok" revision="199fe31115c76231746f5953271795d58679561c" upstream="refs/heads/chromeos"/>
<project name="chromiumos/third_party/libsigrok-cli" path="src/third_party/sigrok-cli" revision="c9edfa218e5a5972531b6f4a3ece8d33a44ae1b5" upstream="refs/heads/chromeos"/>
<project name="chromiumos/third_party/libsigrokdecode" path="src/third_party/libsigrokdecode" revision="3279c2825684c7009775b731d0a9e37815778282" upstream="refs/heads/chromeos"/>
<project name="chromiumos/third_party/libv4lplugins" path="src/third_party/libv4lplugins" revision="5e6034258146af6be973fb6a5bb6b9d6e7489437" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/linux-firmware" path="src/third_party/linux-firmware" revision="be367509666d4a94f0b2844e0630308e19f9abba" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/logitech-updater" path="src/third_party/logitech-updater" revision="e1f835dd60b8b6bbaff5ca9de8a4007ad5bef84d" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/ltp" path="src/third_party/ltp" revision="a65f2a363592cf25342051131358cdf046f20064" upstream="refs/heads/chromeos-20150119"/>
<project name="chromiumos/third_party/marvell" path="src/third_party/marvell" revision="b5d3741d042bde7941284303712c3790ab4e489d" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/mesa" path="src/third_party/arc-mesa" revision="1d88068b471a589d9dc2677f2be8ca8a5abe1d59" upstream="refs/heads/arc-18.2.0-pre1"/>
<project name="chromiumos/third_party/mesa" path="src/third_party/mesa" revision="3e905052248a6e9c0e1ce6b7f32ad5aeff28a7c8" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/mesa" path="src/third_party/mesa-img" revision="129178893b2260df22db96327c5ca9c2ce7db046" upstream="refs/heads/mesa-img"/>
<project name="chromiumos/third_party/mimo-updater" path="src/third_party/mimo-updater" revision="f173901a2ce769fe95b85123f7be445ac9a083a5" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/mmc-utils" path="src/third_party/mmc-utils" revision="1c55306a49b32bbb8c65e1e5e9d630f6720a6810" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/modemmanager-next" path="src/third_party/modemmanager-next" revision="5194d5bc77907627b9b5b28a59e3f1ebb7eacea6" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/nfs-ganesha" path="src/third_party/nfs-ganesha" revision="165395bf01548d8a0135357ca4c222b9c0c0acaa" upstream="refs/heads/V2.3-stable"/>
<project name="chromiumos/third_party/ntirpc" path="src/third_party/ntirpc" revision="a9fc54d636fc3e5b5f0918769a2e5343c5f0d823" upstream="refs/heads/V1.3.3-cros"/>
<project name="chromiumos/third_party/portage_tool" path="src/third_party/portage_tool" revision="329c5bc7b2f6fda2f491c66d043dd71c7d6b1796" upstream="refs/heads/chromeos-2.2.28"/>
<project groups="minilayout,firmware,buildtools" name="chromiumos/third_party/pyelftools" path="chromite/third_party/pyelftools" revision="af64f6c7b19cdb84226161dd3742a13fd7974cc3" upstream="refs/heads/master-0.22"/>
<project name="chromiumos/third_party/realtek-updater" path="src/third_party/realtek-updater" revision="7e603e12fbf9d2a8aeb67f1075fe43dbfaf52f7f" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/rootdev" path="src/third_party/rootdev" revision="8dc336a991e5494e6cc9a0094778fee67f22ed6c" upstream="refs/heads/master"/>
<project groups="firmware" name="chromiumos/third_party/seabios" path="src/third_party/seabios" revision="3004147dd3707e600772ec6c5d37beac7f4b8eb4" upstream="refs/heads/chromeos-2014.11.03"/>
<project name="chromiumos/third_party/sis-updater" path="src/third_party/sis-updater" revision="66abe03278f294247471311b7ea4c57b977bf12b" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/sound-open-firmware" path="src/third_party/sound-open-firmware" revision="b3a8ce9a2a63ca4f8dec7500347c711055251f7b" upstream="refs/heads/master"/>
<project groups="firmware" name="chromiumos/third_party/sysbios" path="src/third_party/sysbios" revision="33e1db34b8162de72a5e9bbbc44e6bce38978396" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/tlsdate" path="src/third_party/tlsdate" revision="7c67bde6c3e9b505975b2933a259db8c3b661a47" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/toolchain-utils" path="src/third_party/toolchain-utils" revision="b54e42c61263fd299a3ca458c13936ad6b987506" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/tpm-emulator" path="src/third_party/tpm-emulator" revision="310a21ef24ace14b4d6e8095172445494f54ff25" upstream="refs/heads/master"/>
<project groups="firmware" name="chromiumos/third_party/tpm2" path="src/third_party/tpm2" revision="f6a820be22639509e49c3184d724cada892e6245" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/trousers" path="src/third_party/trousers" revision="6c2cac92b71c2c96e020a10c4f01afdf311bf8e4" upstream="refs/heads/master-0.3.13"/>
<project name="chromiumos/third_party/u-boot" path="src/third_party/u-boot/files" revision="1e26ac220258662e911d2471a090c9219566fffe" upstream="refs/heads/chromeos-v2017.05"/>
<project name="chromiumos/third_party/webrtc-apm" path="src/third_party/webrtc-apm" revision="edc7e2a9977370ba0ff487cf1367fbdc1bc8d9e9" upstream="refs/heads/master"/>
<project name="chromiumos/third_party/whining" path="src/third_party/whining" revision="c325abd3eff318af433a1a5667f5d2745f893945" upstream="refs/heads/master"/>
<project name="external/git.kernel.org/fs/xfs/xfstests-dev" path="src/third_party/xfstests" revision="84cbe4d0dddb6745d7bcbc98b1a48ba2d6e9cc37" upstream="refs/heads/master"/>
<project groups="minilayout,firmware,buildtools,chromeos-admin" name="infra/luci/client-py" path="chromite/third_party/swarming.client" remote="chromium" revision="281c390193ec8c02e60279f8dac1b86ac52fa4be"/>
<project name="linux-syscall-support" path="src/third_party/breakpad/src/third_party/lss" revision="a89bf7903f3169e6bc7b8efc10a73a7571de21cf"/>
<project name="platform/external/bsdiff" path="src/aosp/external/bsdiff" remote="aosp" revision="c35a3dd7996924b9925880f988993faec3449e26" upstream="refs/heads/master"/>
<project name="platform/external/libcxx" path="src/aosp/external/libcxx" remote="aosp" revision="e2284c4c44cc25133a45bfc8b0a0dc6182da0ce9" upstream="refs/heads/master"/>
<project name="platform/external/libcxxabi" path="src/aosp/external/libcxxabi" remote="aosp" revision="410f4950ad5b32cd4fa1948838b02eddf5b1dcc2" upstream="refs/heads/master"/>
<project name="platform/external/libmojo" path="src/aosp/external/libmojo" remote="aosp" revision="920588a1acdc4721abb713d8162010e4b85ae53e" upstream="refs/heads/master"/>
<project name="platform/external/libunwind_llvm" path="src/aosp/external/libunwind_llvm" remote="aosp" revision="6136ec05d911d4a306778dbee9b3a49c47e421d9" upstream="refs/heads/master"/>
<project name="platform/external/minijail" path="src/aosp/external/minijail" remote="aosp" revision="677900fb3a5fcde716e0a07e15365acc46d7356f" upstream="refs/heads/master"/>
<project name="platform/external/puffin" path="src/aosp/external/puffin" remote="aosp" revision="e117046df35aa9de5c7dc7215951418ce935c764" upstream="refs/heads/master"/>
<project name="toolchain/binutils" path="src/aosp/toolchain/binutils" remote="aosp" revision="cce69c1b1bfc46de5e1cdd4923f87215c0edb884"/>
<project name="toolchain/gcc" path="src/aosp/toolchain/gcc" remote="aosp" revision="ac6128e0a17a52f011797f33ac3e7d6273a9368d"/>
<project name="weave/libweave" path="src/weave/libweave" revision="b603f0f3db52cac5feccdf032466f711369f1f37" upstream="refs/heads/master"/>
<repo-hooks enabled-list="pre-upload" in-project="chromiumos/repohooks"/>
<pending_commit branch="chromeos-3.18" change_id="I8fd737a7a5cd05c059b00103b4b6a794a1035b66" commit="4b734bcaadc5830b2655d37aa09986b46b5b87f4" commit_message="BACKPORT: arm64: kernel: Add support for Privileged Access Never 'Privileged Access Never' is a new arm8.1 feature which prevents privileged code from accessing any virtual address where read or write access is also permitted at EL0. This patch enables the PAN feature on all CPUs, and modifies {get,put}_user helpers temporarily to permit access. This will catch kernel bugs where user memory is accessed directly. 'Unprivileged loads and stores' using ldtrb et al are unaffected by PAN. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I8fd737a7a5cd05c059b00103b4b6a794a1035b66 Reviewed-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; Signed-off-by: James Morse &lt;james.morse@arm.com&gt; [will: use ALTERNATIVE in asm and tidy up pan_enable check] Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt; (cherry picked from commit 338d4f49d6f7114a017d294ccf7374df4f998edc) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; [SR: 3.18: conflicts with 13cc7edb2c7 and 185692ffcc16 arm64: compat: fix stxr failure case in SWP emulation BACKPORT: arm64/uaccess: Enable hardened usercopy] Conflicts: arch/arm64/kernel/armv8_deprecated.c arch/arm64/lib/copy_from_user.S arch/arm64/lib/copy_to_user.S Reviewed-on: https://chromium-review.googlesource.com/1245182 " fail_count="0" gerrit_number="1245182" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/82/1245182/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ie29712c77819a9b249c0145a7c61dd75eaf3e38e" commit="3af4dee7037ec2dd6bb227b0ab6b34da73736776" commit_message="UPSTREAM: arm64: armv8_deprecated: ensure extension of addr commit 55de49f9aa17b0b2b144dd2af587177b9aadf429 upstream. Our compat swp emulation holds the compat user address in an unsigned int, which it passes to __user_swpX_asm(). When a 32-bit value is passed in a register, the upper 32 bits of the register are unknown, and we must extend the value to 64 bits before we can use it as a base address. This patch casts the address to unsigned long to ensure it has been suitably extended, avoiding the potential issue, and silencing a related warning from clang. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Ie29712c77819a9b249c0145a7c61dd75eaf3e38e Fixes: bd35a4adc413 (&quot;arm64: Port SWP/SWPB emulation support from arm&quot;) Cc: &lt;stable@vger.kernel.org&gt; # 3.19.x- Acked-by: Will Deacon &lt;will.deacon@arm.com&gt; Signed-off-by: Mark Rutland &lt;mark.rutland@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt; (cherry picked from commit 01ce16f40c9767c2465fc86b1b54ad11192c6d10) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245183 " fail_count="0" gerrit_number="1245183" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/83/1245183/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I43ad7e6a6674668708bcc7f40b34117216154274" commit="6e6deacb69947ba058e383c9cfbdfec253c9bef7" commit_message="UPSTREAM: arm64: elf: advertise 8.1 atomic instructions as new hwcap The ARM v8.1 architecture introduces new atomic instructions to the A64 instruction set for things like cmpxchg, so advertise their availability to userspace using a hwcap. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I43ad7e6a6674668708bcc7f40b34117216154274 Reviewed-by: Steve Capper &lt;steve.capper@arm.com&gt; Reviewed-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt; (cherry picked from commit 40a1db2434a1b62332b1af25cfa14d7b8c0301fe) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245184 " fail_count="0" gerrit_number="1245184" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/84/1245184/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ibf5a4a46f2a5a406fc9af63dad193b285549fc24" commit="70cb717566020cbfe1fc77c8b2c36224390e94e6" commit_message="UPSTREAM: arm64: lse: use generic cpufeature detection for LSE atomics Rework the cpufeature detection to support ISAR0 and use that for detecting the presence of LSE atomics. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Ibf5a4a46f2a5a406fc9af63dad193b285549fc24 Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt; (cherry picked from commit 2e94da13790336eb3fd00fb5e97610dd9aebe213) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245185 " fail_count="0" gerrit_number="1245185" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/85/1245185/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I8463f4b22fbb4d221e7c841280c68308fae40a68" commit="f5e6ff6fcebd75112d27c6707b52ff6069b84e29" commit_message="UPSTREAM: arm64: alternatives: add cpu feature for lse atomics Add a CPU feature for the LSE atomic instructions, so that they can be patched in at runtime when we detect that they are supported. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I8463f4b22fbb4d221e7c841280c68308fae40a68 Reviewed-by: Steve Capper &lt;steve.capper@arm.com&gt; Reviewed-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt; (cherry picked from commit d964b7229e7f94428a1e8d26999adffbe8a69db2) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245186 " fail_count="0" gerrit_number="1245186" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/86/1245186/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I9e1eb29d54a247814b77a18b58e283601377ecef" commit="2f74a77f67cae4eca829b714dbc33e1b8a5d0ea4" commit_message="BACKPORT: arm64: elf: use cpuid_feature_extract_field for hwcap detection cpuid_feature_extract_field takes care of the fiddly ID register field sign-extension, so use that instead of rolling our own version. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I9e1eb29d54a247814b77a18b58e283601377ecef Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt; (cherry picked from commit 309585b0b931b291d0525b2830161ee76a2f23ff) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; [SR: 3.18: context conflict from not having a591ede4cd1] Conflicts: arch/arm64/kernel/setup.c Reviewed-on: https://chromium-review.googlesource.com/1245187 " fail_count="0" gerrit_number="1245187" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/87/1245187/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ie62ae7c48e5ba41c34fa0c042ce3791e1a3a00ca" commit="486433a4a50829dc9bd5ab49d35b6efaf0231bbe" commit_message="BACKPORT: arm64: apply alternatives for !SMP kernels Currently we only perform alternative patching for kernels built with CONFIG_SMP, as we call apply_alternatives_all() in smp.c, which is only built for CONFIG_SMP. Thus !SMP kernels may not have necessary alternatives patched in. This patch ensures that we call apply_alternatives_all() once all CPUs are booted, even for !SMP kernels, by having the smp_init_cpus() stub call this for !SMP kernels via up_late_init. A new wrapper, do_post_cpus_up_work, is added so we can hook other calls here later (e.g. boot mode logging). BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Ie62ae7c48e5ba41c34fa0c042ce3791e1a3a00ca Cc: Andre Przywara &lt;andre.przywara@arm.com&gt; Cc: Catalin Marinas &lt;catalin.marinas@arm.com&gt; Fixes: e039ee4ee3fcf174 (&quot;arm64: add alternative runtime patching&quot;) Tested-by: Ard Biesheuvel &lt;ard.biesheuvel@linaro.org&gt; Reviewed-by: Ard Biesheuvel &lt;ard.biesheuvel@linaro.org&gt; Signed-off-by: Mark Rutland &lt;mark.rutland@arm.com&gt; Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt; (cherry picked from commit 137650aad96c9594683445e41afa8ac5a2097520) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; [SR: 3.18: context conflict] Conflicts: arch/arm64/Kconfig Reviewed-on: https://chromium-review.googlesource.com/1245188 " fail_count="0" gerrit_number="1245188" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/88/1245188/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ia267dac864f51ff045184e0a5452274c10cbc172" commit="e924307a7cadeba9e64643468f71624b97e47252" commit_message="UPSTREAM: arm64: log CPU boot modes We currently don't log the boot mode for arm64 as we do for arm, and without KVM the user is provided with no indication as to which mode(s) CPUs were booted in, which can seriously hinder debugging in some cases. Add logging to the boot path once all CPUs are up. Where CPUs are mismatched in violation of the boot protocol, WARN and set a taint (as we do for CPU other CPU feature mismatches) given that the firmware/bootloader is buggy and should be fixed. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Ia267dac864f51ff045184e0a5452274c10cbc172 Cc: Catalin Marinas &lt;catalin.marinas@arm.com&gt; Cc: Marc Zyngier &lt;marc.zyngier@arm.com&gt; Tested-by: Ard Biesheuvel &lt;ard.biesheuvel@linaro.org&gt; Reviewed-by: Ard Biesheuvel &lt;ard.biesheuvel@linaro.org&gt; Signed-off-by: Mark Rutland &lt;mark.rutland@arm.com&gt; Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt; (cherry picked from commit 667f3fd3950c123fd62d3b15d9db80926e75f1f0) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245189 " fail_count="0" gerrit_number="1245189" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/89/1245189/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I848ae7f496c3edb8ee80fa4d3f31d88891f4950d" commit="3b421be63044dbe5438395fe053bbc2a66839388" commit_message="BACKPORT: arm64: remove dead-code depending on CONFIG_UP_LATE_INIT Commit 4b3dc9679cf7 (&quot;arm64: force CONFIG_SMP=y and remove redundant and therfore can not be selected anymore. Remove dead #ifdef-block depending on UP_LATE_INIT in arch/arm64/kernel/setup.c BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I848ae7f496c3edb8ee80fa4d3f31d88891f4950d Signed-off-by: Jonas Rabenstein &lt;jonas.rabenstein@studium.uni-erlangen.de&gt; [will: kill do_post_cpus_up_work altogether] Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt; (cherry picked from commit 377bcff9a38a78083d7fff8e8a41cc894cf7813b) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; [SR: 3.18: context around the header includes] Conflicts: arch/arm64/kernel/setup.c Reviewed-on: https://chromium-review.googlesource.com/1245190 " fail_count="0" gerrit_number="1245190" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/90/1245190/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I7915e28032468f3d08f5ac83a4163ca211a10bfe" commit="026ca8c31f92a048c797c8019862a21d549b75b2" commit_message="BACKPORT: arm64: Delay ELF HWCAP initialisation until all CPUs are up Delay the ELF HWCAP initialisation until all the (enabled) CPUs are up, i.e, smp_cpus_done(). This is in preparation for detecting the common features across the CPUS and creating a consistent ELF HWCAP for the system. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I7915e28032468f3d08f5ac83a4163ca211a10bfe Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit 3a75578efae64b94d76eacbf8adf2a3ab13c6aa1) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; [SR: 3.18: context from not having 64f17818977d0 arm64: Make the CPU information more clear, - remove unused local cpu_info - remove unused global cpu_name] Conflicts: arch/arm64/kernel/setup.c Reviewed-on: https://chromium-review.googlesource.com/1245191 " fail_count="0" gerrit_number="1245191" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/91/1245191/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I6c5cf8a7f568ddf55e9af6409699f23ceb9a1177" commit="e17eec9f08c9455c30542f64658d4190a406cafb" commit_message="BACKPORT: arm64: Delay cpuinfo_store_boot_cpu At the moment the boot CPU stores the cpuinfo long before the PERCPU areas are initialised by the kernel. This could be problematic as the non-boot CPU data structures might get copied with the data from the boot CPU, giving us no chance to detect if a particular CPU updated its cpuinfo. This patch delays the boot cpu store to smp_prepare_boot_cpu(). Also kills the setup_processor() which no longer does meaningful work. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I6c5cf8a7f568ddf55e9af6409699f23ceb9a1177 Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit 4b998ff1885eecd3dc330bf057e24667c1db84a4) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; [SR: 3.18: context from not having 61bd93ce801] Conflicts: arch/arm64/kernel/setup.c Reviewed-on: https://chromium-review.googlesource.com/1245192 " fail_count="0" gerrit_number="1245192" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/92/1245192/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Iac6d59974dc5db930e3e10a474723262ee7e81c3" commit="ff7b6b48c841296801b5368673f0f7f3bb10d625" commit_message="UPSTREAM: arm64: Add COMPAT_HWCAP_LPAE Commit a469abd0f868 (ARM: elf: add new hwcap for identifying atomic ldrd/strd instructions) introduces HWCAP_ELF for 32-bit ARM applications. As LPAE is always present on arm64, report the corresponding compat HWCAP to user space. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Iac6d59974dc5db930e3e10a474723262ee7e81c3 Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; Cc: &lt;stable@vger.kernel.org&gt; # 3.11+ Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt; (cherry picked from commit 7d57511d2dba03a8046c8b428dd9192a4bfc1e73) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245193 " fail_count="0" gerrit_number="1245193" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/93/1245193/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Id36d7849b15122d25328aa8750d6c3861ff13a5e" commit="5f31c77ea8037e1217ae60d8c5b540fdc8d97d0c" commit_message="BACKPORT: arm64: Move cpu feature detection code This patch moves the CPU feature detection code from arch/arm64/kernel/{setup.c to cpufeature.c} The plan is to consolidate all the CPU feature handling in cpufeature.c. Apart from changing pr_fmt from &quot;alternatives&quot; to &quot;cpu features&quot;, there are no functional changes. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Id36d7849b15122d25328aa8750d6c3861ff13a5e Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit 9cdf8ec4a86b9310111f741bbaf11df9120e0482) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; [SR: 3.18: context from not having 61bd93ce801bb6 arm64: use fixmap region for permanent FDT] Conflicts: arch/arm64/kernel/setup.c Reviewed-on: https://chromium-review.googlesource.com/1245194 " fail_count="0" gerrit_number="1245194" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/94/1245194/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ice8af1348c072e2f3d3cd7e8166f9d20e290de9e" commit="3b6b0a58072899b98120c684a645f0577c94f667" commit_message="BACKPORT: arm64: Move mixed endian support detection Move the mixed endian support detection code to cpufeature.c from cpuinfo.c. This also moves the update_cpu_features() used by mixed endian detection code, which will get more functionality. Also moves the ID register field shifts to asm/sysreg.h, where all the useful definitions will end up in later patches. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Ice8af1348c072e2f3d3cd7e8166f9d20e290de9e Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit cdcf817b7e4b62b935d8797f7d07ea0b97760884) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; [SR: 3.18: sysreg.h: pull in #defines from 4bf8b96ed3f7 and 44eaacf1b899 cpuinfo.c: context conflict with 7d3b7d67806] Conflicts: arch/arm64/include/asm/sysreg.h arch/arm64/kernel/cpuinfo.c Reviewed-on: https://chromium-review.googlesource.com/1245195 " fail_count="0" gerrit_number="1245195" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/95/1245195/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I6a7d1d7c2d1725d7d0d63adc1e6cf9d1c31e5eeb" commit="577e3cbea96a2ff6cf2cfda5f8427314f2c1ae0a" commit_message="UPSTREAM: arm64: cpufeature.h: add missing #include of kernel.h cpufeature.h makes use of DECLARE_BITMAP, which in turn relies on the BITS_TO_LONGS and DIV_ROUND_UP macros. This patch includes kernel.h in cpufeature.h to prevent all users having to do the same thing. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I6a7d1d7c2d1725d7d0d63adc1e6cf9d1c31e5eeb Acked-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt; (cherry picked from commit 144e9697a9e70b5549fd52df90111f1410bcbfeb) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245196 " fail_count="0" gerrit_number="1245196" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/96/1245196/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ide33fa8b16a9ccce0c573ef817c85da4b090ab3c" commit="5ff9b560c24da65969d979ab1f38ccee95cad3b8" commit_message="UPSTREAM: arm64: Handle width of a cpuid feature Introduce a helper to extract cpuid feature for any given width. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Ide33fa8b16a9ccce0c573ef817c85da4b090ab3c Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit ce98a677d897dbaac86905652292fab1eeeb2b93) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245197 " fail_count="0" gerrit_number="1245197" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/97/1245197/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ica0a211b94703e113997feeb684ba8fa59c12953" commit="920f5e8e8809c38bda42b4cf25e1f7dde6430ee8" commit_message="UPSTREAM: arm64: Keep track of CPU feature registers This patch adds an infrastructure to keep track of the CPU feature registers on the system. For each register, the infrastructure keeps track of the system wide safe value of the feature bits. Also, tracks the which fields of a register should be matched strictly across all the CPUs on the system for the SANITY check infrastructure. The feature bits are classified into following 3 types depending on the implication of the possible values. This information is used to decide the safe value for a feature. LOWER_SAFE - The smaller value is safer HIGHER_SAFE - The bigger value is safer EXACT - We can't decide between the two, so a predefined safe_value is used. This infrastructure will be later used to make better decisions for: - Kernel features (e.g, KVM, Debug) - SANITY Check - CPU capability - ELF HWCAP - Exposing CPU Feature register to userspace. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Ica0a211b94703e113997feeb684ba8fa59c12953 Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; [catalin.marinas@arm.com: whitespace fix] Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit 3c739b57108436211c7f798ba3de0bb0cd8ef469) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245198 " fail_count="0" gerrit_number="1245198" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/98/1245198/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I266cc87c0624abfcb7b2b116a0fbf35d4046dbd3" commit="8552a9100a9ef5397bb5dac2d225f4a17bb64252" commit_message="UPSTREAM: arm64: Do not attempt to use init_mm in reset_context() After secondary CPU boot or hotplug, the active_mm of the idle thread is &amp;init_mm. The init_mm.pgd (swapper_pg_dir) is only meant for TTBR1_EL1 and must not be set in TTBR0_EL1. Since when active_mm == &amp;init_mm the TTBR0_EL1 is already set to the reserved value, there is no need to perform any context reset. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I266cc87c0624abfcb7b2b116a0fbf35d4046dbd3 Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; Cc: &lt;stable@vger.kernel.org&gt; (cherry picked from commit 565630d503ef24e44c252bed55571b3a0d68455f) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245199 " fail_count="0" gerrit_number="1245199" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/99/1245199/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I4c7e9c361f0b31ac7978eba1dadfbcbeaeb69dbc" commit="d13022f64e67fb491c16e736f667c4bbc5c453a7" commit_message="UPSTREAM: arm64: cpufeature: Add helpers for extracting unsigned values The cpuid_feature_extract_field() extracts the feature value as a signed integer. This could be problematic for features whose values are unsigned. e.g, ID_AA64DFR0_EL1:BRPs. Add an unsigned variant for the unsigned fields. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I4c7e9c361f0b31ac7978eba1dadfbcbeaeb69dbc Cc: Ard Biesheuvel &lt;ard.biesheuvel@linaro.org&gt; Reported-by: AKASHI Takahiro &lt;takahiro.akashi@linaro.org&gt; Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit d21182718400f51f0729ae8268d94bd820ec8b71) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245200 " fail_count="0" gerrit_number="1245200" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/00/1245200/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ifab1f920c4480057234f3dbb8a372cc64cb8eeb1" commit="1091a1206a84487657066c284bcdc9c6db764092" commit_message="UPSTREAM: arm64: Consolidate CPU Sanity check to CPU Feature infrastructure This patch consolidates the CPU Sanity check to the new infrastructure. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Ifab1f920c4480057234f3dbb8a372cc64cb8eeb1 Cc: Mark Rutland &lt;mark.rutland@arm.com&gt; Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit 3086d391f992984def0aa6aa4a36f54853c58536) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245201 " fail_count="0" gerrit_number="1245201" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/01/1245201/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I3e7d41354dfa4fa3b0a1a0f83e7e1819d5112986" commit="c6b026f3120b89ec45be7a6eec4f37d588617447" commit_message="UPSTREAM: arm64: Read system wide CPUID value Add an API for reading the safe CPUID value across the system from the new infrastructure. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I3e7d41354dfa4fa3b0a1a0f83e7e1819d5112986 Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit b3f1537893b54d0f42f52e0f4cde5e17e21f564c) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245202 " fail_count="0" gerrit_number="1245202" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/02/1245202/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I9941eafedf65b675e97fdd35ffe989aa48f17677" commit="d1665c7b1e813ecd747772e80d6fab5c8c2dc145" commit_message="BACKPORT: arm64: Cleanup mixed endian support detection Make use of the system wide safe register to decide the support for mixed endian. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I9941eafedf65b675e97fdd35ffe989aa48f17677 Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit c1e8656cbae139c8aaf34d7b802edecbc8a1cf58) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; [SR: 3.18: context manually removed old prototypes] Conflict: arch/arm64/include/asm/cpufeature.h Reviewed-on: https://chromium-review.googlesource.com/1245203 " fail_count="0" gerrit_number="1245203" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/03/1245203/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ica6d9519cce1eeace62ba662aac249e76c47a2a4" commit="4b7f913df7d67bc674a0bac558941ab19746bb3a" commit_message="UPSTREAM: arm64: Refactor check_cpu_capabilities check_cpu_capabilities runs through a given list of caps and checks if the system has the cap, updates the system capability bitmap and also runs any enable() methods associated with them. All of this is not quite obvious from the name 'check'. This patch splits the check_cpu_capabilities into two parts : 1) update_cpu_capabilities =&gt; Runs through the given list and updates the system wide capability map. 2) enable_cpu_capabilities =&gt; Runs through the given list and invokes enable() (if any) for the caps enabled on the system. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Ica6d9519cce1eeace62ba662aac249e76c47a2a4 Cc: Andre Przywara &lt;andre.przywara@arm.com&gt; Cc: Will Deacon &lt;will.deacon@arm.com&gt; Suggested-by: Catalin Marinas &lt;catalin.marinsa@arm.com&gt; Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit ce8b602c694c9482e0ffb7432cd59fa2276673fe) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245204 " fail_count="0" gerrit_number="1245204" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/04/1245204/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I63ca9d31decaa2a1a14b7058bc46eb53e76c28a3" commit="8e6badc5ba19a7c86e2dcee05ebd7ca2fa85a648" commit_message="UPSTREAM: arm64: Delay cpu feature capability checks At the moment we run through the arm64_features capability list for each CPU and set the capability if one of the CPU supports it. This could be problematic in a heterogeneous system with differing capabilities. Delay the CPU feature checks until all the enabled CPUs are up(i.e, smp_cpus_done(), so that we can make better decisions based on the overall system capability. Once we decide and advertise the capabilities the alternatives can be applied. From this state, we cannot roll back a feature to disabled based on the values from a new hotplugged CPU, due to the runtime patching and other reasons. So, for all new CPUs, we need to make sure that they have the established system capabilities. Failing which, we bring the CPU down, preventing it from turning online. Once the capabilities are decided, any new CPU booting up goes through verification to ensure that it has all the enabled capabilities and also invokes the respective enable() method on the CPU. The CPU errata checks are not delayed and is still executed per-CPU to detect the respective capabilities. If we ever come across a non-errata capability that needs to be checked on each-CPU, we could introduce them via a new capability table(or introduce a flag), which can be processed per CPU. The next patch will make the feature checks use the system wide safe value of a feature register. NOTE: The enable() methods associated with the capability is scheduled on all the CPUs (which is the only use case at the moment). If we need a different type of 'enable()' which only needs to be run once on any CPU, we should be able to handle that when needed. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I63ca9d31decaa2a1a14b7058bc46eb53e76c28a3 Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; [catalin.marinas@arm.com: static variable and coding style fixes] Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit dbb4e152b8da1f977d9d8cd7e494ab4ee3622f72) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245205 " fail_count="0" gerrit_number="1245205" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/05/1245205/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I58099af8a93f7120a9f952034fd5b0e2ac36e8b7" commit="ff59c8aef40322369e0a5ca7ac037dab99baacdb" commit_message="UPSTREAM: arm64/capabilities: Make use of system wide safe value Now that we can reliably read the system wide safe value for a feature register, use that to compute the system capability. This patch also replaces the 'feature-register-specific' methods with a generic routine to check the capability. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I58099af8a93f7120a9f952034fd5b0e2ac36e8b7 Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit da8d02d19ffdd201af632c755a473b6df4b3e4cc) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245206 " fail_count="0" gerrit_number="1245206" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/06/1245206/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I2cab414e1532f4649e21424e8bb7f27363cf8e40" commit="071d6d32e2548b3468cd472a15c242964f32d421" commit_message="UPSTREAM: arm64/HWCAP: Use system wide safe values Extend struct arm64_cpu_capabilities to handle the HWCAP detection and make use of the system wide value of the feature registers for a reliable set of HWCAPs. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I2cab414e1532f4649e21424e8bb7f27363cf8e40 Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit 37b01d53ceefa390d6eee7a82f3c156b64951bf3) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245207 " fail_count="0" gerrit_number="1245207" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/07/1245207/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ie720b0363b0a03d055dee551363aef62d4b81b95" commit="213935dce47cf528f8744370c1ec86724daeb9cf" commit_message="UPSTREAM: arm64: Move FP/ASIMD hwcap handling to common code The FP/ASIMD is detected in fpsimd_init(), which is built-in unconditionally. Lets move the hwcap handling to the central place. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Ie720b0363b0a03d055dee551363aef62d4b81b95 Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit fe80f9f2da1006a4308c2bc018ee1d67f10dd8d0) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245208 " fail_count="0" gerrit_number="1245208" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/08/1245208/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I96d2cf811db68299e55954f868a682637e722a4b" commit="28f85ecc9acfa7254e912eaa0cc389d6f39cebe9" commit_message="UPSTREAM: arm64: cpufeature: declare enable_cpu_capabilities as static enable_cpu_capabilities is only called from within cpufeature.c, so it can be declared static. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I96d2cf811db68299e55954f868a682637e722a4b Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit fde4a59fc1c55709b96d0f07110895f20015b6cc) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245209 " fail_count="0" gerrit_number="1245209" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/09/1245209/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I40b86a010b33784b8c94e82802262de5998aa897" commit="5914a631237c62f7341f22de7dc6e51686ab1669" commit_message="UPSTREAM: arm64: mark cpus_have_hwcap as __maybe_unused cpus_have_hwcap() is defined as a 'static' function an only used in one place that is inside of an #ifdef, so we get a warning when the only user is disabled: arch/arm64/kernel/cpufeature.c:699:13: warning: 'cpus_have_hwcap' defined but not used [-Wunused-function] This marks the function as __maybe_unused, so the compiler knows that it can drop the function definition without warning about it. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I40b86a010b33784b8c94e82802262de5998aa897 Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt; Fixes: 37b01d53ceef (&quot;arm64/HWCAP: Use system wide safe values&quot;) Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit 3d6d103538e73a5710ea66d95fa2b652bf6eab77) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245210 " fail_count="0" gerrit_number="1245210" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/10/1245210/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I72b657aaf7186f37d4f6f2f143cc75eb4016f611" commit="ab8fbb868e7e892b5a0c411c2dd22189dc764f2a" commit_message="UPSTREAM: arm64: cpufeature: Track unsigned fields Some of the feature bits have unsigned values and need to be treated accordingly to avoid errors. Adds the property to the feature bits and use the appropriate field extract helpers. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I72b657aaf7186f37d4f6f2f143cc75eb4016f611 Reported-by: AKASHI Takahiro &lt;takahiro.akashi@linaro.org&gt; Cc: Ard Biesheuvel &lt;ard.biesheuvel@linaro.org&gt; Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit 4f0a606bce5ecd3a8210e896c33f41d1bf7f752f) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245211 " fail_count="0" gerrit_number="1245211" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/11/1245211/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I9fe2cf7f523ac6e7b4f4c9ac5613133293170b31" commit="45576e627b85d92f2336b9e60f719cd2024e6080" commit_message="UPSTREAM: arm64: cpufeature: Schedule enable() calls instead of calling them via IPI commit 2a6dcb2b5f3e21592ca8dfa198dcce7bec09b020 upstream. The enable() call for a cpufeature/errata is called using on_each_cpu(). This issues a cross-call IPI to get the work done. Implicitly, this stashes the running PSTATE in SPSR when the CPU receives the IPI, and restores it when we return. This means an enable() call can never modify PSTATE. To allow PAN to do this, change the on_each_cpu() call to use stop_machine(). This schedules the work on each CPU which allows us to modify PSTATE. This involves changing the protype of all the enable() functions. enable_cpu_capabilities() is called during boot and enables the feature on all online CPUs. This path now uses stop_machine(). CPU features for hotplug'd CPUs are enabled by verify_local_cpu_features() which only acts on the local CPU, and can already modify the running PSTATE as it is called from secondary_start_kernel(). BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I9fe2cf7f523ac6e7b4f4c9ac5613133293170b31 Reported-by: Tony Thompson &lt;anthony.thompson@arm.com&gt; Reported-by: Vladimir Murzin &lt;vladimir.murzin@arm.com&gt; Signed-off-by: James Morse &lt;james.morse@arm.com&gt; Cc: Suzuki K Poulose &lt;suzuki.poulose@arm.com&gt; Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt; [Removed enable() hunks for features/errata v4.4. doesn't have. Changed caps-&gt;enable arg in enable_cpu_capabilities()] Signed-off-by: James Morse &lt;james.morse@arm.com&gt; Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt; (cherry picked from commit da643dc17f20e04c089c93a3fe7d89e5be80d1af) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245212 " fail_count="0" gerrit_number="1245212" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/12/1245212/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I925aeb92ce492e4d4fb2438eb2cfd9598314a957" commit="6f76b45e562842986b790e45d453b65d9440edfb" commit_message="UPSTREAM: arch: Add lightweight memory barriers dma_rmb() and dma_wmb() There are a number of situations where the mandatory barriers rmb() and wmb() are used to order memory/memory operations in the device drivers and those barriers are much heavier than they actually need to be. For example in the case of PowerPC wmb() calls the heavy-weight sync instruction when for coherent memory operations all that is really needed is an lsync or eieio instruction. This commit adds a coherent only version of the mandatory memory barriers rmb() and wmb(). In most cases this should result in the barrier being the same as the SMP barriers for the SMP case, however in some cases we use a barrier that is somewhere in between rmb() and smp_rmb(). For example on ARM the rmb barriers break down as follows: Barrier Call Explanation --------- -------- ---------------------------------- rmb() dsb() Data synchronization barrier - system dma_rmb() dmb(osh) data memory barrier - outer sharable smp_rmb() dmb(ish) data memory barrier - inner sharable These new barriers are not as safe as the standard rmb() and wmb(). Specifically they do not guarantee ordering between coherent and incoherent memories. The primary use case for these would be to enforce ordering of reads and writes when accessing coherent memory that is shared between the CPU and a device. It may also be noted that there is no dma_mb(). Most architectures don't provide a good mechanism for performing a coherent only full barrier without resorting to the same mechanism used in mb(). As such there isn't much to be gained in trying to define such a function. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I925aeb92ce492e4d4fb2438eb2cfd9598314a957 Cc: Frederic Weisbecker &lt;fweisbec@gmail.com&gt; Cc: Mathieu Desnoyers &lt;mathieu.desnoyers@polymtl.ca&gt; Cc: Michael Ellerman &lt;michael@ellerman.id.au&gt; Cc: Michael Neuling &lt;mikey@neuling.org&gt; Cc: Russell King &lt;linux@arm.linux.org.uk&gt; Cc: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt; Cc: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt; Cc: Linus Torvalds &lt;torvalds@linux-foundation.org&gt; Cc: Martin Schwidefsky &lt;schwidefsky@de.ibm.com&gt; Cc: Tony Luck &lt;tony.luck@intel.com&gt; Cc: Oleg Nesterov &lt;oleg@redhat.com&gt; Cc: &quot;Paul E. McKenney&quot; &lt;paulmck@linux.vnet.ibm.com&gt; Cc: Peter Zijlstra &lt;peterz@infradead.org&gt; Cc: Ingo Molnar &lt;mingo@kernel.org&gt; Cc: David Miller &lt;davem@davemloft.net&gt; Acked-by: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt; Acked-by: Will Deacon &lt;will.deacon@arm.com&gt; Signed-off-by: Alexander Duyck &lt;alexander.h.duyck@redhat.com&gt; Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt; (cherry picked from commit 1077fa36f23e259858caf6f269a47393a5aff523) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245213 " fail_count="0" gerrit_number="1245213" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/13/1245213/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I2e092ecf64cc45c91e9cd0ee95611817efca3039" commit="ead97da9e5cda41a76176e1f42e0131393b670a3" commit_message="UPSTREAM: arm64: drop sleep_idmap_phys and clean up cpu_resume() Two cleanups of the asm function cpu_resume(): - The global variable sleep_idmap_phys always points to idmap_pg_dir, so we can just use that value directly in the CPU resume path. - Unclutter the load of sleep_save_sp::save_ptr_stash_phys. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I2e092ecf64cc45c91e9cd0ee95611817efca3039 Acked-by: Lorenzo Pieralisi &lt;lorenzo.pieralisi@arm.com&gt; Tested-by: Lorenzo Pieralisi &lt;lorenzo.pieralisi@arm.com&gt; Signed-off-by: Ard Biesheuvel &lt;ard.biesheuvel@linaro.org&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit 9acdc2af0c0b836183b7f31f630bbed341a7cf4d) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245214 " fail_count="0" gerrit_number="1245214" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/14/1245214/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ie7c592943836639bbba8b3a77262df97cd67aed4" commit="50a3d26d89fab4cfa4a3889506a303c1388acc96" commit_message="UPSTREAM: arm/arm64: KVM: Fix PSCI affinity info return value for non valid cores If a guest requests the affinity info for a non-existing vCPU we need to properly return an error, instead of erroneously reporting an off state. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Ie7c592943836639bbba8b3a77262df97cd67aed4 Signed-off-by: Alexander Spyridakis &lt;a.spyridakis@virtualopensystems.com&gt; Signed-off-by: Alvise Rigo &lt;a.rigo@virtualopensystems.com&gt; Acked-by: Mark Rutland &lt;mark.rutland@arm.com&gt; Reviewed-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit 0c0672922dcc70ffba11d96385e98e42fb3ae08d) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245215 " fail_count="0" gerrit_number="1245215" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/15/1245215/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I18b1b41420f6abb72e231453099519bd3f417353" commit="4e3206fb4953b741af773a50f1c16d52d7c3b4fc" commit_message="UPSTREAM: KVM: add comments for kvm_debug_exit_arch struct Bring into line with the comments for the other structures and their KVM_EXIT_* cases. Also update api.txt to reflect use in kvm_run documentation. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I18b1b41420f6abb72e231453099519bd3f417353 Signed-off-by: Alex Benne &lt;alex.bennee@linaro.org&gt; Reviewed-by: David Hildenbrand &lt;dahi@linux.vnet.ibm.com&gt; Reviewed-by: Andrew Jones &lt;drjones@redhat.com&gt; Acked-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit 8ab30c1538b14424015e45063c41d509b24c1dea) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245216 " fail_count="0" gerrit_number="1245216" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/16/1245216/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I7ba290de896371cd3aea5fe64c3bd734ff602ec7" commit="d8d7fc6e3ee27cf2b5ec691183f4297b49bd437b" commit_message="UPSTREAM: KVM: arm64: guest debug, define API headers This commit defines the API headers for guest debugging. There are two architecture specific debug structures: - kvm_guest_debug_arch, allows us to pass in HW debug registers - kvm_debug_exit_arch, signals exception and possible faulting address The type of debugging being used is controlled by the architecture specific control bits of the kvm_guest_debug-&gt;control flags in the ioctl structure. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I7ba290de896371cd3aea5fe64c3bd734ff602ec7 Signed-off-by: Alex Benne &lt;alex.bennee@linaro.org&gt; Reviewed-by: David Hildenbrand &lt;dahi@linux.vnet.ibm.com&gt; Reviewed-by: Andrew Jones &lt;drjones@redhat.com&gt; Acked-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit 21b6f32f9471284f6d4621fc8be71719266db557) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245217 " fail_count="0" gerrit_number="1245217" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/17/1245217/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I47ac0a72d56b83324a8d642f24de0a9acb816dc3" commit="63dc2f9daa52a53d4393551996eb70908feb4f8a" commit_message="UPSTREAM: KVM: arm: guest debug, add stub KVM_SET_GUEST_DEBUG ioctl This commit adds a stub function to support the KVM_SET_GUEST_DEBUG ioctl. Any unsupported flag will return -EINVAL. For now, only KVM_GUESTDBG_ENABLE is supported, although it won't have any effects. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I47ac0a72d56b83324a8d642f24de0a9acb816dc3 Signed-off-by: Alex Benne &lt;alex.bennee@linaro.org&gt;. Reviewed-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit 0e6f07f29cfb8d79dbbdb12560a73f7121ba324e) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245218 " fail_count="0" gerrit_number="1245218" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/18/1245218/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Icdd3f82af4ec28cb054185a2e1b55b0e58eccb3b" commit="a79dca68e3d0dc2d99b4dc81d8369a00ccfc2b3d" commit_message="BACKPORT: KVM: arm: introduce kvm_arm_init/setup/clear_debug This is a precursor for later patches which will need to do more to setup debug state before entering the hyp.S switch code. The existing functionality for setting mdcr_el2 has been moved out of hyp.S and now uses the value kept in vcpu-&gt;arch.mdcr_el2. As the assembler used to previously mask and preserve MDCR_EL2.HPMN I've had to add a mechanism to save the value of mdcr_el2 as a per-cpu variable during the initialisation code. The kernel never sets this number so we are assuming the bootcode has set up the correct value here. This also moves the conditional setting of the TDA bit from the hyp code into the C code which is currently used for the lazy debug register context switch code. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Icdd3f82af4ec28cb054185a2e1b55b0e58eccb3b Signed-off-by: Alex Benne &lt;alex.bennee@linaro.org&gt; Reviewed-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit 56c7f5e77f797fd0dcf2376ce1496f4238e6be33) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; [SR: 3.18: conflict from not having 8a14849b4a35 arm64: KVM: Switch vgic save/restore to alternative_insn] Conflicts: arch/arm64/include/asm/kvm_asm.h Reviewed-on: https://chromium-review.googlesource.com/1245219 " fail_count="0" gerrit_number="1245219" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/19/1245219/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I7b5c5da3cd1d8300cda035e1daf1efe68d8a0543" commit="cd9b207802b8ee8cbf97e48a7fb7869e9cdbcf86" commit_message="UPSTREAM: KVM: arm64: guest debug, add SW break point support This adds support for SW breakpoints inserted by userspace. We do this by trapping all guest software debug exceptions to the hypervisor (MDCR_EL2.TDE). The exit handler sets an exit reason of KVM_EXIT_DEBUG with the kvm_debug_exit_arch structure holding the exception syndrome information. It will be up to userspace to extract the PC (via GET_ONE_REG) and determine if the debug event was for a breakpoint it inserted. If not userspace will need to re-inject the correct exception restart the hypervisor to deliver the debug exception to the guest. Any other guest software debug exception (e.g. single step or HW assisted breakpoints) will cause an error and the VM to be killed. This is addressed by later patches which add support for the other debug types. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I7b5c5da3cd1d8300cda035e1daf1efe68d8a0543 Signed-off-by: Alex Benne &lt;alex.bennee@linaro.org&gt; Reviewed-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit 4bd611ca60afa155bca25b40312ed61c4d46237f) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245220 " fail_count="0" gerrit_number="1245220" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/20/1245220/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I8ab1974be7c283847c30d36678f3133a69792b3d" commit="ccce00765df335b0e183bcef579901586ef704a6" commit_message="UPSTREAM: KVM: arm64: guest debug, add support for single-step This adds support for single-stepping the guest. To do this we need to manipulate the guests PSTATE.SS and MDSCR_EL1.SS bits to trigger stepping. We take care to preserve MDSCR_EL1 and trap access to it to ensure we don't affect the apparent state of the guest. As we have to enable trapping of all software debug exceptions we suppress the ability of the guest to single-step itself. If we didn't we would have to deal with the exception arriving while the guest was in kernelspace when the guest is expecting to single-step userspace. This is something we don't want to unwind in the kernel. Once the host is no longer debugging the guest its ability to single-step userspace is restored. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I8ab1974be7c283847c30d36678f3133a69792b3d Signed-off-by: Alex Benne &lt;alex.bennee@linaro.org&gt; Reviewed-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit 337b99bf7edfb2044781447e7ca386edb1fdba9d) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245221 " fail_count="0" gerrit_number="1245221" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/21/1245221/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="If5565cff1d1da6192c2a30f4c3f2c2273da1bb7d" commit="bcbb4196f071a1d6388c1fdd17a5506022dbb67e" commit_message="UPSTREAM: KVM: arm64: re-factor hyp.S debug register code This is a pre-cursor to sharing the code with the guest debug support. This replaces the big macro that fishes data out of a fixed location with a more general helper macro to restore a set of debug registers. It uses macro substitution so it can be re-used for debug control and value registers. It does however rely on the debug registers being 64 bit aligned (as they happen to be in the hyp ABI). BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: If5565cff1d1da6192c2a30f4c3f2c2273da1bb7d Signed-off-by: Alex Benne &lt;alex.bennee@linaro.org&gt; Reviewed-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit e0a1b9a937dc6df9eb402af8966b5d617c7c6b34) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245222 " fail_count="0" gerrit_number="1245222" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/22/1245222/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I6f44b0267d7a2f47a034554bda2066bc316bb90d" commit="1d57d80c20b7ee16833dc5aa6c2efd09d7951e7d" commit_message="UPSTREAM: KVM: arm64: introduce vcpu-&gt;arch.debug_ptr This introduces a level of indirection for the debug registers. Instead of using the sys_regs[] directly we store registers in a structure in the vcpu. The new kvm_arm_reset_debug_ptr() sets the debug ptr to the guest context. Because we no longer give the sys_regs offset for the sys_reg_desc-&gt;reg field, but instead the index into a debug-specific struct we need to add a number of additional trap functions for each register. Also as the generic generic user-space access code no longer works we have introduced a new pair of function pointers to the sys_reg_desc structure to override the generic code when needed. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I6f44b0267d7a2f47a034554bda2066bc316bb90d Reviewed-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Signed-off-by: Alex Benne &lt;alex.bennee@linaro.org&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit 84e690bfbed1d1ecb45d8eccd4c7b6c8e878da1c) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245223 " fail_count="0" gerrit_number="1245223" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/23/1245223/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I00815c6115f02c680a2249f31012cfb2cae30b53" commit="368903e87c462996ec560b3be695ec3f51c56a0f" commit_message="BACKPORT: KVM: arm64: guest debug, HW assisted debug support This adds support for userspace to control the HW debug registers for guest debug. In the debug ioctl we copy an IMPDEF registers into a new register set called host_debug_state. We use the recently introduced vcpu parameter debug_ptr to select which register set is copied into the real registers when world switch occurs. I've made some helper functions from hw_breakpoint.c more widely available for re-use. As with single step we need to tweak the guest registers to enable the exceptions so we need to save and restore those bits. Two new capabilities have been added to the KVM_EXTENSION ioctl to allow userspace to query the number of hardware break and watch points available on the host hardware. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I00815c6115f02c680a2249f31012cfb2cae30b53 Signed-off-by: Alex Benne &lt;alex.bennee@linaro.org&gt; Reviewed-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit 5540546bc93b49f98a0466fe3f96615286c76574) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; [SR: 3.18: left hole in KVM CAP numbering for things we're missing in 3.18] Conflicts: include/uapi/linux/kvm.h Reviewed-on: https://chromium-review.googlesource.com/1245224 " fail_count="0" gerrit_number="1245224" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/24/1245224/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ic13fd9f6b79d69a021fab5366c2b9ca607a454c7" commit="191d37e1fd6928ff6ebdac6895d9f99b5c6eeea2" commit_message="UPSTREAM: KVM: arm64: enable KVM_CAP_SET_GUEST_DEBUG Finally advertise the KVM capability for SET_GUEST_DEBUG. Once arm support is added this check can be moved to the common kvm_vm_ioctl_check_extension() code. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Ic13fd9f6b79d69a021fab5366c2b9ca607a454c7 Signed-off-by: Alex Benne &lt;alex.bennee@linaro.org&gt; Acked-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit 834bf88726f0f11ddc7ff9679fc9458654c01a12) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245225 " fail_count="0" gerrit_number="1245225" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/25/1245225/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I62cde61479a98a7cc95f3d45459a2497dc4441fd" commit="5fa781e805acb691229289fbd56945d0bc13a541" commit_message="UPSTREAM: KVM: arm64: add trace points for guest_debug debug This includes trace points for: kvm_arch_setup_guest_debug kvm_arch_clear_guest_debug I've also added some generic register setting trace events and also a trace point to dump the array of hardware registers. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I62cde61479a98a7cc95f3d45459a2497dc4441fd Acked-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Signed-off-by: Alex Benne &lt;alex.bennee@linaro.org&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit eef8c85a3b81301f912e8802a1dd9f42dd884947) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245226 " fail_count="0" gerrit_number="1245226" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/26/1245226/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Idcfbee5fdbb79c0f6bfea4d37408ed6e66fc1ee3" commit="598d3bd3f4287a1f34c36c5a5fd0da893d8e5d02" commit_message="UPSTREAM: arm64: KVM: Fix user access for debug registers When setting the debug register from userspace, make sure that copy_from_user() is called with its parameters in the expected order. It otherwise doesn't do what you think. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Idcfbee5fdbb79c0f6bfea4d37408ed6e66fc1ee3 Fixes: 84e690bfbed1 (&quot;KVM: arm64: introduce vcpu-&gt;arch.debug_ptr&quot;) Reported-by: Peter Maydell &lt;peter.maydell@linaro.org&gt; Cc: Alex Benne &lt;alex.bennee@linaro.org&gt; Reviewed-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit 1713e5aa05fff3951e747548b373bd2c81be4e7a) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245227 " fail_count="0" gerrit_number="1245227" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/27/1245227/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Iaee0c079119933f4c8f570c231cd8c797540e406" commit="d5f1f7a79e2aaf51f50beb862633f8e7a06faec8" commit_message="UPSTREAM: arm64: KVM: Optimize arm64 skip 30-50% vfp/simd save/restore on exits This patch only saves and restores FP/SIMD registers on Guest access. To do this cptr_el2 FP/SIMD trap is set on Guest entry and later checked on exit. lmbench, hackbench show significant improvements, for 30-50% exits FP/SIMD context is not saved/restored [chazy/maz: fixed save/restore logic for 32bit guests] BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: Iaee0c079119933f4c8f570c231cd8c797540e406 Signed-off-by: Mario Smarduch &lt;m.smarduch@samsung.com&gt; Signed-off-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit 33c76a0b8126946026fa1122cb774553afae0956) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245228 " fail_count="0" gerrit_number="1245228" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/28/1245228/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I417cdabe2b7237c919b9039454a97f739d6bc242" commit="37edc478a893b93aa76a926f09ad56832798db29" commit_message="UPSTREAM: arm64: KVM: Disable virtual timer even if the guest is not using it When running a guest with the architected timer disabled (with QEMU and the kernel_irqchip=off option, for example), it is important to make sure the timer gets turned off. Otherwise, the guest may try to enable it anyway, leading to a screaming HW interrupt. The fix is to unconditionally turn off the virtual timer on guest exit. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I417cdabe2b7237c919b9039454a97f739d6bc242 Cc: stable@vger.kernel.org Reviewed-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit c4cbba9fa078f55d9f6d081dbb4aec7cf969e7c7) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245229 " fail_count="0" gerrit_number="1245229" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/29/1245229/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I76c6b07d16997253967bce6525d1be7a2c97366d" commit="f3817ebb9984fb2791127c6243ac81882e4b5edf" commit_message="UPSTREAM: arm64: KVM: Remove all traces of the ThumbEE registers Although the ThumbEE registers and traps were present in earlier versions of the v8 architecture, it was retrospectively removed and so we can do the same. Whilst this breaks migrating a guest started on a previous version of the kernel, it is much better to kill these (non existent) registers as soon as possible. BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I76c6b07d16997253967bce6525d1be7a2c97366d Reviewed-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; Signed-off-by: Will Deacon &lt;will.deacon@arm.com&gt; [maz: added commend about migration] Signed-off-by: Marc Zyngier &lt;marc.zyngier@arm.com&gt; (cherry picked from commit 34c3faa353db8f5d3ce9966cf854d5643c64c4db) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245230 " fail_count="0" gerrit_number="1245230" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/30/1245230/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I6fb207ee6dc541ad2ba7b3329c9f79271959d501" commit="cab6a0a64ced5d9099dbc32758fdc37a5500bee8" commit_message="UPSTREAM: arm64/kvm: Make use of the system wide safe values Use the system wide safe value from the new API for safer decisions BUG=chromium:889539 TEST=build/boot on hana with USE=kvm_host - ensure SMC workaround is being called Change-Id: I6fb207ee6dc541ad2ba7b3329c9f79271959d501 Cc: Marc Zyngier &lt;marc.zyngier@arm.com&gt; Cc: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Cc: kvmarm@lists.cs.columbia.edu Signed-off-by: Suzuki K. Poulose &lt;suzuki.poulose@arm.com&gt; Acked-by: Christoffer Dall &lt;christoffer.dall@linaro.org&gt; Tested-by: Dave Martin &lt;Dave.Martin@arm.com&gt; Signed-off-by: Catalin Marinas &lt;catalin.marinas@arm.com&gt; (cherry picked from commit 4db8e5ea6b07ae83e4361aee3f967f7126e01fa4) Signed-off-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1245231 " fail_count="0" gerrit_number="1245231" owner_email="sonnyrao@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/31/1245231/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="If42f994443c4f11152fca8da16f27fa4cd80580d" commit="e4cd9bcb059d45a8fbf4b903136b4e1716271baf" commit_message="move pci root creation to arch passing everything in to the pci code is getting annoying. Instead build it up in arch which already has access to all the needed resources. Change-Id: If42f994443c4f11152fca8da16f27fa4cd80580d Reviewed-on: https://chromium-review.googlesource.com/1237357 Commit-Ready: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Tested-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Reviewed-by: Dylan Reid &lt;dgreid@chromium.org&gt; " fail_count="1" gerrit_number="1237357" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="3" project="chromiumos/platform/crosvm" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosvm" ref="refs/changes/57/1237357/3" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="Ib4000eafe2d7d003ed5753d7b0ea05e16fd06130" commit="d7cd8512a3d9aa0fa2a6ad3343de48a987f3239f" commit_message="devices: pci: add Programming Interface to device PCI class codes are made up of three fields: class, subclass, and programming interface. Some class/subclass combinations do not define any programming interfaces, so add an optional parameter to specify the value and use 0 if it is not provided. Change-Id: Ib4000eafe2d7d003ed5753d7b0ea05e16fd06130 Signed-off-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1237358 Reviewed-by: Dylan Reid &lt;dgreid@chromium.org&gt; " fail_count="1" gerrit_number="1237358" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform/crosvm" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosvm" ref="refs/changes/58/1237358/5" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I0b1f5b827b55c4d8960ffa95331b82f9c692f304" commit="fab739698a7af2768e2b6ebc66fe4bae0673cf4a" commit_message="devices: pci: add keep_fds to PciDevice PciDevice implementations will have file descriptors that need to be preserved across the minijail fork. Change-Id: I0b1f5b827b55c4d8960ffa95331b82f9c692f304 Signed-off-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1237359 Reviewed-by: Dylan Reid &lt;dgreid@chromium.org&gt; " fail_count="1" gerrit_number="1237359" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform/crosvm" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosvm" ref="refs/changes/59/1237359/5" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I2524c4e8c04f75a8d7868cac998304aecbb29c40" commit="f8514cf42feee808e27185372d1df5afcc0151a7" commit_message="devices: pci: add ioeventfds to PciDevice trait VirtioDevices and potentially others need to register ioeventfds that will be triggered when guests write to certain addresses. Allow PciDevices to return an array of ioeventfds that the VM can install. Change-Id: I2524c4e8c04f75a8d7868cac998304aecbb29c40 Signed-off-by: Dylan Reid &lt;dgreid@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1237360 Commit-Ready: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Tested-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; " fail_count="1" gerrit_number="1237360" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform/crosvm" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosvm" ref="refs/changes/60/1237360/5" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I6e965c5fe7218abe6986b461731f18abb34894c1" commit="43be1938fc0f9c8f3d88e27b79eea0d7b781dac4" commit_message="devices: pci: fix add_bar return value Return the BAR number rather than the register offset within PCI config space. Change-Id: I6e965c5fe7218abe6986b461731f18abb34894c1 Signed-off-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1240653 Reviewed-by: Dylan Reid &lt;dgreid@chromium.org&gt; " fail_count="1" gerrit_number="1240653" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="4" project="chromiumos/platform/crosvm" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosvm" ref="refs/changes/53/1240653/4" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="Ia1dcb478cdab6654087925093ef9d1204edb21c9" commit="218c7ede582234b5413b20c04874fdb4a21afb1d" commit_message="devices: pci: fix registration of PCI IRQs MPTABLE needs the PCI device number, not the IRQ; modify the information passed via pci_irqs so that it contains a (device index, interrupt pin) tuple. Change-Id: Ia1dcb478cdab6654087925093ef9d1204edb21c9 Signed-off-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1237362 Reviewed-by: Dylan Reid &lt;dgreid@chromium.org&gt; " fail_count="1" gerrit_number="1237362" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform/crosvm" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosvm" ref="refs/changes/62/1237362/5" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="If61f79cd80950bf517d69c18aaf98c2e76841a56" commit="3a3cd3928c3af6544b77a2f3bdf290c91fd79d4b" commit_message="devices: pci: ignore writable_bits when adding caps The add_capability() function was using the normal PCI configuration write_byte() function, which enforces read-only regions. This won't work once the appropriate regions of config space are marked as read only in the following commit, so add an internal-only helper function to access bytes without applying writable_bits. Change-Id: If61f79cd80950bf517d69c18aaf98c2e76841a56 Signed-off-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1240658 Reviewed-by: Dylan Reid &lt;dgreid@chromium.org&gt; " fail_count="1" gerrit_number="1240658" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="4" project="chromiumos/platform/crosvm" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosvm" ref="refs/changes/58/1240658/4" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I67f93d81cfbac6000db51663bdf76e54aeac08f3" commit="61adbfc280196150176d5b95a4030d52561f88ea" commit_message="devices: pci: make more registers read only Most of PCI configuration space should be read only; initialize the writable_bits field accordingly. Change-Id: I67f93d81cfbac6000db51663bdf76e54aeac08f3 Signed-off-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1240659 Reviewed-by: Dylan Reid &lt;dgreid@chromium.org&gt; " fail_count="1" gerrit_number="1240659" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="4" project="chromiumos/platform/crosvm" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosvm" ref="refs/changes/59/1240659/4" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I87756b0ab31070d8717c76d419957bf5ea5d75ad" commit="d36709afaf8eeab3dfbc4531f594d54686bb2982" commit_message="devices: pci: refactor config access mechanism The current PciRoot is only workable for the legacy I/O port 0xCF8 access mechanism; factor out the config access mechanism part of PciRoot into PciConfigIo so that we can add a MMIO-based access mechanism for ARM. Change-Id: I87756b0ab31070d8717c76d419957bf5ea5d75ad Signed-off-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1241539 Reviewed-by: Dylan Reid &lt;dgreid@chromium.org&gt; " fail_count="1" gerrit_number="1241539" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/crosvm" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosvm" ref="refs/changes/39/1241539/2" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I61206b761f49f963f0cce706268379ceae1a0239" commit="c5015d0f3570873cc4b902e474aea5de92d3e57c" commit_message="devices: pci: add MMIO config access mechanism This will be used on ARM. Change-Id: I61206b761f49f963f0cce706268379ceae1a0239 Signed-off-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1241540 Reviewed-by: Dylan Reid &lt;dgreid@chromium.org&gt; " fail_count="1" gerrit_number="1241540" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/crosvm" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosvm" ref="refs/changes/40/1241540/2" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I5b77e0d84f0bc7b854e33aaeb34ff011af226103" commit="1cef745fa51f5edea1fd0b10f2fdbd154cd4081e" commit_message="virtio: set default queue size to maximum The virtio PCI transport requires that the queue_size configuration value returns the maximum supported queue size on reset; it uses 0 to indicate an unavailable queue. Queue::size is write-only via the existing MmioDevice (the driver must always write a queue size during initialization), so there should be no difference in behavior when using MMIO virtio devices. Change-Id: I5b77e0d84f0bc7b854e33aaeb34ff011af226103 Signed-off-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1237363 Reviewed-by: Dylan Reid &lt;dgreid@chromium.org&gt; " fail_count="1" gerrit_number="1237363" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="6" project="chromiumos/platform/crosvm" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosvm" ref="refs/changes/63/1237363/6" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I0cc44edacc5f435510ab8ae9b38a925a0ee5d008" commit="cc415b3fcfafa24f977f1a2d838752b246eba913" commit_message="x86_64: increase size of MMIO range VirtioPci uses 0x4000 bytes of MMIO space per device, so the existing allocation of 0x10000 was only enough for 4 devices; extend the MMIO region to allow for more devices. Change-Id: I0cc44edacc5f435510ab8ae9b38a925a0ee5d008 Signed-off-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1240654 Reviewed-by: Dylan Reid &lt;dgreid@chromium.org&gt; " fail_count="1" gerrit_number="1240654" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform/crosvm" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosvm" ref="refs/changes/54/1240654/5" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I2f0a9b04356cce912874a06e62b4f3a59cbb08f1" commit="a8b3929407362de1bf74229fa4a2071ca835aaf4" commit_message="aarch64: add generic PCI host controller Implement the generic PCI host as supported by Linux and described in Documentation/devicetree/bindings/pci/host-generic-pci.txt in the kernel source tree. Also increase the ARM64 MMIO region size from 0x10000 to 0x100000 to allow enough space for several virtio PCI devices. Change-Id: I2f0a9b04356cce912874a06e62b4f3a59cbb08f1 Signed-off-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1244398 Reviewed-by: Sonny Rao &lt;sonnyrao@chromium.org&gt; " fail_count="1" gerrit_number="1244398" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="3" project="chromiumos/platform/crosvm" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosvm" ref="refs/changes/98/1244398/3" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="Ieaa83205ba4e3f029f6d183a1b93799352551299" commit="fee175561688b5dff74d1ddab629288445bc1071" commit_message="devices: Implement virtio PCI transport Change-Id: Ieaa83205ba4e3f029f6d183a1b93799352551299 Signed-off-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1237364 Reviewed-by: Dylan Reid &lt;dgreid@chromium.org&gt; " fail_count="1" gerrit_number="1237364" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="10" project="chromiumos/platform/crosvm" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosvm" ref="refs/changes/64/1237364/10" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-4.4" change_id="Ia7e57f97a19e4923d68997a62ffe634884115796" commit="d86736e2d2359717b8579bb6688fd4c65107b428" commit_message="Revert &quot;FROMLIST: ASoC: rt5514: The DSP clock can be calibrated by the other clock source&quot; This reverts commit 3a33e1c62256696c57dedd6e1e418af93943765f. Revert this change and pick the fix from upstream, which support DSP hotwording for both eve and kevin. BUG=b:114680776 TEST=Apply full patch set and use $ test_that --debug --fast --board=kevin \ --args=&quot;chameleon_host=$CHAMELEON_IP&quot; $DUT_IP \ audio_AudioBasicHotwording To check if there is any frequency shift on both kevin and eve. CQ-DEPEND=CL:1235399 Change-Id: Ia7e57f97a19e4923d68997a62ffe634884115796 Reviewed-on: https://chromium-review.googlesource.com/1235398 Commit-Ready: Chih-Yang Hsia &lt;paulhsia@chromium.org&gt; Tested-by: Chih-Yang Hsia &lt;paulhsia@chromium.org&gt; Reviewed-by: Cheng-Yi Chiang &lt;cychiang@chromium.org&gt; " fail_count="1" gerrit_number="1235398" owner_email="paulhsia@chromium.org" pass_count="0" patch_number="3" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/98/1235398/3" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-4.4" change_id="I98de760c7c728feb4d158ef5629f48bc3b42bcec" commit="d88e7a85af246fa51eb86e07bb6e434621cfaa16" commit_message="BACKPORT: ASoC: rt5514: The DSP clock can be calibrated by the other clock source Add the option for the DSP clock that can be calibrated by the other clock source. Signed-off-by: Oder Chiou &lt;oder_chiou@realtek.com&gt; Signed-off-by: Mark Brown &lt;broonie@kernel.org&gt; (cherry picked from commit fc9cab05837639ce3372870b09d26334fb15b157) Conflicts: sound/soc/codecs/rt5514.h BUG=b:114680776 TEST=Apply full patch set and use $ test_that --debug --fast --board=kevin \ --args=&quot;chameleon_host=$CHAMELEON_IP&quot; $DUT_IP \ audio_AudioBasicHotwording To check if there is any frequency shift on kevin and eve. Change-Id: I98de760c7c728feb4d158ef5629f48bc3b42bcec Signed-off-by: paulhsia &lt;paulhsia@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1235399 Commit-Ready: Chih-Yang Hsia &lt;paulhsia@chromium.org&gt; Tested-by: Chih-Yang Hsia &lt;paulhsia@chromium.org&gt; Reviewed-by: Cheng-Yi Chiang &lt;cychiang@chromium.org&gt; " fail_count="1" gerrit_number="1235399" owner_email="paulhsia@chromium.org" pass_count="0" patch_number="3" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/99/1235399/3" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I77ddea0d3c83bee32b2da75e76f2a59b9a40e4a7" commit="46141de6f1af23ce1f899ebc3188dd3220e51018" commit_message="biod: migrate the package to GN BUG=chromium:767517 TEST=precq passes Change-Id: I77ddea0d3c83bee32b2da75e76f2a59b9a40e4a7 Reviewed-on: https://chromium-review.googlesource.com/1198283 Commit-Ready: Keigo Oka &lt;oka@chromium.org&gt; Tested-by: Keigo Oka &lt;oka@chromium.org&gt; Reviewed-by: Keigo Oka &lt;oka@chromium.org&gt; Reviewed-by: Shuhei Takahashi &lt;nya@chromium.org&gt; " fail_count="0" gerrit_number="1198283" owner_email="oka@chromium.org" pass_count="0" patch_number="13" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/83/1198283/13" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Id1ad0d701da41b80ee791d06b356ce21a1fd05ee" commit="665fa3645645afa89e328c5fdadc8a805aa9bb6f" commit_message="arc: migrate arc/network to GN CQ-DEPEND=CL:1149942 CQ-DEPEND=CL:1201803 CQ-DEPEND=CL:1203931 BUG=chromium:767517 TEST=precq passes Change-Id: Id1ad0d701da41b80ee791d06b356ce21a1fd05ee Reviewed-on: https://chromium-review.googlesource.com/1203354 Commit-Ready: Keigo Oka &lt;oka@chromium.org&gt; Tested-by: Keigo Oka &lt;oka@chromium.org&gt; Reviewed-by: Keigo Oka &lt;oka@chromium.org&gt; Reviewed-by: Shuhei Takahashi &lt;nya@chromium.org&gt; " fail_count="0" gerrit_number="1203354" owner_email="oka@chromium.org" pass_count="0" patch_number="3" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/54/1203354/3" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I0d816e8ebc49c30c25072e9ae4b1780771ef54a0" commit="1ce5e5547fef8dcb2c4f9210766e9ea767e41440" commit_message="dlcservice: migrate the package to GN CQ-DEPEND=CL:1149942 CQ-DEPEND=CL:1201803 BUG=chromium:767517 TEST=precq passes Change-Id: I0d816e8ebc49c30c25072e9ae4b1780771ef54a0 Reviewed-on: https://chromium-review.googlesource.com/1209014 Commit-Ready: Keigo Oka &lt;oka@chromium.org&gt; Tested-by: Keigo Oka &lt;oka@chromium.org&gt; Reviewed-by: Keigo Oka &lt;oka@chromium.org&gt; Reviewed-by: Shuhei Takahashi &lt;nya@chromium.org&gt; " fail_count="0" gerrit_number="1209014" owner_email="oka@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/14/1209014/2" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-4.4" change_id="I3b28589c3d238b9f6f82a71321eaf6aa75743e6e" commit="54e832535574728488990dfaf8bb1205fc109a14" commit_message="cros-ec: improve IRQ timestamping jitter This commit enables the ability for the kernel to receive synchronization events from the EC over a GPIO IRQ. This is done in order to improve the jitter with which sensor events are received by the sensor ring. BUG=b:112111610 TEST=collect sensor events on Nocturne Change-Id: I3b28589c3d238b9f6f82a71321eaf6aa75743e6e Signed-off-by: Enrico Granata &lt;egranata@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1229593 Reviewed-by: Gwendal Grignou &lt;gwendal@chromium.org&gt; Reviewed-by: Dmitry Torokhov &lt;dtor@chromium.org&gt; " fail_count="5" gerrit_number="1229593" owner_email="egranata@chromium.org" pass_count="0" patch_number="11" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/93/1229593/11" remote="cros" total_fail_count="5"/><pending_commit branch="master" change_id="If22f4b6f8259fd6f6f5912987042eec7bbf0db48" commit="5d0ddffb1ce727b5813b9fd389eacb97632b8504" commit_message="chromeos-config: clarify identity docs This specifies the background and usecase for customization_id and whitelabel_tag, which was missing previously in the doc. BUG=b:116096324 TEST=./run_tests.sh Change-Id: If22f4b6f8259fd6f6f5912987042eec7bbf0db48 Reviewed-on: https://chromium-review.googlesource.com/1239235 Commit-Ready: Nick Sanders &lt;nsanders@chromium.org&gt; Tested-by: Nick Sanders &lt;nsanders@chromium.org&gt; Reviewed-by: Aaron Durbin &lt;adurbin@chromium.org&gt; " fail_count="1" gerrit_number="1239235" owner_email="nsanders@chromium.org" pass_count="0" patch_number="4" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/35/1239235/4" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.18" change_id="I81e6832f26d34c95ec84e089cd623c752f60724a" commit="53fbded9bb28ab1a08f2a39a2530f07bdd7d0fa8" commit_message="UPSTREAM: hfsplus: fix NULL dereference in hfsplus_lookup() An HFS+ filesystem can be mounted read-only without having a metadata directory, which is needed to support hardlinks. But if the catalog data is corrupted, a directory lookup may still find dentries claiming to be hardlinks. hfsplus_lookup() does check that -&gt;hidden_dir is not NULL in such a situation, but mistakenly does so after dereferencing it for the first time. Reorder this check to prevent a crash. This happens when looking up corrupted catalog data (dentry) on a filesystem with no metadata directory (this could only ever happen on a read-only mount). Wen Xu sent the replication steps in detail to the fsdevel list: https://bugzilla.kernel.org/show_bug.cgi?id=200297 BUG=chromium:888329 TEST=None Conflict Note: The patch applied is the same as upstream. When applying the patch there is a conflict as upstream uses HFSPLUS_I(d_inode(sb-&gt;s_root)) while v3.18 uses HFSPLUS_I(sb-&gt;s_root-&gt;d_inode) in order to obtain the hfsplus_inode_info. Change-Id: I81e6832f26d34c95ec84e089cd623c752f60724a Link: http://lkml.kernel.org/r/20180712215344.q44dyrhymm4ajkao@eaf Signed-off-by: Ernesto A. Fernndez &lt;ernesto.mnd.fernandez@gmail.com&gt; Reported-by: Wen Xu &lt;wen.xu@gatech.edu&gt; Cc: Viacheslav Dubeyko &lt;slava@dubeyko.com&gt; Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt; Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt; (cherry picked from commit a7ec7a4193a2eb3b5341243fc0b621c1ac9e4ec4) Signed-off-by: Zubin Mithra &lt;zsm@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1241534 " fail_count="1" gerrit_number="1241534" owner_email="zsm@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/34/1241534/1" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I83efcbece1c8da58c33ae06bac5a27e59b176687" commit="4d1ec050615a3b5008a13ea08240534e952d7cc7" commit_message="octopus: Prevent powerd from inhibiting side buttons in tablet mode BUG=b:116686313 TEST=Build package and verify power and volume button function Change-Id: I83efcbece1c8da58c33ae06bac5a27e59b176687 Signed-off-by: Amanda Huang &lt;amanda_hwang@compal.corp-partner.google.com&gt; Reviewed-on: https://chromium-review.googlesource.com/1248821 Commit-Ready: Amanda Hwang &lt;amanda_hwang@compal.corp-partner.google.com&gt; Tested-by: Amanda Hwang &lt;amanda_hwang@compal.corp-partner.google.com&gt; Reviewed-by: Jett Rink &lt;jettrink@chromium.org&gt; Reviewed-by: Justin TerAvest &lt;teravest@chromium.org&gt; " fail_count="0" gerrit_number="1248821" owner_email="amanda_hwang@compal.corp-partner.google.com" pass_count="0" patch_number="3" project="chromiumos/overlays/board-overlays" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/board-overlays" ref="refs/changes/21/1248821/3" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.10" change_id="I0083260e7910ab23fb32934d30f6a11fc4e232c6" commit="a5b2615d4519808ef390680d98272523d0cab69e" commit_message="UPSTREAM: ext4: clear i_data in ext4_inode_info when removing inline data When converting from an inode from storing the data in-line to a data block, ext4_destroy_inline_data_nolock() was only clearing the on-disk copy of the i_blocks[] array. It was not clearing copy of the i_blocks[] in ext4_inode_info, in i_data[], which is the copy actually used by ext4_map_blocks(). This didn't matter much if we are using extents, since the extents header would be invalid and thus the extents could would re-initialize the extents tree. But if we are using indirect blocks, the previous contents of the i_blocks array will be treated as block numbers, with potentially catastrophic results to the file system integrity and/or user data. This gets worse if the file system is using a 1k block size and s_first_data is zero, but even without this, the file system can get quite badly corrupted. This addresses CVE-2018-10881. https://bugzilla.kernel.org/show_bug.cgi?id=200015 BUG=chromium:888319 TEST=None Change-Id: I0083260e7910ab23fb32934d30f6a11fc4e232c6 Signed-off-by: Theodore Ts'o &lt;tytso@mit.edu&gt; Cc: stable@kernel.org (cherry picked from commit 6e8ab72a812396996035a37e5ca4b3b99b5d214b) Signed-off-by: Zubin Mithra &lt;zsm@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1251743 " fail_count="1" gerrit_number="1251743" owner_email="zsm@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/43/1251743/1" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I72edb13ef81e5106e2d43a59347ec3bf068f0c1a" commit="1380de448aabae53356737229252afb684456f60" commit_message="UPSTREAM: ext4: verify the depth of extent tree in ext4_find_extent() If there is a corupted file system where the claimed depth of the extent tree is -1, this can cause a massive buffer overrun leading to sadness. This addresses CVE-2018-10877. https://bugzilla.kernel.org/show_bug.cgi?id=199417 BUG=chromium:888315 TEST=None Change-Id: I72edb13ef81e5106e2d43a59347ec3bf068f0c1a Signed-off-by: Theodore Ts'o &lt;tytso@mit.edu&gt; Cc: stable@kernel.org (cherry picked from commit bc890a60247171294acc0bd67d211fa4b88d40ba) Signed-off-by: Zubin Mithra &lt;zsm@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1240897 (cherry picked from commit 5bef272b4b8d9868640f21a405db5cf6497c0d98) Reviewed-on: https://chromium-review.googlesource.com/1251746 " fail_count="1" gerrit_number="1251746" owner_email="zsm@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/46/1251746/1" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-4.14" change_id="I71bf90a955dbef5103db0e58aa38ec50d6ea3797" commit="f3afff0151d4a9a1890c8330b12f428135d185c7" commit_message="CHROMIUM: arch: arm64: config: enable /proc/config.gz This brings the arm64 container-vm config in line with x86. BUG=None TEST=Boot VM on kevin and verify existence of /proc/config.gz Change-Id: I71bf90a955dbef5103db0e58aa38ec50d6ea3797 Signed-off-by: Daniel Verkamp &lt;dverkamp@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1252411 Reviewed-by: Stephen Barber &lt;smbarber@chromium.org&gt; " fail_count="0" gerrit_number="1252411" owner_email="dverkamp@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/11/1252411/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I9412ae7cf0319d160dd4f301e33247b913bb2902" commit="d99df5c151664f27893f0a82938a7336784c7b35" commit_message="hermes: Change interface naming scheme and remove esim interface This CL changes the naming scheme of classes, such that interface classes have the suffix 'Interface', rather than having implementation classes use the suffix 'Impl*'. This is done for consistency, as classes that do not use an interface don't use the 'Impl*' suffix, making it hard to tell from a class name whether it is an implementation class or an interface class. The esim interface class is also removed, as there is only one esim implementation. A future CL separates modem-specific functionality from the esim implementation, making it unnecessary to create more esim implementations. Instead, supporting new modems will simply involve creating a new modem implementation. BUG=chromium:847619 TEST=`cros_workon_make --board ${BOARD} hermes --test` builds successfully. Note that the unit tests still do not pass. This will be changed after the Esim implementation is isolated from QRTR-specific functionality, as unit-testing the resulting Esim implementation will be easier. Change-Id: I9412ae7cf0319d160dd4f301e33247b913bb2902 Reviewed-on: https://chromium-review.googlesource.com/1199596 Commit-Ready: Alex Khouderchah &lt;akhouderchah@chromium.org&gt; Tested-by: Alex Khouderchah &lt;akhouderchah@chromium.org&gt; Reviewed-by: Ben Chan &lt;benchan@chromium.org&gt; " fail_count="1" gerrit_number="1199596" owner_email="akhouderchah@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/96/1199596/5" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I766d5ec3628d5afcc8aeda549d5a7501a23298bd" commit="1dc688120df9a44733fbcb1a8a20570476cf3c80" commit_message="crash: update anomaly_collector links Lets drive people to the C++ file. BUG=chromium:874698 TEST=precq passes Change-Id: I766d5ec3628d5afcc8aeda549d5a7501a23298bd Reviewed-on: https://chromium-review.googlesource.com/1229277 Commit-Ready: Mike Frysinger &lt;vapier@chromium.org&gt; Tested-by: Mike Frysinger &lt;vapier@chromium.org&gt; Reviewed-by: Luigi Semenzato &lt;semenzato@chromium.org&gt; " fail_count="0" gerrit_number="1229277" owner_email="vapier@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/77/1229277/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I54d92a521a8f33fdc5def4595d74e0570f842570" commit="03693a3469e422444ce52062f811f1d4f9b6a232" commit_message="intel: ipu3: fix cts cases testMandatoryReprocessConfigurations [Issue] run cts cases testMandatoryReprocessConfigurations failed. [Root Cause] Since camera hal does not support 4 output streams. Causes camera congfig streams to fail. [Changes] Put the repeated yuv output stream into the outWorker's Listener for listening. Then return the data by copying mWorkingBuffer. BUG=b:116177076 TEST=Build and deploy package to platform and camera works Change-Id: I54d92a521a8f33fdc5def4595d74e0570f842570 Signed-off-by: shigangx.yang &lt;shigangx.yang@intel.com&gt; Reviewed-on: https://chromium-review.googlesource.com/1234720 Commit-Ready: Wei Meng &lt;wei.meng@intel.corp-partner.google.com&gt; Tested-by: Ricky Liang &lt;jcliang@chromium.org&gt; Reviewed-by: Ricky Liang &lt;jcliang@chromium.org&gt; " fail_count="0" gerrit_number="1234720" owner_email="wei.meng@intel.com" pass_count="0" patch_number="5" project="chromiumos/platform/arc-camera" project_url="https://chromium-review.googlesource.com/chromiumos/platform/arc-camera" ref="refs/changes/20/1234720/5" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I80019368220103c45936a14fc0f7a8767330dae3" commit="7e78d9779421dc2643a8a7ef26a7623eedf16389" commit_message="cros-firmware.eclass: Remove unused variables. The STABLE variables have been deprecated for a while, and no overlays use them. Also added TODO for deprecating CROS_FIRMWARE_EXTRA_LIST and CROS_FIRMWARE_BUILD_MAIN_RW_IMAGE. BUG=chromium:882445 TEST=build_packages --board $BOARD; build_image --board $BOARD Change-Id: I80019368220103c45936a14fc0f7a8767330dae3 Reviewed-on: https://chromium-review.googlesource.com/1242863 Commit-Ready: Hung-Te Lin &lt;hungte@chromium.org&gt; Tested-by: Hung-Te Lin &lt;hungte@chromium.org&gt; Reviewed-by: Mike Frysinger &lt;vapier@chromium.org&gt; " fail_count="1" gerrit_number="1242863" owner_email="hungte@chromium.org" pass_count="0" patch_number="1" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/63/1242863/1" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I8f1682846b3a1433102cf31dae07f63a102ac05b" commit="dbc7faf83138f22f64526fb79d8c7223f2322a08" commit_message="Whitelist .gn for shill BUG=chromium:767517 TEST=None Change-Id: I8f1682846b3a1433102cf31dae07f63a102ac05b Reviewed-on: https://chromium-review.googlesource.com/1250301 Commit-Ready: Keigo Oka &lt;oka@chromium.org&gt; Tested-by: Keigo Oka &lt;oka@chromium.org&gt; Reviewed-by: Keigo Oka &lt;oka@chromium.org&gt; Reviewed-by: Shuhei Takahashi &lt;nya@chromium.org&gt; " fail_count="1" gerrit_number="1250301" owner_email="oka@chromium.org" pass_count="0" patch_number="1" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/01/1250301/1" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I0083260e7910ab23fb32934d30f6a11fc4e232c6" commit="3d6b6c3da381143df8434220fad7088262550239" commit_message="UPSTREAM: ext4: clear i_data in ext4_inode_info when removing inline data When converting from an inode from storing the data in-line to a data block, ext4_destroy_inline_data_nolock() was only clearing the on-disk copy of the i_blocks[] array. It was not clearing copy of the i_blocks[] in ext4_inode_info, in i_data[], which is the copy actually used by ext4_map_blocks(). This didn't matter much if we are using extents, since the extents header would be invalid and thus the extents could would re-initialize the extents tree. But if we are using indirect blocks, the previous contents of the i_blocks array will be treated as block numbers, with potentially catastrophic results to the file system integrity and/or user data. This gets worse if the file system is using a 1k block size and s_first_data is zero, but even without this, the file system can get quite badly corrupted. This addresses CVE-2018-10881. https://bugzilla.kernel.org/show_bug.cgi?id=200015 BUG=chromium:888319 TEST=None Change-Id: I0083260e7910ab23fb32934d30f6a11fc4e232c6 Signed-off-by: Theodore Ts'o &lt;tytso@mit.edu&gt; Cc: stable@kernel.org (cherry picked from commit 6e8ab72a812396996035a37e5ca4b3b99b5d214b) Signed-off-by: Zubin Mithra &lt;zsm@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1251742 " fail_count="1" gerrit_number="1251742" owner_email="zsm@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/42/1251742/1" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.14" change_id="I81e6832f26d34c95ec84e089cd623c752f60724a" commit="0b6ea2674f02744d9d7fb7e17588e659d199dbdc" commit_message="UPSTREAM: hfsplus: fix NULL dereference in hfsplus_lookup() An HFS+ filesystem can be mounted read-only without having a metadata directory, which is needed to support hardlinks. But if the catalog data is corrupted, a directory lookup may still find dentries claiming to be hardlinks. hfsplus_lookup() does check that -&gt;hidden_dir is not NULL in such a situation, but mistakenly does so after dereferencing it for the first time. Reorder this check to prevent a crash. This happens when looking up corrupted catalog data (dentry) on a filesystem with no metadata directory (this could only ever happen on a read-only mount). Wen Xu sent the replication steps in detail to the fsdevel list: https://bugzilla.kernel.org/show_bug.cgi?id=200297 BUG=chromium:888329 TEST=None Conflict Note: The patch applied is the same as upstream. When applying the patch there is a conflict as upstream uses HFSPLUS_I(d_inode(sb-&gt;s_root)) while v3.18 uses HFSPLUS_I(sb-&gt;s_root-&gt;d_inode) in order to obtain the hfsplus_inode_info. Change-Id: I81e6832f26d34c95ec84e089cd623c752f60724a Link: http://lkml.kernel.org/r/20180712215344.q44dyrhymm4ajkao@eaf Signed-off-by: Ernesto A. Fernndez &lt;ernesto.mnd.fernandez@gmail.com&gt; Reported-by: Wen Xu &lt;wen.xu@gatech.edu&gt; Cc: Viacheslav Dubeyko &lt;slava@dubeyko.com&gt; Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt; Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt; (cherry picked from commit a7ec7a4193a2eb3b5341243fc0b621c1ac9e4ec4) Signed-off-by: Zubin Mithra &lt;zsm@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1252542 " fail_count="1" gerrit_number="1252542" owner_email="zsm@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/42/1252542/1" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-3.8" change_id="I81e6832f26d34c95ec84e089cd623c752f60724a" commit="db21d8cf55e5c21a484b232f1e81e6df7c5f250b" commit_message="UPSTREAM: hfsplus: fix NULL dereference in hfsplus_lookup() An HFS+ filesystem can be mounted read-only without having a metadata directory, which is needed to support hardlinks. But if the catalog data is corrupted, a directory lookup may still find dentries claiming to be hardlinks. hfsplus_lookup() does check that -&gt;hidden_dir is not NULL in such a situation, but mistakenly does so after dereferencing it for the first time. Reorder this check to prevent a crash. This happens when looking up corrupted catalog data (dentry) on a filesystem with no metadata directory (this could only ever happen on a read-only mount). Wen Xu sent the replication steps in detail to the fsdevel list: https://bugzilla.kernel.org/show_bug.cgi?id=200297 BUG=chromium:888329 TEST=None Conflict Note: The patch applied is the same as upstream. When applying the patch there is a conflict as upstream uses HFSPLUS_I(d_inode(sb-&gt;s_root)) while v3.18 uses HFSPLUS_I(sb-&gt;s_root-&gt;d_inode) in order to obtain the hfsplus_inode_info. Change-Id: I81e6832f26d34c95ec84e089cd623c752f60724a Link: http://lkml.kernel.org/r/20180712215344.q44dyrhymm4ajkao@eaf Signed-off-by: Ernesto A. Fernndez &lt;ernesto.mnd.fernandez@gmail.com&gt; Reported-by: Wen Xu &lt;wen.xu@gatech.edu&gt; Cc: Viacheslav Dubeyko &lt;slava@dubeyko.com&gt; Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt; Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt; (cherry picked from commit a7ec7a4193a2eb3b5341243fc0b621c1ac9e4ec4) Signed-off-by: Zubin Mithra &lt;zsm@chromium.org&gt; Reviewed-on: https://chromium-review.googlesource.com/1252544 " fail_count="1" gerrit_number="1252544" owner_email="zsm@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/kernel" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/kernel" ref="refs/changes/44/1252544/1" remote="cros" total_fail_count="1"/><lkgm version="11115.0.0-rc6"/></manifest>