Control: tag - moreinfo unreproducible Control: tag + confirmed
Ok, based on all the above and my own testing, I'm marking this one as confirmed. I can't say it is a bug per se, - qemu is doing what real hardware is doing. It is not its fault that every host cpu can't do the same pointer auth in hardware as aarch64 cpu does, and so qemu have to emulate that stuff, which requires additional cpu time. But it is not friendly to the users, either, obviously. Especially since it's difficult to find out which config has to be tweaked and how. I'll disable pauth by default for qemu-user in the next upload to debian. For qemu-system (qemu-system-aarch64), which is affected the same way, things are much more involved, since qemu-system guest has to be migratable between qemu versions, and this is a migration property which can't be just changed at will. Also, it is not clear to me what to do with qemu in trixie, - since it is trixie code which made heavy use of pauth and is affected, and the trixie version of qemu executes this trixie code very slowly. I might back-port this change to trixie too, - haven't decided yet. Thanks, /mjt
