From: Seeteena Thoufeek <s1seetee@linux.vnet.ibm.com>
To: david@gibson.dropbear.id.au, agraf@suse.de, qemu-ppc@nongnu.org,
qemu-devel@nongnu.org
Cc: s1seetee@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH v1] spapr_pci: fix the path while fetching loc-code from host DT
Date: Tue, 7 Nov 2017 18:48:58 +0530 [thread overview]
Message-ID: <1510060738-25975-1-git-send-email-s1seetee@linux.vnet.ibm.com> (raw)
The function spapr_phb_vfio_get_loc_code uses wrong path for
fetching loc-code from host DT
this is the call that needs to be fixed:
/* Construct and read from host device tree the loc-code */
path = g_strdup_printf("/proc/device-tree%s/ibm,loc-code", buf);
Signed-off-by: Seeteena Thoufeek <s1seetee@linux.vnet.ibm.com>
---
hw/ppc/spapr_pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/ppc/spapr_pci.c b/hw/ppc/spapr_pci.c
index 5a3122a..ae86322 100644
--- a/hw/ppc/spapr_pci.c
+++ b/hw/ppc/spapr_pci.c
@@ -762,7 +762,7 @@ static char *spapr_phb_vfio_get_loc_code(sPAPRPHBState *sphb, PCIDevice *pdev)
g_free(path);
/* Construct and read from host device tree the loc-code */
- path = g_strdup_printf("/proc/device-tree%s/ibm,loc-code", buf);
+ path = g_strdup_printf("/proc/device-tree/%s/ibm,loc-code", buf);
g_free(buf);
if (!g_file_get_contents(path, &buf, NULL, NULL)) {
goto err_out;
--
1.8.3.1
next reply other threads:[~2017-11-07 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 13:18 Seeteena Thoufeek [this message]
2017-11-08 2:30 ` [Qemu-devel] [Qemu-ppc] [PATCH v1] spapr_pci: fix the path while fetching loc-code from host DT Alexey Kardashevskiy
2017-11-08 6:08 ` David Gibson
2017-11-08 14:34 ` seeteena
2017-11-08 11:29 ` Greg Kurz
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=1510060738-25975-1-git-send-email-s1seetee@linux.vnet.ibm.com \
--to=s1seetee@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).