Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754404Ab3DZMG1 (ORCPT ); Fri, 26 Apr 2013 08:06:27 -0400 Received: from mail-vc0-f171.google.com ([209.85.220.171]:60858 "EHLO mail-vc0-f171.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753763Ab3DZMGR (ORCPT ); Fri, 26 Apr 2013 08:06:17 -0400 MIME-Version: 1.0 In-Reply-To: References: <1366974299-17877-1-git-send-email-pranavkumar@linaro.org> Date: Fri, 26 Apr 2013 17:36:16 +0530 Message-ID: Subject: Re: [PATCH 0/2] Early printk support for virtio console devices. From: Anup Patel To: Peter Maydell Cc: Alexander Graf , linaro-kernel@lists.linaro.org, patches@linaro.org, "linux-kernel@vger.kernel.org List" , kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1269 Lines: 33 On 26 April 2013 17:03, Peter Maydell wrote: > On 26 April 2013 12:19, Alexander Graf wrote: >> MMIO registers are handled by a different layer than the virtio >> console itself. After the virtio refactoring in QEMU, they will >> be completely separate drivers. > > Good point -- we don't really want to be mixing up the > transport and the backend. You can see it in the kvmtool > patch, in fact -- it introduces an "if this is virtio-console" > special case into the mmio.c file which previously was > entirely backend agnostic. Well, we can always have virtio device specific config registers handle by virtio device backends and generic virtio config register handled by transport. kvmtool patch is hacky because it does not provide virtio device specific config read/write callbacks. > > thanks > -- PMM > _______________________________________________ > kvmarm mailing list > kvmarm@lists.cs.columbia.edu > https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm --Anup -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/