From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [Qemu-devel] [RFC PATCH 4/7] sparc: rename hw/iommu.c Date: Wed, 31 Mar 2010 09:27:20 +0200 Message-ID: <4BB2F958.50708@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Eduard - Gabriel Munteanu , joro@8bytes.org, aliguori@us.ibm.com, avi@redhat.com, kvm@vger.kernel.org, qemu-devel@nongnu.org To: Blue Swirl Return-path: Received: from mx1.redhat.com ([209.132.183.28]:45471 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756722Ab0CaH1t (ORCPT ); Wed, 31 Mar 2010 03:27:49 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 03/30/10 19:06, Blue Swirl wrote: > On 3/30/10, Eduard - Gabriel Munteanu wrote: >> hw/iommu.c concerns the SPARC IOMMU. However we intend to implement the >> AMD IOMMU, which could lead to confusion unless we rename the former. > > I was also thinking of renaming the file some time ago. The correct > name would be "sun4m_iommu.c". Sun4c (while still Sparc based) had a > different architecture (IIRC CPU MMU doubled as IOMMU) and Sun4d had > several IO-UNITs instead. All Sun4m machines had an IOMMU. > > But the qdev name of the device is still "iommu" and we can't change > that. So I'm not so sure it's worth renaming. Can't AMD IOMMU reside > in amd_iommu.c? I'd go for the (filename) rename. The qdev name shouldn't cause conflicts due to the different targets. cheers, Gerd