DOCSLIB.ORG

Controlling Tracepoints AMD Performance Counting Clearer

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Controlling Tracepoints AMD Performance Counting Clearer PROgRAMMIng Kernel News zack’s kernel news m68k Revitalized Under git Controlling Tracepoints nilfs2 Headed For Inclusion Geert Uytterhoeven announced a new git Steven Rostedt has posted a patch to Ryusuke Konishi has submitted nilfs2 for repository for the m68k Linux port, replac- ftrace, providing a simple interface for inclusion in the main kernel tree. Up to ing a defunct CVS repository. He also users to enable and disable any trace- now, it has lived in Andrew Morton’s posted a patch to add a make install com- point that already exists in the kernel. -mm tree. As Andrew has said, Konishi’s pilation target for the m68k build and The new /debug/tracing/available_ efforts have been quite impressive, and posted several other m68k updates as well. events file lists all tracepoints available he’s offered him some advice for further for tracking, whereas the /debug/tracing/ development. Andrew strongly supports MSI HOWTO Rewrite set_event can be modified to list the the filesystem and plans to send the Matthew Wilcox has rewritten the MSI events you want to enable or disable. patches along to Linus Torvalds in the HOWTO, the first major rewrite since very near future, barring serious objec- 2004. MSI (or Message Signaled Inter- AMD Performance Counting tion from other kernel hackers. nilfs2 rupts) provide PCI devices with an alter- Jaswinder Singh Rajput posted some provides full versioning within the file- native to traditional interrupts that re- patches to implement performance system, including continuous snapshot- quire the existence of a hardware pin on counting for AMD K7 (and later) proces- ting and access to older snapshots. the device. MSI lets the device trigger an sors. The patches count CPU cycles, interrupt simply by writing data to a spe- number of instructions, clock ticks, page From Og cific memory address. Randy Dunlap and faults, context switches, and various I had to include the following email in Sitsofe Wheeler offered some feedback other items. Ingo Molnár was very full: on the prose, and Matthew updated the pleased with these patches and tested Og here. doc because of it. Grant Gundler and Mi- them, offering some bug reports that Jas- Greg run off to big hill with chael Ellerman had more technical feed- winder was quick to respond to. white stuff. back, which they discussed with Mat- He leave corn bits and paper. thew. Ultimately it looks as though this is Clearer KBuild State When a welcome rewrite, with all in favor. Viewing Help Corn bits have many num-bers. Cheng Renquan has made some im- 2 corns. provements to KBuild. The main user- Num-ber on one corn is 2.6.27.19. The Linux kernel visible change is to present the currently Num-ber on one corn is 2.6.28.7. mailing list com- selected value for any given option visi- Paper have 1 wurd. prises the core of ble from that option’s help message. Linux development Randy Dunlap helped him debug some Paper say "Update!" activities. Traffic vol- technical problems but, overall, felt the Og no no what paper meens. umes are immense, features were important additions to Corn only good for wood-chuck. Why often reaching ten KBuild. Greg care about corn? thousand messages Og con-fus-ed. in a given week, and Improving PCI Detection keeping up to date Og done. As part of a broader swath of PCI with the entire scope of development is patches, Alex Chiang has written some Linus Torvalds replied, “I’m happy to see a virtually impossible task for one per- code to create /sys/bus/pci/rescan. Writ- that we have sunk to a whole new level son. One of the few brave souls to take ing a non-zero value to that file will of professionalism. And imagine that on this task is Zack Brown. force a rescan of the PCI buses on the people ever doubted that open-source Our regular monthly column keeps you abreast of the latest discussions and de- system and rediscover any previously re- could ever be mission critical! Ha!” cisions, selected and summarized by moved PCI devices. Alex also wrote Zack. Zack has been publishing a weekly companion code to create /sys/bus/pci/ Official git Repository online digest, the Kernel Traffic news- devices/ ... /rescan, which forces a res- Until now, Linus Torvalds has been letter, for over five years now. Even can of a device’s parent bus and child listed in the MAINTAINERS file as the reading Kernel Traffic alone can be a buses and rediscovers any devices that maintainer of all kernel things not other- time-consuming task. had previously been removed from that wise maintained, but his git repository Linux Magazine now provides you with part of the device tree. He also created / wasn’t listed. Joe Perches recently the quintessence of Linux kernel activi- sys/bus/pci/devices/ ... /remove, which posted a patch adding git://git.kernel. ties, straight from the horse’s mouth. removes the PCI device and any of its org/pub/scm/linux/kernel/git/torvalds/li- children. nux-2.6.git to that entry. 66 ISSUE 103 JUNE 2009 Kernel News PROgRAMMIng What Is Staging? Greg Kroah-Hartman recently offered The value of putting code into staging when executed (i.e., it’ll print a message some clarification on the nature of the is that it exists in the main kernel tree; saying it ran code from staging). “Staging Tree” because its role had therefore, it has the full universe of ker- Bug reports from a tainted kernel will changed; also, there seemed to be some nel users available to test it while pre- be less likely to find folks willing to confusion about it. senting minimal danger to kernel stabil- debug them. If you’re working on code The staging tree, he explained, was ity. It answers a need that has been ad- in staging, this puts most of the onus on the drivers/staging directory in the offi- dressed in a variety of ways through the you to debug it yourself, and if you cial kernel. Code submitted to that direc- years: How can developers get their think the bug wasn’t triggered by your tory in the linux -next git repository code tested by enough users to make it code, you should reproduce it on an un- would be fed directly to Linus during the acceptable in the main tree before it ac- tainted kernel and submit the report. merge window and would be included in tually goes into the main tree? Then, you’ll find plenty of willing hack- the next official kernel release with little The restrictions placed on projects ers to help you. or no objection from him. going into staging are to make sure that All of this is by way of isolating stag- Appropriate projects for staging are all code preserves kernel stability and is ing development from the rest of kernel drivers and filesystems that require no moving in a direct line toward migrating development. As a developer of staging code changes anywhere else in the tree out of staging and into its proper loca- code, you benefit from an audience of (i.e., they are standalone patches). The tion in the official source tree. Therefore, potentially millions of users, but the re- only exceptions to this are: firmware can any project going into staging should be sponsibility of dealing with reports from (and should) live in the firmware direc- well maintained, either by the person those users, as well as the behavior of tory, symbols may be exported from the submitting it or by a volunteer who’s your own code, lies with you. main kernel code if the relevant subsys- willing to “babysit” the code. Staging is To me, this seems like a really elegant tem maintainer approves, documenta- not a place to “dump code and run solution to a problem that has stymied tion may live in the Documentation di- away,” as Greg puts it. Any code that kernel developers for years; no doubt rectory, although that is frowned upon. lives in staging will taint the kernel logs it’ll be improved as time goes by. Linux Magazine Exclusive JUNE 2009 ISSUE 103 67.
Load more

Recommended publications
  • Redhawk Linux User's Guide
    Linux® User’s Guide 0898004-520 May 2007 Copyright 2007 by Concurrent Computer Corporation. All rights reserved. This publication or any part thereof is intended for use with Concurrent products by Concurrent personnel, customers, and end–users. It may not be reproduced in any form without the written permission of the publisher. The information contained in this document is believed to be correct at the time of publication. It is subject to change without notice. Concurrent makes no warranties, expressed or implied, concerning the information contained in this document. To report an error or comment on a specific portion of the manual, photocopy the page in question and mark the correction or comment on the copy. Mail the copy (and any additional comments) to Concurrent Computer Corporation, 2881 Gateway Drive, Pompano Beach, Florida, 33069. Mark the envelope “Attention: Publications Department.” This publication may not be reproduced for any other reason in any form without written permission of the publisher. Concurrent Computer Corporation and its logo are registered trademarks of Concurrent Computer Corporation. All other Concurrent product names are trademarks of Concurrent while all other product names are trademarks or registered trademarks of their respective owners. Linux® is used pursuant to a sublicense from the Linux Mark Institute. Printed in U. S. A. Revision History: Date Level Effective With August 2002 000 RedHawk Linux Release 1.1 September 2002 100 RedHawk Linux Release 1.1 December 2002 200 RedHawk Linux Release 1.2 April 2003 300 RedHawk Linux Release 1.3, 1.4 December 2003 400 RedHawk Linux Release 2.0 March 2004 410 RedHawk Linux Release 2.1 July 2004 420 RedHawk Linux Release 2.2 May 2005 430 RedHawk Linux Release 2.3 March 2006 500 RedHawk Linux Release 4.1 May 2006 510 RedHawk Linux Release 4.1 May 2007 520 RedHawk Linux Release 4.2 Preface Scope of Manual This manual consists of three parts.
    [Show full text]
  • Kshot: Live Kernel Patching with SMM and SGX
    KShot: Live Kernel Patching with SMM and SGX Lei Zhou∗y, Fengwei Zhang∗, Jinghui Liaoz, Zhengyu Ning∗, Jidong Xiaox Kevin Leach{, Westley Weimer{ and Guojun Wangk ∗Department of Computer Science and Engineering, Southern University of Science and Technology, Shenzhen, China, zhoul2019,zhangfw,ningzy2019 @sustech.edu.cn f g ySchool of Computer Science and Engineering, Central South University, Changsha, China zDepartment of Computer Science, Wayne State University, Detroit, USA, [email protected] xDepartment of Computer Science, Boise State University, Boise, USA, [email protected] Department of Computer Science and Engineering, University of Michigan, Ann Arbor, USA, kjleach,weimerw @umich.edu { f g kSchool of Computer Science and Cyber Engineering, Guangzhou University, Guangzhou, China, [email protected] Abstract—Live kernel patching is an increasingly common kernel vulnerabilities also merit patching. Organizations often trend in operating system distributions, enabling dynamic up- use rolling upgrades [3], [6], in which patches are designed dates to include new features or to fix vulnerabilities without to affect small subsystems that minimize unplanned whole- having to reboot the system. Patching the kernel at runtime lowers downtime and reduces the loss of useful state from running system downtime, to update and patch whole server systems. applications. However, existing kernel live patching techniques However, rolling upgrades do not altogether obviate the need (1) rely on specific support from the target operating system, to restart software or reboot systems; instead, dynamic hot and (2) admit patch failures resulting from kernel faults. We patching (live patching) approaches [7]–[9] aim to apply present KSHOT, a kernel live patching mechanism based on patches to running software without having to restart it.
    [Show full text]
  • Red Hat Enterprise Linux 7 Kernel Administration Guide
    Red Hat Enterprise Linux 7 Kernel Administration Guide Examples of Tasks for Managing the Kernel Last Updated: 2018-05-21 Red Hat Enterprise Linux 7 Kernel Administration Guide Examples of Tasks for Managing the Kernel Marie Dolezelova Red Hat Customer Content Services [email protected] Mark Flitter Red Hat Customer Content Services Douglas Silas Red Hat Customer Content Services Eliska Slobodova Red Hat Customer Content Services Jaromir Hradilek Red Hat Customer Content Services Maxim Svistunov Red Hat Customer Content Services Robert Krátký Red Hat Customer Content Services Stephen Wadeley Red Hat Customer Content Services Florian Nadge Red Hat Customer Content Services Legal Notice Copyright © 2018 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates.
    [Show full text]
  • Red Hat Enterprise Linux 8 Managing, Monitoring and Updating the Kernel
    Red Hat Enterprise Linux 8 Managing, monitoring and updating the kernel A guide to managing the Linux kernel on Red Hat Enterprise Linux 8 Last Updated: 2019-11-05 Red Hat Enterprise Linux 8 Managing, monitoring and updating the kernel A guide to managing the Linux kernel on Red Hat Enterprise Linux 8 Legal Notice Copyright © 2019 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
    [Show full text]
  • Understanding the Linux Virtual Memory Manager
    1 Understanding The Linux Virtual Memory Manager Mel Gorman 15th February 2004 Contents List of Figures 5 List of Tables 7 Acknowledgements 9 1 Introduction 12 1.1 General Kernel Literature . 13 1.2 Thesis Overview . 14 1.3 Typographic Conventions . 14 1.4 About this Document . 14 1.5 Companion CD . 15 2 Code Management 17 2.1 Managing the Source . 17 2.2 Getting Started . 23 2.3 Submitting Work . 24 3 Describing Physical Memory 26 3.1 Nodes . 27 3.2 Zones . 29 3.3 Pages . 31 3.4 High Memory . 33 4 Page Table Management 36 4.1 Describing the Page Directory . 37 4.2 Describing a Page Table Entry . 38 4.3 Using Page Table Entries . 39 4.4 Translating and Setting Page Table Entries . 42 4.5 Allocating and Freeing Page Tables . 42 4.6 Kernel Page Tables . 43 4.7 Mapping addresses to struct pages .................. 44 5 Process Address Space 47 5.1 Linear Address Space . 48 5.2 Managing the Address Space . 49 2 CONTENTS 3 5.3 Process Address Space Descriptor . 50 5.4 Memory Regions . 55 5.5 Exception Handling . 70 5.6 Page Faulting . 71 5.7 Copying To/From Userspace . 77 6 Boot Memory Allocator 80 6.1 Representing the Boot Map . 81 6.2 Initialising the Boot Memory Allocator . 81 6.3 Allocating Memory . 83 6.4 Freeing Memory . 85 6.5 Retiring the Boot Memory Allocator . 85 7 Physical Page Allocation 90 7.1 Managing Free Blocks . 90 7.2 Allocating Pages . 91 7.3 Free Pages .
    [Show full text]
  • Open Source Software License Information
    Open Source Software license information This document contains an open source software license information for the product VACUU·SELECT. The product VACUU·SELECT contains open source components which are licensed under the applicable open source licenses. The applicable open source licenses are listed below. The open source software licenses are granted by the respective right holders directly. The open source licenses prevail all other license information with regard to the respective open source software components contained in the product. Modifications of our programs which are linked to LGPL libraries are permitted for the customer's own use and reverse engineering for debugging such modifications. However, forwarding the information acquired during reverse engineering or debugging to third parties is prohibited. Furthermore, it is prohibited to distribute modified versions of our programs. In any case, the warranty for the product VACUU·SELECT will expire, as long as the customer cannot prove that the defect would also occur without these modification. WARRANTY DISCLAIMER THE OPEN SOURCE SOFTWARE IN THIS PRODUCT IS DISTRIBUTED IN THE HOPE THAT IT WILL BE USEFUL, BUT WITHOUT ANY WARRANTY, WITHOUT EVEN THE IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. See the applicable licenses for more details. Written offer This product VACUU·SELECT contains software components that are licensed by the holder of the rights as free software, or Open Source software, under GNU General Public License, Versions 2 and 3, or GNU Lesser General Public License, Versions 2.1, or GNU Library General Public License, Version 2, respectively. The source code for these software components can be obtained from us on a data carrier (e.g.
    [Show full text]
  • Status and Direction of Kernel Development Andrew Morton
    Status and Direction of Kernel Development Andrew Morton <[email protected]> <[email protected]> Linux Foundation Japan Linux Symposium 2008 July 2008 Page 1 of 18 Overview ● Process – The linux-next tree – Embedded development – X86 – Realtime ● Technology – Filesystems – Memory management – Hardware virtualisation (Xen/vmware/KVM) – OS virtualisation (containers) – RAS – AIO – Tracing Page 2 of 18 The “linux-next” tree ● A GIT tree operated by Stephen Rothwell – Merges together 104 subsystem development trees – This represents 85% of the changes in Linux. The remaining 15% is in the -mm tree. ● I will soon feed most of the -mm tree into linux-next so we get close to 100% Page 3 of 18 Why “linux-next” exists ● To reduce the amount of breakage which occurs during the 2.6.x-rc1 merge window. – because it gets additional testing ● To provide an integration tree in which the various subsystem changes can be tested together ● To help persuade subsystem developers to not make conflicting changes – I was seeing a lot of this happening. The prominence of linux-next makes people more careful about what they merge. ● To take the "subsystem tree integration" function out of my hands – I wasn't doing it very well and it was getting harder and harder Page 4 of 18 “linux-next” status ● It is going well - perhaps better than I had expected ● It still isn't receiving as much testing as I would like. ● There is some testing by "testers" but few if any "developers" appear to be testing linux-next. ● This is bad because individual developers are now testing their changes in the 2.6.x environment, but that code is destined to be integrated into 2.6.x+1.
    [Show full text]
  • Fully Automated Testing of the Linux Kernel
    Fully Automated Testing of the Linux Kernel Martin Bligh Andy P. Whitcroft Google Inc. IBM Corp. [email protected] [email protected] Abstract formance regressions and trends, adding sta- tistical analysis. A broad spectrum of tests are necessary—boot testing, regression, func- Some changes in the 2.6 development process tion, performance, and stress testing; from disk have made fully automated testing vital to the intensive to compute intensive to network in- ongoing stability of Linux R . The pace of de- tensive loads. A fully automated test harness velopment is constantly increasing, with a rate also empowers other other techniques that are of change that dwarfs most projects. The lack impractical when testing manually, in order of a separate 2.7 development kernel means that to make debugging and problem identification we are feeding change more quickly and di- easier. These include automated binary chop rectly into the main stable tree. Moreover, the search amongst thousands of patches to weed breadth of hardware types that people are run- out dysfunctional changes. ning Linux on is staggering. Therefore it is vi- tal that we catch at least a subset of introduced In order to run all of these tests, and collate the bugs earlier on in the development cycle, and results from multiple contributors, we need an keep up the quality of the 2.6 kernel tree. open-source client test harness to enable shar- Given a fully automated test system, we can ing of tests. We also need a consistent output run a broad spectrum of tests with high fre- format in order to allow the results to be col- quency, and find problems soon after they are lated, analysed and fed back to the community introduced; this means that the issue is still effectively, and we need the ability to “pass” fresh in the developers mind, and the offending the reproduction of issues from test harness to patch is much more easily removed (not buried the developer.
    [Show full text]
  • How to Participate in the Linux Community a Guide to the Kernel Development Process
    How to Participate in the Linux Community A Guide To The Kernel Development Process by Jonathan Corbet, [email protected] The purpose of this document is to help developers (and their managers) work with the development community with a minimum of frustration. It is an attempt to document how this community works in a way which is accessible to those who are not intimately familiar with Linux kernel development (or, indeed, free software development in general). While there is some technical material here, this is very much a process- oriented discussion which does not require a deep knowledge of kernel programming to understand. August 2008 1.1: Executive Summary 1.2: What This Document Is About The rest of this section covers the scope of the kernel development The Linux kernel, at over 6 million lines of code and well over 1000 process and the kinds of frustrations that developers and their active contributors, is one of the largest and most active free software employers can encounter there. There are a great many reasons projects in existence. Since its humble beginning in 1991, this kernel why kernel code should be merged into the official (“mainline”) has evolved into a best-of-breed operating system component which kernel, including automatic availability to users, community support runs on pocket-sized digital music players, desktop PCs, the largest in many forms, and the ability to influence the direction of kernel supercomputers in existence, and all types of systems in between. It development. Code contributed to the Linux kernel must be made is a robust, efficient, and scalable solution for almost any situation.
    [Show full text]
  • Hacking the Linux Kernel for Fun and Profit
    Hacking the Linux Kernel for Fun and Profit James Bottomley Hansen Partnership, Inc. 5 April 2008 1 Introduction • The Linux Kernel is becoming an increasingly complex place – The number of “core subsystem” maintainers is growing – The number of supported features is growing – The rate of change of code is also (currently) growing • Often difficult to understand what you’re changing. • Even more difficult to work out what the correct way to change it is. • However, the kernel has a basic need for talented and motivated contributors 2 Agenda 1. OK, I understand the Fun Part, where’s the Profit? 2. Why you should contribute code to the Kernel (and why your Employer should pay you to do it). 3. Why the Kernel needs you to contribute. 4. Why it isn’t as simple as it sounds 5. Where to go to get help 3 Where’s the Money 1. Current total investment in Linux up to 2008: $2BN 2. Annual Income derived from Linux in 2007: $2BN 3. So, there’s a lot of money floating around. 4. The problem is, not much of it goes directly to kernel developers. 5. Open Source is about Code not Business Models 6. However Good Business models make money off Open Source 7. Moral: If you want to get really rich, start a company. 4 Indirect Economic Benefits • Most open source projects hire the top contributors in their area. • Even if that’s not you, a large number of recruiters use open source mailing lists as a tool. • Everything you do in open source is on show and easily searchable – Recruiters know this.
    [Show full text]
  • Building a Robust Linux Kernel Piggybacking the Linux Test Project
    Building a Robust Linux Kernel piggybacking The Linux Test Project Subrata Modak & Balbir Singh, Linux Technology Center, IBM, India OLS 2008 Dated 25/07/2008 Linux is a registered trademark of Linus Torvalds. Agenda ● Introduction – some background checks ● Addressing some Criticism ● Breathing a new life into LTP ● Kernel code coverage statistics ● Role of LTP in testing Linux ● Early & Effective testing ● Simplest way to write an LTP test case ● Future Plans ● Conclusion 2 © 2008 IBM Corporation Everybody is happy, and... they should be ● Linux Kernel is growing at a rapid rate and runs across numerous architectures...neighbor´s envy – ownerś pride Mission Critical... ● Keeping the kernel reliable, stable & robust Somebody doing the Job...?? ● Yes, The Linux Test Project ● It was established to meet the very goals stated above 3 © 2008 IBM Corporation Beware to ignore testing...!! you will end up in ● Frequent crashes ● Frequent Updates ● Unhappy users 4 © 2008 IBM Corporation Introduction – some background checks ● First created by SGI in 2001 - brought organized and automated testing to Linux for first time ● Primary goal: provide a test suite that can validate the robustness, stability & reliability of Linux kernel ● A functional and regression test suite that allows to do stress testing as well ● No. of tests at kernel 2.3 was mere 100 ● Today at 2.6.25 , it stands at 3000+ and growing... ● Tests numerous kernel features, namely syscalls, MM, IPC, I/O, device drivers, FS, Networking, etc ● What´s the code written in ??... 95% in
    [Show full text]
  • Autotest Documentation Release 0.16.3-44-G0d527f
    autotest Documentation Release 0.16.3-44-g0d527f Autotest Team May 31, 2018 Contents 1 Autotest Documentation 3 1.1 General Information...........................................3 1.2 Local (Former Client).......................................... 20 1.3 Remote (Former Server)......................................... 41 1.4 Frontend................................................. 70 1.5 System Administration.......................................... 125 1.6 Scheduler................................................. 146 1.7 Developer................................................. 154 2 client Package 195 2.1 autotest_local Module...................................... 195 2.2 base_sysinfo Module........................................ 195 2.3 base_utils Module.......................................... 196 2.4 bkr_proxy Module.......................................... 200 2.5 bkr_xml Module............................................ 202 2.6 client_logging_config Module................................. 203 2.7 cmdparser Module.......................................... 203 2.8 common Module............................................. 204 2.9 config Module............................................. 204 2.10 cpuset Module............................................. 204 2.11 fsdev_disks Module......................................... 206 2.12 fsdev_mgr Module.......................................... 208 2.13 fsinfo Module............................................. 208 2.14 harness Module............................................ 209
    [Show full text]