All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cheng, Yao" <yao.cheng@intel.com>
To: "Cheng, Yao" <yao.cheng@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
	"Kelley, Sean V" <sean.v.kelley@intel.com>,
	"Chehab, John" <john.chehab@intel.com>,
	"Ewins, Jon" <jon.ewins@intel.com>,
	"Beckett, Robert" <robert.beckett@intel.com>,
	"Barbalho, Rafael" <rafael.barbalho@intel.com>
Cc: "emil.l.velikov@gmail.com" <emil.l.velikov@gmail.com>,
	"Jiang, Fei" <fei.jiang@intel.com>
Subject: Re: [RFC PATCH v3 2/4] drm/ipvr: drm driver for VED
Date: Mon, 1 Dec 2014 03:09:09 +0000	[thread overview]
Message-ID: <8FF7D634BEE4C2428EFFAB6B7E919E4B018350A6@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <8FF7D634BEE4C2428EFFAB6B7E919E4B018323FF@shsmsx102.ccr.corp.intel.com>

Add Jon/Bob/Raf for detail review.
> -----Original Message-----
> From: dri-devel [mailto:dri-devel-bounces@lists.freedesktop.org] On Behalf
> Of Cheng, Yao
> Sent: Thursday, November 27, 2014 19:49
> To: intel-gfx@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
> daniel.vetter@ffwll.ch; Kelley, Sean V; Chehab, John
> Cc: emil.l.velikov@gmail.com; Jiang, Fei
> Subject: RE: [RFC PATCH v3 2/4] drm/ipvr: drm driver for VED
> 
> > -----Original Message-----
> > From: Cheng, Yao
> > Sent: Saturday, November 22, 2014 3:07
> > To: intel-gfx@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
> > daniel.vetter@ffwll.ch; Kelley, Sean V; Chehab, John
> > Cc: Jiang, Fei; dh.herrmann@gmail.com; jani.nikula@linux.intel.com;
> > emil.l.velikov@gmail.com; ville.syrjala@linux.intel.com;
> > jbarnes@virtuousgeek.org; daniel@fooishbar.org; Cheng, Yao
> > Subject: [RFC PATCH v3 2/4] drm/ipvr: drm driver for VED
> > +typedef struct drm_ipvr_private {
> > +	struct drm_device *dev;
> > +	struct pci_dev *pci_root;
> > +
> > +	/* IMG video context */
> > +	struct list_head ipvr_ctx_list;
> 
> The current design leads to ctx leak. There's no ctx_list for each file struct, so
> each create_context_ioctl causes one ctx leak.
> Need to move the ctx_list from dev_private to file_private.
> 
> > +	spinlock_t ipvr_ctx_lock;
> > +	struct idr ipvr_ctx_idr;
> > +	struct ipvr_context default_ctx;
> > +
> > +	/* PM related */
> > +	atomic_t pending_events;
> > +
> > +	/* exec related */
> > +	struct ipvr_validate_context validate_ctx;
> > +
> > +	/* IMG MMU specific */
> > +	struct ipvr_mmu_driver *mmu;
> > +	/*struct ipvr_mmu_pd *pf_pd;*/
> > +	atomic_t ipvr_mmu_invaldc;
> > +
> > +	/* GEM mm related */
> > +	struct ipvr_gem_stat ipvr_stat;
> > +	struct kmem_cache *ipvr_bo_slab;
> > +	struct ipvr_address_space addr_space;
> > +
> > +	/* fence related */
> > +	u32 last_seq;
> > +	wait_queue_head_t fence_queue;
> > +	struct ipvr_fence_driver fence_drv;
> > +
> > +	/* MMIO window shared from parent device */
> > +	u8 __iomem* reg_base;
> > +
> > +	/*
> > +	 * VED specific
> > +	 */
> > +	struct ved_private *ved_private;
> > +}drm_ipvr_private_t;
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2014-12-01  3:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21 19:06 [RFC PATCH v3 0/4] drm driver for VED in Intel GPU Yao Cheng
2014-11-21 19:06 ` [RFC PATCH v3 1/4] drm/i915: add i915_ved.c to setup bridge for VED Yao Cheng
2014-11-28 16:59   ` Robert Beckett
2014-12-01  3:04     ` Cheng, Yao
2014-12-01  8:32       ` [Intel-gfx] " Daniel Vetter
2014-11-21 19:06 ` [RFC PATCH v3 2/4] drm/ipvr: drm driver " Yao Cheng
2014-11-23 13:29   ` Cheng, Yao
2014-11-26 16:50   ` Cheng, Yao
2014-11-27 11:49   ` Cheng, Yao
2014-12-01  3:09     ` Cheng, Yao [this message]

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=8FF7D634BEE4C2428EFFAB6B7E919E4B018350A6@shsmsx102.ccr.corp.intel.com \
    --to=yao.cheng@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=fei.jiang@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=john.chehab@intel.com \
    --cc=jon.ewins@intel.com \
    --cc=rafael.barbalho@intel.com \
    --cc=robert.beckett@intel.com \
    --cc=sean.v.kelley@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.