> handle_riprel_insn() returns 0 if the instruction is not rip-relative > returns 1 if its rip-relative but can use XOL slots. > returns -1 if its rip-relative but cannot use XOL. > > We dont see any instructions that are rip-relative and cannot use XOL. > so the check and return are redundant and I will remove that in the next > patch. How is that? You can only adjust a rip-relative instruction correctly if the instruction copy is within 2GB of the original target address, which cannot be presumed to always be the case in user address space layout (unlike the kernel). Thanks, Roland -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx"> email@xxxxxxxxx </a>