From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, Michael Roth <mdroth@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PULL v4 07/14] qga: guest-get-memory-blocks shouldn't fail for unexposed memory blocks
Date: Mon, 19 Oct 2015 18:38:12 -0500 [thread overview]
Message-ID: <1445297899-20527-8-git-send-email-mdroth@linux.vnet.ibm.com> (raw)
In-Reply-To: <1445297899-20527-1-git-send-email-mdroth@linux.vnet.ibm.com>
Some guests don't expose memory blocks via sysfs at all. This
shouldn't be a failure, instead just return an empty list. For
other access failures we still report an error.
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
---
qga/commands-posix.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/qga/commands-posix.c b/qga/commands-posix.c
index a932809..ff0ba62 100644
--- a/qga/commands-posix.c
+++ b/qga/commands-posix.c
@@ -2213,8 +2213,14 @@ GuestMemoryBlockList *qmp_guest_get_memory_blocks(Error **errp)
dp = opendir("/sys/devices/system/memory/");
if (!dp) {
- error_setg_errno(errp, errno, "Can't open directory"
- "\"/sys/devices/system/memory/\"\n");
+ /* it's ok if this happens to be a system that doesn't expose
+ * memory blocks via sysfs, but otherwise we should report
+ * an error
+ */
+ if (errno != ENOENT) {
+ error_setg_errno(errp, errno, "Can't open directory"
+ "\"/sys/devices/system/memory/\"\n");
+ }
return NULL;
}
--
1.9.1
next prev parent reply other threads:[~2015-10-19 23:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 23:38 [Qemu-devel] [PULL v4 00/14] qemu-ga patch queue Michael Roth
2015-10-19 23:38 ` [Qemu-devel] [PULL v4 01/14] build: qemu-ga: add 'qemu-ga' build target for w32 Michael Roth
2015-10-19 23:38 ` [Qemu-devel] [PULL v4 02/14] qga: Use g_new() & friends where that makes obvious sense Michael Roth
2015-10-19 23:38 ` [Qemu-devel] [PULL v4 03/14] qga: add QGA_CONF environment variable Michael Roth
2015-10-19 23:38 ` [Qemu-devel] [PULL v4 04/14] qga: do not override configuration verbosity Michael Roth
2015-10-19 23:38 ` [Qemu-devel] [PULL v4 05/14] qtest: add a few fd-level qmp helpers Michael Roth
2015-10-19 23:38 ` [Qemu-devel] [PULL v4 06/14] glib-compat: add 2.38/2.40/2.46 asserts Michael Roth
2015-10-19 23:38 ` Michael Roth [this message]
2015-10-19 23:38 ` [Qemu-devel] [PULL v4 08/14] tests: add a local test for guest agent Michael Roth
2015-10-19 23:38 ` [Qemu-devel] [PULL v4 09/14] qga: drop guest_file_init helper and replace it with static initializers Michael Roth
2015-10-19 23:38 ` [Qemu-devel] [PULL v4 10/14] qga: guest exec functionality Michael Roth
2015-10-19 23:38 ` [Qemu-devel] [PULL v4 11/14] qga: handle possible SIGPIPE in guest-file-write Michael Roth
2015-10-19 23:38 ` [Qemu-devel] [PULL v4 12/14] qga: handle G_IO_STATUS_AGAIN in ga_channel_write_all() Michael Roth
2015-10-19 23:38 ` [Qemu-devel] [PULL v4 13/14] qga: guest-exec simple stdin/stdout/stderr redirection Michael Roth
2015-10-19 23:38 ` [Qemu-devel] [PULL v4 14/14] qga: fix uninitialized value warning for win32 Michael Roth
2015-10-20 9:52 ` [Qemu-devel] [PULL v4 00/14] qemu-ga patch queue Peter Maydell
2015-10-20 11:55 ` Peter Maydell
2015-10-20 15:27 ` Michael Roth
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=1445297899-20527-8-git-send-email-mdroth@linux.vnet.ibm.com \
--to=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--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).