From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH unit-tests 3/3] Test that vcpu does not continue to run after issuing S3.
Date: Tue, 11 Jan 2011 16:17:43 +0200 [thread overview]
Message-ID: <20110111141743.GC14750@redhat.com> (raw)
In-Reply-To: <4D2C6455.7050609@redhat.com>
On Tue, Jan 11, 2011 at 04:08:21PM +0200, Avi Kivity wrote:
> On 01/11/2011 03:54 PM, Gleb Natapov wrote:
> >On Tue, Jan 11, 2011 at 03:53:08PM +0200, Avi Kivity wrote:
> >> On 01/11/2011 03:30 PM, Gleb Natapov wrote:
> >> >+
> >> >+asm (
> >> >+ ".global resume_start\n"
> >> >+ ".global resume_end\n"
> >> >+ ".code16\n"
> >> >+ "resume_start:\n"
> >> >+ "mov 0x0, %eax\n"
> >> >+ "mov $0xf4, %dx\n"
> >> >+ "out %eax, %dx\n"
> >> >+ "1: hlt\n"
> >> >+ "jmp 1b\n"
> >> >+ "resume_end:\n"
> >> >+#ifdef __i386__
> >> >+ ".code32\n"
> >> >+#else
> >> >+ ".code64\n"
> >> >+#endif
> >> >+ );
> >>
> >> Is this a kvm unit test or a qemu unit test?
> >>
> >Both? Is this a bad thing?
>
> We may want to move non-kvm tests to qemu.git. Though all of the
> non-api tests work equally for qemu and kvm.
>
We will have to maintain two separate unit test infrastructures then.
We can make x86/qemu or x86/device-model subdir in kvm-unit-test.
--
Gleb.
next prev parent reply other threads:[~2011-01-11 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 13:30 [PATCH unit-tests 1/3] Task stack pointer should point to the end of the page Gleb Natapov
2011-01-11 13:30 ` [PATCH unit-tests 2/3] Test that error code is pushed on exception's task stack Gleb Natapov
2011-01-11 13:30 ` [PATCH unit-tests 3/3] Test that vcpu does not continue to run after issuing S3 Gleb Natapov
2011-01-11 13:53 ` Avi Kivity
2011-01-11 13:54 ` Gleb Natapov
2011-01-11 14:08 ` Avi Kivity
2011-01-11 14:17 ` Gleb Natapov [this message]
2011-01-19 16:37 ` [PATCH unit-tests 1/3] Task stack pointer should point to the end of the page Marcelo Tosatti
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=20110111141743.GC14750@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.