linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Christophe Leroy <christophe.leroy@csgroup.eu>,
	mpe@ellerman.id.au, Nicholas Piggin <npiggin@gmail.com>,
	Naveen N Rao <naveen@kernel.org>,
	linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 2/2] powerpc/vdso: Implement __arch_get_vdso_rng_data()
Date: Mon, 7 Oct 2024 18:28:46 +0200	[thread overview]
Message-ID: <ZwQMPmfG5zDGz1Wr@zx2c4.com> (raw)
In-Reply-To: <Zv_1tqMf-RIXapBD@zx2c4.com>

On Fri, Oct 04, 2024 at 04:03:34PM +0200, Jason A. Donenfeld wrote:
> On Fri, Oct 04, 2024 at 08:52:40PM +1000, Michael Ellerman wrote:
> > 
> > 
> > On October 4, 2024 2:33:54 AM GMT+10:00, "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
> > >Hey Christophe, Michael,
> > >
> > >This series actually looks pretty okay to me. I realize ThomasW is
> > >working on more generic cleanups that might obliterate the need for
> > >this, and that may or may not wind up in 6.13. But, I was thinking, this
> > >seems like a good correct thing to do, and to do it now for 6.12, maybe
> > >as a fix through the powerpc tree. Then ThomasW can base his work atop
> > >this, which might wind up including the nice lr optimizations you've
> > >made. And then also if ThomasW's work doesn't land or gets reverted or
> > >whatever, at least we'll have this in tree for 6.12.
> > >
> > >Michael - what do you think of that? Worth taking these two patches into
> > >your fixes?
> > 
> > I agree the series looks good. But they're not fixes by my reading, so I'd be inclined to put them in next for v6.13?
> 
> They're "close enough" to fixes. The get_realdatapage stuff is super
> wonky and weird and it's quite good Christophe has gotten rid of it.
> Returning NULL from the generic accesor function never really sat right
> and looks buggy even if it does work. But more to the point, given the
> other scheduled churn for 6.13, it's going to be a tree-clashing
> nightmare to get this in later. And this Sunday is rc2 only, so why not.

Bumping to top of the box.

Jason


  reply	other threads:[~2024-10-07 16:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02  8:39 [PATCH 1/2] powerpc/vdso: Add a page for non-time data Christophe Leroy
2024-10-02  8:39 ` [PATCH 2/2] powerpc/vdso: Implement __arch_get_vdso_rng_data() Christophe Leroy
2024-10-03 16:33   ` Jason A. Donenfeld
2024-10-04 10:52     ` Michael Ellerman
2024-10-04 14:03       ` Jason A. Donenfeld
2024-10-07 16:28         ` Jason A. Donenfeld [this message]
2024-10-11 10:39           ` Michael Ellerman
2024-10-10  8:20   ` Thomas Weißschuh
2024-10-10  9:00     ` Christophe Leroy
2024-10-10  9:12       ` Thomas Weißschuh
2024-10-10  9:28         ` Christophe Leroy
2024-10-11 11:46           ` Michael Ellerman
2024-10-12  9:19             ` Christophe Leroy
2024-10-02  8:54 ` [PATCH 1/2] powerpc/vdso: Add a page for non-time data Thomas Weißschuh
2024-10-02 10:10   ` Christophe Leroy
2024-10-02 10:21     ` Thomas Weißschuh
2024-11-07  8:42 ` Michael Ellerman

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=ZwQMPmfG5zDGz1Wr@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michael@ellerman.id.au \
    --cc=mpe@ellerman.id.au \
    --cc=naveen@kernel.org \
    --cc=npiggin@gmail.com \
    /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: link
Be 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).