From: Ard Biesheuvel <ardb@kernel.org> To: "Jason A. Donenfeld" <Jason@zx2c4.com> Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Stephen Boyd <swboyd@chromium.org>, Catalin Marinas <catalin.marinas@arm.com>, Russell King <linux@armlinux.org.uk>, Arnd Bergmann <arnd@arndb.de>, Phil Elwell <phil@raspberrypi.com> Subject: Re: [PATCH] random: do not use jump labels before they are initialized Date: Tue, 7 Jun 2022 14:03:28 +0200 [thread overview] Message-ID: <CAMj1kXF7NToZgAW66puCOwc1+d7ZTmVm_CbDYEeH+j0XJH1vug@mail.gmail.com> (raw) In-Reply-To: <Yp839NjwW3scZEqi@zx2c4.com> On Tue, 7 Jun 2022 at 13:35, Jason A. Donenfeld <Jason@zx2c4.com> wrote: > > Hi Ard, > > On Tue, Jun 07, 2022 at 01:10:52PM +0200, Ard Biesheuvel wrote: > > Fair enough. What I would like is to remove the need to play around > > with the placement of jump_label_init() across architectures. Jump > > labels are fundamentally a performance optimization, so unless you can > > explain how setting it as early as possible makes a material > > difference, performance or otherwise, I really think we should pursue > > a solution that does the static key manipulation at some later time. > > Alright. It sounds like Catalin also prefers the same. This seems simple > enough with minimal downsides: https://lore.kernel.org/lkml/20220607113238.769088-1-Jason@zx2c4.com/ > That looks simple enough. Do we risk causing any boot stalls due to the crediting being deferred? Or new warnings about randomness being used before CRNG is ready? > So maybe we should just go that route. > It is not my preferred approach, but I can live with it.
WARNING: multiple messages have this Message-ID (diff)
From: Ard Biesheuvel <ardb@kernel.org> To: "Jason A. Donenfeld" <Jason@zx2c4.com> Cc: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Stephen Boyd <swboyd@chromium.org>, Catalin Marinas <catalin.marinas@arm.com>, Russell King <linux@armlinux.org.uk>, Arnd Bergmann <arnd@arndb.de>, Phil Elwell <phil@raspberrypi.com> Subject: Re: [PATCH] random: do not use jump labels before they are initialized Date: Tue, 7 Jun 2022 14:03:28 +0200 [thread overview] Message-ID: <CAMj1kXF7NToZgAW66puCOwc1+d7ZTmVm_CbDYEeH+j0XJH1vug@mail.gmail.com> (raw) In-Reply-To: <Yp839NjwW3scZEqi@zx2c4.com> On Tue, 7 Jun 2022 at 13:35, Jason A. Donenfeld <Jason@zx2c4.com> wrote: > > Hi Ard, > > On Tue, Jun 07, 2022 at 01:10:52PM +0200, Ard Biesheuvel wrote: > > Fair enough. What I would like is to remove the need to play around > > with the placement of jump_label_init() across architectures. Jump > > labels are fundamentally a performance optimization, so unless you can > > explain how setting it as early as possible makes a material > > difference, performance or otherwise, I really think we should pursue > > a solution that does the static key manipulation at some later time. > > Alright. It sounds like Catalin also prefers the same. This seems simple > enough with minimal downsides: https://lore.kernel.org/lkml/20220607113238.769088-1-Jason@zx2c4.com/ > That looks simple enough. Do we risk causing any boot stalls due to the crediting being deferred? Or new warnings about randomness being used before CRNG is ready? > So maybe we should just go that route. > It is not my preferred approach, but I can live with it. _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-07 12:03 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-07 10:02 [PATCH] random: do not use jump labels before they are initialized Jason A. Donenfeld 2022-06-07 10:02 ` Jason A. Donenfeld 2022-06-07 10:13 ` Ard Biesheuvel 2022-06-07 10:13 ` Ard Biesheuvel 2022-06-07 10:28 ` Jason A. Donenfeld 2022-06-07 10:28 ` Jason A. Donenfeld 2022-06-07 10:41 ` Jason A. Donenfeld 2022-06-07 10:41 ` Jason A. Donenfeld 2022-06-07 10:56 ` Ard Biesheuvel 2022-06-07 10:56 ` Ard Biesheuvel 2022-06-07 11:04 ` Jason A. Donenfeld 2022-06-07 11:04 ` Jason A. Donenfeld 2022-06-07 11:10 ` Ard Biesheuvel 2022-06-07 11:10 ` Ard Biesheuvel 2022-06-07 11:35 ` Jason A. Donenfeld 2022-06-07 11:35 ` Jason A. Donenfeld 2022-06-07 12:03 ` Ard Biesheuvel [this message] 2022-06-07 12:03 ` Ard Biesheuvel 2022-06-07 12:16 ` Jason A. Donenfeld 2022-06-07 12:16 ` Jason A. Donenfeld 2022-06-07 12:21 ` Ard Biesheuvel 2022-06-07 12:21 ` Ard Biesheuvel 2022-06-08 8:24 ` Ard Biesheuvel 2022-06-08 8:24 ` Ard Biesheuvel
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=CAMj1kXF7NToZgAW66puCOwc1+d7ZTmVm_CbDYEeH+j0XJH1vug@mail.gmail.com \ --to=ardb@kernel.org \ --cc=Jason@zx2c4.com \ --cc=arnd@arndb.de \ --cc=catalin.marinas@arm.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux@armlinux.org.uk \ --cc=phil@raspberrypi.com \ --cc=swboyd@chromium.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 an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.