Chris Wright wrote:
* Zachary Amsden ([email protected]) wrote:
+static void fixup_translation(struct vmi_annotation *a)
+{
+ unsigned char *c, *start, *end;
+ int left;
+
+ memcpy(a->nativeEIP, a->translationEIP, a->translation_size);
+ start = a->nativeEIP;
+ end = a->nativeEIP + a->translation_size;
+
+ for (c = start; c < end;) {
+ switch(*c) {
+ case MNEM_CALL_NEAR:
Why these restrictions? How do you do int $0x82, for example?
We don't. This is the minimal set of instructions that are emitted
during the annotation. The instruction sequence is only sufficient to
call out to the hypervisor ROM.
What we want to do next is to allow the hypervisor itself to do this
code fixup - in effect, relinking in the local translations, which in
many cases would then convert to int $0x82 for inline Xen calls.
Zach
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
