search for: __start_xen

...ded stuff could be loaded into memory according to multiboot protocol. (e.g. implemented by GRUB). It means that current implementation of Xen takes info about current system config from multiboot_info_t structure (it is copied from original place in assembly files and then passed as an argument to __start_xen()) and some other BIOS sources if needed (e.g. VGA config, EDD data). Later when EFI come into the scene there was no significant change in that. multiboot_info_t structure and others are initialized artificially by Xen EFI boot stuff. Additionally, due to that there is no place for extra boot info...

...ection_header_table_t elf_sec; } u; u32 mmap_length; u32 mmap_addr; } multiboot_info_t However, on x86_64 using gcc, addresses as well as unsigned long are 64 bits long. It seems that luckily mmap_addr is below 2*32-1, making the u32 type acceptable so far (for instance in function __start_xen, where the memory map is turned into another structure) but what would it cost to change it into u64 ? After all, the multiboot specification (page 18) has ''unsigned long'' instead of u32 here. _______________________________________________ Xen-devel mailing list Xen-devel@lis...

Hi All, I am not very familiar with xen details. Now I am thinking of building two privilged domain(domain 0 not driver domain) at boot time. The other question is that wether it is possible to create another domain 0 by domain-builder running in domain0? Does it make sense when domain 0 is shut down unexpectedly another domain 0 can run at once. Maybe it is absurd. I am looking forwards

There are BIOSes that want to map the IO-APIC MMIO region from some ACPI method(s), and there is at least one BIOS flavor that wants to use this mapping to clear an RTE''s mask bit. While we can''t allow the latter, we can permit reads and simply drop write attempts, leveraging the already existing infrastructure introduced for dealing with AMD IOMMUs'' representation as

Hi Tim, Could you please have a look at this bug? Thanks a lot. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1774 Best Regards, Yongjie Ren (Jay) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...ing a BUG in the hypervisor code. Following is the stack trace of the xen based kernel: [<ff10f8d6>] alloc_vcpu+0x36/0x120 [<ff1518c0>] smp_prepare_cpus+0x460/0xd30 [<ff132fcd>] intel_p6_mcheck_init+0xbd/0xe0 [<ff1555b4>] get_mtrr_state+0xf4/0x110 [<ff1508f1>] __start_xen+0x5d1/0x9e0 [<ff123270>] new_tlbflush_clock_period+0x0/0x90 [<ff10015a>] start_paging+0x52/0x54 CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT CONTEXT. System shutting down--need manual reset. As opposed to the vanilla linux kernel (that fails to see the loca...

...to learn xen boot codes. I use bochs with gdb stub to implement source codes debug. I rebuild xen kernel with "debug=y, debugger=y" to enable debug, boot xen by bochs, connect gdb remote target, set breakpoint. All are ok now.(I run gdb in directory "xen", and set breakpoint at __start_xen.) But, when the breakpoint is hit, gdb displays:"setup.c:no such file or directory". Of course, I can use directory to add search path to gdb. But if trace into a different directory, I have to use "direcotry" again. You know, the directory structure is some complex, so it's...

...atches for this error, which only affects intel: http://www.gossamer-threads.com/lists/xen/devel/185593 For logging the output is the same as in the above thread: Xen call trace ========== xsave_init + 0x6d/0x1f0 init_intel + 0x13d/0x380 generic_identity + 0x39/0x190 identify_cpu + 0xe2/0x250 __start_xen + 0x2ec6/0x3340 __high_start + 0xa1/0xa3 Error message: =========== Panic on CPU 0: Xen BUG at i387.c:159 For more info: http://wiki.xensource.com/xenwiki/Xen4.0 In Xen 4.0.1 there's a bug in HVM guest save/restore/livemigration on Intel CPUs, related to XSAVE feature. As a workaround yo...

We found machines with >32 E820 memory map entries, where Xen fails to boot (but Linux does boot fine). The native Linux (both x86 and x86_86) already has: #define E820MAX 128 /* number of entries in E820MAP */ Signed-off-by: Jun Nakajima <jun.nakajima@intel.com> Jun --- Intel Open Source Technology Center -- diff -r 3bb1857981e6 -r 51e9c0c806b2 xen/include/asm-x86/e820.h ---

...>map[i].size = e - s; + e820->map[i].type = type; + + return 1; +} + int __init e820_change_range_type( struct e820map *e820, uint64_t s, uint64_t e, uint32_t orig_type, uint32_t new_type) --- a/xen/arch/x86/setup.c +++ b/xen/arch/x86/setup.c @@ -1248,6 +1248,8 @@ void __init __start_xen(unsigned long mb #ifdef CONFIG_X86_64 vesa_mtrr_init(); + + acpi_mmcfg_init(); #endif if ( opt_nosmp ) --- a/xen/arch/x86/x86_32/pci.c +++ b/xen/arch/x86/x86_32/pci.c @@ -60,8 +60,3 @@ int pci_find_ext_capability(int seg, int { return 0; } - -void acpi_mmcfg_init(void) -{...

...asm-x86/mach-generic - I/home/nightly/builds_xen_unstable/xen-3.0-hg-xen-unstable-6096- 20050812/xen/include/asm-x86/mach-default -O3 -fomit-frame-pointer -msoft- float -m64 -mno-red-zone -fpic -fno-reorder-blocks -fno-asynchronous-unwind- tables -DNDEBUG -c setup.c -o setup.o setup.c: In function `__start_xen'': setup.c:530: error: unrecognizable insn: (insn:HI 2752 2751 396 19 (set (reg/f:DI 707) (plus:DI (reg/f:DI 262) (const_int 137438953472000 [0x7d0000000000]))) -1 (insn_list 2751 (nil)) (expr_list:REG_DEAD (reg/f:DI 262) (expr_list:REG_EQUAL (const:DI (plus...

Hi! From other people posting to this list, I know that there has been a bug related to the issue described in Xen Security Advisory 36 that disables iommu for some AMD users like me. However, even when passing "iommu=no-amd-iommu-perdev-intremap" it still disables i/o virtualisatoin. Related Xen dmesg output: (XEN) IVHD Error: Invalid IO-APIC 0 (XEN) AMD-Vi: Error initialization

...@@ static void machine_real_restart(const u #endif -void machine_restart(char *cmd) +/* + * generic teardown (i.e. kill watchdog, disable hvm, disable IO APIC, etc.) + * + * will teardown APs and leave in hlt loop + * will teardown BSP and reboot or halt + * + * TEARDOWN_TYPE_EARLY is used by __start_xen (in EARLY_FAIL()) before much + * of the system has been initialized (e.g. before fixmap) + */ +static void machine_teardown(int type) { int i; + int timeout = 10; + + if ( type != TEARDOWN_TYPE_EARLY ) + { + /* Ensure we are the boot CPU. */ + if ( GET_APIC_ID(apic_rea...

.... total_memory is: info.total_pages/((1 << 20) / vinfo->pagesize) where ''info'' is what libxl_get_physinfo() provides. On its turn, libxl_get_physinfo() is xc_physinfo(), which is XEN_SYSCTL_physinfo, which uses total_pages, which is assigned the number of pages, down in __start_xen(), as it results from parsing the E820 map (looking for RAM blocks). OTOH, memsize comes from libxl_get_numainfo(), which is xc_numainfo(), which is XEN_SYSCTL_numainfo, which puts in memsize what node_spanned_pages(<node_id>) says. That seems to come, on a NUMA box, from the parsing of SRA...

...000 00000000 00000000 00000000 00000000 (XEN) 00000000 00000000 00000000 ff1bb080 (XEN) Xen call trace: (XEN) [<ff146c26>] amd_mcheck_init+0x26/0xe0 (XEN) [<ff1464cc>] identify_cpu+0x1fc/0x210 (XEN) [<ff1b3fbe>] subarch_init_memory+0x4e/0x70 (XEN) [<ff1ad999>] __start_xen+0xab9/0x1380 (XEN) [<ff1a1fff>] e820nr+0x0/0x4 (XEN) [<ff1a15ff>] e820map+0x0/0xa00 (XEN) [<ff10006c>] __high_start+0x58/0x5a (XEN) (XEN) (XEN) **************************************** (XEN) Panic on CPU 0: (XEN) GENERAL PROTECTION FAULT (XEN) [error_code=0000] (XEN)...

...(XEN) [<ff1288ad>] clear_fault_bits+0x2d/0xc0 (XEN) [<ff12971b>] init_vtd_hw+0x13b/0x3c0 (XEN) [<ff129f39>] intel_vtd_setup+0x599/0x600 (XEN) [<ff126b96>] iommu_setup+0x26/0x100 (XEN) [<ff117e80>] stopmachine_softirq+0x0/0xa0 (XEN) [<ff1f69d5>] __start_xen+0xef5/0x1570 (XEN) [<ff1e6250>] e820nr+0x0/0x4 (XEN) [<ff10006c>] __high_start+0x58/0x5a (XEN) (XEN) Pagetable walk from fff7aff8: (XEN) L3[0x003] = 000000000022f001 55555555 (XEN) L2[0x1ff] = 0000000000271063 55555555 (XEN) L1[0x17a] = 0000000000000000 ffffffff (XEN) (XE...

1: correct LDT checks 2: add address validity check to guest_map_l1e() 3: use {rd,wr}{fs,gs}base when available 4: check for canonical address before doing page walks Signed-off-by: Jan Beulich <jbeulich@suse.com>

...sprintf: 240 0xffff83000012aa7e printf: 240 0xffff83000012b1e3 debugtrace_printk: 240 0xffff83000014261b find_matching_ucodes: 240 0xffff8300001500a5 map_pages_to_xen: 240 0xffff8300001c219a __start_xen: 240 0xffff830000114845 translate_gpfn_list: 232 0xffff830000114c78 translate_gpfn_list: 232 0xffff830000115b27 do_memory_op: 232 0xffff830000116067 do_memory_op: 232 0xffff8300001af923 vmx_assist:...

...to BAUD_AUTO instead, so you can just specify "console=com1" and it will most likely work. Signed-off-by: John Levon <john.levon@sun.com> diff --git a/xen/arch/x86/setup.c b/xen/arch/x86/setup.c --- a/xen/arch/x86/setup.c +++ b/xen/arch/x86/setup.c @@ -303,6 +303,7 @@ void __init __start_xen(multiboot_info_t paddr_t s, e; int i, e820_warn = 0, e820_raw_nr = 0, bytes = 0; struct ns16550_defaults ns16550 = { + .baud = BAUD_AUTO, .data_bits = 8, .parity = ''n'', .stop_bits = 1 ____________________________________________...

...0000 (XEN) Xen call trace: (XEN) [<ffff8300001180f4>] __bug+0x24/0x30 (XEN) [<ffff830000106f15>] alloc_vcpu+0x45/0x130 (XEN) [<ffff830000107369>] alloc_idle_vcpu+0x59/0x80 (XEN) [<ffff830000169f49>] smp_prepare_cpus+0x4a9/0xd10 (XEN) [<ffff830000168f0c>] __start_xen+0x75c/0xac0 (XEN) [<ffff8300001001c1>] __high_start+0x94/0x96 (XEN) (XEN) ************************************ (XEN) CPU0 FATAL TRAP 6 (invalid opcode), ERROR_CODE 0000, IN INTERRUPT CONTEXT. (XEN) System shutting down -- need manual reset. (XEN) ************************************ This...