From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Matthew Auld <matthew.auld@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gemfs: don't mark huge_opt as static
Date: Fri, 26 Nov 2021 12:20:47 +0000 [thread overview]
Message-ID: <398b3993-804d-2f7f-8a53-b3452f444cbc@linux.intel.com> (raw)
In-Reply-To: <20211126110843.2028582-1-matthew.auld@intel.com>
On 26/11/2021 11:08, Matthew Auld wrote:
> vfs_kernel_mount() modifies the passed in mount options, leaving us with
> "huge", instead of "huge=within_size". Normally this shouldn't matter
> with the usual module load/unload flow, however with the core_hotunplug
> IGT we are hitting the following, when re-probing the memory regions:
Doh and thanks for fixing it. I obviously figured out it changes the
string but did not grasp all the consequences.
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
> i915 0000:00:02.0: [drm] Transparent Hugepage mode 'huge'
> tmpfs: Bad value for 'huge'
> [drm] Unable to create a private tmpfs mount, hugepage support will be disabled(-22).
>
> References: https://gitlab.freedesktop.org/drm/intel/-/issues/4651
> Signed-off-by: Matthew Auld <matthew.auld@intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> ---
> drivers/gpu/drm/i915/gem/i915_gemfs.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gem/i915_gemfs.c b/drivers/gpu/drm/i915/gem/i915_gemfs.c
> index dbdbdc344d87..182da3c04771 100644
> --- a/drivers/gpu/drm/i915/gem/i915_gemfs.c
> +++ b/drivers/gpu/drm/i915/gem/i915_gemfs.c
> @@ -12,6 +12,7 @@
>
> int i915_gemfs_init(struct drm_i915_private *i915)
> {
> + char huge_opt[] = "huge=within_size"; /* r/w */
> struct file_system_type *type;
> struct vfsmount *gemfs;
> char *opts;
> @@ -33,8 +34,6 @@ int i915_gemfs_init(struct drm_i915_private *i915)
> opts = NULL;
> if (intel_vtd_active()) {
> if (IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE)) {
> - static char huge_opt[] = "huge=within_size"; /* r/w */
> -
> opts = huge_opt;
> drm_info(&i915->drm,
> "Transparent Hugepage mode '%s'\n",
>
next prev parent reply other threads:[~2021-11-26 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 11:08 [Intel-gfx] [PATCH] drm/i915/gemfs: don't mark huge_opt as static Matthew Auld
2021-11-26 11:50 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-11-26 12:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-11-26 12:20 ` Tvrtko Ursulin [this message]
2021-11-26 14:36 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=398b3993-804d-2f7f-8a53-b3452f444cbc@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@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 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.