mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeremy Linton <jeremy.linton@arm.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Juergen Gross <jgross@suse.com>,
	"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: Re: [PATCH] tracing/xen: Hide events that are not used when X86_PAE is not defined
Date: Wed, 11 Oct 2017 19:39:20 -0500	[thread overview]
Message-ID: <bf4f50a7-4d31-ebdf-f946-ab3e61e59c8e@arm.com> (raw)
In-Reply-To: <20171010191256.3d6d72cb@gandalf.local.home>

On 10/10/2017 06:12 PM, Steven Rostedt wrote:
> From: Steven Rostedt (VMware) <rostedt@goodmis.org>
> 
> TRACE_EVENTS() take up memory. If they are defined but not used, then
> they simply waste space. If their use case is behind a define, then the
> trace events should be as well.
> 
> The trace events xen_mmu_set_pte_atomic, xen_mmu_pte_clear, and
> xen_mmu_pmd_clear are not used when CONFIG_X86_PAE is not defined.

The only place i see them being used is mmu_pv.c, where they are wrapped 
in the stated #define.

Looks good.

Reviewed-by: Jeremy Linton <jeremy.linton@arm.com>

Thanks,

> 
> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> ---
> Index: linux-trace.git/include/trace/events/xen.h
> ===================================================================
> --- linux-trace.git.orig/include/trace/events/xen.h
> +++ linux-trace.git/include/trace/events/xen.h
> @@ -147,7 +147,6 @@ DECLARE_EVENT_CLASS(xen_mmu__set_pte,
>   		     TP_ARGS(ptep, pteval))
>   
>   DEFINE_XEN_MMU_SET_PTE(xen_mmu_set_pte);
> -DEFINE_XEN_MMU_SET_PTE(xen_mmu_set_pte_atomic);
>   
>   TRACE_EVENT(xen_mmu_set_pte_at,
>   	    TP_PROTO(struct mm_struct *mm, unsigned long addr,
> @@ -169,21 +168,6 @@ TRACE_EVENT(xen_mmu_set_pte_at,
>   		      (int)sizeof(pteval_t) * 2, (unsigned long long)__entry->pteval)
>   	);
>   
> -TRACE_EVENT(xen_mmu_pte_clear,
> -	    TP_PROTO(struct mm_struct *mm, unsigned long addr, pte_t *ptep),
> -	    TP_ARGS(mm, addr, ptep),
> -	    TP_STRUCT__entry(
> -		    __field(struct mm_struct *, mm)
> -		    __field(unsigned long, addr)
> -		    __field(pte_t *, ptep)
> -		    ),
> -	    TP_fast_assign(__entry->mm = mm;
> -			   __entry->addr = addr;
> -			   __entry->ptep = ptep),
> -	    TP_printk("mm %p addr %lx ptep %p",
> -		      __entry->mm, __entry->addr, __entry->ptep)
> -	);
> -
>   TRACE_DEFINE_SIZEOF(pmdval_t);
>   
>   TRACE_EVENT(xen_mmu_set_pmd,
> @@ -201,6 +185,24 @@ TRACE_EVENT(xen_mmu_set_pmd,
>   		      (int)sizeof(pmdval_t) * 2, (unsigned long long)__entry->pmdval)
>   	);
>   
> +#ifdef CONFIG_X86_PAE
> +DEFINE_XEN_MMU_SET_PTE(xen_mmu_set_pte_atomic);
> +
> +TRACE_EVENT(xen_mmu_pte_clear,
> +	    TP_PROTO(struct mm_struct *mm, unsigned long addr, pte_t *ptep),
> +	    TP_ARGS(mm, addr, ptep),
> +	    TP_STRUCT__entry(
> +		    __field(struct mm_struct *, mm)
> +		    __field(unsigned long, addr)
> +		    __field(pte_t *, ptep)
> +		    ),
> +	    TP_fast_assign(__entry->mm = mm;
> +			   __entry->addr = addr;
> +			   __entry->ptep = ptep),
> +	    TP_printk("mm %p addr %lx ptep %p",
> +		      __entry->mm, __entry->addr, __entry->ptep)
> +	);
> +
>   TRACE_EVENT(xen_mmu_pmd_clear,
>   	    TP_PROTO(pmd_t *pmdp),
>   	    TP_ARGS(pmdp),
> @@ -210,6 +212,7 @@ TRACE_EVENT(xen_mmu_pmd_clear,
>   	    TP_fast_assign(__entry->pmdp = pmdp),
>   	    TP_printk("pmdp %p", __entry->pmdp)
>   	);
> +#endif
>   
>   #if CONFIG_PGTABLE_LEVELS >= 4
>   
> 

  parent reply	other threads:[~2017-10-12  0:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 23:12 Steven Rostedt
2017-10-10 23:25 ` Boris Ostrovsky
2017-10-12  1:05   ` Steven Rostedt
2017-10-12  0:39 ` Jeremy Linton [this message]
2017-10-12  1:05   ` Steven Rostedt

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=bf4f50a7-4d31-ebdf-f946-ab3e61e59c8e@arm.com \
    --to=jeremy.linton@arm.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.org \
    /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

all inboxes | Powered by JetHome®