From: Paolo Bonzini <pbonzini@redhat.com>
To: David Matlack <dmatlack@google.com>
Cc: Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Tom Rix <trix@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Peter Xu <peterx@redhat.com>, Jim Mattson <jmattson@google.com>,
Oliver Upton <oupton@google.com>,
"open list:CLANG/LLVM BUILD SUPPORT" <llvm@lists.linux.dev>,
kvm list <kvm@vger.kernel.org>
Subject: Re: [PATCH 0/2] KVM: selftests: Fix Clang build issues in KVM_ASM_SAFE()
Date: Fri, 12 Aug 2022 09:49:07 +0200 [thread overview]
Message-ID: <a9035e7c-4587-6df7-c16c-e656d1734145@redhat.com> (raw)
In-Reply-To: <CALzav=frNna1fZYTxwz+Lo=1=zsOLAKoAd3pntXfUiDNdJ_PoA@mail.gmail.com>
On 8/11/22 00:53, David Matlack wrote:
> On Fri, Jul 22, 2022 at 4:48 PM David Matlack <dmatlack@google.com> wrote:
>>
>> The LLVM integrated assembler has some differences from the GNU
>> assembler, and recent commit 3b23054cd3f5 ("KVM: selftests: Add x86-64
>> support for exception fixup") seems to be tripping over a few of those
>> differences.
>
> Paolo, what do you think about these changes? I'm still hitting the
> mentioned Clang build issues on kvm/master, commit 93472b797153
> ("Merge tag 'kvmarm-5.20' of
> git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into
> HEAD").
I had missed them, so thanks for pinging.
Paolo
next prev parent reply other threads:[~2022-08-12 7:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 23:48 [PATCH 0/2] KVM: selftests: Fix Clang build issues in KVM_ASM_SAFE() David Matlack
2022-07-22 23:48 ` [PATCH 1/2] KVM: selftests: Fix KVM_EXCEPTION_MAGIC build with Clang David Matlack
2022-07-23 0:01 ` Sean Christopherson
2022-07-23 0:07 ` David Matlack
2022-07-22 23:48 ` [PATCH 2/2] KVM: selftests: Fix ambiguous mov in KVM_ASM_SAFE() David Matlack
2022-07-23 0:14 ` Sean Christopherson
2022-08-10 22:53 ` [PATCH 0/2] KVM: selftests: Fix Clang build issues " David Matlack
2022-08-12 7:49 ` Paolo Bonzini [this message]
2022-08-12 7:57 ` Paolo Bonzini
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=a9035e7c-4587-6df7-c16c-e656d1734145@redhat.com \
--to=pbonzini@redhat.com \
--cc=dmatlack@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=oupton@google.com \
--cc=peterx@redhat.com \
--cc=seanjc@google.com \
--cc=trix@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.