>
> The sane pattern is and seems to has always been.
>
> arch_function()
> {
> platform_ops.platform_function();
> }
Yes agreed. We'll slowly move there. Patches to accelerate it are
welcome (for post .22)
But you're flaming the wrong person for this really. Jeremy and other
paravirt implementors have done a lot of work of moving things into this
direction.
> At the same time I find it very distressing how many functions named
> native_xxx we are accumulating. Especially when all native refers is
> to the default i386 subarch and not to anything particularly native.
> Just one particular way something was implemented.
How else would you name and/or implement that?
> The fact that 2 level or 3 level page tables can't be selected at
> runtime seems to be a failing to think of themselves as a generic
> a subarch mechanism. I can't fault you to much for that one as
> that is a little off the beaten path.
That would really require generic mm changes to do properly. I know
PA-RISC does it without that, but that wouldn't fly on x86 I think
because PAE and non PAE are more different there.
-Andi
_______________________________________________
Virtualization mailing list
Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/virtualization
