Alyssa Rosenzweig <aly...@rosenzweig.io> writes:
>> @@ -55,6 +63,15 @@ struct drm_panfrost_submit {
>>  
>>      /** A combination of PANFROST_JD_REQ_* */
>>      __u32 requirements;
>> +
>> +    /** Pointer to a u32 array of perfmons that should be attached to the 
>> job. */
>> +    __u64 perfmon_handles;
>> +
>> +    /** Number of perfmon handles passed in (size is that times 4). */
>> +    __u32 perfmon_handle_count;
>> +
>> +    /** Unused field, should be set to 0. */
>> +    __u32 padding;
>
> Bleep blorp. If we're modifying _submit, we'll need to be swift about
> merging this ahead of the main code to make sure we don't break the
> UABI. Although I guess if we're just adding fields at the end, that's a
> nonissue.

You can extend ioctl structs safely.  When older userspace passes theirs
in, it has the shorter length encoded in the cmd. The kernel allocates
the newest version's space, copies in the shorter struct, and
zero-extends the rest.

Attachment: signature.asc
Description: PGP signature

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Reply via email to