search for: pt_base

Displaying 20 results from an estimated 81 matches for "pt_base".

2006 Aug 24
3
How to show deug info via XENPRINTF?
Hi all. I am trying to debug a kernel that I built, and I hope I could see some debug info printing out via XENPRINTF. I use it in the source code of kernel like: XENPRINTF("nr_pages: %ld shared_info: 0x%lx flags: 0x%lx pt_base: 0x%lx " "mod_start: 0x%lx mod_len: 0x%lx\n", xen_start_info->nr_pages, xen_start_info->shared_info, xen_start_info->flags, xen_start_info->pt_base, xen_start_info->mod_start, xen_start_info->mod_len); But it doesn''t print anything out wh...
2006 Aug 24
3
How to show deug info via XENPRINTF?
Hi all. I am trying to debug a kernel that I built, and I hope I could see some debug info printing out via XENPRINTF. I use it in the source code of kernel like: XENPRINTF("nr_pages: %ld shared_info: 0x%lx flags: 0x%lx pt_base: 0x%lx " "mod_start: 0x%lx mod_len: 0x%lx\n", xen_start_info->nr_pages, xen_start_info->shared_info, xen_start_info->flags, xen_start_info->pt_base, xen_start_info->mod_start, xen_start_info->mod_len); But it doesn''t print anything out wh...
2009 May 07
1
[PATCH 5/5] xen: reserve Xen start_info rather than e820 reserving
...4 --- a/arch/x86/xen/setup.c +++ b/arch/x86/xen/setup.c @@ -61,9 +61,9 @@ char * __init xen_memory_setup(void) * - xen_start_info * See comment above "struct start_info" in <xen/interface/xen.h> */ - e820_add_region(__pa(xen_start_info->mfn_list), - xen_start_info->pt_base - xen_start_info->mfn_list, - E820_RESERVED); + reserve_early(__pa(xen_start_info->mfn_list), + __pa(xen_start_info->pt_base), + "XEN START INFO"); sanitize_e820_map(e820.map, ARRAY_SIZE(e820.map), &e820.nr_map); -- 1.6.0.6 ______________________________...
2013 Sep 24
4
Problems with vTPM manager
...quot;vtpmmgr" iomem=["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:...
2012 Nov 16
1
[PATCH v4] x86/xen: Use __pa_symbol instead of __pa on C visible symbols
...LE, PFN_DOWN(__pa(pgd))); pin_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);
2012 Nov 16
1
[PATCH v4] x86/xen: Use __pa_symbol instead of __pa on C visible symbols
...LE, PFN_DOWN(__pa(pgd))); pin_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);
2013 Jun 19
9
some problems to start vTPM vtpm-stubdom
..."file:/var/vtpmmgr-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:...
2013 Jun 19
9
some problems to start vTPM vtpm-stubdom
..."file:/var/vtpmmgr-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:...
2007 Sep 23
9
Confused about start of day setup
...ges. My kernel is mapped at 0 (due 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 initi...
2012 Feb 20
2
[PATCH] Disable PAT support when running under Xen (v1).
...s. */ __supported_pte_mask &= ~_PAGE_GLOBAL; +#if 0 if (!xen_initial_domain()) +#endif __supported_pte_mask &= ~(_PAGE_PWT | _PAGE_PCD); __supported_pte_mask |= _PAGE_IOMAP; @@ -1204,10 +1206,6 @@ asmlinkage void __init xen_start_kernel(void) pgd = (pgd_t *)xen_start_info->pt_base; - if (!xen_initial_domain()) - __supported_pte_mask &= ~(_PAGE_PWT | _PAGE_PCD); - - __supported_pte_mask |= _PAGE_IOMAP; /* Don''t do the full vcpu_info placement stuff until we have a possible map and a non-dummy shared_info. */ per_cpu(xen_vcpu, 0) = &HYPERVISOR_shar...
2013 Sep 24
0
Problems starting vtmmgr
...quot;vtpmmgr" iomem=["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:...
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
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
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
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
2007 Jun 15
11
[PATCH 00/10] paravirt/subarchitecture boot protocol
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
2007 Jun 20
9
[PATCH 0/9] x86 boot protocol updates
[ 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
2007 Jun 20
9
[PATCH 0/9] x86 boot protocol updates
[ 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
2006 Jul 17
3
mini-os under xen 3.0.2
...ut as far as I understand the source code and the README, it should continue by printing the current time in regular intervals, which it does not. Here is the output I receive: ---------------------------------- Xen Minimal OS! start_info: c001d000 nr_pages: 8192 shared_inf: 00be3000 pt_base: c0020000 mod_start: 0x0 mod_len: 0 flags: 0x0 cmd_line: MM: Init _text: c0000000 _etext: c0009577 _edata: c000a604 stack start: c0011e40 _end: c00142a4 start_pfn: 25 max_pfn: 2000 Mapping memory range 0xc0400000 - 0xc2000000 MM:...
2008 Jan 18
0
[PATCH] minios: support COW for a zero page
...- a/extras/mini-os/arch/x86/traps.c Fri Jan 18 15:55:13 2008 +0000 +++ b/extras/mini-os/arch/x86/traps.c Fri Jan 18 16:02:32 2008 +0000 @@ -118,6 +118,46 @@ void page_walk(unsigned long virt_addres } +static int handle_cow(unsigned long addr) { + pgentry_t *tab = (pgentry_t *)start_info.pt_base, page; + unsigned long new_page; + int rc; + +#if defined(__x86_64__) + page = tab[l4_table_offset(addr)]; + if (!(page & _PAGE_PRESENT)) + return 0; + tab = pte_to_virt(page); +#endif +#if defined(__x86_64__) || defined(CONFIG_X86_PAE) + page = tab[l3_table_offset(addr...
2008 Sep 23
0
答复: Re: 答复: RE: 答复:RE:
...hvmachine-dm 2 32 1 -b---- 8.2 and qemu.log : Using config file "/etc/xen/vm/hvmachine-dm". Started domain hvmachine-dm Xen Minimal OS! ^Mstart_info: 0x311000 ^M nr_pages: 8192 shared_inf: 001d1000 ^M pt_base: 0x314000 mod_start: 0x0 ^M mod_len: 0 ^M flags: 0x0 ^M cmd_line: -d 1 ^M stack: 0x2e8620-0x308620 ^MMM: Init ^M _text: 0x0 ^M _etext: 0xd8828 ^M _erodata: 0x105000 ^M _edata: 0x1101e8 ^M stack start: 0x2e8620 ^M _end: 0x308db8 ^M star...
2012 Nov 26
13
[PATCH 0 of 4] Minios improvements for app development
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