public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Cole Robinson <crobinso@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH kvm-unit-tests 2/5] x86/README: Drop it
Date: Wed, 20 Mar 2013 15:54:05 -0300	[thread overview]
Message-ID: <20130320185405.GB3888@amt.cnet> (raw)
In-Reply-To: <a8d7a63268a524a54bfe8eb5fffeee50ae4833bd.1363391818.git.crobinso@redhat.com>

On Fri, Mar 15, 2013 at 08:09:06PM -0400, Cole Robinson wrote:
> Was out of date, and not particularly useful to begin with.
> ---
>  x86/README | 16 ----------------
>  1 file changed, 16 deletions(-)
>  delete mode 100644 x86/README
> 
> diff --git a/x86/README b/x86/README
> deleted file mode 100644
> index d644abd..0000000
> --- a/x86/README
> +++ /dev/null
> @@ -1,16 +0,0 @@
> -Tests in this directory and what they do:
> -
> -access: lots of page table related access (pte/pde) (read/write)
> -apic: enable x2apic, self ipi, ioapic intr, ioapic simultaneous
> -emulator: move to/from regs, cmps, push, pop, to/from cr8, smsw and lmsw
> -hypercall: intel and amd hypercall insn
> -msr: write to msr (only KERNEL_GS_BASE for now)
> -port80: lots of out to port 80
> -realmode: goes back to realmode, shld, push/pop, mov immediate, cmp immediate, add immediate,
> -         io, eflags instructions (clc, cli, etc.), jcc short, jcc near, call, long jmp, xchg
> -sieve: heavy memory access with no paging and with paging static and with paging vmalloc'ed
> -smptest: run smp_id() on every cpu and compares return value to number
> -tsc: write to tsc(0) and write to tsc(100000000000) and read it back
> -vmexit: long loops for each: cpuid, vmcall, mov_from_cr8, mov_to_cr8, inl_pmtimer, ipi, ipi+halt
> -kvmclock_test: test of wallclock, monotonic cycle and performance of kvmclock
> -pcid: basic functionality test of PCID/INVPCID feature
> \ No newline at end of file
> -- 
> 1.8.1.4

The summary can be useful (would rather update it than remove it).


  reply	other threads:[~2013-03-20 19:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-16  0:09 [PATCH kvm-unit-tests 1/5] .gitignore: Add *.flat and config.mak Cole Robinson
2013-03-16  0:09 ` [PATCH kvm-unit-tests 2/5] x86/README: Drop it Cole Robinson
2013-03-20 18:54   ` Marcelo Tosatti [this message]
2013-03-25 18:32     ` Cole Robinson
2013-03-16  0:09 ` [PATCH kvm-unit-tests 3/5] x86/run-kvm-unit-tests: " Cole Robinson
2013-03-16  0:09 ` [PATCH kvm-unit-tests 4/5] Rewrite x86-run in python Cole Robinson
2013-03-16  0:09 ` [PATCH kvm-unit-tests 5/5] x86-run: Pull extra arguments from unittests.cfg Cole Robinson
2013-03-17 15:25   ` Gleb Natapov
2013-03-17 23:58     ` Cole Robinson
2013-03-20 19:06       ` Marcelo Tosatti
2013-03-25 18:30         ` Cole Robinson
2013-04-14 13:40           ` Gleb Natapov
2013-04-14 18:20             ` Cole Robinson

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=20130320185405.GB3888@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=crobinso@redhat.com \
    --cc=kvm@vger.kernel.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