From: "stephane eranian" <eranian@googlemail.com>
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 16:18:20 +0000 [thread overview]
Message-ID: <7c86c4470712120818k37f55cfavafe6cf6ede0c0684@mail.gmail.com> (raw)
In-Reply-To: <1196959881.6586.6.camel@elijah.suse.cz>
Petr,
On Dec 12, 2007 12:07 PM, Petr Tesarik <ptesarik@suse.cz> wrote:
>
> 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).
>
Yes. The TIF flag has the advantage of being in the same cacheline.
> 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...
>
Yes, I ran into that difficulty myself when I tried adding my TIF flag.
Not sure how you could work around it.
> Anyway, I'd like to push the changes to ptrace first, because that's
> currently broken.
That's fine. What you have right now show work.
thanks.
prev parent reply other threads:[~2007-12-12 16:18 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
2007-12-12 14:21 ` Petr Tesarik
2007-12-12 16:18 ` stephane eranian [this message]
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=7c86c4470712120818k37f55cfavafe6cf6ede0c0684@mail.gmail.com \
--to=eranian@googlemail.com \
--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