All of lore.kernel.org
 help / color / mirror / Atom feed
From: Halil Pasic <pasic@linux.ibm.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Usama Arif <usama.arif@bytedance.com>,
	virtio-dev@lists.oasis-open.org, stefanha@redhat.com,
	ndragazis@arrikto.com, fam.zheng@bytedance.com,
	liangma@liangbit.com, Halil Pasic <pasic@linux.ibm.com>
Subject: Re: [virtio-dev] Re: [PATCH 1/4] content: Introduce driver/device auxiliary notifications
Date: Thu, 11 Aug 2022 16:41:49 +0200	[thread overview]
Message-ID: <20220811164149.2e6ed3a7.pasic@linux.ibm.com> (raw)
In-Reply-To: <87ilmzcffd.fsf@redhat.com>

On Thu, 11 Aug 2022 11:12:06 +0200
Cornelia Huck <cohuck@redhat.com> wrote:

> >  
> >> I think making the people not motivated to do the design and write the
> >> spec for all the platforms add to that list is a reasonable middle
> >> ground. It would also make the differences very clear, and the same goes
> >> for the intention (i.e. not omitted by mistake).  
> 
> Hm. On the one hand, I like that it would add a laundry list for
> transports regarding features that might be implemented. 

I believe, all three of us are in agreement on this one. I could hack up
a spec-patch for ccw at some point in time which rectifies things for
the features that are already in the spec.

> In the other
> hand, I think the main problem is not enough people with enough
> understanding and bandwidth to add new features everywhere... but I
> suppose that needs to be fixed in a different place anyway.

I kind of agree, especially with the part that this is not the right
place to fix that problem, if it is a problem. Actually I see this
rather as a strength of virtio: a large amount of freedom in deciding
how much and where to invest. I would rather not specify stuff without
having some sort of a reference implementation, so the ability to
delay specifying how some optional features are to work with virtio-ccw
is very welcome form my perspective.

Regards,
Halil


  parent reply	other threads:[~2022-08-11 14:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220330152105.3770439-1-usama.arif@bytedance.com>
     [not found] ` <20220330152105.3770439-5-usama.arif@bytedance.com>
2022-08-09 20:06   ` [virtio-dev] Re: [PATCH 4/4] vhost-user: add vhost-user device type Michael S. Tsirkin
2022-08-11 10:05     ` Usama Arif
2022-08-11 11:20       ` Michael S. Tsirkin
2022-08-12  9:51         ` [External] " Usama Arif
     [not found] ` <20220330152105.3770439-2-usama.arif@bytedance.com>
2022-08-09 20:07   ` [PATCH 1/4] content: Introduce driver/device auxiliary notifications Michael S. Tsirkin
2022-08-10  9:54     ` [virtio-dev] " Cornelia Huck
2022-08-10 12:45       ` Michael S. Tsirkin
2022-08-10 13:07         ` [virtio-dev] " Cornelia Huck
2022-08-10 17:59         ` Halil Pasic
2022-08-10 17:41       ` Halil Pasic
2022-08-10 19:23         ` Michael S. Tsirkin
2022-08-11  9:12           ` Cornelia Huck
2022-08-11 11:15             ` Michael S. Tsirkin
2022-08-11 14:41             ` Halil Pasic [this message]
2022-08-11 17:27             ` Halil Pasic
2022-08-11  8:53         ` Cornelia Huck
2022-08-11 14:09           ` Halil Pasic
2022-08-11 16:20             ` David Hildenbrand
2022-03-30 15:26 [virtio-dev] [PATCH 0/4] Introduce aux. notifications and virtio-vhost-user Usama Arif
2022-03-30 15:26 ` [virtio-dev] [PATCH 1/4] content: Introduce driver/device auxiliary notifications Usama Arif
2022-04-04 10:06   ` [virtio-dev] " Stefan Hajnoczi

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=20220811164149.2e6ed3a7.pasic@linux.ibm.com \
    --to=pasic@linux.ibm.com \
    --cc=cohuck@redhat.com \
    --cc=fam.zheng@bytedance.com \
    --cc=liangma@liangbit.com \
    --cc=mst@redhat.com \
    --cc=ndragazis@arrikto.com \
    --cc=stefanha@redhat.com \
    --cc=usama.arif@bytedance.com \
    --cc=virtio-dev@lists.oasis-open.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.