dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Keith Packard" <keithp@keithp.com>
To: Jason Ekstrand <jason@jlekstrand.net>
Cc: ML mesa-dev <mesa-dev@lists.freedesktop.org>,
	Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 6/7] anv: add VK_EXT_display_control to anv driver [v2]
Date: Tue, 19 Jun 2018 22:31:46 -0700	[thread overview]
Message-ID: <87d0wmowfx.fsf@keithp.com> (raw)
In-Reply-To: <CAOFGe96mCyAk1Uui4AMXCGSosQu_no8wU5qy6fFh2+pwVL792g@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1171 bytes --]

Jason Ekstrand <jason@jlekstrand.net> writes:

>> +   if (allocator)
>> +     alloc = allocator;
>> +   else
>> +     alloc = &device->instance->alloc;
>>
>
> This is what vk_alloc2 is for. :-)
...
> And vk_free2
...
> This isn't needed if you're using vk_alloc2

Yeah, but I need to pass the allocator down to the wsi common code, and
that doesn't have any way to touch the device driver allocator
pointer. I bet I'm just missing something here. Help?

>> +
>> +   fence = vk_zalloc2(&device->alloc, allocator, sizeof (*fence), 8,
>> +                      VK_SYSTEM_ALLOCATION_SCOPE_OBJECT);
>>
>
> Above you used vk_alloc and here you're using vk_zalloc.  Mind picking
> one?  I don't think zalloc is needed but it doesn't hurt so I don't care
> which.

Thanks. Existing code is using zalloc for fences; I'll use that everywhere.

> Indentation could be consistent between the two functions you add.  I don't
> care which style.

Sure; these function names are kinda long. I've wrapped the first call
after the (

> vk_free2?

I've had to compute 'alloc' to pass into wsi_common; I figured I might
as well use it.

-- 
-keith

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-06-20  5:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-15  2:52 [PATCH 0/7] vulkan: Add VK_EXT_display_control and VK_EXT_display_surface_counter Keith Packard
2018-06-15  2:52 ` [PATCH 1/7] vulkan: Add VK_EXT_display_surface_counter [v4] Keith Packard
2018-06-16 18:22   ` Jason Ekstrand
2018-06-16 18:55     ` Keith Packard
2018-06-15  2:52 ` [PATCH 2/7] anv: Add VK_EXT_display_surface_counter to anv driver [v2] Keith Packard
2018-06-15  2:52 ` [PATCH 3/7] radv: Add VK_EXT_display_surface_counter to radv driver Keith Packard
2018-06-15  2:52 ` [PATCH 4/7] anv: Support wait for heterogeneous list of fences [v2] Keith Packard
2018-06-19 23:26   ` Jason Ekstrand
2018-06-20  0:36     ` Keith Packard
2018-06-20  0:42       ` Jason Ekstrand
2018-06-20  1:22         ` Keith Packard
2018-06-20  2:22           ` Jason Ekstrand
2018-06-20  5:16             ` Keith Packard
2018-06-20  5:22               ` Jason Ekstrand
2018-06-20  5:36                 ` Keith Packard
2018-06-15  2:52 ` [PATCH 5/7] vulkan: add VK_EXT_display_control [v5] Keith Packard
2018-06-20  0:28   ` Jason Ekstrand
2018-06-20  4:44     ` Keith Packard
2018-06-20 21:52       ` Jason Ekstrand
2018-06-20 22:49         ` Keith Packard
2018-06-15  2:52 ` [PATCH 6/7] anv: add VK_EXT_display_control to anv driver [v2] Keith Packard
2018-06-20  0:33   ` Jason Ekstrand
2018-06-20  5:31     ` Keith Packard [this message]
2018-06-20 17:13       ` Jason Ekstrand
2018-06-20 22:45         ` Keith Packard
2018-06-15  2:52 ` [PATCH 7/7] radv: add VK_EXT_display_control to radv driver [v3] Keith Packard

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=87d0wmowfx.fsf@keithp.com \
    --to=keithp@keithp.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jason@jlekstrand.net \
    --cc=mesa-dev@lists.freedesktop.org \
    /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