search for: nr_pt_frame

...ething which seems strange to me: the build_pagetable() function in mm.c. This function aims at building up the additional page tables which were not allocated by the hypervisor during the domain construction (domain_build.c). I do not understand the following calculation: pfn_to_map = (start_info.nr_pt_frames - NOT_L1_FRAMES) * L1_PAGETABLE_ENTRIES; pfn_to_map is supposed to be the first page frame number to be mapped by the function. However, the guest OS gets a list of pfns (start_pfn - max_pfn, including the phys_to_machine table) assigned by the hypervisor, and the first pfns are supposed to conta...

...mem=["fed40,5"] And I get this output when I try xl create -c vtpmmgr-stubdom.cfg: Parsing config from /home/xen_images/vtpmmgr-stubdom.cfg Daemon running with PID 5048 Xen Minimal OS! start_info: 0xa2000(VA) nr_pages: 0x1000 shared_inf: 0x44e09000(MA) pt_base: 0xa5000(VA) nr_pt_frames: 0x5 mfn_list: 0x9a000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line: stack: 0x597e0-0x797e0 MM: Init _text: 0x0(VA) _etext: 0x39357(VA) _erodata: 0x45000(VA) _edata: 0x47c40(VA) stack start: 0x597e0(VA) _end: 0x99e00(VA) start_pfn:...

...pagetable_pfn(MMUEXT_PIN_L3_TABLE, - PFN_DOWN(__pa(initial_page_table))); - xen_write_cr3(__pa(initial_page_table)); + PFN_DOWN(__pa_symbol(initial_page_table))); + xen_write_cr3(__pa_symbol(initial_page_table)); memblock_reserve(__pa(xen_start_info->pt_base), xen_start_info->nr_pt_frames * PAGE_SIZE);

...pagetable_pfn(MMUEXT_PIN_L3_TABLE, - PFN_DOWN(__pa(initial_page_table))); - xen_write_cr3(__pa(initial_page_table)); + PFN_DOWN(__pa_symbol(initial_page_table))); + xen_write_cr3(__pa_symbol(initial_page_table)); memblock_reserve(__pa(xen_start_info->pt_base), xen_start_info->nr_pt_frames * PAGE_SIZE);

...gr-stubdom.img,hda,w"] name="vtpmmgr" iomem=["fed40,1"] ==== It prints out with below: ======= Parsing config from vtpmmgr.cfg Daemon running with PID 2406 Xen Minimal OS! start_info: 0xa2000(VA) nr_pages: 0x1000 shared_inf: 0xcd7b0000(MA) pt_base: 0xa5000(VA) nr_pt_frames: 0x5 mfn_list: 0x9a000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line: stack: 0x597e0-0x797e0 MM: Init _text: 0x0(VA) _etext: 0x39357(VA) _erodata: 0x45000(VA) _edata: 0x47c40(VA) stack start: 0x597e0(VA) _end: 0x99e00(VA) start_pfn:...

...gr-stubdom.img,hda,w"] name="vtpmmgr" iomem=["fed40,1"] ==== It prints out with below: ======= Parsing config from vtpmmgr.cfg Daemon running with PID 2406 Xen Minimal OS! start_info: 0xa2000(VA) nr_pages: 0x1000 shared_inf: 0xcd7b0000(MA) pt_base: 0xa5000(VA) nr_pt_frames: 0x5 mfn_list: 0x9a000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line: stack: 0x597e0-0x797e0 MM: Init _text: 0x0(VA) _etext: 0x39357(VA) _erodata: 0x45000(VA) _edata: 0x47c40(VA) stack start: 0x597e0(VA) _end: 0x99e00(VA) start_pfn:...

...to Mini-OS being there): _text : 0x0 _etext : 0xcaef _edata : 0xe8c4 __bss_start : 0x10000 _end : 0x21590 nr_pages : 3072 start_info : 0x27000 pt_base : 0x2a000 nr_pt_frames : 5 machine_to_phys_mapping: 0xffff800000000000 phys_to_machine_mapping: 0x21000 The Mini-OS source says that free pages follow pt_base + nr_pt_frames + 3 (store, console, something pages). So far so good. So I reserve myself 42 pages for initial data structures and remove the rest...

...mem=["fed40,5"] And I get this output when I try xl create -c vtpmmgr-stubdom.cfg: Parsing config from /home/xen_images/vtpmmgr-stubdom.cfg Daemon running with PID 5048 Xen Minimal OS! start_info: 0xa2000(VA) nr_pages: 0x1000 shared_inf: 0x44e09000(MA) pt_base: 0xa5000(VA) nr_pt_frames: 0x5 mfn_list: 0x9a000(VA) mod_start: 0x0(VA) mod_len: 0 flags: 0x0 cmd_line: stack: 0x597e0-0x797e0 MM: Init _text: 0x0(VA) _etext: 0x39357(VA) _erodata: 0x45000(VA) _edata: 0x47c40(VA) stack start: 0x597e0(VA) _end: 0x99e00(VA) start_pfn:...

...tinfo_end, + vstartinfo_start, vstartinfo_start + PAGE_SIZE, + vstartinfo_start + PAGE_SIZE, vstartinfo_end, vstack_start, vstack_end, dsi.v_start, v_end); printf(" ENTRY ADDRESS: %08lx\n", dsi.v_kernentry); @@ -261,6 +265,8 @@ start_info->nr_pt_frames = nr_pt_pages; start_info->mfn_list = vphysmap_start; start_info->domain_controller_evtchn = control_evtchn; + start_info->store_page = vstartinfo_start + PAGE_SIZE; + start_info->store_evtchn = store_evtchn; if ( initrd_len != 0 ) { start_info-...

Hi, I‘m trying to install vTPM based on Xen-4.2.2, linux-kernel 3.9.1 (Dom0) and TPM emulator. However, I cannot find the TPM backed driver in this version of Dom0 linux kernel. There is no CONFIG_XEN_TPMDEV_BACKEND in the kernel config file. The config file for Dom0 is attached. Maybe it provides some useful information. So, how to install a Xen TPM backend driver in the Dom0 linux-kernel.

...fffffff81de7000 ffffffff81de8000 (END) On the domU console trying to boot the pv_ops 2.6.30.1 kernel with pvgrub: Started domain security (id=13) Xen Minimal OS! start_info: 0xa12000(VA) nr_pages: 0x10000 shared_inf: 0xb3ad0000(MA) pt_base: 0xa15000(VA) nr_pt_frames: 0x9 mfn_list: 0x992000(VA) mod_start: 0x991000(VA) mod_len: 4096 flags: 0x0 cmd_line: stack: 0x950860-0x970860 MM: Init _text: 0x0(VA) _etext: 0x617a4(VA) _erodata: 0x79000(VA) _edata: 0x81b00(VA) stack start: 0x950860(VA) _end: 0x990e68(VA)...

...flags; /* SIF_xxx flags. */ > u16 domain_controller_evtchn; > /* THE FOLLOWING ARE ONLY FILLED IN ON INITIAL BOOT (NOT RESUME). */ >- unsigned long pt_base; /* VIRTUAL address of page directory. */ >- unsigned long nr_pt_frames;/* Number of bootstrap p.t. frames. */ >- unsigned long mfn_list; /* VIRTUAL address of page-frame list. */ >- unsigned long mod_start; /* VIRTUAL address of pre-loaded module. */ >- unsigned long mod_len; /* Size (bytes) of pre-loaded module. */ >+...

...xl create -c vtpmmgr-stubdom.cfg > > I receive the following error: > > Parsing config from vtpmmgr-stubdom.cfg > Daemon running with PID 29361 > Xen Minimal OS! > start_info: 0xa2000(VA) > nr_pages: 0x1000 > shared_inf: 0x83ad7000(MA) > pt_base: 0xa5000(VA) > nr_pt_frames: 0x5 > mfn_list: 0x9a000(VA) > mod_start: 0x0(VA) > mod_len: 0 > flags: 0x0 > cmd_line: > stack: 0x597e0-0x797e0 > MM: Init > _text: 0x0(VA) > _etext: 0x39357(VA) > _erodata: 0x45000(VA) > _edata: 0x47c40(VA) > stack start: 0x597e0(VA) > _end: 0x99...

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which adds fields to specify the hardware subarchitecture and some

[ This patch depends on the cross-architecture ELF cleanup patch. ] This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which

[ This patch depends on the cross-architecture ELF cleanup patch. ] This series updates the boot protocol to 2.07 and uses it to implement paravirtual booting. This allows the bootloader to tell the kernel what kind of hardware/pseudo-hardware environment it's coming up under, and the kernel can use the appropriate boot sequence code. Specifically: - Update the boot protocol to 2.07, which

This patch series contains a set of patches making minios rather easier to use, from an application development point of view. Overview of patches: 1 Command line argument parsing support, from Xen. 2 Weak console handler function. 3 Build system tweaks for application directories. 4 Trailing whitespace cleanup. (because it is very messy) Patch 4 is likely to be more controversial than

...nsole_info struct. */ + uint32_t info_size; /* Size of console_info struct from start.*/ + } dom0; + } console; + /* THE FOLLOWING ARE ONLY FILLED IN ON INITIAL BOOT (NOT RESUME). */ + unsigned long pt_base; /* VIRTUAL address of page directory. */ + unsigned long nr_pt_frames; /* Number of bootstrap p.t. frames. */ + unsigned long mfn_list; /* VIRTUAL address of page-frame list. */ + unsigned long mod_start; /* VIRTUAL address of pre-loaded module. */ + unsigned long mod_len; /* Size (bytes) of pre-loaded module. */ + int8_t cmd_line[MAX_GUEST_...