From: Hemant Kumar <hemant@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, acme@kernel.org, mingo@kernel.org,
mpe@ellerman.id.au, sukadev@linux.vnet.ibm.com,
maddy@linux.vnet.ibm.com, warrier@linux.vnet.ibm.com,
srikar@linux.vnet.ibm.com, paulus@samba.org,
scottwood@freescale.com, Hemant Kumar <hemant@linux.vnet.ibm.com>
Subject: [PATCH RESEND v4 2/3] kvm/powerpc: Add exit reason for return code 0x0
Date: Mon, 15 Jun 2015 10:26:08 +0530 [thread overview]
Message-ID: <1434344169-32438-2-git-send-email-hemant@linux.vnet.ibm.com> (raw)
In-Reply-To: <1434344169-32438-1-git-send-email-hemant@linux.vnet.ibm.com>
This patch adds an exit reason "RETURN_TO_HOST" for the return code
0x0. Note that this is not related to any interrupt vector address, but
this is added just to make sure that perf doesn't complain if and when a
kvm exit happens with a trap code as 0x0.
Signed-off-by: Hemant Kumar <hemant@linux.vnet.ibm.com>
---
arch/powerpc/include/uapi/asm/trace_book3s.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/powerpc/include/uapi/asm/trace_book3s.h b/arch/powerpc/include/uapi/asm/trace_book3s.h
index f647ce0..8635005 100644
--- a/arch/powerpc/include/uapi/asm/trace_book3s.h
+++ b/arch/powerpc/include/uapi/asm/trace_book3s.h
@@ -6,6 +6,7 @@
*/
#define kvm_trace_symbol_exit \
+ {0x0, "RETURN_TO_HOST"}, \
{0x100, "SYSTEM_RESET"}, \
{0x200, "MACHINE_CHECK"}, \
{0x300, "DATA_STORAGE"}, \
--
1.9.3
next prev parent reply other threads:[~2015-06-15 4:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 4:56 [PATCH RESEND v4 1/3] kvm/powerpc: Export kvm exit reasons Hemant Kumar
2015-06-15 4:56 ` Hemant Kumar [this message]
2015-06-15 4:56 ` [PATCH RESEND v4 3/3] kvm/powerpc: Export HCALL reason codes Hemant Kumar
2015-06-15 5:37 ` Paul Mackerras
2015-06-15 5:39 ` [PATCH RESEND v4 1/3] kvm/powerpc: Export kvm exit reasons Paul Mackerras
2015-06-16 3:28 ` Hemant Kumar
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=1434344169-32438-2-git-send-email-hemant@linux.vnet.ibm.com \
--to=hemant@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=sukadev@linux.vnet.ibm.com \
--cc=warrier@linux.vnet.ibm.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 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).