From: "Wang, Zhi A" <zhi.a.wang@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"intel-gvt-dev@lists.freedesktop.org"
<intel-gvt-dev@lists.freedesktop.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Intel-gfx] [PULL] gvt-next
Date: Tue, 26 Apr 2022 16:58:33 +0000 [thread overview]
Message-ID: <e245c195-fdb0-32c4-dcfb-8ff49bc3a63c@intel.com> (raw)
In-Reply-To: <20220426155318.GQ2125828@nvidia.com>
On 4/26/22 3:53 PM, Jason Gunthorpe wrote:
> On Tue, Apr 26, 2022 at 07:58:59AM +0000, Wang, Zhi A wrote:
>> Hi folks:
>>
>> Here is the pull of gvt-next which fixs the compilation error when i915 debug
>> is open after the GVT-g refactor patches.
>>
>> Thanks so much for the efforts.
>>
>> Thanks,
>> Zhi.
>>
>> The following changes since commit 2917f53113be3b7a0f374e02cebe6d6b749366b5:
>>
>> vfio/mdev: Remove mdev drvdata (2022-04-21 07:36:56 -0400)
>>
>> are available in the Git repository at:
>>
>> https://github.com/intel/gvt-linux tags/gvt-next-2022-04-26
>>
>> for you to fetch changes up to 2da299cee780ea797b3f72558687868072cf5eb5:
>>
>> drm/i915/gvt: Add missing export of symbols. (2022-04-25 18:03:04 -0400)
>>
>> gvt-next-2022-04-26
>>
>> - Add two missing exports of symbols when i915 debug is enabled.
>>
>> Zhi Wang (1):
>> drm/i915/gvt: Add missing export of symbols.
>>
>> drivers/gpu/drm/i915/intel_gvt.c | 2 ++
>> 1 file changed, 2 insertions(+)
>
> This still has another compile problem:
>
> ERROR: modpost: "intel_runtime_pm_put" [vmlinux] is a static EXPORT_SYMBOL_GPL
>
> Because:
>
> #if IS_ENABLED(CONFIG_DRM_I915_DEBUG_RUNTIME_PM)
> void intel_runtime_pm_put(struct intel_runtime_pm *rpm, intel_wakeref_t wref);
> #else
> static inline void
> intel_runtime_pm_put(struct intel_runtime_pm *rpm, intel_wakeref_t wref)
> {
> intel_runtime_pm_put_unchecked(rpm);
> }
> #endif
>
> Looks like it happens if CONFIG_DRM_I915_DEBUG_RUNTIME_PM=n
>
> I think you probably want to #ifdef the export in the same way:
>
> --- a/drivers/gpu/drm/i915/intel_gvt.c
> +++ b/drivers/gpu/drm/i915/intel_gvt.c
> @@ -309,7 +309,9 @@ EXPORT_SYMBOL_NS_GPL(__intel_context_do_pin, I915_GVT);
> EXPORT_SYMBOL_NS_GPL(__intel_context_do_unpin, I915_GVT);
> EXPORT_SYMBOL_NS_GPL(intel_ring_begin, I915_GVT);
> EXPORT_SYMBOL_NS_GPL(intel_runtime_pm_get, I915_GVT);
> +#if IS_ENABLED(CONFIG_DRM_I915_DEBUG_RUNTIME_PM)
> EXPORT_SYMBOL_NS_GPL(intel_runtime_pm_put, I915_GVT);
> +#endif
Sigh. That's tricky. Let me prepare another one.
> EXPORT_SYMBOL_NS_GPL(intel_runtime_pm_put_unchecked, I915_GVT);
> EXPORT_SYMBOL_NS_GPL(intel_uncore_forcewake_for_reg, I915_GVT);
> EXPORT_SYMBOL_NS_GPL(intel_uncore_forcewake_get, I915_GVT);
>
> Jason
>
next prev parent reply other threads:[~2022-04-26 16:58 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 7:58 [Intel-gfx] [PULL] gvt-next Wang, Zhi A
2022-04-26 8:37 ` Jani Nikula
2022-04-26 8:38 ` Wang, Zhi A
2022-04-26 8:42 ` Wang, Zhi A
2022-04-26 11:52 ` Jason Gunthorpe
2022-04-28 21:35 ` Alex Williamson
2022-04-28 21:48 ` Alex Williamson
2022-04-26 15:53 ` Jason Gunthorpe
2022-04-26 16:58 ` Wang, Zhi A [this message]
2022-04-26 19:19 ` Robert Beckett
2022-04-26 15:56 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for gvt-next (rev2) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-11-11 8:59 [Intel-gfx] [PULL] gvt-next Zhenyu Wang
2022-11-15 15:36 ` Rodrigo Vivi
2022-11-17 3:02 ` Zhenyu Wang
2022-11-17 3:37 ` Vivi, Rodrigo
2022-11-17 5:28 ` Zhenyu Wang
2022-11-17 6:41 ` Zhenyu Wang
2022-11-17 13:49 ` Rodrigo Vivi
2022-04-20 8:04 Wang, Zhi A
2022-04-20 12:13 ` Jason Gunthorpe
2022-04-20 14:41 ` Wang, Zhi A
2022-04-20 15:02 ` Jason Gunthorpe
2022-04-20 16:13 ` Wang, Zhi A
2021-03-16 7:43 Zhenyu Wang
2021-03-16 11:52 ` Jani Nikula
2020-11-23 9:05 Zhenyu Wang
2020-11-23 9:32 ` Joonas Lahtinen
2020-11-24 3:13 ` Zhenyu Wang
2020-11-24 9:48 ` Jani Nikula
2020-11-27 13:26 ` Joonas Lahtinen
2020-09-10 5:37 Zhenyu Wang
2020-09-11 23:58 ` Rodrigo Vivi
2020-09-14 2:34 ` Zhenyu Wang
2020-09-14 18:39 ` Vivi, Rodrigo
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=e245c195-fdb0-32c4-dcfb-8ff49bc3a63c@intel.com \
--to=zhi.a.wang@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hch@lst.de \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox