From: Victor Kaplansky <victork@redhat.com>
To: dev@dpdk.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Subject: [dpdk-dev] dpdk: vhost/virtio staging/testing tree
Date: Fri, 12 Feb 2016 13:54:21 +0200 [thread overview]
Message-ID: <20160212135131-mutt-send-email-victork@redhat.com> (raw)
Hi!
Since I was maintaining an internal tree with patches related to
vhost/virtio, I decided to make this staging tree public. It is
useful to me and I hope it will be useful to others.
Collecting patches like this allows tracking dependencies between
patches, their improvement etc. I also rebase the tree so
contributors don't have to.
Before publishing, I test the tree so it can serve as a known
good state for people interested in preliminary testing of
patches that aren't yet upstream, improving testing/validation as
multiple people can test the same code.
Others can send patches referring to that tree to avoid conflicts
when several people are working on the same file.
I can also ping them collectively, keeping and rebasing the
patches that have been posted on list already, so it should be
enough to repost a short summary here, rather than flood
everyone's mailboxes by pinging each patch or reposting a full
patch-set.
I would like to stress that this is a staging/testing tree and
not fork of any kind: in particular, don't use this in
production, wait for patches to land upstream first!
If virtio maintainers would like to take over maintaining this
tree, please let me know.
The tree is here:
git://github.com/vkaplans/dpdk.git virtio
(Could be at dpdk.org just as well, but I don't have an account
there).
Beware: do not publish a tree on top of this one as I might be
re-basing it.
If you want me to add a patch there, just mail it to the list and
(preferably) Cc me. Also, please let me know if there are more
vhost/virtio related patches that I missed worth includng into my
tree.
---
Here is the list of patches in my tree: they have been tested by
me and are known to work together:
18e570dc vhost: remove duplicate header include
bc5a6193 vhost: enable log_shmfd protocol feature
905161a5 vhost: handle VHOST_USER_SEND_RARP request
99373fac vhost: claim that we support GUEST_ANNOUNCE feature
7cabbc72 vhost: log vring desc buffer changes
978cf176 vhost: log used vring changes
21d371b3 vhost: introduce vhost_log_write
c71eb45d vhost: handle VHOST_USER_SET_LOG_BASE request
4024209f vhost: Add VHOST PMD
6e2f1457 ethdev: Add a new event type to notify a queue state changed event
Thanks,
--
Victor
next reply other threads:[~2016-02-12 11:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 11:54 Victor Kaplansky [this message]
2016-02-16 4:02 ` Yuanhan Liu
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=20160212135131-mutt-send-email-victork@redhat.com \
--to=victork@redhat.com \
--cc=dev@dpdk.org \
--cc=mst@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;
as well as URLs for NNTP newsgroup(s).