Re: [PATCH] i386: For debugging, make the initial page table setup less forgiving.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Eric W. Biederman wrote:
I suspect what we want to do is come up with a function to call
to test to see if a page should be read-only and map such pages
_PAGE_KERNEL_RO, or _PAGE_KERNEL_RO_EXEC if it's code.

Speaking of things what are paravirt_alloc_pd and parafirt_alloc_pd supposed to do?

For hypervisors which shadow kernel page tables, none of these concerns with keeping page tables read-only arise. However, another set of concerns does arise with maintaining shadow synchronization. One of those problems is keeping the hypervisor aware of when pages are being used as page tables.

However, it turns out both direct page table and shadow page table implementations can be made to use one page table allocation function; in the direct page table case (as for Xen), this is the point where page tables can be recognized and made read-only. So this is the dual purpose of the paravirt_alloc_p[dt] functions.

Zach
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux