Fabian Ruffy

> It sounds like this DEBUG configuration is what I'd call a "fringe" case: It kinda matters, or at least it's interesting, but the upside of running them continually is...

Sounds great! Let me know if you have questions or confusion. I think the linked program should be the majority of the kernel code.

Is this ready for review?

> a successful test run of the p4c PTF test suite using the modified bmv2 + veths for packet I/O. Assuming there is such a thing... cc @fruffy It depends......

There was a similar PR once but it was never resolved https://github.com/p4lang/p4c/pull/3669. I guess this one supersedes it. Related P4-specification issue: https://github.com/p4lang/p4-spec/issues/1139

The P4Testgen failures are because of crashes in BMv2. It is possible that the generated JSON is invalid.

Depends on #4728.

@vlstill This passes now after #4728 has been merged.

> I'd like to contribute to this issue, can you let me know how i can solve it. This could be larger in scope. Essentially what needs to be done...

> Hi may work on this @fruffy ? Sure! Feel free to make a PR. But it could be a fair bit of work.