From: Ramalingam C <ramalingam.c@intel.com> To: "Tang, CQ" <cq.tang@intel.com> Cc: intel-gfx <intel-gfx@lists.freedesktop.org>, "Auld, Matthew" <matthew.auld@intel.com> Subject: Re: [PATCH v4 1/2] drm/i915: lookup for mem_region of a mem_type Date: Wed, 6 Nov 2019 21:55:12 +0530 [thread overview] Message-ID: <20191106162512.GA8066@intel.com> (raw) In-Reply-To: <1D440B9B88E22A4ABEF89F9F1F81BC29E947BA8A@FMSMSX103.amr.corp.intel.com> On 2019-11-06 at 21:45:44 +0530, Tang, CQ wrote: > > > > -----Original Message----- > > From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of > > Ramalingam C > > Sent: Wednesday, November 6, 2019 8:08 AM > > To: intel-gfx <intel-gfx@lists.freedesktop.org>; Chris Wilson <chris@chris- > > wilson.co.uk> > > Cc: Auld, Matthew <matthew.auld@intel.com> > > Subject: [Intel-gfx] [PATCH v4 1/2] drm/i915: lookup for mem_region of a > > mem_type > > > > Lookup function to retrieve the pointer to a memory region of a mem_type. > > We could have multi-regions with the same memory type. Your code just returns the first one. Is this desired? At present even i915_gem_object_create_lmem i915_gem_object_create_shmem retrieve the mem_region in this manner only. may be when we have more region_ids per type we could extend based on a need. This is just my thoughts. -Ram > > --CQ > > > > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com> > > cc: Matthew Auld <matthew.auld@intel.com> > > --- > > drivers/gpu/drm/i915/intel_memory_region.c | 12 ++++++++++++ > > drivers/gpu/drm/i915/intel_memory_region.h | 3 +++ > > 2 files changed, 15 insertions(+) > > > > diff --git a/drivers/gpu/drm/i915/intel_memory_region.c > > b/drivers/gpu/drm/i915/intel_memory_region.c > > index baaeaecc64af..ae899df7a1c2 100644 > > --- a/drivers/gpu/drm/i915/intel_memory_region.c > > +++ b/drivers/gpu/drm/i915/intel_memory_region.c > > @@ -16,6 +16,18 @@ const u32 intel_region_map[] = { > > [INTEL_REGION_STOLEN] = REGION_MAP(INTEL_MEMORY_STOLEN, > > 0), }; > > > > +struct intel_memory_region * > > +intel_memory_region_lookup(struct drm_i915_private *i915, > > + enum intel_memory_type mem_type) > > +{ > > + enum intel_region_id id; > > + > > + for (id = INTEL_REGION_SMEM; id < INTEL_REGION_UNKNOWN; > > id++) > > + if (i915->mm.regions[id]->type == mem_type) > > + return i915->mm.regions[id]; > > + return NULL; > > +} > > + > > static u64 > > intel_memory_region_free_pages(struct intel_memory_region *mem, > > struct list_head *blocks) > > diff --git a/drivers/gpu/drm/i915/intel_memory_region.h > > b/drivers/gpu/drm/i915/intel_memory_region.h > > index 238722009677..d210936c4d72 100644 > > --- a/drivers/gpu/drm/i915/intel_memory_region.h > > +++ b/drivers/gpu/drm/i915/intel_memory_region.h > > @@ -125,5 +125,8 @@ void intel_memory_region_put(struct > > intel_memory_region *mem); > > > > int intel_memory_regions_hw_probe(struct drm_i915_private *i915); void > > intel_memory_regions_driver_release(struct drm_i915_private *i915); > > +struct intel_memory_region * > > +intel_memory_region_lookup(struct drm_i915_private *i915, > > + enum intel_memory_type mem_type); > > > > #endif > > -- > > 2.20.1 > > > > _______________________________________________ > > Intel-gfx mailing list > > Intel-gfx@lists.freedesktop.org > > https://lists.freedesktop.org/mailman/listinfo/intel-gfx _______________________________________________ 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: Ramalingam C <ramalingam.c@intel.com> To: "Tang, CQ" <cq.tang@intel.com> Cc: intel-gfx <intel-gfx@lists.freedesktop.org>, "Auld, Matthew" <matthew.auld@intel.com> Subject: Re: [Intel-gfx] [PATCH v4 1/2] drm/i915: lookup for mem_region of a mem_type Date: Wed, 6 Nov 2019 21:55:12 +0530 [thread overview] Message-ID: <20191106162512.GA8066@intel.com> (raw) Message-ID: <20191106162512.WIZIyPuCRrPdshVTftxc7PYO_25EyPjkjVJTbHHB-Ys@z> (raw) In-Reply-To: <1D440B9B88E22A4ABEF89F9F1F81BC29E947BA8A@FMSMSX103.amr.corp.intel.com> On 2019-11-06 at 21:45:44 +0530, Tang, CQ wrote: > > > > -----Original Message----- > > From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of > > Ramalingam C > > Sent: Wednesday, November 6, 2019 8:08 AM > > To: intel-gfx <intel-gfx@lists.freedesktop.org>; Chris Wilson <chris@chris- > > wilson.co.uk> > > Cc: Auld, Matthew <matthew.auld@intel.com> > > Subject: [Intel-gfx] [PATCH v4 1/2] drm/i915: lookup for mem_region of a > > mem_type > > > > Lookup function to retrieve the pointer to a memory region of a mem_type. > > We could have multi-regions with the same memory type. Your code just returns the first one. Is this desired? At present even i915_gem_object_create_lmem i915_gem_object_create_shmem retrieve the mem_region in this manner only. may be when we have more region_ids per type we could extend based on a need. This is just my thoughts. -Ram > > --CQ > > > > > Signed-off-by: Ramalingam C <ramalingam.c@intel.com> > > cc: Matthew Auld <matthew.auld@intel.com> > > --- > > drivers/gpu/drm/i915/intel_memory_region.c | 12 ++++++++++++ > > drivers/gpu/drm/i915/intel_memory_region.h | 3 +++ > > 2 files changed, 15 insertions(+) > > > > diff --git a/drivers/gpu/drm/i915/intel_memory_region.c > > b/drivers/gpu/drm/i915/intel_memory_region.c > > index baaeaecc64af..ae899df7a1c2 100644 > > --- a/drivers/gpu/drm/i915/intel_memory_region.c > > +++ b/drivers/gpu/drm/i915/intel_memory_region.c > > @@ -16,6 +16,18 @@ const u32 intel_region_map[] = { > > [INTEL_REGION_STOLEN] = REGION_MAP(INTEL_MEMORY_STOLEN, > > 0), }; > > > > +struct intel_memory_region * > > +intel_memory_region_lookup(struct drm_i915_private *i915, > > + enum intel_memory_type mem_type) > > +{ > > + enum intel_region_id id; > > + > > + for (id = INTEL_REGION_SMEM; id < INTEL_REGION_UNKNOWN; > > id++) > > + if (i915->mm.regions[id]->type == mem_type) > > + return i915->mm.regions[id]; > > + return NULL; > > +} > > + > > static u64 > > intel_memory_region_free_pages(struct intel_memory_region *mem, > > struct list_head *blocks) > > diff --git a/drivers/gpu/drm/i915/intel_memory_region.h > > b/drivers/gpu/drm/i915/intel_memory_region.h > > index 238722009677..d210936c4d72 100644 > > --- a/drivers/gpu/drm/i915/intel_memory_region.h > > +++ b/drivers/gpu/drm/i915/intel_memory_region.h > > @@ -125,5 +125,8 @@ void intel_memory_region_put(struct > > intel_memory_region *mem); > > > > int intel_memory_regions_hw_probe(struct drm_i915_private *i915); void > > intel_memory_regions_driver_release(struct drm_i915_private *i915); > > +struct intel_memory_region * > > +intel_memory_region_lookup(struct drm_i915_private *i915, > > + enum intel_memory_type mem_type); > > > > #endif > > -- > > 2.20.1 > > > > _______________________________________________ > > Intel-gfx mailing list > > Intel-gfx@lists.freedesktop.org > > https://lists.freedesktop.org/mailman/listinfo/intel-gfx _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-11-06 16:24 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-11-06 16:08 [PATCH v4 1/2] drm/i915: lookup for mem_region of a mem_type Ramalingam C 2019-11-06 16:08 ` [Intel-gfx] " Ramalingam C 2019-11-06 16:08 ` [PATCH v4 2/2] drm/i915: Create dumb buffer from LMEM Ramalingam C 2019-11-06 16:08 ` [Intel-gfx] " Ramalingam C 2019-11-07 9:45 ` Chris Wilson 2019-11-07 9:45 ` [Intel-gfx] " Chris Wilson 2019-11-06 16:15 ` [PATCH v4 1/2] drm/i915: lookup for mem_region of a mem_type Tang, CQ 2019-11-06 16:15 ` [Intel-gfx] " Tang, CQ 2019-11-06 16:25 ` Ramalingam C [this message] 2019-11-06 16:25 ` Ramalingam C 2019-11-06 20:14 ` ✓ Fi.CI.BAT: success for series starting with [v4,1/2] " Patchwork 2019-11-06 20:14 ` [Intel-gfx] " Patchwork 2019-11-07 21:19 ` ✓ Fi.CI.IGT: " Patchwork 2019-11-07 21:19 ` [Intel-gfx] " Patchwork 2019-12-02 6:54 [PATCH v4 1/2] " Ramalingam C
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=20191106162512.GA8066@intel.com \ --to=ramalingam.c@intel.com \ --cc=cq.tang@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: linkBe 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.