search for: vizoso

On 07/31/2017 02:30 PM, Nicholas Wilson via llvm-dev wrote: > >> On 31 Jul 2017, at 3:23 pm, Neil Henning <ll... at duskborn.com> wrote: > > Moving forward, other than securing the triples spirv32, spirv64, and spirvlogical from LLVM, how can we go about coordinating efforts? I feel that having one backend is a better use of everybody’s time than having three. If we

> On 27 Sep 2017, at 8:21 pm, Tomeu Vizoso <tomeu.vizoso at collabora.com> wrote: > > Hi there, > > any news on coordination? We have customers who are successfully using > Mesa in their products, and that are now asking about OpenCL. None yet, I’m still waiting for IWOCL to spearhead the coordination. > My curre...

...if we add the converter to the LLVM project as an optional tool? We would of course take care of configuring and maintaining it ourselves. Cheers, Anastasia ________________________________ From: Tom Stellard <tstellar at redhat.com> Sent: 26 February 2018 17:37 To: Anastasia Stulova; Tomeu Vizoso; llvm-dev at lists.llvm.org Cc: nd Subject: Re: [llvm-dev] SPIRV-LLVM as an external tool On 02/26/2018 09:25 AM, Anastasia Stulova wrote: > >> This is great to see. Is this code the basis of the forks that Anastasia > talked about or did those come from somewhere else? > > >...

...-------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > *From:* Tom Stellard <tstellar at redhat.com> > *Sent:* 26 February 2018 17:37 > *To:* Anastasia Stulova; Tomeu Vizoso; llvm-dev at lists.llvm.org > *Cc:* nd > *Subject:* Re: [llvm-dev] SPIRV-LLVM as an external tool > > On 02/26/2018 09:25 AM, Anastasia Stulova wrote: >> >>> This is great to see. Is this code the basis of the forks that Anastasia >> talked about or did those co...

...won't help us with item (3) at all, and item (4) will be incomplete. Cheers, Anastasia ________________________________ From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> Sent: 23 February 2018 20:28 To: Tomeu Vizoso; LLVM Developers Subject: Re: [llvm-dev] SPIRV-LLVM as an external tool On 02/21/2018 03:34 PM, Pierre Moreau wrote: > On 2018-02-21 — 14:55, Tom Stellard via llvm-dev wrote: >> On 02/21/2018 12:15 AM, Tomeu Vizoso via llvm-dev wrote: >>> Hi, >>> >>> for a few m...

On 2018-02-21 — 14:55, Tom Stellard via llvm-dev wrote: > On 02/21/2018 12:15 AM, Tomeu Vizoso via llvm-dev wrote: > > Hi, > > > > for a few months already I have been asking around for opinions on how > > people could best work together on Khronos' SPIR-V <-> LLVM-IR converter > > and some consensus seems to have formed. > > > > Most of...

...complete and compliant OpenCL C++ support, without using any external tools. See discussion with Tom earlier. Thanks! Anastasia ________________________________ From: Chris Lattner <clattner at nondot.org> Sent: 01 March 2018 01:52 To: tstellar at redhat.com Cc: Anastasia Stulova; Tomeu Vizoso; llvm-dev at lists.llvm.org; nd Subject: Re: [llvm-dev] SPIRV-LLVM as an external tool On Feb 27, 2018, at 10:25 AM, Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 02/27/2018 05:07 AM, Anastasia Stulova wrote: >>> SPIR-V does not have to be a part of LLVM for...

...ld happen in the near future. If at some point we have also a backend, and people want to have it along the other backends in the main LLVM repo, that will be great. But in the meantime we need a place to work together. Regards, Tomeu > Nic > >> On 21 Feb 2018, at 4:15 pm, Tomeu Vizoso via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi, >> >> for a few months already I have been asking around for opinions on how >> people could best work together on Khronos' SPIR-V <-> LLVM-IR converter >> and some consensus seems to have...

On Feb 27, 2018, at 10:25 AM, Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 02/27/2018 05:07 AM, Anastasia Stulova wrote: >>> SPIR-V does not have to be a part of LLVM for you to do this. You can add >>> the SPIR-V target to clang and then define a SPIR-V toolchain (i.e. clang/Driver/Toolchains) >>> that uses the external tool to translate

...----------------------------------------------------------------------------------------------------------- > *From:* llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> > *Sent:* 23 February 2018 20:28 > *To:* Tomeu Vizoso; LLVM Developers > *Subject:* Re: [llvm-dev] SPIRV-LLVM as an external tool > > On 02/21/2018 03:34 PM, Pierre Moreau wrote: >> On 2018-02-21 — 14:55, Tom Stellard via llvm-dev wrote: >>> On 02/21/2018 12:15 AM, Tomeu Vizoso via llvm-dev wrote: >>>> Hi, >&gt...

...ool, it would be very helpful. Thanks, Anastasia ________________________________ From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Pierre Moreau via llvm-dev <llvm-dev at lists.llvm.org> Sent: 21 February 2018 23:34 To: tstellar at redhat.com Cc: LLVM Developers; Tomeu Vizoso Subject: Re: [llvm-dev] SPIRV-LLVM as an external tool On 2018-02-21 — 14:55, Tom Stellard via llvm-dev wrote: > On 02/21/2018 12:15 AM, Tomeu Vizoso via llvm-dev wrote: > > Hi, > > > > for a few months already I have been asking around for opinions on how > > people cou...

...y see any myself. Neil ________________________________ From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Philip Reames via llvm-dev <llvm-dev at lists.llvm.org> Sent: 06 March 2018 23:07:54 To: Anastasia Stulova; Chris Lattner Cc: llvm-dev at lists.llvm.org; nd; Tomeu Vizoso Subject: Re: [llvm-dev] SPIRV-LLVM as an external tool I've only been skimming the discussion thread so far, but so far, I see no strong reason for this to be a LLVM subproject in it's current form. I would recommend pursing a standalone open source project, building a community around t...

...s Stach <l.stach at pengutronix.de> Cc: Russell King <linux+etnaviv at armlinux.org.uk> Cc: Christian Gmeiner <christian.gmeiner at gmail.com> Cc: Qiang Yu <yuq825 at gmail.com> Cc: Ben Skeggs <bskeggs at redhat.com> Cc: Rob Herring <robh at kernel.org> Cc: Tomeu Vizoso <tomeu.vizoso at collabora.com> Cc: Steven Price <steven.price at arm.com> Cc: Alyssa Rosenzweig <alyssa.rosenzweig at collabora.com> Cc: Gerd Hoffmann <kraxel at redhat.com> Cc: Alex Deucher <alexander.deucher at amd.com> Cc: "Christian K?nig" <christian....

If the wait timeouts, the caps are probably invalid and we shouldn't be passing them to userspace. Signed-off-by: Tomeu Vizoso <tomeu.vizoso at collabora.com> --- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/virtio/virtgpu_ioctl.c b/drivers/gpu/drm/virtio/virtgpu_ioctl.c index b94bd5440e57..902120ad4a6d 100644 --- a/drivers/gpu/drm/virtio/virtgpu_ioctl....

If the wait timeouts, the caps are probably invalid and we shouldn't be passing them to userspace. Signed-off-by: Tomeu Vizoso <tomeu.vizoso at collabora.com> --- drivers/gpu/drm/virtio/virtgpu_ioctl.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/virtio/virtgpu_ioctl.c b/drivers/gpu/drm/virtio/virtgpu_ioctl.c index b94bd5440e57..902120ad4a6d 100644 --- a/drivers/gpu/drm/virtio/virtgpu_ioctl....

On 02/21/2018 03:34 PM, Pierre Moreau wrote: > On 2018-02-21 — 14:55, Tom Stellard via llvm-dev wrote: >> On 02/21/2018 12:15 AM, Tomeu Vizoso via llvm-dev wrote: >>> Hi, >>> >>> for a few months already I have been asking around for opinions on how >>> people could best work together on Khronos' SPIR-V <-> LLVM-IR converter >>> and some consensus seems to have formed. >>> &g...

On 09/27/2017 05:21 AM, Tomeu Vizoso wrote: > On 07/31/2017 02:30 PM, Nicholas Wilson via llvm-dev wrote: >> >>> On 31 Jul 2017, at 3:23 pm, Neil Henning <ll... at duskborn.com> wrote: >> >> Moving forward, other than securing the triples spirv32, spirv64, and spirvlogical from LLVM, how can we go a...

Hi, for a few months already I have been asking around for opinions on how people could best work together on Khronos' SPIR-V <-> LLVM-IR converter and some consensus seems to have formed. Most of the people I talked to favored having the converter become an external tool within the LLVM project, similar to libclc. I think that the LLVM project's processes, infrastructure and

On 02/12/2018 12:52 PM, Gerd Hoffmann wrote: > Hi, > >> can we reach agreement on whether vsock should be involved in this? > > I think the best approach would be to have guest proxy and host proxy > use vsock for the wayland protocol. Use a wayland protocol extension to > reference the buffers in stdvga / ivshmem / virtio-gpu. Only the two > proxies need to

On 02/12/2018 12:52 PM, Gerd Hoffmann wrote: > Hi, > >> can we reach agreement on whether vsock should be involved in this? > > I think the best approach would be to have guest proxy and host proxy > use vsock for the wayland protocol. Use a wayland protocol extension to > reference the buffers in stdvga / ivshmem / virtio-gpu. Only the two > proxies need to