From: Paolo Bonzini <pbonzini@redhat.com>
To: Claudio Fontana <cfontana@suse.de>,
Jason Andryuk <jandryuk@gmail.com>,
qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>, Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH 1/2] accel: move qtest CpusAccel functions to a common location
Date: Mon, 12 Oct 2020 22:30:24 +0200 [thread overview]
Message-ID: <1f99e620-8356-a67f-1741-4e1c607795e1@redhat.com> (raw)
In-Reply-To: <f29b58c7-62c5-ad10-91c8-47598759c876@suse.de>
On 12/10/20 22:23, Claudio Fontana wrote:
> On 10/12/20 10:07 PM, Jason Andryuk wrote:
>> Move and rename accel/qtest/qtest-cpu.* files to accel/dummy/ so they
>> can be re-used by Xen.
>>
>> Signed-off-by: Jason Andryuk <jandryuk@gmail.com>
>> ---
>> .../qtest-cpus.c => dummy/dummy-cpus.c} | 22 +++++--------------
>> .../qtest-cpus.h => dummy/dummy-cpus.h} | 10 ++++-----
>> accel/dummy/meson.build | 6 +++++
>> accel/meson.build | 1 +
>> accel/qtest/meson.build | 1 -
>> accel/qtest/qtest.c | 7 +++++-
>> 6 files changed, 23 insertions(+), 24 deletions(-)
>> rename accel/{qtest/qtest-cpus.c => dummy/dummy-cpus.c} (76%)
>> rename accel/{qtest/qtest-cpus.h => dummy/dummy-cpus.h} (59%)
>> create mode 100644 accel/dummy/meson.build
Maybe accel/dummy-cpus.c, no need to add a new directory.
>> diff --git a/accel/qtest/qtest.c b/accel/qtest/qtest.c
>> index 537e8b449c..ac54bc8f52 100644
>> --- a/accel/qtest/qtest.c
>> +++ b/accel/qtest/qtest.c
>> @@ -25,7 +25,12 @@
>> #include "qemu/main-loop.h"
>> #include "hw/core/cpu.h"
>>
>> -#include "qtest-cpus.h"
>> +#include "accel/dummy/dummy-cpus.h"
>
> this is a bit strange from my perspective, does not look right.
>
> Maybe this dummy cpu prototype should be somewhere in include/ ,
> like include/sysemu/cpus.h or even better include/sysemu/accel.h
Yes, it should be in include/sysemu/cpus.h.
Paolo
>> +
>> +const CpusAccel qtest_cpus = {
>> + .create_vcpu_thread = dummy_start_vcpu_thread,
>> + .get_virtual_clock = qtest_get_virtual_clock,
>> +};
>>
>> static int qtest_init_accel(MachineState *ms)
>> {
>>
>
next prev parent reply other threads:[~2020-10-12 20:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 20:07 [PATCH 0/2] Add Xen CpusAccel Jason Andryuk
2020-10-12 20:07 ` [PATCH 1/2] accel: move qtest CpusAccel functions to a common location Jason Andryuk
2020-10-12 20:23 ` Claudio Fontana
2020-10-12 20:30 ` Paolo Bonzini [this message]
2020-10-12 20:38 ` Jason Andryuk
2020-10-12 20:40 ` Jason Andryuk
2020-10-12 20:44 ` Paolo Bonzini
2020-10-12 20:07 ` [PATCH 2/2] accel: Add xen CpusAccel using dummy-cpu Jason Andryuk
2020-10-12 20:25 ` Claudio Fontana
2020-10-12 20:16 ` [PATCH 0/2] Add Xen CpusAccel Claudio Fontana
2020-10-13 8:42 ` Philippe Mathieu-Daudé
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=1f99e620-8356-a67f-1741-4e1c607795e1@redhat.com \
--to=pbonzini@redhat.com \
--cc=cfontana@suse.de \
--cc=jandryuk@gmail.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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).