linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Bill Huey (hui)" <bill.huey@gmail.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Steven Rostedt <rostedt@goodmis.org>,
	Alessandro Zummo <a.zummo@towertech.it>,
	linux-kernel@vger.kernel.org
Cc: luca abeni <luca.abeni@unitn.it>, Juri Lelli <juri.lelli@arm.com>,
	Mike Galbraith <umgwanakikbuti@gmail.com>,
	Dario Faggioli <raistlin@linux.it>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH RFC v1 05/12] Task tracking per file descriptor
Date: Wed, 13 Apr 2016 23:47:52 -0700	[thread overview]
Message-ID: <1460616479-32258-6-git-send-email-bill.huey@gmail.com> (raw)
In-Reply-To: <1460616479-32258-1-git-send-email-bill.huey@gmail.com>

Task tracking per file descriptor for thread death clean up.

Signed-off-by: Bill Huey (hui) <bill.huey@gmail.com>
---
 drivers/rtc/class.c | 3 +++
 include/linux/rtc.h | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/drivers/rtc/class.c b/drivers/rtc/class.c
index 74fd974..ad570b9 100644
--- a/drivers/rtc/class.c
+++ b/drivers/rtc/class.c
@@ -201,6 +201,9 @@ struct rtc_device *rtc_device_register(const char *name, struct device *dev,
 	rtc->irq_freq = 1;
 	rtc->max_user_freq = 64;
 	rtc->dev.parent = dev;
+#ifdef CONFIG_RTC_CYCLIC
+	INIT_LIST_HEAD(&rtc->rt_overrun_tasks); //struct list_head
+#endif
 	rtc->dev.class = rtc_class;
 	rtc->dev.groups = rtc_get_dev_attribute_groups();
 	rtc->dev.release = rtc_device_release;
diff --git a/include/linux/rtc.h b/include/linux/rtc.h
index b693ada..1424550 100644
--- a/include/linux/rtc.h
+++ b/include/linux/rtc.h
@@ -114,6 +114,9 @@ struct rtc_timer {
 struct rtc_device {
 	struct device dev;
 	struct module *owner;
+#ifdef CONFIG_RTC_CYCLIC
+	struct list_head rt_overrun_tasks;
+#endif
 
 	int id;
 	char name[RTC_DEVICE_NAME_SIZE];
-- 
2.5.0

  parent reply	other threads:[~2016-04-14  6:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-14  6:47 [PATCH RFC v1 00/12] Cyclic Scheduler Against RTC Bill Huey (hui)
2016-04-14  6:47 ` [PATCH RFC v1 01/12] Kconfig change Bill Huey (hui)
2016-04-14  6:47 ` [PATCH RFC v1 02/12] Reroute rtc update irqs to the cyclic scheduler handler Bill Huey (hui)
2016-04-14  6:47 ` [PATCH RFC v1 03/12] Add cyclic support to rtc-dev.c Bill Huey (hui)
2016-04-14  6:47 ` [PATCH RFC v1 04/12] Anonymous struct initialization Bill Huey (hui)
2016-04-14  6:47 ` Bill Huey (hui) [this message]
2016-04-14  6:47 ` [PATCH RFC v1 06/12] Add anonymous struct to sched_rt_entity Bill Huey (hui)
2016-04-14  6:47 ` [PATCH RFC v1 07/12] kernel/userspace additions for addition ioctl() support for rtc Bill Huey (hui)
2016-04-14  6:47 ` [PATCH RFC v1 08/12] Compilation support Bill Huey (hui)
2016-04-14  6:47 ` [PATCH RFC v1 09/12] Add priority support for the cyclic scheduler Bill Huey (hui)
2016-04-14  6:47 ` [PATCH RFC v1 10/12] Export SCHED_FIFO/RT requeuing functions Bill Huey (hui)
2016-04-14  6:47 ` [PATCH RFC v1 11/12] Cyclic scheduler support Bill Huey (hui)
2016-04-14  6:47 ` [PATCH RFC v1 12/12] Cyclic/rtc documentation Bill Huey (hui)

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=1460616479-32258-6-git-send-email-bill.huey@gmail.com \
    --to=bill.huey@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=a.zummo@towertech.it \
    --cc=juri.lelli@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.abeni@unitn.it \
    --cc=raistlin@linux.it \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=umgwanakikbuti@gmail.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;
as well as URLs for NNTP newsgroup(s).