Project 4: /dev/dice Solution

Project Description

Standard UNIX and Linux systems come with a few special files like /dev/zero, which returns nothing but zeros when it is read, and /dev/random, which returns random bytes. In this project, you will write a device driver to create a new device, /dev/dice which returns randomly selected rolls of a 6-sided die.







How It Will Work




For this project, we will need to create three parts: the device driver, the special file /dev/dice, and a test program to convince ourselves it works




The test program will be an implementaJon of the game of craps.







Driver Implementation




Our device driver will be a character device that will implement a read funcJon (which is the implementaJon of the read() syscall) and returns appropriate die rolls (a single die roll is a 1 byte value from 0 to 5 and we must support read()ing an arbitrary count of these). As we discussed in class, the kernel does not have the full C Standard library available to it and so we need to get use a different funcJon to get random numbers. By including <linux/random.h we can use the funcJon get_random_bytes(), which you can turn into a helper funcJon to get a single byte:




unsigned char get_random_byte(int max) {




unsigned char c;

get_random_bytes(&c, 1);

return c%max;

}










The Game of Craps (30 points)




Using your driver, you will be implemenJng the game of Craps. For those unfamiliar with the rules, Craps is played with two dice which are rolled together. The sum of these two dice is computed and if the sum is:




2, 3, or 12 – the player immediately loses.



7 or 11 – the player immediately wins.



Any other number is referred to as the “point.” The goal then becomes to keep rolling the dice unJl: o The player rolls a 7 – the player loses



o The player rolls the “point” – the player wins.




Your job is to make a simple craps game. In this game the player will enter his or her name, the program will display a welcome message, and ask if the player would like to play or quit. The program will then roll two dice, and display them and their total. If the player has won, display a message congratulaJng them. If the player has lost, report it to them. Otherwise, store this first roll as the “point” roll and keep rolling unJl the player wins or loses. When the game ends, ask if the player would like to play again. Example:







Welcome to Jon’s Casino!




Please enter your name: Jonathan

Jonathan, would you like to Play or Quit? play

You have rolled 5 + 2 = 7




You Win!




Would you like to play again? no




Goodbye, Jonathan!




Hints




Remember that rolling two 6-sided dice is different than rolling one 12-sided die.







Use string input, do not make an integer menu or use single characters.







Gets each die to display by reading bytes from the /dev/dice file.



You may write the craps program using stdlib’s rand() for tesJng, but make sure you eventually replace it with your read()s of /dev/dice










Installation and Example




On thoth.cs.pitt.edu, login and cd to your /u/SysLab/USERNAME directory.



tar xvfz ../shared/hello_dev.tar.gz



cd hello_dev



Open the Makefile with the editor of your choice. (E.g., nano Makefile)



We need to setup the path to compile against the proper version of the kernel. To do this, change the line:



KDIR := /lib/modules/$(shell uname -r)/build




to




KDIR := /u/SysLab/shared/linux-2.6.23.1




Build the kernel object. The ARCH=i386 is important because we are building a 32-bit kernel on a 64-bit machine.



make ARCH=i386







Download and launch QEMU. For Windows users, you can just double click the qemu-win.bat that is supplied in the zipfile available on my website. Mac users should download and install Q.app and use the tty.qcow2 disk image provided in the main zipfile. Linux users are lel to install qemu as appropriate and also use the tty.qcow2 disk image provided in the main zipfile.



When Linux boots under QEMU login using the root/root account (username/password).



We now need to download the kernel module you just built into the kernel using scp:






scp USERNAME@thoth.cs.pitt.edu:/u/SysLab/USERNAME/hello_dev/hello_dev.ko .




10. Load the driver using insmod:




insmod hello_dev.ko







We now need to make the device file in /dev. First, we need to find the MAJOR and MINOR numbers that idenJfy the new device:






cd /sys/class/misc/hello




cat dev

The output should be a number like 10:63. The 10 is the MAJOR and the 63 is the MINOR.



We use mknod to make a special file. The name will be hello and it is a character device. The 10 and the 63 correspond to the MAJOR and MINOR numbers we discovered above (if different, use the ones you saw.)






cd /dev/




mknod hello c 10 63




14. We can now read the data out of /dev/hello with a simple call to cat:







cat /dev/hello




You should see “Hello, world!” which came from the driver. We can clean up by removing the device and unloading the module:



rm /dev/hello




rmmod hello_dev.ko










What to Do Next

The code for the example we went through comes from

hpp://www.linuxdevcenter.com/pub/a/linux/2007/07/05/devhelloworld-a-simple-introducJon-to-device-drivers-

under-linux.html?page=2 which I’ve mirrored at: hpp://people.cs.pip.edu/~jmisurda/teaching/cs449/valerie-




henson-device-drivers-hello.pdf







Read that while going through the source to get an idea of what the Module is doing. Start with the third secJon enJtled “Hello, World! Using /dev/hello_world” and read up unJl the author starts describing udev rules; we are not using udev under QEMU.




When you have an idea of what is going on, make a new directory under your /u/SysLab/USERNAME directory called

dice_driver:




mkdir dice_driver







Copy and rename the hello_dev.c from the example, and copy over the Makefile. Edit the Makefile to build your new file. Change all the references of “hello” to “dice_driver”.







Building the Driver




To build any changes you have made, on thoth in your dice_driver directory, simply:







make ARCH=i386




If you want to force a rebuild of everything you may want to remove the object files first:







rm *.o







Copying the Files to QEMU




From QEMU, you will need to download the driver that you just built. Use scp to download the driver to a home directory (/root/ if root):







scp USERNAME@thoth.cs.pitt.edu:/u/SysLab/USERNAME/dice_driver/dice_driver.ko .







Loading the Driver into the Kernel in QEMU
As root (either by logging in or via su):




insmod dice_driver.ko






















Making the /dev/dice Device




Like in the example, we’ll need to determine the MAJOR and MINOR numbers for this parJcular driver.




cd /sys/class/misc/dice_driver




cat dev




and use those numbers to make the /dev/dice file:







cd /dev




mknod dice c MAJOR MINOR







Unloading the Driver from the Kernel in QEMU




As root (either by logging in or via su):







rmmod dice_driver.ko




Then you can remove the /dev/dice file:







rm /dev/dice










Implementing and Building the craps Program




Since thoth is a 64-bit machine and QEMU emulates a 32-bit machine, we should build with the -m32 flag:




gcc –m32 –o craps craps.c -static










Running craps




We cannot run our craps program on thoth.cs.pitt.edu because its kernel does not have the device driver loaded. However, we can test the program under QEMU once we have installed the new driver. We first need to download craps using scp as we did for the driver. However, we can just run it from our home directory without any installaJon necessary.







File Backups




One of the major contribuJons the university provides for the AFS filesystem is nightly backups. However, the /u/SysLab/ parJJon is not part of AFS space. Thus, any files you modify under your personal directory in /u/SysLab/ are not backed up. If there is a catastrophic disk failure, all of your work will be irrecoverably lost. As such, it is my recommendaJon that you:




Backup all the files you change under /u/SysLab to your ~/private/ directory frequently!




Loss of work not backed up is not grounds for an extension. YOU HAVE BEEN WARNED.
Hints and Notes




printk() is the version of printf() you can use for debugging messages from the kernel.







In the driver, you can use some standard C funcJons, but not all. They must be part of the kernel to work.







In the craps program, you may use any of the C standard library funcJons.







As root, typing poweroff in QEMU will shut it down cleanly.







If the module crashes, it may become impossible to delete the file you created with mkdev in /dev. If that happens, just grab a new disk image and start over. It’s why we’re developing in a virtual machine as opposed to a real one.










Requirements and Submission




You need to submit:




Your dice_driver.c file and the Makefile







Your well-commented craps program’s source







Make a tar.gz file named USERNAME-project4.tar.gz




Copy your archive to the submit directory:




~jrmst106/submit/449/