search for: base_address

...ff-by: Sylvain Gault <sylvain.gault at gmail.com> --- efi/x86_64/linux.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/efi/x86_64/linux.S b/efi/x86_64/linux.S index 972c0b2..29dde94 100644 --- a/efi/x86_64/linux.S +++ b/efi/x86_64/linux.S @@ -27,7 +27,7 @@ kernel_jump: base_address: pop %rsi - /* need to perform a long jump to update cs + /* need to perform a long jump to update cs */ /* load absolute address of pm_code in jmp_address location */ lea (pm_code - base_address)(%rsi, 1), %rax -- 2.5.1

...elector (0x10) and return address (%rdi) - * on the stack in preparation for the far return below. - */ - mov $0x1000000000, %rcx - addq %rcx, %rdi - pushq %rdi + /* save the content of rsi (boot_param argument of kernel_jump function) */ + mov %rsi, %rbx + + call base_address +base_address: + pop %rsi + + /* need to perform a long jump to update cs + + /* load absolute address of pm_code in jmp_address location */ + lea (pm_code - base_address)(%rsi, 1), %rax + mov %eax, (jmp_address - base_address)(%rsi, 1) + + ljmp *(jmp_address - base_address)(%rsi,...

...li - /* - * Setup our segment selector (0x10) and return address (%rdi) - * on the stack in preparation for the far return below. - */ - mov $0x1000000000, %rcx - addq %rcx, %rdi - pushq %rdi + /* save the content of rsi (boot_param argument of kernel_jump function) */ + mov %rsi, %rbx + + call base_address +base_address: + pop %rsi + + /* need to perform a long jump to update cs + + /* load absolute address of pm_code in jmp_address location */ + lea (pm_code - base_address)(%rsi, 1), %rax + mov %eax, (jmp_address - base_address)(%rsi, 1) + + ljmp *(jmp_address - base_address)(%rsi, 1) + +jmp_address...

Hi all, I''ve got the latest win32-mmap code checked into CVS. Unfortunately, it seems that I''m not able to open an existing mapping and retrieve set data. Below is a simple example that seems like it ought to work but doesn''t. Any ideas? # map1.rb require ''win32/mmap'' include Win32 mmap = MMap.new(:name => ''alpha'', :size

hello, I''m running XEN 2.0 on IBM ThinkPad T23. Now the weird thing is that I get two different outputs from /sbin/lspci depending on whether I run 2.6.8.1-xen0 or 2.6.8.1-bproc. In particular the output from 2.6.8.1-xen0 seems to be missing those 4 lines 0000:00:01.0 PCI bridge: Intel Corp. 82830 830 Chipset AGP Bridge (rev 02) 0000:00:1e.0 PCI bridge: Intel Corp. 82801BAM/CAM PCI

...+} + +static void __init paravirt_init_resources(struct resource *res, + struct acpi_iort_node *node) +{ + int i; + int num_res = 0; + int hw_irq, trigger; + struct acpi_iort_pviommu *pviommu; + + pviommu = (struct acpi_iort_pviommu *)node->node_data; + + res[num_res].start = pviommu->base_address; + res[num_res].end = pviommu->base_address + pviommu->span - 1; + res[num_res].flags = IORESOURCE_MEM; + num_res++; + + for (i = 0; i < pviommu->interrupt_count; i++) { + hw_irq = IORT_IRQ_MASK(pviommu->interrupts[i]); + trigger = IORT_IRQ_TRIGGER_MASK(pviommu->interrupts[i]);...

...aulo > --- > efi/x86_64/linux.S | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/efi/x86_64/linux.S b/efi/x86_64/linux.S > index 972c0b2..29dde94 100644 > --- a/efi/x86_64/linux.S > +++ b/efi/x86_64/linux.S > @@ -27,7 +27,7 @@ kernel_jump: > base_address: > pop %rsi > > - /* need to perform a long jump to update cs > + /* need to perform a long jump to update cs */ > > /* load absolute address of pm_code in jmp_address location > */ lea (pm_code - base_address)(%rsi, 1), %rax -- Paulo Alcantara, C.E.S.A.R Speaking f...

...ll/only under a flag? So, I've brought this up a few times before - that DWARFv5 does a pretty good job of reducing relocations (& reducing .o file size with Split DWARF) by allowing many uses of addresses to include some kind of address+offset (debug_rnglists and loclists allowing "base_address" then offset_pairs (an improvement over similar functionality in DWARFv4 because the offset pairs can be uleb encoded - so they can be quite compact)) But one place that DWARFv5 misses to reduce relocations further is direct addresses from debug_info, such as DW_AT_low_pc. For a while I'...

.../* register base address of the unit */ u16 segment; @@ -70,7 +70,7 @@ struct acpi_drhd_unit { }; struct acpi_rmrr_unit { - struct dmar_scope scope; /* must be first member of struct */ + struct dmar_scope scope; struct list_head list; u64 base_address; u64 end_address; @@ -79,7 +79,7 @@ struct acpi_rmrr_unit { }; struct acpi_atsr_unit { - struct dmar_scope scope; /* must be first member of struct */ + struct dmar_scope scope; struct list_head list; u16 segment; u8 all_ports:1; ______________...

Hi all, Looking at the IO.readlines source in io.c, it looks to me like they grab 8k chunks, split on the input record separator, and buffer accordingly. Since it looks like ReadFileScatter() does some of that work automatically (in page file sized chunks), I thought I''d give it a try. Here''s what I''ve got, but it doesn''t work. I have an incorrect parameter

...> > So, I've brought this up a few times before - that DWARFv5 does a pretty > good job of reducing relocations (& reducing .o file size with Split > DWARF) by allowing many uses of addresses to include some kind of > address+offset (debug_rnglists and loclists allowing "base_address" then > offset_pairs (an improvement over similar functionality in DWARFv4 because > the offset pairs can be uleb encoded - so they can be quite compact)) > > > > But one place that DWARFv5 misses to reduce relocations further is > direct addresses from debug_info, such as...

...'ve brought this up a few times before - that DWARFv5 does a pretty > > good job of reducing relocations (& reducing .o file size with Split > > DWARF) by allowing many uses of addresses to include some kind of > > address+offset (debug_rnglists and loclists allowing "base_address" then > > offset_pairs (an improvement over similar functionality in DWARFv4 because > > the offset pairs can be uleb encoded - so they can be quite compact)) > > > > > > But one place that DWARFv5 misses to reduce relocations further is > > direct addresses...

..._header header; + u8 reserved[12]; + struct acpi_table_header base_table; +}; + +#define ACPI_VIOT_IORT_NODE_VIRTIO_PCI_IOMMU 0x80 +#define ACPI_VIOT_IORT_NODE_VIRTIO_MMIO_IOMMU 0x81 + +struct acpi_viot_iort_virtio_pci_iommu { + u32 devid; +}; + +struct acpi_viot_iort_virtio_mmio_iommu { + u64 base_address; + u64 span; + u64 flags; + u64 interrupt; +}; + +/* FIXME: rename this monstrosity. */ +#define ACPI_VIOT_IORT_VIRTIO_MMIO_IOMMU_CACHE_COHERENT (1<<0) + /******************************************************************************* * * LPIT - Low Power Idle Table -- 2.24.0

...named modules_head which is a linked list of struct elf_module. You'll have to load the .elf file with the add-symbol-file command. Unfortunately, this command will only load the the .text section at the precise address given while syslinux load the full ELF file at the base address module->base_address. But you can give this command all the sections to load and addresses at which to load them with the command: add-symbol-file themodule.elf 0xtextaddress -s .data 0xdataaddress -s .rodata 0xrodataaddress ... And you can get the address of the sections in memory by adding the module base address wi...

...(64 * KB) #define MAX_LIB_HEAP_SIZE (600 * KB) /*---------------------------------------------------------------------- -----*\ \*---------------------------------------------------------------------- -----*/ #if LINUX_VERSION_CODE < KERNEL_VERSION(2, 3, 13) # define GET_PCI_BASE(d, r) (d)->base_address[r] #else # define GET_PCI_BASE(d, r) (d)->resource[r].start #endif #if LINUX_VERSION_CODE < KERNEL_VERSION(2, 3, 43) # define KFREE_SKB(x) dev_kfree_skb(x) #else # include <linux/netdevice.h> # define KFREE_SKB(x) dev_kfree_skb_any(x) #endif #if defined (CONFIG_ISAPNP_MODULE) &&...

...before - that DWARFv5 does a pretty >>>> > good job of reducing relocations (& reducing .o file size with Split >>>> > DWARF) by allowing many uses of addresses to include some kind of >>>> > address+offset (debug_rnglists and loclists allowing "base_address" then >>>> > offset_pairs (an improvement over similar functionality in DWARFv4 because >>>> > the offset pairs can be uleb encoded - so they can be quite compact)) >>>> > > >>>> > > But one place that DWARFv5 misses to reduce r...

On Wed, Jan 13, 2016 at 01:22:17AM +0100, Celelibi wrote: > 2016-01-12 22:21 UTC+01:00, Tal Lubko: > > On Mon, Jan 11, 2016 at 07:20:20PM -0500, Shao Miller wrote: > >> > >> Yes, you can print debug-output from custom builds. > >> > > > > Regarding my other question (debugging). > > I know it is possible to use prints for debugging. > > I

...************************************************ + * + * DRTM - Dynamic Root of Trust for Measurement table + * + ******************************************************************************/ + +struct acpi_table_drtm { + struct acpi_table_header header; /* Common ACPI table header */ + u64 entry_base_address; + u64 entry_length; + u32 entry_address32; + u64 entry_address64; + u64 exit_address; + u64 log_area_address; + u32 log_area_length; + u64 arch_dependent_address; + u32 flags; +}; + +/* 1) Validated Tables List */ + +struct acpi_drtm_vtl_list { + u32 validated_table_list_count; +}; + +/* 2) Resour...

Hello, I''m also seeing this exact same problem. I''ve posted on xen-users, but did not get an answer. Venkat seems to be experiencing the same problem as me. I have the latest BIOS for my motherboard DQ35JO. (BIOS ver 933) I''m running a Q6600 as well. It hangs at "Brought up 4 CPUs." I''ve tried all sorts of combinations of Xen versions and kernels to

I try pci pci passthrough with xen 3.3.1 and CentOS 5.2(64bit) on a SUPERMICRO C7X58 board I see the following the error in my boot log. (XEN) [VT-D]dmar.c:372: RMRR is incorrect. This problem is caused by this condition in dmr.c:372. if ( rmrr->base_address >= rmrr->end_address ) { dprintk(XENLOG_ERR VTDPREFIX, "RMRR is incorrect.\n"); return -EFAULT; } As an experiment, I delete the "return -EFAULT" and re-compiling Xen, I can pass a PCI device through to Gest-OS(Windows XP) and have no problem with using the device...