From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [RFC v2] misc/xenmicrocode: Upload /lib/firmware/ to the hypervisor Date: Fri, 12 Jun 2015 09:48:24 +0100 Message-ID: <557A9CD8.9010507@citrix.com> References: <1422580462-26324-1-git-send-email-mcgrof@do-not-panic.com> <54CB93F4.2050409@citrix.com> <20150130195131.GL19988@wotan.suse.de> <54CBEB8D.8030509@citrix.com> <20150130215701.GN19988@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Z3Kdf-0002K9-6n for xen-devel@lists.xenproject.org; Fri, 12 Jun 2015 08:48:35 +0000 In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Luis R. Rodriguez" Cc: Juergen Gross , Michal Marek , Jason Douglas , Stefano Stabellini , Takashi Iwai , Henrique de Moraes Holschuh , David Vrabel , Jan Beulich , xen-devel@lists.xenproject.org, Boris Ostrovsky , Borislav Petkov , Olaf Hering List-Id: xen-devel@lists.xenproject.org On 12/06/15 03:30, Luis R. Rodriguez wrote: > On Fri, Jan 30, 2015 at 1:57 PM, Luis R. Rodriguez wrote: >> On Fri, Jan 30, 2015 at 08:37:33PM +0000, Andrew Cooper wrote: >>> The right thing to do is to fix the hypercall implementation, at which >>> point the utility below is fine and xc_microcode_update() can be a thing >>> wrapper around the hypercall. >>> >>> The actions Xen needs to take are: >>> >>> - Copy the buffer into Xen. >>> - Scan the buffer for the correct patch >>> - Rendezvous all online cpus in an IPI to apply the patch, and keep the >>> processors in until all have completed the patch. >>> >>> The IPI itself probably wants common rendezvous code, and a system >>> specific call for application. The system specific call will need to >>> adhere to the requirements in the relevant manual. Care will have to be >>> taken to avoid deadlocking with the time calibration rendezvous, and >>> facilities such as the watchdog might temporally need pausing. >>> >>> If you feel up to all that, then please go ahead. If not, I will >>> attempt to find some copious free time. >> You can have a crack at that. Let me know when the above is ready and I'll >> respin. I'd try it but it seems you would spend considerbly less time than >> me doing the above. > Andrew, wanted to check to see if you have had time to work on the above. Sadly no - I have not had time. ~Andrew