On 5 January 2012 00:16, Anthony Liguori <anth...@codemonkey.ws> wrote: > On 01/04/2012 05:33 PM, Peter Maydell wrote: >> A lot of the usage of target_phys_addr_t in hw/ is actually not >> handling addresses at all, but merely offsets into device IO regions >> (ie as parameters to device read/write functions)... > > Exactly, which is why using target_phys_addr_t (and subsequently building > the device twice) doesn't make a lot of sense.
So should we have a hw_offset type for this? That would cut out a lot of the noise and let us find out how much code in hw/ is actually using physaddrs... -- PMM
