On Wed, 11 Oct 2017 19:39:20 -0500
Jeremy Linton wrote:
> On 10/10/2017 06:12 PM, Steven Rostedt wrote:
> > From: Steven Rostedt (VMware)
> >
> > 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
> >
On Tue, 10 Oct 2017 19:25:10 -0400
Boris Ostrovsky wrote:
> On 10/10/2017 07:12 PM, Steven Rostedt wrote:
> > From: Steven Rostedt (VMware)
> >
> > 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
>
On 10/10/2017 06:12 PM, Steven Rostedt wrote:
From: Steven Rostedt (VMware)
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
On 10/10/2017 07:12 PM, Steven Rostedt wrote:
> From: Steven Rostedt (VMware)
>
> 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_a
From: Steven Rostedt (VMware)
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 us
5 matches
Mail list logo