similar to: assembly language use in xen

This set of patches converts the way frames gets created from using PUSHes/POPs to using MOVes, thus allowing (in certain cases) to avoid saving/restoring part of the register set. While the place where the (small) win from this comes from varies between CPUs, the net effect is a 1 to 2% reduction on a combined interruption entry and exit when the full state save can be avoided. 1: use MOV

Hello, We are looking to use Xen as our hypervisor. However, after doing some research it''s still not clear as to the amount of memory Xen 64bit can support? The highest I''ve found is 4TB of physical memory. For the host VM''s, I''ve found several statements that indicated that the max per VM was 32GB. Are these numbers accurate? And can these limits be removed

Keir: Not sure from when, at least now hvm_do_resume is double invoked in both 1: arch_vmx_do_resume from schedule_tail, and 2) vmx_asm_do_vmentry of ASM code for both x86 32 & 64 bits. I am wondering if the #1 is a redundant, can u have a double check? thx,eddie _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

Is there a required Clang and LLVM version one needs to do a ''make xen-dist clang=y''? I recently tried and the process failed. I haven''t begun debugging as I figured I would ask the obvious first. The build failed with the following: ... make[4]: Entering directory `/home/builder/xen-unstable/xen/drivers'' make -f /home/builder/xen-unstable/xen/Rules.mk -C char

hi, my friends: recently, i am reading the source codes about hypercall. First, i study a simple hypercall, for example, the "do_xen_version". In "xen-3.1.0-src\xen\common\kernel.c", the definition of "do_xen_version" is: DO(xen_version) (int cmd, XEN_GUEST_HANDLE(void) arg) { .... } according to the " #define DO(fn) long do_##fn ", the expanded form is

Hi I am tring to build the testcode for xenstored # cd xen-3.1-src/tools/xenstore/ # make testcode but it generating error due to conflict of function in fake_libxc with libxc. Error: gcc -Werror -Wp,-MD,.fake_libxc.o.d -I../../tools/libxc -I. -DTESTING -c -o fake_libxc.o fake_libxc.c fake_libxc.c:41: error: conflicting types for ‘xc_evtchn_notify’ ../../tools/libxc/xenctrl.h:692: error:

Hi I am tring to build the testcode for xenstored # cd xen-3.1-src/tools/xenstore/ # make testcode but it generating error due to conflict of function in fake_libxc with libxc. Error: gcc -Werror -Wp,-MD,.fake_libxc.o.d -I../../tools/libxc -I. -DTESTING -c -o fake_libxc.o fake_libxc.c fake_libxc.c:41: error: conflicting types for ‘xc_evtchn_notify’ ../../tools/libxc/xenctrl.h:692: error:

hi,everybody There is a function do_IRQ() in file xen/arch/x86/irq.c, but where does do_IRQ() be called please? Thanks! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Interesting - the patch doesn't address this yet. It looks like we have a difference (maybe bug?) in how we handle Intel vs. AT&T inline assembly: https://godbolt.org/z/GQw9ED Suppose we're expanding an operand with an 'i' constraint, where the operand is given as, e.g. (i32* @Bar). If the inline assembly is in Intel dialect, this expands as "Bar" in AT&T syntax

This patch adds an implementation of the TCG BIOS extensions to the Bochs BIOS and enables logging of boot measurements using the previously implemented support for TCPA ACPI tables. A low-level driver for a TPM TIS device and an Atmel device is provided. The implemented specification is described here:

Hi, I notice `lli -print-machineinstrs -x86-asm-syntax=(att|intel)' both prefix registers with `%'. Is this right? I thought AT&T did this and Intel didn't. The GNU gas manual concurs. http://www.gnu.org/software/binutils/manual/gas-2.9.1/html_chapter/as_16.html Cheers, Ralph.

Hi all, I''ve been trying to understand the pci_setup function in hvmloader.c in Xen unstable. I''m kinda lost at Line 328. base = (resource->base + bar_sz - 1) & ~(bar_sz - 1) I''d appreciate if someone could explain to me why base is calculated this way. Specifically, I don''t understand the bitwise AND with the one''s complements of

I do recieve this error when building xen-unstable tree. gcc -O2 -fomit-frame-pointer -m32 -march=i686 -DNDEBUG -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wno-unused-value -Wdeclaration-after-statement -DVMXASSIST -nostdinc -fno-builtin -fno-common -iwithprefix include -Werror -Wno-pointer-arith -pipe -I/home/xen-unstable.hg/xen/include

The Intel version is just a clone of the AT&T version at this time. No one has yet taken the time to make it produce actual Intel syntax. Ralph Corderoy wrote: > Hi, > > I notice `lli -print-machineinstrs -x86-asm-syntax=(att|intel)' both > prefix registers with `%'. Is this right? I thought AT&T did this and > Intel didn't. The GNU gas manual concurs. >

Hi Jeff, > > I notice `lli -print-machineinstrs -x86-asm-syntax=(att|intel)' both > > prefix registers with `%'. Is this right? I thought AT&T did this > > and Intel didn't. The GNU gas manual concurs. > > > > http://www.gnu.org/software/binutils/manual/gas-2.9.1/html_chapter/as_16.html > > The Intel version is just a clone of the

We know. Someone offered to do the Intel version, but did little more than a huge cut and paste of the AT&T version and then lost interest. No one else has had the time or inclination to finish the (barely begun) job. Patches accepted :) Ralph Corderoy wrote: > Hi, > > >> It's a long way towards it: >> >> # AT&T. # Intel.

Hi, kubernetes-0.17.1-3 is in virt7-testing repo [1]. Please test and feedback. [1] http://cbs.centos.org/repos/virt7-testing/x86_64/os/Packages/ -- Navid Shaikh IRC: nshaikh

Hi, > It's a long way towards it: > > # AT&T. # Intel. > .text .text > .align 16 .align 16 > .globl main .globl main > .type main, @function > main: main: >

Keir, It''s a resending patch for the timeout mechanism to deal with the shared interrupt issue for vt-d enabled hvm guest. We modify the patch following your comments last time and make some other small fix: 1) We don''t touch the locking around the hvm_dpci_eoi(). 2) Remove the HZ from the TIME_OUT_PERIOD macro which may confuse others. 3) Add some

On Wed, Nov 20, 2013 at 8:55 PM, Stephen Checkoway <s at pahtak.org> wrote: > > This has come up before <https://groups.google.com/forum/#!topic/llvm-dev/vomnIQjefzA>. I don't recall if there was a resolution. > Thanks for the link, completely missed when googled the issue. I think no consensus was reached (I cannot find any commit in the repository addressing such