xc_mem_access_enable_emulate() and xc_mem_access_disable_emulate()
are currently no-ops, that is all they do is set a flag that
nobody else checks. The user can already set the EMULATE flags in
the vm_event response if emulation is desired, and having an extra
check above that is not inherently saf
On 02/14/2016 10:38 AM, Razvan Cojocaru wrote:
> xc_mem_access_enable_emulate() and xc_mem_access_disable_emulate()
> are currently no-ops, that is all they do is set a flag that
> nobody else checks. The user can already set the EMULATE flags in
> the vm_event response if emulation is desired, and
Hi all,
Just been looking at the polarssl parts in Xen 4.6 and others - seems
like we're hard coded to version 1.1.4 which was released on 31st May 2012.
Branch 1.1.x has been EOL for a number of years, 1.2.x has been EOL
since Jan.
It's now called mbedtls and current versions are 2.2.1 released
flight 82162 qemu-upstream-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82162/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-qcow2 6 xen-bootfail REGR. vs. 77722
test-ar
flight 82198 qemu-upstream-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82198/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail REGR. vs. 80694
test-amd64-amd64-xl
flight 82239 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82239/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 5 xen-build fail REGR. vs. 80121
Tests which did not succe
flight 82212 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82212/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-rtds 11 guest-start fail REGR. vs. 81620
build-amd64-rumpuserxen
flight 82234 qemu-upstream-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82234/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-i386-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail like 66772
Tests which did
On Sun, Feb 14, 2016 at 1:38 AM, Razvan Cojocaru
wrote:
> xc_mem_access_enable_emulate() and xc_mem_access_disable_emulate()
> are currently no-ops, that is all they do is set a flag that
> nobody else checks. The user can already set the EMULATE flags in
> the vm_event response if emulation is d
flight 82264 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82264/
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
The Makefile / Kconfig currently controlling compilation here is:
obj-y += grant-table.o features.o balloon.o manage.o preempt.o time.o
[...]
obj-$(CONFIG_XEN_BALLOON) += xen-balloon.o
...with:
drivers/xen/Kconfig:config XEN_BALLOON
drivers/xen/Kconfig:bool "Xen memory balloo
The Kconfig currently controlling compilation of this code is:
arch/x86/xen/Kconfig:config XEN_PVHVM
arch/x86/xen/Kconfig: def_bool y
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when reading the drive
The Kconfig currently controlling compilation of this code is:
config XEN_SYS_HYPERVISOR
bool "Create xen entries under /sys/hypervisor"
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when reading t
Code that uses no modular facilities whatsoever should not be
sourcing module.h at all, since that header drags in a bunch
of other headers with it.
Similarly, code that is not explicitly using modular facilities
like module_init() but only is declaring module_param setup
variables should be using
This series of commits is a part of a larger project to ensure
people don't reference modular support functions in non-modular
code. Overall there was roughly 5k lines of dead code in the
kernel due to this. So far we've fixed several areas, like tty,
x86, net, ... and we continue to work on othe
The Makefile / Kconfig currently controlling compilation here is:
obj-y += xenbus_dev_frontend.o
[...]
obj-$(CONFIG_XEN_BACKEND) += xenbus_dev_backend.o
...with:
drivers/xen/Kconfig:config XEN_BACKEND
drivers/xen/Kconfig:bool "Backend driver support"
...meaning that they currently are not
flight 82388 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82388/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 5 xen-build fail REGR. vs. 79947
build-amd64-xsm
flight 82303 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82303/
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
flight 82419 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82419/
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
flight 82477 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82477/
Perfect :-)
All tests in this flight passed
version targeted for testing:
xen 483ad4439f7fc71e12d46dae516f2b9ab2b977ad
baseline version:
xen 1ac81bb7166b79b655
On 02/04/16 20:24, Stefano Stabellini wrote:
> On Thu, 4 Feb 2016, Haozhong Zhang wrote:
> > On 02/03/16 15:22, Stefano Stabellini wrote:
> > > On Wed, 3 Feb 2016, George Dunlap wrote:
> > > > On 03/02/16 12:02, Stefano Stabellini wrote:
> > > > > On Wed, 3 Feb 2016, Haozhong Zhang wrote:
> > > > >
flight 82431 qemu-upstream-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82431/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-winxpsp3 15 guest-localmigrate/x10 fail REGR. vs.
77858
Test
On Fri, Feb 12, 2016 at 11:13 AM, Paul Durrant wrote:
> ...for receive-side packets.
>
> My recent patch to include/xen/interface/io/netif.h defines a set of
> control messages that can be used by a VM frontend driver to configure
> toeplitz hashing of receive-side packets and consequent steering
On Fri, Feb 12, 2016 at 5:59 PM, Paul Durrant wrote:
>> -Original Message-
>> From: David Miller [mailto:da...@davemloft.net]
>> Sent: 12 February 2016 16:42
>> To: Paul Durrant
>> Cc: net...@vger.kernel.org; xen-de...@lists.xenproject.org
>> Subject: Re: [PATCH net-next v1 0/8] xen-netbac
On Fri, Feb 12, 2016 at 11:13 AM, Paul Durrant wrote:
> ...rather than a boolean merely indicating a canonical L4 hash.
>
> skb_set_hash() takes a hash type (from enum pkt_hash_types) as an
> argument but information is lost since only a single bit in the skb
> stores whether that hash type is PKT
On Fri, Feb 12, 2016 at 11:13 AM, Paul Durrant wrote:
> My recent patch to include/xen/interface/io/netif.h defines a new extra
> info type that can be used to pass toeplitz hash values between backend
> and VM frontend.
>
> This patch adds code to xen-netback to pass hash values calculated for
>
flight 82450 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82450/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail REGR.
vs. 65543
test-amd64-amd64-
On 12/02/16 19:36, Olaf Hering wrote:
> On Fri, Feb 12, Wei Liu wrote:
>
>> On Thu, Feb 11, 2016 at 03:43:31PM +, Olaf Hering wrote:
>>> Just to make them public, not meant for merging:
>>
>> I might be mistaken, but if you don't provide a hotplug script or some
>> sort for Xen how do you expe
flight 82482 qemu-upstream-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82482/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-libvirt-qcow2 6 xen-boot fail in 82162 pass in 82482
test-armhf-armhf-xl-c
On Thu, Feb 11, 2016 at 1:40 AM, Ian Campbell
wrote:
> On Wed, 2016-02-10 at 17:47 -0800, Suriyan Ramasami wrote:
> >
> >
> > On Wed, Feb 10, 2016 at 2:03 AM, Ian Campbell
> > wrote:
> > > On Tue, 2016-02-09 at 10:20 -0800, Suriyan Ramasami wrote:
> > > > I agree on the first two paragraphs.
>
This patch series is an attempt to move some of the monitor vm-events code to
the common-side. Done to make it easier to move additional parts that can be
moved to common when ARM-side implementations are to be added.
Patches summary:
1. Merge almost identical functions hvm_event_int3 + hvm_event
This patch merges almost identical functions hvm_event_int3 and
hvm_event_single_step into a single function called hvm_event_breakpoint.
Also fixes event.c file header comment in the process.
Signed-off-by: Corneliu ZUZU
---
xen/arch/x86/hvm/event.c| 108 +++-
This patch moves monitor_domctl to common-side.
Purpose: move what's common to common, prepare for implementation
of such vm-events on ARM.
* move get_capabilities to arch-side => arch_monitor_get_capabilities.
* add arch-side monitor op handling function => arch_monitor_domctl_op.
e.g. X86-side
flight 82511 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82511/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-armhf-armhf-libvirt 14 guest-saverestorefail never pass
test-armhf-armhf-libvirt 12 migrate-sup
Even if placed in .init.* there's no reason to needlessly bloat the
binary due to padding fields the compiler needs to insert on 64-bit
architectures.
Signed-off-by: Jan Beulich
--- a/xen/include/xen/init.h
+++ b/xen/include/xen/init.h
@@ -81,34 +81,35 @@ struct kernel_param {
OPT_SIZE,
In order to reduce the risk of unintentionally adding a function
pointer to just one of the two tables, merge them into one, with each
entry pair getting generated by a single macro invocation (at once
dropping all explicit casting outside the macro definition).
Signed-off-by: Jan Beulich
--- a/
36 matches
Mail list logo
