From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>, qemu-devel@nongnu.org
Cc: "Igor Mammedov" <imammedo@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [RFC 00/10] Target-specific unit test support, add unit tests for target-i386/cpu.c code
Date: Fri, 26 Sep 2014 17:20:32 +0200 [thread overview]
Message-ID: <54258440.3060203@redhat.com> (raw)
In-Reply-To: <1411676309-20218-1-git-send-email-ehabkost@redhat.com>
Il 25/09/2014 22:18, Eduardo Habkost ha scritto:
> This is an attempt to write unit tests for the target-i386/cpu.c code. By now, I
> just implemented 3 simple test cases, to ensure X86CPU objects can be created,
> and to ensure the CPU features are set properly depending on the CPU model
> table.
+ qemu-log.o \
+ qom/object.o qom/qom-qobject.o qom/cpu.o qom/container.o \
+ hw/core/qdev.o hw/core/qdev-properties.o hw/core/irq.o hw/core/fw-path-provider.o hw/core/hotplug.o \
+ vmstate.o qemu-file.o $(util-obj-y) \
+ x86_64-softmmu/cpus.o x86_64-softmmu/target-i386/machine.o \
+ tests/vl-stub.o tests/x86-stub.o tests/coroutine-stub.o tests/monitor-stub.o tests/aio-stub.o tests/timer-stub.o tests/block-stub.o \
+ stubs/reset.o stubs/sysbus.o stubs/vmstate.o stubs/fdset-remove-fd.o stubs/mon-printf.o stubs/qtest.o stubs/vm-stop.o
Do you really need cpus.c? That's what brings in most dependencies,
and everything else should be included in libqemustub.a. Also,
util-obj-y should be replaced with libqemuutil.a
In any case, most of these files are not needed by the linux-user
version of cpu.c, so I would need to know what exactly forces you
to include each of the files.
Also, would it be possible to do these tests via qtest and
qom-get/qom-set?
That said, please feel free to send patches 1-3 now, via qemu-trivial.
Thanks,
Paolo
next prev parent reply other threads:[~2014-09-26 15:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 20:18 [Qemu-devel] [RFC 00/10] Target-specific unit test support, add unit tests for target-i386/cpu.c code Eduardo Habkost
2014-09-25 20:18 ` [Qemu-devel] [RFC 01/10] tests: Add missing include to test-bitops.c Eduardo Habkost
2014-09-25 20:18 ` [Qemu-devel] [RFC 02/10] bitops.h: Don't include qemu-common.h Eduardo Habkost
2014-09-25 20:18 ` [Qemu-devel] [RFC 03/10] bitmap.h: " Eduardo Habkost
2014-09-25 20:18 ` [Qemu-devel] [RFC 04/10] tests: Move fake yield_until_fd_readable() to coroutine-stub.c Eduardo Habkost
2014-09-25 20:18 ` [Qemu-devel] [RFC 05/10] tests: Support target-specific unit tests Eduardo Habkost
2014-09-25 20:18 ` [Qemu-devel] [RFC 06/10] tests: Make test-x86-cpuid target-specific Eduardo Habkost
2014-09-25 20:18 ` [Qemu-devel] [RFC 07/10] tests: Add unit test for X86CPU code Eduardo Habkost
2014-09-25 20:18 ` [Qemu-devel] [RFC 08/10] target-i386: Isolate enabled-by-default features to a separate array Eduardo Habkost
2014-09-25 20:18 ` [Qemu-devel] [RFC 09/10] tests: test-x86-cpu: Add TCG feature bit initialization test Eduardo Habkost
2014-09-25 20:18 ` [Qemu-devel] [RFC 10/10] tests: test-x86-cpu: Add KVM " Eduardo Habkost
2014-09-26 15:20 ` Paolo Bonzini [this message]
2014-09-26 16:34 ` [Qemu-devel] [RFC 00/10] Target-specific unit test support, add unit tests for target-i386/cpu.c code Eduardo Habkost
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=54258440.3060203@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--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).