From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alvaro Karsz <alvaro.karsz@solid-run.com>
Cc: virtualization@lists.linux-foundation.org,
linux-block@vger.kernel.org,
Stefan Hajnoczi <stefanha@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH v5] virtio_blk: add VIRTIO_BLK_F_LIFETIME feature support
Date: Thu, 29 Dec 2022 08:31:26 -0500 [thread overview]
Message-ID: <20221229082943-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJs=3_ApAnMTC0O81vO=hvRLssLYRnJsVUE5gd_aomCB+5eWLQ@mail.gmail.com>
On Thu, Dec 29, 2022 at 02:08:34PM +0200, Alvaro Karsz wrote:
> > So due to my mistake this got pushed out to next linux release.
> > Sorry :(
>
> No problem at all :)
>
> > I'd like to use this opportunity to write a new better
> > interface that actually works with modern backends,
> > and add it to the virtio spec.
> >
> > Do you think you can take up this task?
>
> Sure, I can do it.
> So, the idea is to:
>
> * Drop this patch
> * Implement a new, more general virtio block feature for virtio spec
> * Add linux support for the new feature
>
> right?
That's certainly an option.
Let's start with point 2, and get ack from people who objected to this
feature.
--
MST
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alvaro Karsz <alvaro.karsz@solid-run.com>
Cc: Jens Axboe <axboe@kernel.dk>,
virtualization@lists.linux-foundation.org,
linux-block@vger.kernel.org,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v5] virtio_blk: add VIRTIO_BLK_F_LIFETIME feature support
Date: Thu, 29 Dec 2022 08:31:26 -0500 [thread overview]
Message-ID: <20221229082943-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAJs=3_ApAnMTC0O81vO=hvRLssLYRnJsVUE5gd_aomCB+5eWLQ@mail.gmail.com>
On Thu, Dec 29, 2022 at 02:08:34PM +0200, Alvaro Karsz wrote:
> > So due to my mistake this got pushed out to next linux release.
> > Sorry :(
>
> No problem at all :)
>
> > I'd like to use this opportunity to write a new better
> > interface that actually works with modern backends,
> > and add it to the virtio spec.
> >
> > Do you think you can take up this task?
>
> Sure, I can do it.
> So, the idea is to:
>
> * Drop this patch
> * Implement a new, more general virtio block feature for virtio spec
> * Add linux support for the new feature
>
> right?
That's certainly an option.
Let's start with point 2, and get ack from people who objected to this
feature.
--
MST
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2022-12-29 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 12:21 [PATCH v5] virtio_blk: add VIRTIO_BLK_F_LIFETIME feature support Alvaro Karsz
2022-12-19 12:21 ` Alvaro Karsz
2022-12-29 8:10 ` Michael S. Tsirkin
2022-12-29 8:10 ` Michael S. Tsirkin
2022-12-29 12:08 ` Alvaro Karsz
2022-12-29 12:08 ` Alvaro Karsz
2022-12-29 13:31 ` Michael S. Tsirkin [this message]
2022-12-29 13:31 ` Michael S. Tsirkin
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=20221229082943-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alvaro.karsz@solid-run.com \
--cc=axboe@kernel.dk \
--cc=jasowang@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.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.