From: "Du, Changbin" <changbin.du@intel.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: airlied@linux.ie, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, daniel.vetter@intel.com,
intel-gvt-dev@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: prevent generating unusable gvt build which no mpt module is selected
Date: Thu, 25 May 2017 14:09:44 +0800 [thread overview]
Message-ID: <20170525060944.GA25623@intel.com> (raw)
In-Reply-To: <87efvetrl1.fsf@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 3002 bytes --]
Hi, Jani, just relized you are in i915 team. :)
> > +menu "Intel GVT-g graphics virtualization host support"
> > + depends on DRM_I915
> > + depends on 64BIT
> > +
> > config DRM_I915_GVT
> > - bool "Enable Intel GVT-g graphics virtualization host support"
> > - depends on DRM_I915
> > - depends on 64BIT
> > - default n
> > - help
> > + bool "Enable Intel GVT-g graphics virtualization host support"
> > + default n
> > + depends on DRM_I915_GVT_KVMGT
> > + help
>
> With this change, you can't actually change this config option. It's
> purely subject to CONFIG_DRM_I915_GVT_KVMGT. You need to enable KVMGT to
> even see this option, but enabling it will enable this one too. You
> can't disable this before you disable KVMGT, but then disabling KVMGT
> will disable this one too. This config option becomes pointless as a
> visible option. Which isn't all that bad, considering
> Documentation/kbuild/kconfig-language.txt:
>
Jani, this is by design in this patch. We will add another xengt hypervisor glue
layer to support XenGT. After that, enable DRM_I915_GVT only if at least one of
KVMGT or XENGT enabled or both. Also it doesn't make sense that we only build
KVMGT/XenGT module without DRM_I915_GVT.
Such mechanism is not as straigforward as two simple 'choice', so I agree with
'choice' if you prefer it. As you said, it is not a big problem.
> Note:
> select should be used with care. select will force
> a symbol to a value without visiting the dependencies.
> By abusing select you are able to select a symbol FOO even
> if FOO depends on BAR that is not set.
> In general use select only for non-visible symbols
> (no prompts anywhere) and for symbols with no dependencies.
> That will limit the usefulness but on the other hand avoid
> the illegal configurations all over.
>
Yes, we should always be carefull with 'select' and should not use it if
possible. So here I must create a 'menu' to ensure its safety.
> BR,
> Jani.
>
> > Choose this option if you want to enable Intel GVT-g graphics
> > virtualization technology host support with integrated graphics.
> > With GVT-g, it's possible to have one integrated graphics
> > @@ -116,13 +119,14 @@ config DRM_I915_GVT
> >
> > config DRM_I915_GVT_KVMGT
> > tristate "Enable KVM/VFIO support for Intel GVT-g"
> > - depends on DRM_I915_GVT
> > + select DRM_I915_GVT
> > depends on KVM
> > depends on VFIO_MDEV && VFIO_MDEV_DEVICE
> > default n
> > help
> > Choose this option if you want to enable KVMGT support for
> > Intel GVT-g.
> > +endmenu
> >
> > menu "drm/i915 Debugging"
> > depends on DRM_I915
>
> --
> Jani Nikula, Intel Open Source Technology Center
> _______________________________________________
> intel-gvt-dev mailing list
> intel-gvt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gvt-dev
--
Thanks,
Changbin Du
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-05-25 6:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 8:50 [PATCH] drm/i915: prevent generating unusable gvt build which no mpt module is selected changbin.du
2017-05-24 9:17 ` Zhenyu Wang
2017-05-24 9:21 ` Chris Wilson
2017-05-24 9:36 ` Du, Changbin
2017-05-24 9:57 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-05-24 11:35 ` [PATCH] " Jani Nikula
2017-05-25 6:09 ` Du, Changbin [this message]
2017-05-26 9:58 ` Jani Nikula
2017-05-26 10:27 ` Du, Changbin
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=20170525060944.GA25623@intel.com \
--to=changbin.du@intel.com \
--cc=airlied@linux.ie \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=jani.nikula@linux.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;
as well as URLs for NNTP newsgroup(s).