From: Mandeep Singh Baines <msb@google.com>
To: mingo@elte.hu, linux-kernel@vger.kernel.org
Cc: hannes@cmpxchg.org, rientjes@google.com, mbligh@google.com,
thockin@google.com
Subject: [PATCH] softlockup: fix to allow compiling with !DETECT_HUNG_TASK
Date: Fri, 16 Jan 2009 09:09:38 -0800 [thread overview]
Message-ID: <20090116170938.GA11346@google.com> (raw)
Ingo Molnar (mingo@elte.hu) wrote:
>
> doesnt build with !SOFTLOCKUP:
>
> kernel/fork.c:1049: error: 'struct task_struct' has no member named 'last_switch_count'
> kernel/fork.c:1050: error: 'struct task_struct' has no member named 'last_switch_timestamp'
>
> Could you send a delta fix patch relative to -v4 please? Thanks,
>
> Ingo
Oops. Will be more careful next time.
---
Fixes the following compile error:
kernel/fork.c:1049: error: 'struct task_struct' has no member named 'last_switch_count'
kernel/fork.c:1050: error: 'struct task_struct' has no member named 'last_switch_timestamp'
Signed-off-by: Mandeep Singh Baines <msb@google.com>
---
kernel/fork.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/fork.c b/kernel/fork.c
index fb1f5e9..d68e59b 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -1045,7 +1045,7 @@ static struct task_struct *copy_process(unsigned long clone_flags,
p->default_timer_slack_ns = current->timer_slack_ns;
-#ifdef CONFIG_DETECT_SOFTLOCKUP
+#ifdef CONFIG_DETECT_HUNG_TASK
p->last_switch_count = 0;
p->last_switch_timestamp = 0;
#endif
--
1.5.4.5
next reply other threads:[~2009-01-16 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 17:09 Mandeep Singh Baines [this message]
2009-01-16 17:18 ` [PATCH] softlockup: fix to allow compiling with !DETECT_HUNG_TASK Ingo Molnar
2009-01-17 18:31 ` [PATCH] softlockup: fix potential race in hung_task when resetting timeout Mandeep Singh Baines
2009-01-18 18:22 ` Ingo Molnar
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=20090116170938.GA11346@google.com \
--to=msb@google.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=rientjes@google.com \
--cc=thockin@google.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