public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
Cc: intel-gfx@lists.freedesktop.org, akash.goel@intel.com,
	shashidhar.hiremath@intel.com
Subject: Re: [PATCH] igt/gem_create_stolen: Verifying extended gem_create ioctl
Date: Fri, 8 May 2015 09:16:29 +0200	[thread overview]
Message-ID: <20150508071629.GJ30184@phenom.ffwll.local> (raw)
In-Reply-To: <1431062666.17871.9.camel@ankitprasad-desktop>

On Fri, May 08, 2015 at 10:54:26AM +0530, Ankitprasad Sharma wrote:
> On Thu, 2015-05-07 at 08:52 +0200, Daniel Vetter wrote:
> > On Wed, May 06, 2015 at 03:51:52PM +0530, ankitprasad.r.sharma@intel.com wrote:
> > > From: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
> > > 
> > > This patch adds the testcases for verifying the new extended
> > > gem_create ioctl. By means of this extended ioctl, memory
> > > placement of the GEM object can be specified, i.e. either
> > > shmem or stolen memory.
> > > These testcases include functional tests and interface tests for
> > > testing the gem_create ioctl call for stolen memory placement
> > > 
> > > v2: Testing pread/pwrite functionality for stolen backed objects,
> > > added local struct for extended gem_create and gem_get_aperture,
> > > until headers catch up (Chris)
> > > 
> > > v3: Removed get_aperture related functions, extended gem_pread
> > > to compare speeds for user pages with and without page faults,
> > > unexposed local_gem_create struct, changed gem_create_stolen
> > > usage (Chris)
> > > 
> > > Signed-off-by: Ankitprasad Sharma <ankitprasad.r.sharma@intel.com>
> > 
> > An igt to check for invalid arguments of the gem create ioctl (especially
> > the newly added flags parameters) seems to be missing.
> > -Daniel
> 
> \Wwe already have a test to check invalid arguments for the newly added
> flags parameter in the current set of tests.
> 
> static void invalid_flag_test(int fd)

Oh right I totally missed that. Especially for future extension I think
Chris' idea to split up tests sounds really good, i.e.

gem_create/invalid-flags (the one testcase I didn't spot)
gem_stolen/<all the other tests>

Otherwise the next person extending gem_create will miss your
invalid-flags test for it.
Thanks, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-05-08  7:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 10:21 [PATCH] igt/gem_create_stolen: Verifying extended gem_create ioctl ankitprasad.r.sharma
2015-05-07  6:52 ` Daniel Vetter
2015-05-07  9:12   ` Chris Wilson
2015-05-07 13:16     ` Daniel Vetter
2015-05-08  5:24   ` Ankitprasad Sharma
2015-05-08  7:16     ` Daniel Vetter [this message]
2015-05-10 18:47       ` Ankitprasad Sharma
2015-05-11  9:49         ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2015-04-29  9:32 ankitprasad.r.sharma
2015-04-29 10:49 ` Chris Wilson
2015-04-11 12:28 ankitprasad.r.sharma
2015-04-11 13:30 ` Chris Wilson

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=20150508071629.GJ30184@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=akash.goel@intel.com \
    --cc=ankitprasad.r.sharma@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=shashidhar.hiremath@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