flight 79397 linux-3.14 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79397/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 6 xen-build fail REGR. vs. 78986
build-i386-rumpuserxen
Hey Jens,
Please git pull the following branch:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-4.5
which has one bug-fix. I had it in my tree at some point and after an rebase
(done months ago) lost it!
It solves an migration problem where the number of queues may
On Wed, Jan 27, 2016 at 01:30:05PM -0500, Konrad Rzeszutek Wilk wrote:
> On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote:
> > Xen developers,
> >
> > After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed
> > NIC stopped working.
I have very similar (the same?) proble
flight 79389 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79389/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 6 xen-build fail REGR. vs. 59254
build-i386-rumpuserxe
On Tue, Jan 26, 2016 at 04:37:05AM -0700, Jan Beulich wrote:
> (re-adding xen-devel)
>
> >>> On 26.01.16 at 12:28, wrote:
> > Iommu=0 let the whole Qubes system work, without enforcing hardware
> > compartimentalisation (iommu is enforced in software mode)
> >
> > When iommu=no-igfx is enforced,
> -Original Message-
> From: iGVT-g [mailto:igvt-g-boun...@lists.01.org] On Behalf Of Alex
> Williamson
> Sent: Friday, January 29, 2016 10:00 AM
> To: Gerd Hoffmann
> Cc: igv...@ml01.01.org; xen-de...@lists.xensource.com; Eduardo Habkost;
> Stefano Stabellini; qemu-de...@nongnu.org; Cao
This run is configured for baseline tests only.
flight 38715 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38715/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-credit2 6 xen-boot
On 1/26/2016 12:28 PM, Meng Xu wrote:
Hi Dario and Tianyang,
On Tue, Jan 26, 2016 at 9:06 AM, Dario Faggioli
wrote:
On Mon, 2016-01-25 at 18:00 -0500, Meng Xu wrote:
On Mon, Jan 25, 2016 at 5:04 PM, Tianyang Chen
wrote:
I have removed some of the Ccs so they won't get bothered as we
discu
On Thu, Jan 28, 2016 at 09:55:45AM +, Dario Faggioli wrote:
> On Wed, 2016-01-27 at 15:53 +, George Dunlap wrote:
> > On 27/01/16 15:27, Konrad Rzeszutek Wilk wrote:
> > >
> > > So Elena started looking at the CPU bound and seeing how Xen
> > > behaves then
> > > and if we can improve the
> -Original Message-
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Thursday, January 28, 2016 6:55 PM
> To: Kay, Allen M; Gerd Hoffmann; qemu-de...@nongnu.org
> Cc: igv...@ml01.01.org; xen-de...@lists.xensource.com; Eduardo Habkost;
> Stefano Stabellini; Cao jin; vfi
flight 79388 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79388/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 60684
build-amd6
On 1/29/16 12:20 PM, Andrew Cooper wrote:
> Signed-off-by: Andrew Cooper
> ---
> CC: Jan Beulich
> CC: Doug Goldstein
> CC: Tim Deegan
> CC: George Dunlap
>
> v2:
> * Expand text. Use more-common makefile syntax
> ---
> xen/arch/x86/Kconfig| 18 ++
> xen/arch/x8
On 1/29/2016 7:09 PM, Jan Beulich wrote:
On 29.01.16 at 17:24, wrote:
One could shrink the domain structure by transforming some of its fields
to pointers, e.g. I could transform the pl_time field into a pointer and
dynamically allocate its data when domain_create is called.
Sounds like a reas
On 1/29/2016 6:47 PM, Lengyel, Tamas wrote:
by leaving there only the x86-specific part, i.e.:
struct {
uint8_t mov_to_msr_enabled : 1;
uint8_t mov_to_msr_extended : 1;
} monitor;
and moving the rest directly into the domain str
flight 79390 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79390/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt 11 guest-start fail REGR. vs. 79146
Tests which did not succe
flight 79429 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79429/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 12
c/s 0f1cb96e "x86 hvm: Allow cross-vendor migration" caused HVM domains to
unconditionally intercept #UD exceptions. While cross-vendor migration is
cool as a demo, it is extremely niche.
Intercepting #UD allows userspace code in a multi-vcpu guest to execute
arbitrary instructions in the x86 emu
This run is configured for baseline tests only.
flight 38714 linux-3.16 real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38714/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Doug Goldstein
CC: Tim Deegan
CC: George Dunlap
v2:
* Expand text. Use more-common makefile syntax
---
xen/arch/x86/Kconfig| 18 ++
xen/arch/x86/Rules.mk | 4
xen/arch/x86/mm/shadow/Makefile |
On Fri, 2016-01-29 at 08:09 +0100, Gerd Hoffmann wrote:
> Hi,
>
> > 1) The OpRegion MemoryRegion is mapped into system_memory through
> > programming of the 0xFC config space register.
> > a) vfio-pci could pick an address to do this as it is realized.
> > b) SeaBIOS/OVMF could program this.
>
On Fri, Jan 29, 2016 at 10:18:01AM -0700, Jim Fehlig wrote:
> Konrad Rzeszutek Wilk wrote:
> > On Wed, Jan 27, 2016 at 07:42:49PM -0700, Jim Fehlig wrote:
> >> On 01/27/2016 02:09 PM, Konrad Rzeszutek Wilk wrote:
> >>> On Wed, Jan 27, 2016 at 02:25:51PM -0600, Doug Goldstein wrote:
> On 1/27/1
flight 79387 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79387/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-rumpuserxen 6 xen-build fail REGR. vs. 66399
build-i386-rumpuserxen
On Fri, Jan 29, 2016 at 10:15 AM, Andrew Cooper
wrote:
> On 29/01/16 08:55, Razvan Cojocaru wrote:
> > This patch pauses the domain for all writes through the 'ad'
> > pointer in monitor_domctl(), defers a domain_unpause() call until
> > after the CRs are updated for the MONITOR_EVENT_WRITE_CTRLR
Konrad Rzeszutek Wilk wrote:
> On Wed, Jan 27, 2016 at 07:42:49PM -0700, Jim Fehlig wrote:
>> On 01/27/2016 02:09 PM, Konrad Rzeszutek Wilk wrote:
>>> On Wed, Jan 27, 2016 at 02:25:51PM -0600, Doug Goldstein wrote:
On 1/27/16 12:32 PM, Konrad Rzeszutek Wilk wrote:
> On Mon, Jan 25, 2016 at
On 29/01/16 08:55, Razvan Cojocaru wrote:
> This patch pauses the domain for all writes through the 'ad'
> pointer in monitor_domctl(), defers a domain_unpause() call until
> after the CRs are updated for the MONITOR_EVENT_WRITE_CTRLREG
> case, and makes sure that the domain is paused for both vm_e
On 29/01/16 16:16, Doug Goldstein wrote:
> Hi all,
>
> I agree to the conditions in the Xen Project Security [1] and Coverity
> [2] Contribution guidelines.
>
> I have been a Gentoo Linux developer since 2001 and involved with
> downstream packaging of virtualization products in Gentoo for at least
On 29/01/16 17:09, Jan Beulich wrote:
On 29.01.16 at 17:24, wrote:
>> To investigate I compiled the unaltered domain.c & used the pahole tool
>> (part of dwarves package) to obtain the complete layout of the domain
>> structure (& its members).
>> What I obtained:
>> * sizeof(struct do
On 29/01/16 16:53, Jan Beulich wrote:
On 29.01.16 at 15:02, wrote:
>> On 29/01/16 14:57, Egger, Christoph wrote:
>>> On 29/01/16 14:24, Jan Beulich wrote:
Christoph,
in commit dd6de3ab99 ("Implement Nested-on-Nested") you added
code to hap_invlpg() supposedly emulating INV
>>> On 29.01.16 at 17:24, wrote:
> To investigate I compiled the unaltered domain.c & used the pahole tool
> (part of dwarves package) to obtain the complete layout of the domain
> structure (& its members).
> What I obtained:
> * sizeof(struct domain) is already = 4096 bytes (= PAGE_SIZE)
flight 79424 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79424/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 12
>>> On 29.01.16 at 17:48, wrote:
> On 29/01/16 10:29, Jan Beulich wrote:
>> --- a/xen/arch/x86/xstate.c
>> +++ b/xen/arch/x86/xstate.c
>> @@ -29,6 +29,8 @@ unsigned int *__read_mostly xstate_sizes
>> static unsigned int __read_mostly xstate_features;
>> static unsigned int __read_mostly
>> xsta
On 29/01/16 10:30, Jan Beulich wrote:
> Since we never hand out compacted state, at least for now we're also
> not going to accept such.
>
> Reported-by: Harmandeep Kaur
> Signed-off-by: Jan Beulich
Reviewed-by: Andrew Cooper
___
Xen-devel mailing li
On 29/01/16 10:29, Jan Beulich wrote:
> XRSTORS unconditionally faults when xcomp_bv has bit 63 clear. Instead
> of just fixing this issue, overhaul the fault recovery code, which -
> one of the many mistakes made when xstate support got introduced - was
> blindly mirroring that accompanying FXRSTO
>>> On 29.01.16 at 17:32, wrote:
> On Fri, Jan 29, 2016 at 9:19 AM, Jan Beulich wrote:
>> >>> On 29.01.16 at 17:12, wrote:
>> > On Fri, Jan 29, 2016 at 4:03 AM, Jan Beulich wrote:
>> >> >>> On 28.01.16 at 21:58, wrote:
>> >> > --- a/xen/include/public/memory.h
>> >> > +++ b/xen/include/public/
> by leaving there only the x86-specific part, i.e.:
> struct {
> uint8_t mov_to_msr_enabled : 1;
> uint8_t mov_to_msr_extended : 1;
> } monitor;
>
> and moving the rest directly into the domain structure, i.e. add @ the end
> of struct domain [@ xen/inclu
>>> On 29.01.16 at 17:26, wrote:
> On Fri, Jan 29, 2016 at 09:00:15AM -0700, Jan Beulich wrote:
>> >>> On 29.01.16 at 16:30, wrote:
>> > I am hoping the maintainers can guide me in how they would like:
>> > - Deal with documentation? I removed the allowsuperpage from documentation
>> >but pe
On Fri, Jan 29, 2016 at 01:27:16PM +0800, Wen Congyang wrote:
> This patchset is Prerequisite for COLO feature. Refer to:
> http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
>
> Patch status:
> 1. Acked patches: patch 2, 3, 4, 9, 10, 15, 16, 18
> 2. Reviewd patches: patch 1, 10, 13, 15, 1
On Fri, Jan 29, 2016 at 01:27:28PM +0800, Wen Congyang wrote:
> In COLO mode, both VMs are running, and are considered in sync if the
> visible network traffic is identical. After some time, they fall out of
> sync.
>
> At this point, the two VMs have definitely diverged. Lets call the
> primary
On Fri, Jan 29, 2016 at 01:27:22PM +0800, Wen Congyang wrote:
> Introduce enum type libxl_checkpointed_stream in IDL.
> rename the last argument of migrate_receive from "remus" to
> "checkpointed" since the semantics of this parameter has
> changed.
>
> NOTE:
> libxl_domain_restore_params and dom
On Fri, Jan 29, 2016 at 01:27:23PM +0800, Wen Congyang wrote:
> Pass checkpointed_stream from libxl to libxc.
> It won't affact legacy migration because legacy migration
> won't use this param.
>
> Signed-off-by: Yang Hongyang
> Signed-off-by: Wen Congyang
> CC: Ian Campbell
> CC: Ian Jackson
On Fri, Jan 29, 2016 at 01:27:25PM +0800, Wen Congyang wrote:
> Secondary vm is running in COLO mode, we need to send secondary
> vm's dirty page information to primary host at checkpoint, so we
> have to enable qemu logdirty on secondary.
>
> libxl__domain_suspend_common_switch_qemu_logdirty() is
On Fri, Jan 29, 2016 at 01:27:24PM +0800, Wen Congyang wrote:
> In normal migration, the qemu state is passed to qemu as a parameter.
> With COLO, secondary vm is running. So we will do the following steps
> at every checkpoint:
> 1. suspend both primary vm and secondary vm
> 2. sync the state
> 3.
>>> On 29.01.16 at 11:45, wrote:
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -940,6 +940,8 @@ static int hvm_ioreq_server_alloc_rangesets(struct
> hvm_ioreq_server *s,
> {
> unsigned int i;
> int rc;
> +unsigned int max_wp_ram_ranges =
> +s->domain->a
On Fri, Jan 29, 2016 at 01:27:30PM +0800, Wen Congyang wrote:
> The error code ERROR_REMUS_XXX was introduced in Xen 4.5, and
> changed to ERROR_CHECKPOINT_XXX after previous renaming.
> The patch fix the backword compatibility.
>
> Signed-off-by: Yang Hongyang
> Signed-off-by: Wen Congyang
Rev
On Fri, Jan 29, 2016 at 9:19 AM, Jan Beulich wrote:
> >>> On 29.01.16 at 17:12, wrote:
> > On Fri, Jan 29, 2016 at 4:03 AM, Jan Beulich wrote:
> >> >>> On 28.01.16 at 21:58, wrote:
> >> > --- a/xen/arch/x86/mm/p2m.c
> >> > +++ b/xen/arch/x86/mm/p2m.c
> >> > @@ -1777,14 +1777,57 @@ bool_t p2m_m
On Fri, Jan 29, 2016 at 01:27:21PM +0800, Wen Congyang wrote:
> Before this patch:
> 1. suspend
> a. PVHVM and PV: we use the same way to suspend the guest (send the suspend
>request to the guest). If the guest doesn't support evtchn, the xenstore
>variant will be used, suspending the guest
On Fri, Jan 29, 2016 at 01:27:19PM +0800, Wen Congyang wrote:
> This is purely code motion.
>
> Signed-off-by: Yang Hongyang
> Signed-off-by: Wen Congyang
> CC: Ian Jackson
> CC: Wei Liu
> Acked-by: Ian Campbell
Reviewed-by: Konrad Rzeszutek Wilk
___
On Fri, Jan 29, 2016 at 01:27:18PM +0800, Wen Congyang wrote:
> After previous refactoring, we are now able to move all remus code
> into a separate file libxl_remus.c.
>
> Export following functions for internal use:
> - Remus callbacks
> * libxl__remus_domain_suspend_callback
> * libxl__remu
On Fri, Jan 29, 2016 at 01:27:20PM +0800, Wen Congyang wrote:
> Currently struct libxl__domain_suspend_state contains 2 type of states,
> one is save state, another is suspend state. This patch separates those
> two out.
> The motivation of this is that COLO will need to do suspend/resume
> continu
On Fri, Jan 29, 2016 at 10:16:04AM -0600, Doug Goldstein wrote:
> Hi all,
>
> I agree to the conditions in the Xen Project Security [1] and Coverity
> [2] Contribution guidelines.
>
> I have been a Gentoo Linux developer since 2001 and involved with
> downstream packaging of virtualization produc
>>> On 29.01.16 at 17:12, wrote:
> On Fri, Jan 29, 2016 at 4:03 AM, Jan Beulich wrote:
>> >>> On 28.01.16 at 21:58, wrote:
>> > --- a/xen/arch/x86/mm/p2m.c
>> > +++ b/xen/arch/x86/mm/p2m.c
>> > @@ -1777,14 +1777,57 @@ bool_t p2m_mem_access_check(paddr_t gpa,
>> unsigned long gla,
>> > retur
>>> On 27.01.16 at 09:30, wrote:
> Changes in v7:
> no changes.
>
>
> This patch disables pkeys for guest in non-paging mode, However XEN always
> uses
> paging mode to emulate guest non-paging mode, To emulate this behavior, pkeys
> needs to be manually disabled when guest switches to non-
On Fri, Jan 29, 2016 at 09:00:15AM -0700, Jan Beulich wrote:
> >>> On 29.01.16 at 16:30, wrote:
> > I am hoping the maintainers can guide me in how they would like:
> > - Deal with documentation? I removed the allowsuperpage from documentation
> >but perhaps it should just mention deprecated?
I'm trying to refactor some arch-specific code into common code and was
surprised to find out that the x86 domain structure already occupies
PAGE_SIZE bytes, couldn't even add an unsigned short field in it w/o
causing a compile-time error.
I'm using the master branch of git://xenbits.xenproject.
On Thu, Jan 28, 2016 at 09:46:46AM +, Dario Faggioli wrote:
> On Wed, 2016-01-27 at 11:03 -0500, Elena Ufimtseva wrote:
> > On Wed, Jan 27, 2016 at 10:27:01AM -0500, Konrad Rzeszutek Wilk
> > wrote:
> > > On Wed, Jan 27, 2016 at 03:10:01PM +, George Dunlap wrote:
> > > > On 27/01/16 14:33,
Hi all,
I agree to the conditions in the Xen Project Security [1] and Coverity
[2] Contribution guidelines.
I have been a Gentoo Linux developer since 2001 and involved with
downstream packaging of virtualization products in Gentoo for at least 8
years with a specific focus on QEMU, libvirt, KVM
>>> On 29.01.16 at 16:30, wrote:
> @@ -985,20 +968,7 @@ get_page_from_l2e(
> return rc;
> }
>
> -if ( !opt_allow_superpage )
> -{
> -MEM_LOG("Attempt to map superpage without allowsuperpage "
> -"flag in hypervisor");
> -return -EINVAL;
> -
On Fri, Jan 29, 2016 at 4:03 AM, Jan Beulich wrote:
> >>> On 28.01.16 at 21:58, wrote:
> > --- a/xen/arch/x86/mm/p2m.c
> > +++ b/xen/arch/x86/mm/p2m.c
> > @@ -1777,14 +1777,57 @@ bool_t p2m_mem_access_check(paddr_t gpa,
> unsigned long gla,
> > return (p2ma == p2m_access_n2rwx);
> > }
> >
>>> On 29.01.16 at 15:02, wrote:
> On 29/01/16 14:57, Egger, Christoph wrote:
>> On 29/01/16 14:24, Jan Beulich wrote:
>>> Christoph,
>>>
>>> in commit dd6de3ab99 ("Implement Nested-on-Nested") you added
>>> code to hap_invlpg() supposedly emulating INVLPGA. I've been
>>> stumbling across this a n
>>> On 29.01.16 at 16:30, wrote:
> I am hoping the maintainers can guide me in how they would like:
> - Deal with documentation? I removed the allowsuperpage from documentation
>but perhaps it should just mention deprecated?
Since you delete the option, deleting it from doc seems fine to me.
Hey,
This patchset removes the opt_allow_superpage parameter and also the code
around it.
I've tested (migration, bootup, etc) with normal PV and HVM guests and all
works.
I haven't yet tested kernels that had PV superpage support in (UEK2, UEK3,
classic
Xen kernels) but looking at the code it
The last bastion of users is moving away from needing
this.
Please note that there was an partial removal by
c/s 9b3c6b13e0c085ceb53210f8e682a073096b94fa
"libxc: remove superpages option for pv domains" so an user
could not even run PV guests with superpage.
HVM guests are not affected - they hav
On 1/29/16 4:36 AM, Lars Kurth wrote:
> Hi everyone,
>
> as part of the review of Xen Project infrastructure, we are looking at some
> old services that we want to retire. I had an action, to verify whether
> anyone is still using http://bugzilla.xensource.com/bugzilla ... I believe
> that the
On 29/01/16 10:26, Jan Beulich wrote:
> We must not clear the compaction bit when using XSAVES/XRSTORS. And
> we need to guarantee that xcomp_bv never has any bits clear which
> are set in xstate_bv (which requires partly undoing commit 83ae0bb226
> ["x86/xsave: simplify xcomp_bv initialization"]).
On 29/01/16 10:27, Jan Beulich wrote:
> The packed attribute was pointlessly used here - there are no
> misaligned fields, and hence even if the attribute took effect, it
> would at best lead to the compiler generating worse code.
>
> At the same time specify the required alignment of the fpu_sse s
On Wed, 2016-01-27 at 15:24 +, Ian Campbell wrote:
> On Wed, 2016-01-27 at 09:11 -0600, Doug Goldstein wrote:
> > On 1/27/16 9:05 AM, Ian Campbell wrote:
> > > Indeed, I was referring to the change from:
> > >
> > > -ifeq (arm64,$(XEN_TARGET_ARCH))
> > >
> > > to
> > >
> > > +ifdef CONFIG_AR
On 1/27/16 8:37 PM, Jim Fehlig wrote:
> On 01/27/2016 01:25 PM, Doug Goldstein wrote:
>> On 1/27/16 12:32 PM, Konrad Rzeszutek Wilk wrote:
>>> On Mon, Jan 25, 2016 at 05:25:02PM -0700, Jim Fehlig wrote:
I would like to hear the community's opinion on supporting more qdisk
types in
x
On Wed, Jan 27, 2016 at 07:42:49PM -0700, Jim Fehlig wrote:
> On 01/27/2016 02:09 PM, Konrad Rzeszutek Wilk wrote:
> > On Wed, Jan 27, 2016 at 02:25:51PM -0600, Doug Goldstein wrote:
> >> On 1/27/16 12:32 PM, Konrad Rzeszutek Wilk wrote:
> >>> On Mon, Jan 25, 2016 at 05:25:02PM -0700, Jim Fehlig wr
On 29/01/16 14:57, Egger, Christoph wrote:
> On 29/01/16 14:24, Jan Beulich wrote:
>> Christoph,
>>
>> in commit dd6de3ab99 ("Implement Nested-on-Nested") you added
>> code to hap_invlpg() supposedly emulating INVLPGA. I've been
>> stumbling across this a number of times in the past, not being able
flight 79379 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79379/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-libvirt-qcow2 3 host-install(3) broken in 79328 pass in 79379
test-armhf-armhf-xl-credit2 6 xe
On 29/01/16 14:24, Jan Beulich wrote:
> Christoph,
>
> in commit dd6de3ab99 ("Implement Nested-on-Nested") you added
> code to hap_invlpg() supposedly emulating INVLPGA. I've been
> stumbling across this a number of times in the past, not being able
> to make the connection between (a) VMX/EPT and
On Thu, 28 Jan 2016, Leonid Yegoshin wrote:
> In http://patchwork.linux-mips.org/patch/10505/ the very last mesg exchange
> is:
[...]
> ... and that stops forever...
Thanks for the reminder -- last June was very hectic, I travelled a lot
and I lost the discussion from my radar. Apologies for t
This run is configured for baseline tests only.
flight 38712 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38712/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 14 guest-
Christoph,
in commit dd6de3ab99 ("Implement Nested-on-Nested") you added
code to hap_invlpg() supposedly emulating INVLPGA. I've been
stumbling across this a number of times in the past, not being able
to make the connection between (a) VMX/EPT and INVLPGA and
(b) SVM's INVLPGA intercept and this
flight 38713 distros-debian-jessie real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38713/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-armhf-jessie-netboot-pygrub 12 saverestore-support-check fail
never pass
test-armhf-ar
>>> On 28.01.16 at 21:58, wrote:
> --- a/xen/arch/x86/mm/p2m.c
> +++ b/xen/arch/x86/mm/p2m.c
> @@ -1777,14 +1777,57 @@ bool_t p2m_mem_access_check(paddr_t gpa, unsigned
> long gla,
> return (p2ma == p2m_access_n2rwx);
> }
>
> +static int p2m_set_altp2m_mem_access(struct domain *d, struct
On Thu, 2016-01-28 at 18:31 -0800, Andy Lutomirski wrote:
>
> To everyone else: we've waffled on this for way too long. I think
> we should to get DMA API implementation in with a conservative
> policy like this rather than waiting until we achieve perfection.
> I'm tired of carrying these patche
On Fri, 2016-01-29 at 10:03 +, osstest service owner wrote:
> flight 79367 linux-3.16 real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/79367/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-i386-rumpuserxen
On 29/01/16 11:46, Jan Beulich wrote:
On 29.01.16 at 11:21, wrote:
>> --- a/xen/common/sched_credit.c
>> +++ b/xen/common/sched_credit.c
>> @@ -1086,12 +1086,19 @@ csched_dom_cntl(
>> static inline void
>> __csched_set_tslice(struct csched_private *prv, unsigned timeslice)
>> {
>> +uns
flight 79371 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79371/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail
REGR. vs. 65543
test-amd64-i386-
XenGT leverages ioreq server to track and forward the accesses to
GPU I/O resources, e.g. the PPGTT(per-process graphic translation
tables). Currently, ioreq server uses rangeset to track the BDF/
PIO/MMIO ranges to be emulated. To select an ioreq server, the
rangeset is searched to see if the I/
Currently in ioreq server, guest write-protected ram pages are
tracked in the same rangeset with device mmio resources. Yet
unlike device mmio, which can be in big chunks, the guest write-
protected pages may be discrete ranges with 4K bytes each. This
patch uses a seperate rangeset for the guest r
This patch refactors struct rangeset to base it on the red-black
tree structure, instead of on the current doubly linked list. By
now, ioreq leverages rangeset to keep track of the IO/memory
resources to be emulated. Yet when number of ranges inside one
ioreq server is very high, traversing a doubl
A new parameter - max_wp_ram_ranges is added to set the upper limit
of write-protected ram ranges to be tracked inside one ioreq server
rangeset.
Ioreq server uses a group of rangesets to track the I/O or memory
resources to be emulated. Default limit of ranges that one rangeset
can allocate is se
>>> On 29.01.16 at 11:21, wrote:
> --- a/xen/common/sched_credit.c
> +++ b/xen/common/sched_credit.c
> @@ -1086,12 +1086,19 @@ csched_dom_cntl(
> static inline void
> __csched_set_tslice(struct csched_private *prv, unsigned timeslice)
> {
> +unsigned long flags;
> +
> +spin_lock_irqsave
Hi all,
this is a quick note to let you note that we are deferring the upgrades that
were originally planned on Feb 1 and 4th. We ran into some issues with the Jan
28th upgrade, which would occur again. We are working with Rackspace to find a
solution that avoids the issues we have seen on the 2
Hi everyone,
as part of the review of Xen Project infrastructure, we are looking at some old
services that we want to retire. I had an action, to verify whether anyone is
still using http://bugzilla.xensource.com/bugzilla ... I believe that the
service can be retired, as it has been replaced by
On 29/01/16 02:31, Andy Lutomirski wrote:
> Signed-off-by: Andy Lutomirski
> ---
> drivers/virtio/virtio_ring.c | 12
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
> index c169c6444637..305c05cc249a 100644
> --- a/dri
Since we never hand out compacted state, at least for now we're also
not going to accept such.
Reported-by: Harmandeep Kaur
Signed-off-by: Jan Beulich
--- a/xen/arch/x86/domctl.c
+++ b/xen/arch/x86/domctl.c
@@ -964,7 +964,7 @@ long arch_do_domctl(
{
if ( evc->size
XRSTORS unconditionally faults when xcomp_bv has bit 63 clear. Instead
of just fixing this issue, overhaul the fault recovery code, which -
one of the many mistakes made when xstate support got introduced - was
blindly mirroring that accompanying FXRSTOR, neglecting the fact that
XRSTOR{,S} aren't
The packed attribute was pointlessly used here - there are no
misaligned fields, and hence even if the attribute took effect, it
would at best lead to the compiler generating worse code.
At the same time specify the required alignment of the fpu_sse sub-
structure, such that the various typeof() u
We must not clear the compaction bit when using XSAVES/XRSTORS. And
we need to guarantee that xcomp_bv never has any bits clear which
are set in xstate_bv (which requires partly undoing commit 83ae0bb226
["x86/xsave: simplify xcomp_bv initialization"]). Split initialization
of xcomp_bv from the oth
branch xen-unstable
xenbranch xen-unstable
job test-armhf-armhf-xl-credit2
testid xen-boot
Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemuu git://xenbits.xen.org/qemu-xen.git
Tree: xen
1: xstate: fix xcomp_bv initialization
2: adjust xsave structure attributes
3: xstate: fix fault behavior on XRSTORS
4: xstate: extend validation to cover full header
Reported-by: Harmandeep Kaur
Signed-off-by: Jan Beulich
___
Xen-devel mailing list
When modifying the timeslice of the credit scheduler in a cpupool the
cpupool global credit value (n_cpus * credits_per_tslice) isn't
recalculated. This will lead to wrong scheduling decisions later.
Do the recalculation when updating the timeslice.
Signed-off-by: Juergen Gross
---
xen/common/s
>>> On 28.01.16 at 20:17, wrote:
> Latest set looks good. No boot issues. No resets.
> Full log at http://paste2.org/NxHNW4vn
Thanks!
> Sorry I don't know much about source of last few
> lines. I was just tracing in xen when these came.
> I was unable to create them again. I will inform
> you i
flight 79367 linux-3.16 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/79367/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 77819
build-amd64-rumpuserxe
On Fri, 2016-01-29 at 00:52 +, osstest service owner wrote:
> flight 79328 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/79328/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> build-amd64-rumpuser
>>> On 29.01.16 at 02:53, wrote:
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Friday, January 29, 2016 12:38 AM
>> >>> On 28.01.16 at 06:12, wrote:
>> > --- a/xen/arch/x86/hvm/vmx/vmx.c
>> > +++ b/xen/arch/x86/hvm/vmx/vmx.c
>> > @@ -83,7 +83,140 @@ static int vmx_msr_write_intercept(u
This patch pauses the domain for all writes through the 'ad'
pointer in monitor_domctl(), defers a domain_unpause() call until
after the CRs are updated for the MONITOR_EVENT_WRITE_CTRLREG
case, and makes sure that the domain is paused for both vm_event
enable and disable cases in vm_event_domctl()
1 - 100 of 106 matches
Mail list logo
