From: "Arnd Bergmann" <arnd@arndb.de>
To: "Sean Christopherson" <seanjc@google.com>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Dave Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Imre Deak" <imre.deak@intel.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i915: fix DRM_I915_GVT_KVMGT dependencies
Date: Thu, 17 Oct 2024 05:11:37 +0000 [thread overview]
Message-ID: <6201c467-e5f2-4aa1-967c-8d9116c5367a@app.fastmail.com> (raw)
In-Reply-To: <ZxBZx5EUhJFjTcXP@google.com>
On Thu, Oct 17, 2024, at 00:26, Sean Christopherson wrote:
> On Tue, Oct 15, 2024, Arnd Bergmann wrote:
>> diff --git a/drivers/gpu/drm/i915/Kconfig b/drivers/gpu/drm/i915/Kconfig
>> index 46301c06d18a..985cb78d8256 100644
>> --- a/drivers/gpu/drm/i915/Kconfig
>> +++ b/drivers/gpu/drm/i915/Kconfig
>> @@ -118,9 +118,8 @@ config DRM_I915_USERPTR
>> config DRM_I915_GVT_KVMGT
>> tristate "Enable KVM host support Intel GVT-g graphics virtualization"
>> depends on DRM_I915
>> - depends on X86
>> + depends on KVM_X86
>
> Can GVT-g even work on non-Intel CPUs? I.e. would it make sense to take a
> dependency on KVM_INTEL?
>
Yes, I think that should work, but I'm not sure if it needs a dependency
on both KVM_INTEL and KVM_X86 in that case, to handle the link-time
dependency in all configurations.
Arnd
next prev parent reply other threads:[~2024-10-17 5:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 15:21 Arnd Bergmann
2024-10-17 0:26 ` Sean Christopherson
2024-10-17 5:11 ` Arnd Bergmann [this message]
2024-10-17 16:54 ` Rodrigo Vivi
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=6201c467-e5f2-4aa1-967c-8d9116c5367a@app.fastmail.com \
--to=arnd@arndb.de \
--cc=airlied@gmail.com \
--cc=arnd@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert+renesas@glider.be \
--cc=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=pbonzini@redhat.com \
--cc=rodrigo.vivi@intel.com \
--cc=seanjc@google.com \
--cc=simona@ffwll.ch \
--cc=tursulin@ursulin.net \
/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
all inboxes | Powered by JetHome®