On Wed, Sep 04, 2024 at 05:34:42PM +0300, Jani Nikula wrote:
> On Wed, 04 Sep 2024, Andi Shyti wrote:
> > Hi Sima,
> >
> > On Tue, Aug 27, 2024 at 07:05:05PM +0200, Daniel Vetter wrote:
> >> On Mon, Aug 19, 2024 at 01:31:40PM +0200, Andi Shyti wrote:
> >> > The i915 driver generates sysfs entries
On 04/09/2024 15:34, Jani Nikula wrote:
On Wed, 04 Sep 2024, Andi Shyti wrote:
Hi Sima,
On Tue, Aug 27, 2024 at 07:05:05PM +0200, Daniel Vetter wrote:
On Mon, Aug 19, 2024 at 01:31:40PM +0200, Andi Shyti wrote:
The i915 driver generates sysfs entries for each engine of the
GPU in /sys/clas
On Wed, 04 Sep 2024, Andi Shyti wrote:
> Hi Sima,
>
> On Tue, Aug 27, 2024 at 07:05:05PM +0200, Daniel Vetter wrote:
>> On Mon, Aug 19, 2024 at 01:31:40PM +0200, Andi Shyti wrote:
>> > The i915 driver generates sysfs entries for each engine of the
>> > GPU in /sys/class/drm/cardX/engines/.
>> >
>
Hi Sima,
On Tue, Aug 27, 2024 at 07:05:05PM +0200, Daniel Vetter wrote:
> On Mon, Aug 19, 2024 at 01:31:40PM +0200, Andi Shyti wrote:
> > The i915 driver generates sysfs entries for each engine of the
> > GPU in /sys/class/drm/cardX/engines/.
> >
> > The process is straightforward: we loop over t
On Tue, Aug 27, 2024 at 07:05:05PM +0200, Daniel Vetter wrote:
> On Mon, Aug 19, 2024 at 01:31:40PM +0200, Andi Shyti wrote:
> > The i915 driver generates sysfs entries for each engine of the
> > GPU in /sys/class/drm/cardX/engines/.
> >
> > The process is straightforward: we loop over the UABI en
On Mon, Aug 19, 2024 at 01:31:40PM +0200, Andi Shyti wrote:
> The i915 driver generates sysfs entries for each engine of the
> GPU in /sys/class/drm/cardX/engines/.
>
> The process is straightforward: we loop over the UABI engines and
> for each one, we:
>
> - Create the object.
> - Create basi
Hi Rodrigo,
On Fri, Aug 23, 2024 at 09:41:31AM -0400, Rodrigo Vivi wrote:
> On Wed, Aug 21, 2024 at 09:32:48AM +0200, Andi Shyti wrote:
> > On Tue, Aug 20, 2024 at 05:22:40PM -0400, Rodrigo Vivi wrote:
> > > On Mon, Aug 19, 2024 at 01:31:40PM +0200, Andi Shyti wrote:
...
> > > > It might make sens
On Wed, Aug 21, 2024 at 09:32:48AM +0200, Andi Shyti wrote:
> Hi Rodrigo,
>
> On Tue, Aug 20, 2024 at 05:22:40PM -0400, Rodrigo Vivi wrote:
> > On Mon, Aug 19, 2024 at 01:31:40PM +0200, Andi Shyti wrote:
> > > The i915 driver generates sysfs entries for each engine of the
> > > GPU in /sys/class/d
Hi Again, Rodrigo,
...
> > Also it looks something is off with the goto paths...
> >
> > That if (0) is also ugly... probably better to use a
> > kobject_put with continue on every failing point as well...
>
> ehehe... I came to like it, to be honest. Besides I like single
> exit paths instead
Hi Rodrigo,
On Tue, Aug 20, 2024 at 05:22:40PM -0400, Rodrigo Vivi wrote:
> On Mon, Aug 19, 2024 at 01:31:40PM +0200, Andi Shyti wrote:
> > The i915 driver generates sysfs entries for each engine of the
> > GPU in /sys/class/drm/cardX/engines/.
> >
> > The process is straightforward: we loop over
On Mon, Aug 19, 2024 at 01:31:40PM +0200, Andi Shyti wrote:
> The i915 driver generates sysfs entries for each engine of the
> GPU in /sys/class/drm/cardX/engines/.
>
> The process is straightforward: we loop over the UABI engines and
> for each one, we:
>
> - Create the object.
> - Create basi
The i915 driver generates sysfs entries for each engine of the
GPU in /sys/class/drm/cardX/engines/.
The process is straightforward: we loop over the UABI engines and
for each one, we:
- Create the object.
- Create basic files.
- If the engine supports timeslicing, create timeslice duration fi
12 matches
Mail list logo
