public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Tesarik <ptesarik@suse.cz>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 1/3] Rename TIF_PERFMON_WORK back to TIF_NOTIFY_RESUME
Date: Wed, 12 Dec 2007 11:07:37 +0000	[thread overview]
Message-ID: <475FC0F9.80605@suse.cz> (raw)
In-Reply-To: <1196959881.6586.6.camel@elijah.suse.cz>

Stephane Eranian wrote:
> Hello,
> 
> On Thu, Dec 06, 2007 at 05:51:21PM +0100, Petr Tesarik wrote:
>> The RSE synchronization will need a TIF_ flag, but all work-to-be-done
>> bits are already used, so we'll have to multiplex TIF_NOTIFY_RESUME
>> again.
>>
> 
> Yes, I knew this was coming. I think it is okay to multiplex on
> TIF_NOITFY_RESUME. However, I think it would be cleaner and likely
> more efficient to add yet another TIF flags for perfmon instead of
> adding the pfm_needs_checking field. That new TIF flag would not have
> to be in the low 7 bits. It could be higher because it would not be
> checked by the assembly code but rather in do_notify_resume_user().
> The TIF limitation is just in the assembly code.
> 
> Any comments?

I'm making a mental note to review this later for optimization. AFAICS
fetching the pfm_needs_checking field is not too costly, but of course
it's an extra memory reference (and possibly a cache miss).

On a related note, I think that we should be able to use all 8 bits for
pending work TIF_ bits despite the brain-damaged sign extension in "and
imm8", but I don't have the time now to go through all uses of the
thread flags in assembly. Not really sure if it's worth adding one TIF_
bit, because we'll pretty certainly need one more bit in the future...

Anyway, I'd like to push the changes to ptrace first, because that's
currently broken.

Kind regards,
Petr Tesarik

  parent reply	other threads:[~2007-12-12 11:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-06 16:51 [PATCH 1/3] Rename TIF_PERFMON_WORK back to TIF_NOTIFY_RESUME Petr Tesarik
2007-12-06 17:15 ` Stephane Eranian
2007-12-12 11:07 ` Petr Tesarik [this message]
2007-12-12 14:21 ` Petr Tesarik
2007-12-12 16:18 ` stephane eranian

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=475FC0F9.80605@suse.cz \
    --to=ptesarik@suse.cz \
    --cc=linux-ia64@vger.kernel.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