migration: merge enforce_config_section somewhat
commit4ffdb337e74f9a4dae97ea0396d4e1a3dbb13723
authorPeter Xu <peterx@redhat.com>
Tue, 27 Jun 2017 04:10:18 +0000 (27 12:10 +0800)
committerJuan Quintela <quintela@redhat.com>
Wed, 28 Jun 2017 09:18:39 +0000 (28 11:18 +0200)
tree2243b983606fe0232371458a3fe1ad43dd7336db
parent15c38503253bb9ba9b8efd17662069f69ca2b997
migration: merge enforce_config_section somewhat

These two parameters:

- MachineState::enforce_config_section
- MigrationState::send_configuration

are playing similar role here. This patch merges the first one into
second, then we'll have a single place to reference whether we need to
send the configuration section.

I didn't remove the MachineState.enforce_config_section field since when
applying that machine property (in machine_set_property()) we haven't
yet initialized global properties and migration object. Then, it's
still not easy to pass that boolean to MigrationState at such an early
time.

A natural benefit for current patch is that now we kept the meaning of
"enforce-config-section" since it'll still have the highest
priority (that's what "enforce" mean I guess).

Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <1498536619-14548-10-git-send-email-peterx@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
migration/migration.c
migration/savevm.c