From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin Subject: Re: [PATCH RFC] virtio-spec: flexible configuration layout Date: Wed, 09 Nov 2011 11:55:02 +0200 Message-ID: <1320832502.31056.22.camel@lappy> References: <87wrbkvh3v.fsf@rustcorp.com.au> <20111101114542.GA13434@redhat.com> <1320150813.3847.24.camel@lappy> <20111101124223.GA14060@redhat.com> <8739e7uy87.fsf@rustcorp.com.au> <20111102233110.GA20289@redhat.com> <20111108214021.GA4538@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Rusty Russell , lkml - Kernel Mailing List , Alexey Kardashevskiy , Amit Shah , Christian Borntraeger , Krishna Kumar , Pawel Moll , Wang Sheng-Hui , virtualization@lists.linux-foundation.org, kvm@vger.kernel.org, avi@redhat.com To: "Michael S. Tsirkin" Return-path: In-Reply-To: <20111108214021.GA4538@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Tue, 2011-11-08 at 23:40 +0200, Michael S. Tsirkin wrote: > Here's a spec change documenting what my C patch does > (almost - I tweaked the layout a bit, but the idea is the same). > Some more cleanups are needed but I thought I'd send it > for early flames/comments. > > The idea is simple: we split functionally unrelated > register groups to independent structures, and let > the device place is anywhere using a capability > in PCI configuration space. I'm also wondering it it's ok to move virtio configuration out of virtio space and into PCI space for archs that don't have PCI (such as ARM). Would it mean they get stuck with legacy configuration (and no new features)? Or is there an alternative for them? -- Sasha.