From: Cornelia Huck <cohuck@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org, kvm@vger.kernel.org,
Cornelia Huck <cohuck@redhat.com>
Subject: [PATCH for-8.2 0/2] arm/kvm: use kvm_{get,set}_one_reg
Date: Tue, 18 Jul 2023 13:14:02 +0200 [thread overview]
Message-ID: <20230718111404.23479-1-cohuck@redhat.com> (raw)
The kvm_{get,set}_one_reg functions have been around for a very long
time, and using them instead of open-coding the ioctl invocations
saves lines of code, and gives us a tracepoint as well. They cannot
be used by invocations of the ioctl not acting on a CPUState, but
that still leaves a lot of conversions in the target/arm code.
target/mips and target/ppc also have some potential for conversions,
but as I cannot test either (and they are both in 'Odd fixes' anyway),
I left them alone.
Survives some testing on a Mt. Snow.
Cornelia Huck (2):
arm/kvm: convert to kvm_set_one_reg
arm/kvm: convert to kvm_get_one_reg
target/arm/kvm.c | 28 +++--------
target/arm/kvm64.c | 123 ++++++++++++---------------------------------
2 files changed, 39 insertions(+), 112 deletions(-)
--
2.41.0
next reply other threads:[~2023-07-18 11:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 11:14 Cornelia Huck [this message]
2023-07-18 11:14 ` [PATCH for-8.2 1/2] arm/kvm: convert to kvm_set_one_reg Cornelia Huck
2023-07-24 2:26 ` Gavin Shan
2023-07-24 8:47 ` Cornelia Huck
2023-07-18 11:14 ` [PATCH for-8.2 2/2] arm/kvm: convert to kvm_get_one_reg Cornelia Huck
2023-07-24 2:35 ` Gavin Shan
2023-07-24 8:48 ` Cornelia Huck
2023-07-25 0:01 ` Gavin Shan
2023-07-27 9:55 ` Cornelia Huck
2023-10-10 10:09 ` Cornelia Huck
2023-07-31 7:15 ` Gavin Shan
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=20230718111404.23479-1-cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).