Use one subsection for each feature. This means that we don't need to
bump the version field each time that a new feature gets introduced.
Introduce cpsr_vmstate field, as I am not sure if I can use
uncached_cpsr for saving state.
Signed-off-by: Juan Quintela quint...@redhat.com
---
On 4 May 2012 11:54, Juan Quintela quint...@redhat.com wrote:
Use one subsection for each feature. This means that we don't need to
bump the version field each time that a new feature gets introduced.
Introduce cpsr_vmstate field, as I am not sure if I can use
uncached_cpsr for saving state.
Peter Maydell peter.mayd...@linaro.org wrote:
On 4 May 2012 11:54, Juan Quintela quint...@redhat.com wrote:
Use one subsection for each feature. This means that we don't need to
bump the version field each time that a new feature gets introduced.
Introduce cpsr_vmstate field, as I am not
On 4 May 2012 16:28, Juan Quintela quint...@redhat.com wrote:
The only other sane approach that I can think is changing:
#define VMSTATE_INT32_V(_f, _s, _v) \
into something like:
VMSTATE_INT32_GENERAL(_f, _s, _v, _getter, _setter)
and then
