From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: speeding up thread-creation
Date: Fri, 21 Nov 2003 18:31:06 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106943948323107@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106940282522654@msgid-missing>
>>>>> On Fri, 21 Nov 2003 09:22:17 -0800, Stephane Eranian <eranian@hpl.hp.com> said:
Stephane> I assume you want to rely on the thread's flags to
Stephane> determine if it is worth copying the thread_lazy structure
Stephane> during a clone.
Yup. I'd say "necessary" instead of "worth" though. Also, we know
that the fph partition never needs to be copied (it contains scratch
registers only).
Stephane> For perfmon, we may need to have two flags: one that says
Stephane> we are storing information in pmds/pmcs and one that says
Stephane> we need to context switch the PMU state. Today PM_VALID
Stephane> flag is used to mean the latter only.
I think that would be fine. In what cases would you want to clone the
PMU state when PM_VALID is false?
--david
prev parent reply other threads:[~2003-11-21 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 8:19 speeding up thread-creation David Mosberger
2003-11-21 17:22 ` Stephane Eranian
2003-11-21 18:31 ` David Mosberger [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=marc-linux-ia64-106943948323107@msgid-missing \
--to=davidm@napali.hpl.hp.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