linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Hemant Kumar <hemant@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, 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,
	scottwood@freescale.com
Subject: Re: [PATCH RESEND v4 1/3] kvm/powerpc: Export kvm exit reasons
Date: Mon, 15 Jun 2015 15:39:43 +1000	[thread overview]
Message-ID: <20150615053943.GB15637@pale.ozlabs.ibm.com> (raw)
In-Reply-To: <1434344169-32438-1-git-send-email-hemant@linux.vnet.ibm.com>

On Mon, Jun 15, 2015 at 10:26:07AM +0530, Hemant Kumar wrote:
> To analyze the kvm exits with perf, we will need to map the exit codes
> with the exit reasons. Such a mapping exists today in trace_book3s.h.
> Currently its not exported to perf.
> 
> This patch moves these kvm exit reasons and their mapping from
> "arch/powerpc/kvm/trace_book3s.h" to
> "arch/powerpc/include/uapi/asm/trace_book3s.h".
> Accordingly change the include files in "trace_hv.h" and "trace_pr.h".

These are not really exit reasons so much as Power ISA interrupt
vectors, defined externally to the kernel (in the Power ISA document)
and not subject to change (at least, kernel developers can't change
them).  So I don't see why this needs to be "exported" from the
kernel.

Paul.

  parent reply	other threads:[~2015-06-15  5:40 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 ` [PATCH RESEND v4 2/3] kvm/powerpc: Add exit reason for return code 0x0 Hemant Kumar
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 ` Paul Mackerras [this message]
2015-06-16  3:28   ` [PATCH RESEND v4 1/3] kvm/powerpc: Export kvm exit reasons 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=20150615053943.GB15637@pale.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=acme@kernel.org \
    --cc=hemant@linux.vnet.ibm.com \
    --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=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).