virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH] Use PCI revision field to indicate virtio PCI ABI version
Date: Tue, 29 Jan 2008 16:42:32 +0200	[thread overview]
Message-ID: <479F3B58.9000301@qumranet.com> (raw)
In-Reply-To: <200801291529.53808.borntraeger@de.ibm.com>

Christian Borntraeger wrote:
> Am Dienstag, 29. Januar 2008 schrieb Anthony Liguori:
>   
>> That's not what I was agreeing too.  I don't want to plumb an ABI 
>> interface through virtio for each device.  This is what I didn't like 
>> about having an ABI field in the first place.  I'm thinking we should 
>> just drop both of these and instead just rely on feature bits.
>>     
>
> Me also updating the our prototype code to the latest levels...
>
> And I agree with Anthony. Feature bits seems to be a much better solution 
> than ABI versions.
>   

I agree that feature bits are the long term solution; but we need a 
short term solution before the ABI is stabilized.  We don't want to add 
feature bits now, since that will encode virtio development history into 
those bits (likely consuming most of them).


-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2008-01-29 14:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 15:59 [PATCH] Use PCI revision field to indicate virtio PCI ABI version Anthony Liguori
2008-01-29  3:20 ` Rusty Russell
2008-01-29  8:03   ` Avi Kivity
2008-01-29 12:38     ` Rusty Russell
2008-01-29 16:03       ` Anthony Liguori
2008-01-30 11:10         ` Rusty Russell
2008-01-29 14:16     ` Anthony Liguori
2008-01-29 14:29       ` Christian Borntraeger
2008-01-29 14:42         ` Avi Kivity [this message]
2008-01-29 14:56           ` Anthony Liguori
2008-01-29 15:32             ` Avi Kivity
2008-01-29 15:39               ` Christian Borntraeger
2008-01-29 16:02                 ` Avi Kivity

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=479F3B58.9000301@qumranet.com \
    --to=avi@qumranet.com \
    --cc=aliguori@us.ibm.com \
    --cc=borntraeger@de.ibm.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 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).