All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Matthew Auld <matthew.auld@intel.com>
Subject: Re: [PATCH] drm/i915/lmem: add the fake lmem region
Date: Thu, 31 Oct 2019 14:40:35 +0200	[thread overview]
Message-ID: <20191031124035.g2grwflwdu5wfobe@ahiler-desk1.fi.intel.com> (raw)
In-Reply-To: <CAM0jSHO3McVPWCLszV30bp2wydF0TDB4pGriW05ZVBPBg0Tuuw@mail.gmail.com>

On Wed, Oct 30, 2019 at 10:22:37PM +0000, Matthew Auld wrote:
> On Tue, 29 Oct 2019 at 16:51, Matthew Auld <matthew.auld@intel.com> wrote:
> >
> > Intended for upstream testing so that we can still exercise the LMEM
> > plumbing and !i915_ggtt_has_aperture paths. Smoke tested on Skull Canyon
> > device. This works by allocating an intel_memory_region for a reserved
> > portion of system memory, which we treat like LMEM. For the LMEMBAR we
> > steal the aperture and 1:1 it map to the stolen region.
> >
> > To enable simply set the i915 modparam fake_lmem_start= on the kernel
> > cmdline with the start of reserved region(see memmap=). The size of the
> > region we can use is determined by the size of the mappable aperture, so
> > the size of reserved region should be >= mappable_end. For now we only
> > enable for the selftests. Depends on CONFIG_DRM_I915_UNSTABLE being
> > enabled.
> >
> > eg. memmap=2G$16G i915.fake_lmem_start=0x400000000
> 
> Hi Arek,
> 
> Would you be able to update the fi-skl-lmem kernel cmd line with
> s/i915_fake_lmem_start/i915.fake_lmem_start?

done
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
To: Matthew Auld <matthew.william.auld@gmail.com>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Matthew Auld <matthew.auld@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/lmem: add the fake lmem region
Date: Thu, 31 Oct 2019 14:40:35 +0200	[thread overview]
Message-ID: <20191031124035.g2grwflwdu5wfobe@ahiler-desk1.fi.intel.com> (raw)
Message-ID: <20191031124035.bQER-8IUCezzL8_MnpQjyuqtCcYa-dzXZwPjWFt4fG0@z> (raw)
In-Reply-To: <CAM0jSHO3McVPWCLszV30bp2wydF0TDB4pGriW05ZVBPBg0Tuuw@mail.gmail.com>

On Wed, Oct 30, 2019 at 10:22:37PM +0000, Matthew Auld wrote:
> On Tue, 29 Oct 2019 at 16:51, Matthew Auld <matthew.auld@intel.com> wrote:
> >
> > Intended for upstream testing so that we can still exercise the LMEM
> > plumbing and !i915_ggtt_has_aperture paths. Smoke tested on Skull Canyon
> > device. This works by allocating an intel_memory_region for a reserved
> > portion of system memory, which we treat like LMEM. For the LMEMBAR we
> > steal the aperture and 1:1 it map to the stolen region.
> >
> > To enable simply set the i915 modparam fake_lmem_start= on the kernel
> > cmdline with the start of reserved region(see memmap=). The size of the
> > region we can use is determined by the size of the mappable aperture, so
> > the size of reserved region should be >= mappable_end. For now we only
> > enable for the selftests. Depends on CONFIG_DRM_I915_UNSTABLE being
> > enabled.
> >
> > eg. memmap=2G$16G i915.fake_lmem_start=0x400000000
> 
> Hi Arek,
> 
> Would you be able to update the fi-skl-lmem kernel cmd line with
> s/i915_fake_lmem_start/i915.fake_lmem_start?

done
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-10-31 12:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 16:51 [PATCH] drm/i915/lmem: add the fake lmem region Matthew Auld
2019-10-29 16:51 ` [Intel-gfx] " Matthew Auld
2019-10-30  1:43 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2019-10-30  1:43   ` [Intel-gfx] " Patchwork
2019-10-30  1:57 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-10-30  1:57   ` [Intel-gfx] " Patchwork
2019-10-30  9:14 ` [PATCH] " Chris Wilson
2019-10-30  9:14   ` [Intel-gfx] " Chris Wilson
2019-10-30 22:22 ` Matthew Auld
2019-10-30 22:22   ` [Intel-gfx] " Matthew Auld
2019-10-31 12:40   ` Arkadiusz Hiler [this message]
2019-10-31 12:40     ` Arkadiusz Hiler
2019-10-31 20:40     ` Chris Wilson
2019-10-31 20:40       ` [Intel-gfx] " Chris Wilson
2019-11-05 13:05       ` Matthew Auld
2019-11-05 13:05         ` [Intel-gfx] " Matthew Auld
2019-11-06  8:30         ` Arkadiusz Hiler
2019-11-06  8:30           ` [Intel-gfx] " Arkadiusz Hiler
2019-11-06 11:17           ` Chris Wilson
2019-11-06 11:17             ` [Intel-gfx] " Chris Wilson
2019-11-06 13:58             ` Arkadiusz Hiler
2019-11-06 13:58               ` [Intel-gfx] " Arkadiusz Hiler

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=20191031124035.g2grwflwdu5wfobe@ahiler-desk1.fi.intel.com \
    --to=arkadiusz.hiler@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.auld@intel.com \
    --cc=matthew.william.auld@gmail.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.