linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hemant Kumar <hemant@linux.vnet.ibm.com>
To: Paul Mackerras <paulus@samba.org>
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: Tue, 16 Jun 2015 08:58:07 +0530	[thread overview]
Message-ID: <557F97C7.1090100@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150615053943.GB15637@pale.ozlabs.ibm.com>

Hi Paul,

On 06/15/2015 11:09 AM, Paul Mackerras wrote:
> 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.
>

The exit reasons are needed in the perf userspace and we wanted to avoid
code duplication, so, if there are any changes, we won't need to update them
at both places.
However, we could add them to perf userspace itself separately and let perf
userspace use those.

What would you suggest?

-- 
Thanks,
Hemant Kumar

      reply	other threads:[~2015-06-16  3:29 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 ` [PATCH RESEND v4 1/3] kvm/powerpc: Export kvm exit reasons Paul Mackerras
2015-06-16  3:28   ` Hemant Kumar [this message]

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=557F97C7.1090100@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).