From: Davide Libenzi <davidel@xmailserver.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Arjan van de Ven <arjan@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@zip.com.au>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Ulrich Drepper <drepper@redhat.com>,
Zach Brown <zach.brown@oracle.com>,
Evgeniy Polyakov <johnpol@2ka.mipt.ru>,
"David S. Miller" <davem@davemloft.net>,
Suparna Bhattacharya <suparna@in.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [patch 05/14] syslets: core code
Date: Fri, 16 Feb 2007 16:52:04 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0702161647090.14869@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <20070215165228.GF4285@elte.hu>
On Thu, 15 Feb 2007, Ingo Molnar wrote:
> + spin_lock(&ah->lock);
> +
> + new_async_thread = pick_ready_cachemiss_thread(ah);
> + if (!new_async_thread)
> + goto out_unlock;
> +
> + async_ready = t->async_ready;
> + WARN_ON(!async_ready);
> + t->async_ready = NULL;
> +
> + new_task = new_async_thread->task;
> +
> + move_user_context(new_task, t);
Since I lost the email where you were describing the todo list, I'll hook
into this one.
I haven't seen you mentioning it, but at least TID and signal handling
need to be swapped to. So it'd be better to have a generic
move_user_context() that does system independent work, and an
arch_move_user_context() that takes care of system dependent stuff (that
is called by move_user_context()).
- Davide
prev parent reply other threads:[~2007-02-17 0:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 16:52 Ingo Molnar
2007-02-15 17:46 ` Zach Brown
2007-02-16 18:28 ` Frederik Deweerdt
2007-02-17 0:52 ` Davide Libenzi [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=Pine.LNX.4.64.0702161647090.14869@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=drepper@redhat.com \
--cc=hch@infradead.org \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=suparna@in.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=zach.brown@oracle.com \
/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
all inboxes | Powered by JetHome®