Date: Thu, 10 May 2018 21:22:27 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 192487] cpucontrol uses unsafe procedure to detect current microcode version Message-ID: <bug-192487-227-mQPD0zU79N@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-192487-227@https.bugs.freebsd.org/bugzilla/> References: <bug-192487-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D192487 --- Comment #8 from Stefan B. <sblachmann@gmail.com> --- Ed, this would be great. May I point you at another issue: in the current implementation, the eval_cpu_features system call output from cpuctl.ko goes to the console, spamming a half screenful of information - for each and every core again. T= his can be a *lot* of dmesg spam. I would be willing to address this too when merging-in Dan's suggested chan= ges. Warner suggested that cpupdate being put on phabricator, but I haven't heard from him for a while. He seems very busy and told me that my initial reply = got into his spam folder somehow. Could you maybe cc him and ask him whether he= got my email from April 24th? What about putting cpupdate, the updated cpuctl and cpucontrol on phabricat= or then, so these can be reviewed together? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-192487-227-mQPD0zU79N>