Reading that diff, I get a sense they pass on underlying-hardware cpu flags as-is, and then only write the support code when they feel like it.
If so, that is ridiculous. They should immediately mask against a list of KNOWN and CURRENTLY SUPPORTED bits, and not pass on unknown stuff. SASANO Takayoshi <[email protected]> wrote: > > 1) Broken emulator > > 2) Old broken emulator > > > > A real cpu behaves that way. The capability bits says the feature > > exists, and when it exists, it MUST work. > > Yes, I think KVM/QEMU may be malfunction and I found a patch for > QEMU that supports MSR_TSX_CTRL. > > https://www.mail-archive.com/[email protected]/msg660546.html > > > Have you have filed a bug with the authors of the emulator? > > So I didn't write any bug report to them. > > > If newer code emulators have it fixed, then again, how is this our > > fault for using the feature as advertised in all real hardware? > > It may be no problem that running KVM/QEMU locally (simply install new > emulator by myself), but I found this MSR_TSX_CTRL problem on VPS service. > > I understand that I have to consult support desk of the service provider and > ask them to update QEMU. > > Regards, > -- > SASANO Takayoshi (JG1UAA) <[email protected]>
