>>> "Tian, Kevin" 12/04/15 2:49 AM >>>
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Thursday, December 03, 2015 9:16 PM
>> >>> On 03.12.15 at 09:09, wrote:
>> > If impacted domain is Dom0 or hardware domain, just throw out a
>> > warning.
>> > It's an open here whether we want to
flight 65336 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65336/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf e04671e81a7fe842f640a926171048e5524b46e0
baseline version:
ovmf dcb2e4bb61931e2dee1739bb76aba315002
On 11/26/2015 09:59 AM, Ian Campbell wrote:
> libxlConnectDomainXMLFromNative calls both xenParseXM and xenParseXL
> with cfg->verInfo->xen_version_major, however AFAICT they both (either
> inherently, or through there use of xenParseConfigCommon expect a
> value from xenConfigVersionEnum (which do
On December 04, 2015 at 9:52 AM, wrote:
> > From: Xu, Quan
> > Sent: Thursday, December 03, 2015 4:09 PM
> >
> > If IOTLB/Context/IETC flush is timeout, we should think all devices
> > under this IOMMU cannot function correctly.
> > So for each device under this IOMMU we'll mark it as unassignable
flight 65327 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65327/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 16
guest-localmigrate/x10 fail in 65210 RE
Hi folks,
On page 12 of "The Definitive Guide to the Xen Hypervisor", it is mentioned
that "Xen, like Linux, uses the MS-DOS calling convention, rather than the
UNIX convention used by FreeBSD."
I keep digging online and I can't find any information about an "MS-DOS
calling convention". We've alr
This run is configured for baseline tests only.
flight 38425 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38425/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf dcb2e4bb61931e2dee1739bb76aba315002f0a82
baseline version:
ovm
flight 65323 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65323/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 guest-localmigrate
fail REGR. vs
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Thursday, December 03, 2015 7:19 PM
>
> On 03/12/15 08:50, Tian, Kevin wrote:
> >> From: Jan Beulich [mailto:jbeul...@suse.com]
> >> Sent: Thursday, December 03, 2015 4:18 PM
> >>
> > On 03.12.15 at 03:40, wrote:
> >>> Just conf
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Thursday, December 03, 2015 7:24 PM
>
> On 03/12/15 01:19, Tian, Kevin wrote:
> >> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> >> Sent: Thursday, November 26, 2015 9:56 PM
> >>
> >> On 26/11/15 13:48, Malcolm Crossley wr
> From: Xu, Quan
> Sent: Thursday, December 03, 2015 4:09 PM
>
> If IOTLB/Context/IETC flush is timeout, we should think
> all devices under this IOMMU cannot function correctly.
> So for each device under this IOMMU we'll mark it as
> unassignable and kill the domain owning the device.
>
> If De
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, December 03, 2015 9:16 PM
>
> >>> On 03.12.15 at 09:09, wrote:
> > If impacted domain is Dom0 or hardware domain, just throw out a warning.
> > It's an open here whether we want to kill
> > Dom0 or hardware domain (or direct
> From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
> Sent: Wednesday, December 02, 2015 12:50 AM
>
> It was lost when vpmu* files were moved from xen/arch/x86/hvm/{vmx|svm}/ to
> xen/arch/x86/cpu/
>
> Signed-off-by: Boris Ostrovsky
> Cc: ian.campb...@citrix.com
> Cc: ian.jack...@eu.citr
> From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
> Sent: Thursday, December 03, 2015 11:47 PM
>
> On 12/03/2015 01:18 AM, Tian, Kevin wrote:
> >> From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
> >> Sent: Wednesday, December 02, 2015 12:50 AM
> >>
> >> We only support family 6
> From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
> Sent: Wednesday, December 02, 2015 12:50 AM
>
> We need to have at least version 2 since it's the first version to
> support various control and status registers (such as
> MSR_CORE_PERF_GLOBAL_CTRL) that VPMU relies on always having.
>
> From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
> Sent: Thursday, December 03, 2015 11:45 PM
>
> On 12/03/2015 06:02 AM, Jan Beulich wrote:
> On 03.12.15 at 11:46, wrote:
> >>> From: Jan Beulich [mailto:jbeul...@suse.com]
> >>> Sent: Thursday, December 03, 2015 6:36 PM
> >>>
>
flight 65324 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65324/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-pair 21 guest-migrate/src_host/dst_host fail REGR.
vs. 63340
test-amd64-i386-l
flight 65320 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65320/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-vhd 6 xen-boot fail REGR. vs. 64579
Regressions which a
This run is configured for baseline tests only.
flight 38423 qemu-upstream-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38423/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-pygrub 10 guest
On 12/01/15 06:28, Paul Durrant wrote:
>> -Original Message-
>> From: xen-devel-boun...@lists.xen.org [mailto:xen-devel-
>> boun...@lists.xen.org] On Behalf Of Don Slutz
>> Sent: 28 November 2015 21:45
>> To: xen-devel@lists.xen.org
>> Cc: Jun Nakajima; Wei Liu; Kevin Tian; Keir (Xen.org);
flight 65335 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65335/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 13
On 12/03/2015 06:48 PM, Jim Fehlig wrote:
> Joao Martins wrote:
>> Introduces support for domainGetJobStats which has the same
>> info as domainGetJobInfo but in a slightly different format.
>> Another difference is that virDomainGetJobStats can also
>> retrieve info on the most recently complete
On 12/02/2015 11:27 PM, Jim Fehlig wrote:
> On 11/10/2015 08:32 AM, Joao Martins wrote:
>> Introduce support for VIR_MIGRATE_PEER2PEER in libxl driver
>> for supporting migration in Openstack. Most of the changes
>> occur at the source and no modifications at the receiver.
>>
>> In P2P mode there
Joao Martins wrote:
> Introduces support for domainGetJobStats which has the same
> info as domainGetJobInfo but in a slightly different format.
> Another difference is that virDomainGetJobStats can also
> retrieve info on the most recently completed job. Though so
> far this is only used in the so
flight 65314 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65314/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-qemuu-nested-intel 16 debian-hvm-install/l1/l2 fail REGR. vs.
65114
test-armhf-ar
On 03/12/15 06:22, Ian Campbell wrote:
In particular around error handling, behaviour on fork and the unmap
notification mechanism.
Behaviour of xengnttab_map_*grant_refs and xengntshr_share_pages on
partial failure has been confirmed/inferred (by inspection) on Linux
and Mini-os (the only two k
flight 65319 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65319/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf dcb2e4bb61931e2dee1739bb76aba315002f0a82
baseline version:
ovmf c972495ed0a939ed30f5ab5fa14f215b8bb
flight 65332 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65332/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-xl 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 13
Ian Campbell writes ("[PATCH OSSTEST] cr-try-bisect-adhoc: Add a reminder about
OSSTEST_EMAIL_HEADER"):
> ... I'm forever spamming Ian J for a couple of iterations when I set
> one of these up and forget to override the default destination.
Acked-by: Ian Jackson
On Thu, Dec 03, 2015 at 10:06:02PM +0530, kumara rathnavel wrote:
> Hello All,
>
Hello
>
> I am not able to run Xentrace. I am using FreeBSD as Dom0. I have given
> size and event in command line parameters during boot also.
>
> Please help me !!!
>
> Thankyou in Advance
Have you checked
If a guest allocates a page and the tlbflush_timestamp on the page
indicates that a TLB flush of the previous owner is required, only the
linear and combined mappings are invalidated. The guest-physical
mappings are not invalidated.
This is currently safe because the EPT code ensures that the
gue
From: David Vrabel
Holding the p2m lock while calling ept_sync_domain() is very expensive
since it does a on_selected_cpus() call. IPIs on many socket machines
can be very slows and on_selected_cpus() is serialized.
Defer the invalidate until the p2m lock is released. Since the processor
may c
This series improves the performance of EPT by further reducing the
impact of the translation invalidations (ept_sync_domain()). By:
a) Deferring invalidations until the p2m write lock is released.
Prior to this change a 16 VCPU guest could not be successfully
migrated on an (admittedly slow) 160
Ian Campbell writes ("[PATCH OSSTEST] standalone: Log things we are running via
with_logging"):
> Turning on set -x is too verbose, so just echo the command ourselves.
It's not clear to me from the context whether $@ might contain things
which would require quoting. set -x would quote them.
You
Hello All,
I am not able to run Xentrace. I am using FreeBSD as Dom0. I have given
size and event in command line parameters during boot also.
Please help me !!!
Thankyou in Advance
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.x
On 12/2/15 4:39 AM, Ian Campbell wrote:
> On Tue, 2015-12-01 at 04:00 -0700, Jan Beulich wrote:
>> But not forking doesn't mean importing the whole directory. Some
>> Makefile adjustments will be necessary anyway, so removing some
>> of the frontends wouldn't make things worse. We indeed should
>>
On 02/12/15 07:14, Tian, Kevin wrote:
>> From: David Vrabel [mailto:david.vra...@citrix.com]
>> Sent: Saturday, November 14, 2015 2:50 AM
>>
>> This RFC series improves the performance of EPT by reducing the impact
>> of the translation invalidations (ept_sync_domain()). Two approaches
>> are used
On 12/03/2015 01:18 AM, Tian, Kevin wrote:
From: Boris Ostrovsky [mailto:boris.ostrov...@oracle.com]
Sent: Wednesday, December 02, 2015 12:50 AM
We only support family 6 so quirk handling is always needed.
what about you adding other family support in the future then you'll
add back below quirk
On 12/03/2015 06:02 AM, Jan Beulich wrote:
On 03.12.15 at 11:46, wrote:
From: Jan Beulich [mailto:jbeul...@suse.com]
Sent: Thursday, December 03, 2015 6:36 PM
On 03.12.15 at 07:16, wrote:
From: Dietmar Hahn [mailto:dietmar.h...@ts.fujitsu.com]
Sent: Wednesday, December 02, 2015 5:21 PM
Turning on set -x is too verbose, so just echo the command ourselves.
Signed-off-by: Ian Campbell
---
standalone | 1 +
1 file changed, 1 insertion(+)
diff --git a/standalone b/standalone
index c804b74..6897400 100755
--- a/standalone
+++ b/standalone
@@ -195,6 +195,7 @@ with_logging() {
i
... I'm forever spamming Ian J for a couple of iterations when I set
one of these up and forget to override the default destination.
Signed-off-by: Ian Campbell
---
In reality I usually just cowboy into daily-cron-email-adhoc* in
adhoc.git, but in the future I should do this instead I reckon.
---
On Mon, 2015-11-16 at 11:37 +, Ian Campbell wrote:
> On Fri, 2015-11-13 at 12:41 +, Andrew Cooper wrote:
> > On 13/11/15 11:05, Roger Pau Monne wrote:
> > > With the addition of HVMlite the hypervisor now always requires a
> > > non-
> > > null
> > > arch domain config, which is different b
On 03/12/15 11:23, Vitaly Kuznetsov wrote:
> David Vrabel writes:
>
>> Adding the rtc platform device when there are no legacy irqs (no
>> legacy PIC)
>
> No PIC != No legacy IRQs, Hyper-V Gen2 represents such a platform (and
> it has RTC on irq8). I've tested this patch against it and it appear
This makes adhoc bisects slightly more important than smoke tests, on
the basis that a smoke test can choose another host while an adhoc
bisect cannot.
Document this is README.planner and while there make a note of the
usage of OSSTEST_RESOURCE_WAITSTART by cr-try-bisect.
Signed-off-by: Ian Campb
On 03.12.2015 at 9:16am, wrote:
> >>> On 03.12.15 at 09:09, wrote:
> > If impacted domain is Dom0 or hardware domain, just throw out a
> warning.
> > It's an open here whether we want to kill
> > Dom0 or hardware domain (or directly panic hypervisor). Comments
> > are welcomed.
>
> I th
flight 65306 qemu-upstream-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65306/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-libvirt-vhd 9 debian-di-installfail like 65053
Tests which did not
flight 38422 distros-debian-wheezy real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38422/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-amd64-wheezy-netboot-pygrub 9 debian-di-install fail blocked
in 38352
baseline
>>> On 27.11.15 at 14:43, wrote:
> +int arch_set_info_hvm_guest(struct vcpu *v, const vcpu_hvm_context_t *ctx)
> +{
> +struct cpu_user_regs *uregs = &v->arch.user_regs;
> +struct segment_register cs, ds, ss, es, tr;
> +const char *errstr;
> +int rc;
> +
> +if ( ctx->pad != 0 )
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, December 3, 2015 7:19 PM
> To: Wu, Feng
> Cc: xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] [PATCH v10 0/7] Add VT-d Posted-Interrupts support
>
> >>> On 03.12.15 at 09:35, wrote:
> > VT-d Posted
>>> On 03.12.15 at 09:09, wrote:
> If impacted domain is Dom0 or hardware domain, just throw out a warning.
> It's an open here whether we want to kill
> Dom0 or hardware domain (or directly panic hypervisor). Comments are
> welcomed.
I think that's a reasonable default, provided by tha
>>> On 03.12.15 at 13:52, wrote:
> On 11/30/15 9:18 AM, Jan Beulich wrote:
> On 24.11.15 at 18:52, wrote:
>>> ---
>>> xen/arch/x86/Kconfig | 7 +++
>>> 1 file changed, 7 insertions(+)
>>
>> This can't be complete - you ought to be deleting the current definition.
>
> I don't understand
On 03/12/15 12:47, Jan Beulich wrote:
On 03.12.15 at 12:41, wrote:
>> On 03/12/15 11:41, Jan Beulich wrote:
>> On 03.12.15 at 12:02, wrote:
--- a/xen/arch/arm/vgic-v2.c
+++ b/xen/arch/arm/vgic-v2.c
@@ -315,11 +315,10 @@ static int vgic_v2_distr_mmio_write(struct vcpu *v,
On 11/30/15 9:18 AM, Jan Beulich wrote:
On 24.11.15 at 18:52, wrote:
>> ---
>> xen/arch/x86/Kconfig | 7 +++
>> 1 file changed, 7 insertions(+)
>
> This can't be complete - you ought to be deleting the current definition.
I don't understand?
>
>> --- a/xen/arch/x86/Kconfig
>> +++ b/x
On 03/12/15 11:21, Ian Campbell wrote:
> As far as I can tell there is no requirement for these and it builds
> fine without them.
>
> Signed-off-by: Ian Campbell
Sorry - my fault.
This will be because of c/s b15bc4345e "tools/libxc: Remove legacy
migration implementation" where I ended up movin
>>> On 03.12.15 at 12:41, wrote:
> On 03/12/15 11:41, Jan Beulich wrote:
> On 03.12.15 at 12:02, wrote:
>>> --- a/xen/arch/arm/vgic-v2.c
>>> +++ b/xen/arch/arm/vgic-v2.c
>>> @@ -315,11 +315,10 @@ static int vgic_v2_distr_mmio_write(struct vcpu *v,
> mmio_info_t *info)
>>> return 0;
flight 65303 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/65303/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-winxpsp3 6 xen-boot fail REGR. vs. 59254
test-amd64-i386-qemut
> On 3 Dec 2015, at 11:22, Ian Campbell wrote:
>
> xtl doesn't require the full LDLIBS_libxenctrl, just the -L and
> xenlight.cmxa, the latter which contains LDLIBS_libxenctrl as needed.
> Fixing this avoids the need to be concerned about LDLIBS_libxenctrl
> becoming more than one word in the fu
On 03/12/15 11:41, Jan Beulich wrote:
On 03.12.15 at 12:02, wrote:
>> --- a/xen/arch/arm/vgic-v2.c
>> +++ b/xen/arch/arm/vgic-v2.c
>> @@ -315,11 +315,10 @@ static int vgic_v2_distr_mmio_write(struct vcpu *v,
>> mmio_info_t *info)
>> return 0;
>>
>> case GICD_ICACTIVER ... GIC
>>> On 03.12.15 at 12:02, wrote:
> --- a/xen/arch/arm/vgic-v2.c
> +++ b/xen/arch/arm/vgic-v2.c
> @@ -315,11 +315,10 @@ static int vgic_v2_distr_mmio_write(struct vcpu *v,
> mmio_info_t *info)
> return 0;
>
> case GICD_ICACTIVER ... GICD_ICACTIVERN:
> -if ( dabt.size != DAB
Hi Stefano,
On 03/12/15 11:02, Stefano Stabellini wrote:
> Injecting a fault to the guest just because it is writing to one of the
> GICD_ICACTIVER registers, which are part of the GICv2 and GICv3 specs,
> is harsh. Additionally it causes recent linux kernels to fail to boot on
> Xen.
>
> Ignore
libxengnttab has just been split out from libxc. From mini-os's point
of view we don't care about the distinction, so keep things simple by
just including libxengnttab if libxc is enabled.
Signed-off-by: Ian Campbell
Acked-by: Samuel Thibault
Acked-by: Wei Liu
---
v2: Adjust for libs/$lib layou
libxenevtchn has just been split out from libxc. From mini-os's point
of view we don't care about the distinction, so keep things simple by
just including libxenevtchn if libxc is enabled.
Signed-off-by: Ian Campbell
Acked-by: Samuel Thibault
Acked-by: Wei Liu
---
v2: Adjust for libs/$lib layou
David Vrabel writes:
> Adding the rtc platform device when there are no legacy irqs (no
> legacy PIC)
No PIC != No legacy IRQs, Hyper-V Gen2 represents such a platform (and
it has RTC on irq8). I've tested this patch against it and it appears to
work because the device is present in ACPI and we
libxenforeignmemory has just been split out from libxc. From mini-os's
point of view we don't care about the distinction, so keep things
simple by just including libxenforeignmemory if libxc is enabled.
Signed-off-by: Ian Campbell
Acked-by: Samuel Thibault
Acked-by: Wei Liu
---
v2: Adjust for l
On 03/12/15 01:19, Tian, Kevin wrote:
>> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
>> Sent: Thursday, November 26, 2015 9:56 PM
>>
>> On 26/11/15 13:48, Malcolm Crossley wrote:
>>> On 26/11/15 13:46, Jan Beulich wrote:
>>> On 25.11.15 at 11:28, wrote:
> The problem is that San
libxencall has just been split out from libxc. From mini-os's point
of view we don't care about the distinction, so keep things simple by
just including libxencall if libxc is enabled.
Signed-off-by: Ian Campbell
Acked-by: Samuel Thibault
Acked-by: Wei Liu
---
v2: Adjust for libs/$lib layout.
-
libxenctrl links against this library
Signed-off-by: Ian Campbell
Acked-by: Ian Jackson
---
v3: Library moved to tools/libs
---
xen-hooks.mak | 1 +
1 file changed, 1 insertion(+)
diff --git a/xen-hooks.mak b/xen-hooks.mak
index 179a6b7..229d642 100644
--- a/xen-hooks.mak
+++ b/xen-hooks.mak
@
We intend to stabilise some parts of the libxenctrl interface by
splitting out some functionality into separate stable libraries.
This is the mini-os part of the first phase of that change.
This mail is (or is intended to be) a reply to a "0/"
super-intro mail covering all of the related patch se
/dev/xen/gntdev related wrappers have been moved out of libxenctrl
into their own library.
Signed-off-by: Ian Campbell
Acked-by: Ian Jackson
---
v3: Library moved to tools/libs/
---
hw/xen_backend.c | 4 ++--
hw/xen_backend.h | 2 +-
hw/xen_common.h | 1 +
hw/xen_console.c | 4 ++--
hw/xen
Using an existing libxenctrl handle after a fork was never
particularly safe (especially if foreign mappings existed at the time
of the fork) and the xc fd has been unavailable for many releases.
Reopen the handle after fork and therefore do away with xc_fd().
Signed-off-by: Ian Campbell
Acked-b
In Xen 4.7 we are refactoring parts libxenctrl into a number of
separate libraries which will provide backward and forward API and ABI
compatiblity.
Specifically libxenevtchn, libxengnttab and libxenforeignmemory.
Previous patches have already laid the groundwork for using these by
switching the
libxentoollog has just been split out from libxc. From mini-os's point
of view we don't care about the distinction, so keep things simple by
just including libxentoollog if libxc is enabled.
Signed-off-by: Ian Campbell
Acked-by: Samuel Thibault
Acked-by: Wei Liu
---
v2: Adjust for libs/$lib lay
In Xen 4.7 we are refactoring parts libxenctrl into a number of
separate libraries which will provide backward and forward API and ABI
compatiblity.
One such library will be libxenforeignmemory which provides access to
privileged foreign mappings and which will provide an interface
equivalent to x
This has been split out of libxenctrl, so the build needs to be able
to find the header and the library. QEMU does not use xtl_* itself so
-rpath-link is sufficient to allow linking to libxenctrl.so (which
links against libxentoollog).
Signed-off-by: Ian Campbell
Acked-by: Ian Jackson
---
v3: L
libxenctrl links against this library.
Also, request the compat xc_map_foreign API from libxc.
Signed-off-by: Ian Campbell
Acked-by: Ian Jackson
---
v3: Library moved to tools/libs/
---
xen-hooks.mak | 2 ++
1 file changed, 2 insertions(+)
diff --git a/xen-hooks.mak b/xen-hooks.mak
index 229d
libxencall will provide a stable API and ABI for calling hypercalls
(although those hypercalls themselves may not have a stable API). As
well as the hypercall buffer infrastructure needed in order to safely
provide pointer arguments to hypercalls.
libxenctrl encapsulates a instance of this interfa
In Xen 4.7 we are refactoring parts libxenctrl into a number of
separate libraries which will provide backward and forward API and ABI
compatiblity.
One such library will be libxenevtchn which provides access to event
channels.
In preparation for this switch the compatibility layer in xen_common.
In Xen 4.7 we are refactoring parts libxenctrl into a number of
separate libraries which will provide backward and forward API and ABI
compatiblity.
One such library will be libxenforeignmemory which provides access to
privileged foreign mappings and which will provide an interface
equivalent to x
This means adding -L for libxen{evtchn,gnttab,foreignmemory} so that
it can link them directly (rather than using the libxenctrl compat
layer exposed via -rpath-link). Also add -I for libxenforeignmemory.
Signed-off-by: Ian Campbell
Acked-by: Wei Liu
---
tools/Makefile | 4
1 file changed,
Use pthread_atfork to prevent the application from forking before the
madvisoe(), which would result in CoW mappings getting passed to
hypercalls.
(largely cribbed from libxl_fork.c)
Signed-off-by: Ian Campbell
---
v6: New
---
tools/libs/call/buffer.c | 2 +-
tools/libs/call/linux.c | 66
In Xen 4.7 we are refactoring parts libxenctrl into a number of
separate libraries which will provide backward and forward API and ABI
compatiblity.
One such library will be libxengnttab which provides access to grant
tables.
In preparation for this switch the compatibility layer in xen_common.h
/dev/xen/evtchn related wrappers have been moved out of libxenctrl
into their own library.
Note that i386-dm/helper2.c's xc_interface * was always really an
xc_evtchn *, it's just they used to be typedefs to the same thing...
Signed-off-by: Ian Campbell
Acked-by: Ian Jackson
---
v3: Library mov
We intend to stabilise some parts of the libxenctrl interface by
splitting out some functionality into separate stable libraries.
This is the qemu-xen-traditional part of the first phase of that change.
This mail is (or is intended to be) a reply to a "0/"
super-intro mail covering all of the rel
Until the previous patch this relied on xc_fd(), which was only
implemented for Xen 4.0 and earlier.
Given this wasn't working since Xen 4.0 I have marked this as disabled
by default.
Removing this support drops the use of a bunch of symbols from
libxenctrl, specifically:
- xc_domain_create
All of the work in con_disconnect applies to the primary console case
(when xendev->dev is NULL). Therefore remove the early check and bail
and allow it to fall through. All of the existing code is correctly
conditional already.
The ->dev and ->gnttabdev handles are either both set or neither. For
We stick with using FD_CLOEXEC on the legacy /proc/xen/privcmd
fallback device since it was present in older kernel where O_CLOEXEC
may not be assured.
Signed-off-by: Ian Campbell
---
v6: New
---
tools/libs/call/linux.c | 57 -
1 file changed, 37 i
We intend to stabilise some parts of the libxenctrl interface by
splitting out some functionality into separate stable libraries.
This is the qemu-xen part of the first phase of that change.
This mail is (or is intended to be) a reply to a "0/"
super-intro mail covering all of the related patch s
Signed-off-by: Ian Campbell
Acked-by: Wei Liu
---
tools/libs/call/linux.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tools/libs/call/linux.c b/tools/libs/call/linux.c
index 55e1e83..3641e41 100644
--- a/tools/libs/call/linux.c
+++ b/tools/libs/call/linux.c
@@ -94,7 +
These are already arch specific, so just use the appropriate
interfaces (as determined by looking at the xc_memalign backend).
Signed-off-by: Ian Campbell
Acked-by: Wei Liu
---
tools/libs/call/netbsd.c | 4 ++--
tools/libs/call/solaris.c | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
From: Roger Pau Monne
With the addition of HVMlite the hypervisor now always requires a non-null
arch domain config, which is different between HVM and PV guests.
Add a new parameter to xc_domain_create that contains a pointer to an arch
domain config. If the pointer is null, create a default ar
xtl doesn't require the full LDLIBS_libxenctrl, just the -L and
xenlight.cmxa, the latter which contains LDLIBS_libxenctrl as needed.
Fixing this avoids the need to be concerned about LDLIBS_libxenctrl
becoming more than one word in the future.
Since the tests are pure ocaml (no C components) CFLA
These were wrong in the context of libxc before this code was
extracted, clean them up.
Also add some emacs magic blocks
Signed-off-by: Ian Campbell
Acked-by: Wei Liu
---
tools/libs/call/buffer.c | 4 ++--
tools/libs/call/core.c| 2 +-
tools/libs/call/minios.c
This behaviour has been confirmed by inspection on:
- Linux
- FreeBSD (NB: hcall->retval is the hypercall return value only for
values >= 0. For negative values the underlying privcmd driver
translates the value from Xen to FreeBSD errno space and returns it as
the result of the ioctl,
In tree libraries which link against other in tree libraries in a way
which is opaque to their callers need special handling, specifically
correct use of -Wl,-rpath-link for the recusively used libraries.
Currently this is rather simple, but up coming changes are going to
introduce transitive depe
Surprisingly it appears no callers need updating.
Signed-off-by: Ian Campbell
Acked-by: Wei Liu
Acked-by: Ian Jackson
---
v4: New patch
---
tools/libs/foreignmemory/compat.c | 2 +-
tools/libs/foreignmemory/freebsd.c | 4 ++--
.../libs/foreignmemory/include/x
v4: Config.mk instead of .config
---
Config.mk | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/Config.mk b/Config.mk
index 64fcf1b..09c6e80 100644
--- a/Config.mk
+++ b/Config.mk
@@ -242,20 +242,20 @@ endif
ifeq ($(GIT_HTTP),y)
OVMF_UPSTREAM_URL ?= http:/
In particular around error handling, behaviour on fork and the unmap
notification mechanism.
Behaviour of xengnttab_map_*grant_refs and xengntshr_share_pages on
partial failure has been confirmed/inferred (by inspection) on Linux
and Mini-os (the only two known implementations. Likewise the
behavi
libxengnttab will provide a stable API and ABI for accessing the
grant table devices.
The functions are moved into the xengnt{tab,shr} namespace to make a
clean break from libxc and avoid ambiguity regarding which interfaces
are stable.
All in-tree users are updated to use the new names.
Upon re
We intend to stabilise some parts of the libxenctrl interface by
splitting out some functionality into separate stable libraries.
This is the xen part of the first phase of that change.
This mail is (or is intended to be) a reply to a "0/"
super-intro mail covering all of the related patch series
In attempting to disaggregate libxenctrl I found that many of the
pieces were going to want access to this library, so split it out (as
it probably should always have been).
Various build adjustments are needed. In particular things which use
xtl_* themselves now need to explicity link against the
1 - 100 of 163 matches
Mail list logo
