Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Longpeng (Mike)" <longpeng2@huawei.com>
Cc: Halil Pasic <pasic@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org, virtio-dev@lists.oasis-open.org,
	luonengjun@huawei.com, cornelia.huck@de.ibm.com,
	stefanha@redhat.com, denglingli@chinamobile.com,
	Jani.Kokkonen@huawei.com, Ola.Liljedahl@arm.com,
	Varun.Sethi@freescale.com, xin.zeng@intel.com,
	brian.a.keating@intel.com, liang.j.ma@intel.com,
	john.griffin@intel.com, weidong.huang@huawei.com, agraf@suse.de,
	jasowang@redhat.com, vincent.jardin@6wind.com,
	arei.gonglei@huawei.com, wangxinxin.wang@huawei.com,
	jianjay.zhou@huawei.com
Subject: Re: [virtio-dev] Re: [Qemu-devel] [v23 1/2] virtio-crypto: Add virtio crypto device specification
Date: Wed, 20 Jun 2018 06:34:24 +0300	[thread overview]
Message-ID: <20180620063204-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <5A55AA45.9090004@huawei.com>

On Wed, Jan 10, 2018 at 01:53:09PM +0800, Longpeng (Mike) wrote:
> Hi Halil,
> 
> We are fixing the Intel BUG these days, so I will go through your comments after
> we're done. Thanks.

All right - are you guys done with meltdown/spectre? I'd like us
to start finally getting parts of this in the spec.
This is already used in the field - let's get into spec
whatever is already out there.

Argue about future enhancements later.


-- 
MST

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2018-06-20  3:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1514626559-162312-1-git-send-email-longpeng2@huawei.com>
2017-12-30  9:35 ` [virtio-dev] [v23 2/2] virtio-crypto: Add conformance clauses Longpeng(Mike)
     [not found] ` <1514626559-162312-2-git-send-email-longpeng2@huawei.com>
2018-01-09 17:05   ` [virtio-dev] Re: [Qemu-devel] [v23 1/2] virtio-crypto: Add virtio crypto device specification Halil Pasic
2018-01-09 17:41     ` Michael S. Tsirkin
2018-01-10  5:53     ` Longpeng (Mike)
2018-06-20  3:34       ` Michael S. Tsirkin [this message]
2018-03-16 16:27     ` Michael S. Tsirkin
2018-03-16 18:18       ` Halil Pasic
2018-03-19  0:13         ` Michael S. Tsirkin
2018-07-20 12:01     ` Longpeng (Mike)
2018-07-26 16:55       ` Halil Pasic
2018-07-27  0:59         ` Longpeng (Mike)
2018-07-27 11:51         ` Michael S. Tsirkin
2018-08-01 20:21           ` [virtio-dev] Re: [Qemu-devel] [virtio-dev] " Halil Pasic
2018-08-02  1:56             ` Longpeng (Mike)

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=20180620063204-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=Jani.Kokkonen@huawei.com \
    --cc=Ola.Liljedahl@arm.com \
    --cc=Varun.Sethi@freescale.com \
    --cc=agraf@suse.de \
    --cc=arei.gonglei@huawei.com \
    --cc=brian.a.keating@intel.com \
    --cc=cornelia.huck@de.ibm.com \
    --cc=denglingli@chinamobile.com \
    --cc=jasowang@redhat.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=john.griffin@intel.com \
    --cc=liang.j.ma@intel.com \
    --cc=longpeng2@huawei.com \
    --cc=luonengjun@huawei.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vincent.jardin@6wind.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=wangxinxin.wang@huawei.com \
    --cc=weidong.huang@huawei.com \
    --cc=xin.zeng@intel.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