On 24.07.2024 03:14, Techguru wrote: > I am in the process of getting up to speed on your governance > policies, applied for Coverity access to use some of the known issues > there as training wheels, and putting my gitlab fork into good working > order with CI. > > I would rather not duplicate effort which has already been proposed, > so definitely open to any pointers, any requests for how to chunk > things into smaller patches, any requests for particular > ordering/sequencing of patch sets. > > Some obvious areas: 16k pages;
For this I'd suggest that you start with a conceptual model rather than thinking of patches straight away. It has been the topic of past discussions, without - iirc - conclusive results. I'm sure you're aware that 4k page size is, sadly, baked into certain parts of the public interface (see e.g. io/ring.h). Otoh it may well be that you're goal is explicitly not to be able to run any guests working with 4k pages. If so, what would need ensuring is that such guests would cleanly fail to start, rather than crash early in a cryptic way. Jan > device trees; interrupts; power > management; any essential device drivers. > > >
