Messages in this thread | | | Date | Tue, 16 Nov 2004 09:56:34 +0000 (GMT) | From | Hugh Dickins <> | Subject | Re: [PATCH] WTF is VLI? |
| |
On Tue, 16 Nov 2004, Keith Owens wrote: > > ksymoops has to work with lots of different log formats from lots of > different architectures. Some arch's already print the code around the > oops and enclose the failing instruction in <> or [], some do not. > > Just looking at a code string, you cannot tell if the arch has variable > length instructions or not (don't forget that ksymoops also works cross > architecture). The VLI tag will work for _all_ architectures that have > variable length instructions, not just i386. At the very least, s390 > can use it as well.
But, to an outsider, it seems that the "VLI" can only be relevant when disassembling the "Code:", and surely each arch disassembler knows already if it's dealing with Variable Length Instructions.
No big deal, just odd. I've no wish to add to ksymoops's difficulties.
Hugh
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |