From: Richard Henderson <richard.henderson@linaro.org>
To: "Richard W.M. Jones" <rjones@redhat.com>,
Eduardo Lima <elima@redhat.com>
Cc: peter.maydell@linaro.org, sw@weilnetz.de,
Daniel Berrange <berrange@redhat.com>,
qemu-devel@nongnu.org, f4bug@amsat.org
Subject: Re: QEMU 6.2.0 and rhbz#1999878
Date: Fri, 3 Dec 2021 14:00:50 -0800 [thread overview]
Message-ID: <ca5c4fb4-3e9e-03c7-b682-cd29a01e0f13@linaro.org> (raw)
In-Reply-To: <20211203210325.GG1127@redhat.com>
On 12/3/21 1:03 PM, Richard W.M. Jones wrote:
> On Fri, Dec 03, 2021 at 05:35:41PM -0300, Eduardo Lima wrote:
>>
>>
>> On Fri, Dec 3, 2021 at 4:37 PM Richard W.M. Jones <rjones@redhat.com> wrote:
>>
>> On Fri, Dec 03, 2021 at 04:20:23PM -0300, Eduardo Lima wrote:
>> > Hi Rich,
>> >
>> > Can you confirm if the patch you added for qemu in Fedora has still not
>> been
>> > merged upstream? I could not find it on the git source tree.
>> >
>> > +Patch2: 0001-tcg-arm-Reduce-vector-alignment-requirement-for-NEON.patch
>> > +From 1331e4eec016a295949009b4360c592401b089f7 Mon Sep 17 00:00:00 2001
>> > +From: Richard Henderson <richard.henderson@linaro.org>
>> > +Date: Sun, 12 Sep 2021 10:49:25 -0700
>> > +Subject: [PATCH] tcg/arm: Reduce vector alignment requirement for NEON
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1999878
>> https://lists.nongnu.org/archive/html/qemu-devel/2021-09/msg01028.html
>>
>> The patch I posted wasn't correct (or meant to be), it was just a
>> workaround. However I think you're right - I don't believe the
>> original problem was ever fixed.
>>
>> Yes, I saw that your original patch had been replaced by this new
>> one I mentioned, so I thought it was the correct solution, but I
>> could not find this new one on the repository as well.
>
> Oh I see, it was indeed replaced by Richard Henderson's patch:
>
> https://src.fedoraproject.org/rpms/qemu/blob/rawhide/f/0001-tcg-arm-Reduce-vector-alignment-requirement-for-NEON.patch
>
>> At the moment I kept it as part of 6.2.0 build, which I am just about to push
>> to rawhide. It builds locally, and I am only waiting for the scratch-build to
>> finish.
>
> Yes looks like we need to keep it, and get it upstream too.
Whoops. That dropped through the cracks.
I'll queue that now-ish.
r~
next prev parent reply other threads:[~2021-12-03 22:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJzYwARYDA+E4wrszx-F1D_9+VAYB2dU=M-LtvzPJey02gu2qg@mail.gmail.com>
2021-12-03 19:37 ` QEMU 6.2.0 and rhbz#1999878 Richard W.M. Jones
2021-12-03 20:35 ` Eduardo Lima
2021-12-03 21:03 ` Richard W.M. Jones
2021-12-03 22:00 ` Richard Henderson [this message]
2021-12-04 0:09 ` Richard Henderson
2021-12-09 16:22 ` Eduardo Lima
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=ca5c4fb4-3e9e-03c7-b682-cd29a01e0f13@linaro.org \
--to=richard.henderson@linaro.org \
--cc=berrange@redhat.com \
--cc=elima@redhat.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=sw@weilnetz.de \
/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).