test suite reviews and discussions
 help / color / mirror / Atom feed
From: Rami Rosen <ramirose@gmail.com>
To: dts@dpdk.org
Cc: Rami Rosen <ramirose@gmail.com>
Subject: [dts] [PATCH] doc: adding info to virtualization gsg about dumping PCI info in a VM
Date: Tue, 25 Dec 2018 13:24:28 +0200	[thread overview]
Message-ID: <1545737068-104145-1-git-send-email-ramirose@gmail.com> (raw)

This patch adds more info about using the "info pci" QEMU/Monitor 
command to dump PCI info in a VM, and fixes two trivial typos 
in that same sentence as well.

Signed-off-by: Rami Rosen <ramirose@gmail.com>
---
 doc/dts_gsg/virtualization.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 mode change 100644 => 100755 doc/dts_gsg/virtualization.rst

diff --git a/doc/dts_gsg/virtualization.rst b/doc/dts_gsg/virtualization.rst
old mode 100644
new mode 100755
index 6033a8b..3d6c28b
--- a/doc/dts_gsg/virtualization.rst
+++ b/doc/dts_gsg/virtualization.rst
@@ -423,8 +423,8 @@ When assign host pci device into guest, we also add "id" string for this device.
 
 	-device pci-assign,host=07:10.0,id=pt_0
 	
-With this command, we assign host VF device 07:10.0 into guest and it named as "pt_0". "pt_0" mean it's the first device pass through into guest os.
-After guest os started, we use dump pci command and generate guest and host pci mapping by "id".
+With this command, we assign host VF device 07:10.0 into guest and it is named as "pt_0". "pt_0" means it's the first device pass through into guest os.
+After guest os started, we use the QEMU/Monitor "info pci" command to dump PCI information and generate guest and host pci mapping by "id".
 
 .. code-block:: console
 
-- 
1.8.3.1

             reply	other threads:[~2018-12-25 11:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-25 11:24 Rami Rosen [this message]
2018-12-26 17:35 ` Lijuan Tu

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=1545737068-104145-1-git-send-email-ramirose@gmail.com \
    --to=ramirose@gmail.com \
    --cc=dts@dpdk.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).