All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Anthony Liguori <aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] Update virtio to latest ABI
Date: Mon, 28 Jan 2008 19:26:34 +0200	[thread overview]
Message-ID: <479E104A.2040405@qumranet.com> (raw)
In-Reply-To: <479DFC3E.8020709-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>

Anthony Liguori wrote:
>>
>> I'm worried about the ramp up to 2.6.25 causing confusion among users 
>> as before that things will break left and right, if we don't provide 
>> a tighter check.
>>
>
> Well, using the PCI revision ID isn't a bad idea.  It wouldn't have 
> helped this last problem because that was an ABI break in the network 
> driver and we really can't indicate a ABI break in the PCI driver for 
> any possibly virtio device.


Why not?  we have one pci device per virtio device, and in the same way 
the pci id is device-specific, the revision id can be device specific as 
well.  We just need a virtio revision field, and a pci-virtio binding 
for that field.

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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2008-01-28 17:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 20:00 [PATCH] Update virtio to latest ABI Anthony Liguori
     [not found] ` <12012048063315-git-send-email-aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-01-27  7:18   ` Avi Kivity
     [not found]     ` <479C3049.1010509-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-27 23:06       ` Anthony Liguori
     [not found]         ` <479D0E7B.2060400-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-01-28 10:49           ` Avi Kivity
     [not found]             ` <479DB34F.8080001-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-28 16:01               ` Anthony Liguori
     [not found]                 ` <479DFC3E.8020709-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-01-28 17:26                   ` Avi Kivity [this message]
     [not found]                     ` <479E104A.2040405-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-28 18:28                       ` Anthony Liguori

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=479E104A.2040405@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=aliguori-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.