From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35987) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z4piM-0000S1-8d for qemu-devel@nongnu.org; Tue, 16 Jun 2015 08:11:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z4piI-0001kD-Lj for qemu-devel@nongnu.org; Tue, 16 Jun 2015 08:11:38 -0400 Received: from mail-wg0-f45.google.com ([74.125.82.45]:35183) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z4piI-0001k1-FM for qemu-devel@nongnu.org; Tue, 16 Jun 2015 08:11:34 -0400 Received: by wgbhy7 with SMTP id hy7so10708652wgb.2 for ; Tue, 16 Jun 2015 05:11:34 -0700 (PDT) Message-ID: <55801264.7030507@linaro.org> Date: Tue, 16 Jun 2015 14:11:16 +0200 From: Eric Auger MIME-Version: 1.0 References: <1434455898-17895-1-git-send-email-eric.auger@linaro.org> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v17] hw/arm/sysbus-fdt: enable vfio-calxeda-xgmac dynamic instantiation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: b.reynal@virtualopensystems.com, Patch Tracking , QEMU Developers , Alex Williamson , eric.auger@st.com, Christoffer Dall Hi Peter, On 06/16/2015 01:59 PM, Peter Maydell wrote: > On 16 June 2015 at 12:58, Eric Auger wrote: >> This patch allows the instantiation of the vfio-calxeda-xgmac device >> from the QEMU command line (-device vfio-calxeda-xgmac,host=""). >> >> A specialized device tree node is created for the guest, containing >> compat, dma-coherent, reg and interrupts properties. >> >> Signed-off-by: Eric Auger >> Acked-by: Peter Maydell > > This was part of a series before -- is it a standalone > patch now? What's the relationship with the other patches? This patch makes possible to instantiate the VFIO Calxeda xgmac device which is already in the master. The rest of the series enables irqfd usage by the base VFIO device so to me it is independent. Currently eventfds are handled on user-side, which is particularly inefficient but functional. Let me know if you prefer I resend the whole series. Best Regards Eric > > thanks > -- PMM >