summaryrefslogtreecommitdiff
path: root/timer.h
diff options
context:
space:
mode:
authorTobias Klauser <tklauser@distanz.ch>2016-12-16 12:02:06 +0100
committerTobias Klauser <tklauser@distanz.ch>2016-12-16 12:02:06 +0100
commit374141decf7c9978fd2c535099440d68e11e7683 (patch)
treee4319060aea90473e47488a04f09ea995a609d59 /timer.h
parent074f8fc82ff26bb02c3c09f6ed71bca77e08e020 (diff)
trafgen: proto: Zero out the correct packet slot
In the third attempt, finally do the packet slot zeroing correctly. Zero the struct packet in __init_new_packet_slot() not the struct packet_dyn in __init_new_counter_slot(). Don't know what hit me yesterday... Fixes: d6d511ecff24 ("trafgen: proto: Zero out newly allocated struct packet") Signed-off-by: Tobias Klauser <tklauser@distanz.ch>
Diffstat (limited to 'timer.h')
0 files changed, 0 insertions, 0 deletions
the microcode engine is shared between the two threads, the update on CPU1 doesn't happen because it has already happened on CPU0 and we don't find a newer microcode revision on CPU1. Which doesn't set the intel_ucode_patch pointer and at initrd jettisoning time we don't save the microcode patch for later application. Now, when we suspend to RAM, the loaded microcode gets cleared so we need to reload but there's no patch saved in the cache. Removing the optimization fixes this issue and all is fine and dandy. Fixes: 06b8534cb728 ("x86/microcode: Rework microcode loading") Signed-off-by: Borislav Petkov <bp@suse.de> Reviewed-by: Thomas Gleixner <tglx@linutronix.de> Link: http://lkml.kernel.org/r/20170120202955.4091-2-bp@alien8.de Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'net/9p/mod.c')