Re: [PATCH] rust: add basic ELF sections parser

[Danilo Krummrich <dakr@kernel.org>]

On Fri, May 16, 2025 at 12:00:11PM -0700, John Hubbard wrote:
> On 5/16/25 9:01 AM, Danilo Krummrich wrote:
> > I did not argue for or against it -- what I do disagree with is that we seem to
> > just agree to disagree and stuff a generic piece of code into nova-core after
> > three mails back and forth.
> > 
> > Please keep discussing the above with Greg until we get to a real conclusion.
> 
> Danilo, this is a small amount of code. Is there any real problem with
> a compromise, that starts out with Greg's approach of putting this code
> in Nova?
> 
> And then we can promote it if and when we can make a good case for that.
> 
> But in the meantime, we really need to be able to take "yes" (from Greg)
> for an answer! I don't want to blow up the firmware images, shred
> the "Nouveau and Nova can use the same images" story, and delay merging,
> all over 100 lines of code.

What I disagree with is that it seems that you actually *can* "make a good case
for it", but stop discussing it with Greg, because he would agree with just
stuffing this generic infrastructure in the driver.

It seems like taking the way of least resistance even though you seem to have
good arguments for this to be generic infrastructure.

The fact that *only* nova-core would use it to begin with is not the relevant
factor. nova-core is, for obvious reasons, the only user of quite some generic
infrastructure, yet we don't stuff it into the driver.

The relevant factor is, do we agree that this is a valid requirement for drivers
in general (which you seem to answer with a clear "yes"). Which means we should
keep discussing it.

If we can't conclude that this should be generic infrastructure, we can still
figure out the way forward for nova-core (i.e. have our own ELF parser in
nova-core if necessary).

But, as I said above, please don't stop the discussion with agreeing to disagree
after three mails back and forth.

We have plenty of time to discuss it; we do not target v6.16 and the v6.17 merge
window is far away.

- Danilo