From: Jason Andryuk <jandryuk@gmail.com>
To: qemu-devel@nongnu.org
Cc: Claudio Fontana <cfontana@suse.de>,
Jason Andryuk <jandryuk@gmail.com>,
Thomas Huth <thuth@redhat.com>,
Laurent Vivier <lvivier@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Anthony Perard <anthony.perard@citrix.com>,
Paul Durrant <paul@xen.org>,
xen-devel@lists.xenproject.org
Subject: [PATCH v2 0/3] Add Xen CpusAccel
Date: Tue, 13 Oct 2020 10:05:08 -0400 [thread overview]
Message-ID: <20201013140511.5681-1-jandryuk@gmail.com> (raw)
Xen was left behind when CpusAccel became mandatory and fails the assert
in qemu_init_vcpu(). It relied on the same dummy cpu threads as qtest.
Move the qtest cpu functions to a common location and reuse them for
Xen.
v2:
New patch "accel: Remove _WIN32 ifdef from qtest-cpus.c"
Use accel/dummy-cpus.c for filename
Put prototype in include/sysemu/cpus.h
Jason Andryuk (3):
accel: Remove _WIN32 ifdef from qtest-cpus.c
accel: move qtest CpusAccel functions to a common location
accel: Add xen CpusAccel using dummy-cpus
accel/{qtest/qtest-cpus.c => dummy-cpus.c} | 27 ++++------------------
accel/meson.build | 8 +++++++
accel/qtest/meson.build | 1 -
accel/qtest/qtest-cpus.h | 17 --------------
accel/qtest/qtest.c | 5 +++-
accel/xen/xen-all.c | 8 +++++++
include/sysemu/cpus.h | 3 +++
7 files changed, 27 insertions(+), 42 deletions(-)
rename accel/{qtest/qtest-cpus.c => dummy-cpus.c} (71%)
delete mode 100644 accel/qtest/qtest-cpus.h
--
2.25.1
next reply other threads:[~2020-10-13 14:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 14:05 Jason Andryuk [this message]
2020-10-13 14:05 ` [PATCH v2 3/3] accel: Add xen CpusAccel using dummy-cpus Jason Andryuk
2020-10-13 14:12 ` Claudio Fontana
2020-10-16 15:05 ` Anthony PERARD
2020-10-13 17:16 ` [PATCH v2 0/3] Add Xen CpusAccel Paolo Bonzini
2020-10-22 15:17 ` Jason Andryuk
2020-10-22 15:29 ` Paolo Bonzini
2020-10-23 7:09 ` Thomas Huth
2020-10-23 9:34 ` 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=20201013140511.5681-1-jandryuk@gmail.com \
--to=jandryuk@gmail.com \
--cc=anthony.perard@citrix.com \
--cc=cfontana@suse.de \
--cc=lvivier@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=thuth@redhat.com \
--cc=xen-devel@lists.xenproject.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).