From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758853AbbFBQYR (ORCPT ); Tue, 2 Jun 2015 12:24:17 -0400 Received: from cantor2.suse.de ([195.135.220.15]:47273 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754099AbbFBQYL (ORCPT ); Tue, 2 Jun 2015 12:24:11 -0400 Date: Tue, 2 Jun 2015 18:24:03 +0200 From: Borislav Petkov To: Andy Shevchenko Cc: Ingo Molnar , linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/1] x86/microcode: vsnprintf() might be unavailable Message-ID: <20150602162403.GD20576@pd.tnic> References: <1433257003-159485-1-git-send-email-andriy.shevchenko@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <1433257003-159485-1-git-send-email-andriy.shevchenko@linux.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 02, 2015 at 05:56:43PM +0300, Andy Shevchenko wrote: > On Intel CPUs with x32 kernels we call load_builtin_intel_microcode() from > head_32.S on quite earlier stage. At that point sprintf() might be out of scope > to be called. Hrrm, I don't get that. How can sprintf() be out of scope? Testing on 32-bit was successful here. How is x32 different? Thanks. -- Regards/Gruss, Boris. ECO tip #101: Trim your mails when you reply. --