From: Andre Przywara <andre.przywara@amd.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
George Dunlap <george.dunlap@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH] libxc: fix tracing (broken with hypercall buffers)
Date: Tue, 16 Nov 2010 12:28:26 +0100 [thread overview]
Message-ID: <4CE26ADA.5080309@amd.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 359 bytes --]
Hi,
the attached patch makes Xen tracing work again, after the introduction
of the hypercall buffers broke it. Just a missing line.
Thanks to Uwe Dannowski for reporting this.
Signed-off-by: Andre Przywara <andre.przywara@amd.com>
Regards,
Andre.
--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448-3567-12
[-- Attachment #2: libxc_fix_tracing_hypercall_buffers.patch --]
[-- Type: text/x-patch, Size: 417 bytes --]
diff -r 87f248de5230 tools/libxc/xc_tbuf.c
--- a/tools/libxc/xc_tbuf.c Mon Nov 15 09:31:38 2010 +0000
+++ b/tools/libxc/xc_tbuf.c Tue Nov 16 10:11:39 2010 +0100
@@ -121,6 +121,7 @@
uint64_t mask64 = mask;
bytemap = xc_hypercall_buffer_alloc(xch, bytemap, sizeof(mask64));
+ if (bytemap == NULL)
{
PERROR("Could not allocate memory for xc_tbuf_set_cpu_mask hypercall");
goto out;
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2010-11-16 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 11:28 Andre Przywara [this message]
2010-11-16 11:34 ` [PATCH] libxc: fix tracing (broken with hypercall buffers) Ian Campbell
2010-11-19 18:21 ` [PATCH] libxc: fix tracing (broken with hypercall buffers) [and 1 more messages] Ian Jackson
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=4CE26ADA.5080309@amd.com \
--to=andre.przywara@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.