lkml.org 
[lkml]   [2022]   [Jan]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 10/26] x86/tdx: Support TDX guest port I/O at decompression time
On Wed, Jan 19, 2022 at 08:46:24PM +0100, Borislav Petkov wrote:
> On Wed, Jan 19, 2022 at 06:49:25PM +0300, Kirill A. Shutemov wrote:
> > const struct port_io_ops default_pio_ops = {
> > .inb = inb,
> > .inw = inw,
> > .inl = inl,
> > .outb = outb,
> > .outw = outw,
> > .outl = outl,
> > };
> >
> > make pio_ops a pointer and assign it here:
> >
> > pio_ops = &default_pio_ops;
> >
> > But it leads to an issue on linking:
> >
> > ld.lld: error: Unexpected run-time relocations (.rela) detected!
>
> So the above generates absolute relocations of type R_X86_64_64
>
> Relocation section '.rela.data.rel.local' at offset 0x5c18 contains 6 entries:
> Offset Info Type Sym. Value Sym. Name + Addend
> 000000000000 000200000001 R_X86_64_64 0000000000000000 .text + 10
> 000000000008 000200000001 R_X86_64_64 0000000000000000 .text + 30
> 000000000010 000200000001 R_X86_64_64 0000000000000000 .text + 50
> 000000000018 000200000001 R_X86_64_64 0000000000000000 .text + 0
> 000000000020 000200000001 R_X86_64_64 0000000000000000 .text + 20
> 000000000028 000200000001 R_X86_64_64 0000000000000000 .text + 40
>
> and the linker doesn't like them probably because of the mcmodel we use
> but I need to talk to toolchain folks first to make sense of what's
> going on...

JFYI, the message comes from ASSERT in vmlinux.lds.S.

I assume for now I can proceed with the assignment that works, right?
It can be changed later once we figure out what is going on.

--
Kirill A. Shutemov

\
 
 \ /
  Last update: 2022-01-19 21:09    [W:0.143 / U:0.216 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site