From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw1-x112e.google.com (mail-yw1-x112e.google.com [IPv6:2607:f8b0:4864:20::112e]) by sourceware.org (Postfix) with ESMTPS id 448DA3858C2C for ; Tue, 7 Mar 2023 20:34:19 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 448DA3858C2C Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-yw1-x112e.google.com with SMTP id 00721157ae682-536cb25982eso266336697b3.13 for ; Tue, 07 Mar 2023 12:34:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678221258; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=s7pX57NlkL7PN+rpOUxcZAIp1AuPvbtvp1POQzfg0BU=; b=MOBDsJhGuiUdf43LY+lCbfmPcvJe6IU6XMfhqpM+XLOaqgRcb0HZqVqZtQUulwK5ir cOo0ethvdvKHYBkgXpkFOxAVzFwwxvRI7KiJ/ZyYtv1YNrpi/hO1NS0bBEGCY5piOKFx 22JWJOgHWft6LAltooylyL4UZbGAJYAbctJHMOXJCEOGAb2QJYYf24w7vElJFJjWUpzk Fjos9150Cn08LPwA2N06Cm5UCKg6k7uwxgDN8aqxO5kJ6KsRvEOzFzx9TtCOLk824cS0 5/jcgAOYw+QcC8b8XPE/ZDD/6i/eidRVOfD9UfpF9eG+wQzctF0Q997mAnu1KvZAOG1y h0Gg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678221258; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=s7pX57NlkL7PN+rpOUxcZAIp1AuPvbtvp1POQzfg0BU=; b=DRW5mhpvdqNteoUOh5EqZFgVMjzhkAPkdqiQq/3ZLLjLSPP470VC+wmLhuluNv4P4T mCWFUWRYUdt354Wx8gexO8cICL87BD0FVTfI4AWOlBvDGrTyrHvpcDa13qKAYeYyCcv7 AsZB7AZGEJ5Kjgt72hIakFKJhocS45f9Enlvn0/4YqixeJZgmZLV1okp2EoBgbzZ34rk tJaqFFyT4nRGjn0r4o0WGpvdZ8kjY9REHVe5c+G3D99BDMyGtT0YriT27QI2pkFlvXeM Jer41rlvn2Aj38TXWhyWLr4nGw66FKB4TkYnuq42NrSYzExzOtPEe/ESs2Q+ddcm3BL7 GSHw== X-Gm-Message-State: AO0yUKWDzmYEjmR9zBUzND4jstX4F/LddinwOLCVc27gWy5WE+1HocLu yV8HZ4PBxJypCqrFQ/ygaHGAH4cRP7SzeR9vckc= X-Google-Smtp-Source: AK7set/0+TmIOrrltuNsif1XC5fG6w7TGNWpi1w5V9xY2QK/+GpSQFzQOYesRALhbBx9bQ/N/w6P+3kqk4OfUA0CJgA= X-Received: by 2002:a81:a9c8:0:b0:52e:e8b1:d51e with SMTP id g191-20020a81a9c8000000b0052ee8b1d51emr10249728ywh.1.1678221258604; Tue, 07 Mar 2023 12:34:18 -0800 (PST) MIME-Version: 1.0 References: <764b9e03-18bd-6945-692f-a250522196ca@suse.com> In-Reply-To: From: "H.J. Lu" Date: Tue, 7 Mar 2023 12:33:42 -0800 Message-ID: Subject: Re: [PATCH 00/18] x86: new .insn directive To: Jan Beulich Cc: Binutils , "Jiang, Haochen" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-3016.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Mon, Mar 6, 2023 at 1:26=E2=80=AFAM Jan Beulich wrot= e: > > On 03.03.2023 17:50, H.J. Lu wrote: > > X86 encoding scheme is quite complex. It may get even more complex in > > the future. > > Indeed. Also some complexities did exist only transiently, like AMD's > DREX. MVEX is mentioned in the series, and I'm not sure whether to > call this "historic" as well. However, ... > > > I suggest we wait for a while so that we can get clear pictures > > what the future encoding scheme looks like. > > ... I have to admit that I'm puzzled by this suggestion. The rate at > which new encoding schemes appear is pretty low. So unless you know > of something to see the (public) light of day soon, I wonder what > meaning you assign to "a while". The plan certainly is for this work > to land well in time for 2.40, unless there are clear technical > issues speaking against it. In no event do I plan to wait very long > with committing not directly .insn-related changes in the series, > like patches 06 ... 09 or even 10, and maybe 04 as well as 12. > > I shall perhaps also add that I view entirely new encoding schemes > as less of a problem - support for them can be added to .insn > handling incrementally. What could be more problematic are changes > to one of the existing schemes. > We will evaluate if these changes will cause any potential issues for the future. --=20 H.J.