From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: any plans to sopport virtio-serial ? Date: Wed, 24 Nov 2010 14:10:54 +0100 Message-ID: <4CED0EDE.6010406@redhat.com> References: <1290499219.17994.119.camel@vase> <1290505747.31507.7631.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1290505747.31507.7631.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" , "v.tolstov@selfip.ru" List-Id: xen-devel@lists.xenproject.org Hi, > As I understand it (which is very vague) virtio allows each architecture > to supply device discovery, shared ring and event notification backends > which it then builds the specific device services on top of. Yes. I think there are three backends now: pci, lguest, s390. > I think the > most obvious solution is to do device discovery using XenStore but to do > the shared ring and event notification bits with page grants and event > channels respectively. I was under the impression that virtio was > designed with the possibility of this sort of Xen backend in mind. Yes, that should be possible. Another option would be to just use the pci backend. As I understand it nowdays pci is available even in pv guests for pci device passthrough, so in theory this should work fine for both pv and hvm guests ... cheers, Gerd