From: Kashyap Chamarthy <kchamart@redhat.com>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com, berrange@redhat.com, marcel@redhat.com,
Kashyap Chamarthy <kchamart@redhat.com>
Subject: [Qemu-devel] [PATCH] docs: pcie: Spell out machine type needs for PCIe features
Date: Mon, 19 Feb 2018 16:43:33 +0100 [thread overview]
Message-ID: <20180219154333.20810-1-kchamart@redhat.com> (raw)
PCIe features are available only via the Q35 machine for x86, or the
'virt' machine type for AArch64 architecture.
Mention that explicitly.
Thanks: Daniel Berrangé
Signed-off-by: Kashyap Chamarthy <kchamart@redhat.com>
---
docs/pcie.txt | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/docs/pcie.txt b/docs/pcie.txt
index 8d3694970e..3e5bf52e0b 100644
--- a/docs/pcie.txt
+++ b/docs/pcie.txt
@@ -3,8 +3,14 @@ PCI EXPRESS GUIDELINES
1. Introduction
================
-The doc proposes best practices on how to use PCI Express/PCI device
-in PCI Express based machines and explains the reasoning behind them.
+The doc proposes best practices on how to use PCI Express (PCIe) / PCI
+device in PCI Express based machines and explains the reasoning behind
+them.
+
+This applies to the Q35 machine type on x86 and the 'virt' machine type
+on AArch64 (in other words, PCIe features are available only when using
+the Q35 and 'virt' machine types for the said architectures). Other
+machine types do not use PCI Express at this time.
The following presentations accompany this document:
(1) Q35 overview.
--
2.13.6
next reply other threads:[~2018-02-19 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-19 15:43 Kashyap Chamarthy [this message]
2018-02-19 15:46 ` [Qemu-devel] [PATCH] docs: pcie: Spell out machine type needs for PCIe features Daniel P. Berrangé
2018-02-19 16:20 ` Kashyap Chamarthy
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=20180219154333.20810-1-kchamart@redhat.com \
--to=kchamart@redhat.com \
--cc=berrange@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@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 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.