structure which
> can be rewritten to match the 2nd process)
>
> Jose
>
> --------------
> *From:* mesa-dev on behalf of
> Dave Airlie
> *Sent:* Thursday, April 27, 2023 08:39
> *To:* Josh Gargus
> *Cc:* mesa-dev@lists.freedesktop.org
> *Subject:* R
Dave
Airlie
Sent: Thursday, April 27, 2023 08:39
To: Josh Gargus
Cc: mesa-dev@lists.freedesktop.org
Subject: Re: Advice on modifying Lavapipe to isolate JIT compilation in
separate process
!! External Email
On Thu, 27 Apr 2023 at 15:18, Josh Gargus wrote:
>
> Thanks for your advice!
On Thu, 27 Apr 2023 at 15:18, Josh Gargus wrote:
>
> Thanks for your advice! I hadn't looked at Venus, but that seems like a very
> promising place to start.
>
> The other approach feels more approachable now too; it feels like there are
> less "unknown unknowns", although there are plenty of k
Thanks for your advice! I hadn't looked at Venus, but that seems like a
very promising place to start.
The other approach feels more approachable now too; it feels like there are
less "unknown unknowns", although there are plenty of known unknowns to
investigate (address independence was one that
On Thu, 27 Apr 2023 at 05:27, Josh Gargus wrote:
>
> Hi, I'm from the Fuchsia team at Google. We would like to provide Lavapipe
> as an ICD within Fuchsia. However, our default security policy is to deny
> client apps the capability to map memory as writable/executable; we don't
> want to rel
