[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Xen-devel] Re: [PATCH][RFC] jump_labels/x86: Use either 5 byte or 2 byte jumps
- To: Jason Baron <jbaron@xxxxxxxxxx>
- From: Steven Rostedt <rostedt@xxxxxxxxxxx>
- Date: Fri, 07 Oct 2011 15:33:08 -0400
- Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, the arch/x86 maintainers <x86@xxxxxxxxxx>, Jeremy Fitzhardinge <jeremy.fitzhardinge@xxxxxxxxxx>, David Daney <david.daney@xxxxxxxxxx>, peterz@xxxxxxxxxxxxx, Jan Glauber <jang@xxxxxxxxxxxxxxxxxx>, Michael, Richard Henderson <rth@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Ellerman <michael@xxxxxxxxxxxxxx>, Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>
- Delivery-date: Fri, 07 Oct 2011 12:34:54 -0700
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
On Fri, 2011-10-07 at 15:21 -0400, Steven Rostedt wrote:
> > > + /*
> > > + * This is specific to x86. The jump_table is stored in three
> > > + * long words. The first is the location of the jmp target we
> > > + * must update.
> > > + */
> > > + cnt = size / sizeof(uint_t);
> > > +
> > > + for (i = 0; i < cnt; i += 3)
> > > + if (0)make_nop((void *)ehdr, *(uint_t *)(data + i *
> > > sizeof(uint_t)));
I just compiled and booted the
- if (0)make_nop((void *)ehdr, *(uint_t *)(data + i *
sizeof(uint_t)));
+ make_nop((void *)ehdr, *(uint_t *)(data + i * sizeof(uint_t)));
version, and it still works.
Phew!
-- Steve
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
