* [Qemu-devel] [PATCH] docs: pcie: Spell out machine type needs for PCIe features
@ 2018-02-19 15:43 Kashyap Chamarthy
2018-02-19 15:46 ` Daniel P. Berrangé
0 siblings, 1 reply; 3+ messages in thread
From: Kashyap Chamarthy @ 2018-02-19 15:43 UTC (permalink / raw)
To: qemu-devel; +Cc: mst, berrange, marcel, Kashyap Chamarthy
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
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] [PATCH] docs: pcie: Spell out machine type needs for PCIe features
2018-02-19 15:43 [Qemu-devel] [PATCH] docs: pcie: Spell out machine type needs for PCIe features Kashyap Chamarthy
@ 2018-02-19 15:46 ` Daniel P. Berrangé
2018-02-19 16:20 ` Kashyap Chamarthy
0 siblings, 1 reply; 3+ messages in thread
From: Daniel P. Berrangé @ 2018-02-19 15:46 UTC (permalink / raw)
To: Kashyap Chamarthy; +Cc: qemu-devel, mst, marcel
On Mon, Feb 19, 2018 at 04:43:33PM +0100, Kashyap Chamarthy wrote:
> 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.
Pre-existing bug s/device/devices/
> +This applies to the Q35 machine type on x86 and the 'virt' machine type
For consistency I'd suggest 'q35' rather than Q35.
> +on AArch64 (in other words, PCIe features are available only when using
> +the Q35 and 'virt' machine types for the said architectures). Other
And again, though I feel the stuff in (...) is just repeating what's
said in the stuff either side of the brackets.
> +machine types do not use PCI Express at this time.
>
> The following presentations accompany this document:
> (1) Q35 overview.
> --
> 2.13.6
>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] [PATCH] docs: pcie: Spell out machine type needs for PCIe features
2018-02-19 15:46 ` Daniel P. Berrangé
@ 2018-02-19 16:20 ` Kashyap Chamarthy
0 siblings, 0 replies; 3+ messages in thread
From: Kashyap Chamarthy @ 2018-02-19 16:20 UTC (permalink / raw)
To: Daniel P. Berrangé; +Cc: qemu-devel, mst, marcel
On Mon, Feb 19, 2018 at 03:46:12PM +0000, Daniel P. Berrangé wrote:
> On Mon, Feb 19, 2018 at 04:43:33PM +0100, Kashyap Chamarthy wrote:
> > PCIe features are available only via the Q35 machine for x86, or the
[...]
> > 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.
>
> Pre-existing bug s/device/devices/
Fixed in v2.
> > +This applies to the Q35 machine type on x86 and the 'virt' machine type
>
> For consistency I'd suggest 'q35' rather than Q35.
Yep, fixed in v2.
(I actually did that first in v1 and removed it — as I saw the
captialized variant used througout the doc. But I see you're asking to
be consistent in the sentence.)
> > +on AArch64 (in other words, PCIe features are available only when using
> > +the Q35 and 'virt' machine types for the said architectures). Other
>
> And again, though I feel the stuff in (...) is just repeating what's
> said in the stuff either side of the brackets.
I was also hesitant on the repetition. But I wanted to put some wording
that is unambiguous about the mandatory requirements. How about this,
that I currently have in my v2 draft:
"Note that the PCIe features are available only when using the 'q35'
machine type on x86 architecture and the 'virt' machine type on
AArch64. Other machine types do not use PCIe at this time."
Thanks for the quick review!
--
/kashyap
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2018-02-19 16:20 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-02-19 15:43 [Qemu-devel] [PATCH] docs: pcie: Spell out machine type needs for PCIe features Kashyap Chamarthy
2018-02-19 15:46 ` Daniel P. Berrangé
2018-02-19 16:20 ` Kashyap Chamarthy
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.