qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Taylor Simpson <tsimpson@quicinc.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Brian Cain" <bcain@quicinc.com>,
	"Matheus Bernardino (QUIC)" <quic_mathbern@quicinc.com>,
	"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [PULL 00/11] Hexagon bug fixes and performance improvement
Date: Tue, 15 Nov 2022 13:42:05 -0500	[thread overview]
Message-ID: <CAJSP0QU8MSoZnL2Zjo7xUHfcTG52w+ciipG2W5x1jt_87avM_A@mail.gmail.com> (raw)
In-Reply-To: <SN4PR0201MB8808C57A38E108ECA717F17FDE049@SN4PR0201MB8808.namprd02.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]

On Tue, Nov 15, 2022, 12:44 Taylor Simpson <tsimpson@quicinc.com> wrote:

>
>
> > -----Original Message-----
> > From: Stefan Hajnoczi <stefanha@gmail.com>
> > Sent: Tuesday, November 15, 2022 10:52 AM
> > To: Taylor Simpson <tsimpson@quicinc.com>
> > Cc: qemu-devel@nongnu.org; richard.henderson@linaro.org;
> > philmd@linaro.org; peter.maydell@linaro.org; Brian Cain
> > <bcain@quicinc.com>; Matheus Bernardino (QUIC)
> > <quic_mathbern@quicinc.com>; stefanha@redhat.com
> > Subject: Re: [PULL 00/11] Hexagon bug fixes and performance improvement
> >
> > On Tue, 15 Nov 2022 at 11:16, Taylor Simpson <tsimpson@quicinc.com>
> > wrote:
> > >
> > > OK.  I wasn't sure if performance improvements would be considered new
> > features or not.
> >
> > No problem! If there is a performance regression in the upcoming release,
> > then fixes will be accepted. For example, if QEMU 7.1 was fast but the
> > upcoming QEMU 7.2 release is going to be slow then a performance fix will
> > be accepted to avoid a regression in 7.2.
> >
> > On the other hand, if it's a fix for something that was already slow in
> the last
> > release (7.1), then it's less likely to be accepted during freeze.
>
> The performance improvements fall into this bucket.
>
> >
> > These are general guidelines and maintainers have a say in what gets
> > merged. In this case I looked at the pull request and I wasn't sure if
> you had
> > decided based on these guidelines or not. It helps when it's clear from
> the
> > commit message (or from the commit description in more involved cases)
> > that the commit fixes a bug or has some other justification.
>
> I'm the maintainer for the directories touched by these patches
> (target/hexagon and tests/tcg/hexagon), but I'll defer you as a more senior
> maintainer to decide not to merge if it is too risky at this stage.
>

Thanks!

Stefan


> Taylor
>
>
>

[-- Attachment #2: Type: text/html, Size: 3473 bytes --]

      reply	other threads:[~2022-11-15 18:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  0:52 [PULL 00/11] Hexagon bug fixes and performance improvement Taylor Simpson
2022-11-11  0:52 ` [PULL 01/11] Hexagon (target/hexagon) Add pkt and insn to DisasContext Taylor Simpson
2022-11-11  0:52 ` [PULL 02/11] Hexagon (target/hexagon) Fix predicated assignment to .tmp and .cur Taylor Simpson
2022-11-11  0:52 ` [PULL 03/11] Hexagon (target/hexagon) Add overrides for S2_asr_r_r_sat/S2_asl_r_r_sat Taylor Simpson
2022-11-11  0:52 ` [PULL 04/11] Hexagon (target/hexagon) Only use branch_taken when packet has multi cof Taylor Simpson
2022-11-11  0:52 ` [PULL 05/11] Hexagon (target/hexagon) Remove PC from the runtime state Taylor Simpson
2022-11-11  0:52 ` [PULL 06/11] Hexagon (target/hexagon) Remove next_PC from " Taylor Simpson
2022-11-11  0:52 ` [PULL 07/11] Hexagon (target/hexagon) Add overrides for direct call instructions Taylor Simpson
2022-11-11  0:52 ` [PULL 08/11] Hexagon (target/hexagon) Add overrides for compound compare and jump Taylor Simpson
2022-11-11  0:52 ` [PULL 09/11] Hexagon (target/hexagon) Add overrides for various forms of jump Taylor Simpson
2022-11-11  0:52 ` [PULL 10/11] Hexagon (target/hexagon) Use direct block chaining for direct jump/branch Taylor Simpson
2022-11-11  0:52 ` [PULL 11/11] Hexagon (target/hexagon) Use direct block chaining for tight loops Taylor Simpson
2022-11-11  1:06 ` [PULL 00/11] Hexagon bug fixes and performance improvement Stefan Hajnoczi
2022-11-15 16:16   ` Taylor Simpson
2022-11-15 16:52     ` Stefan Hajnoczi
2022-11-15 17:44       ` Taylor Simpson
2022-11-15 18:42         ` Stefan Hajnoczi [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=CAJSP0QU8MSoZnL2Zjo7xUHfcTG52w+ciipG2W5x1jt_87avM_A@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=bcain@quicinc.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quic_mathbern@quicinc.com \
    --cc=richard.henderson@linaro.org \
    --cc=stefanha@redhat.com \
    --cc=tsimpson@quicinc.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).