Re: [PATCH v7 04/10] accel/rocket: Add job submission IOCTL

2025-07-11 Thread Tomeu Vizoso
On Fri, Jul 11, 2025 at 6:40 PM Robin Murphy wrote: > > On 11/07/2025 5:00 pm, Tomeu Vizoso wrote: > > On Tue, Jun 24, 2025 at 3:50 PM Robin Murphy wrote: > >> > >> On 2025-06-06 7:28 am, Tomeu Vizoso wrote: > >> [...] > >>> diff --git a/drivers/accel/rocket/rocket_device.h > >>> b/drivers/accel

Re: [PATCH v7 04/10] accel/rocket: Add job submission IOCTL

2025-07-11 Thread Robin Murphy
On 11/07/2025 5:00 pm, Tomeu Vizoso wrote: On Tue, Jun 24, 2025 at 3:50 PM Robin Murphy wrote: On 2025-06-06 7:28 am, Tomeu Vizoso wrote: [...] diff --git a/drivers/accel/rocket/rocket_device.h b/drivers/accel/rocket/rocket_device.h index 10acfe8534f00a7985d40a93f4b2f7f69d43caee..50e46f0516

Re: [PATCH v7 04/10] accel/rocket: Add job submission IOCTL

2025-07-11 Thread Tomeu Vizoso
On Tue, Jun 24, 2025 at 3:50 PM Robin Murphy wrote: > > On 2025-06-06 7:28 am, Tomeu Vizoso wrote: > [...] > > diff --git a/drivers/accel/rocket/rocket_device.h > > b/drivers/accel/rocket/rocket_device.h > > index > > 10acfe8534f00a7985d40a93f4b2f7f69d43caee..50e46f0516bd1615b5f826c5002a6c0ecbf9

Re: [PATCH v7 04/10] accel/rocket: Add job submission IOCTL

2025-06-30 Thread Rob Herring
On Fri, Jun 6, 2025 at 1:29 AM Tomeu Vizoso wrote: > > Using the DRM GPU scheduler infrastructure, with a scheduler for each > core. > > Userspace can decide for a series of tasks to be executed sequentially > in the same core, so SRAM locality can be taken advantage of. > > The job submission cod

Re: [PATCH v7 04/10] accel/rocket: Add job submission IOCTL

2025-06-24 Thread Robin Murphy
On 2025-06-06 7:28 am, Tomeu Vizoso wrote: [...] diff --git a/drivers/accel/rocket/rocket_device.h b/drivers/accel/rocket/rocket_device.h index 10acfe8534f00a7985d40a93f4b2f7f69d43caee..50e46f0516bd1615b5f826c5002a6c0ecbf9aed4 100644 --- a/drivers/accel/rocket/rocket_device.h +++ b/drivers/acc

[PATCH v7 04/10] accel/rocket: Add job submission IOCTL

2025-06-05 Thread Tomeu Vizoso
Using the DRM GPU scheduler infrastructure, with a scheduler for each core. Userspace can decide for a series of tasks to be executed sequentially in the same core, so SRAM locality can be taken advantage of. The job submission code was initially based on Panfrost. v2: - Remove hardcoded number