qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Igor Mammedov" <imammedo@redhat.com>
Subject: [Qemu-devel] [PATCH for-2.4 v5 0/7] Target-specific unit test support, add unit tests for target-i386/cpu.c code
Date: Mon, 23 Mar 2015 16:37:05 -0300	[thread overview]
Message-ID: <1427139432-27530-1-git-send-email-ehabkost@redhat.com> (raw)

Changes v4 -> v5:
 * Rewrite fake kvm_arch_get_supported_cpuid() code
 * Add new test to ensure KVM defaults won't override explicit command-line
   options

Changes v3 -> v4:
 * Move target_words_bigendian() prototype back inside tests/x86-stub.c.

Changes v2 -> v3:
 * Extra KVM "host" CPU model test cases
 * Move target_words_bigendian() prototype to exec-all.h

Changes v1 -> v2:
 * Make dependency list of test binary much simpler, now that cpus.o
   was removed.

Eduardo Habkost (7):
  tests: Support target-specific unit tests
  tests: Make test-x86-cpuid target-specific
  tests: Add unit test for X86CPU code
  target-i386: Isolate enabled-by-default features to a separate array
  tests: test-x86-cpu: Add TCG feature bit initialization test
  tests: test-x86-cpu: Add KVM feature bit initialization test
  tests: test-x86-cpu: Ensure that -cpu override KVM-specific defaults

 target-i386/cpu.c    |  12 ++-
 tests/.gitignore     |   1 +
 tests/Makefile       |  49 +++++++++---
 tests/test-x86-cpu.c | 208 +++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/vl-stub.c      |  15 ++++
 tests/x86-stub.c     | 165 ++++++++++++++++++++++++++++++++++++++++
 6 files changed, 437 insertions(+), 13 deletions(-)
 create mode 100644 tests/test-x86-cpu.c
 create mode 100644 tests/vl-stub.c
 create mode 100644 tests/x86-stub.c

-- 
2.1.0

             reply	other threads:[~2015-03-23 19:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 19:37 Eduardo Habkost [this message]
2015-03-23 19:37 ` [Qemu-devel] [PATCH for-2.4 v5 1/7] tests: Support target-specific unit tests Eduardo Habkost
2015-03-23 19:37 ` [Qemu-devel] [PATCH for-2.4 v5 2/7] tests: Make test-x86-cpuid target-specific Eduardo Habkost
2015-03-23 19:37 ` [Qemu-devel] [PATCH for-2.4 v5 3/7] tests: Add unit test for X86CPU code Eduardo Habkost
2015-03-23 19:37 ` [Qemu-devel] [PATCH for-2.4 v5 4/7] target-i386: Isolate enabled-by-default features to a separate array Eduardo Habkost
2015-03-23 19:37 ` [Qemu-devel] [PATCH for-2.4 v5 5/7] tests: test-x86-cpu: Add TCG feature bit initialization test Eduardo Habkost
2015-03-23 19:37 ` [Qemu-devel] [PATCH for-2.4 v5 6/7] tests: test-x86-cpu: Add KVM " Eduardo Habkost
2015-03-23 19:37 ` [Qemu-devel] [PATCH for-2.4 v5 7/7] tests: test-x86-cpu: Ensure that -cpu override KVM-specific defaults Eduardo Habkost
2015-04-08 13:06 ` [Qemu-devel] [PATCH for-2.4 v5 0/7] Target-specific unit test support, add unit tests for target-i386/cpu.c code Andreas Färber
2015-04-08 13:42   ` Eduardo Habkost
2015-04-08 14:05     ` Andreas Färber
2015-04-08 14:57       ` 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=1427139432-27530-1-git-send-email-ehabkost@redhat.com \
    --to=ehabkost@redhat.com \
    --cc=afaerber@suse.de \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@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).