From: Andrew Cooper <Andrew.Cooper3@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Ranconfig failure between VT-d and HVM
Date: Wed, 20 Apr 2022 18:01:20 +0000 [thread overview]
Message-ID: <4095a567-86aa-8311-ed92-730348ab43d3@citrix.com> (raw)
In-Reply-To: <9537f2bf-981c-d4ac-d41d-ab59f7d7ab2c@citrix.com>
On 20/04/2022 18:49, Andrew Cooper wrote:
> https://gitlab.com/xen-project/people/andyhhp/xen/-/jobs/2355562119
>
> ld: prelink.o: in function `vtd_setup':
> drivers/passthrough/vtd/iommu.c:(.init.text+0x219f6): undefined
> reference to `opt_hap_2mb'
> drivers/passthrough/vtd/iommu.c:(.init.text+0x219f6): relocation
> truncated to fit: R_X86_64_PC32 against undefined symbol `opt_hap_2mb'
> ld: drivers/passthrough/vtd/iommu.c:(.init.text+0x21a23): undefined
> reference to `opt_hap_1gb'
> drivers/passthrough/vtd/iommu.c:(.init.text+0x21a23): relocation
> truncated to fit: R_X86_64_PC32 against undefined symbol `opt_hap_1gb'
> ld: ./.xen-syms.0: hidden symbol `opt_hap_2mb' isn't defined
> ld: final link failed: bad value
> make[3]: *** [arch/x86/Makefile:137: xen-syms] Error 1
>
> It's really not clear why this has first show up now. There has been a
> huge quantity of noise in Gitlab CI for the past 3 weeks with ARM being
> offline, but I can't see anything relevant in the large number of IOMMU
> changes in that period.
>
> Anyway, the issue is simple. It's vtd_ept_page_compatible() in a
> !CONFIG_HVM build.
And just after sending, I realised it's not an IOMMU change.
commit c479415610f0448bb07d39185e72ef36e08ebec0
Author: Jan Beulich <jbeulich@suse.com>
Date: Fri Apr 8 13:50:29 2022
x86/P2M: p2m.c is HVM-only
CI disputes the claim.
~Andrew
next prev parent reply other threads:[~2022-04-20 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 17:49 Ranconfig failure between VT-d and HVM Andrew Cooper
2022-04-20 18:01 ` Andrew Cooper [this message]
2022-04-21 8:32 ` Jan Beulich
2022-04-21 14:12 ` Jan Beulich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4095a567-86aa-8311-ed92-730348ab43d3@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.