linux-kernel - Are we still willing to pay the cost of moving include/linux/irqdesc.h into kernel/irq/?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <5559B574.7070402@linux.intel.com>
Date:	Mon, 18 May 2015 17:48:36 +0800
From:	Jiang Liu <jiang.liu@...ux.intel.com>
To:	Thomas Gleixner <tglx@...utronix.de>
CC:	linux-kernel@...r.kernel.org
Subject: Are we still willing to pay the cost of moving include/linux/irqdesc.h
 into kernel/irq/?

Hi Thomas,
	When refining irq related data structures, I found once we had
a plan to move include/linux/irqdesc.h into kernel/irq/, and I have
basic ideas about how to achieve the goal as:
1) de-inline accessor functions in irqdesc.h and move the declaration
   into linux/irq.h.
2) remove reference to irq_desc->xxxx from drivers one by one (this
   step is simple)
3) remove reference to irq_desc->xxxx from arch (this step is hard)
4) move irqdesc.h into kernel/irq/

But are we still willing to pay the cost of converting inline access
helpers into normal functions?
One possible tradeoff is to remove reference of irq_desc->xxxx from
drivers/, which is straight forward and shouldn't cause serious
performance regressions:)

Thanks!
Gerry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/