[lkml]   [2017]   [Oct]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Xen-devel] [PATCH 11/13] x86/paravirt: Add paravirt alternatives infrastructure
On 10/17/2017 09:10 AM, Brian Gerst wrote:
> On Mon, Oct 16, 2017 at 2:18 PM, Boris Ostrovsky
> <> wrote:
>> Replacing the macro with
>> #define PV_INDIRECT(addr) *addr // well, it's not so much
>> indirect anymore
>> makes things work. Or maybe it can be adjusted top be kept truly indirect.
> That is still an indirect call, just using absolute addressing for the
> pointer instead of RIP-relative.

Oh, right, I've got my terminology all wrong.


> Alternatives has very limited
> relocation capabilities. It will only handle a single call or jmp
> replacement. Using absolute addressing is slightly less efficient
> (takes one extra byte to encode, and needs a relocation for KASLR),
> but it works just as well. You could also relocate the instruction
> manually by adding the delta between the original and replacement code
> to the displacement.

 \ /
  Last update: 2017-10-17 16:07    [W:0.101 / U:3.808 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site