diff options
| author | Slava Malyugin <slavamn@google.com> | 2018-07-03 21:01:03 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2018-07-09 12:42:42 -0700 |
| commit | ac5a8dbe505daf95a802cc606988bc2323087a05 (patch) | |
| tree | 670823310e13005629ea86d90625c28789802199 /gpu_display | |
| parent | ef7352f20828fbe3f7498b4bed231deb98c3da9c (diff) | |
| download | crosvm-ac5a8dbe505daf95a802cc606988bc2323087a05.tar crosvm-ac5a8dbe505daf95a802cc606988bc2323087a05.tar.gz crosvm-ac5a8dbe505daf95a802cc606988bc2323087a05.tar.bz2 crosvm-ac5a8dbe505daf95a802cc606988bc2323087a05.tar.lz crosvm-ac5a8dbe505daf95a802cc606988bc2323087a05.tar.xz crosvm-ac5a8dbe505daf95a802cc606988bc2323087a05.tar.zst crosvm-ac5a8dbe505daf95a802cc606988bc2323087a05.zip | |
x86_64: fill cache info in cpuid, stop spoofing CPU vendor id
The fix passes through cache-related CPU entries 2, 4, 0x80000005 and 0x80000006 similar to how QEMU does it. Note passing this cpuid info itself is not sufficient unless CPU vendor is something Linux kernel recognizes. Therefore, I am removing cute spoofing of the vendor id, allowing host value to pass through. I believe it is generally a bad idea to spoof vendor id as lots of kernel and user space code gets confused and may take unoptimized paths. The corollary is that removing the spoofing may have unintended consequences correctness- and performance-wise. I would appreciate recommendation on additional testing. BUG=chromium:859678 TEST=lscpu in Guest, 'cargo test' Change-Id: I6963b00d9eecf49fb4578bcc75ad744c3099f045 Reviewed-on: https://chromium-review.googlesource.com/1125529 Commit-Ready: Slava Malyugin <slavamn@chromium.org> Tested-by: Slava Malyugin <slavamn@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org>
Diffstat (limited to 'gpu_display')
0 files changed, 0 insertions, 0 deletions