similar to: Related to Xen Terminology

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

I want to know any difference between writing, reading and shadow page table (for example performance). I am thankful for any help or resource for that. -- Best Regards Mohamad Taghi Mir Mohamad Rezaie Iran University of Science and Technology Department of Computer Science & Engineering System Software Group _______________________________________________ Xen-devel mailing list

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

paging mechanism clarification Hi All, The Xen uses 2 level Paging Mechanism to resolve the Virtual Addresses into frame numbers from domU.The first level is taken care by the MMU for the domU i.e translation from virtual address to the physical address just like normal paging mechanism. The second level of translation is done by the Xen hypervisor.It translates the pseduo physical address

In a recent conversation one of my coworkers raised a concern about memory limitations when running 32-bit guests on top of the 64-bit hypervisor. At this point the discussion is academic; I don''t know when/if we''ll ever be able to get system resources to test it, to see if the concerns that he expressed are real. So I decided to post this in hope of getting comments from the

I''m to porting a lightweight kernel to Xen 3.0.4-x86_64 and have run into a problem while setting the PML4. Xen complains that it has a bad type of ''PGT_writable_page'' (e8000001), while it expects 80000000. However, I''m almost certain that this is not the case. I added a routine to do a depth first search of the four page table levels looking for this machine

All, I''m posting to the Xen-devel list and the OSDL fastboot list. There are a number of Xen folks who''ll want to look at the code. For the fastboot folks, this is mostly intended as an announcement of the port. Please limit your replies to the list(s) that they applies to, thanks :-) A number of people have expressed interest in kexec support for Xen guests. In

In xen 3.0.4-1 source, where is the *unhook/rehook page table implementation* which is important things in ''writable page table mode''.? I can''t find it. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Dear all; Has anyone tried the new CPU (codename Yonah) produced by Apple? I heard from the engineer of Apple that MacBook Pro is already reachable, although it is not distributed to the public until February. If anyone has some information, I would like to buy it to enlarge the frontier. -- Does Yonah demand xen/i86 or xen/ppc? Or we need brand-new source code? That is the problem. Is

hi I try to understand the code of xen memory there are gmfn, gpfn and pfn in the xen and in the /xen/include/xen/mm.h there are some explanation about them as follows: * 1. gpfn/gpaddr: A guest-specific pseudo-physical frame number or address. * 2. gmfn/gmaddr: A machine address from the p.o.v. of a particular guest. * 3. mfn/maddr: A real machine frame number or address. * 4.

Hello every body. Well, my question is very simple . I Have a HVM working fine ( I hope so ... ) on a CentOS 5.1 , xen 3.1. I created config file by hand .. I''m not using virtmanager from CentOS .. I '' m using LVM dev w/o file system formated. My HDA is configured like this: disk = [ ''phy:/dev/vms_1/win01,hda,w'' ] My question , what is the diference if I

Hi all. I''m now try to read and write puseud physical memory of domU from Dom0 with xenaccess(this is using libxc). #http://xenaccess.sourceforge.net/ With xenaccess, I''m succeeded read and writing almost of the memory. But It fail when I try to access head 1M region and some bit regions. To be precise, xc_map_foreign_range() of libxc returns error code. **

Hi, I have a question about memory page tables in Xen. As far as I understood, every modification to page table will go through Xen(hypervisor). Is it so that all page tables are actually allocated in Xen(hypervisor) instead of guest OS(domain)? Also, is it the case that Xen(hypervisor) needs to maintain a page table for each process running in every domain? Thanks Haifeng

Hi, Which of the Mercurial repos contains Linux kernel sources that were used to build the Xen 3.1 binary distribution? I have this question because I am suspecting that the sata_via driver included in the distribution is not supporting my SATA controller VIA8237x (I get error messages when modprobe''ing it from an init ramdisk). This repo (http://xenbits.xensource.com/linux-2.6-xen.hg)

Hello virtual friends. I''m using Windows HVM on CentOS 5.1, xen 3.1. When I conect VNC to Dom0 IP , I get correct screen, main windows console. But I have a very very poor mouse performance. I tried xensoure 4.1 , and I saw a mouse performance a little bit better than xen 3.1 w / CentOS 5.1. What is me problem, CentOS 5.1 or xen 3.1 , or compilation wrong maked by CentOS people. Why

On Mon, Apr 15, 2019 at 6:21 PM Thomas Zimmermann <tzimmermann at suse.de> wrote: > > Hi > > Am 15.04.19 um 17:54 schrieb Daniel Vetter: > > On Tue, Apr 09, 2019 at 09:50:40AM +0200, Thomas Zimmermann wrote: > >> Hi > >> > >> Am 09.04.19 um 09:12 schrieb kraxel at redhat.com: > >>> Hi, > >>> > >>>> If not

On Mon, Apr 15, 2019 at 6:21 PM Thomas Zimmermann <tzimmermann at suse.de> wrote: > > Hi > > Am 15.04.19 um 17:54 schrieb Daniel Vetter: > > On Tue, Apr 09, 2019 at 09:50:40AM +0200, Thomas Zimmermann wrote: > >> Hi > >> > >> Am 09.04.19 um 09:12 schrieb kraxel at redhat.com: > >>> Hi, > >>> > >>>> If not

Dear, I''m looking to get Xen running on a system that (afterwards) seems a bit too new. The board has the Intel G33 chipset with the Intel ICH9 southbridge. This chipset is NOT supported by kernel 2.6.18 which ships with Xen 3.1.2 (and Debian Etch). So the question is: * What version of Xen to install to get going? Should I choose unstable? * What distribution will be the easiest to get