linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@qumranet.com>
To: Amit Shah <amit.shah@qumranet.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	benami@il.ibm.com, Avi Kivity <avi@qumranet.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	kvm@vger.kernel.org, aliguori@us.ibm.com, allen.m.kay@intel.com,
	muli@il.ibm.com, linux-mm@kvack.org, tglx@linutronix.de,
	mingo@elte.hu
Subject: Re: [PATCH] reserved-ram for pci-passthrough without VT-d capable hardware
Date: Wed, 30 Jul 2008 15:58:46 +0200	[thread overview]
Message-ID: <20080730135846.GB11494@duo.random> (raw)
In-Reply-To: <200807301150.44266.amit.shah@qumranet.com>

On Wed, Jul 30, 2008 at 11:50:43AM +0530, Amit Shah wrote:
> * On Tuesday 29 July 2008 18:47:35 Andi Kleen wrote:
> > > I'm not so interested to go there right now, because while this code
> > > is useful right now because the majority of systems out there lacks
> > > VT-d/iommu, I suspect this code could be nuked in the long
> > > run when all systems will ship with that, which is why I kept it all
> >
> > Actually at least on Intel platforms and if you exclude the lowest end
> > VT-d is shipping universally for quite some time now. If you
> > buy a Intel box today or bought it in the last year the chances are pretty
> > high that it has VT-d support.
> 
> I think you mean VT-x, which is virtualization extensions for the x86 
> architecture. VT-d is virtualization extensions for devices (IOMMU).

I think Andi understood VT-d right but even if he was right that every
reader of this email that is buying a new VT-x system today is also
almost guaranteed to get a VT-d motherboard (which I disagree unless
you buy some really expensive toy), there are current large
installations of VT-x systems that lacks VT-d and that with recent
current dual/quadcore cpus are very fast and will be used for the next
couple of years and they will not upgrade just the motherboard to use
pci-passthrough.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  parent reply	other threads:[~2008-07-30 13:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1214232737-21267-1-git-send-email-benami@il.ibm.com>
     [not found] ` <1214232737-21267-2-git-send-email-benami@il.ibm.com>
     [not found]   ` <20080625005739.GM6938@duo.random>
2008-06-25  1:18     ` Andrea Arcangeli, Andrea Arcangeli
2008-07-29 12:11       ` Andrea Arcangeli, Andrea Arcangeli
2008-07-29 12:43         ` Andi Kleen
2008-07-29 12:53           ` Andrea Arcangeli
2008-07-29 13:17             ` Andi Kleen
2008-07-30  6:20               ` Amit Shah
2008-07-30 12:27                 ` Andi Kleen
2008-07-30 13:58                 ` Andrea Arcangeli [this message]
2008-07-30 14:16                   ` Dor Laor
2008-07-30 14:38                     ` Andrea Arcangeli
2008-07-30 14:22                   ` FUJITA Tomonori

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=20080730135846.GB11494@duo.random \
    --to=andrea@qumranet.com \
    --cc=akpm@linux-foundation.org \
    --cc=aliguori@us.ibm.com \
    --cc=allen.m.kay@intel.com \
    --cc=amit.shah@qumranet.com \
    --cc=andi@firstfloor.org \
    --cc=avi@qumranet.com \
    --cc=benami@il.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=muli@il.ibm.com \
    --cc=tglx@linutronix.de \
    /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