All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Krishna Kumar <krkumar2@in.ibm.com>,
	kvm@vger.kernel.org, Pawel Moll <pawel.moll@arm.com>,
	Wang Sheng-Hui <shhuiw@gmail.com>,
	Alexey Kardashevskiy <aik@ozlabs.ru>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	virtualization@lists.linux-foundation.org,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Sasha Levin <levinsasha928@gmail.com>,
	Amit Shah <amit.shah@redhat.com>
Subject: Re: [PATCHv3 RFC] virtio-pci: flexible configuration layout
Date: Wed, 30 Nov 2011 09:58:45 +1030	[thread overview]
Message-ID: <87sjl6tsnm.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20111128084009.GB20084@redhat.com>

On Mon, 28 Nov 2011 10:41:51 +0200, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Mon, Nov 28, 2011 at 11:25:43AM +1030, Rusty Russell wrote:
> > > > But I'm *terrified* of making the spec more complex;
> > > 
> > > All you do is move stuff around. Why do you think it simplifies the spec
> > > so much?
> > 
> > No, but it reduces the yuk factor.  Which has been important to adoption.
> 
> Sorry if I'm dense. Could you please clarify: do you think we can live
> with the slightly higher yuk factor assuming the spec moves the
> legacy mode into an appendix as you explain below and driver has a
> single 'legacy' switch?

Yep, it's all a trade-off.  A clean slate is good, but if we can make
our lives in transition less painful, I'm all for it.

> I think I see a way to do that in a relatively painless way.
> Do you prefer seeing driver patches or spec? Or are you not interested
> in reusing the same structure at all?

I think we should look at code at this point; my gut says we're going to
be not-quite-similar-enough-to-be-useful.  At which point, a clean-slate
approach is more appealing.  But the code will show, one way or another.

Thanks,
Rusty.

WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
	lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Alexey Kardashevskiy <aik@ozlabs.ru>,
	Amit Shah <amit.shah@redhat.com>,
	Christian Borntraeger <borntraeger@de.ibm.com>,
	Krishna Kumar <krkumar2@in.ibm.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Wang Sheng-Hui <shhuiw@gmail.com>,
	virtualization@lists.linux-foundation.org, kvm@vger.kernel.org
Subject: Re: [PATCHv3 RFC] virtio-pci: flexible configuration layout
Date: Wed, 30 Nov 2011 09:58:45 +1030	[thread overview]
Message-ID: <87sjl6tsnm.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20111128084009.GB20084@redhat.com>

On Mon, 28 Nov 2011 10:41:51 +0200, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> On Mon, Nov 28, 2011 at 11:25:43AM +1030, Rusty Russell wrote:
> > > > But I'm *terrified* of making the spec more complex;
> > > 
> > > All you do is move stuff around. Why do you think it simplifies the spec
> > > so much?
> > 
> > No, but it reduces the yuk factor.  Which has been important to adoption.
> 
> Sorry if I'm dense. Could you please clarify: do you think we can live
> with the slightly higher yuk factor assuming the spec moves the
> legacy mode into an appendix as you explain below and driver has a
> single 'legacy' switch?

Yep, it's all a trade-off.  A clean slate is good, but if we can make
our lives in transition less painful, I'm all for it.

> I think I see a way to do that in a relatively painless way.
> Do you prefer seeing driver patches or spec? Or are you not interested
> in reusing the same structure at all?

I think we should look at code at this point; my gut says we're going to
be not-quite-similar-enough-to-be-useful.  At which point, a clean-slate
approach is more appealing.  But the code will show, one way or another.

Thanks,
Rusty.

  reply	other threads:[~2011-11-29 23:28 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 18:36 [PATCHv3 RFC] virtio-pci: flexible configuration layout Michael S. Tsirkin
2011-11-22 18:36 ` Michael S. Tsirkin
2011-11-23  2:32 ` Rusty Russell
2011-11-23  2:32   ` Rusty Russell
2011-11-23  8:46   ` Michael S. Tsirkin
2011-11-23  8:46     ` Michael S. Tsirkin
2011-11-23 15:34     ` Michael S. Tsirkin
2011-11-23 15:34       ` Michael S. Tsirkin
2011-11-24  0:36     ` Rusty Russell
2011-11-24  0:36       ` Rusty Russell
2011-11-24  6:24       ` Michael S. Tsirkin
2011-11-24  6:24         ` Michael S. Tsirkin
2011-11-24  7:11       ` Michael S. Tsirkin
2011-11-24  7:11         ` Michael S. Tsirkin
2011-11-28  0:55         ` Rusty Russell
2011-11-28  0:55           ` Rusty Russell
2011-11-28  8:41           ` Michael S. Tsirkin
2011-11-28  8:41             ` Michael S. Tsirkin
2011-11-29 23:28             ` Rusty Russell [this message]
2011-11-29 23:28               ` Rusty Russell
2011-11-30  7:18               ` Michael S. Tsirkin
2011-11-30  7:18                 ` Michael S. Tsirkin
2011-11-28  9:15           ` Sasha Levin
2011-11-28  9:15             ` Sasha Levin
2011-11-29 23:40             ` Rusty Russell
2011-11-29 23:40               ` Rusty Russell
2011-11-30  8:14               ` Michael S. Tsirkin
2011-11-30  8:14                 ` Michael S. Tsirkin
2011-11-30 13:12               ` Sasha Levin
2011-11-30 13:12                 ` Sasha Levin
2011-12-01  2:42                 ` Rusty Russell
2011-12-01  2:42                   ` Rusty Russell
2011-11-23  8:49   ` Michael S. Tsirkin
2011-11-23  8:49     ` Michael S. Tsirkin
2011-11-23  9:38     ` Sasha Levin
2011-11-23  9:38       ` Sasha Levin
2011-11-24  1:07       ` Rusty Russell
2011-11-24  1:07         ` Rusty Russell
2011-11-23  9:44   ` Sasha Levin
2011-11-23  9:44     ` Sasha Levin

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=87sjl6tsnm.fsf@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=aik@ozlabs.ru \
    --cc=amit.shah@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=krkumar2@in.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pawel.moll@arm.com \
    --cc=shhuiw@gmail.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.