From: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org, Joerg Roedel <joro@8bytes.org>,
aliguori@us.ibm.com, kvm@vger.kernel.org, avi@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH 4/7] sparc: rename hw/iommu.c
Date: Tue, 30 Mar 2010 23:15:04 +0300 [thread overview]
Message-ID: <20100330201504.GA7956@localhost> (raw)
In-Reply-To: <i2gf43fc5581003301300m7019f68em53341d00af6d2dca@mail.gmail.com>
On Tue, Mar 30, 2010 at 11:00:10PM +0300, Blue Swirl wrote:
> On 3/30/10, Joerg Roedel <joro@8bytes.org> wrote:
> > On Tue, Mar 30, 2010 at 08:06:36PM +0300, Blue Swirl wrote:
> > > On 3/30/10, Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro> 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?
> >
> >
> > Keeping the plain name 'iommu' will likely cause confusion when more
> > iommu implementations are added. It is better to rename it so that the
> > name better describes what the file implements. So this change makes
> > sense for me.
>
> I see. I'm OK then with "sun4m_iommu.c".
Yes, I think it's enough to just change the filename, since multiple
such devices aren't likely to conflict, in any configuration.
Then "sun4m_iommu.c" it is. Will resubmit with the next patchset.
Eduard
next prev parent reply other threads:[~2010-03-30 20:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 8:20 [Qemu-devel] [RFC PATCH 0/7] Beginning implementing the AMD IOMMU emulation Eduard - Gabriel Munteanu
2010-03-30 8:20 ` [Qemu-devel] [RFC PATCH 1/7] acpi: qemu_realloc() might return a different pointer Eduard - Gabriel Munteanu
2010-03-30 8:20 ` [Qemu-devel] [RFC PATCH 2/7] acpi: split and rename acpi_table_add() Eduard - Gabriel Munteanu
2010-03-30 8:20 ` [Qemu-devel] [RFC PATCH 3/7] acpi: move table header definition into pc.h Eduard - Gabriel Munteanu
2010-03-30 8:20 ` [Qemu-devel] [RFC PATCH 4/7] sparc: rename hw/iommu.c Eduard - Gabriel Munteanu
2010-03-30 17:06 ` Blue Swirl
2010-03-30 19:28 ` Joerg Roedel
2010-03-30 20:00 ` Blue Swirl
2010-03-30 20:15 ` Eduard - Gabriel Munteanu [this message]
2010-03-31 7:27 ` Gerd Hoffmann
2010-03-30 8:20 ` [Qemu-devel] [RFC PATCH 5/7] x86-64: AMD IOMMU stub Eduard - Gabriel Munteanu
2010-03-30 20:37 ` Blue Swirl
2010-03-30 8:20 ` [Qemu-devel] [RFC PATCH 6/7] acpi: cleanup acpi_checksum() Eduard - Gabriel Munteanu
2010-03-30 8:20 ` [Qemu-devel] [RFC PATCH 7/7] acpi: fix bug in acpi_checksum() caused by garbage in checksum field Eduard - Gabriel Munteanu
2010-03-30 15:10 ` Richard Henderson
2010-03-30 19:40 ` [Qemu-devel] Re: [RFC PATCH 0/7] Beginning implementing the AMD IOMMU emulation Joerg Roedel
2010-03-31 5:38 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100330201504.GA7956@localhost \
--to=eduard.munteanu@linux360.ro \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).