qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] add iommu version to sparc32
Date: Sat, 17 Nov 2007 11:12:49 +0200	[thread overview]
Message-ID: <f43fc5580711170112g2c14e324h6f73f846d6ce1d60@mail.gmail.com> (raw)
In-Reply-To: <473CCE9A.1010709@earthlink.net>

On 11/16/07, Robert Reif <reif@earthlink.net> wrote:
>
> >>Add iommu version to sparc32.  Also reset iommu after initialization.
> >>
> >>
> >
> >Should the version be tied to CPU model instead of machine type? At
> >least for Turbosparc this seems to be the case.
> >
> >
> On SMP systems the IOMMU is on the system board in a separate ASIC.  On
> single CPU systems the IOMMU is integrated into the CPU.  Without checking
> the FEH, the SS 5 was the only single CPU system that shipped with more than
> one family of CPUs (MicroSparc II and TurboSparc and they do have different
> IOMMU versions).  That could be special cased.

OK, then the machine is more correct place.

Thanks, patch applied.

> Unfortunately QEMU will allow you to specify unrealistic systems.  We
> should
> probably add allowable CPU types to specific machine types to catch this.

Well, there are plenty of things that can be unrealistic, for example
memory size. For the IOMMU case, Linux does not make any checks for
the version, same with NetBSD. I don't think it matters too much.

      reply	other threads:[~2007-11-17  9:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-12 23:01 [Qemu-devel] [PATCH] add iommu version to sparc32 Robert Reif
2007-11-15 17:21 ` Blue Swirl
2007-11-15 22:56   ` Robert Reif
2007-11-17  9:12     ` Blue Swirl [this message]

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=f43fc5580711170112g2c14e324h6f73f846d6ce1d60@mail.gmail.com \
    --to=blauwirbel@gmail.com \
    --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).