On 05/23/2018 10:48 PM, Manish Jaggi wrote:
Hi Sameer,
General Comment, please use appropriate variable names for XXX_domain
structures in code which is xen specific.
I thought that we had discussed this before on one of the RFCs. At this
point we are just using the format used for smmu-v2.
flight 123075 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/123075/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-i386 14 guest-saverestore fail REGR. vs. 122357
test-amd64-i386-f
On Thu, May 24, 2018 at 1:16 PM Steven Rostedt wrote:
> On Thu, 24 May 2018 13:40:24 +0200
> Petr Mladek wrote:
> > On Wed 2018-05-23 12:54:15, Thomas Garnier wrote:
> > > When using -fPIE/PIC with function tracing, the compiler generates a
> > > call through the GOT (call *__fentry__@GOTPCREL)
flight 123101 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/123101/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 77ca824c652443bdf3edaa0bb109fd8225a71cd3
baseline version:
ovmf 1e35fcc9ee8b6b991535d
Hey Linus,
Please git pull the following branch in your tree:
git pull git://git.kernel.org/pub/scm/linux/kernel/git/konrad/swiotlb.git
stable/for-linus-4.17
There is one single fix in there - that is under Xen the DMA32 heap
(in the hypervisor) would end up looking like swiss cheese. The reaso
On 05/24/2018 04:27 AM, Ian Jackson wrote:
Ian Jackson writes ("Likely build race, "/usr/bin/ld: cannot find -lvirt""):
tl;dr:
I think there is a bug in libvirt's build system which, with
low probability, causes a build failure containing this message:
/usr/bin/ld: cannot find -lvirt
Comple
flight 74740 distros-debian-wheezy real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74740/
Perfect :-)
All tests in this flight passed as required
baseline version:
flight 74722
jobs:
build-amd64 pass
build-armh
flight 123079 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/123079/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-credit2 broken
test-armhf-armhf-xl-credit2 4 host-insta
This run is configured for baseline tests only.
flight 74739 linux-3.18 real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74739/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-examine 11 examine-serial/bo
This run is configured for baseline tests only.
flight 74741 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/74741/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 77ca824c652443bdf3edaa0bb109fd8225a71cd3
baseline v
Hi there
I'm trying to apply xsa263 patches, specifically for 4.10. However they
dont seem to on top of 4.10.1 release.
I see they do apply cleanly to current 4.10 staging branch. Are staging
trees for stable branches like 4.10 considered suitable/safe to rebase
to for packaging purposes? ie
Hi,
This series implements a new xl config entry. Users can use the new
config entry to statically setup shared memory areas among VMs that
don't have grant table support so that they could communicate with each
other through the static shared memory areas.
It was originally developed by Zhongze,
From: Zhongze Liu
Author: Zhongze Liu
The existing XENMAPSPACE_gmfn_foreign subop of XENMEM_add_to_physmap forbids
a Dom0 to map memory pages from one DomU to another, which restricts some useful
yet not dangerous use cases -- such as sharing pages among DomU's so that they
can do shm-based com
From: Zhongze Liu
Author: Zhongze Liu
Add libxl__sshm_del to unmap static shared memory areas mapped by
libxl__sshm_add during domain creation. The unmapping process is:
* For a master: decrease the refcount of the sshm region, if the refcount
reaches 0, cleanup the whole sshm path.
* For a
From: Zhongze Liu
Author: Zhongze Liu
Add docs to document the motivation, usage, use cases and other
relevant information about the static shared memory feature.
This is for the proposal "Allow setting up shared memory areas between VMs
from xl config file". See:
https://lists.xen.org/arch
From: Zhongze Liu
Author: Zhongze Liu
Add a new structure to the IDL family to represent static shared memory regions
as proposed in the proposal "Allow setting up shared memory areas between VMs
from xl config file" (see [1]).
And deleted some trailing white spaces.
[1] https://lists.xen.org
From: Zhongze Liu
Author: Zhongze Liu
Add libxl__sshm_add to map shared pages from one DomU to another, The mapping
process involves the following steps:
* Set defaults and check for further errors in the static_shm configs:
overlapping areas, invalid ranges, duplicated master domain,
From: Zhongze Liu
Author: Zhongze Liu
Add the parsing utils for the newly introduced libxl_static_sshm struct
to the libxl/libxlu_* family. And add realated parsing code in xl to
parse the struct from xl config files. This is for the proposal "Allow
setting up shared memory areas between VMs fr
flight 123086 xen-4.10-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/123086/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-pvhv2-intel 12 guest-start fail never pass
test-amd64-amd64-xl-pvhv2-amd 12
On 05/25/2018 01:59 AM, Sameer Goel wrote:
On 05/23/2018 10:48 PM, Manish Jaggi wrote:
Hi Sameer,
General Comment, please use appropriate variable names for XXX_domain
structures in code which is xen specific.
I thought that we had discussed this before on one of the RFCs.
Yes and no one
On 24/05/18 16:07, Andrew Cooper wrote:
> This helps debug #DF's which occur in alternative patches
>
> Reported-by: George Dunlap
> Signed-off-by: Andrew Cooper
Release-acked-by: Juergen Gross
Juergen
___
Xen-devel mailing list
Xen-devel@lists.xe
On 05/23/2018 02:46 PM, Juergen Gross wrote:
On 23/05/18 13:36, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Building for a 32-bit target results in warnings from casting
between a 32-bit pointer and a 64-bit integer. Fix the warnings
by casting those pointers to uintptr_t firs
We should index an L1 table with an L1 index.
Reported-by: Simon Gaiser
Signed-off-by: Jan Beulich
---
v2: Entirely different.
--- a/xen/arch/x86/smpboot.c
+++ b/xen/arch/x86/smpboot.c
@@ -883,7 +883,7 @@ static void cleanup_cpu_root_pgt(unsigne
l2_pgentry_t *l2t = l3e_to_l2e(l3t[l3_ta
At 12:20 +0100 on 22 May (1526991646), Andrew Cooper wrote:
> Intel hardware only uses 4 bits in MSR_EFER. Changes to LME and LMA are
> handled automatically via the VMENTRY_CTLS.IA32E_MODE bit.
>
> SCE is handled by ad-hoc logic in context_switch(), vmx_restore_guest_msrs()
> and vmx_update_gues
At 06:02 +0200 on 23 May (1527055365), Juergen Gross wrote:
> On 22/05/18 21:47, Marek Marczykowski-Górecki wrote:
> > Older gcc does not support #pragma GCC diagnostics, so use alternative
> > approach - change variable type to uint32_t (this code handle 32-bit
> > requests only anyway), which app
101 - 125 of 125 matches
Mail list logo
