From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, famz@redhat.com, mprivozn@redhat.com,
bsd@redhat.com, qemu-stable@nongnu.org,
Yang Hongyang <yanghy@cn.fujitsu.com>,
Jason Wang <jasowang@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] vl: Delay initialization of memory backends
Date: Mon, 5 Sep 2016 13:53:37 +0200 [thread overview]
Message-ID: <8603a7b4-d485-4e2f-b93e-a91f4bf21ac3@redhat.com> (raw)
In-Reply-To: <20160902181055.GK1151@thinpad.lan.raisama.net>
On 02/09/2016 20:10, Eduardo Habkost wrote:
> On Fri, Sep 02, 2016 at 04:56:49PM +0200, Paolo Bonzini wrote:
>> On 02/09/2016 16:04, Eduardo Habkost wrote:
> [...]
>>> Now, why exactly vhost-user-test needs accel=tcg and can't use
>>> accel=qtest?
>>
>> Because it uses iPXE to exercise the NIC.
>
> Is it used to actually exercise the NIC, or just to initialize
> it?
Well that's one way to exercise it. :)
> Original commit says "pc-bios/pxe-virtio.rom is used to
> instantiate a virtio pcicontroller". I don't see any test code
> that receives any data from iPXE: nothing is read from log_fd,
> the VHOST_USER_SET_VRING_KICK/VHOST_USER_SET_VRING_CALL FDs are
> simply ignored. The only memory writes/reads are on the first
> memory page.
>
> I suggest simply using libqos. If somebody really wants rx/tx
> tests using vhost-user, they can be written using libqos (just
> like virtio-net-test.c).
Ok, this makes sense.
Paolo
next prev parent reply other threads:[~2016-09-05 11:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 20:17 [Qemu-devel] [PATCH] vl: Delay initialization of memory backends Eduardo Habkost
2016-08-31 21:47 ` no-reply
2016-09-01 15:10 ` Eduardo Habkost
2016-09-01 15:41 ` Paolo Bonzini
2016-09-01 17:39 ` Eduardo Habkost
2016-09-01 19:34 ` Eduardo Habkost
2016-09-01 22:29 ` Bandan Das
2016-09-02 8:59 ` Paolo Bonzini
2016-09-02 14:04 ` Eduardo Habkost
2016-09-02 14:56 ` Paolo Bonzini
2016-09-02 18:10 ` Eduardo Habkost
2016-09-05 11:53 ` Paolo Bonzini [this message]
2016-09-01 16:52 ` Michal Privoznik
2016-09-01 17:26 ` Eduardo Habkost
2016-09-02 6:13 ` Markus Armbruster
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=8603a7b4-d485-4e2f-b93e-a91f4bf21ac3@redhat.com \
--to=pbonzini@redhat.com \
--cc=bsd@redhat.com \
--cc=ehabkost@redhat.com \
--cc=famz@redhat.com \
--cc=jasowang@redhat.com \
--cc=mprivozn@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=yanghy@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).