All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Kiper <daniel.kiper@oracle.com>
To: advisory-board@lists.xenproject.org,
	virtio-dev@lists.oasis-open.org, xen-devel@lists.xenproject.org
Cc: wei.liu2@citrix.com, ian.campbell@citrix.com, rusty@au1.ibm.com,
	andreslc@gridcentric.ca, mst@redhat.com, ian@bromium.com,
	anthony@codemonkey.ws, sasha.levin@oracle.com,
	stefano.stabellini@eu.citrix.com
Subject: Is: Wrap-up Was: VIRTIO - compatibility with different virtualization solutions
Date: Mon, 10 Mar 2014 08:54:23 +0100	[thread overview]
Message-ID: <20140310075423.GE31874__20563.6251288981$1394438204$gmane$org@olila.local.net-space.pl> (raw)
In-Reply-To: <20140217132331.GA3441@olila.local.net-space.pl>

Hi,

After some email exchange it looks that there is no consensus how VRITIO
should work on Xen. There is some hand waiving and some preliminary tests
but it is not sufficient to take final decision and put all needed stuff
into upcoming VIRTIO specification release. However, it is certain that
any solution which will be chosen in upcoming future MUST not break Xen
security model, has a good performance and easily integrate with currently
existing solutions. Additionally, it looks that that some terms (e.g.
physical address) in VIRTIO specification shall be changed to something
which is more platform independent (e.g. handle). Although such changes
should not lead to changes in currently existing VIRTIO implementations.

Taking into account above mentioned things I state that more research
and development work is needed. I volunteer to lead this task. Hence
I would like to propose that VIRTIO-46 task (Verify that VIRTIO devices
could be implemented in Xen environment) should be opened and work on
it should be deferred (from formal POV but that does not mean that work
should be on hold in real) until next VIRTIO release. Additionally,
I would like to rise VIRTIO on Xen issue during Xen Hackathon 2014 and
in other avenues to discuss this with other stake holders of VIRTIO.

Daniel

  parent reply	other threads:[~2014-03-10  7:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 13:23 VIRTIO - compatibility with different virtualization solutions Daniel Kiper
2014-02-19  0:26 ` Rusty Russell
     [not found] ` <87vbwcaqxe.fsf@rustcorp.com.au>
2014-02-19  4:42   ` Anthony Liguori
2014-02-20  1:31     ` Rusty Russell
     [not found]     ` <87ha7ubme0.fsf@rustcorp.com.au>
2014-02-20 12:28       ` Stefano Stabellini
2014-02-20 20:28       ` Daniel Kiper
2014-02-21  2:50       ` Anthony Liguori
2014-02-21 10:05         ` Wei Liu
2014-02-21 15:01           ` Konrad Rzeszutek Wilk
2014-02-25  0:33             ` Rusty Russell
     [not found]             ` <87y51058vf.fsf@rustcorp.com.au>
2014-02-25 21:09               ` Konrad Rzeszutek Wilk
2014-02-19 10:09   ` Ian Campbell
2014-02-20  7:48     ` Rusty Russell
     [not found]     ` <8761oab4y7.fsf@rustcorp.com.au>
2014-02-20 20:37       ` Daniel Kiper
     [not found]       ` <20140220203704.GG3441@olila.local.net-space.pl>
2014-02-21  0:54         ` [virtio-dev] " Rusty Russell
     [not found]         ` <8761o99tft.fsf@rustcorp.com.au>
2014-02-21  3:00           ` Anthony Liguori
2014-02-25  0:40             ` Rusty Russell
     [not found]             ` <87vbw458jr.fsf@rustcorp.com.au>
2014-02-25 21:12               ` Konrad Rzeszutek Wilk
2014-02-26  9:38               ` Ian Campbell
2014-02-21 10:21           ` Wei Liu
2014-02-21 15:11           ` Konrad Rzeszutek Wilk
2014-03-03  5:52             ` Rusty Russell
     [not found]             ` <87ppm325i6.fsf@rustcorp.com.au>
2014-03-04 23:16               ` Michael S. Tsirkin
2014-02-19 10:11   ` Ian Campbell
2014-03-10  7:54 ` Daniel Kiper [this message]
     [not found] ` <20140310075423.GE31874@olila.local.net-space.pl>
2014-03-10 11:19   ` Is: Wrap-up Was: " Fabio Fantoni
2014-03-11 14:29     ` Ian Campbell

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='20140310075423.GE31874__20563.6251288981$1394438204$gmane$org@olila.local.net-space.pl' \
    --to=daniel.kiper@oracle.com \
    --cc=advisory-board@lists.xenproject.org \
    --cc=andreslc@gridcentric.ca \
    --cc=anthony@codemonkey.ws \
    --cc=ian.campbell@citrix.com \
    --cc=ian@bromium.com \
    --cc=mst@redhat.com \
    --cc=rusty@au1.ibm.com \
    --cc=sasha.levin@oracle.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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 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.