David Laight wrote:
The in_le32() not only contains the unwanted 'sync', but also a 'twi' (trap immediate - NFI exactly what this does) and 'isync'. The 'isync' is particularly horrid and unnecessary (aborts the instruction queue and refeches the opcode bytes).
I've also wondered why some time ago, and this is what I could find: it's a special sequence that is detected by the bus error handler (machine check exception happens on I/O error i.e. aborted pci transaction or some such), so that it can 'recover' by continuing at the next instruction (and setting an error variable).
Perhaps there is no other way to recover reliably from bus errors? Micha -- To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
