All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dor Laor <dlaor@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "Passera, Pablo R" <pablo.r.passera@intel.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: 1-1 mapping of devices without VT-d
Date: Tue, 02 Dec 2008 01:01:07 +0200	[thread overview]
Message-ID: <49346CB3.1020901@redhat.com> (raw)
In-Reply-To: <4934527C.1090507@msgid.tls.msk.ru>

Michael Tokarev wrote:
> Dor Laor wrote:
> []
>   
>> Although it had worked for us out of tree, there is no immediate need to
>> pursue it.
>> If anyone would like to nurture these patches he is more than welcome.
>> ps: you also have pv-dma option for Linux guests (same status though).
>> As time goes by most host will have either vt-d or amd iommu.
>>     
>
> Hmm.  Well, as time goes by, most hosts will be 64 bit or more.
> But it does not mean that there's no need to maintain 32bits
> arch anymore...  i hope anyway :)
>
>   
But of course
> Are you saying that PCI passthrough without hardware support will
> not be available in (standard) kvm, even if patches exists for that?
>
>   
No, just might take a some time to go to mainline. Patches need further 
polishing and we
also need wider demand for it.
Actually pvdma can help vt-d so we won't have to make all the guest 
memory unswappable.
> /mjt
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


      reply	other threads:[~2008-12-01 23:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01 15:34 1-1 mapping of devices without VT-d Passera, Pablo R
2008-12-01 20:13 ` Dor Laor
2008-12-01 21:09   ` Michael Tokarev
2008-12-01 23:01     ` Dor Laor [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=49346CB3.1020901@redhat.com \
    --to=dlaor@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=pablo.r.passera@intel.com \
    /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.