[Xen-devel] patch about "don't reset vcpu_info on a cancelled suspend"

2015-12-28 Thread Ouyangzhaowei (Charles)
Hi David, This patch has been applied to for-linus-4.1b, and we wonder if this patch will be applied to linux kernel, or does it still needs more test to apply to linux kernel? thanks On 2015.5.28 19:07, David Vrabel wrote: >> vcpu_info would be reset to wrong place on canceled suspend on PVOPS

[Xen-devel] Xen Debuggers

2015-12-28 Thread hanji unit
Hello, is there any supported way to attach a debugger to Xen 4.4.0, or does everyone just use the printf method? ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel

[Xen-devel] [PATCH 1/2] xenconfig: support parsing and formatting vif bandwidth

2015-12-28 Thread Jim Fehlig
Both xm and xl config have long supported specifying vif rate limiting, e.g. vif = [ 'mac=00:16:3E:74:3d:76,bridge=br0,rate=10MB/s' ] Add support for mapping rate to and from in the xenconfig parser and formatter. rate is mapped to the required 'average' attribute of the element, e.g. .

[Xen-devel] [PATCH 2/2] libxl: support vif outgoing bandwidth QoS

2015-12-28 Thread Jim Fehlig
The libxl_device_nic structure supports specifying an outgoing rate limit based on a time interval and bytes allowed per interval. In xl config a rate limit is specified as "/s@". INTERVAL is optional and defaults to 50ms. libvirt expresses outgoing limits by average (required), peak, burst, and f

[Xen-devel] [PATCH 0/2] Xen: Support vif outging bandwidth QoS

2015-12-28 Thread Jim Fehlig
Happy Holidays! :-) This small series adds support for specifying vif outgoing rate limits in Xen. The first patch adds support for converting rate limits between xl/xm config and domXML, along with introducing a test for the conversion logic. The second patch adds outgoing rate limiting to the li

Re: [Xen-devel] [PATCH RFC 1/3] x86/pvclock: add setter for pvclock_pvti_cpu0_va

2015-12-28 Thread Andy Lutomirski
On Mon, Dec 28, 2015 at 1:52 PM, Joao Martins wrote: > Right now there is only a pvclock_pvti_cpu0_va() which is defined on > kvmclock since: > > commit dac16fba6fc5 > ("x86/vdso: Get pvclock data from the vvar VMA instead of the fixmap") > > The only user of this interface so far is kvm. This com

Re: [Xen-devel] Debugging console

2015-12-28 Thread quizyjones
If you run with Debian and Grub 2 (which should be the case if you are running Squeeze), then you should edit /etc/default/grub as below:GRUB_CMDLINE_XEN="loglvl=all guest_loglvl=all com1=115200,8n1,0x3e8,5 console=com1,vga" GRUB_CMDLINE_LINUX="console=hvc0 earlyprintk=xen"The above setup of the

[Xen-devel] [PATCH RFC 3/3] xen/Kconfig: add XEN_TIME_VSYSCALL option

2015-12-28 Thread Joao Martins
This option enables support for pvclock vsyscall/vdso support on Xen. Default is off, since Xen doesn't expose yet the PVCLOCK_TSC_STABLE_BIT flag. Signed-off-by: Joao Martins --- arch/x86/xen/Kconfig | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/x86/xen/Kconfig b/arch/x86/xen/Kc

[Xen-devel] [PATCH RFC 0/3] x86/xen: pvclock vdso support

2015-12-28 Thread Joao Martins
Hey! This series proposes support for pvclock vdso under Xen: Patch 1 adds setting cpu 0 pvti page; Patch 2 registers the pvti page with Xen and sets it accordingly in pvclock and Patch 3 adds a Kconfig option since Xen doesn't yet support the PVCLOCK_TSC_STABLE_BIT flag. Though its support will p

[Xen-devel] [PATCH RFC 1/3] x86/pvclock: add setter for pvclock_pvti_cpu0_va

2015-12-28 Thread Joao Martins
Right now there is only a pvclock_pvti_cpu0_va() which is defined on kvmclock since: commit dac16fba6fc5 ("x86/vdso: Get pvclock data from the vvar VMA instead of the fixmap") The only user of this interface so far is kvm. This commit adds a setter function for the pvti page and moves pvclock_pvt

[Xen-devel] [PATCH RFC 2/3] x86/xen/time: setup vcpu 0 time info page

2015-12-28 Thread Joao Martins
In order to support pvclock vdso on xen we need to setup the time info page for vcpu 0 and register the page with Xen using the VCPUOP_register_vcpu_time_memory_area hypercall. This hypercall will also forcefully update the pvti which will set some of the necessary flags for vdso. Afterwards we che

[Xen-devel] [PATCH RFC 1/6] public/xen.h: add flags field to vcpu_time_info

2015-12-28 Thread Joao Martins
This field has two possible flags (as of latest pvclock ABI shared with KVM). flags: bits in this field indicate extended capabilities coordinated between the guest and the hypervisor. Specifically on KVM, availability of specific flags has to be checked in 0x4001 cpuid leaf. On Xen, we don't

[Xen-devel] [PATCH RFC 4/6] x86/time: refactor read_platform_stime()

2015-12-28 Thread Joao Martins
To fetch the last read from the clocksource which was used to calculate system_time. In the case of clocksource=tsc we will use it to set tsc_timestamp. Signed-off-by: Joao Martins --- xen/arch/x86/time.c | 16 ++-- 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/xen/a

[Xen-devel] [PATCH RFC 0/6] x86/time: PVCLOCK_TSC_STABLE_BIT support

2015-12-28 Thread Joao Martins
Hey! I've been working on pvclock vdso support on Linux guests, and came across Xen lacking support for PVCLOCK_TSC_STABLE_BIT flag which is required for vdso as of the latest pvclock ABI shared with KVM. In addition, I've found some problems which aren't necessarily visible to kernel as the pvcl

[Xen-devel] [PATCH RFC 6/6] x86/time: convert counter to tsc for non-tsc clocksource

2015-12-28 Thread Joao Martins
This commit is an attempt at suporting PVCLOCK_TSC_STABLE_BIT when using other clocksources. master_tsc_stamp is set by converting master_stime (returned from read_platform_stime()) and converting it to a TSC by scaling the ns value accordingly. We scale the system time if TSC is reliable, and und

[Xen-devel] [PATCH RFC 2/6] x86/time: implement tsc as clocksource

2015-12-28 Thread Joao Martins
Introduce support for using TSC as platform time which is the highest resolution time and most performant to get (~20 nsecs). Though there are also several problems associated with its usage, and there isn't a complete (and architecturally defined) guarantee that all machines will provide reliable

[Xen-devel] [PATCH RFC 5/6] x86/time: implement PVCLOCK_TSC_STABLE_BIT

2015-12-28 Thread Joao Martins
When using TSC as clocksource we will solely rely on TSC for updating vcpu time infos (pvti). Right now, each vCPU takes the tsc_timestamp at different instants meaning every EPOCH + delta. This delta is variable depending on the time the CPU calibrates with CPU 0 (master), and will likely be diffe

[Xen-devel] [PATCH RFC 3/6] x86/time: streamline platform time init on plt_init()

2015-12-28 Thread Joao Martins
And use to initialize platform time solely for clocksource=tsc, as opposed to initializing platform overflow timer, which would only fire in ~180 years (on 2.2 Ghz Broadwell processor). Signed-off-by: Joao Martins --- xen/arch/x86/time.c | 41 + 1 file cha

[Xen-devel] Debugging console

2015-12-28 Thread Carl Patenaude Poulin
Hi all, We've got __HYPERVISOR_console_io working on our unikernel! The only issue is that it prints to `xl dmesg`. Is there a way to get it to print to `xl console`? Best Carl Patenaude Poulin McGill University ___ Xen-devel mailing list Xen-devel@lis

[Xen-devel] [nested xen]how to correspond a cr3 to specific vm or pid?

2015-12-28 Thread quizyjones
Hello, recently I'm looking into the code of nested xen under /xen/arch/x86/mm/hap, here are some questions which I hope to get help from you. 1. About nested ept. Is the memory translation process like this: L2 VA --> L2 PT --> L2 PA --> L1 EPT --> L1 VA --> L1 PT --> L0 EPT --> MA? What's the

[Xen-devel] [distros-debian-sid test] 38567: tolerable FAIL

2015-12-28 Thread Platform Team regression test user
flight 38567 distros-debian-sid real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/38567/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-armhf-armhf-armhf-sid-netboot-pygrub 9 debian-di-install fail like 38546 test-amd64-i386-amd

Re: [Xen-devel] Coverity tidying

2015-12-28 Thread Andrew Cooper
On 28/12/15 05:16, Joshua Otto wrote: On Mon, Dec 14, 2015 at 11:08:43AM +, Ian Campbell wrote: On Sat, 2015-12-12 at 17:07 -0500, Joshua Otto wrote: On Fri, Dec 11, 2015 at 01:52:41PM +, Ian Campbell wrote: Cool! Just to be clear, you are looking for one project for the 3 of you to