Linux kernel regressions
 help / color / mirror / Atom feed
From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Michael Ellerman" <mpe@ellerman.id.au>,
	"Thorsten Leemhuis" <regressions@leemhuis.info>,
	"Vaibhav Jain" <vaibhav@linux.ibm.com>,
	<linuxppc-dev@lists.ozlabs.org>, <kvm@vger.kernel.org>,
	<kvm-ppc@vger.kernel.org>
Cc: "Jordan Niethe" <jniethe5@gmail.com>,
	"Vaidyanathan Srinivasan" <svaidy@linux.vnet.ibm.com>,
	<mikey@neuling.org>, <paulus@ozlabs.org>, <sbhat@linux.ibm.com>,
	<gautam@linux.ibm.com>, <kconsul@linux.vnet.ibm.com>,
	<amachhiw@linux.vnet.ibm.com>, <David.Laight@ACULAB.COM>,
	"Linux kernel regressions list" <regressions@lists.linux.dev>
Subject: Re: [PATCH] KVM: PPC: Book3S HV nestedv2: Cancel pending HDEC exception
Date: Wed, 10 Apr 2024 14:28:07 +1000	[thread overview]
Message-ID: <D0G5QG4M991A.1QAWDKSYM6A89@gmail.com> (raw)
In-Reply-To: <87y19obfck.fsf@mail.lhotse>

On Mon Apr 8, 2024 at 3:20 PM AEST, Michael Ellerman wrote:
> Thorsten Leemhuis <regressions@leemhuis.info> writes:
> > On 05.04.24 05:20, Michael Ellerman wrote:
> >> "Linux regression tracking (Thorsten Leemhuis)"
> >> <regressions@leemhuis.info> writes:
> >>> Hi, Thorsten here, the Linux kernel's regression tracker. Top-posting
> >>> for once, to make this easily accessible to everyone.
> >>>
> >>> Was this regression ever resolved? Doesn't look like it, but maybe I
> >>> just missed something.
> >> 
> >> I'm not sure how it ended up on the regression list.
> >
> > That is easy to explain: I let lei search for mails containing words
> > like regress, bisect, and revert to become aware of regressions that
> > might need tracking. And...
> >
> >> IMHO it's not really a regression.
> >
> > ...sometimes I misjudge or misinterpret something and add it to the
> > regression tracking. Looks like that happened here.
> >
> > Sorry for that and the noise it caused!
>
> No worries.

It is actually a regression. It only really affects performance,
but the logic is broken (my fault). We were going to revert it, and
solve the initial regression a better way.

Thanks,
Nick

      reply	other threads:[~2024-04-10  4:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240313072625.76804-1-vaibhav@linux.ibm.com>
     [not found] ` <CZYME80BW9P7.3SC4GLHWCDQ9K@wheely>
2024-04-04  8:35   ` [PATCH] KVM: PPC: Book3S HV nestedv2: Cancel pending HDEC exception Linux regression tracking (Thorsten Leemhuis)
2024-04-05  3:20     ` Michael Ellerman
2024-04-05  5:54       ` Thorsten Leemhuis
2024-04-08  5:20         ` Michael Ellerman
2024-04-10  4:28           ` Nicholas Piggin [this message]

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=D0G5QG4M991A.1QAWDKSYM6A89@gmail.com \
    --to=npiggin@gmail.com \
    --cc=David.Laight@ACULAB.COM \
    --cc=amachhiw@linux.vnet.ibm.com \
    --cc=gautam@linux.ibm.com \
    --cc=jniethe5@gmail.com \
    --cc=kconsul@linux.vnet.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mikey@neuling.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@ozlabs.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=sbhat@linux.ibm.com \
    --cc=svaidy@linux.vnet.ibm.com \
    --cc=vaibhav@linux.ibm.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 read-only IMAP folder(s) and NNTP newsgroup(s).