[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] WebVulkan

SPIRV supports multiple memory models, addressing models, Storage Classes, etc…

Perhaps we could define WebVulkan as supporting a subset of these?

Also, GPU drivers provide cross-process isolation of the GPU memory.  Perhaps the browser could add an additional layer of security by instantiating a separate GPU process for each WebVulkan context?  If we depend on the GPU driver’s existing security models, would we need to manage a blacklist of driver versions with known vulnerabilities?

Thanks for the excellent discussion!

- Kearwood “Kip” Gilbert

On Aug 5, 2016, at 10:33 AM, Florian Bösch <pyalot@gmail.com> wrote:

On Fri, Aug 5, 2016 at 7:09 PM, Brandon Jones <bajones@google.com> wrote:
The memory model Vulkan exposes is simply not something we can do in the browser. That's not a subject that's up for debate, it's a fact.
Come again? No? Why? How? What? Who decided that?