02:13 <i509vcb> Not sure how VkEvent would be implemented. Assuming there isn't special stuff in agxv I'd guess a buffer you write to after some stage finishes?

02:18 <i509vcb> Self contained things like a vk_meta implementation could be a cool idea but you'd probably end up writing hundreds of lines of unsafe Rust with ash which wouldn't be much better than C

02:32 <i509vcb> On Rust until meson supports crates from cargo we'd probably need to vendor some rust stuff...

02:32 <i509vcb> Mainly ash

02:34 <i509vcb> Speaking of which the vk_meta discussion for layer_id seemed inconclusive from what I recall?

02:44 <i509vcb> I'm tempted to throw a hack commit to just make it work and revisit in the future

05:37 <i509vcb> hmm now to figure out why the palm trees are uhh weird https://usercontent.irccloud-cdn.com/file/TGYv01le/Screenshot_20230930_003310.png

06:32 <chadmed> they have been attacked by fusarium :)

21:05 <ella-0> i509vcb: i think vkevent might need some uapi changes? at least what's currently used for implementing explicit synchronisation could be exposed more for implementing vkevent to some degree.

21:06 <ella-0> the other option is just a basic compute job that handles vkevent which I think v3dv does

21:11 <i509vcb> alyssa probably has an opinion how to do this

21:15 <ella-0> as for crates it might make sense to vendor ash (because it doesn't really have any other subdepednencies) but I personally wouldn't want to depend on much else; the dependency hell that crates can cause if one is not careful makes my other job (maintaing Iglunix) a bit of a pain.

22:24 <i509vcb> Although if someone wanted to use proc-macro in mesa then it would be pain

22:29 <ella-0> Wouldn't have thought so; It's included in rust-src

22:50 <i509vcb> Well for writing proc macros

22:51 <i509vcb> Although the kernel figured it out so *shrug*

22:52 <i509vcb> (although needing to build tokio for mesa just sounds like an npm nightmare)

23:10 <ella-0> I didn't think you needed anything else really wo write proc macros