On Wed, 2015-01-14 at 12:24 +0000, Julien Grall wrote: > On 13/01/15 15:58, Ian Campbell wrote: > > They don't actually have to be, but exposing vgic_allocate_virq to the > > tools would be overkill, so hardcoding is the pragmatic choice. > > > > We could e.g. randomise the PPI in the tools, to stop people making > > assumptions. (If we were feeling mean of course...) > > It would be nice to have a such think. If not randomize at each boot, > maybe per Xen version.
Like I say, that would be quite mean of us. (I was 99% joking about this FWIW, perhaps I needed to ring that bell a bit more though). > Though it would break mini-os on ARM as the IRQ is hardcoded in the OS. AIUI there is an eventual desire to have an ARM mini-os binary be portable across Xen versions, which will require dtb parsing for this stuff (actually, I thought the latest patches had added a bunch of such stuff, but maybe not this specific aspect). Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
