From: Marcelo Tosatti <mtosatti@redhat.com>
To: Lucas Meneghel Rodrigues <lmr@redhat.com>
Cc: kvm@vger.kernel.org, avi@redhat.com
Subject: Re: [PATCH] vmexit: Update unittests.cfg with list of vmexit subtests
Date: Wed, 16 May 2012 18:26:23 -0300 [thread overview]
Message-ID: <20120516212623.GC25397@amt.cnet> (raw)
In-Reply-To: <1337032631-12346-1-git-send-email-lmr@redhat.com>
On Mon, May 14, 2012 at 06:57:11PM -0300, Lucas Meneghel Rodrigues wrote:
> vmexit takes a parameter to run appropriate subtests, but
> unittests.cfg was not updated to reflect that. As this
> config file is used by automated test harnesses such as
> autotest, this will make the appropriate tests not
> executed.
>
> Tested successfuly with qemu-kvm shipped in Fedora 17
> and RHEL 6.3. I've found problems with qemu-kvm compiled
> from master HEAD, but it's not related to this patch, as
> all other unittests are failing (currently under investigation).
>
> Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
Applied, thanks.
prev parent reply other threads:[~2012-05-16 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 21:57 [PATCH] vmexit: Update unittests.cfg with list of vmexit subtests Lucas Meneghel Rodrigues
2012-05-16 21:26 ` Marcelo Tosatti [this message]
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=20120516212623.GC25397@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lmr@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