linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hare@suse.de (Hannes Reinecke)
Subject: [RFC PATCH 0/2] virtio nvme
Date: Mon, 28 Sep 2015 07:58:48 +0200	[thread overview]
Message-ID: <5608D718.7050708@suse.de> (raw)
In-Reply-To: <1443330116.15432.57.camel@haakon3.risingtidesystems.com>

On 09/27/2015 07:01 AM, Nicholas A. Bellinger wrote:
> On Wed, 2015-09-23@15:58 -0700, Ming Lin wrote:
>> On Fri, 2015-09-18@14:09 -0700, Nicholas A. Bellinger wrote:
>>> On Fri, 2015-09-18@11:12 -0700, Ming Lin wrote:
>>>> On Thu, 2015-09-17@17:55 -0700, Nicholas A. Bellinger wrote:
> 
> <SNIP>
> 

<Even more SNIP>

> 
> Btw, after chatting with Dr. Hannes this week at SDC here are his
> original rts-megasas -v6 patches from Feb 2013.
> 
> Note they are standalone patches that require a sufficiently old enough
> LIO + QEMU to actually build + function.
> 
> https://github.com/Datera/rts-megasas/blob/master/rts_megasas-qemu-v6.patch
> https://github.com/Datera/rts-megasas/blob/master/rts_megasas-fabric-v6.patch
> 
> For groking purposes, they demonstrate the principle design for a host
> kernel level driver, along with the megasas firmware interface (MFI)
> specific emulation magic that makes up the bulk of the code.
> 
And indeed, Nic persuaded me to have them updated to qemu latest.
Which I'll be doing shortly. Stay tuned.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		               zSeries & Storage
hare at suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: F. Imend?rffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG N?rnberg)

      parent reply	other threads:[~2015-09-28  5:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10  5:48 [RFC PATCH 0/2] virtio nvme Ming Lin
2015-09-10  5:48 ` [RFC PATCH 1/2] virtio_nvme(kernel): virtual NVMe driver using virtio Ming Lin
2015-09-10  5:48 ` [RFC PATCH 2/2] virtio-nvme(qemu): NVMe device " Ming Lin
2015-09-10 14:02 ` [RFC PATCH 0/2] virtio nvme Keith Busch
2015-09-10 17:02   ` Ming Lin
2015-09-11  4:55     ` Ming Lin
2015-09-11 17:46     ` J Freyensee
2015-09-10 14:38 ` Stefan Hajnoczi
2015-09-10 17:28   ` Ming Lin
2015-09-11  7:48     ` Stefan Hajnoczi
2015-09-11 17:21       ` Ming Lin
2015-09-11 17:53         ` Stefan Hajnoczi
2015-09-11 18:54           ` Ming Lin
2015-09-17  6:10     ` Nicholas A. Bellinger
2015-09-17 18:18       ` Ming Lin
2015-09-17 21:43         ` Nicholas A. Bellinger
2015-09-17 23:31       ` Ming Lin
2015-09-18  0:55         ` Nicholas A. Bellinger
2015-09-18 18:12           ` Ming Lin
2015-09-18 21:09             ` Nicholas A. Bellinger
2015-09-18 23:05               ` Ming Lin
2015-09-23 22:58               ` Ming Lin
2015-09-27  5:01                 ` Nicholas A. Bellinger
2015-09-27  6:49                   ` Ming Lin
2015-09-28  5:58                   ` Hannes Reinecke [this message]

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=5608D718.7050708@suse.de \
    --to=hare@suse.de \
    /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).