| <?xml version="1.0" encoding="utf-8"?><manifest revision="224f88bb1b5eedbd1bf47a93ee673da96872b0c8"> |
| <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/libbrillo" path="src/aosp/external/libbrillo" revision="c4075810a258bbc60c7bcf0617c1dcb995edc8a8" upstream="refs/heads/master"/> |
| <project name="aosp/platform/external/libchrome" path="src/aosp/external/libchrome" revision="0b087f9dcf23367a24f0bacc738abe9ec8ed6506" 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/connectivity/apmanager" path="src/aosp/system/connectivity/apmanager" revision="367bdb38f60fdfe76814c8cf9f383ff8d6f5b484" upstream="refs/heads/master"/> |
| <project name="aosp/platform/system/connectivity/shill" path="src/aosp/system/connectivity/shill" revision="b0fad5dbdf8e187d761dd6a82bc757ef67bdc243" 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="76af266b36c5be01e819e7cd01f9cf19a72ccaa9" upstream="refs/heads/master"/> |
| <project name="apps/libapps" path="src/third_party/libapps" revision="34084004ea7bc8f29c6df7eacf8d46b274f340de" 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="94288c26d2ffe3aec9848c147839afee597acefd" upstream="refs/heads/master"/> |
| <project name="chromium/deps/libmtp" path="chromium/src/third_party/libmtp" remote="chromium" revision="a9c7333ec45588e0e6c2a26d21a8a474df1f53b6" 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="7822084a27865e185d561dd44632c761d8c1bec8" 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="5888d6f676722fdac3f65e673c0232667309296c"/> |
| <project groups="minilayout,firmware,buildtools,chromeos-admin,labtools,sysmon,devserver" name="chromiumos/chromite" path="chromite" revision="e6853c3d4b19bfc20fdf8985bfe2efa3c1969ea0" upstream="refs/heads/master"> |
| <copyfile dest="AUTHORS" src="AUTHORS"/> |
| <copyfile dest="LICENSE" src="LICENSE"/> |
| </project> |
| <project name="chromiumos/docs" path="docs" revision="23c971e885b19823edbdbc8ac26bd445e189eeea" upstream="refs/heads/master"/> |
| <project name="chromiumos/graphyte" path="src/platform/graphyte" revision="5042b8cf876294f36b721bde1d71e32f1a9c45cd" 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="f960281389e1d96e05d5d47f7f93402c50aa601d" 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="62c689e8d8655ac7410af6687da7179c0d6597ae" 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/lucifer" path="infra/lucifer" revision="2d02902f78f351816a078213f6353c5a1ab84e4c" upstream="refs/heads/master"/> |
| <project groups="chromeos-admin,labtools" name="chromiumos/infra/skylab_inventory" path="infra/skylab_inventory" revision="c1e867d38e574d31bc3ffda030a41a2e07e402df" upstream="refs/heads/master"/> |
| <project name="chromiumos/infra/suite_scheduler" path="infra/suite_scheduler" revision="02590fe17e0309e981f3e3bfdd0c5bd5c5feda65" 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="432fc2afc58bed4e1ffa53465b66cf289ae62f7c" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware" name="chromiumos/overlays/board-overlays" path="src/overlays" revision="a3c02f3e892b703e789321d4402423a945a5fbb4" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,labtools" name="chromiumos/overlays/chromiumos-overlay" path="src/third_party/chromiumos-overlay" revision="d0010673156d252037676b5653b37711e84bc3a4" sync-c="true" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,labtools" name="chromiumos/overlays/eclass-overlay" path="src/third_party/eclass-overlay" revision="37f59d89268b031d709ae2be5ed2e289c0bfff9e" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,labtools" name="chromiumos/overlays/portage-stable" path="src/third_party/portage-stable" revision="3315105a9a1d09a446f5861fa274665c8f3f7b19" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/arc-camera" path="src/platform/arc-camera" revision="b5248daae48335fa8f199c53dcaf71ac3a37f744" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/assets" path="src/platform/assets" revision="f09a19c98edab2419dbf385b040a431bcb8c008e" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/audiotest" path="src/platform/audiotest" revision="f15c830081b498ba8c4130de95d51ece8f8ef2e7" 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="acb6efd5d9db5903b462aea03fde2e8391068cf9" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/bmpblk" path="src/platform/bmpblk" revision="7d2154c31e59daa6f0f817575b4182ddef4c92af" 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="54d1e0437a0f246fb0132b7b24a2b74bf09d1124" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/chameleon" path="src/platform/chameleon" revision="08eab5f8b7788353bbab2b699c15926fa9a3d7e2" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/chromiumos-assets" path="src/platform/chromiumos-assets" revision="c72f1bc16319ebd970ad277e76ef10d0b4663461" 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="7bc20e670968a979c2dabf55497761b5c7fd0792" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,buildtools,labtools" name="chromiumos/platform/crosutils" path="src/scripts" revision="16441e1a62cf3a7e51748b31a61b8e23e8c34429" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/crosvm" path="src/platform/crosvm" revision="d8f10af6aeaff319f407578cdff1afd0324f5912" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/platform/depthcharge" path="src/platform/depthcharge" revision="faa19fa0f16e49f34d591551e532c72935f8110c" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,buildtools,devserver" name="chromiumos/platform/dev-util" path="src/platform/dev" revision="f6bd5742fe5235a79e439d5e0f022b5e940c7625" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/dm-verity" path="src/platform/verity" revision="0a59878032d4bda0c4a7c13b2086c59283df63f1" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/drm-tests" path="src/platform/drm-tests" revision="9a187d45f371a3f7d4a965095657403dbb91c9df" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/platform/ec" path="src/platform/ec" revision="359f1b582a080511179c26b6dd25e2db58587d23" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/experimental" path="src/platform/experimental" revision="71e236cd2eb8aa7aef05aa0d63c42c21f490c50d" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/factory" path="src/platform/factory" revision="98b911b1ba3e13de9aeba5812785b889ad6d6d6f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/factory_installer" path="src/platform/factory_installer" revision="1c428ba510cdd30cafbf97bdd3510aa29a8279b4" upstream="refs/heads/master"/> |
| <project groups="firmware" name="chromiumos/platform/firmware" path="src/platform/firmware" revision="b168a20180bfbfe98e580aee51b9fc28a9c09276" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/frecon" path="src/platform/frecon" revision="f6d4ab0388806d23ec5f25c592b8e3b57f0bb574" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/gestures" path="src/platform/gestures" revision="2233f714ef80f48b92991662f96b5e19e65d72aa" 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="9bcfabcaa75750fe01d97351941fb1d45e7e8722" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/initramfs" path="src/platform/initramfs" revision="093fd2ce7aef034aa98b5e7234e79b6b067d45c4" 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="2b682fde2d2fe12b95b434a47466bc69aa08b6bd" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/moblab" path="src/platform/moblab" revision="b437b3edaf1027e9e3b8bdb878a9f9f3eb21b6a4" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/monitor_reconfig" path="src/platform/monitor_reconfig" revision="f022d19d84f232290b596beeb26347f62442e7eb" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mosys" path="src/platform/mosys" revision="624dad49bbdffdc394f3c9253bdc778f38d5ba15" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mtplot" path="src/platform/mtplot" revision="5e4f631e633384751f582bd9db5f4d6eb2112494" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/mttools" path="src/platform/mttools" revision="0d2d0c4445ac6f9233aa4e297e0d2c031469225b" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/newblue" path="src/platform/newblue" revision="57a4a9133dd2b5ecc87eeb2c2519de33c71005b1" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/punybench" path="src/platform/punybench" revision="c050715684a5dde3a4fc818f3de816a407fdb2de" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/system_api" path="src/platform/system_api" revision="ae8d0e90949f1429af9d48235f06bece7ab805d5" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/tast" path="src/platform/tast" revision="e14825680ed4851058cdc0a6455435d2b4643ba6" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/tast-tests" path="src/platform/tast-tests" revision="614b78bd30d90762b0565236c8632af3f9c13571" 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_noise_filter" path="src/platform/touch_noise_filter" revision="f1eb895f7ea70ad99bbe60508fda825923c35af6" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/touch_updater" path="src/platform/touch_updater" revision="a4eca6b5591a14c9a5e5c2c371daffe18f190cc0" 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="ba07736e4444b0d2c265f2e72dff9d3c7e0f0baa" 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="066c7f963b3ef733716251b666e0af0afd03b4fe" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/uboot-env" path="src/platform/uboot-env" revision="108ebbfac4d13d11e1940216434c368384ee0c0b" upstream="refs/heads/master"/> |
| <project groups="firmware,buildtools" name="chromiumos/platform/vboot_reference" path="src/platform/vboot_reference" revision="2c3d2c17ee9b379c4e076eaa574ffb671b7e4cb5" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/vpd" path="src/platform/vpd" revision="1c1806d8df4bb5976eed71a2e2bf156c36ccdce2" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/webplot" path="src/platform/webplot" revision="bbd5ea22ef9f8e109e363b26958d9a2fc8921f0f" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/xf86-input-cmt" path="src/platform/xf86-input-cmt" revision="3f2ffc921952e57a4343463b0679d90b80b51fc7" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform/xorg-conf" path="src/platform/xorg-conf" revision="df7bb0d01d48578d1c123327540615e072d2885c" upstream="refs/heads/master"/> |
| <project name="chromiumos/platform2" path="src/platform2" revision="0721e6874fe6fa422dc97c48224ab4c751afa0c8" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,buildtools,labtools" name="chromiumos/repohooks" path="src/repohooks" revision="6850d51607dc09c3c390bf3a5a0ed7acb20d61b9" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/adhd" path="src/third_party/adhd" revision="b17de17308e8bd129d0dbecab71fb14aee405eac" 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="10787b0519afce1e887a935789b2d624849856a9" 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="d14112f44bd81eb3a9f62ccad2ec3b74e07db25d" upstream="refs/heads/master"/> |
| <project groups="buildtools,labtools,devserver" name="chromiumos/third_party/autotest" path="src/third_party/autotest/files" revision="69f63c1c2c54b9e8de3a96aa5612baf7781a2f23" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/aver-updater" path="src/third_party/aver-updater" revision="c2dc0bdb6d5b2ded5c4233aa62e92e2ad415e9f9" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/bluez" path="src/third_party/bluez" revision="e18ea6f3bbf8dfc93b2ab6f7a5a6c73de9d5695c" upstream="refs/heads/chromeos-5.44"/> |
| <project groups="firmware" name="chromiumos/third_party/bootstub" path="src/third_party/bootstub" revision="5ac54e8d3d305c2c6c7297e8e54d3cf7e4629b29" 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="f716c3b772192dc892e5cda616222b09638f7e1c" upstream="refs/heads/chromeos-2016.05"/> |
| <project groups="firmware" name="chromiumos/third_party/coreboot/blobs" path="src/third_party/coreboot/3rdparty/blobs" revision="8e9f99b3e60d0ffe8b67cc93ea4ab1b9ed191e45" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/cros-adapta" path="src/third_party/cros-adapta" revision="afaffa715a920d53051768321ac37b0642c8bda3" 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/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="minilayout,firmware,buildtools" name="chromiumos/third_party/dpkt" path="chromite/third_party/dpkt" revision="f5259728b1294412bee945df9708efba09ea9160"> |
| <annotation name="branch-mode" value="pin"/> |
| </project> |
| <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/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="800865f86cd84c60484a93d3500f3da7d2f87ff0" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/gcc" path="src/third_party/gcc" revision="a2bc87ab8851051e765d60626a6997f63ddfe00e" upstream="refs/heads/master"/> |
| <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 name="chromiumos/third_party/grub2" path="src/third_party/grub2" revision="df6034c59cb2d847f9e780cf2def30c5c9b8305f" upstream="refs/heads/master"/> |
| <project groups="labtools" name="chromiumos/third_party/hdctools" path="src/third_party/hdctools" revision="59147b3e200e59a4410f8f5399ee65c482cb12e6" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/hostap" path="src/third_party/wpa_supplicant" revision="156cbc7f2f7526747e595497639880c7e3218184" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/hostap" path="src/third_party/wpa_supplicant-2.6" revision="102e08459ab87fad8ac3d92ae02f52d07952f543" upstream="refs/heads/wpa_supplicant-2.6"/> |
| <project name="chromiumos/third_party/huddly-updater" path="src/third_party/huddly-updater" revision="eeb79ce39812a393bba8c5e888e3c25f4b30334d" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.8" revision="e312f8a99312741898d721dd4d6c8f579498dd28" upstream="refs/heads/chromeos-3.8"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.10" revision="c94cba83c74a0aedbc764a83e6b24515e2b5dbc5" upstream="refs/heads/chromeos-3.10"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.14" revision="997a86aa2ce44b746c3214f6952ac6ac44debc58" upstream="refs/heads/chromeos-3.14"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v3.18" revision="acf94392fbb4db8c36176723b372700f1c38d555" upstream="refs/heads/chromeos-3.18"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v4.4" revision="7fa1c9e5ee7fa66a8a2f46044c2e1715c2b13d0a" upstream="refs/heads/chromeos-4.4"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/v4.14" revision="7fa27ecb1b04b99f60b671a3c61e58f4fc987e8b" upstream="refs/heads/chromeos-4.14"/> |
| <project name="chromiumos/third_party/kernel" path="src/third_party/kernel/experimental" revision="c70caee3e6bff5abbecd4ebc694d5bb5ed6ebd5a" upstream="refs/heads/next/chromeos-experimental"/> |
| <project name="chromiumos/third_party/khronos" path="src/third_party/khronos" revision="f427d0ac31d1878a6e2c9209f63a8f560983b6bf" 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="0061b1f244574e615c415479725046ab2951f09a" upstream="refs/heads/chromeos-2.4.89"/> |
| <project name="chromiumos/third_party/libmbim" path="src/third_party/libmbim" revision="b7036f2f9a196a272f5d4f341ddf84483979d7e1" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libqmi" path="src/third_party/libqmi" revision="ca47222f26c082e0caa80c9f221fcad8b48c6360" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libqrtr" path="src/third_party/libqrtr" revision="238c066146896e9caa9e724ce43080d07ac4fb3f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/libresample" path="src/third_party/libresample" revision="cc9f20f439396b7d45e94b8301edd95d33f26a46" 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="609671ec2166055d21e579af75e214a8b4c4cae0" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/logitech-updater" path="src/third_party/logitech-updater" revision="d08fba1244f890cbbddefe645505fd8f21b84d8f" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/ltp" path="src/third_party/ltp" revision="7df860dd2389c5c9a5b2ed9ac8a7f1d48d6fed03" 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/memtest" path="src/third_party/memtest" revision="3d4be6e3bfd819856e38a82e35c206fec4551851" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/arc-mesa" revision="202b321335e7d1e751268f8f26895a9b14bf8858" upstream="refs/heads/arc-17.3"/> |
| <project name="chromiumos/third_party/mesa" path="src/third_party/mesa" revision="a2e9d9b4c199ff1b53a625a345e566200016e2d9" 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="bcc3e2e4246431be511be3959a11cd9733bedd29" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/modemmanager-next" path="src/third_party/modemmanager-next" revision="f64d6a2d27be8898a7333022de3abe72e869aa98" 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="b6da57f1a32837dc71787f1c5d0adba1ea3acb32" 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="fc570685c1ca4acb871c706a66d0493b5e92c7c9" 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/tegra-power-query" path="src/third_party/tegra-power-query" revision="66f1f0d949f4ca4836c1a65b622629205240e37a" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tegrastats" path="src/third_party/tegrastats" revision="1be161a89525d840e1f6d1f21b3f45645a7dedb3" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/tlsdate" path="src/third_party/tlsdate" revision="b9acd27dcfdf2e54d8bc1a61c223ed8e1f8452eb" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/toolchain-utils" path="src/third_party/toolchain-utils" revision="e2a920a2de9c03553db50be9484ca802d0a80dae" 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="f5ddef5e9eb5b41686468053871b5c3dfdd16627" upstream="refs/heads/master"/> |
| <project name="chromiumos/third_party/trousers" path="src/third_party/trousers" revision="d7fa9879234533afab08f137e0f1efc36a5c17b9" 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/u-boot" path="src/third_party/u-boot/next" revision="23d97f8348d640504a58ddf40e9c0ef211be6f1b" upstream="refs/heads/chromeos-v2015.07-rc1"/> |
| <project name="chromiumos/third_party/webrtc-apm" path="src/third_party/webrtc-apm" revision="c547affa46e1843508f05eda548178cb22057108" 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="60300eb6e150d1095fb01fe186f9e1bf65337905" upstream="refs/heads/master"/> |
| <project groups="minilayout,firmware,buildtools,chromeos-admin" name="external/swarming.client" path="chromite/third_party/swarming.client" remote="chromium" revision="715861067a7cc8d20d2d629b6d76d796c004feb4"/> |
| <project name="linux-syscall-support" path="src/third_party/breakpad/src/third_party/lss" revision="e6527b0cd469e3ff5764785dadcb39bf7d787154"/> |
| <project name="platform/external/bsdiff" path="src/aosp/external/bsdiff" remote="aosp" revision="c82a7587b850ae43ba4bdb1d317e697642896215" upstream="refs/heads/master"/> |
| <project name="platform/external/libcxx" path="src/aosp/external/libcxx" remote="aosp" revision="bfb1424a250f9a28c9a6033bd6c7f62579e7228d" upstream="refs/heads/master"/> |
| <project name="platform/external/libcxxabi" path="src/aosp/external/libcxxabi" remote="aosp" revision="1607e38f339e32d6bcf7bb02531d3bf19f42f5c0" 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="2dd29ac655fd62d8ba81208a6d14fd16cfcbbc0c" upstream="refs/heads/master"/> |
| <project name="platform/external/minijail" path="src/aosp/external/minijail" remote="aosp" revision="2892c1dedf860cfde2a0d72f4af4ed57bfa03fb3" upstream="refs/heads/master"/> |
| <project name="platform/external/puffin" path="src/aosp/external/puffin" remote="aosp" revision="7c4c62ba3dfbd220efd6dd78eebfd13a189ed95d" upstream="refs/heads/master"/> |
| <project name="toolchain/binutils" path="src/aosp/toolchain/binutils" remote="aosp" revision="b415c49e4c4b8fcddc1f5551bb1e357a8fe93ad7"/> |
| <project name="toolchain/gcc" path="src/aosp/toolchain/gcc" remote="aosp" revision="71959ce8f47f676a26bb21da7117101d9d73867e"/> |
| <project name="weave/libweave" path="src/weave/libweave" revision="682a416bd5fe6bb88e267b312bddb786588bdebe" upstream="refs/heads/master"/> |
| <repo-hooks enabled-list="pre-upload" in-project="chromiumos/repohooks"/> |
| <pending_commit branch="master" change_id="I2fdd6bf6ec3d42c4f694e90a7506b2664e20fffc" commit="278210b7b7f11da359b9beb9997fe11cb66977fc" commit_message="Add aver-updater to manifest A public repo was created for Aver VC520 firmware updater. Adding it to external manifest. BUG=chromium:844503 TEST=none Change-Id: I2fdd6bf6ec3d42c4f694e90a7506b2664e20fffc Reviewed-on: https://chromium-review.googlesource.com/1069296 Commit-Ready: Zhongze Hu <frankhu@google.com> Tested-by: Zhongze Hu <frankhu@google.com> Reviewed-by: Bernie Thompson <bhthompson@chromium.org> " fail_count="0" gerrit_number="1069296" owner_email="frankhu@google.com" pass_count="0" patch_number="1" project="chromiumos/manifest" project_url="https://chromium-review.googlesource.com/chromiumos/manifest" ref="refs/changes/96/1069296/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I7bdc17bd40328dcc5a7872763350bbbf8dceac2c" commit="73599da9512e0ca4e7e87c1320eeee17accf932a" commit_message="UPSTREAM: x86_64, switch_to(): Load TLS descriptors before switching DS and ES commit f647d7c155f069c1a068030255c300663516420e upstream. Otherwise, if buggy user code points DS or ES into the TLS array, they would be corrupted after a context switch. This also significantly improves the comments and documents some gotchas in the code. Before this patch, the both tests below failed. With this patch, the es test passes, although the gsbase test still fails. ----- begin es test ----- /* * Copyright (c) 2014 Andy Lutomirski * GPL v2 */ static unsigned short GDT3(int idx) { return (idx << 3) | 3; } static int create_tls(int idx, unsigned int base) { struct user_desc desc = { .entry_number = idx, .base_addr = base, .limit = 0xfffff, .seg_32bit = 1, .contents = 0, /* Data, grow-up */ .read_exec_only = 0, .limit_in_pages = 1, .seg_not_present = 0, .useable = 0, }; if (syscall(SYS_set_thread_area, &desc) != 0) err(1, "set_thread_area"); return desc.entry_number; } int main() { int idx = create_tls(-1, 0); printf("Allocated GDT index %d\n", idx); unsigned short orig_es; asm volatile ("mov %%es,%0" : "=rm" (orig_es)); int errors = 0; int total = 1000; for (int i = 0; i < total; i++) { asm volatile ("mov %0,%%es" : : "rm" (GDT3(idx))); usleep(100); unsigned short es; asm volatile ("mov %%es,%0" : "=rm" (es)); asm volatile ("mov %0,%%es" : : "rm" (orig_es)); if (es != GDT3(idx)) { if (errors == 0) printf("[FAIL]\tES changed from 0x%hx to 0x%hx\n", GDT3(idx), es); errors++; } } if (errors) { printf("[FAIL]\tES was corrupted %d/%d times\n", errors, total); return 1; } else { printf("[OK]\tES was preserved\n"); return 0; } } ----- end es test ----- ----- begin gsbase test ----- /* * gsbase.c, a gsbase test * Copyright (c) 2014 Andy Lutomirski * GPL v2 */ static unsigned char *testptr, *testptr2; static unsigned char read_gs_testvals(void) { unsigned char ret; asm volatile ("movb %%gs:%1, %0" : "=r" (ret) : "m" (*testptr)); return ret; } int main() { int errors = 0; testptr = mmap((void *)0x200000000UL, 1, PROT_READ | PROT_WRITE, MAP_PRIVATE | MAP_FIXED | MAP_ANONYMOUS, -1, 0); if (testptr == MAP_FAILED) err(1, "mmap"); testptr2 = mmap((void *)0x300000000UL, 1, PROT_READ | PROT_WRITE, MAP_PRIVATE | MAP_FIXED | MAP_ANONYMOUS, -1, 0); if (testptr2 == MAP_FAILED) err(1, "mmap"); *testptr = 0; *testptr2 = 1; if (syscall(SYS_arch_prctl, ARCH_SET_GS, (unsigned long)testptr2 - (unsigned long)testptr) != 0) err(1, "ARCH_SET_GS"); usleep(100); if (read_gs_testvals() == 1) { printf("[OK]\tARCH_SET_GS worked\n"); } else { printf("[FAIL]\tARCH_SET_GS failed\n"); errors++; } asm volatile ("mov %0,%%gs" : : "r" (0)); if (read_gs_testvals() == 0) { printf("[OK]\tWriting 0 to gs worked\n"); } else { printf("[FAIL]\tWriting 0 to gs failed\n"); errors++; } usleep(100); if (read_gs_testvals() == 0) { printf("[OK]\tgsbase is still zero\n"); } else { printf("[FAIL]\tgsbase was corrupted\n"); errors++; } return errors == 0 ? 0 : 1; } ----- end gsbase test ----- BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I7bdc17bd40328dcc5a7872763350bbbf8dceac2c Signed-off-by: Andy Lutomirski <luto@amacapital.net> Cc: Andi Kleen <andi@firstfloor.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Link: http://lkml.kernel.org/r/509d27c9fec78217691c3dad91cec87e1006b34a.1418075657.git.luto@amacapital.net Signed-off-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit a1f3f3d87a0bd360dfbb9642dffadcc8e2f1de3a in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068275 " fail_count="0" gerrit_number="1068275" owner_email="sonnyrao@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/75/1068275/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I6b2b1c39ac14a87b6ad714c021eab27ccc838272" commit="bce554dd1b7bf291217ced8594f41c8529bf00f4" commit_message="UPSTREAM: x86, kvm: Clear paravirt_enabled on KVM guests for espfix32's benefit commit 29fa6825463c97e5157284db80107d1bfac5d77b upstream. paravirt_enabled has the following effects: - Disables the F00F bug workaround warning. There is no F00F bug workaround any more because Linux's standard IDT handling already works around the F00F bug, but the warning still exists. This is only cosmetic, and, in any event, there is no such thing as KVM on a CPU with the F00F bug. - Disables 32-bit APM BIOS detection. On a KVM paravirt system, there should be no APM BIOS anyway. - Disables tboot. I think that the tboot code should check the CPUID hypervisor bit directly if it matters. - paravirt_enabled disables espfix32. espfix32 should *not* be disabled under KVM paravirt. The last point is the purpose of this patch. It fixes a leak of the high 16 bits of the kernel stack address on 32-bit KVM paravirt guests. Fixes CVE-2014-8134. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I6b2b1c39ac14a87b6ad714c021eab27ccc838272 Suggested-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Signed-off-by: Andy Lutomirski <luto@amacapital.net> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit ead468da1150996a29e6c565db3c5cad79e5e4b1 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068276 " fail_count="0" gerrit_number="1068276" owner_email="sonnyrao@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/76/1068276/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ica59bb3a11ae1a48b4313aeab98ee5cd59edc978" commit="b4e42943598dcdc828bca7feaf848f14229c9960" commit_message="UPSTREAM: x86/asm/traps: Disable tracing and kprobes in fixup_bad_iret and sync_regs commit 7ddc6a2199f1da405a2fb68c40db8899b1a8cd87 upstream. These functions can be executed on the int3 stack, so kprobes are dangerous. Tracing is probably a bad idea, too. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: Ica59bb3a11ae1a48b4313aeab98ee5cd59edc978 Fixes: b645af2d5905 ("x86_64, traps: Rework bad_iret") Signed-off-by: Andy Lutomirski <luto@amacapital.net> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Steven Rostedt <rostedt@goodmis.org> Link: http://lkml.kernel.org/r/50e33d26adca60816f3ba968875801652507d0c4.1416870125.git.luto@amacapital.net Signed-off-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit afe83db5ddb73ffafb4669dfa2e1a3c3ad960155 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068317 " fail_count="0" gerrit_number="1068317" owner_email="sonnyrao@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/17/1068317/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I2d060a9160b09506e07a92e69e417cfaceaafb53" commit="4098928296293cd6b7d7fe67b9a46784ea0fd968" commit_message="UPSTREAM: x86, microcode, AMD: Do not use smp_processor_id() in preemtible context commit 2ef84b3bb97f03332f0c1edb4466b1750dcf97b5 upstream. Hand down the cpu number instead, otherwise lockdep screams when doing echo 1 > /sys/devices/system/cpu/microcode/reload. BUG: using smp_processor_id() in preemptible [00000000] code: amd64-microcode/2470 caller is debug_smp_processor_id+0x12/0x20 CPU: 1 PID: 2470 Comm: amd64-microcode Not tainted 3.18.0-rc6+ #26 ... BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I2d060a9160b09506e07a92e69e417cfaceaafb53 Signed-off-by: Borislav Petkov <bp@suse.de> Link: http://lkml.kernel.org/r/1417428741-4501-1-git-send-email-bp@alien8.de Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 6a76bc2d9e7a1d5184692f5dc9c2c183d65f53e4 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068318 " fail_count="0" gerrit_number="1068318" owner_email="sonnyrao@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/18/1068318/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Id03051c291bdebd652d7b8997ba1fe99583beba4" commit="99756ed4b18b4a652383005075d80cb8511b1bfe" commit_message="UPSTREAM: x86, microcode, intel: Drop unused parameter commit 47768626c6db42cd06ff077ba12dd2cb10ab818b upstream. apply_microcode_early() doesn't use mc_saved_data, kill it. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: Id03051c291bdebd652d7b8997ba1fe99583beba4 Signed-off-by: Borislav Petkov <bp@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 97d0906a8988184ebabe8e5836c00ce77f8d2284 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068319 " fail_count="0" gerrit_number="1068319" owner_email="sonnyrao@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/19/1068319/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="If9817421f2819e5f73082b1f30205569988e8ee5" commit="ed53aff69176a0d594ddc2738a52048ed1c7864e" commit_message="UPSTREAM: x86, microcode: Don't initialize microcode code on paravirt commit a18a0f6850d4b286a5ebf02cd5b22fe496b86349 upstream. Paravirtual guests are not expected to load microcode into processors and therefore it is not necessary to initialize microcode loading logic. In fact, under certain circumstances initializing this logic may cause the guest to crash. Specifically, 32-bit kernels use __pa_nodebug() macro which does not work in Xen (the code path that leads to this macro happens during resume when we call mc_bp_resume()->load_ucode_ap() ->check_loader_disabled_ap()) BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: If9817421f2819e5f73082b1f30205569988e8ee5 Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com> Link: http://lkml.kernel.org/r/1417469264-31470-1-git-send-email-boris.ostrovsky@oracle.com Signed-off-by: Borislav Petkov <bp@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 44c4db3ab0378564d40f9b6aafd12908cdcb97ca in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068320 " fail_count="0" gerrit_number="1068320" owner_email="sonnyrao@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/20/1068320/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I9ec644a8b9b93da96091f400c23ffff37359796d" commit="76069bfe7fbf51df62d8885101e0b8c9c52168f7" commit_message="UPSTREAM: x86, microcode: Reload microcode on resume commit fbae4ba8c4a387e306adc9c710e5c225cece7678 upstream. Normally, we do reapply microcode on resume. However, in the cases where that microcode comes from the early loader and the late loader hasn't been utilized yet, there's no easy way for us to go and apply the patch applied during boot by the early loader. Thus, reuse the patch stashed by the early loader for the BSP. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I9ec644a8b9b93da96091f400c23ffff37359796d Signed-off-by: Borislav Petkov <bp@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit d239198442d300710a2389449a583edbcfb68581 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068321 " fail_count="0" gerrit_number="1068321" owner_email="sonnyrao@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/21/1068321/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I01cd632b25d8526ce694f48ae8cfe270c87a4f2a" commit="fd9f6f0da26622651f93f64f5cac1c4a351005ae" commit_message="UPSTREAM: x86/microcode/intel: Fish out the stashed microcode for the BSP commit 25cdb9c86826f8d035d8aaa07fc36832e76bd8a0 upstream. I'm such a moron! The simple solution of saving the BSP patch for use on resume was too simple (and wrong!), hint: sizeof(struct microcode_intel). What needs to be done instead is to fish out the microcode patch we have stashed previously and apply that on the BSP in case the late loader hasn't been utilized. So do that instead. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I01cd632b25d8526ce694f48ae8cfe270c87a4f2a Signed-off-by: Borislav Petkov <bp@suse.de> Cc: Linus Torvalds <torvalds@linux-foundation.org> Link: http://lkml.kernel.org/r/20141208110820.GB20057@pd.tnic Signed-off-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit f3d4175f055094fca46a81d0066c692c8a7a7bd5 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068322 " fail_count="0" gerrit_number="1068322" owner_email="sonnyrao@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/22/1068322/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Id38c82a6b9c22eb97bd536deb5dc53f8fea8fd67" commit="28e402cbaaf8a6d5b8471a45581d274527a10d8f" commit_message="UPSTREAM: x86: export get_xsave_addr commit ba7b39203a3a18018173b87e73f27169bd8e5147 upstream. get_xsave_addr is the API to access XSAVE states, and KVM would like to use it. Export it. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: Id38c82a6b9c22eb97bd536deb5dc53f8fea8fd67 Cc: x86@kernel.org Cc: H. Peter Anvin <hpa@linux.intel.com> Acked-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 1f92632c5b225e5e85ae32f3276676feaaef259b in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068323 " fail_count="0" gerrit_number="1068323" owner_email="sonnyrao@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/23/1068323/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I440bba066c6cccf7da838d1303a71b5bebef3cbc" commit="7bf4764e9fa48540c079be5093bef01d7312bc92" commit_message="UPSTREAM: KVM: x86: support XSAVES usage in the host commit df1daba7d1cb8ed7957f873cde5c9e953cbaa483 upstream. Userspace is expecting non-compacted format for KVM_GET_XSAVE, but struct xsave_struct might be using the compacted format. Convert in order to preserve userspace ABI. Likewise, userspace is passing non-compacted format for KVM_SET_XSAVE but the kernel will pass it to XRSTORS, and we need to convert back. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I440bba066c6cccf7da838d1303a71b5bebef3cbc Fixes: f31a9f7c71691569359fa7fb8b0acaa44bce0324 Cc: Fenghua Yu <fenghua.yu@intel.com> Cc: H. Peter Anvin <hpa@linux.intel.com> Tested-by: Nadav Amit <namit@cs.technion.ac.il> Reviewed-by: Radim Krm <rkrcmar@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit c4a525417ca4a0be15208b28f3c7d90eeb79beaa in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068324 " fail_count="0" gerrit_number="1068324" owner_email="sonnyrao@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/24/1068324/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I6b73591e36733afd6ef81133d5bb80ae80e2c803" commit="ecb510d065f6ebeae0b0c66d4c71462ad400461a" commit_message="UPSTREAM: KVM: x86: em_ret_far overrides cpl commit ab646f54f4fd1a8b9671b8707f0739fdd28ce2b1 upstream. commit d50eaa18039b ("KVM: x86: Perform limit checks when assigning EIP") mistakenly used zero as cpl on em_ret_far. Use the actual one. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I6b73591e36733afd6ef81133d5bb80ae80e2c803 Fixes: d50eaa18039b8b848c2285478d0775335ad5e930 Signed-off-by: Nadav Amit <namit@cs.technion.ac.il> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 09e365b46c716bcfd4890ee4c9fb85adc730990b in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068325 " fail_count="0" gerrit_number="1068325" owner_email="sonnyrao@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/25/1068325/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I93ace9b3056fe11e9248211fc03c702407e005c9" commit="f8d454f3ff37110c69e21575d23220bcc72e2f0d" commit_message="UPSTREAM: kvm: x86: mask out XSAVES commit b65d6e17fe2239c9b2051727903955d922083fbf upstream. This feature is not supported inside KVM guests yet, because we do not emulate MSR_IA32_XSS. Mask it out. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I93ace9b3056fe11e9248211fc03c702407e005c9 Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit d3105d563783081ccb90e384af574fe718470067 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068326 " fail_count="0" gerrit_number="1068326" owner_email="sonnyrao@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/26/1068326/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ia7769a8722b821039ba960fd7174bb82e5ab6f1b" commit="290cb8194cd1e0e96dc4c383c6fa9d4f70c94aea" commit_message="UPSTREAM: kvm: x86: drop severity of "generation wraparound" message commit a629df7eadffb03e6ce4a8616e62ea29fdf69b6b upstream. Since most virtual machines raise this message once, it is a bit annoying. Make it KERN_DEBUG severity. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: Ia7769a8722b821039ba960fd7174bb82e5ab6f1b Fixes: 7a2e8aaf0f6873b47bc2347f216ea5b0e4c258ab Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 032e45d8b7f43d83b46dfa94910fb620e41b735f in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068327 " fail_count="0" gerrit_number="1068327" owner_email="sonnyrao@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/27/1068327/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I8daf4db657380da52bfb01be25c79da8ae897480" commit="86379d166e86a140bc3648ab7d80582eb31eefe4" commit_message="UPSTREAM: x86, vdso: Use asm volatile in __getcpu commit 1ddf0b1b11aa8a90cef6706e935fc31c75c406ba upstream. In Linux 3.18 and below, GCC hoists the lsl instructions in the pvclock code all the way to the beginning of __vdso_clock_gettime, slowing the non-paravirt case significantly. For unknown reasons, presumably related to the removal of a branch, the performance issue is gone as of e76b027e6408 x86,vdso: Use LSL unconditionally for vgetcpu but I don't trust GCC enough to expect the problem to stay fixed. There should be no correctness issue, because the __getcpu calls in __vdso_vlock_gettime were never necessary in the first place. Note to stable maintainers: In 3.18 and below, depending on configuration, gcc 4.9.2 generates code like this: 9c3: 44 0f 03 e8 lsl %ax,%r13d 9c7: 45 89 eb mov %r13d,%r11d 9ca: 0f 03 d8 lsl %ax,%ebx This patch won't apply as is to any released kernel, but I'll send a trivial backported version if needed. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host [ Backported by Andy Lutomirski. Should apply to all affected versions. This fixes a functionality bug as well as a performance bug: buggy kernels can infinite loop in __vdso_clock_gettime on affected compilers. See, for exammple: https://bugzilla.redhat.com/show_bug.cgi?id=1178975 ] Change-Id: I8daf4db657380da52bfb01be25c79da8ae897480 Fixes: 51c19b4f5927 x86: vdso: pvclock gettime support Cc: Marcelo Tosatti <mtosatti@redhat.com> Acked-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Andy Lutomirski <luto@amacapital.net> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit ccf8296923d31dd16e9b8857213fa671d1252bb1 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068328 " fail_count="0" gerrit_number="1068328" owner_email="sonnyrao@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/28/1068328/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I3e7baed4cb22ebba057a6bdf255964f0c1a9f10f" commit="16dd2d176158180043ff9fe15887e643c002f33e" commit_message="UPSTREAM: crypto: sha-mb - Add avx2_supported check. commit 0b8c960cf6defc56b3aa1a71b5af95872b6dff2b upstream. This patch fixes this allyesconfig target build error with older binutils. LD arch/x86/crypto/built-in.o ld: arch/x86/crypto/sha-mb/built-in.o: No such file: No such file or directory BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I3e7baed4cb22ebba057a6bdf255964f0c1a9f10f Signed-off-by: Vinson Lee <vlee@twitter.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 553aeac6c8d9a30ce3f6572d194da42c4df6d933 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068329 " fail_count="0" gerrit_number="1068329" owner_email="sonnyrao@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/29/1068329/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I231afb9faddacc4e351454f489b77500438b9852" commit="f8575a828a10ea84c01f42ec0796695dcff031ca" commit_message="UPSTREAM: crypto: aesni - fix "by8" variant for 128 bit keys commit 0b1e95b2fa0934c3a08db483979c70d3b287f50e upstream. The "by8" counter mode optimization is broken for 128 bit keys with input data longer than 128 bytes. It uses the wrong key material for en- and decryption. The key registers xkey0, xkey4, xkey8 and xkey12 need to be preserved in case we're handling more than 128 bytes of input data -- they won't get reloaded after the initial load. They must therefore be (a) loaded on the first iteration and (b) be preserved for the latter ones. The implementation for 128 bit keys does not comply with (a) nor (b). Fix this by bringing the implementation back to its original source and correctly load the key registers and preserve their values by *not* re-using the registers for other purposes. Kudos to James for reporting the issue and providing a test case showing the discrepancies. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I231afb9faddacc4e351454f489b77500438b9852 Reported-by: James Yonan <james@openvpn.net> Cc: Chandramouli Narayanan <mouli@linux.intel.com> Signed-off-by: Mathias Krause <minipli@googlemail.com> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 087e791172c5df20d02c27de99ecba0efc7dc7ac in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068330 " fail_count="0" gerrit_number="1068330" owner_email="sonnyrao@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/30/1068330/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I90c90f2f72fce00efeedadcf93b5dca331c20999" commit="e7ca27cc852298b80ac31b9b0258a325269612ec" commit_message="UPSTREAM: perf/x86/intel/uncore: Make sure only uncore events are collected commit af91568e762d04931dcbdd6bef4655433d8b9418 upstream. The uncore_collect_events functions assumes that event group might contain only uncore events which is wrong, because it might contain any type of events. This bug leads to uncore framework touching 'not' uncore events, which could end up all sorts of bugs. One was triggered by Vince's perf fuzzer, when the uncore code touched breakpoint event private event space as if it was uncore event and caused BUG: BUG: unable to handle kernel paging request at ffffffff82822068 IP: [<ffffffff81020338>] uncore_assign_events+0x188/0x250 ... The code in uncore_assign_events() function was looking for event->hw.idx data while the event was initialized as a breakpoint with different members in event->hw union. This patch forces uncore_collect_events() to collect only uncore events. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I90c90f2f72fce00efeedadcf93b5dca331c20999 Reported-by: Vince Weaver <vince@deater.net> Signed-off-by: Jiri Olsa <jolsa@redhat.com> Cc: Arnaldo Carvalho de Melo <acme@redhat.com> Cc: Frederic Weisbecker <fweisbec@gmail.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Stephane Eranian <eranian@google.com> Cc: Yan, Zheng <zheng.z.yan@intel.com> Link: http://lkml.kernel.org/r/1418243031-20367-2-git-send-email-jolsa@kernel.org Signed-off-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 8fa60ccc1cee10853e941a75c4359f9265ae0b59 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068331 " fail_count="0" gerrit_number="1068331" owner_email="sonnyrao@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/31/1068331/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I78e1c4829a02af535e6c9e9da8066896d2b2e50b" commit="b8b051368b4f28e938beb58aba863693f879e943" commit_message="UPSTREAM: perf/x86/uncore/hsw-ep: Handle systems with only two SBOXes commit 5306c31c5733cb4a79cc002e0c3ad256fd439614 upstream. There was another report of a boot failure with a #GP fault in the uncore SBOX initialization. The earlier work around was not enough for this system. The boot was failing while trying to initialize the third SBOX. This patch detects parts with only two SBOXes and limits the number of SBOX units to two there. Stable material, as it affects boot problems on 3.18. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I78e1c4829a02af535e6c9e9da8066896d2b2e50b Tested-by: Andreas Oehler <andreas@oehler-net.de> Signed-off-by: Andi Kleen <ak@linux.intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Arnaldo Carvalho de Melo <acme@kernel.org> Cc: Stephane Eranian <eranian@google.com> Cc: Yan, Zheng <zheng.z.yan@intel.com> Link: http://lkml.kernel.org/r/1420583675-9163-1-git-send-email-andi@firstfloor.org Signed-off-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 7f5dada0d5890fd3c4eee140f9489ef32f1a3ae6 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068332 " fail_count="0" gerrit_number="1068332" owner_email="sonnyrao@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/32/1068332/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I6a2c350f658b289957434cb0f4c812ebb63c5d8c" commit="9e66b54c3b26c7c45f45d6870cc4ce048dbae492" commit_message="UPSTREAM: x86/build: Clean auto-generated processor feature files commit 280dbc572357eb50184663fc9e4aaf09c8141e9b upstream. Commit 9def39be4e96 ("x86: Support compiling out human-friendly processor feature names") made two source file targets conditional. Such conditional targets will not be cleaned automatically by make mrproper. Fix by adding explicit clean-files targets for the two files. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I6a2c350f658b289957434cb0f4c812ebb63c5d8c Fixes: 9def39be4e96 ("x86: Support compiling out human-friendly processor feature names") Signed-off-by: Bjrn Mork <bjorn@mork.no> Cc: Josh Triplett <josh@joshtriplett.org> Link: http://lkml.kernel.org/r/1419335863-10608-1-git-send-email-bjorn@mork.no Signed-off-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit bf80baa10a012b3e1b86833f0b5e7cdefe7cbf6b in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068333 " fail_count="0" gerrit_number="1068333" owner_email="sonnyrao@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/33/1068333/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I4c3c8167ea92e10cb6e3f5e3ee56edbfc0dd3e5c" commit="bc62937df2bfdf7c63177faae8280dcf11ebfc19" commit_message="UPSTREAM: ftrace/jprobes/x86: Fix conflict between jprobes and function graph tracing commit 237d28db036e411f22c03cfd5b0f6dc2aa9bf3bc upstream. If the function graph tracer traces a jprobe callback, the system will crash. This can easily be demonstrated by compiling the jprobe sample module that is in the kernel tree, loading it and running the function graph tracer. # modprobe jprobe_example.ko # echo function_graph > /sys/kernel/debug/tracing/current_tracer # ls The first two commands end up in a nice crash after the first fork. (do_fork has a jprobe attached to it, so "ls" just triggers that fork) The problem is caused by the jprobe_return() that all jprobe callbacks must end with. The way jprobes works is that the function a jprobe is attached to has a breakpoint placed at the start of it (or it uses ftrace if fentry is supported). The breakpoint handler (or ftrace callback) will copy the stack frame and change the ip address to return to the jprobe handler instead of the function. The jprobe handler must end with jprobe_return() which swaps the stack and does an int3 (breakpoint). This breakpoint handler will then put back the saved stack frame, simulate the instruction at the beginning of the function it added a breakpoint to, and then continue on. For function tracing to work, it hijakes the return address from the stack frame, and replaces it with a hook function that will trace the end of the call. This hook function will restore the return address of the function call. If the function tracer traces the jprobe handler, the hook function for that handler will not be called, and its saved return address will be used for the next function. This will result in a kernel crash. To solve this, pause function tracing before the jprobe handler is called and unpause it before it returns back to the function it probed. Some other updates: Used a variable "saved_sp" to hold kcb->jprobe_saved_sp. This makes the code look a bit cleaner and easier to understand (various tries to fix this bug required this change). Note, if fentry is being used, jprobes will change the ip address before the function graph tracer runs and it will not be able to trace the function that the jprobe is probing. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I4c3c8167ea92e10cb6e3f5e3ee56edbfc0dd3e5c Link: http://lkml.kernel.org/r/20150114154329.552437962@goodmis.org Acked-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 7769f8be6bd1715ddaa720539200a01bf4bdbe4e in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068334 " fail_count="0" gerrit_number="1068334" owner_email="sonnyrao@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/1068334/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I81379f26f335801ff7a00b8118589e857bcfc4df" commit="ecab4df5e645cae0b3e3b57781cf622649ed8a84" commit_message="UPSTREAM: x86, um: actually mark system call tables readonly commit b485342bd79af363c77ef1a421c4a0aef2de9812 upstream. Commit a074335a370e ("x86, um: Mark system call tables readonly") was supposed to mark the sys_call_table in UML as RO by adding the const, but it doesn't have the desired effect as it's nevertheless being placed into the data section since __cacheline_aligned enforces sys_call_table being placed into .data..cacheline_aligned instead. We need to use the ____cacheline_aligned version instead to fix this issue. Before: $ nm -v arch/x86/um/sys_call_table_64.o | grep -1 "sys_call_table" U sys_writev 0000000000000000 D sys_call_table 0000000000000000 D syscall_table_size After: $ nm -v arch/x86/um/sys_call_table_64.o | grep -1 "sys_call_table" U sys_writev 0000000000000000 R sys_call_table 0000000000000000 D syscall_table_size BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I81379f26f335801ff7a00b8118589e857bcfc4df Fixes: a074335a370e ("x86, um: Mark system call tables readonly") Cc: H. Peter Anvin <hpa@zytor.com> Cc: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Daniel Borkmann <dborkman@redhat.com> Signed-off-by: Richard Weinberger <richard@nod.at> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 51fbc0559758cc38fbb479640767234bb146e75c in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068335 " fail_count="0" gerrit_number="1068335" owner_email="sonnyrao@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/35/1068335/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I2704e005207cab09767567a13c7ecbd2f979a56e" commit="139b844bc8c83ac20b46eb413a318338527bc5b2" commit_message="UPSTREAM: KVM: nVMX: Disable unrestricted mode if ept=0 commit 78051e3b7e35722ad3f31dd611f1b34770bddab8 upstream. If L0 has disabled EPT, don't advertise unrestricted mode at all since it depends on EPT to run real mode code. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I2704e005207cab09767567a13c7ecbd2f979a56e Fixes: 92fbc7b195b824e201d9f06f2b93105f72384d65 Reviewed-by: Jan Kiszka <jan.kiszka@siemens.com> Signed-off-by: Bandan Das <bsd@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 0bcd13a05308afc6bb95479be9ca876e68f68951 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068336 " fail_count="0" gerrit_number="1068336" owner_email="sonnyrao@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/36/1068336/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I3fc375fa8ac04c8c060d10517d47e2dd28a8fb96" commit="c188ac8940296484731b5642cc7118ee0d1287e2" commit_message="UPSTREAM: x86, irq: Properly tag virtualization entry in /proc/interrupts commit 4a0d3107d6b19125f21172c2b7d95f9c30ecaf6f upstream. The mis-naming likely was a copy-and-paste effect. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I3fc375fa8ac04c8c060d10517d47e2dd28a8fb96 Signed-off-by: Jan Beulich <jbeulich@suse.com> Link: http://lkml.kernel.org/r/54B9408B0200007800055E8B@mail.emea.novell.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 89a2e6efe29a525665a94ace4a40bf2e6aa90885 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068337 " fail_count="0" gerrit_number="1068337" owner_email="sonnyrao@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/37/1068337/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ie381e13153325b8d401b43a4e6971c980a598c5f" commit="4047346d8dd72388a096f540742bc6239a338b56" commit_message="UPSTREAM: x86, hyperv: Mark the Hyper-V clocksource as being continuous commit 32c6590d126836a062b3140ed52d898507987017 upstream. The Hyper-V clocksource is continuous; mark it accordingly. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: Ie381e13153325b8d401b43a4e6971c980a598c5f Signed-off-by: K. Y. Srinivasan <kys@microsoft.com> Acked-by: jasowang@redhat.com Cc: gregkh@linuxfoundation.org Cc: devel@linuxdriverproject.org Cc: olaf@aepfle.de Cc: apw@canonical.com Link: http://lkml.kernel.org/r/1421108762-3331-1-git-send-email-kys@microsoft.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 246b625243c5e2889e97098662ec069f1ebcac9d in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068338 " fail_count="0" gerrit_number="1068338" owner_email="sonnyrao@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/38/1068338/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Id6bd83eabe66d1b226ff1415eda89e88fe7bb875" commit="c71c6b83600015f1368644f029b3cf4d2891f5d9" commit_message="UPSTREAM: x86/tsc: Change Fast TSC calibration failed from error to info commit 520452172e6b318f3a8bd9d4fe1e25066393de25 upstream. Many users see this message when booting without knowning that it is of no importance and that TSC calibration may have succeeded by another way. As explained by Paul Bolle in http://lkml.kernel.org/r/1348488259.1436.22.camel@x61.thuisdomein "Fast TSC calibration failed" should not be considered as an error since other calibration methods are being tried afterward. At most, those send a warning if they fail (not an error). So let's change the message from error to warning. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: Id6bd83eabe66d1b226ff1415eda89e88fe7bb875 [ tglx: Make if pr_info. It's really not important at all ] Fixes: c767a54ba065 x86/debug: Add KERN_<LEVEL> to bare printks, convert printks to pr_<level> Signed-off-by: Alexandre Demers <alexandre.f.demers@gmail.com> Link: http://lkml.kernel.org/r/1418106470-6906-1-git-send-email-alexandre.f.demers@gmail.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 056ad39c15c36bc5ce8ede2ae4db45b44181a6d4 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068339 " fail_count="0" gerrit_number="1068339" owner_email="sonnyrao@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/39/1068339/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I6dc28f26ac8bab892feb053be67a76712c189287" commit="aa4c8d0e34e502a3f78f15569a87bc0627c1276a" commit_message="UPSTREAM: x86, boot: Skip relocs when load address unchanged commit f285f4a21c3253887caceed493089ece17579d59 upstream. On 64-bit, relocation is not required unless the load address gets changed. Without this, relocations do unexpected things when the kernel is above 4G. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I6dc28f26ac8bab892feb053be67a76712c189287 Reported-by: Baoquan He <bhe@redhat.com> Signed-off-by: Kees Cook <keescook@chromium.org> Tested-by: Thomas D. <whissi@whissi.de> Cc: Vivek Goyal <vgoyal@redhat.com> Cc: Jan Beulich <JBeulich@suse.com> Cc: Junjie Mao <eternal.n08@gmail.com> Cc: Andi Kleen <ak@linux.intel.com> Link: http://lkml.kernel.org/r/20150116005146.GA4212@www.outflux.net Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit c546e47591d7c8b4fa3dc2d9dae14c127f0c3b22 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068340 " fail_count="0" gerrit_number="1068340" owner_email="sonnyrao@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/40/1068340/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I28c4347e0d5d198eee9bc241bd3b107f6afba2d2" commit="ba7c7cce23db785d737d01a28230c85f382dc22c" commit_message="UPSTREAM: KVM: x86: SYSENTER emulation is broken commit f3747379accba8e95d70cec0eae0582c8c182050 upstream. SYSENTER emulation is broken in several ways: 1. It misses the case of 16-bit code segments completely (CVE-2015-0239). 2. MSR_IA32_SYSENTER_CS is checked in 64-bit mode incorrectly (bits 0 and 1 can still be set without causing #GP). 3. MSR_IA32_SYSENTER_EIP and MSR_IA32_SYSENTER_ESP are not masked in legacy-mode. 4. There is some unneeded code. Fix it. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I28c4347e0d5d198eee9bc241bd3b107f6afba2d2 Signed-off-by: Nadav Amit <namit@cs.technion.ac.il> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit cb2567bf3eed3c7fe5fd914d827e3088d21e565f in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068341 " fail_count="0" gerrit_number="1068341" owner_email="sonnyrao@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/41/1068341/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ifb5f490288db2443f66e0637aebe3953bbdea757" commit="9d6c1260dc631b19334be41b55bd6d07a7764b8a" commit_message="UPSTREAM: KVM: x86: Fix of previously incomplete fix for CVE-2014-8480 commit 63ea0a49ae0b145b91ff2b070c01b66fc75854b9 upstream. STR and SLDT with rip-relative operand can cause a host kernel oops. Mark them as DstMem as well. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: Ifb5f490288db2443f66e0637aebe3953bbdea757 Signed-off-by: Nadav Amit <namit@cs.technion.ac.il> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit f84d9d8d9b3b03b4e449b7c40f99ddacb6d189ad in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068342 " fail_count="0" gerrit_number="1068342" owner_email="sonnyrao@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/1068342/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Iea8bbf69921861b6baaf44ed6eef3c9212f3974a" commit="479af323cfd21deb24890cf6c7b3c881aa1e7687" commit_message="UPSTREAM: x86, tls, ldt: Stop checking lm in LDT_empty commit e30ab185c490e9a9381385529e0fd32f0a399495 upstream. 32-bit programs don't have an lm bit in their ABI, so they can't reliably cause LDT_empty to return true without resorting to memset. They shouldn't need to do this. This should fix a longstanding, if minor, issue in all 64-bit kernels as well as a potential regression in the TLS hardening code. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: Iea8bbf69921861b6baaf44ed6eef3c9212f3974a Fixes: 41bdc78544b8 x86/tls: Validate TLS entries to protect espfix Signed-off-by: Andy Lutomirski <luto@amacapital.net> Cc: torvalds@linux-foundation.org Link: http://lkml.kernel.org/r/72a059de55e86ad5e2935c80aa91880ddf19d07c.1421954363.git.luto@amacapital.net Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit e3b3b6d580b073a5fbf9b74495a88eb9f69bb23c in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068343 " fail_count="0" gerrit_number="1068343" owner_email="sonnyrao@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/1068343/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="If5768271e6cb8cc834fcfa6f1dfde0f53d773259" commit="ee56757b4169808e96296f25133692731ba62f0e" commit_message="UPSTREAM: x86, tls: Interpret an all-zero struct user_desc as "no segment" commit 3669ef9fa7d35f573ec9c0e0341b29251c2734a7 upstream. The Witcher 2 did something like this to allocate a TLS segment index: struct user_desc u_info; bzero(&u_info, sizeof(u_info)); u_info.entry_number = (uint32_t)-1; syscall(SYS_set_thread_area, &u_info); Strictly speaking, this code was never correct. It should have set read_exec_only and seg_not_present to 1 to indicate that it wanted to find a free slot without putting anything there, or it should have put something sensible in the TLS slot if it wanted to allocate a TLS entry for real. The actual effect of this code was to allocate a bogus segment that could be used to exploit espfix. The set_thread_area hardening patches changed the behavior, causing set_thread_area to return -EINVAL and crashing the game. This changes set_thread_area to interpret this as a request to find a free slot and to leave it empty, which isn't *quite* what the game expects but should be close enough to keep it working. In particular, using the code above to allocate two segments will allocate the same segment both times. According to FrostbittenKing on Github, this fixes The Witcher 2. If this somehow still causes problems, we could instead allocate a limit==0 32-bit data segment, but that seems rather ugly to me. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: If5768271e6cb8cc834fcfa6f1dfde0f53d773259 Fixes: 41bdc78544b8 x86/tls: Validate TLS entries to protect espfix Signed-off-by: Andy Lutomirski <luto@amacapital.net> Cc: torvalds@linux-foundation.org Link: http://lkml.kernel.org/r/0cb251abe1ff0958b8e468a9a9a905b80ae3a746.1421954363.git.luto@amacapital.net Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 7b6b3d67f0d7d67426da74611698a74ffb33bea7 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068344 " fail_count="0" gerrit_number="1068344" owner_email="sonnyrao@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/1068344/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I18acaab78305420718960df2c9adf802c87ecb06" commit="2775e0752451b3bb4d6abd1b893ed1a27ace0ef3" commit_message="UPSTREAM: x86/apic: Re-enable PCI_MSI support for non-SMP X86_32 commit 38a1dfda8e77d7ba74c94d06d8bc41ba98a4bc8c upstream. Commit 0dbc6078c06bc0 ('x86, build, pci: Fix PCI_MSI build on !SMP') introduced the dependency that X86_UP_APIC is only available when PCI_MSI is false. This effectively prevents PCI_MSI support on 32bit UP systems because it disables both APIC and IO-APIC. But APIC support is architecturally required for PCI_MSI. The intention of the patch was to enforce APIC support when PCI_MSI is enabled, but failed to do so. Remove the !PCI_MSI dependency from X86_UP_APIC and enforce X86_UP_APIC when PCI_MSI support is enabled on 32bit UP systems. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I18acaab78305420718960df2c9adf802c87ecb06 [ tglx: Massaged changelog ] Fixes 0dbc6078c06bc0 'x86, build, pci: Fix PCI_MSI build on !SMP' Signed-off-by: Bryan O'Donoghue <pure.logic@nexus-software.ie> Suggested-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Link: http://lkml.kernel.org/r/1421967529-9037-1-git-send-email-pure.logic@nexus-software.ie Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 990785dcf5f47148bd92b312179be5e8404dd727 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068345 " fail_count="0" gerrit_number="1068345" owner_email="sonnyrao@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/45/1068345/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Iab33be49d060b3158c480018918ced4090f4d49c" commit="c841ef5399bf14bfcadb72d0558fb534d9a7c9bb" commit_message="UPSTREAM: x86, build: replace Perl script with Shell script commit d69911a68c865b152a067feaa45e98e6bb0f655b upstream. Commit e6023367d779 ("x86, kaslr: Prevent .bss from overlaping initrd") added Perl to the required build environment. This reimplements in shell the Perl script used to find the size of the kernel with bss and brk added. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: Iab33be49d060b3158c480018918ced4090f4d49c Signed-off-by: Kees Cook <keescook@chromium.org> Reported-by: Rob Landley <rob@landley.net> Acked-by: Rob Landley <rob@landley.net> Cc: Anca Emanuel <anca.emanuel@gmail.com> Cc: Fengguang Wu <fengguang.wu@intel.com> Cc: Junjie Mao <eternal.n08@gmail.com> Cc: Kees Cook <keescook@chromium.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: <stable@vger.kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 179ac907a28e4d890314757f921880121642e3e5 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068346 " fail_count="0" gerrit_number="1068346" owner_email="sonnyrao@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/1068346/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I5b460dc40d2fb3bced30dbc073b01916a9305202" commit="0346059132e8d46bf72b057021fd4c7b50c93ee6" commit_message="UPSTREAM: vm: add VM_FAULT_SIGSEGV handling support commit 33692f27597fcab536d7cbbcc8f52905133e4aa7 upstream. The core VM already knows about VM_FAULT_SIGBUS, but cannot return a "you should SIGSEGV" error, because the SIGSEGV case was generally handled by the caller - usually the architecture fault handler. That results in lots of duplication - all the architecture fault handlers end up doing very similar "look up vma, check permissions, do retries etc" - but it generally works. However, there are cases where the VM actually wants to SIGSEGV, and applications _expect_ SIGSEGV. In particular, when accessing the stack guard page, libsigsegv expects a SIGSEGV. And it usually got one, because the stack growth is handled by that duplicated architecture fault handler. However, when the generic VM layer started propagating the error return from the stack expansion in commit fee7e49d4514 ("mm: propagate error from stack expansion even for guard page"), that now exposed the existing VM_FAULT_SIGBUS result to user space. And user space really expected SIGSEGV, not SIGBUS. To fix that case, we need to add a VM_FAULT_SIGSEGV, and teach all those duplicate architecture fault handlers about it. They all already have the code to handle SIGSEGV, so it's about just tying that new return value to the existing code, but it's all a bit annoying. This is the mindless minimal patch to do this. A more extensive patch would be to try to gather up the mostly shared fault handling logic into one generic helper routine, and long-term we really should do that cleanup. Just from this patch, you can generally see that most architectures just copied (directly or indirectly) the old x86 way of doing things, but in the meantime that original x86 model has been improved to hold the VM semaphore for shorter times etc and to handle VM_FAULT_RETRY and other "newer" things, so it would be a good idea to bring all those improvements to the generic case and teach other architectures about them too. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I5b460dc40d2fb3bced30dbc073b01916a9305202 Reported-and-tested-by: Takashi Iwai <tiwai@suse.de> Tested-by: Jan Engelhardt <jengelh@inai.de> Acked-by: Heiko Carstens <heiko.carstens@de.ibm.com> # "s390 still compiles and boots" Cc: linux-arch@vger.kernel.org Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit da7f8de9647a8401c36e0bff69dfa58b066a4c47 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068347 " fail_count="0" gerrit_number="1068347" owner_email="sonnyrao@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/47/1068347/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Iacb294467034970c45d864bba72a60982f8aa8ac" commit="9d4c1cc90215c0fa54526f71a6ea8f6c566908a4" commit_message="UPSTREAM: xen/arm/arm64: introduce xen_arch_need_swiotlb commit a4dba130891271084344c12537731542ec77cb85 upstream. Introduce an arch specific function to find out whether a particular dma mapping operation needs to bounce on the swiotlb buffer. On ARM and ARM64, if the page involved is a foreign page and the device is not coherent, we need to bounce because at unmap time we cannot execute any required cache maintenance operations (we don't know how to find the pfn from the mfn). No change of behaviour for x86. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: Iacb294467034970c45d864bba72a60982f8aa8ac Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Reviewed-by: David Vrabel <david.vrabel@citrix.com> Reviewed-by: Catalin Marinas <catalin.marinas@arm.com> Acked-by: Ian Campbell <ian.campbell@citrix.com> Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit a6df13631781815752638547a49222610929f89e in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068348 " fail_count="0" gerrit_number="1068348" owner_email="sonnyrao@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/48/1068348/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I4016f66570e255aede687c727e8f938011247ddb" commit="ec6a40c4a5b7cca027cf3f4bfc25cd44cfb5800a" commit_message="UPSTREAM: PCI: Add NEC variants to Stratus ftServer PCIe DMI check commit 51ac3d2f0c505ca36ffc9715ffd518d756589ef8 upstream. NEC OEMs the same platforms as Stratus does, which have multiple devices on some PCIe buses under downstream ports. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I4016f66570e255aede687c727e8f938011247ddb Link: https://bugzilla.kernel.org/show_bug.cgi?id=51331 Fixes: 1278998f8ff6 ("PCI: Work around Stratus ftServer broken PCIe hierarchy (fix DMI check)") Signed-off-by: Charlotte Richardson <charlotte.richardson@stratus.com> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> CC: Myron Stowe <myron.stowe@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 42dcb705660528b22f6e071e8fdec2e5b7336b3c in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068349 " fail_count="0" gerrit_number="1068349" owner_email="sonnyrao@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/49/1068349/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I294197380b02e60815d085c4d4105abc5bfd5aa3" commit="e08fc6cd04218a0ac37d80d2f549488e72a2758c" commit_message="UPSTREAM: x86, microcode: Return error from driver init code when loader is disabled commit da63865a01c6384d459464e5165d95d4f04878d8 upstream. Commits 65cef1311d5d ("x86, microcode: Add a disable chicken bit") and a18a0f6850d4 ("x86, microcode: Don't initialize microcode code on paravirt") allow microcode driver skip initialization when microcode loading is not permitted. However, they don't prevent the driver from being loaded since the init code returns 0. If at some point later the driver gets unloaded this will result in an oops while trying to deregister the (never registered) device. To avoid this, make init code return an error on paravirt or when microcode loading is disabled. The driver will then never be loaded. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I294197380b02e60815d085c4d4105abc5bfd5aa3 Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com> Link: http://lkml.kernel.org/r/1422411669-25147-1-git-send-email-boris.ostrovsky@oracle.com Reported-by: James Digwall <james@dingwall.me.uk> Signed-off-by: Borislav Petkov <bp@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit ff0d1886ef0210b5dbc08934340aaf029b59aea4 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068350 " fail_count="0" gerrit_number="1068350" owner_email="sonnyrao@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/50/1068350/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I11b42dbd8dfd655f2ab4baaab995d5864ebf305a" commit="2feea695b460c2678dab6185d7bcab9b3a601a06" commit_message="UPSTREAM: x86: mm: move mmap_sem unlock from mm_fault_error() to caller commit 7fb08eca45270d0ae86e1ad9d39c40b7a55d0190 upstream. This replaces four copies in various stages of mm_fault_error() handling with just a single one. It will also allow for more natural placement of the unlocking after some further cleanup. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I11b42dbd8dfd655f2ab4baaab995d5864ebf305a Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 61cfce3e9a5de651613a0d01aecf2d08133f4bdd in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068351 " fail_count="0" gerrit_number="1068351" owner_email="sonnyrao@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/51/1068351/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I8ef32604ce8cf2a33f7a2bb5f6ed1093234f4199" commit="54d2c87e8f652d3c48883a54dc2adc0c4137d98a" commit_message="UPSTREAM: mm/hugetlb: pmd_huge() returns true for non-present hugepage commit cbef8478bee55775ac312a574aad48af7bb9cf9f upstream. Migrating hugepages and hwpoisoned hugepages are considered as non-present hugepages, and they are referenced via migration entries and hwpoison entries in their page table slots. This behavior causes race condition because pmd_huge() doesn't tell non-huge pages from migrating/hwpoisoned hugepages. follow_page_mask() is one example where the kernel would call follow_page_pte() for such hugepage while this function is supposed to handle only normal pages. To avoid this, this patch makes pmd_huge() return true when pmd_none() is true *and* pmd_present() is false. We don't have to worry about mixing up non-present pmd entry with normal pmd (pointing to leaf level pte entry) because pmd_present() is true in normal pmd. The same race condition could happen in (x86-specific) gup_pmd_range(), where this patch simply adds pmd_present() check instead of pmd_huge(). This is because gup_pmd_range() is fast path. If we have non-present hugepage in this function, we will go into gup_huge_pmd(), then return 0 at flag mask check, and finally fall back to the slow path. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I8ef32604ce8cf2a33f7a2bb5f6ed1093234f4199 Fixes: 290408d4a2 ("hugetlb: hugepage migration core") Signed-off-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com> Cc: Hugh Dickins <hughd@google.com> Cc: James Hogan <james.hogan@imgtec.com> Cc: David Rientjes <rientjes@google.com> Cc: Mel Gorman <mel@csn.ul.ie> Cc: Johannes Weiner <hannes@cmpxchg.org> Cc: Michal Hocko <mhocko@suse.cz> Cc: Rik van Riel <riel@redhat.com> Cc: Andrea Arcangeli <aarcange@redhat.com> Cc: Luiz Capitulino <lcapitulino@redhat.com> Cc: Nishanth Aravamudan <nacc@linux.vnet.ibm.com> Cc: Lee Schermerhorn <lee.schermerhorn@hp.com> Cc: Steve Capper <steve.capper@linaro.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit bebc511a44cbb8473a0bbd90be7de3c04729a676 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068352 " fail_count="0" gerrit_number="1068352" owner_email="sonnyrao@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/52/1068352/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ic8b0c9c2cd8b574ab9bb0ac2072c5e99f8582ffd" commit="cd09cb0a1e6114b7d531d7ea22ccddf71f53f4b1" commit_message="UPSTREAM: KVM: x86: update masterclock values on TSC writes commit 7f187922ddf6b67f2999a76dcb71663097b75497 upstream. When the guest writes to the TSC, the masterclock TSC copy must be updated as well along with the TSC_OFFSET update, otherwise a negative tsc_timestamp is calculated at kvm_guest_time_update. Once "if (!vcpus_matched && ka->use_master_clock)" is simplified to "if (ka->use_master_clock)", the corresponding "if (!ka->use_master_clock)" becomes redundant, so remove the do_request boolean and collapse everything into a single condition. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: Ic8b0c9c2cd8b574ab9bb0ac2072c5e99f8582ffd Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit d204feb2946a5b9f9a73c1d20c25a3930dc56fcd in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068353 " fail_count="0" gerrit_number="1068353" owner_email="sonnyrao@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/53/1068353/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I8c51cd4f777bd9d09d49a2759bc1ca22cca19d7d" commit="89eeb2a9c644381cff4f3c904a38604d967d3b66" commit_message="UPSTREAM: x86/xen: Treat SCI interrupt as normal GSI interrupt commit b568b8601f05a591a7ff09d8ee1cedb5b2e815fe upstream. Currently Xen Domain0 has special treatment for ACPI SCI interrupt, that is initialize irq for ACPI SCI at early stage in a special way as: xen_init_IRQ() ->pci_xen_initial_domain() ->xen_setup_acpi_sci() Allocate and initialize irq for ACPI SCI Function xen_setup_acpi_sci() calls acpi_gsi_to_irq() to get an irq number for ACPI SCI. But unfortunately acpi_gsi_to_irq() depends on IOAPIC irqdomains through following path acpi_gsi_to_irq() ->mp_map_gsi_to_irq() ->mp_map_pin_to_irq() ->check IOAPIC irqdomain For PV domains, it uses Xen event based interrupt manangement and doesn't make uses of native IOAPIC, so no irqdomains created for IOAPIC. This causes Xen domain0 fail to install interrupt handler for ACPI SCI and all ACPI events will be lost. Please refer to: https://lkml.org/lkml/2014/12/19/178 So the fix is to get rid of special treatment for ACPI SCI, just treat ACPI SCI as normal GSI interrupt as: acpi_gsi_to_irq() ->acpi_register_gsi() ->acpi_register_gsi_xen() ->xen_register_gsi() With above change, there's no need for xen_setup_acpi_sci() anymore. The above change also works with bare metal kernel too. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I8c51cd4f777bd9d09d49a2759bc1ca22cca19d7d Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com> Tested-by: Sander Eikelenboom <linux@eikelenboom.it> Cc: Tony Luck <tony.luck@intel.com> Cc: xen-devel@lists.xenproject.org Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: David Vrabel <david.vrabel@citrix.com> Cc: Rafael J. Wysocki <rjw@rjwysocki.net> Cc: Len Brown <len.brown@intel.com> Cc: Pavel Machek <pavel@ucw.cz> Cc: Bjorn Helgaas <bhelgaas@google.com> Link: http://lkml.kernel.org/r/1421720467-7709-2-git-send-email-jiang.liu@linux.intel.com Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Signed-off-by: Stefan Bader <stefan.bader@canonical.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit d7e48886e503d5c7413c8f546c9d4dadab58da3c in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068354 " fail_count="0" gerrit_number="1068354" owner_email="sonnyrao@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/54/1068354/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ie7fa0b393bb13058110d831e970839562200c1e5" commit="07016908c20f4720f8114b2cbc239471da213ac4" commit_message="UPSTREAM: x86/efi: Avoid triple faults during EFI mixed mode calls commit 96738c69a7fcdbf0d7c9df0c8a27660011e82a7b upstream. Andy pointed out that if an NMI or MCE is received while we're in the middle of an EFI mixed mode call a triple fault will occur. This can happen, for example, when issuing an EFI mixed mode call while running perf. The reason for the triple fault is that we execute the mixed mode call in 32-bit mode with paging disabled but with 64-bit kernel IDT handlers installed throughout the call. At Andy's suggestion, stop playing the games we currently do at runtime, such as disabling paging and installing a 32-bit GDT for __KERNEL_CS. We can simply switch to the __KERNEL32_CS descriptor before invoking firmware services, and run in compatibility mode. This way, if an NMI/MCE does occur the kernel IDT handler will execute correctly, since it'll jump to __KERNEL_CS automatically. However, this change is only possible post-ExitBootServices(). Before then the firmware "owns" the machine and expects for its 32-bit IDT handlers to be left intact to service interrupts, etc. So, we now need to distinguish between early boot and runtime invocations of EFI services. During early boot, we need to restore the GDT that the firmware expects to be present. We can only jump to the __KERNEL32_CS code segment for mixed mode calls after ExitBootServices() has been invoked. A liberal sprinkling of comments in the thunking code should make the differences in early and late environments more apparent. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: Ie7fa0b393bb13058110d831e970839562200c1e5 Reported-by: Andy Lutomirski <luto@amacapital.net> Tested-by: Borislav Petkov <bp@suse.de> Signed-off-by: Matt Fleming <matt.fleming@intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 55c0226ff05f539b49b0cbc8b9f1ddc0856f0429 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068355 " fail_count="0" gerrit_number="1068355" owner_email="sonnyrao@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/55/1068355/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I62693018dc928b993e61b6469af82583f1cef479" commit="12ec9dd6df2f74e371ba91edab504fc69b113a2a" commit_message="UPSTREAM: x86/irq: Fix regression caused by commit b568b8601f05 commit 1ea76fbadd667b19c4fa4466f3a3b55a505e83d9 upstream. Commit b568b8601f05 ("Treat SCI interrupt as normal GSI interrupt") accidently removes support of legacy PIC interrupt when fixing a regression for Xen, which causes a nasty regression on HP/Compaq nc6000 where we fail to register the ACPI interrupt, and thus lose eg. thermal notifications leading a potentially overheated machine. So reintroduce support of legacy PIC based ACPI SCI interrupt. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I62693018dc928b993e61b6469af82583f1cef479 Reported-by: Ville Syrjl <syrjala@sci.fi> Tested-by: Ville Syrjl <syrjala@sci.fi> Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Acked-by: Pavel Machek <pavel@ucw.cz> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Len Brown <len.brown@intel.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Rafael J. Wysocki <rjw@rjwysocki.net> Cc: Sander Eikelenboom <linux@eikelenboom.it> Cc: linux-pm@vger.kernel.org Link: http://lkml.kernel.org/r/1424052673-22974-1-git-send-email-jiang.liu@linux.intel.com Signed-off-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> (cherry picked from commit 1e5c8725fc15223701aa9bed537d9beaaa629008 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068356 " fail_count="0" gerrit_number="1068356" owner_email="sonnyrao@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/56/1068356/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I8e5080452c592ef8764bcd60e7f5883d5907c2a7" commit="fa19282e10f86e51dd3be6bf40210e374d98ddc7" commit_message="UPSTREAM: x86/asm/entry/64: Remove a bogus 'ret_from_fork' optimization commit 956421fbb74c3a6261903f3836c0740187cf038b upstream. 'ret_from_fork' checks TIF_IA32 to determine whether 'pt_regs' and the related state make sense for 'ret_from_sys_call'. This is entirely the wrong check. TS_COMPAT would make a little more sense, but there's really no point in keeping this optimization at all. This fixes a return to the wrong user CS if we came from int 0x80 in a 64-bit task. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I8e5080452c592ef8764bcd60e7f5883d5907c2a7 Signed-off-by: Andy Lutomirski <luto@amacapital.net> Cc: Borislav Petkov <bp@alien8.de> Cc: Denys Vlasenko <dvlasenk@redhat.com> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Oleg Nesterov <oleg@redhat.com> Cc: Thomas Gleixner <tglx@linutronix.de> Link: http://lkml.kernel.org/r/4710be56d76ef994ddf59087aad98c000fbab9a4.1424989793.git.luto@amacapital.net [ Backported from tip:x86/asm. ] Signed-off-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Sasha Levin <sasha.levin@oracle.com> (cherry picked from commit ce5dd33cbf06346752eeb5530e135d953d6b7abb in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068357 " fail_count="0" gerrit_number="1068357" owner_email="sonnyrao@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/57/1068357/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I1165b0469ad00d238813be2d2e6c96bd990f1cfa" commit="d9cc254a1e2d91f933ea355d70ec5f3ac1264f7f" commit_message="UPSTREAM: KVM: emulate: fix CMPXCHG8B on 32-bit hosts commit 4ff6f8e61eb7f96d3ca535c6d240f863ccd6fb7d upstream. This has been broken for a long time: it broke first in 2.6.35, then was almost fixed in 2.6.36 but this one-liner slipped through the cracks. The bug shows up as an infinite loop in Windows 7 (and newer) boot on 32-bit hosts without EPT. Windows uses CMPXCHG8B to write to page tables, which causes a page fault if running without EPT; the emulator is then called from kvm_mmu_page_fault. The loop then happens if the higher 4 bytes are not 0; the common case for this is that the NX bit (bit 63) is 1. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I1165b0469ad00d238813be2d2e6c96bd990f1cfa Fixes: 6550e1f165f384f3a46b60a1be9aba4bc3c2adad Fixes: 16518d5ada690643453eb0aef3cc7841d3623c2d Reported-by: Erik Rull <erik.rull@rdsoftware.de> Tested-by: Erik Rull <erik.rull@rdsoftware.de> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Sasha Levin <sasha.levin@oracle.com> (cherry picked from commit c8b6504b25d2894e7e3b4909bae15ebcd740120b in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068358 " fail_count="0" gerrit_number="1068358" owner_email="sonnyrao@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/58/1068358/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="I7b1d0989e787260815c4caaf4b7de72677f214f8" commit="a4c0fe5e968e9a03b4d730371ed1c6c3784128e4" commit_message="UPSTREAM: crypto: aesni - fix memory usage in GCM decryption [ Upstream commit ccfe8c3f7e52ae83155cb038753f4c75b774ca8a ] The kernel crypto API logic requires the caller to provide the length of (ciphertext || authentication tag) as cryptlen for the AEAD decryption operation. Thus, the cipher implementation must calculate the size of the plaintext output itself and cannot simply use cryptlen. The RFC4106 GCM decryption operation tries to overwrite cryptlen memory in req->dst. As the destination buffer for decryption only needs to hold the plaintext memory but cryptlen references the input buffer holding (ciphertext || authentication tag), the assumption of the destination buffer length in RFC4106 GCM operation leads to a too large size. This patch simply uses the already calculated plaintext size. In addition, this patch fixes the offset calculation of the AAD buffer pointer: as mentioned before, cryptlen already includes the size of the tag. Thus, the tag does not need to be added. With the addition, the AAD will be written beyond the already allocated buffer. Note, this fixes a kernel crash that can be triggered from user space via AF_ALG(aead) -- simply use the libkcapi test application from [1] and update it to use rfc4106-gcm-aes. Using [1], the changes were tested using CAVS vectors to demonstrate that the crypto operation still delivers the right results. [1] http://www.chronox.de/libkcapi.html BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: I7b1d0989e787260815c4caaf4b7de72677f214f8 CC: Tadeusz Struk <tadeusz.struk@intel.com> Cc: stable@vger.kernel.org Signed-off-by: Stephan Mueller <smueller@chronox.de> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: Sasha Levin <sasha.levin@oracle.com> (cherry picked from commit 3b389956156c23d7936f5a863cf7ac18a92dfee1 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068359 " fail_count="0" gerrit_number="1068359" owner_email="sonnyrao@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/59/1068359/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Ie47e6505d5512d4597870ed96af063855e3bdedc" commit="5bd9b6fd45cc3f875b3a0046f6cb8e441cba7ffd" commit_message="UPSTREAM: x86/fpu: Avoid math_state_restore() without used_math() in __restore_xstate_sig() [ Upstream commit a7c80ebcac3068b1c3cb27d538d29558c30010c8 ] math_state_restore() assumes it is called with irqs disabled, but this is not true if the caller is __restore_xstate_sig(). This means that if ia32_fxstate == T and __copy_from_user() fails, __restore_xstate_sig() returns with irqs disabled too. This triggers: BUG: sleeping function called from invalid context at kernel/locking/rwsem.c:41 dump_stack ___might_sleep ? _raw_spin_unlock_irqrestore __might_sleep down_read ? _raw_spin_unlock_irqrestore print_vma_addr signal_fault sys32_rt_sigreturn Change __restore_xstate_sig() to call set_used_math() unconditionally. This avoids enabling and disabling interrupts in math_state_restore(). If copy_from_user() fails, we can simply do fpu_finit() by hand. [ Note: this is only the first step. math_state_restore() should not check used_math(), it should set this flag. While init_fpu() should simply die. ] BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: Ie47e6505d5512d4597870ed96af063855e3bdedc Signed-off-by: Oleg Nesterov <oleg@redhat.com> Signed-off-by: Borislav Petkov <bp@suse.de> Cc: <stable@vger.kernel.org> Cc: Andy Lutomirski <luto@amacapital.net> Cc: Borislav Petkov <bp@alien8.de> Cc: Dave Hansen <dave.hansen@intel.com> Cc: Fenghua Yu <fenghua.yu@intel.com> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Pekka Riikonen <priikone@iki.fi> Cc: Quentin Casasnovas <quentin.casasnovas@oracle.com> Cc: Rik van Riel <riel@redhat.com> Cc: Suresh Siddha <sbsiddha@gmail.com> Cc: Thomas Gleixner <tglx@linutronix.de> Link: http://lkml.kernel.org/r/20150307153844.GB25954@redhat.com Signed-off-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Sasha Levin <sasha.levin@oracle.com> (cherry picked from commit 1a29c27a0feda99289ddc41cb5dfbe010d37d374 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068360 " fail_count="0" gerrit_number="1068360" owner_email="sonnyrao@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/60/1068360/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="Id0484fb8c16fa0a32b2ceb12a71df4a3a0b8c34e" commit="5c5afe86038717e178e1b9b2b75abe26c093781d" commit_message="UPSTREAM: x86/fpu: Drop_fpu() should not assume that tsk equals current [ Upstream commit f4c3686386393c120710dd34df2a74183ab805fd ] drop_fpu() does clear_used_math() and usually this is correct because tsk == current. However switch_fpu_finish()->restore_fpu_checking() is called before __switch_to() updates the "current_task" variable. If it fails, we will wrongly clear the PF_USED_MATH flag of the previous task. So use clear_stopped_child_used_math() instead. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: Id0484fb8c16fa0a32b2ceb12a71df4a3a0b8c34e Signed-off-by: Oleg Nesterov <oleg@redhat.com> Signed-off-by: Borislav Petkov <bp@suse.de> Reviewed-by: Rik van Riel <riel@redhat.com> Cc: <stable@vger.kernel.org> Cc: Andy Lutomirski <luto@amacapital.net> Cc: Borislav Petkov <bp@alien8.de> Cc: Dave Hansen <dave.hansen@intel.com> Cc: Fenghua Yu <fenghua.yu@intel.com> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Pekka Riikonen <priikone@iki.fi> Cc: Quentin Casasnovas <quentin.casasnovas@oracle.com> Cc: Suresh Siddha <sbsiddha@gmail.com> Cc: Thomas Gleixner <tglx@linutronix.de> Link: http://lkml.kernel.org/r/20150309171041.GB11388@redhat.com Signed-off-by: Ingo Molnar <mingo@kernel.org> Signed-off-by: Sasha Levin <sasha.levin@oracle.com> (cherry picked from commit 1b6bd91982a1f8b67684a1886dea0373c26e73c2 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068361 " fail_count="0" gerrit_number="1068361" owner_email="sonnyrao@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/61/1068361/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-3.18" change_id="If76f4c922d09e2b89c6e18d6e41c86ae7186b2d9" commit="0b8de94bb56718a240c4661e91493574e44ccd87" commit_message="UPSTREAM: kvm: move advertising of KVM_CAP_IRQFD to common code [ Upstream commit dc9be0fac70a2ad86e31a81372bb0bdfb6945353 ] POWER supports irqfds but forgot to advertise them. Some userspace does not check for the capability, but others check it---thus they work on x86 and s390 but not POWER. To avoid that other architectures in the future make the same mistake, let common code handle KVM_CAP_IRQFD the same way as KVM_CAP_IRQFD_RESAMPLE. BUG=chromium:842936 TEST=build/boot on caroline with USE=kvm_host Change-Id: If76f4c922d09e2b89c6e18d6e41c86ae7186b2d9 Reported-and-tested-by: Greg Kurz <gkurz@linux.vnet.ibm.com> Cc: stable@vger.kernel.org Fixes: 297e21053a52f060944e9f0de4c64fad9bcd72fc Signed-off-by: Paolo Bonzini <pbonzini@redhat.com> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com> Signed-off-by: Sasha Levin <sasha.levin@oracle.com> (cherry picked from commit 9ab9ee7a87bbea7b4719e0445bcda2d7f0b7d197 in https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/) Signed-off-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068362 " fail_count="0" gerrit_number="1068362" owner_email="sonnyrao@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/62/1068362/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-4.14" change_id="I7d3b0a38cc17af33a2672e1c14bedbb009e5fa7a" commit="87019829e9114d161b25ce187828e388e6b5cc61" commit_message="UPSTREAM: scsi: ufs: add ufs a command complete time stamp Signed-off-by: Zang Leigang <zangleigang@hisilicon.com> Reviewed-by: Subhash Jadavani <subhashj@codeaurora.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: I7d3b0a38cc17af33a2672e1c14bedbb009e5fa7a Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit 090171885f505ea6814ad6459e9982bb4444c245) Reviewed-on: https://chromium-review.googlesource.com/1056074 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Gwendal Grignou <gwendal@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="2" gerrit_number="1056074" owner_email="evgreen@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/74/1056074/1" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-4.14" change_id="I10cc9ed85bb18898f5cbf5d5f2a375c4d8eb6312" commit="1230a93f91f029c0208c1f4657ce89c297eb81ef" commit_message="UPSTREAM: scsi: ufs: continue to boot even with Boot LUN is disabled Several configurable fields of the Device Descriptor and the Unit Descriptors determine the Boot LUN status. The bBootEnable field and the bBootLunEn attribute is set to zero by default, so the Boot LUN is disabled by default. At which point the scsi device add for Boot LUN will fail, but we can continue to use the ufs device in fact. This failure shouldn't abort the device boot. Signed-off-by: Huanlin Ke <kehuanlin@pinecone.net> Reviewed-by: Subhash Jadavani <subhashj@codeaurora.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: I10cc9ed85bb18898f5cbf5d5f2a375c4d8eb6312 Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit 3d21fbdedc8b0a6a73528bc6fd2850fdc1e93031) Reviewed-on: https://chromium-review.googlesource.com/1056075 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="2" gerrit_number="1056075" owner_email="evgreen@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/75/1056075/1" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-4.14" change_id="I32994422d3fd0fc60841368a2ac2a5f30ff94d02" commit="3aa66e872fe003279342b907c7e3493e7a77548a" commit_message="UPSTREAM: scsi: ufs: fix wrong command type of UTRD for UFSHCI v2.1 Since the command type of UTRD in UFS 2.1 specification is the same with UFS 2.0. And it assumes the future UFS specification will follow the same definition. Signed-off-by: kehuanlin <kehuanlin@pinecone.net> Reviewed-by: Subhash Jadavani <subhashj@codeaurora.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: I32994422d3fd0fc60841368a2ac2a5f30ff94d02 Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit 83dc7e3dea76b77b6bcc289eb86c5b5c145e8dff) Reviewed-on: https://chromium-review.googlesource.com/1056076 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="2" gerrit_number="1056076" owner_email="evgreen@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/76/1056076/1" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-4.14" change_id="Iffc098173f1ce2b9a7b83d2ed74230909c1bcd1f" commit="2f9e20b819581468a90615afb9b2ab6c55be82ee" commit_message="UPSTREAM: scsi: ufs: Change HCI macro to actual bit position Currently UFS HCI uses UFS_BIT() macro to get various bit position for the hardware registers status bits. Which makes code longer instead of shorter. This macro does not improve code readability as well. Lets re-write these macro definition with the actual bit position. Suggested-by: Bart Van Assche <Bart.VanAssche@wdc.com> Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com> Reviewed-by: Bart Van Assche <bart.vanassche@wdc.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: Iffc098173f1ce2b9a7b83d2ed74230909c1bcd1f Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit cc81641a45252084878034620bcf80e15c9f9580) Reviewed-on: https://chromium-review.googlesource.com/1056077 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="2" gerrit_number="1056077" owner_email="evgreen@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/77/1056077/1" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-4.14" change_id="Idd6e8fd1ef5471b3986f99ed614a6c0c5bd735f6" commit="483a4a6bad9e00e3d0eef4fc8e75590e71185df2" commit_message="UPSTREAM: scsi: ufs-qcom: Remove uses of UFS_BIT() macro Use actual bit position instead of UFS_BIT() macro. This patch also changes bit-17 to meaningful #define. This change is as per discussion here [1] [1] -> https://lkml.org/lkml/2017/8/28/786 Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com> Cc: Subhash Jadavani <subhashj@codeaurora.org> Reviewed-by: Bart Van Assche <bart.vanassche@wdc.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: Idd6e8fd1ef5471b3986f99ed614a6c0c5bd735f6 Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit 7e014efdc0b11ceff44d13e9be2d9a6063250c6c) Reviewed-on: https://chromium-review.googlesource.com/1056078 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="2" gerrit_number="1056078" owner_email="evgreen@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/78/1056078/1" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-4.14" change_id="Idb172877777934fefc205fcc67d4b1d51cff47ad" commit="e9f7f773ed5bb84a8bfd3cd499ab83dc3e116134" commit_message="UPSTREAM: scsi: ufs: Remove unused #defines HOST_ERROR_INDICATOR and DEVICE_ERROR_INDICATOR are not used anywhere. Also as per JESD223C specification, bit[7:4] are reserved. Lets remove these #defines. Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com> Reviewed-by: Bart Van Assche <bart.vanassche@wdc.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: Idb172877777934fefc205fcc67d4b1d51cff47ad Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit 5b35c70d8651450091a84d3980c26639390e1fc2) Reviewed-on: https://chromium-review.googlesource.com/1056079 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="2" gerrit_number="1056079" owner_email="evgreen@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/79/1056079/1" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-4.14" change_id="I31304a1acbf81b2144ca5e85edafeb2b46552fba" commit="3b298c3fa829cc8405d4066b2ddd07df59f99ccf" commit_message="UPSTREAM: scsi: ufs: Remove unused UFS_BIT() macro Since we have converted all the user of UFS_BIT() macro with the actual bit position, let remove unused UFS_BIT()macro. Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com> Reviewed-by: Bart Van Assche <bart.vanassche@wdc.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: I31304a1acbf81b2144ca5e85edafeb2b46552fba Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit 395c81ad23f25ee68e234c6676f13d9cbce4a76e) Reviewed-on: https://chromium-review.googlesource.com/1056080 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="2" gerrit_number="1056080" owner_email="evgreen@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/80/1056080/1" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-4.14" change_id="I7eb3ae417baca3fbb1f85648f3403aad796e90fa" commit="62b4f380e044a6b7380f228f9d2c151bff54d7d0" commit_message="UPSTREAM: scsi: ufs: add some definitions included in UFS HCI specification These would be used in the future in some specific drivers. Signed-off-by: Kiwoong Kim <kwmad.kim@samsung.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: I7eb3ae417baca3fbb1f85648f3403aad796e90fa Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit cffe3ff34668ad753cbd5a4e5481f235021c49e4) Reviewed-on: https://chromium-review.googlesource.com/1056081 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="2" gerrit_number="1056081" owner_email="evgreen@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/81/1056081/1" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-4.14" change_id="I20b13cf413125fddd021771d5f21029374db21f7" commit="f576e52734fb0a73b9fa1a4f823ec7c9b7db4c97" commit_message="UPSTREAM: scsi: ufs: Enable quirk to ignore sending WRITE_SAME command WRITE_SAME command is not supported by UFS. Enable a quirk for the upper level drivers to not send WRITE SAME command. [mkp: botched patch, applied by hand] Signed-off-by: Sujit Reddy Thumma <sthumma@codeaurora.org> Signed-off-by: Subhash Jadavani <subhashj@codeaurora.org> Signed-off-by: Asutosh Das <asutoshd@codeaurora.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: I20b13cf413125fddd021771d5f21029374db21f7 Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit 84af7e8b895088d89f246d6b0f82717fafdebf61) Reviewed-on: https://chromium-review.googlesource.com/1056082 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="2" gerrit_number="1056082" owner_email="evgreen@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/82/1056082/1" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-4.14" change_id="Icedf3b0058af1fd06f7783c533ee72bbd5d62414" commit="ff411153736e992dad8b148a29865a2f1c1eeda3" commit_message="UPSTREAM: scsi: ufs: sysfs: attribute group for existing sysfs entries. This patch introduces attribute group to show existing sysfs entries. Signed-off-by: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: Icedf3b0058af1fd06f7783c533ee72bbd5d62414 Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit cbb6813ee771abc17a713432f31820581eafd4ae) Reviewed-on: https://chromium-review.googlesource.com/1056083 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="2" gerrit_number="1056083" owner_email="evgreen@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/83/1056083/1" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-4.14" change_id="Ie1f992a7db7b39fa876bf917ca962482a228bcde" commit="a44a484501b03725dafe0d402c7fbd6c82a653dd" commit_message="UPSTREAM: scsi: ufs: sysfs: device descriptor This patch introduces a sysfs group entry for the UFS device descriptor parameters. The group adds "device_descriptor" folder under the UFS driver sysfs entry (/sys/bus/platform/drivers/ufshcd/*). The parameters are shown as hexadecimal numbers. The full information about the parameters could be found at UFS specifications 2.1. Signed-off-by: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: Ie1f992a7db7b39fa876bf917ca962482a228bcde Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit 45bced87e79316ecd868aee8f187284025792c5f) Reviewed-on: https://chromium-review.googlesource.com/1056084 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="2" gerrit_number="1056084" owner_email="evgreen@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/84/1056084/1" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-4.14" change_id="Ic12b873a99f6f90cdf2cfcf51aec13749f82cd08" commit="4153b1a6813c3cbb4a84d83d39dc150e09bb9dab" commit_message="UPSTREAM: scsi: ufs: sysfs: interconnect descriptor This patch introduces a sysfs group entry for the UFS interconnect descriptor parameters. The group adds "interconnect_descriptor" folder under the UFS driver sysfs entry (/sys/bus/platform/drivers/ufshcd/*). The parameters are shown as hexadecimal numbers. The full information about the parameters could be found at UFS specifications 2.1. Signed-off-by: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: Ic12b873a99f6f90cdf2cfcf51aec13749f82cd08 Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit 8c2582bfbd9abe84b9cf435996aa720a84f908c4) Reviewed-on: https://chromium-review.googlesource.com/1056085 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="2" gerrit_number="1056085" owner_email="evgreen@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/85/1056085/1" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-4.14" change_id="I00f9a8b01a109992bc5596bf087c29ca5b7c236b" commit="5b3837abbaacdf746e9435b1b794196818bc6516" commit_message="UPSTREAM: scsi: ufs: sysfs: geometry descriptor This patch introduces a sysfs group entry for the UFS geometry descriptor parameters. The group adds "geometry_descriptor" folder under the UFS driver sysfs entry (/sys/bus/platform/drivers/ufshcd/*). The parameters are shown as hexadecimal numbers. The full information about the parameters could be found at UFS specifications 2.1. Signed-off-by: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: I00f9a8b01a109992bc5596bf087c29ca5b7c236b Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit c720c091222e26d46c0fd9c70144a0f916bf3993) Reviewed-on: https://chromium-review.googlesource.com/1056086 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="3" gerrit_number="1056086" owner_email="evgreen@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/86/1056086/1" remote="cros" total_fail_count="3"/><pending_commit branch="chromeos-4.14" change_id="I86b1c2860639cb93a68f5b4a1ebdb4eb878b0a90" commit="5123dfe2b9429c7b762b9115fef198dbc44a03e5" commit_message="UPSTREAM: scsi: ufs: sysfs: health descriptor This patch introduces a sysfs group entry for the UFS health descriptor parameters. The group adds "health_descriptor" folder under the UFS driver sysfs entry (/sys/bus/platform/drivers/ufshcd/*). The parameters are shown as hexadecimal numbers. The full information about the parameters could be found at UFS specifications 2.1. Signed-off-by: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: I86b1c2860639cb93a68f5b4a1ebdb4eb878b0a90 Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit c648c2d27f168ae4faeb43f8c3074226aae3862c) Reviewed-on: https://chromium-review.googlesource.com/1056307 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="3" gerrit_number="1056307" owner_email="evgreen@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/07/1056307/1" remote="cros" total_fail_count="3"/><pending_commit branch="chromeos-4.14" change_id="Ib4cb3068735ab5caad0af132616678a012fa911e" commit="1c02ad4bca74594190add104c5b3e5e333d17459" commit_message="UPSTREAM: scsi: ufs: sysfs: power descriptor This patch introduces a sysfs group entry for the UFS power descriptor parameters. The group adds "power_descriptor" folder under the UFS driver sysfs entry (/sys/bus/platform/drivers/ufshcd/*). The parameters are shown as hexadecimal numbers. The full information about the parameters could be found at UFS specifications 2.1. Signed-off-by: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: Ib4cb3068735ab5caad0af132616678a012fa911e Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit c2e6e283c52f3a2c4a99774b36bcc88e7cbd5eb7) Reviewed-on: https://chromium-review.googlesource.com/1056308 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="3" gerrit_number="1056308" owner_email="evgreen@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/08/1056308/1" remote="cros" total_fail_count="3"/><pending_commit branch="chromeos-4.14" change_id="I9846f288b6c0fec2edcf9412bd446e2bc7c75dea" commit="46f1dd027c41c28241c524b6c45df6ba219a89ff" commit_message="UPSTREAM: scsi: ufs: sysfs: string descriptors This patch introduces a sysfs group entry for the UFS string descriptors. The group adds "string_descriptors" folder under the UFS driver sysfs entry (/sys/bus/platform/drivers/ufshcd/*). The folder will contain 5 files that will show string values defined by the UFS spec: a manufacturer name, a product name, an OEM id, a serial number and a product revision. The full information about the string descriptors could be found at UFS specifications 2.1. Signed-off-by: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: I9846f288b6c0fec2edcf9412bd446e2bc7c75dea Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit 2238d31cdeabc585de5869efd11856815aa4dd13) Reviewed-on: https://chromium-review.googlesource.com/1056309 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="3" gerrit_number="1056309" owner_email="evgreen@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/09/1056309/1" remote="cros" total_fail_count="3"/><pending_commit branch="chromeos-4.14" change_id="If6400c14b3bc5cef883aa81ede10775a1b7284de" commit="17a1fcd5b8aef2da4be162d98af9cd766f279a83" commit_message="UPSTREAM: scsi: core: host template attribute groups The patch introduces an additional field in the scsi_host_template structure - struct attribute_group **sdev_group. This field allows to define groups of attributes. It will provide an ability to use binary attributes as well as device attributes and to group them under subfolders if necessary. Signed-off-by: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: If6400c14b3bc5cef883aa81ede10775a1b7284de Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit 86b87cde0b5581cdb1a7babeb9c4c387761f151b) Reviewed-on: https://chromium-review.googlesource.com/1056296 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="3" gerrit_number="1056296" owner_email="evgreen@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/96/1056296/1" remote="cros" total_fail_count="3"/><pending_commit branch="chromeos-4.14" change_id="I860a821552aeea6560a86ab57cab87f061bdb51e" commit="f3156c05492b3188bd7fec76455ea33d235b9e7c" commit_message="UPSTREAM: scsi: ufs: sysfs: unit descriptor This patch introduces a sysfs group entry for the UFS unit descriptor parameters. The group adds "unit_descriptor" folder under the corresponding SCSI device sysfs entry (/sys/class/scsi_device/*/device/). The parameters are shown as hexadecimal numbers. The full information about the parameters could be found at UFS specifications 2.1. Signed-off-by: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: I860a821552aeea6560a86ab57cab87f061bdb51e Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit d829fc8a1058851f1058b4a29ea02da125c1684a) Reviewed-on: https://chromium-review.googlesource.com/1056310 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="3" gerrit_number="1056310" owner_email="evgreen@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/1056310/2" remote="cros" total_fail_count="3"/><pending_commit branch="chromeos-4.14" change_id="I4bdf34d5ca170e36627262bb9ec0f7a63c645a1b" commit="57777fd1f3be16e961aa6199678926cb89229e12" commit_message="UPSTREAM: scsi: ufs: sysfs: flags This patch introduces a sysfs group entry for the UFS flags. The group adds "flags" folder under the UFS driver sysfs entry (/sys/bus/platform/drivers/ufshcd/*). The flags are shown as boolean value ("true" or "false"). The full information about the UFS flags could be found at UFS specifications 2.1. Signed-off-by: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: I4bdf34d5ca170e36627262bb9ec0f7a63c645a1b Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit d10b2a8ea8fd0d6c8a667dc1950c8c061bfbbcdd) Reviewed-on: https://chromium-review.googlesource.com/1056311 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="3" gerrit_number="1056311" owner_email="evgreen@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/1056311/2" remote="cros" total_fail_count="3"/><pending_commit branch="chromeos-4.14" change_id="I0381034332c6584e18066f107f80ec74d4541a2b" commit="7834ead9d52d3452e53d70c9f78b6c808dce29a8" commit_message="UPSTREAM: scsi: ufs: sysfs: attributes This patch introduces a sysfs group entry for the UFS attributes. The group adds "attributes" folder under the UFS driver sysfs entry (/sys/bus/platform/drivers/ufshcd/*). The attributes are shown as hexadecimal numbers. The full information about the attributes could be found at UFS specifications 2.1. Signed-off-by: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: I0381034332c6584e18066f107f80ec74d4541a2b Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit ec92b59cc03c3d5757449c1c9344524e088df2bd) Reviewed-on: https://chromium-review.googlesource.com/1056312 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="3" gerrit_number="1056312" owner_email="evgreen@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/1056312/2" remote="cros" total_fail_count="3"/><pending_commit branch="chromeos-4.14" change_id="I0380c03e057b8064b0eb13d9cacc9dbe6561cd1f" commit="ad0644d56c7b5704bab654ed9d97d871f8a2b68b" commit_message="UPSTREAM: scsi: ufs: Fix kernel-doc errors and warnings Avoid that the kernel-doc tool complains about mismatches between kernel-doc headers and function definitions. Avoid that errors like the following are reported when building the UFS driver with W=1: drivers/scsi/ufs/tc-dwc-g210-pci.c:60: error: Cannot parse struct or union! drivers/scsi/ufs/tc-dwc-g210-pltfrm.c:26: warning: cannot understand function prototype: 'struct ufs_hba_variant_ops tc_dwc_g210_20bit_pltfm_hba_vops = ' Signed-off-by: Bart Van Assche <bart.vanassche@wdc.com> Cc: Vivek Gautam <vivek.gautam@codeaurora.org> Cc: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: I0380c03e057b8064b0eb13d9cacc9dbe6561cd1f Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit 8aa29f192ca675746ab4f39e46a5fd712a76faa6) Reviewed-on: https://chromium-review.googlesource.com/1056313 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="3" gerrit_number="1056313" owner_email="evgreen@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/1056313/2" remote="cros" total_fail_count="3"/><pending_commit branch="chromeos-4.14" change_id="Id62dbc4b2d8420591f945d80c06392936147f8f6" commit="40d43cabad5a710d4710c609e676e9542f869a3d" commit_message="UPSTREAM: scsi: ufs: sysfs: reworking of the rpm_lvl and spm_lvl entries Read from these files will return the integer value of the chosen power management level now. Separate entries were added to show the target UFS device and UIC link states. The description of the possible power managements levels was added to the ABI file. The on-write behaviour of these entries wasn't changed. [mkp: typo] Signed-off-by: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Acked-by: Adrian Hunter <adrian.hunter@intel.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: Id62dbc4b2d8420591f945d80c06392936147f8f6 Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit 114c1aa210494a02c26aa33f793e5b641df01989) Reviewed-on: https://chromium-review.googlesource.com/1056314 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="3" gerrit_number="1056314" owner_email="evgreen@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/1056314/2" remote="cros" total_fail_count="3"/><pending_commit branch="chromeos-4.14" change_id="If8f5ba8ec86f4382343ac0569d5bb155b4c27e74" commit="ddc8f0949d99db61c86964644557363f05faa4e7" commit_message="UPSTREAM: scsi: ufs: Add support for Auto-Hibernate Idle Timer UFS host controllers may support an autonomous power management feature called the Auto-Hibernate Idle Timer. The timer is set to the number of microseconds of idle time before the UFS host controller will autonomously put the link into Hibernate state. That will save power at the expense of increased latency. Any access to the host controller interface registers will automatically put the link out of Hibernate state. So once configured, the feature is transparent to the driver. Expose the Auto-Hibernate Idle Timer value via SysFS to allow users to choose between power efficiency or lower latency. Set a default value of 150 ms. Signed-off-by: Adrian Hunter <adrian.hunter@intel.com> Acked-by: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: If8f5ba8ec86f4382343ac0569d5bb155b4c27e74 Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit ad448378825f5746c5fa37718724bc8f4e7b6945) Reviewed-on: https://chromium-review.googlesource.com/1056315 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="3" gerrit_number="1056315" owner_email="evgreen@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/1056315/2" remote="cros" total_fail_count="3"/><pending_commit branch="chromeos-4.14" change_id="I2fac8b38d0b422786d62edf3f1be4834c18b2313" commit="8797ed0a2e4a8a24bdfef10d9438042a9b35ab6f" commit_message="UPSTREAM: scsi: ufs: add trace event for ufs upiu Add UFS Protocol Information Units(upiu) trace events for ufs driver, used to trace various ufs transaction types- command, task-management and device management. The trace-point format is generic and can be easily adapted to trace other upius if needed. Currently tracing ufs transaction of type 'device management', which this patch introduce, cannot be obtained from any other trace. Device management transactions are used for communication with the device such as reading and writing descriptor or attributes etc. Signed-off-by: Ohad Sharabi <ohad.sharabi@sandisk.com> Reviewed-by: Stanislav Nijnikov <stanislav.nijnikov@wdc.com> Reviewed-by: Bart Van Assche <bart.vanassche@wdc.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> BUG=b:74254727 TEST=Build kernel for Cheza Change-Id: I2fac8b38d0b422786d62edf3f1be4834c18b2313 Signed-off-by: Evan Green <evgreen@chromium.org> (cherry picked from commit 6667e6d91c88a788d5ab1b1e999d245473e84a90) Reviewed-on: https://chromium-review.googlesource.com/1056316 Commit-Ready: Douglas Anderson <dianders@chromium.org> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="3" gerrit_number="1056316" owner_email="evgreen@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/1056316/2" remote="cros" total_fail_count="3"/><pending_commit branch="master" change_id="I6ae3a805167a3404701d8a53c14dc83299afb376" commit="0faaed8045782928a710e14dd69956dd0f5b3fc8" commit_message="lpc/espi: define new targeted config options Introduce CONFIG_HOSTCMD_LPC and CONFIG_HOSTCMD_ESPI which will replace CONFIG_LPC and CONFIG_ESPI. Today the CONFIG_LPC option guards both common code to eSPI and LPC and LPC-only code. Going forward CONFIG_HOSTCMD_LPC will guard only LPC code, and a new option CONFIG_HOSTCMD_X86 will guard common code to both LPC and eSPI. I am leaving the CONFIG_LPC and CONFIG_ESPI defines in this CL so each CL in the stack compiles. BRANCH=none BUG=chromium:818804 TEST=Full stack builds and works on yorp (espi) and grunt (lpc) Change-Id: I6ae3a805167a3404701d8a53c14dc83299afb376 Signed-off-by: Jett Rink <jettrink@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1067498 Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="0" gerrit_number="1067498" owner_email="jettrink@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/98/1067498/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Idd1519494a4f880b7b2018d059579d50c5461fcf" commit="e7404f4d054145b5bdb2c762bf8a262136bae335" commit_message="espi: convert all eSPI board to use CONFIG_HOSTCMD_ESPI Convert all boards that use both CONFIG_ESPI and CONFIG_LPC to only use the CONFIG_HOSTCMD_ESPI option. BRANCH=none BUG=chromium:818804 TEST=entire stack works with lpc and espi Change-Id: Idd1519494a4f880b7b2018d059579d50c5461fcf Signed-off-by: Jett Rink <jettrink@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1067499 Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="0" gerrit_number="1067499" owner_email="jettrink@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/99/1067499/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I4a70e10c34d79361ceada1ff40b8912b8a6fdaa7" commit="755d6a2c7eb46e27a2db9913835d797ebc7cd9b7" commit_message="lpc: convert LPC only boards to use CONFIG_HOSTCMD_LPC BRANCH=none BUG=chromium:818804 TEST=Full stack builds and works on yorp (espi) and grunt (lpc) Change-Id: I4a70e10c34d79361ceada1ff40b8912b8a6fdaa7 Signed-off-by: Jett Rink <jettrink@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1067500 Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="0" gerrit_number="1067500" owner_email="jettrink@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/00/1067500/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ic477277543c1f24999070dc408052c7266df22e6" commit="63e61db20b6665649baa020f8a336a79772337b2" commit_message="lpc: add explicit LPC define in board.h The ITE eval board relied on the chip's define for LPC. Since the ITE chip supports both LPC and eSPI, we want to define LPC here to be explicit. BRANCH=none BUG=chromium:818804 TEST=Full stack builds and works on yorp (espi) and grunt (lpc) Change-Id: Ic477277543c1f24999070dc408052c7266df22e6 Signed-off-by: Jett Rink <jettrink@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1067501 Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="0" gerrit_number="1067501" owner_email="jettrink@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/01/1067501/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ie272787b2425175fe36b06fcdeeee90ec5ccbe95" commit="6c9298923548ddd49ef3d69a3c3e2290e0326650" commit_message="lpc/espi: convert ec chip code to use granular option Break the ec chip code up with the more granular CONFIG_HOSTCMD_(X86|LPC|ESPI) options. BRANCH=none BUG=chromium:818804 TEST=Full stack builds and works on yorp (espi) and grunt (lpc) Change-Id: Ie272787b2425175fe36b06fcdeeee90ec5ccbe95 Signed-off-by: Jett Rink <jettrink@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1067502 Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="0" gerrit_number="1067502" owner_email="jettrink@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/02/1067502/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Iba9a48f2cab12fadd0d9ab8eab0d5d5476eab238" commit="1e2dbaab6f2056a6e76826e4ec2db8b50f0490dd" commit_message="lpc/espi: convert remaning CONFIG_LPC to CONFIG_HOSTCMD_X86 We have converted all LPC-only configs to HOSTCMD_LPC so the remaining CONFIG_LPC defines represent the common case. BRANCH=none BUG=chromium:818804 TEST=Full stack builds and works on yorp (espi) and grunt (lpc) Change-Id: Iba9a48f2cab12fadd0d9ab8eab0d5d5476eab238 Signed-off-by: Jett Rink <jettrink@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1067503 Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="0" gerrit_number="1067503" owner_email="jettrink@chromium.org" pass_count="0" patch_number="4" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/03/1067503/4" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I3d94c35c50e4cae1b2853b06665fc6415b2a9166" commit="e171a210545d7f8e733911fc5254a439ba37c8d4" commit_message="metrics: memd: remove regex dependency env_logger by default depends on regex, which depends on a lot of other packages. This reduces the size of the executable from 1.4 to 0.6 MB. This also accidentally bumped the version number for a number of other dependencies. Maybe I should freeze them all in Cargo.toml. BUG=chromium:729335 TEST=tested upstart with start/stop/reboot Change-Id: I3d94c35c50e4cae1b2853b06665fc6415b2a9166 Reviewed-on: https://chromium-review.googlesource.com/1063041 Commit-Ready: Luigi Semenzato <semenzato@chromium.org> Tested-by: Luigi Semenzato <semenzato@chromium.org> Reviewed-by: Luigi Semenzato <semenzato@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> " fail_count="2" gerrit_number="1063041" owner_email="semenzato@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/41/1063041/5" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="If00d8cd491d4567b70a60519fcdf6446716b8ddc" commit="6967df5cb54a8fac66c001421197f4f851baa25f" commit_message="metrics: memd: treat low-memory notifications as "interesting" This ensures that a clip is collected whenever a low-mem notification fires even if no tab is subsequently discarded (if, for instance, by the time the tab discarder is running, enough memory has been freed, by swapping or other means). BUG=chromium:729335 TEST=memd-tester still passes Change-Id: If00d8cd491d4567b70a60519fcdf6446716b8ddc Reviewed-on: https://chromium-review.googlesource.com/1063169 Commit-Ready: Luigi Semenzato <semenzato@chromium.org> Tested-by: Luigi Semenzato <semenzato@chromium.org> Reviewed-by: Luigi Semenzato <semenzato@chromium.org> Reviewed-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> " fail_count="2" gerrit_number="1063169" owner_email="semenzato@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/69/1063169/5" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I51877ef1a0c94c817bfc3dbbb77e783172297a2b" commit="69a7758cdbe092cfc89ba43300a28806ddf269ec" commit_message="metrics: memd: correctly convert timeval fields Don't make assumptions on the size of the timeval fields (which is different on different platforms) and instead convert directly to their types. BUG=chromium:729335 TEST=compiles for kevin and caroline Change-Id: I51877ef1a0c94c817bfc3dbbb77e783172297a2b Reviewed-on: https://chromium-review.googlesource.com/1064314 Commit-Ready: Luigi Semenzato <semenzato@chromium.org> Tested-by: Luigi Semenzato <semenzato@chromium.org> Reviewed-by: Luigi Semenzato <semenzato@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> " fail_count="2" gerrit_number="1064314" owner_email="semenzato@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/14/1064314/5" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I94268a20eb89471a1b6dd49d33a644372fef28d2" commit="70fd7ead5e4496028cba364c1cc4ddc70d7b6cf7" commit_message="metrics: memd: use syslog crate Logging via syslog adds about 100k to the binary size (330k to 440k on x86 and 290k to 380k on arm). BUG=chromium:729335 TEST=none Change-Id: I94268a20eb89471a1b6dd49d33a644372fef28d2 Reviewed-on: https://chromium-review.googlesource.com/1064691 Commit-Ready: Luigi Semenzato <semenzato@chromium.org> Tested-by: Luigi Semenzato <semenzato@chromium.org> Reviewed-by: Luigi Semenzato <semenzato@chromium.org> " fail_count="2" gerrit_number="1064691" owner_email="semenzato@chromium.org" pass_count="0" patch_number="6" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/91/1064691/6" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I51a5b25dc9c84cce8494bccd9ca10f4798d6bc00" commit="58cd347c53f141662c07be2d019664d825130c30" commit_message="metrics: memd: fix parsing bug Parsing of /proc/loadavg was broken because the input could contain extra spaces. This makes the parser more lenient. Also provides more info on errors. BUG=chromium:729335 TEST=ran integration test and ran on device Change-Id: I51a5b25dc9c84cce8494bccd9ca10f4798d6bc00 Reviewed-on: https://chromium-review.googlesource.com/1066453 Commit-Ready: Luigi Semenzato <semenzato@chromium.org> Tested-by: Luigi Semenzato <semenzato@chromium.org> Reviewed-by: Luigi Semenzato <semenzato@chromium.org> " fail_count="2" gerrit_number="1066453" owner_email="semenzato@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/53/1066453/2" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I7256633fb7002da9ce8af03be2f24410b90ccf3f" commit="c3e68139b39bfb65504275d9dd48567b04113e6d" commit_message="Add low-level p9 protocol implementation Implement encoding and decoding various primitives using the p9 protocol. In addition, add a procedural macro to derive the encoding and decoding implementation for structs built out of the primitives. BUG=chromium:703939 TEST=unit tests CQ-DEPEND=CL:1065063 Change-Id: I7256633fb7002da9ce8af03be2f24410b90ccf3f Signed-off-by: Chirantan Ekbote <chirantan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/969965 Reviewed-by: Stephen Barber <smbarber@chromium.org> " fail_count="0" gerrit_number="969965" owner_email="chirantan@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/65/969965/5" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I6b48f3e2eb9779fca57f8b71120b7bb1e8ab4ab9" commit="2ade51ec9e76debfe2625fabfce21539da6200ac" commit_message="p9: protocol: Add message definitions Add definitions for all the messages we expect to send and receive over the wire. BUG=chromium:703939 TEST=none Change-Id: I6b48f3e2eb9779fca57f8b71120b7bb1e8ab4ab9 Signed-off-by: Chirantan Ekbote <chirantan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1013201 Reviewed-by: Stephen Barber <smbarber@chromium.org> " fail_count="0" gerrit_number="1013201" owner_email="chirantan@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/01/1013201/4" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="If1451d5bcc2737abc2a14d2b81005c6318165e1f" commit="b1cc4e407fdaf0b9c2b8d21fff3e362c848b222c" commit_message="Update libc version to 0.2.40 The p9 crate needs the libc::DT_UNKNOWN constant, which isn't available in version 0.2.34 but is available in version 0.2.40. BUG=chromium:703939 TEST=none CQ-DEPEND=CL:1065064 Change-Id: If1451d5bcc2737abc2a14d2b81005c6318165e1f Signed-off-by: Chirantan Ekbote <chirantan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1013202 Reviewed-by: Stephen Barber <smbarber@chromium.org> " fail_count="0" gerrit_number="1013202" owner_email="chirantan@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/02/1013202/4" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I6f78a3d3da97e09039eb9d828b420e710b0cf562" commit="99d38f68c91fd941cc3ab6499940501a10a45f1e" commit_message="crosvm: Update libc dependency to 0.2.40 Update the libc crate to 0.2.40 since it provides constants that crosvm needs and are not available in earlier versions of the crate. BUG=chromium:703939 TEST=emerge-{eve,kevin} crosvm CQ-DEPEND=CL:1013202 Change-Id: I6f78a3d3da97e09039eb9d828b420e710b0cf562 Signed-off-by: Chirantan Ekbote <chirantan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1065064 " fail_count="0" gerrit_number="1065064" owner_email="chirantan@chromium.org" pass_count="0" patch_number="3" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/64/1065064/3" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-2016.05" change_id="I5cddf649037d5d030d4b471da20b800062a0f701" commit="474cb0dc23d890b92896306f2f8602e590ce90d8" commit_message="UPSTREAM: soc/nvidia/tegra(124|210): Add distclean targets Add distclean targets so these can be called by the junit.xml test target needed for jenkins testing. BUG=none BRANCH=none TEST=none Change-Id: I5cddf649037d5d030d4b471da20b800062a0f701 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 7a604bbccd604a6110c4e8761a5c3e99ac292304 Original-Change-Id: I5991b43503da1778a6d74a57fbc0daf862e570d7 Original-Signed-off-by: Martin Roth <gaumless@gmail.com> Original-Reviewed-on: https://review.coreboot.org/26433 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Julius Werner <jwerner@chromium.org> Original-Reviewed-by: Paul Menzel <paulepanter@users.sourceforge.net> Reviewed-on: https://chromium-review.googlesource.com/1068864 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="1" gerrit_number="1068864" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/64/1068864/1" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-2016.05" change_id="If2a5577a4bce964a3fb42149e141f2c68c570ae6" commit="623c894d1b0227029d570032f57bce5b628b89cd" commit_message="UPSTREAM: util/testing: Convert tegra124 and tegra210 builds to junit Because the tegra124 & tegra201 lp0 builds weren't junit tests, the builds weren't actually picked up by jenkins, so any failures were not previously reported. BUG=none BRANCH=none TEST=none Change-Id: If2a5577a4bce964a3fb42149e141f2c68c570ae6 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 1613e25be19eb51c9274437a1dfcace9ad1a999c Original-Change-Id: Ie443ca713912d01ccf6921ce49f846d7297163ef Original-Signed-off-by: Martin Roth <gaumless@gmail.com> Original-Reviewed-on: https://review.coreboot.org/26422 Original-Reviewed-by: Patrick Georgi <pgeorgi@google.com> Original-Reviewed-by: Jonathan Neuschfer <j.neuschaefer@gmx.net> Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-on: https://chromium-review.googlesource.com/1068865 Commit-Ready: Martin Roth <martinroth@chromium.org> Tested-by: Patrick Georgi <pgeorgi@chromium.org> Tested-by: Martin Roth <martinroth@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="2" gerrit_number="1068865" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/65/1068865/1" remote="cros" total_fail_count="2"/><pending_commit branch="chromeos-2016.05" change_id="Iecf8de44abcf90892931380e2bf142e597d37379" commit="5dd04d7c6406bed57287c989ac30b5b3de8c2595" commit_message="UPSTREAM: Documentation: Update doxygen config files - Update the config files to 1.8.13 - Unify the coreboot and coreboot_simple configs. The only difference now is that coreboot uses the graphviz library to generate call graphs and other things, while coreboot_simple does not. This means that the doxygen_simple target builds in just over a minute, while the doxygen build target takes roughly an hour. - Both targets now only document coreboot proper. While at times it might be useful to see links to code from src/vendorcode, 3rdparty, or util, these directories also really clutter up the doxygen output. To make it easier to see the coreboot code, all of these directories are excluded. BUG=none BRANCH=none TEST=none Change-Id: Iecf8de44abcf90892931380e2bf142e597d37379 Signed-off-by: Patrick Georgi <pgeorgi@google.com> Original-Commit-Id: 2626ecdf5050d02f580a886b03bdaeb892dc4f11 Original-Change-Id: Iefc667ee2f65859f151f5a97b7b9d182e8ed31f7 Original-Signed-off-by: Martin Roth <gaumless@gmail.com> Original-Reviewed-on: https://review.coreboot.org/26390 Original-Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Original-Reviewed-by: Patrick Georgi <pgeorgi@google.com> Reviewed-on: https://chromium-review.googlesource.com/1068866 Commit-Ready: Martin Roth <martinroth@chromium.org> Tested-by: Patrick Georgi <pgeorgi@chromium.org> Reviewed-by: Patrick Georgi <pgeorgi@chromium.org> " fail_count="2" gerrit_number="1068866" owner_email="pgeorgi@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/coreboot" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/coreboot" ref="refs/changes/66/1068866/1" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="Ifa537ac681286443700b7c4d0386396586c31c7b" commit="ef073ec1efaa6bb5c3805b3c6870de269d030e92" commit_message="vm_tools: sommelier: extract gtk-shell code into .c file Move code that implements gtk-shell interface into its own .c file. No change to logic. BUG=chromium:841106 TEST=emerge-tatl termina_container_tools Change-Id: Ifa537ac681286443700b7c4d0386396586c31c7b Reviewed-on: https://chromium-review.googlesource.com/1067091 Commit-Ready: David Reveman <reveman@chromium.org> Tested-by: David Reveman <reveman@chromium.org> Reviewed-by: Stephen Barber <smbarber@chromium.org> " fail_count="2" gerrit_number="1067091" owner_email="reveman@chromium.org" pass_count="0" patch_number="3" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/91/1067091/3" remote="cros" total_fail_count="3"/><pending_commit branch="master" change_id="Ic02478db2d3548c7b1bddedb17efaf674b0f8271" commit="70dece05867241df21dae9a9593f1307819a5041" commit_message="vm_tools: sommelier: implement viewporter interface This allows applications to delegate scaling and cropping to the host compositor. This is useful for efficient video playback. It also allows sommelier to run on top of another sommelier instance without losing proper scaling support. This is useful for debugging purposes. BUG=chromium:841106 TEST=weston-scale works as expected Change-Id: Ic02478db2d3548c7b1bddedb17efaf674b0f8271 Reviewed-on: https://chromium-review.googlesource.com/1067155 Commit-Ready: David Reveman <reveman@chromium.org> Tested-by: David Reveman <reveman@chromium.org> Reviewed-by: Stephen Barber <smbarber@chromium.org> " fail_count="0" gerrit_number="1067155" owner_email="reveman@chromium.org" pass_count="0" patch_number="5" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/55/1067155/5" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="Ie8a2150aca0ccf755d56c15364cc0acf6881cfaf" commit="e19fb49e940c92cbcd7047a933e6a49c9641f9c9" commit_message="vm_tools: Add unit tests for icon_finder.cc. BUG=chromium:822467 TEST=unit tests Change-Id: Ie8a2150aca0ccf755d56c15364cc0acf6881cfaf Reviewed-on: https://chromium-review.googlesource.com/1064791 Commit-Ready: Tim Zheng <timzheng@chromium.org> Tested-by: Tim Zheng <timzheng@chromium.org> Reviewed-by: Stephen Barber <smbarber@chromium.org> " fail_count="1" gerrit_number="1064791" owner_email="timzheng@chromium.org" pass_count="0" patch_number="3" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/91/1064791/3" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="Ic85e20b353afcf65f7ca21af3068b5d279f85565" commit="dc56913d36166965a68614fb627ea115d3b61510" commit_message="Add garcon_icon_finder_test to vm_tools tests. BUG=chromium:822467 TEST=Unit tests. CQ-DEPEND=CL:1064791 Change-Id: Ic85e20b353afcf65f7ca21af3068b5d279f85565 Reviewed-on: https://chromium-review.googlesource.com/1065066 Commit-Ready: Tim Zheng <timzheng@chromium.org> Tested-by: Tim Zheng <timzheng@chromium.org> Reviewed-by: Stephen Barber <smbarber@chromium.org> " fail_count="0" gerrit_number="1065066" owner_email="timzheng@chromium.org" pass_count="0" patch_number="4" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/66/1065066/4" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-4.14" change_id="Ie5a709f0a941c16680724981ea94a9d4dfcdb24a" commit="d9e8a6a318fb6f2109c970a0983d0f770601054b" commit_message="Revert "FROMLIST: drm/dp: Correctly mask DP_TRAINING_AUX_RD_INTERVAL values for DP 1.4" This reverts commit ef1d0d991585027f4f88ecd3fb701889703ed279. Signed-off-by: Matt Atwood <matthew.s.atwood@intel.corp-partner.google.com> BUG=b:70725562 TEST=Boot Nocturne to Graphics Change-Id: Ie5a709f0a941c16680724981ea94a9d4dfcdb24a Reviewed-on: https://chromium-review.googlesource.com/1050490 Commit-Ready: Matthew S Atwood <matthew.s.atwood@intel.corp-partner.google.com> Tested-by: Benson Leung <bleung@chromium.org> Reviewed-by: Dominik Behr <dbehr@chromium.org> Reviewed-by: Stéphane Marchesin <marcheu@chromium.org> " fail_count="0" gerrit_number="1050490" owner_email="matthew.s.atwood@intel.corp-partner.google.com" 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/90/1050490/1" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-4.14" change_id="I9c210579d69b70d4d06a7dba389699149c2142db" commit="630a16eb0ad859d0dad8f574c6e87fd2b90b06f1" commit_message="FROMGIT: drm/dp: Add DP_DPCD_REV_XX to drm_dp_helper As more differentation occurs between DP spec. Its useful to have these as macros in a drm_dp_helper. v2: DPCD_REV_XX to DP_DPCD_REV_XX Signed-off-by: Matt Atwood <matthew.s.atwood@intel.com> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20180504221800.17830-1-matthew.s.atwood@intel.com (cherry picked from commit 0597017cd18dc973ec6c80e55abfa36df05665d6 https://anongit.freedesktop.org/git/drm-tip.git drm-tip) Signed-off-by: Matt Atwood <matthew.s.atwood@intel.corp-partner.google.com> BUG=b:70725562 TEST=Boot Meowth to Graphics Change-Id: I9c210579d69b70d4d06a7dba389699149c2142db Reviewed-on: https://chromium-review.googlesource.com/1050491 Commit-Ready: Matthew S Atwood <matthew.s.atwood@intel.corp-partner.google.com> Tested-by: Benson Leung <bleung@chromium.org> Reviewed-by: Dominik Behr <dbehr@chromium.org> Reviewed-by: Stéphane Marchesin <marcheu@chromium.org> " fail_count="0" gerrit_number="1050491" owner_email="matthew.s.atwood@intel.corp-partner.google.com" 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/91/1050491/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I4e56c44fb6dce3a948f965b8cefd4b3273bc2c31" commit="261b2adc190ef9facb4a3e1c72306e17bb8abe04" commit_message="system_api: use system_api/vm_concierge_proto as go package Match golang protobuf conventions by exporting system_api/vm_concierge to system_api/vm_concierge_proto. BUG=chromium:725692 TEST=emerge system_api CQ-DEPEND=CL:1068132 Change-Id: I4e56c44fb6dce3a948f965b8cefd4b3273bc2c31 Reviewed-on: https://chromium-review.googlesource.com/1068134 Commit-Ready: Stephen Barber <smbarber@chromium.org> Tested-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Dan Erat <derat@chromium.org> " fail_count="0" gerrit_number="1068134" owner_email="smbarber@chromium.org" pass_count="0" patch_number="3" project="chromiumos/overlays/chromiumos-overlay" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/chromiumos-overlay" ref="refs/changes/34/1068134/3" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I5a363e84986f224eca6d6d4aeec618669e60c4e7" commit="5c9fdbe5442de474b4ab089f631cdfda4a63cb0d" commit_message="vm_concierge: export goprotos as system_api/vm_concierge_proto Match golang protobuf conventions by exporting system_api/vm_concierge to system_api/vm_concierge_proto. BUG=chromium:725692 TEST=emerge system_api CQ-DEPEND=CL:1068134 Change-Id: I5a363e84986f224eca6d6d4aeec618669e60c4e7 Reviewed-on: https://chromium-review.googlesource.com/1068132 Commit-Ready: Stephen Barber <smbarber@chromium.org> Tested-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Dan Erat <derat@chromium.org> Reviewed-by: Rahul Chaudhry <rahulchaudhry@chromium.org> " fail_count="0" gerrit_number="1068132" owner_email="smbarber@chromium.org" pass_count="0" patch_number="4" project="chromiumos/platform/system_api" project_url="https://chromium-review.googlesource.com/chromiumos/platform/system_api" ref="refs/changes/32/1068132/4" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I2630a04795e16eb35dcdee46c17db64ba380ca09" commit="6d5c3a2382bca3c4a7d088d0a4eaa3453301798e" commit_message="GS Cache: list member of a tar file This change adds a feature of GS cache server to list all members of a tar file as lines of CSV, e.g. <filename>,<record start>,<record size>,<record end>,<content start>,<content size><content end> ... This feature is useful when we extract files from a tar by using HTTP Range header, e.g. curl -r <content start>-<content end> http://gs-cache/download/path/to/file.tar Another usecase is extracting some of files and re-create another tar file: for f in file_info_list: reader.seek(f.record_start) writer.write(reader.read(r.record_size)) BUG=chromium:824580 TEST=Ran unit tests. Change-Id: I2630a04795e16eb35dcdee46c17db64ba380ca09 Reviewed-on: https://chromium-review.googlesource.com/1047959 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Congbin Guo <guocb@chromium.org> Reviewed-by: Congbin Guo <guocb@chromium.org> " fail_count="2" gerrit_number="1047959" owner_email="guocb@chromium.org" pass_count="0" patch_number="11" project="chromiumos/platform/dev-util" project_url="https://chromium-review.googlesource.com/chromiumos/platform/dev-util" ref="refs/changes/59/1047959/11" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I9f72b51cdcb694ca1f3bce0a039f3c038fc41629" commit="3fea4acf9a4231d8634b14e99398c7a91cb544f9" commit_message="GS Cache: Bind to either network port or socket, not both. Before this change, gs_archive_server cannot just bind to a socket because there is always a default port to listen. This makes it hard to start multiple instances to bind on sockets (because we have to assign ports for all of instanceses even when we don't want to). In this change, I changed the option --socket and --port to be a mutual exclusive group, which means one and only one could be specified. This makes it easier for Puppet to start multiple intances. BUG=chromium:824580 TEST=Ran and verified the sever with different combination of options. Change-Id: I9f72b51cdcb694ca1f3bce0a039f3c038fc41629 Reviewed-on: https://chromium-review.googlesource.com/1067709 Commit-Ready: Congbin Guo <guocb@chromium.org> Tested-by: Congbin Guo <guocb@chromium.org> Reviewed-by: Congbin Guo <guocb@chromium.org> " fail_count="0" gerrit_number="1067709" owner_email="guocb@chromium.org" pass_count="0" patch_number="3" project="chromiumos/platform/dev-util" project_url="https://chromium-review.googlesource.com/chromiumos/platform/dev-util" ref="refs/changes/09/1067709/3" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I64a7fba7fc44d66a4c3de1f0ada1d9ac1ad9d177" commit="93aca392f8994072991424d8e9efccc0dc36c25b" commit_message="metrics: use ScopedTempDir::GetPath() in tests The path() method is deprecated and will be removed from future versions of libchrome. BUG=b:37434548 TEST=unit tests Change-Id: I64a7fba7fc44d66a4c3de1f0ada1d9ac1ad9d177 Reviewed-on: https://chromium-review.googlesource.com/1064973 Commit-Ready: Eric Caruso <ejcaruso@chromium.org> Tested-by: Eric Caruso <ejcaruso@chromium.org> Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org> " fail_count="5" gerrit_number="1064973" owner_email="ejcaruso@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/73/1064973/1" remote="cros" total_fail_count="5"/><pending_commit branch="master" change_id="If08e20538d7c9345224049b4cf0fb98db0401ae1" commit="411fb85c8a168cb8524eb31cdbb487098d2adfd5" commit_message="authpolicy: remove reference to FundamentalValue This is inlined into base::Value now. BUG=b:37434548 TEST=unit tests Change-Id: If08e20538d7c9345224049b4cf0fb98db0401ae1 Reviewed-on: https://chromium-review.googlesource.com/1065125 Commit-Ready: Eric Caruso <ejcaruso@chromium.org> Tested-by: Eric Caruso <ejcaruso@chromium.org> Reviewed-by: Lutz Justen <ljusten@chromium.org> " fail_count="2" gerrit_number="1065125" owner_email="ejcaruso@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/25/1065125/2" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I227dcfac22128389c3d3ab3efdddd045141dff7e" commit="92e610260c929721b66b9752e2b4be8682724853" commit_message="bip: enabled PPC interrupts Need to enable PPC interrupts, otherwise system doesn't work correctly include USB 2.0 not working (since the BC1.2 chip won't be powered after the Vbus change) BRANCH=none BUG=b:79886742 TEST=USB 2.0 works on insertion on C0 on bip Change-Id: I227dcfac22128389c3d3ab3efdddd045141dff7e Signed-off-by: Jett Rink <jettrink@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1066221 Reviewed-by: Aaron Durbin <adurbin@chromium.org> " fail_count="0" gerrit_number="1066221" owner_email="jettrink@chromium.org" pass_count="0" patch_number="3" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/21/1066221/3" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ie9949ca67a005fd32ac7f5511fe89643cec25bba" commit="53ec17bf52fb2e62bc2dade0aec63ede4dc9532b" commit_message="tast-tests: Add User accessor for Chrome struct BUG=chromium:725692 TEST=tast tests build Change-Id: Ie9949ca67a005fd32ac7f5511fe89643cec25bba Reviewed-on: https://chromium-review.googlesource.com/1068207 Commit-Ready: Stephen Barber <smbarber@chromium.org> Tested-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Dan Erat <derat@chromium.org> " fail_count="1" gerrit_number="1068207" owner_email="smbarber@chromium.org" pass_count="0" patch_number="3" project="chromiumos/platform/tast-tests" project_url="https://chromium-review.googlesource.com/chromiumos/platform/tast-tests" ref="refs/changes/07/1068207/3" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I76ec337ebefb2986c1b52af4c4e087b406fa2bdf" commit="7a73397119e7d2953ec2d5aec275dab43c76502f" commit_message="arc-setup: tell crash/ the reason of container upgrade failure The frequency is very low, but crash/ says there are cases where the 'nsenter arcbootcontinue' command fails. This CL tries to tell crash/ whether or not the crash is from nsenter, and not from arcbootcontinue. BUG=chromium:843140 TEST=Add 'kill -9 $CONTAINER_PID &' to arc-boot-continue.conf, confirm the new check catches the container shutdown. Change-Id: I76ec337ebefb2986c1b52af4c4e087b406fa2bdf Reviewed-on: https://chromium-review.googlesource.com/1066287 Commit-Ready: Yusuke Sato <yusukes@chromium.org> Tested-by: Yusuke Sato <yusukes@chromium.org> Reviewed-by: Yusuke Sato <yusukes@chromium.org> Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org> " fail_count="1" gerrit_number="1066287" owner_email="yusukes@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/87/1066287/2" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I510c31bf0acaa121b434e8eb25e7f353be9ab23c" commit="89d7075a30a97492574716dd6ca5ca05c38adb8f" commit_message="power: Do not change wakeup capability for internal kb. This code was primarily added to supress spurious wakes from touchpad and touchscreen(crbug.com/221348, crbug.com/391046). Internal keyboard never seemed to be a problamatic device. Powerd trying to control wake cpabilities on devices that EC enumerates creates complex bugs. So remove the check. Please look at the bug for more info. BUG=chromium:836279 TEST=Tested that EC is still a wake enabled device before sleep. Change-Id: I510c31bf0acaa121b434e8eb25e7f353be9ab23c Signed-off-by: Ravi Chandra Sadineni <ravisadineni@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1069220 Reviewed-by: Dan Erat <derat@chromium.org> " fail_count="1" gerrit_number="1069220" owner_email="ravisadineni@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/20/1069220/1" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I4b76030cef5b5b2f1389999b6dc82d707ee21262" commit="02d1473a339d1b33cb2ed24b1e5b376ea3c5a01e" commit_message="vm_tools: sommelier: Add virtwl DMABuf support. This allows sommelier to use the virtwl DMABuf API to allocate buffers that can be shared with host compositor using the linux_dmabuf protocol. This is done by introducing a new shm driver named 'virtwl-dmabuf'. This driver is also set as the default shm driver on amd64. 'virtwl' is still default on arm. README.md has also been updated to reflect this change. BUG=chromium:837209 TEST=sommelier can allocate and use dmabufs Change-Id: I4b76030cef5b5b2f1389999b6dc82d707ee21262 Reviewed-on: https://chromium-review.googlesource.com/1034220 Commit-Ready: David Reveman <reveman@chromium.org> Tested-by: David Reveman <reveman@chromium.org> Reviewed-by: David Reveman <reveman@chromium.org> Reviewed-by: Stephen Barber <smbarber@chromium.org> " fail_count="0" gerrit_number="1034220" owner_email="reveman@chromium.org" pass_count="0" patch_number="13" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/20/1034220/13" remote="cros" total_fail_count="6"/><pending_commit branch="master" change_id="I764fe0a0a91ae11d8c09f0c15659f62bf77bd00e" commit="3b6a952aae882d2f2f45c9ad7af10bd83ad4577a" commit_message="Provide easy interface to access Android file stat TEST=invoke from the test and see expected return value BUG=None Change-Id: I764fe0a0a91ae11d8c09f0c15659f62bf77bd00e Reviewed-on: https://chromium-review.googlesource.com/1067485 Commit-Ready: Victor Hsieh <victorhsieh@chromium.org> Tested-by: Victor Hsieh <victorhsieh@chromium.org> Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org> " fail_count="0" gerrit_number="1067485" owner_email="victorhsieh@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/85/1067485/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ia7d8ba65855fe4c643aa06f4dc826deb16b05c8c" commit="533f9c518f56f6cb13a891b3a9a3e0e797f69a04" commit_message="Add owner_id to message StartVmRequest Although we can infer owner_id from the rootfs file path, this way is more future proof. Bug: crbug:842561 Change-Id: Ia7d8ba65855fe4c643aa06f4dc826deb16b05c8c Reviewed-on: https://chromium-review.googlesource.com/1068632 Commit-Ready: Nicholas Verne <nverne@chromium.org> Tested-by: Nicholas Verne <nverne@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org> " fail_count="1" gerrit_number="1068632" owner_email="nverne@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/system_api" project_url="https://chromium-review.googlesource.com/chromiumos/platform/system_api" ref="refs/changes/32/1068632/1" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="Id2e51fe5123421f39327e8809c2610c737917ebe" commit="75ba79cc64a21f0bd75c66ad1392a9203e4fdfd6" commit_message="Report stage failures to monarch. Report stage failures with known category and build_config to monarch. This will enable us to alert on high lab failure rate. BUG=chromium:841573 TEST=run_tests Change-Id: Id2e51fe5123421f39327e8809c2610c737917ebe Reviewed-on: https://chromium-review.googlesource.com/1065213 Commit-Ready: Ningning Xia <nxia@chromium.org> Tested-by: Ningning Xia <nxia@chromium.org> Reviewed-by: Ningning Xia <nxia@chromium.org> " fail_count="2" gerrit_number="1065213" owner_email="nxia@chromium.org" pass_count="0" patch_number="6" project="chromiumos/chromite" project_url="https://chromium-review.googlesource.com/chromiumos/chromite" ref="refs/changes/13/1065213/6" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I7136bb54073de9c5951a174c308151b1871c56f3" commit="4754dd120c330cea296816f4dcb2641ad683fb48" commit_message="cr50: Refactor tracking vendor command origin Added flags parameter to extension_route_command(). The caller now specifies whether the command comes from the USB interface or the AP. Moved USB-specific shuffling of response to embed result code into usb_upgrade.c, so extension_route_command() can be more generic. No change to permissions/behavior for existing commands. ccd_command_wrapper() still sends vendor commands as if they come from the AP. That's fixed in the next CL. Reduces code size by 128 bytes BUG=b:79983505 BRANCH=cr50 TEST=manual Build with DEBUG_EXTENSION defined, to turn on printing each command 'ccd lock' comes from AP and works From host, 'gscutil -I' comes from USB and fails From AP, 'gscutil -t -I' comes from AP and works Change-Id: I7136bb54073de9c5951a174c308151b1871c56f3 Signed-off-by: Randall Spangler <rspangler@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1068101 Reviewed-by: Vadim Bendebury <vbendeb@chromium.org> " fail_count="0" gerrit_number="1068101" owner_email="rspangler@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/01/1068101/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I1620ff77e02c1b98038e141fb7cc7039f43c7895" commit="6fe7ac0973258d825c2188977b7624dc3405ad96" commit_message="autotest: wifi: fix broken CAPABILITY_VHT check Two mistakes: - 'self.client.require_capabilities', not self.context.client, since 'self' is the context. - require_capabilities expects a list BUG=chromium:827829 TEST=The below passes of grunt instead of throwing an exception - `test_that -b grunt grunt network_WiFi_SimpleConnect.wifi_check5VHT80_pure` Fixes: 753498b61 ("autotest: wifi: Add checks to support pure VHT80 testing") Change-Id: I1620ff77e02c1b98038e141fb7cc7039f43c7895 Signed-off-by: Kirtika Ruchandani <kirtika@google.com> Reviewed-on: https://chromium-review.googlesource.com/1069413 Commit-Ready: Kirtika Ruchandani <kirtika@chromium.org> Tested-by: Kirtika Ruchandani <kirtika@chromium.org> Reviewed-by: Brian Norris <briannorris@chromium.org> " fail_count="0" gerrit_number="1069413" owner_email="kirtika@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/13/1069413/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I7a0642cbe03c5a0adb6997ddc80c9cb797715749" commit="90fe7d16c46ffb1e1fdc1a3df3a689533f4e84ac" commit_message="chip/stm32/clock: Initialize 'alarm_us' The new GCC build shows a warning/error in clock-f.c: 'alarm_us' may be used uninitialized in this function [-Werror=maybe-uninitialized] This is actually a fake warning. In the context of the logic, there is no way 'alarm_us' would be used uninitialized. But let's still initialize 'alarm_us' to clear the compiler warning. BUG=none BRANCH=scarlet TEST='USE=coreboot-sdk emerge-scarlet chromeos-ec' TEST=make buildall -j Change-Id: I7a0642cbe03c5a0adb6997ddc80c9cb797715749 Signed-off-by: Philip Chen <philipchen@google.com> Reviewed-on: https://chromium-review.googlesource.com/1068256 Commit-Ready: Martin Roth <martinroth@chromium.org> Tested-by: Philip Chen <philipchen@chromium.org> Tested-by: Martin Roth <martinroth@chromium.org> Reviewed-by: Martin Roth <martinroth@chromium.org> " fail_count="0" gerrit_number="1068256" owner_email="philipchen@chromium.org" pass_count="0" patch_number="2" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/56/1068256/2" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I0f118205f7fa66255c6d17ece07c5e81bf88a63f" commit="466d86e08c9b53b7ed963413b69febbd50288ce3" commit_message="kexec-tools: Fix build with clang. Disable integrated assembler to make kexec-tools build with clang. BUG=chromium:844451 TEST=kexec-tools builds wih clang. Change-Id: I0f118205f7fa66255c6d17ece07c5e81bf88a63f Reviewed-on: https://chromium-review.googlesource.com/1069407 Commit-Ready: Manoj Gupta <manojgupta@chromium.org> Tested-by: Manoj Gupta <manojgupta@chromium.org> Reviewed-by: Caroline Tice <cmtice@chromium.org> " fail_count="0" gerrit_number="1069407" owner_email="manojgupta@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/07/1069407/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I0ab42c722e2511cbfa50cab2142baec0906d8263" commit="c327a3748af97abe5019ae14e16ad55fe14701be" commit_message="cleanup: add comment to CONFIG_BATTERY_REVIVE_DISCONNECT When you define CONFIG_BATTERY_REVIVE_DISCONNECT you also need to define battery_get_disconnected_state method() BRANCH=none BUG=none TEST=none Change-Id: I0ab42c722e2511cbfa50cab2142baec0906d8263 Signed-off-by: Jett Rink <jettrink@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1055819 Reviewed-by: Aseda Aboagye <aaboagye@chromium.org> " fail_count="0" gerrit_number="1055819" owner_email="jettrink@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/19/1055819/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I9dd5d18be5f9df0e338e76b072fb82ed2df3e2de" commit="36fae1fb30502d4d5e7fab0c73f2ad6b4eddbd02" commit_message="ec_chip_mchp: Fix bug in GPIO interrupt handling. The previous chip level GPIO itnerrupt change introduced a bug in calculation of the gpio table index. Bug only manifested if GPIOs in different banks were configured for interrupts. BRANCH=none BUG= TEST=Configure board with at least one GPIO interrupt per bank. Check proper handler is called when pin interrupt is triggered. CQ-DEPEND=CL:1053576 Change-Id: I9dd5d18be5f9df0e338e76b072fb82ed2df3e2de Signed-off-by: scott worley <scott.worley@microchip.corp-partner.google.com> Reviewed-on: https://chromium-review.googlesource.com/1053827 Commit-Ready: Randall Spangler <rspangler@chromium.org> Tested-by: Scott Worley <scott.worley@microchip.corp-partner.google.com> Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="0" gerrit_number="1053827" owner_email="scott.worley@microchip.corp-partner.google.com" pass_count="0" patch_number="1" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/27/1053827/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I48b07ecaac2976c5e06e23a4ecf4397ed41c89d1" commit="f5835bbb78fa706ebff5732c9cc51c784d155a85" commit_message="ec_chip_mchp: Clear ADC sticky hardware status before starting. Before starting an ADC conversion clear sticky hardware status in ADC and interrupt aggregator. BRANCH=none BUG= TEST=Build boards using chip mchp and check for spurious ADC interrupts. CQ-DEPEND=CL:1053576 Change-Id: I48b07ecaac2976c5e06e23a4ecf4397ed41c89d1 Signed-off-by: scott worley <scott.worley@microchip.corp-partner.google.com> Reviewed-on: https://chromium-review.googlesource.com/1053867 Commit-Ready: Randall Spangler <rspangler@chromium.org> Tested-by: Scott Worley <scott.worley@microchip.corp-partner.google.com> Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="0" gerrit_number="1053867" owner_email="scott.worley@microchip.corp-partner.google.com" pass_count="0" patch_number="1" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/67/1053867/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I293132fce46cc460d1cf51abacf4b6a494c8c4a3" commit="b0be5445e4d5bdb61cfcb9c851fef45f77f93b36" commit_message="ec_chip_mchp: Lower UART interrupt priority. Reduce UART interrupt priority to not interfere with critical interrupts. WDT highest, GPIO & other HW, UART, Port80(lowest). BRANCH=none BUG= TEST=Build boards based on chip mchp. CQ-DEPEND=CL:1053576 Change-Id: I293132fce46cc460d1cf51abacf4b6a494c8c4a3 Signed-off-by: scott worley <scott.worley@microchip.corp-partner.google.com> Reviewed-on: https://chromium-review.googlesource.com/1053873 Commit-Ready: Randall Spangler <rspangler@chromium.org> Tested-by: Scott Worley <scott.worley@microchip.corp-partner.google.com> Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="0" gerrit_number="1053873" owner_email="scott.worley@microchip.corp-partner.google.com" pass_count="0" patch_number="1" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/73/1053873/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I12709a434d5aaa84fabe459176a3423365343308" commit="5d33b144c2c7586018317b48e9751d4c0ef576c8" commit_message="ec_chip_mchp: Expand data SRAM to 64KB. Observed task stack sizes growing, especially PD related. Adjust chip configuration for 64KB data. Use RAM size config items in flash layout config items. Update SPI image generator python script to not add a Boot-ROM header to EC_RW and add a test mode for debugging SPI read and hash calculations. BRANCH=none BUG= TEST=Build boards based on chip mchp. Check RO and RW EC binaries are correct size and located properly in ec.bin CQ-DEPEND=CL:1036258,CL:1053576 Change-Id: I12709a434d5aaa84fabe459176a3423365343308 Signed-off-by: scott worley <scott.worley@microchip.corp-partner.google.com> Reviewed-on: https://chromium-review.googlesource.com/1053948 Commit-Ready: Randall Spangler <rspangler@chromium.org> Tested-by: Scott Worley <scott.worley@microchip.corp-partner.google.com> Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="0" gerrit_number="1053948" owner_email="scott.worley@microchip.corp-partner.google.com" pass_count="0" patch_number="2" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/48/1053948/2" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I3e08d2f731fa644c3e3253cbca711e1116789b41" commit="230a081982c1f454a09aebd5a2fa86335b521c78" commit_message="ec_chip_mchp: Lower Port80 interrupt priority. Prevent host spew of port 80h writes from impacting servicing more critical interrupts. BRANCH=none BUG= TEST=Build boards based on chip mchp. CQ-DEPEND=CL:1053576 Change-Id: I3e08d2f731fa644c3e3253cbca711e1116789b41 Signed-off-by: scott worley <scott.worley@microchip.corp-partner.google.com> Reviewed-on: https://chromium-review.googlesource.com/1053949 Commit-Ready: Randall Spangler <rspangler@chromium.org> Tested-by: Scott Worley <scott.worley@microchip.corp-partner.google.com> Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="0" gerrit_number="1053949" owner_email="scott.worley@microchip.corp-partner.google.com" pass_count="0" patch_number="1" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/49/1053949/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ibec9ecdd4b67789a468dddfbc1c82565f90d48a8" commit="d613a1bdc5d1da16701fd0e386fc01cb3a774d4d" commit_message="util: do not generate redundant CROS_EC_VERSION The values of CROS_EC_VERSION and VERSION variables generated by getversion.sh are exactly the same. VERSION is used in more places than CROS_EC_VERSION, let's keep VERSION and use it everywhere. BRANCH=none BUG=chromium:632937 TEST=make buildall Change-Id: Ibec9ecdd4b67789a468dddfbc1c82565f90d48a8 Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1069330 Reviewed-by: Randall Spangler <rspangler@chromium.org> " fail_count="0" gerrit_number="1069330" owner_email="vbendeb@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/ec" project_url="https://chromium-review.googlesource.com/chromiumos/platform/ec" ref="refs/changes/30/1069330/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I24bf87fa135b8530d3a3ca171695390adfcb39cc" commit="9fb82cebbb35877fab8d7b273ee939d867622232" commit_message="login: Support TPM firmware updates preserving stateful. This add support for a new update mode to the StartTPMFirmwareUpdate DBus call. It will set up the device to request a TPM firmware update, request encrypted stateful to be preserved, trigger a TPM clear on next reboot, and finally kick off the reboot. BUG=chromium:788719 TEST=New unit test. Change-Id: I24bf87fa135b8530d3a3ca171695390adfcb39cc Reviewed-on: https://chromium-review.googlesource.com/1016764 Commit-Ready: Mattias Nissler <mnissler@chromium.org> Tested-by: Mattias Nissler <mnissler@chromium.org> Reviewed-by: Dan Erat <derat@chromium.org> " fail_count="0" gerrit_number="1016764" owner_email="mnissler@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform2" project_url="https://chromium-review.googlesource.com/chromiumos/platform2" ref="refs/changes/64/1016764/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="Ie86b91ad8c1d86e41a63e40639ad8d8dbebe426a" commit="5279867148fb5017789e8dadd053a713fc0d0d4b" commit_message="metrics: Rename cumulative distribution metric The SecondDistributionMetric has always been cumulative but this was not clear from the name. This has resulted in at least one misuse, and is likely to cause more in the future. The old name is added as a synonym, as an interim measure while it is in transition. BUG=None TEST=Converted unit tests. Change-Id: Ie86b91ad8c1d86e41a63e40639ad8d8dbebe426a Reviewed-on: https://chromium-review.googlesource.com/1066593 Commit-Ready: Jacob Kopczynski <jkop@chromium.org> Tested-by: Jacob Kopczynski <jkop@chromium.org> Reviewed-by: Jacob Kopczynski <jkop@chromium.org> " fail_count="1" gerrit_number="1066593" owner_email="jkop@chromium.org" pass_count="0" patch_number="4" project="chromiumos/chromite" project_url="https://chromium-review.googlesource.com/chromiumos/chromite" ref="refs/changes/93/1066593/4" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I11f9545df698d31e321545104e639ca7d1e3ec23" commit="9d5ca81bb5e6fb21eea2d45cf2903e801bef123e" commit_message="autotest: Convert slave delay to float We care about the delay at a specific time, not the cumulative delay over the course of a period. BUG=chromium:810966 TEST=None Change-Id: I11f9545df698d31e321545104e639ca7d1e3ec23 Reviewed-on: https://chromium-review.googlesource.com/1066927 Commit-Ready: Jacob Kopczynski <jkop@chromium.org> Tested-by: Jacob Kopczynski <jkop@chromium.org> Reviewed-by: Jacob Kopczynski <jkop@chromium.org> " fail_count="1" gerrit_number="1066927" owner_email="jkop@chromium.org" pass_count="0" patch_number="4" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/27/1066927/4" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="Id911494ecae1cdd7b6de733bf7ef0d815f47e240" commit="5f5488c5f6d3db093c4ddc853f39f3e89e7cb13a" commit_message="cros_gdb: support simple chrome This makes cros_gdb work in simple chrome work flow. BUG=chromium:843275 TEST=cros_gdb --board samus --remote ${ip} --attach browser works inside simple chrome chrome-sdk. Change-Id: Id911494ecae1cdd7b6de733bf7ef0d815f47e240 Reviewed-on: https://chromium-review.googlesource.com/1068133 Commit-Ready: Yunlian Jiang <yunlian@chromium.org> Tested-by: Yunlian Jiang <yunlian@chromium.org> Reviewed-by: Manoj Gupta <manojgupta@chromium.org> " fail_count="0" gerrit_number="1068133" owner_email="yunlian@chromium.org" pass_count="0" patch_number="6" project="chromiumos/chromite" project_url="https://chromium-review.googlesource.com/chromiumos/chromite" ref="refs/changes/33/1068133/6" remote="cros" total_fail_count="0"/><pending_commit branch="chromeos-4.4" change_id="I4af3ab742b4dbeb6b29ae9c5c47b4c13142eb2f1" commit="8eabe07b2ceb5df4d8404a8144e16397979f26ef" commit_message="UPSTREAM: PM / devfreq: devm_kzalloc to have dev pointer more precisely devm_kzalloc of devfreq's statistics data structure has been using its parent device as the dev allocated for. If a device's devfreq is disabled in run-time, such allocated memory won't be freed. Desginating more precisely with the devfreq device pointer fixes the issue. Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com> (cherry picked from commit 3e1d7fb0d279fea19eb4e36cc9bddf89264ba03f) BUG=b:74321682, b:73050145 TEST=build for scarlet and boot Change-Id: I4af3ab742b4dbeb6b29ae9c5c47b4c13142eb2f1 Signed-off-by: Matthias Kaehlcke <mka@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1067717 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Reviewed-by: Brian Norris <briannorris@chromium.org> " fail_count="1" gerrit_number="1067717" owner_email="mka@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/17/1067717/1" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="Id520d7a00597a4d514cc48c1cbf9d290f15843c0" commit="00b434a7c9091c607fafff70e82be06535da1d09" commit_message="common_util: Fix IsRunningOnMoblab function to work with nextgen New moblab use -moblab postfix, old moblabs used _moblab Allow this code to work with both TEST=Tested on moblab BUG=chromium:814949 Change-Id: Id520d7a00597a4d514cc48c1cbf9d290f15843c0 Reviewed-on: https://chromium-review.googlesource.com/1067880 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Keith Haddow <haddowk@chromium.org> Reviewed-by: Xixuan Wu <xixuan@chromium.org> " fail_count="1" gerrit_number="1067880" owner_email="haddowk@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/dev-util" project_url="https://chromium-review.googlesource.com/chromiumos/platform/dev-util" ref="refs/changes/80/1067880/1" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="Id5a56a377c2c168e71c9cb64bbbb83fd2ff4180d" commit="706e73c417a2c40dc62779beb423dc2c20508d8e" commit_message="mod_test_image_for_dbusspy: punt This appears to have been dead for a while now, and no one has mentioned caring about it, so punt! BUG=None TEST=precq passes Change-Id: Id5a56a377c2c168e71c9cb64bbbb83fd2ff4180d Reviewed-on: https://chromium-review.googlesource.com/1067969 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org> " fail_count="1" gerrit_number="1067969" owner_email="vapier@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/crosutils" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosutils" ref="refs/changes/69/1067969/1" remote="cros" total_fail_count="1"/><pending_commit branch="chromeos-4.14" change_id="I5c4ca55a945e28d1833ebbd8de93a215bf94bb10" commit="098b65c810ce4a5803d13534c32107badb1e4353" commit_message="FROMGIT: pinctrl: qcom: Print high/low status of gpios in debugfs I was debugging some gpio issues and I thought that the output of gpio debugfs was telling me the high or low level of the gpios with a '1' or a '0'. We saw a line like this though: gpio93 : in 4 2mA pull down and I started to think that there may be a gas leak in the building because '4' doesn't mean high or low, and other pins said '0' or '1'. It turns out, '4' is the function selection for the pinmux of the gpio and not the value on the pin. Reading code helps decipher what debugfs is actually saying. Add support to read the input or output pin depending on how the pin is configured so we can easily see the high or low value of the pin in debugfs. Now the output looks like gpio93 : in low func4 2mA pull down which clearly shows that the pin is an input, low, with function 4 and a 2mA drive strength plus a pull down. Cc: Bjorn Andersson <bjorn.andersson@linaro.org> Cc: Alexandru M Stan <amstan@chromium.org> Signed-off-by: Stephen Boyd <swboyd@chromium.org> Signed-off-by: Linus Walleij <linus.walleij@linaro.org> BUG=None TEST=cat /sys/kernel/debug/gpio on cheza, see 'func' and gpio values Change-Id: I5c4ca55a945e28d1833ebbd8de93a215bf94bb10 Signed-off-by: Stephen Boyd <swboyd@chromium.org> (cherry picked from commit 59a18c24ba4d7bc555e4d8327f26943309f51fa0 git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git devel) Reviewed-on: https://chromium-review.googlesource.com/1068647 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Reviewed-by: Douglas Anderson <dianders@chromium.org> " fail_count="1" gerrit_number="1068647" owner_email="swboyd@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/47/1068647/1" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="Ic38333fa83f0989146028dd732dfbb5078cf5256" commit="2f434cb412592bf71a51b4bcb9024b7932412307" commit_message="eclass: update perl and ruby eclass from upstream. This pulls upstream perl and ruby eclass files so that we can upgrade perl and git. BUG=chromium:840379 TEST=chromiumos-sdk samusl-release Change-Id: Ic38333fa83f0989146028dd732dfbb5078cf5256 Reviewed-on: https://chromium-review.googlesource.com/1062771 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Yunlian Jiang <yunlian@chromium.org> Reviewed-by: Manoj Gupta <manojgupta@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org> " fail_count="3" gerrit_number="1062771" owner_email="yunlian@chromium.org" pass_count="0" patch_number="1" project="chromiumos/overlays/portage-stable" project_url="https://chromium-review.googlesource.com/chromiumos/overlays/portage-stable" ref="refs/changes/71/1062771/1" remote="cros" total_fail_count="3"/><pending_commit branch="master" change_id="I1eb25cf7129b00108d7f4753118e3967eb7abf81" commit="d7a386ca6af51b5b371502d56df5c4fbcfbef85f" commit_message="autotest: Try to fix potential evemu-device process leaks. security_SandboxedServices is failing sporadically due to unexpected evemu-device processes running as root. These look like they're started by the InputPlayback test, and they're presumably being left behind by earlier tests. - Add an __exit__ method to the Keyboard class so it can be used in 'with' blocks. - Make power_Display explicitly close Keyboard. - Make ArcPlayVideoResource, desktopui_CheckRlzPingSent, and ui_AppLauncher explicitly close InputPlayback. Also make security_SandboxedServices include process names in errors. BUG=chromium:795128 TEST=none Change-Id: I1eb25cf7129b00108d7f4753118e3967eb7abf81 Reviewed-on: https://chromium-review.googlesource.com/1067074 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Dan Erat <derat@chromium.org> Reviewed-by: Katherine Threlkeld <kathrelkeld@chromium.org> " fail_count="2" gerrit_number="1067074" owner_email="derat@chromium.org" pass_count="0" patch_number="2" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/74/1067074/2" remote="cros" total_fail_count="2"/><pending_commit branch="master" change_id="I6562b581d8b86c98de3b62c8a7a001343a17e72a" commit="f539e699e63eba72a13f9d1cf13422667b72fc51" commit_message="platform_ToolchainOptions: drop perf binaries from libgcc whitelist perf/trace are no longer compiled with gcc, so we can drop them off the whitelist. BUG=chromium:797835 TEST=Run test on Eve Change-Id: I6562b581d8b86c98de3b62c8a7a001343a17e72a Reviewed-on: https://chromium-review.googlesource.com/1067497 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Dmitry Torokhov <dtor@chromium.org> Reviewed-by: Manoj Gupta <manojgupta@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org> " fail_count="1" gerrit_number="1067497" owner_email="dtor@chromium.org" pass_count="0" patch_number="1" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/97/1067497/1" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="Ia3d3c16c5a686a6c366eadeb0c9f5646e60c5737" commit="791250a012f2fc1c586f3a94476c9a60853a2a9f" commit_message="mod_test_image_for_pyauto.sh: punt We dropped pyauto a while back, so drop this script too. BUG=None TEST=precq passes Change-Id: Ia3d3c16c5a686a6c366eadeb0c9f5646e60c5737 Reviewed-on: https://chromium-review.googlesource.com/1067995 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Mike Frysinger <vapier@chromium.org> Reviewed-by: Richard Barnette <jrbarnette@google.com> " fail_count="1" gerrit_number="1067995" owner_email="vapier@chromium.org" pass_count="0" patch_number="1" project="chromiumos/platform/crosutils" project_url="https://chromium-review.googlesource.com/chromiumos/platform/crosutils" ref="refs/changes/95/1067995/1" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="Ib5e6fc67382a957e4358250a04d96801c637e4cc" commit="048024c934dc5f9463a98a85a10d8408aebf224a" commit_message="arc: Uprev arc-cache-builder-0.2.7 ag/4164398 TEST=Locally eve BUG=b:79209220 Change-Id: Ib5e6fc67382a957e4358250a04d96801c637e4cc Reviewed-on: https://chromium-review.googlesource.com/1069315 Commit-Ready: Yury Khmel <khmel@google.com> Tested-by: Yury Khmel <khmel@google.com> Reviewed-by: Luis Hector Chavez <lhchavez@chromium.org> Reviewed-by: Yury Khmel <khmel@google.com> " fail_count="0" gerrit_number="1069315" owner_email="khmel@google.com" 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/15/1069315/1" remote="cros" total_fail_count="0"/><pending_commit branch="master" change_id="I3c1f28fdc24612ad3bd574cd49865b1833549a90" commit="08b55cbcbaaade354b65fe9b1d4fc27aaf9fb767" commit_message="[autotest] Handle all updating in ChromiumOSUpdater. This moves all business logic of CrosHost.machine_install() into the ChromiumOSUpdater class. BUG=None TEST=run the sanity suite in a local instance Change-Id: I3c1f28fdc24612ad3bd574cd49865b1833549a90 Reviewed-on: https://chromium-review.googlesource.com/1062905 Commit-Ready: Richard Barnette <jrbarnette@chromium.org> Tested-by: Richard Barnette <jrbarnette@chromium.org> Reviewed-by: Xixuan Wu <xixuan@chromium.org> " fail_count="1" gerrit_number="1062905" owner_email="jrbarnette@chromium.org" pass_count="0" patch_number="4" project="chromiumos/third_party/autotest" project_url="https://chromium-review.googlesource.com/chromiumos/third_party/autotest" ref="refs/changes/05/1062905/4" remote="cros" total_fail_count="6"/><pending_commit branch="master" change_id="Ic774270de2d4ba097911dc55c3ed4794472d0e3a" commit="7f39e3f90170fb133b2beef18b5b11a053616465" commit_message="chromeos_config: Add non-important nyan_blaze paladin. To avoid add too many release/pfq/tryjob configs, choose to launch nyan_blaze to test non-important CQ first. BUG=chromium:845314 TEST=None Change-Id: Ic774270de2d4ba097911dc55c3ed4794472d0e3a Reviewed-on: https://chromium-review.googlesource.com/1068119 Commit-Ready: Xixuan Wu <xixuan@chromium.org> Tested-by: Xixuan Wu <xixuan@chromium.org> Reviewed-by: Ningning Xia <nxia@chromium.org> " fail_count="1" gerrit_number="1068119" owner_email="xixuan@chromium.org" pass_count="0" patch_number="2" project="chromiumos/chromite" project_url="https://chromium-review.googlesource.com/chromiumos/chromite" ref="refs/changes/19/1068119/2" remote="cros" total_fail_count="1"/><pending_commit branch="master" change_id="I332aefc995a4195a734a98e00a380328c6682113" commit="74db1741d701046d40bf919125f04928e645e141" commit_message="Add tests touch_GestureNav to ebuild BUG=None TEST=Tested against lab hosts Change-Id: I332aefc995a4195a734a98e00a380328c6682113 Reviewed-on: https://chromium-review.googlesource.com/1068076 Commit-Ready: Kalin Stoyanov <kalin@chromium.org> Tested-by: Kalin Stoyanov <kalin@chromium.org> Reviewed-by: Harpreet Grewal <harpreet@chromium.org> " fail_count="0" gerrit_number="1068076" owner_email="kalin@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/76/1068076/1" remote="cros" total_fail_count="0"/><lkgm version="10706.0.0-rc1"/></manifest> |
