All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] [POWERPC] Rework EXC_LEVEL_EXCEPTION_PROLOG code
Date: Thu, 01 May 2008 14:02:55 -0500	[thread overview]
Message-ID: <481A13DF.3000405@freescale.com> (raw)
In-Reply-To: <17325743-606C-4B3D-88C0-2D0B7902B4E1@kernel.crashing.org>

Kumar Gala wrote:
> copying the flags isn't the issue.  Its acting on the flags thats the 
> problem.  I'm not 100% sure the C code that might clear the flags is 
> consistent on how it access them.  

Actually *delivering* the signal should never be done except when 
returning to user.  That's different from sending the signal, though.

BTW, it doesn't seem all that unreasonable for a kernel 
profiling/tracing exception to signal a process that, for example, an 
event buffer is over a certain threshold.

 > So if one bit of code clears
 > task_struct->stack->thread_info->flags and other clears
 > thread_info(STACK)->flags we get into an issue on how to merge after
 > that.

It appears that TIF_SIGPENDING is always accessed through the task 
struct, though not so for TIF_NEED_RESCHED.

-Scott

  reply	other threads:[~2008-05-01 19:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30  9:27 [PATCH] [POWERPC] Rework EXC_LEVEL_EXCEPTION_PROLOG code Kumar Gala
2008-04-30 21:54 ` Benjamin Herrenschmidt
2008-04-30 22:13   ` Kumar Gala
2008-04-30 22:18     ` Benjamin Herrenschmidt
2008-04-30 23:24       ` Kumar Gala
2008-04-30 22:22     ` Benjamin Herrenschmidt
2008-04-30 23:28       ` Kumar Gala
2008-04-30 23:52         ` Benjamin Herrenschmidt
2008-04-30 23:47     ` Paul Mackerras
2008-05-01  6:01       ` Kumar Gala
2008-05-01  7:53         ` Benjamin Herrenschmidt
2008-05-01 13:22           ` Kumar Gala
2008-05-01 14:26             ` Josh Boyer
2008-05-01 14:31               ` Kumar Gala
2008-05-05 11:57             ` Gabriel Paubert
2008-05-05 12:06               ` Benjamin Herrenschmidt
2008-05-01  8:24         ` Paul Mackerras
2008-05-01 13:17           ` Kumar Gala
2008-05-01 16:14             ` Scott Wood
2008-05-01 16:22               ` Scott Wood
2008-05-01 16:33               ` Kumar Gala
2008-05-01 16:42                 ` Scott Wood
2008-05-01 17:48                   ` Kumar Gala
2008-05-01 19:02                     ` Scott Wood [this message]
2008-05-01 23:34             ` Paul Mackerras
2008-05-02  4:02               ` Kumar Gala

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=481A13DF.3000405@freescale.com \
    --to=scottwood@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.