From: Jan Kiszka <jan.kiszka@siemens.com>
To: Hu Yaohui <loki2441@gmail.com>, kvm <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Le Tan <tamlokveer@gmail.com>
Subject: Re: direct device assignment in nested VM
Date: Fri, 04 Jul 2014 07:44:11 +0200 [thread overview]
Message-ID: <53B63F2B.1050503@siemens.com> (raw)
In-Reply-To: <CAHqbYQsN-9zMrsZ6aBG-iJ=vJ58y1s_tz5kX63Jo+kf+Nd2q1Q@mail.gmail.com>
On 2014-07-04 05:27, Hu Yaohui wrote:
> Hi All,
> Is direct device assignment in nested VM supported in the latest KVM
> mainline now?
Le Tan is currently working on emulated device assignment (VT-d
emulation in QEMU). This is the necessary first step and could later be
extended to enable assignment of physical devices to nested guests with
support of the host IOMMU (out of scope for Le's project, though).
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2014-07-04 5:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 3:27 direct device assignment in nested VM Hu Yaohui
2014-07-04 5:44 ` Jan Kiszka [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=53B63F2B.1050503@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loki2441@gmail.com \
--cc=tamlokveer@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox