LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org> To: torvic9@mailbox.org Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "x86@kernel.org" <x86@kernel.org>, "clang-built-linux@googlegroups.com" <clang-built-linux@googlegroups.com>, "graysky@archlinux.us" <graysky@archlinux.us> Subject: Re: [PATCH 2/2] x86, Makefile: Add new generic x86-64 settings v2/v3/v4 Date: Wed, 18 Aug 2021 08:15:17 +0100 [thread overview] Message-ID: <YRyzhWJrqcRZkYRM@infradead.org> (raw) In-Reply-To: <796036867.117557.1629210288168@office.mailbox.org> On Tue, Aug 17, 2021 at 04:24:48PM +0200, torvic9@mailbox.org wrote: > + Generic x86-64 CPU. > + Run equally well on all x86-64 CPUs with min support of x86-64-v2. > + help > + Generic x86-64-v3 CPU with v3 instructions. > + Run equally well on all x86-64 CPUs with min support of x86-64-v3. > + > + help > + Generic x86-64 CPU with v4 instructions. > + Run equally well on all x86-64 CPUs with min support of x86-64-v4. How the f&%$% is a user supposed to know what these garbage descriptions are supposed to mean?
next prev parent reply other threads:[~2021-08-18 7:16 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-17 14:23 [PATCH 1/2] x86, Makefile: Move the CPU-specific 64-bit tuning settings to arch/x86/Makefile.cpu torvic9 2021-08-17 14:24 ` [PATCH 2/2] x86, Makefile: Add new generic x86-64 settings v2/v3/v4 torvic9 2021-08-17 18:17 ` Nick Desaulniers 2021-08-17 18:22 ` Nick Desaulniers 2021-08-17 18:31 ` Tor Vic 2021-08-17 18:47 ` Nick Desaulniers 2021-08-17 18:36 ` Borislav Petkov 2021-08-17 19:12 ` Tor Vic 2021-08-18 15:08 ` torvic9 2021-08-18 17:59 ` Borislav Petkov 2021-08-18 18:28 ` Tor Vic 2021-08-18 18:43 ` Borislav Petkov 2021-08-18 7:15 ` Christoph Hellwig [this message] 2021-08-18 9:46 ` torvic9 2021-08-19 21:58 ` David Laight 2021-08-17 17:58 ` [PATCH 1/2] x86, Makefile: Move the CPU-specific 64-bit tuning settings to arch/x86/Makefile.cpu Nick Desaulniers 2021-08-17 18:28 ` Tor Vic 2021-08-18 7:11 ` Christoph Hellwig 2021-08-18 9:46 ` torvic9 2021-08-18 14:51 ` Masahiro Yamada
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=YRyzhWJrqcRZkYRM@infradead.org \ --to=hch@infradead.org \ --cc=clang-built-linux@googlegroups.com \ --cc=graysky@archlinux.us \ --cc=linux-kernel@vger.kernel.org \ --cc=torvic9@mailbox.org \ --cc=x86@kernel.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).