From: Bill Wendling <morbo@google.com>
To: kvm@vger.kernel.org, pbonzini@redhat.com,
alexandru.elisei@arm.com, thuth@redhat.com
Cc: jmattson@google.com, Bill Wendling <morbo@google.com>
Subject: [kvm-unit-tests v2 PATCH 0/2] realmode test fixes for clang
Date: Wed, 16 Oct 2019 18:25:00 -0700 [thread overview]
Message-ID: <20191017012502.186146-1-morbo@google.com> (raw)
In-Reply-To: <20191012235859.238387-1-morbo@google.com>
The following patches fix some realmode test compatibility issues
between gcc and clang.
This update should address the comments by Jim Mattson.
Re explicitly copying the regs structure, I tried to use the inline asm
code you suggested, but wasn't able to get it to work for me. It never
seemed to copy the structure correctly. Doing the loop explicitly solved
the issue.
Bill Wendling (2):
x86: realmode: explicitly copy regs structure
x86: realmode: fix esp in call test
x86/realmode.c | 19 +++++++++++++++----
1 file changed, 15 insertions(+), 4 deletions(-)
--
2.23.0.700.g56cf767bdb-goog
next prev parent reply other threads:[~2019-10-17 1:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 23:58 [kvm-unit-tests PATCH 0/2] realmode test fixes for clang Bill Wendling
2019-10-12 23:58 ` [kvm-unit-tests PATCH 1/2] x86: realmode: explicitly copy structure to avoid memcpy Bill Wendling
2019-10-16 19:07 ` Jim Mattson
2019-10-21 15:38 ` Paolo Bonzini
2019-10-12 23:58 ` [kvm-unit-tests PATCH 2/2] x86: realmode: use inline asm to get stack pointer Bill Wendling
2019-10-16 19:53 ` Jim Mattson
2019-10-16 21:52 ` Jim Mattson
2019-10-21 15:41 ` Paolo Bonzini
2019-10-17 1:25 ` Bill Wendling [this message]
2019-10-17 1:25 ` [kvm-unit-tests v2 PATCH 1/2] x86: realmode: explicitly copy regs structure Bill Wendling
2019-10-17 1:25 ` [kvm-unit-tests v2 PATCH 2/2] x86: realmode: fix esp in call test Bill Wendling
2019-10-17 23:27 ` Jim Mattson
2019-10-21 15:43 ` Paolo Bonzini
2019-10-21 16:43 ` Jim Mattson
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=20191017012502.186146-1-morbo@google.com \
--to=morbo@google.com \
--cc=alexandru.elisei@arm.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=thuth@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.