Summary: | (cli, sti) vex amd64->IR: unhandled instruction bytes: 0xFA 0xC7 0x45 0xFC | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Yousong Mei <YousongMei> |
Component: | vex | Assignee: | Julian Seward <jseward> |
Status: | REPORTED --- | ||
Severity: | crash | CC: | njn |
Priority: | NOR | ||
Version: | 3.2.1 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Bug Depends on: | |||
Bug Blocks: | 253451 |
Description
Yousong Mei
2006-09-21 23:54:08 UTC
What do cli and sti do in user-mode? I can see the kernel might want to use them, but in user-mode what are they for? It's possible to use them in usermode if the process has used iopl() get access to them. But its pretty rare, and they're pretty much impossible to use correctly in general. The big offender used to be the X server, but I don't think it does any more. You could probably implement them as no-ops without any loss of generality. (But if you did, I bet the next report will be that in/out are not implemented.) In our case, we try to measure some timing and we do not want to interrupt to happen when we measure the timing, which will skew the result. Thanks. At 03:36 PM 9/21/2006, Julian Seward wrote: [bugs.kde.org quoted mail] |