linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Madhavan Srinivasan <maddy@linux.ibm.com>
To: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>, mpe@ellerman.id.au
Cc: atrajeev@linux.vnet.ibm.com, kjain@linux.ibm.com,
	npiggin@gmail.com, christophe.leroy@csgroup.eu,
	naveen.n.rao@linux.ibm.com, disgoel@linux.vnet.ibm.com,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 3/3] powerpc: Document details on H_HTM hcall
Date: Wed, 26 Jun 2024 09:25:13 +0530	[thread overview]
Message-ID: <e3433830-d9a9-43cc-8440-5fb5ee996a55@linux.ibm.com> (raw)
In-Reply-To: <87le2x5qmv.fsf@gmail.com>


On 6/22/24 1:57 PM, Ritesh Harjani (IBM) wrote:
> Madhavan Srinivasan <maddy@linux.ibm.com> writes:
>
>> Add documentation to 'papr_hcalls.rst' describing the
>> input, output and return values of the H_HTM hcall as
>> per the internal specification.
>>
>> Signed-off-by: Madhavan Srinivasan <maddy@linux.ibm.com>
>> ---
>>   Documentation/arch/powerpc/papr_hcalls.rst | 11 +++++++++++
>>   1 file changed, 11 insertions(+)
>>
>> diff --git a/Documentation/arch/powerpc/papr_hcalls.rst b/Documentation/arch/powerpc/papr_hcalls.rst
>> index 80d2c0aadab5..805e1cb9bab9 100644
>> --- a/Documentation/arch/powerpc/papr_hcalls.rst
>> +++ b/Documentation/arch/powerpc/papr_hcalls.rst
>> @@ -289,6 +289,17 @@ to be issued multiple times in order to be completely serviced. The
>>   subsequent hcalls to the hypervisor until the hcall is completely serviced
>>   at which point H_SUCCESS or other error is returned by the hypervisor.
>>   
>> +**H_HTM**
>> +
>> +| Input: flags, target, operation (op), op-param1, op-param2, op-param3
>> +| Out: *dumphtmbufferdata*
>> +| Return Value: *H_Success,H_Busy,H_LongBusyOrder,H_Partial,H_Parameter,
>> +		 H_P2,H_P3,H_P4,H_P5,H_P6,H_State,H_Not_Available,H_Authority*
>> +
>> +H_HTM supports setup, configuration, control and dumping of Hardware Trace
>> +Macro (HTM) function and its data. HTM buffer stores tracing data for functions
>> +like core instruction, core LLAT and nest.
>> +
> Minor nit: Maybe the set of debugfs cmds to collect the trace and some
> example trace log? If it is not confidential?

I could add the file structure in the commit message, but logs are just 
binary data.

Maddy

>
>>   References
>>   ==========
>>   .. [1] "Power Architecture Platform Reference"
>> -- 
>> 2.45.2

      reply	other threads:[~2024-06-26  3:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-20 17:46 [PATCH 1/3] powerpc/pseries: Macros and wrapper functions for H_HTM call Madhavan Srinivasan
2024-06-20 17:46 ` [PATCH 2/3] powerpc/pseries: Export hardware trace macro dump via debugfs Madhavan Srinivasan
2024-06-22  7:40   ` Ritesh Harjani
2024-06-26  3:51     ` Madhavan Srinivasan
2024-06-26  8:12     ` Michael Ellerman
2024-06-26  0:58   ` kernel test robot
2024-06-20 17:46 ` [PATCH 3/3] powerpc: Document details on H_HTM hcall Madhavan Srinivasan
2024-06-22  8:27   ` Ritesh Harjani
2024-06-26  3:55     ` Madhavan Srinivasan [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=e3433830-d9a9-43cc-8440-5fb5ee996a55@linux.ibm.com \
    --to=maddy@linux.ibm.com \
    --cc=atrajeev@linux.vnet.ibm.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=disgoel@linux.vnet.ibm.com \
    --cc=kjain@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=naveen.n.rao@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=ritesh.list@gmail.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).