On 01/04/2012 10:07 PM, Alexander Graf wrote: > Ok here's another idea on how to handle this. What if we encode the > register size in the constant? That way, if the register grows later, > we can still be backwards compatible, but give user space exactly the > size it asks for. > > We could then just take a void* from user space and merely c_t_u and c_f_u the value in exactly the size defined by the constant. > Later, for MANY_REGS we could then just take a list of registers and write a bytestream of results to a user pointer. > > That should be a lot easier and efficient than an interface that treats everything as u64. OK. > Alex > >> >> Btw, any reason you're only bringing up these really great ideas on my 2nd pull request after these patches were uncommented on the ML for quite a while? :) Sorry about that -- I was trying to focus on getting e500mc patches out before vacation (and various other distractions), and missed looking at the patch itself the first time around. -Scott -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
