On 07/21/2011 03:52 PM, Jan Kiszka wrote:
> > The problem is that "update" can change lots of things. offset, size, > whether it's mmio or RAM, read-onlyness, even the wierd things like > coalesced mmio. So it's either a function with 324.2 parameters (or a > large struct), or it's a series of functions with demarcation as to > where the update begins and ends. We do not need to provide update support for each and every bit, but for the common cases. memory_region_update_alias(region, offset, size) would be an excellent first candidate IMO.
It's not enough, look at cirrus and PAM. -- error compiling committee.c: too many arguments to function -- 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
