qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: peter.maydell@linaro.org, berrange@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] tcg/arm: Reduce vector alignment requirement for NEON
Date: Mon, 13 Sep 2021 09:19:22 -0700	[thread overview]
Message-ID: <f6e7ab0f-aebe-c9c5-d479-fa30e69fcd1c@linaro.org> (raw)
In-Reply-To: <20210913110727.GF26415@redhat.com>

On 9/13/21 4:07 AM, Richard W.M. Jones wrote:
>> [    0.000000] Linux version 5.14.0-60.fc36.armv7hl (mockbuild@buildvm-a32-12.iad2.fedoraproject.org) (gcc (GCC) 11.2.1 20210728 (Red Hat 11.2.1-1), GNU ld version 2.37-9.fc36) #1 SMP Mon Aug 30 14:08:34 UTC 2021
>>
>> I thought about parameterizing this patch further, but I can't think of
>> another ISA that would be affected.  (i686 clumsily changed its abi 20
>> years ago to avoid faulting on vector spills; other isas so far have
>> allowed vectors to be unaligned.)
> 
> Is it possible this change could have caused a more serious
> regression?

I don't think so...

> Now when I try to boot the Fedora kernel using TCG on
> armv7hl I can't even get to the point where it detects virtio-scsi
> devices.
> 
> Full log is here (go down to the bottom and work backwards):
> 
>    https://kojipkgs.fedoraproject.org//work/tasks/7337/75597337/build.log

I downloaded the 5.14.0-60 kernel from above, and I can reproduce the original error, and 
I see that it's fixed afterward.

I'll have a look at this new build log in a moment...


r~


  reply	other threads:[~2021-09-13 16:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-12 17:49 [PATCH] tcg/arm: Reduce vector alignment requirement for NEON Richard Henderson
2021-09-13  8:07 ` Richard W.M. Jones
2021-09-13 11:07 ` Richard W.M. Jones
2021-09-13 16:19   ` Richard Henderson [this message]
2021-09-13 16:28     ` Richard W.M. Jones
2021-09-13 17:01       ` Peter Maydell

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=f6e7ab0f-aebe-c9c5-d479-fa30e69fcd1c@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.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).