From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: gleb@kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kvm@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] virt/kvm/assigned-dev.c: Set 'dev->irq_source_id' to '-1' after free it
Date: Wed, 20 Aug 2014 08:01:31 +0800 [thread overview]
Message-ID: <53F3E55B.8010009@gmail.com> (raw)
In-Reply-To: <53F3E490.1060400@gmail.com>
By the way, at present, I use Qemu as user mode program, is there common
test with both Qemu and KVM/Xen? And is a PC enough for the common test?
Thanks.
On 08/20/2014 07:58 AM, Chen Gang wrote:
> On 08/19/2014 11:49 PM, Paolo Bonzini wrote:
>> Il 19/08/2014 17:44, Chen Gang ha scritto:
>>>> Hello maintainers:
>>>>
>>>> Please help check this patch, when you have time.
>> Hi, it's already on its way to 3.17-rc2, but I first have to run a bunch
>> of tests.
>
> OK, thanks. Also can let me try the test, although I am not quite
> familiar with KVM. Since I plan to focus on KVM/Xen next, I shall
> construct related environments for its' common test, at least.
>
> I am just constructing the gcc common test environments under a new PC,
> is a PC also enough for KVM/Xen common test?
>
> Welcome any ideas, suggestions or completions about it (especially the
> information about KVM/Xen common test).
>
>
> Thanks.
>
--
Chen Gang
Open share and attitude like air water and life which God blessed
next parent reply other threads:[~2014-08-20 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <53E4EED7.6050302@gmail.com>
[not found] ` <53F370CD.80201@gmail.com>
[not found] ` <53F37221.5020508@redhat.com>
[not found] ` <53F3E490.1060400@gmail.com>
2014-08-20 0:01 ` Chen Gang [this message]
2014-08-20 11:21 ` [Qemu-devel] [PATCH] virt/kvm/assigned-dev.c: Set 'dev->irq_source_id' to '-1' after free it Chen Gang
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=53F3E55B.8010009@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).