When you are done, WeensyOS should look like this. In the virtual map, kernel memory is no longer reverse-video, since the user canâ€™t access it. Note the lonely CGA console memory block. Hints: Implement process isolation by giving each process its own independent page table. Your OS should look like this: Thus, each process only has permission to access its own pages. You can tell this because only its own pages are shown in reverse video. What goes in per-process page tables: How to implement per-process page tables: So far, WeensyOS processes use physical page allocation: the page with physical address X is used to satisfy the sys_page_alloc(X) allocation request for virtual address X. This is inflexible and limits utilization. Change the implementation of the INT_SYS_PAGE_ALLOC system call so that it can use any free physical page to satisfy a sys_page_alloc(X) request. Your new INT_SYS_PAGE_ALLOC code must perform the following tasks. Donâ€™t modify the physical_page_alloc helper function, which is also used by the program loader. You can write a new function if you want. Hereâ€™s how our OS looks after this step. Hints: Now the processes are isolated, which is awesome. But theyâ€™re still not taking full advantage of virtual memory. Isolated address spaces can use the same virtual addresses for different physical memory. Thereâ€™s no need to keep the four process address spaces disjoint. In this step, change each processâ€™s stack to start from address 0x300000 == MEMSIZE_VIRTUAL. Now the processes have enough heap room to use up all of physical memory! If thereâ€™s no physical memory available, sys_page_alloc should return an error to the caller (by returning -1). (Our solution additionally prints â€œOut of physical memory!â€ to the console when this happens; you donâ€™t need to.) We return in this exercise to a topic that we saw earlier in the semester: the fork() system call. In the first WeensyOS lab, you implemented a primitive version of fork. In this exercise, you will implement a more realistic fork; this one will actually give the new process a separate memory address space. Backing up a bit, recall that fork is one of Unixâ€™s great ideas. It starts a new process as a copy of an existing process. (fork returns in each process, the original and the copy.) To the child process, it returns 0. To the parent process, it returns the childâ€™s process ID. Now, run WeensyOS with make run or make run-console. At any time, press the â€˜fâ€™ key. This will soft-reboot WeensyOS and ask it to run a single p-fork process, rather than the gang of allocators. You should see something like this: Your job now is to implement (most of) fork. When youâ€™re done, you should see something like this after pressing â€˜fâ€™. An image like this means you forgot to copy the data for some pages, so the processes are actually sharing stack and/or data pages: Requirements: max Use virtual_memory_map. A description of this function is in kernel.h. You will benefit from reading all the function descriptions in kernel.h. If you really want to look at the code for virtual_memory_map, it is in k-hardware.c, along with many other grody hardware functions. The perm argument to virtual_memory_map is a bitwise-or of zero or more PTE flags, PTE_P, PTE_W, and PTE_U. PTE_P marks Present pages (pages that are mapped). PTE_W marks Writable pages. PTE_U marks User-accessible pagesâ€”pages accessible to applications. You want kernel memory to be mapped with permissions PTE_P|PTE_W, which will prevent applications from reading or writing the memory, while allowing the kernel to both read and write. Make sure that your sys_page_alloc system call is safe. Applications shouldnâ€™t be able to use sys_page_alloc to screw up the kernel. Similarly, if the application requests to allocate an address that is the last page in virtual memory space, you should arrange for the system call to return an error (this page will be used as the stack page later). Each processâ€™s initial page table should be based on kernel_pagetable. The x86 architecture uses two-level page tables. A WeensyOS page table thus consists of two physical pages, one for the level-1 page table and another for a single level-2 page table. You must allocate both these pages. (In a larger operating system, there would be many level-2 page tables.) These pages should be owned by the process (should have pageinfo[PN].owner == processid). Because of a restriction in how program_load works, you must use addresses in kernel address space (i.e., below PROC_START_ADDR) for the initial processesâ€™ page tables. The level-1 page table is all 0, except that pagetable->entry should equal (x86_pageentry_t) address_of_new_l2_pagetable | PTE_P | PTE_W | PTE_U. You need to set this up yourself. The initial mappings for addresses less than PROC_START_ADDR should be copied from those in kernel_pagetable. You can use a loop with virtual_memory_lookup and virtual_memory_map to copy them. Alternately, you can copy the mappings from the kernelâ€™s page table into the new page table using memcpy. This is faster, but make sure you copy the right data! The initial mappings for the user areaâ€”addresses greater than or equal to PROC_START_ADDRâ€”should be inaccessible to user processes (the PTE_U bit should be cleared in the corresponding page table entries). In our solution (shown above), these addresses are totally inaccessible (they are not mapped, so they show as blank). However, you can implement this differently (for example, by having the inaccessible addresses be mapped but not with PTE_U privilege); if you do that, your display will look different from the animated gifs throughout this lab description. Change process_setup to create per-process page tables. We suggest you write a copy_pagetable(x86_pagetable* pagetable, int8_t owner) function that allocates and returns a new page table, initialized as a copy of pagetable. This function will be useful in Exercise 5. In process_setup you can modify the page table returned by copy_pagetable according to the requirements above. Your function can use pageinfo to find free pages to use for page tables. Read about pageinfo at the top of kernel.c. If you create an incorrect page table, itâ€™s likely that WeensyOS will crazily reboot. Hint: The macros in x86.h will be handy, particularly PTE_ADDR (see the section on “Address composition” above). Find a free physical page using the pageinfo array. Return -1 to the application if you canâ€™t find one. Use any algorithm you like to find a free physical page; we just return the first one we find. Record the physical pageâ€™s allocation in pageinfo. Map that physical page at the requested virtual address. Look at the other code in kernel.c for some hints on how to examine the pageinfo array. A physical page is free if pageinfo[PAGENUMBER].refcount == 0. We give you the basic structure of fork. Specifically, we include the code that initializes the child processâ€™s registers as a copy of the parent processâ€™s registers (and sets reg_eax to 0). We also include the code that looks for a free process slot in the processes array. (You implemented these things in the first WeensyOS lab.) If no slot exists, fork returns -1 to the caller. If a free slot is found, you need to make a copy of current->p_pagetable, the forking processâ€™s page table, using your copy_pagetable function from earlier. But you must also copy the process data in every application page shared by the two processes. The processes should not share any writable memory except the console (otherwise they wouldnâ€™t be isolated). So fork must examine every virtual address in the old page table. Whenever the parent process has an application-writable page at virtual address V, then fork must allocate a new physical page P; copy the data from the parentâ€™s page into P, using memcpy; and finally map page P at address V in the child processâ€™s page table. Use virtual_memory_lookup to query the mapping between virtual and physical addresses in a page table.
Delivering a high-quality product at a reasonable price is not enough anymore.
That’s why we have developed 5 beneficial guarantees that will make your experience with our service enjoyable, easy, and safe.
You have to be 100% sure of the quality of your product to give a money-back guarantee. This describes us perfectly. Make sure that this guarantee is totally transparent.Read more
Each paper is composed from scratch, according to your instructions. It is then checked by our plagiarism-detection software. There is no gap where plagiarism could squeeze in.Read more
Thanks to our free revisions, there is no way for you to be unsatisfied. We will work on your paper until you are completely happy with the result.Read more
Your email is safe, as we store it according to international data protection rules. Your bank details are secure, as we use only reliable payment systems.Read more
By sending us your money, you buy the service we provide. Check out our terms and conditions if you prefer business talks to be laid out in official language.Read more