From: Le Tan <tamlokveer@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Knut Omang <knut.omang@oracle.com>,
Jan Kiszka <jan.kiszka@web.de>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] About the VT-d features that q35 chipset supports
Date: Tue, 5 Aug 2014 20:55:14 +0800 [thread overview]
Message-ID: <CACrq+iLqG9rPD2yHJBHN3APbUYR_0XEssNnyMFBOtpbx8_riuA@mail.gmail.com> (raw)
Hi,
I am now adding features to the VT-d emulation for q35 chipset. I
think it is good to know what features q35 chipset supports exactly.
However I can't find materials about this. Does anyone know this? Or
it will be fine if someone can tell me the value of the Capability
Register and Extended Capability Register of the VT-d on q35.
Any help is appreciated!
Thanks very much!
Regards,
Le
next reply other threads:[~2014-08-05 12:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 12:55 Le Tan [this message]
2014-08-05 17:08 ` [Qemu-devel] About the VT-d features that q35 chipset supports Jan Kiszka
2014-08-05 23:10 ` Le Tan
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=CACrq+iLqG9rPD2yHJBHN3APbUYR_0XEssNnyMFBOtpbx8_riuA@mail.gmail.com \
--to=tamlokveer@gmail.com \
--cc=jan.kiszka@web.de \
--cc=knut.omang@oracle.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).