public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alexander van Heukelum" <heukelum@fastmail.fm>
To: "Ingo Molnar" <mingo@elte.hu>, "lkml" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/7] traps: x86_64: add TRACE_IRQS_OFF in error_entry
Date: Fri, 26 Sep 2008 14:39:11 +0200	[thread overview]
Message-ID: <1222432751.13247.1276111293@webmail.messagingengine.com> (raw)
In-Reply-To: <1222430588-29072-2-git-send-email-heukelum@fastmail.fm>


On Fri, 26 Sep 2008 14:03:02 +0200, "Alexander van Heukelum"
<heukelum@fastmail.fm> said:
> Add TRACE_IRQS_OFF just before entering the C code.
> 
> All exceptions are taken via interrupt gates. If irq tracing is
> enabled, it should be notified as soon as possible. Interrupts
> are only (conditionally) re-enabled in C code.
> 
> Signed-off-by: Alexander van Heukelum <fastmail.fm>

That should be: <heukelum@fastmail.fm> ---^^^
Same for patch 2/7. How did that happen?

> ---
>  arch/x86/kernel/entry_64.S |    3 ++-
>  1 files changed, 2 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/x86/kernel/entry_64.S b/arch/x86/kernel/entry_64.S
> index 89434d4..78fa552 100644
> --- a/arch/x86/kernel/entry_64.S
> +++ b/arch/x86/kernel/entry_64.S
> @@ -1058,7 +1058,8 @@ KPROBE_ENTRY(error_entry)
>  	je  error_kernelspace
>  error_swapgs:	
>  	SWAPGS
> -error_sti:	
> +error_sti:
> +	TRACE_IRQS_OFF
>  	movq %rdi,RDI(%rsp) 	
>  	CFI_REL_OFFSET	rdi,RDI
>  	movq %rsp,%rdi
> -- 
> 1.5.4.3
> 
-- 
  Alexander van Heukelum
  heukelum@fastmail.fm

-- 
http://www.fastmail.fm - Or how I learned to stop worrying and
                          love email again


  parent reply	other threads:[~2008-09-26 12:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-26 12:03 [PATCH 0/7] traps: x86: irqtrace cleanup and some traps.c unification Alexander van Heukelum
2008-09-26 12:03 ` [PATCH 1/7] traps: x86_64: add TRACE_IRQS_OFF in error_entry Alexander van Heukelum
2008-09-26 12:03   ` [PATCH 2/7] traps: x86_64: add TRACE_IRQS_OFF in paranoidentry macro Alexander van Heukelum
2008-09-26 12:03     ` [PATCH 3/7] traps: x86_64: remove trace_hardirqs_fixup from DO_ERROR_INFO macro Alexander van Heukelum
2008-09-26 12:03       ` [PATCH 4/7] traps: x86_64: remove trace_hardirqs_fixup from int3 handler Alexander van Heukelum
2008-09-26 12:03         ` [PATCH 5/7] traps: x86_64: remove trace_hardirqs_fixup from debug handler Alexander van Heukelum
2008-09-26 12:03           ` [PATCH 6/7] traps: x86: remove trace_hardirqs_fixup from pagefault handler Alexander van Heukelum
2008-09-26 12:03             ` [PATCH 7/7] traps: i386: make do_trap more like x86_64 Alexander van Heukelum
2008-09-26 12:39   ` Alexander van Heukelum [this message]
2008-09-27 16:30 ` [PATCH 0/7] traps: x86: irqtrace cleanup and some traps.c unification Ingo Molnar

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=1222432751.13247.1276111293@webmail.messagingengine.com \
    --to=heukelum@fastmail.fm \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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