On 06.02.15 04:55, David Gibson wrote: > At the moment, the PAPR RTC implementation (actually a paravirt > firmware interface, rather than a normal device) works directly off > host time, and so doesn't respect the options such as clock=vm which > can be specified in the -rtc command line option. This series > addresses those defects. > > The above makes it clearer that the spapr RTC should probably be its > own separate qdev, so this series also implements that. > > Finally it moves the code from mc146818rtc for publishing the RTC time > via QOM into generic QOM helpers, and extends the PAPR RTC driver to > export in a similar way. > > Changes since v2: > * We still need the rtc_offset field in sPAPREnvironment to handle > incoming migrations from older versions, but we no longer send it > for outgoing migrations. > Changes since v1: > * Actually create a qdev device for the PAPR RTC > * Instead of duplicating the QOM publishing code from mc146818, move > it into a generic helper >
Thanks, applied to ppc-next. Alex
