Displaying 2 results from an estimated 2 matches for "write_lgt_entry".
Did you mean:
write_ldt_entry
2007 Apr 18
0
someone screwed something up
...ignment from incompatible pointer type
>
> paravirt_ops.write_ldt_entry = lguest_write_ldt_entry;
> paravirt_ops.write_gdt_entry = lguest_write_gdt_entry;
> paravirt_ops.write_idt_entry = lguest_write_idt_entry;
And here it is:
==
The prototype for paravirt_ops write_lgt_entry, write_gdt_entry and
write_idt_entry was type-corrected, so change lguest to match. We can
also use the "write_dt_entry" which was exported by that same cleanup
patch, rather than write our own.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
diff -r f52fef6a1f2d arch/i386/l...
2007 Apr 18
0
someone screwed something up
...ignment from incompatible pointer type
>
> paravirt_ops.write_ldt_entry = lguest_write_ldt_entry;
> paravirt_ops.write_gdt_entry = lguest_write_gdt_entry;
> paravirt_ops.write_idt_entry = lguest_write_idt_entry;
And here it is:
==
The prototype for paravirt_ops write_lgt_entry, write_gdt_entry and
write_idt_entry was type-corrected, so change lguest to match. We can
also use the "write_dt_entry" which was exported by that same cleanup
patch, rather than write our own.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
diff -r f52fef6a1f2d arch/i386/l...