From: Jan Kiszka <jan.kiszka@web.de>
To: Le Tan <tamlokveer@gmail.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
Knut Omang <knut.omang@oracle.com>,
Anthony Liguori <aliguori@amazon.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/3] intel-iommu: add Intel IOMMU emulation to q35 and add a machine option "vtd" as a switch
Date: Sat, 26 Jul 2014 10:47:19 +0200 [thread overview]
Message-ID: <53D36B17.3020705@web.de> (raw)
In-Reply-To: <1406044070-25667-4-git-send-email-tamlokveer@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
On 2014-07-22 17:47, Le Tan wrote:
> Add Intel IOMMU emulation to q35 chipset and expose it to the guest.
> 1. Add a machine option. Users can use "-machine vtd=on|off" in the command
> line to enable/disable Intel IOMMU. The default is off.
Better call it "iommu". We could once reuse the switch when someone adds
an AMD IOMMU emulation (and a corresponding chipset as well, I suppose).
And maybe other target archs will find it useful as well.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2014-07-26 8:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 15:47 [Qemu-devel] [PATCH 0/3] intel-iommu: introduce Intel IOMMU (VT-d) emulation to q35 chipset Le Tan
2014-07-22 15:47 ` [Qemu-devel] [PATCH 1/3] intel-iommu: introduce Intel IOMMU (VT-d) emulation Le Tan
2014-07-22 20:05 ` Michael S. Tsirkin
2014-07-23 1:25 ` Le Tan
2014-07-23 7:58 ` Paolo Bonzini
2014-07-23 23:21 ` Le Tan
2014-07-23 20:29 ` Stefan Weil
2014-07-23 23:24 ` Le Tan
2014-08-03 15:16 ` Knut Omang
2014-07-22 15:47 ` [Qemu-devel] [PATCH 2/3] intel-iommu: add DMAR table to ACPI tables Le Tan
2014-07-22 15:47 ` [Qemu-devel] [PATCH 3/3] intel-iommu: add Intel IOMMU emulation to q35 and add a machine option "vtd" as a switch Le Tan
2014-07-26 8:47 ` 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=53D36B17.3020705@web.de \
--to=jan.kiszka@web.de \
--cc=alex.williamson@redhat.com \
--cc=aliguori@amazon.com \
--cc=knut.omang@oracle.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--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;
as well as URLs for NNTP newsgroup(s).