diff options
| author | Jan Beulich <jbeulich@suse.com> | 2013-09-23 16:23:52 +0200 |
|---|---|---|
| committer | Jan Beulich <jbeulich@suse.com> | 2013-09-23 16:23:52 +0200 |
| commit | 6916c31d0ea7deeedbfe5e034202567c73b73a4e (patch) | |
| tree | b46528c435c01702f3339a32631aa2c5da5f5517 /tools/blktap2/drivers/hashtable_utility.c | |
| parent | 9e5a66bc88a0cf0ff0f3339381a2332f305d1a9c (diff) | |
| download | xen-6916c31d0ea7deeedbfe5e034202567c73b73a4e.tar.gz xen-6916c31d0ea7deeedbfe5e034202567c73b73a4e.tar.bz2 xen-6916c31d0ea7deeedbfe5e034202567c73b73a4e.zip | |
x86: machine_restart() must not call acpi_dmar_reinstate() twice
.. as that function is not idempotent (it always alters the table
checksum). The (generally) duplicate call was a result from it being
made before machine_restart() re-invoking itself on the boot CPU.
Considering that no problem arose so far from the table corruption I
doubt that we need to restore the correct table signature on the
reboot path in general. The only case I can see this as potentially
necessary is the tboot one, hence do the call just in that case.
Signed-off-by: Jan Beulich <jbeulich@suse.com>
Acked-by: Keir Fraser <keir@xen.org>
master commit: a54dc5f4fe1eae6b1beb21326ef0338cd3969cd1
master date: 2013-09-13 14:27:34 +0200
Diffstat (limited to 'tools/blktap2/drivers/hashtable_utility.c')
0 files changed, 0 insertions, 0 deletions