All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Roedel <joro@8bytes.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Rodrigo Campos <rodrigo@sdfg.com.ar>, kvm@vger.kernel.org
Subject: Re: PCI Device Assignment status
Date: Sun, 5 Sep 2010 19:00:08 +0200	[thread overview]
Message-ID: <20100905170008.GC8162@8bytes.org> (raw)
In-Reply-To: <AANLkTi=3KgPTUwxJezTRjEODWfY1f9bMHVSvzBQurrBt@mail.gmail.com>

On Fri, Sep 03, 2010 at 04:38:00PM -0600, Alex Williamson wrote:
> On Fri, Sep 3, 2010 at 9:54 AM, Rodrigo Campos <rodrigo@sdfg.com.ar> wrote:
> > Hi!
> >
> > I wanted to know the status of PCI device assignment.
> >
> > As far as I can see in the webpage and in the mailing list, it seems to be
> > working ok if you have VT-d support on the motherboard and cpu. But if it isn't
> > too much trouble, I wanted some confirmation about this, since I'm not sure and
> > I don't want to buy hardware to test this when there is no way it's going to
> > work :)
> 
> Yes, it works if you have VT-d support (Intel) or AMD IOMMU (note this
> is different than the AMD GART that's often used as an IOMMU).  The
> Intel boxes are a lot easier to find.

For an AMD IOMMU you just need to buy a Mainboard with the AMD 890FX
chipset. As far as I know all available boards support IOMMU with the
latest BIOS.
On the server-side, look for an AMD SR56x0 chipset [where x=(5|7|9)].

	Joerg


  parent reply	other threads:[~2010-09-05 17:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-03 15:54 PCI Device Assignment status Rodrigo Campos
2010-09-03 22:38 ` Alex Williamson
2010-09-04  2:45   ` Rodrigo Campos
2010-09-05 17:00   ` Joerg Roedel [this message]
2010-09-06 14:38     ` Rodrigo Campos
2010-09-04  0:48 ` Kenni Lund
2010-09-04  2:57   ` Rodrigo Campos
2010-09-06 11:11 ` Konstantin Khlebnikov
2010-09-06 14:40   ` Rodrigo Campos

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=20100905170008.GC8162@8bytes.org \
    --to=joro@8bytes.org \
    --cc=alex.williamson@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=rodrigo@sdfg.com.ar \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.