similar to: Pinning L1 page table with wrpt

I sent this patch directly to Gregor, and neglected to CC this list. Sorry about that. I''d like to make it so that there is no need to modify any Mini-OS source files when extending it with an application. All that is required is a change to Makefile, and a small change to kernel.c, printf.c, and string.c. I have enclosed the patch. With this patch, one could write an application in a

hi, I''m developing my own 32-bit (no PAE) paravirtualized kernel for xen with Mini-OS as a starting point. I am currently working on process page table support (equivalent of arch/i386/mm/pgtable-xen.c) and mostly following Linux for the moment. I noticed that linux-2.6.18-xen never pins an L1 table (a pte), yet __pgd_pin() walks the page directory and gives up write access on the kernel

hi, it would be extremely useful for me if someone with knowledge of how the current tools and drivers use Xenstore would be kind enough to update the Wiki with current information. I have been spending quite a lot of time trying to get my domU connected to a block device in dom0 using a home-brewed domain creation tool, and I am still at the ''Timeout connecting to device!''

Hi, Patch below is needed to make my system work stable in PAE mode. Havn''t seen problems without PAE, not sure whenever thats just pure luck or whenever there is a bug in my PAE xenlinux kernel. To me it looks like a generic bug though. I''ve actually trapped into problems with unpin only: A process exits, somewhere in exit_mm() the page tables are unpinned, shortly thereafter

This is my current set of updates to Xen for 2.6.24. This is largely a bugfix set, and a couple of them are also relevent to 2.6.23. These are in the pre-x86 merge form; I'll update them once the merge goes into git. Quick overview: - remove some dead code in arch/i386/mm/init.c - clean up some duplicate includes - when sending an IPI, yield the vcpu if the destination doesn't have

This is my current set of updates to Xen for 2.6.24. This is largely a bugfix set, and a couple of them are also relevent to 2.6.23. These are in the pre-x86 merge form; I'll update them once the merge goes into git. Quick overview: - remove some dead code in arch/i386/mm/init.c - clean up some duplicate includes - when sending an IPI, yield the vcpu if the destination doesn't have

This is my current set of updates to Xen for 2.6.24. This is largely a bugfix set, and a couple of them are also relevent to 2.6.23. These are in the pre-x86 merge form; I'll update them once the merge goes into git. Quick overview: - remove some dead code in arch/i386/mm/init.c - clean up some duplicate includes - when sending an IPI, yield the vcpu if the destination doesn't have

Is there any way to make gaming in domU work? It''s not clear to me, if this can be done with open-gl or so. If this is impossible now, is some development planned in this area? Eventually I would wait buying my next pc until the necessary cpu features are available. TIA, martin -- _______________________________________________________________________________ No MS-Word attachments

At OLS I gave a talk on some of the Xen scalability inhibitors, and one of these was writable page tables. We went over why the feature does not scale, but just as important, we found that the uniprocessor case does not provide any advantage either. These tests were done on x86_64, so I wanted to run the 1-way test on 32 bit to show the same problem. So, I have run with writable PTs and

hi, I am trying to add xenbus watch support to mini-os, but am getting into a endless loop of watches firing over and over. Below is an excerpt from the xenstore tracefile: IN 0x805acc8 20070103 19:32:18 WATCH (/local/domain/0/backend/vif/26/0/state 00043818 ) CREATE watch 0x805a8b8 OUT 0x805acc8 20070103 19:32:18 WATCH (OK ) OUT 0x805acc8 20070103 19:32:18 WATCH_EVENT

Hi, I need to get the exact downtime for doing a live migration with ms precision. (I am not bothered about whole migration time which is close to 1 minute.. I need to measure the live migration downtime during which the DomU is out of service.. the figure quoted in the xen documentation says it as ~60 ms.. ) I hope someone must have tried to measure this before. Can you suggest me ideas

Hi All, Can anyone please tell me what does pinning and unpinning of pages mean in XEN? Regards, Sameer _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi there! I was wondering what the general opinion on autotoolizing xen is? I am volunteering to do so, if there is interest in updating the build system to use autoconf, automake and/or libtool. Is one configure script for all of xen enough or do you want to be able to configure all/some tools separately? I know that Anthony is no fan of libtool... are there more reservations about some

On Thu, May 16, 2019 at 06:27:45PM +0200, Thomas Zimmermann wrote: > The new interfaces drm_gem_vram_{pin/unpin}_reserved() are variants of the > GEM VRAM pin/unpin functions that do not reserve the BO during validation. > The mgag200 driver requires this behavior for its cursor handling. The > patch also converts the driver to use the new interfaces. > > Signed-off-by: Thomas

On Thu, May 16, 2019 at 06:27:45PM +0200, Thomas Zimmermann wrote: > The new interfaces drm_gem_vram_{pin/unpin}_reserved() are variants of the > GEM VRAM pin/unpin functions that do not reserve the BO during validation. > The mgag200 driver requires this behavior for its cursor handling. The > patch also converts the driver to use the new interfaces. > > Signed-off-by: Thomas

Hello, as some might have read in my previous postings, I have a Mini-OS dom0 that constructs a Mini-OS domU on x86 xen-3.0.4-testing. As the memory layout my Dom0 builds does not guarantee, that pages the DomU Mini-OS tries to use as page tables are mapped to existing memory, I changed new_pt_frame in arch/x86/mm.c in the following way: The pt_pfn is mapped R/W, then it is zeroed by a

When operating on an unpinned pagetable (ie, one under construction or destruction), it isn''t necessary to use a hypercall to update a pud/pmd entry. Jan Beulich observed that a similar optimisation avoided many thousands of hypercalls while doing a kernel build. One tricky part is that early in the kernel boot there''s no page structure, so we can''t check to see if the

Am 20.05.19 um 18:26 schrieb Daniel Vetter: > [CAUTION: External Email] > > On Mon, May 20, 2019 at 06:19:00PM +0200, Daniel Vetter wrote: >> On Thu, May 16, 2019 at 06:27:45PM +0200, Thomas Zimmermann wrote: >>> The new interfaces drm_gem_vram_{pin/unpin}_reserved() are variants of the >>> GEM VRAM pin/unpin functions that do not reserve the BO during validation.

A kernel test bot reported a problem with the locktorture testcase that was triggered by the GEM VRAM helpers. ... [ 10.004734] RIP: 0010:ttm_bo_validate+0x41/0x141 [ttm] ... [ 10.015669] ? kvm_sched_clock_read+0x5/0xd [ 10.016157] ? get_lock_stats+0x11/0x3f [ 10.016607] drm_gem_vram_pin+0x77/0xa2 [drm_vram_helper] [ 10.017229]

A kernel test bot reported a problem with the locktorture testcase that was triggered by the GEM VRAM helpers. ... [ 10.004734] RIP: 0010:ttm_bo_validate+0x41/0x141 [ttm] ... [ 10.015669] ? kvm_sched_clock_read+0x5/0xd [ 10.016157] ? get_lock_stats+0x11/0x3f [ 10.016607] drm_gem_vram_pin+0x77/0xa2 [drm_vram_helper] [ 10.017229]