From: Zhang Le <robert@thizgroup.com>
To: liyu <liyu@ccoss.com.cn>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Question] I doublt on spin_lock again.
Date: Wed, 23 Nov 2005 10:51:22 +0800 [thread overview]
Message-ID: <4383D92A.9070409@thizgroup.com> (raw)
In-Reply-To: <4383CE48.60007@ccoss.com.cn>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
liyu wrote:
| 1. I found these use spin_lock(&rq->lock) in set_user_nice(), but
| not disable interrput ( e.g. when sys_nice() call it ), if the
| one timer interrput come before we unlock the spin_lock, Shall we
| dead lock here? Since the scheduler_tick() may try to hold the
| same lock.
set_user_nice() -> task_rq_lock -> local_irq_save()
|
| 2. # define __acquires(x) __attribute__((context(0,1))) # define
| __releases(x) __attribute__((context(1,0))) # define
| __acquire(x) __context__(1) # define __release(x)
| __context__(-1)
info gcc
BTW, have you ever read "HOWTO do Linux kernel development" be Greg?
Do it, if you haven't
- --
Zhang Le, Robert
Linux Engineer/Trainer
ThizLinux Laboratory Limited
Address: Unit 1004, 10/F, Tower B,
Hunghom Commercial Centre, 37 Ma Tau Wai Road,
To Kwa Wan, Kowloon, Hong Kong
Telephone: (852) 2735 2725
Mobile:(852) 9845 4336
Fax: (852) 2111 0702
URL: http://www.thizgroup.com
Public key: gpg --keyserver pgp.mit.edu --recv-keys 1E4E2973
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFDg9kOvFHICB5OKXMRAg7BAJwIhyW9Qop4YGF9G56nzqImjy8UgQCfUE/g
b8pK2Fk6oW8ScK42krTZdOQ=
=mDfg
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-11-23 2:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 2:04 [Question] I doublt on spin_lock again liyu
2005-11-23 2:51 ` Zhang Le [this message]
2005-11-23 2:56 ` liyu
2005-11-23 4:09 ` Zhang Le
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=4383D92A.9070409@thizgroup.com \
--to=robert@thizgroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liyu@ccoss.com.cn \
/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