From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 276E1C433C1 for ; Fri, 26 Mar 2021 18:18:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D79A661A44 for ; Fri, 26 Mar 2021 18:18:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230202AbhCZSRc (ORCPT ); Fri, 26 Mar 2021 14:17:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44648 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230224AbhCZSRW (ORCPT ); Fri, 26 Mar 2021 14:17:22 -0400 Received: from mail.skyhub.de (mail.skyhub.de [IPv6:2a01:4f8:190:11c2::b:1457]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6BE45C0613B1; Fri, 26 Mar 2021 11:17:22 -0700 (PDT) Received: from zn.tnic (p200300ec2f075f009137b2b45d3c68fe.dip0.t-ipconnect.de [IPv6:2003:ec:2f07:5f00:9137:b2b4:5d3c:68fe]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.skyhub.de (SuperMail on ZX Spectrum 128k) with ESMTPSA id CB25E1EC0535; Fri, 26 Mar 2021 19:17:20 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alien8.de; s=dkim; t=1616782640; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=lCGNB4Q23IgTbOgpsWfCfXWoIrcS1GBbFYaRAmoXHaw=; b=mrts/cj+qTY4IQ8mWSMmtJDsPGhFhOtWksTbeSNSOWLgOwOlbe7f0iYnARoyrxab57W/jj t1bW91zURmlEf5jpwLervY3VhwvTZhj87S9vHOrufA+d8fdaVIFBW4k1+Eq5Y/HlscILAq wLjc1EEY9WS9zOvCmm+WZuXmij9x4dY= Date: Fri, 26 Mar 2021 19:17:17 +0100 From: Borislav Petkov To: Len Brown Cc: Andy Lutomirski , Thomas Gleixner , "Chang S. Bae" , Ingo Molnar , X86 ML , "Brown, Len" , Dave Hansen , "Liu, Jing2" , "Ravi V. Shankar" , Linux Kernel Mailing List , Linux Documentation List Subject: Re: [PATCH v4 22/22] x86/fpu/xstate: Introduce boot-parameters to control state component support Message-ID: <20210326181641.GD27507@zn.tnic> References: <20210221185637.19281-1-chang.seok.bae@intel.com> <20210221185637.19281-23-chang.seok.bae@intel.com> <871rc9bl3v.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 26, 2021 at 01:53:47PM -0400, Len Brown wrote: > At Dave's suggestion, we had a 64 *KB* sanity check on this path. > Boris forced us to remove it, because we could not tell him > how we chose the number 64. The only 64 I can remember is #define XSTATE_BUFFER_MAX_BYTES (64 * 1024) What does an arbitrary number have to do with signal handling and pushing a fat frame on the sigaltstack? -- Regards/Gruss, Boris. SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 36809, AG Nürnberg