>>> On 05.02.16 at 14:42, wrote:
> --- a/xen/arch/x86/cpu/intel.c
> +++ b/xen/arch/x86/cpu/intel.c
> @@ -18,11 +18,18 @@
>
> #define select_idle_routine(x) ((void)0)
>
> -static unsigned int probe_intel_cpuid_faulting(void)
> +static bool_t __init probe_intel_cpuid_faulting(void)
> {
>
>>> On 05.02.16 at 14:42, wrote:
> @@ -126,126 +133,189 @@ static const struct cpuidmask *__init noinline
> get_cpuidmask(const char *opt)
> }
>
> /*
> + * Sets caps in expected_levelling_cap, probes for the specified mask MSR,
> and
> + * set caps in levelling_caps if it is found. Processo
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
Add file header comment and local variable block @ EOF
of xen/arch/arm/hvm.c.
Signed-off-by: Corneliu ZUZU
Acked-by: Stefano Stabellini
---
Changed since v4:
---
xen/arch/arm/hvm.c | 29 -
1 file changed, 28 insertions(+), 1 deletion(-)
diff --git a/xen/arch/arm/h
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. Fix file comment
Acked-by: Stefano Stabellini
2. Move m
n
>>> On 2/17/2016 at 12:56 AM, in message <20160216165608.ga21...@gmail.com>,
>>> Olaf
Hering wrote:
> On Tue, Jan 19, Chunyan Liu wrote:
>
> > #xl usbctrl-attach test_vm version=1 ports=8
>
> > #xl usbdev-attach test_vm hostbus=1 hostaddr=2
>
> I think this does not handle the -N k
flight 82825 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82825/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-rtds 15 guest-start/debian.repeatfail like 82516
build-amd64-rumpuserxen
On Tue, Feb 2, 2016 at 9:46 PM, Andy Lutomirski wrote:
> This switches virtio to use the DMA API on Xen and if requested by
> module option.
Michael, any update on this?
--Andy
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xe
---
docs/misc/xl-disk-configuration.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/misc/xl-disk-configuration.txt
b/docs/misc/xl-disk-configuration.txt
index 6a2118d..29f6ddb 100644
--- a/docs/misc/xl-disk-configuration.txt
+++ b/docs/misc/xl-disk-configuration.txt
@
This series contains a few improvments related to libxl's
support for the various qdisk types. Patch1 is a small fix
for libxlu_cfg to error when encountering unknown backslash-
escaped characters instead of silently dropping them. Patch2
is actually unrelated and fixes a typo noticed while reviewi
When dequoting config strings in xlu__cfgl_dequote(), unknown
characters following a '\', and the '\' itself, are discarded.
E.g. a disk configuration string containing
rbd:pool/image:mon_host=192.168.0.100\:6789
would be dequoted as
rbd:pool/image:mon_host=192.168.0.1006789
Instead of disc
target= in disk config can be used to convey arbitrary
configuration information to backends. Add a bit more info
to xl-disk-configuration.txt to clarify this, including some
simple nbd and rbd qdisk configurations.
---
docs/misc/xl-disk-configuration.txt | 10 +-
1 file changed, 9 inserti
> From: Paul Durrant [mailto:paul.durr...@citrix.com]
> Sent: Tuesday, February 16, 2016 7:11 PM
>
> > -Original Message-
> > From: Jan Beulich [mailto:jbeul...@suse.com]
> > Sent: 16 February 2016 10:34
> > To: Paul Durrant
> > Cc: Andrew Cooper; George Dunlap; Ian Campbell; Ian Jackson;
> From: Tian, Kevin
> Sent: Thursday, February 04, 2016 1:52 PM
>
> > From: Jan Beulich [mailto:jbeul...@suse.com]
> > Sent: Wednesday, February 03, 2016 5:35 PM
> > > (XEN) nvmx_handle_vmwrite: 0
> > > (XEN) nvmx_handle_vmwrite: 2008
> > > (XEN) nvmx_handle_vmwrite: 2008
> > > (XEN) nvmx_handle_v
On Tue, Feb 16, 2016 at 2:03 AM, Ian Campbell
wrote:
> On Sun, 2016-02-14 at 22:32 -0800, Suriyan Ramasami wrote:
> >
> >
> > On Thu, Feb 11, 2016 at 1:40 AM, Ian Campbell <
> > ian.campb...@citrix.com> wrote:
> > > On Wed, 2016-02-10 at 17:47 -0800, Suriyan Ramasami wrote:
> > > >
> > > >
> > >
flight 82793 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82793/
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. 79037
build-i386-rumpuserxen
On Tue, Feb 16, 2016 at 03:09:37PM -0700, Jim Fehlig wrote:
> Wei Liu wrote:
> > This patch series consolidates adhoc parsers in xl.
>
> Hi Wei,
>
> I never tested or reviewed this series after seeing Ian's comments. Did you
> have
> time to work on a V2? Or did I miss a V2? :-) Let me know if I
flight 82764 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82764/
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 82785 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82785/
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-
Wei Liu wrote:
> This patch series consolidates adhoc parsers in xl.
Hi Wei,
I never tested or reviewed this series after seeing Ian's comments. Did you have
time to work on a V2? Or did I miss a V2? :-) Let me know if I can help.
Regards,
Jim
___
Xen
On Tue, 2016-02-16 at 17:45 +, Ian Jackson wrote:
> Ian Campbell writes ("[PATCH] xl: close nullfd after dup2'ing it to
> stdin"):
> > Taking care not to do so if nullfd happens (somehow) to have the
> same
> > fd number as stdin/out/err.
>
> I think that can only happen if the program (the pr
The target= setting in xl disk configuration can be used to encode
meta info that is meaningful to a backend. Leverage this fact to
support qdisk network disk types such as rbd. E.g. xl disk config
containing
disk = [ "format=raw,vdev=hdb,access=rw,backendtype=qdisk,
target=rbd:pool/
While at it, improve a few comments. No functional change.
Signed-off-by: Jim Fehlig
---
tests/xlconfigtest.c | 34 +++---
1 file changed, 19 insertions(+), 15 deletions(-)
diff --git a/tests/xlconfigtest.c b/tests/xlconfigtest.c
index 4b2f28f..aa53ed8 100644
--- a/t
xl/libxl already supports qemu's network-based block backends
such as nbd and rbd. libvirt has supported configuring such
s for long time too. This patch adds support for rbd
disks in the libxl driver by generating a rbd device URL from
the virDomainDiskDef object. The URL is passed to libxl via th
xl/libxl already supports qemu's network-based block backends
such as nbd and rbd. libvirt has supported configuring network
disks for long time too. This series marries the two in the
libxl driver and in the xl<->xml converter. Only rbd supported
is added in this series. Support for other backends
The most formal form of xl disk configuration uses key=value
syntax to define each configuration item, e.g.
format=raw, vdev=xvda, access=rw, backendtype=phy, target=disksrc
Change the xl disk formatter to produce this syntax, which allows
target= to contain meta info needed to setup a network-ba
flight 82783 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82783/
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
On 02/16/2016 12:37 PM, Roger Pau Monne wrote:
diff --git a/xen/include/public/xen.h b/xen/include/public/xen.h
index 7b629b1..6ba060f 100644
--- a/xen/include/public/xen.h
+++ b/xen/include/public/xen.h
@@ -787,25 +787,46 @@ typedef struct start_info start_info_t;
/*
* Start of day structur
> >>> +/* Return value is the number of bytes written, or XEN_Exx on error.
> >>> + * Calling with empty parameter returns the size of build_id. */
> >>> +#define XENVER_build_id 10
> >>> +struct xen_build_id {
> >>> +uint32_tlen; /* IN: size of buf[]. */
> >>> +#if defined(__STDC_V
On 16/02/16 20:22, Konrad Rzeszutek Wilk wrote:
> On Tue, Feb 16, 2016 at 08:09:13PM +, Andrew Cooper wrote:
>> On 12/02/16 18:05, Konrad Rzeszutek Wilk wrote:
>>
>> Building the hypervisor with buildid and making it available via
>> hypercall really should be split into two different patches,
On Tue, Feb 16, 2016 at 08:09:13PM +, Andrew Cooper wrote:
> On 12/02/16 18:05, Konrad Rzeszutek Wilk wrote:
>
> Building the hypervisor with buildid and making it available via
> hypercall really should be split into two different patches, especially
> given the complexity in each.
OK, will
On 12/02/16 18:05, Konrad Rzeszutek Wilk wrote:
> Signed-off-by: Konrad Rzeszutek Wilk
> ---
> xen/common/xsplice.c | 36
> 1 file changed, 28 insertions(+), 8 deletions(-)
>
> diff --git a/xen/common/xsplice.c b/xen/common/xsplice.c
> index 2ba5bb5..8c5557e 1
On 12/02/16 18:05, Konrad Rzeszutek Wilk wrote:
> As it should be an useful debug mechanism.
>
> Signed-off-by: Konrad Rzeszutek Wilk
> ---
> xen/common/xsplice.c | 18 +-
> 1 file changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/xen/common/xsplice.c b/xen/common/xsplice.
On 12/02/16 18:05, Konrad Rzeszutek Wilk wrote:
Building the hypervisor with buildid and making it available via
hypercall really should be split into two different patches, especially
given the complexity in each.
> The mechanism to get this is via the XENVER hypercall and
> we add a new sub-com
On Tue, Feb 16, 2016 at 06:37:46PM +0100, Roger Pau Monne wrote:
> After some discussion around the new boot ABI consensus has been reached
> about the layout and contents of the start info. The following patch updates
> the layout to what has been agreed.
.. It would be good to have an URL to the
flight 82876 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82876/
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 12/02/16 18:05, Konrad Rzeszutek Wilk wrote:
> diff --git a/xen/common/xsplice.c b/xen/common/xsplice.c
> index d863a99..65b1f11 100644
> --- a/xen/common/xsplice.c
> +++ b/xen/common/xsplice.c
> @@ -695,7 +695,7 @@ static int find_special_sections(struct payload *payload,
> if ( sec )
>
On 12/02/16 18:05, Konrad Rzeszutek Wilk wrote:
> diff --git a/xen/common/symbols.c b/xen/common/symbols.c
> index a59c59d..bf5623f 100644
> --- a/xen/common/symbols.c
> +++ b/xen/common/symbols.c
> @@ -17,6 +17,7 @@
> #include
> #include
> #include
> +#include
> #include
> #include
>
On 16/02/16 17:37, Roger Pau Monne wrote:
> After some discussion around the new boot ABI consensus has been reached
> about the layout and contents of the start info. The following patch updates
> the layout to what has been agreed.
>
> Also, the new layout is described in binary terms in order to
On 12/02/16 18:05, Konrad Rzeszutek Wilk wrote:
> diff --git a/xen/arch/x86/domain.c b/xen/arch/x86/domain.c
> index 9d43f7b..b5995b9 100644
> --- a/xen/arch/x86/domain.c
> +++ b/xen/arch/x86/domain.c
> @@ -36,6 +36,7 @@
> #include
> #include
> #include
> +#include
> #include
> #include
Hi Dario,
Since this patch did some obvious change, I will reply with
reviewed-by, although my reviewed-by does not count much. ;-)
On Tue, Feb 16, 2016 at 1:11 PM, Dario Faggioli
wrote:
>
> it is enabled for pretty much all of them already.
> There were just a few that had it disabled.
>
> When
when tracing runstate changes, the vcpu and domain IDs
are encoded in the lower and higher, respectively, parts
of a 32 bits integer. When decoding a trace with
xentrace_format, this makes it possible to display
such events like this:
CPU0 833435853624 (+ 768) running_to_runnable [ dom:vcpu
vcpu_wake() and vcpu_sleep() are called before the specific
schedulers wakeup and sleep routines (in fact, it is them
that calls those specific routine).
Make the trace reflect that, by moving the records up. In
fact, it is more natural and easy to find the record of
the event (e.g., the wakeup) *
as it is always acts on v->processor of the vcpu that
we are tickling.
Getting rid of it makes the code easier to understand
and better looking.
While there, remove a spurious blank line.
Signed-off-by: Dario Faggioli
Reviewed-by: Konrad Rzeszutek Wilk
---
Cc: George Dunlap
---
Changes from v
(i.e., domain creation and destruction) so the
trace will show properly decoded info, rather
than just a bunch of hex codes.
---
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
Cc: Olaf Hering
Cc: Konrad Rzeszutek Wilk
---
Changes from v1:
* new patch in the series.
---
tools
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
Cc: Olaf Hering
Cc: Konrad Rzeszutek Wilk
---
Changes from v2:
* new patch in the series.
---
tools/xentrace/formats |3 +++
1 file changed, 3 insertions(+)
diff --git a/tools/xentrace/for
so the trace will show properly decoded info,
rather than just a bunch of hex codes.
Signed-off-by: Dario Faggioli
Reviewed-by: Konrad Rzeszutek Wilk
---
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
Cc: Olaf Hering
Cc: Konrad Rzeszutek Wilk
---
Changes from v1:
* '} * r
so the trace will show properly decoded info,
rather than just a bunch of hex codes.
Signed-off-by: Dario Faggioli
Reviewed-by: Konrad Rzeszutek Wilk
---
Cc: George Dunlap
Cc: Meng Xu
Cc: Tianyang Chen
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
Cc: Olaf Hering
---
Changes from v1:
* '}
so the trace will show properly decoded info,
rather than just a bunch of hex codes.
Signed-off-by: Dario Faggioli
Reviewed-by: Konrad Rzeszutek Wilk
---
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
Cc: Olaf Hering
---
Changes from v1:
* '} * r =' turned into '} *r =', as
so the trace will show properly decoded info,
rather than just a bunch of hex codes.
Signed-off-by: Dario Faggioli
Reviewed-by: Konrad Rzeszutek Wilk
---
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
Cc: Olaf Hering
---
Changes from v1:
* SCHED_DOM_{ADD,REM} handling sligh
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
Cc: Meng Xu
Cc: Tianyang Chen
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
Cc: Olaf Hering
---
tools/xentrace/formats |6 ++
1 file changed, 6 insertions(+)
diff --git a/tools/xentrace/formats b/tools/xentrace/formats
index 6911f
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
Cc: Olaf Hering
---
Changes from v1:
* fix typo in two events (rq_idx/rq_id)., as requested during
review.
---
tools/xentrace/formats | 13 +
1 file changed, 13 insertions(+)
d
Signed-off-by: Dario Faggioli
Reviewed-by: Konrad Rzeszutek Wilk
---
Cc: George Dunlap
Cc: Ian Jackson
Cc: Ian Campbell
Cc: Wei Liu
Cc: Olaf Hering
---
tools/xentrace/formats |7 +++
1 file changed, 7 insertions(+)
diff --git a/tools/xentrace/formats b/tools/xentrace/formats
index
when tracing runstate changes, the vcpu and domain IDs
are encoded in the lower and higher, respectively, parts
of a 32 bits integer. When decoding a trace with
xentrace_format, this makes it possible to display
such events like this:
CPU0 833435853624 (+ 768) running_to_runnable [ dom:vcpu
to include the vcpu IDs, in a way that matches
how the "dom:vcpu" couple is displayed in other
events (runstate changes).
Also add the trace for TRC_SCHED_SHUTDOWN_CODE which
was missing and was done via SCHEDOP_shutdown_code hypercall.
(TRC_SCHED_SHUTDOWN trace was present).
Signed-off-by: Dario
it is enabled for pretty much all of them already.
There were just a few that had it disabled.
When tracing a scheduler, timing information is
really important, so enable it everywhere scheduling
related.
Note that this was not really a problem if looking
at the traces with xenalyze, but it was i
Hi,
Take 2 of this series. v1 is here:
http://lists.xenproject.org/archives/html/xen-devel/2016-02/msg01016.html
Konrad's feedback taken into acount, which basically meant modifying a little
bit patch 3 ("xen: sched: improve domain creation tracing"), and adding two
simple patches to xentrace f
by doing the following two things:
- move TRC_SCHED_DOM_{ADD,REM}, into the functions
that do the actual scheduling-related domain
initialization;
- add two 'generic' DOM_{ADD,REM} events. They're
made part of the TRC_DOM0 tracing class, as Dom0
is, usually, from where domains are c
flight 82734 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82734/
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
Roger Pau Monne writes ("[PATCH v4 4/4] libxl: fix cd-eject"):
> Current libxl__device_disk_set_backend implementation tried to guess the
> backend of devices with format LIBXL_DISK_FORMAT_EMPTY, which is of course
> doomed to fail since the disk is empty. Instead just return early from the
> funct
Wei Liu writes ("[PATCH] MAINTAINERS: add myself as seabios maintainer"):
> SEABIOS UPSTREAM
> M: Ian Campbell
> +M: Wei Liu
> S: Supported
> T: git git://xenbits.xen.org/seabios.git
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-de
On Tue, Feb 16, 2016 at 10:48 AM, Corneliu ZUZU
wrote:
> On 2/16/2016 6:02 PM, Tamas K Lengyel wrote:
>
>
>> @@ -143,77 +72,75 @@ int monitor_domctl(struct domain *d, struct
>> xen_domctl_monitor_op *mop)
>>
>> case XEN_DOMCTL_MONITOR_EVENT_MOV_TO_MSR:
>> {
>>
>
> So since we will now h
Jim Fehlig writes ("Re: [Xen-devel] [PATCH V13 5/5] xl: add pvusb commands"):
> I just noticed this is the case with network devices as well. E.g.
>
> #xl network-attach hvm-domU mac=00:16:3e:xx:yy:zz,bridge=br0
> libxl: error: libxl_device.c:1095:device_hotplug_child_death_cb: script: Could
> not
Olaf Hering writes ("Re: [PATCH v8 3/5] libxl: add support for vscsi"):
> On Mon, Feb 15, Ian Jackson wrote:
> > One reason you might define a virtual controller with no devices yet
> > is so that you have a stable and pre-expected device path for any
> > actual targets you choose to hotplug later.
On 2/16/2016 6:02 PM, Tamas K Lengyel wrote:
@@ -143,77 +72,75 @@ int monitor_domctl(struct domain *d, struct
xen_domctl_monitor_op *mop)
case XEN_DOMCTL_MONITOR_EVENT_MOV_TO_MSR:
{
So since we will now have two separate booleans, requested_status and
old_status an
Ian Campbell writes ("[PATCH] xl: close nullfd after dup2'ing it to stdin"):
> Taking care not to do so if nullfd happens (somehow) to have the same
> fd number as stdin/out/err.
I think that can only happen if the program (the process) has a
serious problem: ie, fd 0 1 or 2 would have to be close
On Wed, Jan 13, 2016 at 11:47:55AM +0100, Fabio Fantoni wrote:
[...]
> >>
> >>diff --git a/docs/man/xl.cfg.pod.5 b/docs/man/xl.cfg.pod.5
> >>index 3b695bd..04a96ba 100644
> >>--- a/docs/man/xl.cfg.pod.5
> >>+++ b/docs/man/xl.cfg.pod.5
> >>@@ -1607,82 +1607,6 @@ it.
> >> =back
> >>-=head3 Spice Gra
Wei Liu writes ("Re: [PATCH] libxl: close fd's in parent when spawning qdisk"):
> On Tue, Feb 16, 2016 at 11:49:53AM +, Ian Campbell wrote:
> > Coverity points out that these remain open in the parent upon
> > success, which is a resource leak.
>
> Acked-by: Wei Liu
Committed-by: Ian Jackson
Wei Liu writes ("Re: [PATCH] tools: libxl: NULL terminate partially constructed
hex string"):
> On Tue, Feb 16, 2016 at 11:18:20AM +, Ian Campbell wrote:
> > Coverity (correctly) complains that the strncpy(p, "0x", 2) will not
> > null terminate p.
> > Signed-off-by: Ian Campbell
>
> Acked-b
Current libxl__device_disk_set_backend implementation tried to guess the
backend of devices with format LIBXL_DISK_FORMAT_EMPTY, which is of course
doomed to fail since the disk is empty. Instead just return early from the
function if an empty disk is detected.
This fixes cd ejection.
Signed-off-
And use it as the default value for the VGA kind. This allows libxl to set
it to the default value later on when the domain type is known. For HVM
guests the default value is LIBXL_VGA_INTERFACE_TYPE_CIRRUS while for
HVMlite the default value is LIBXL_VGA_INTERFACE_TYPE_NONE.
Signed-off-by: Roger
Current implementation of elf_load_bsdsyms is broken when loading inside of
a HVM guest, because it assumes elf_memcpy_safe is able to write into guest
memory space, which it is not.
Take the oportunity to do some cleanup and properly document how
elf_{parse/load}_bsdsyms works. The new implementa
Hello,
This series contains some assorted patches and improvements. They are
completely ortogonal one fro meach other, so they can be applied
independently without issues. I've just decided to group them together
because I prefer it rather than spamming the list with 4 different threads.
#1 up
After some discussion around the new boot ABI consensus has been reached
about the layout and contents of the start info. The following patch updates
the layout to what has been agreed.
Also, the new layout is described in binary terms in order to avoid issues
with alignments when using C structs.
Wei Liu writes ("Re: [PATCH] tools: libxl: free devpath on failure in
libxl__blktap_devpath"):
> On Tue, Feb 16, 2016 at 11:09:43AM +, Ian Campbell wrote:
> > The underlying code paths in tap_ctl_create attempt to handle both
> > *devpath == NULL (by allocating) and *devpath != NULL (caller pr
Wei Liu writes ("[PATCH v2] stubdom: fix link farm runes"):
> Previously in the three problematic libraries all public headers were
> linked to source code directory. We should have created an include
> directory for each library and linked public headers there.
>
> Note that there was no breakage
Signed-off-by: Wei Liu
---
Cc: Ian Campbell
Cc: Ian Jackson
Cc: Jan Beulich
Cc: Keir Fraser
Cc: Tim Deegan
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index f07384c..c056284 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -299,6 +299,7 @@ F: x
On Tue, 16 Feb 2016, Arnd Bergmann wrote:
> The Xen framebuffer driver selects the xen keyboard driver, so the latter
> will be built-in if XEN_FBDEV_FRONTEND=y. However, when CONFIG_INPUT
> is a loadable module, this configuration cannot work. On mainline kernels,
> the symbol will be enabled but
On Tue, Jan 19, Chunyan Liu wrote:
> #xl usbctrl-attach test_vm version=1 ports=8
> #xl usbdev-attach test_vm hostbus=1 hostaddr=2
I think this does not handle the -N knob of xl. Other commands check the
global dryrun_only variable.
Olaf
___
Xen-de
Hi,
trying to bring up Xen on an ARM64 CA57 device (1 core atm) using a
recent Xen 4.7-unstable and Linux kernel 4.4.0+ I'm getting [1]. The
device tree configures arm,gic-400.
Regarding the , the Linux kernel boot messages are stopping
here. The debugger shows the system looping in xen/arch
On 16/02/16 15:38, Philipp Hahn wrote:
> Hello,
>
> I'm trying to understand Xens implementation of (wall-)clock time and
> observed a strange behaviour:
>
> Summary: When a Linux-PV-domU is migrated between two hosts, the
> "ntpdate" time jumps.
>
> Environment: xen-4.1 with linux-3.2 and linux
>
>
> @@ -143,77 +72,75 @@ int monitor_domctl(struct domain *d, struct
> xen_domctl_monitor_op *mop)
>
> case XEN_DOMCTL_MONITOR_EVENT_MOV_TO_MSR:
> {
>
So since we will now have two separate booleans, requested_status and
old_status and then manually verify they are opposite..
> -
flight 82711 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82711/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale 15 guest-start/debian.repeat fail REGR. vs. 82574
test-armhf-armhf-xl
Some constants defined in xen/include/public/xen.h are not usable in
assembler sources as they are either defined with "U" or "UL" suffixes
or they are inside #ifndef __ASSEMBLY__ areas.
Change this as grub2 could make use of those definitions.
This requires to move the definition of mk_unsigned_
Hello,
I'm trying to understand Xens implementation of (wall-)clock time and
observed a strange behaviour:
Summary: When a Linux-PV-domU is migrated between two hosts, the
"ntpdate" time jumps.
Environment: xen-4.1 with linux-3.2 and linux-3.10, ntpdate running in
all dom[0U].
1. If I start a n
config.h contains an unused definition of mk_unsigned_long().
Remove it.
Signed-off-by: Juergen Gross
---
xen/include/xen/config.h | 9 -
1 file changed, 9 deletions(-)
diff --git a/xen/include/xen/config.h b/xen/include/xen/config.h
index d780121..a992933 100644
--- a/xen/include/xen/
On Mon, Feb 15, Ian Jackson wrote:
> One reason you might define a virtual controller with no devices yet
> is so that you have a stable and pre-expected device path for any
> actual targets you choose to hotplug later.
Would it be acceptable to reuse the devid as the "group index"?
The various v
Ian Campbell writes ("[PATCH OSSTEST] crontab: Add a coverity run on a
Wednesday"):
> In addition to the current Sunday run.
>
> Projects of Xen's size are currently allowed 2 builds per week (max 1
> per day), so make use of both.
>
> Signed-off-by: Ian Campbell
Acked-by: Ian Jackson
__
This patch modified the control ring protocol (of which there is
not yet an implementation) to make it more general. Most of the
concepts are not limited to toeplitz hashing so it's best not to
make them unnecessarily specific.
Apart from changing the names of various definitions and modifying
com
On Tuesday 16 February 2016 12:14:14 Stefano Stabellini wrote:
> > at all.
>
> Please correct me if I am wrong, but the difference is that with this
> change if INPUT=m, then the build system would ask the user whether she
> wants to select INPUT_XEN_KBDDEV_FRONTEND as m or y, instead of
> uncondi
In addition to the current Sunday run.
Projects of Xen's size are currently allowed 2 builds per week (max 1
per day), so make use of both.
Signed-off-by: Ian Campbell
---
This change is already live in the production colo
---
crontab | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
The Xen framebuffer driver selects the xen keyboard driver, so the latter
will be built-in if XEN_FBDEV_FRONTEND=y. However, when CONFIG_INPUT
is a loadable module, this configuration cannot work. On mainline kernels,
the symbol will be enabled but not used, while in combination with
a patch I have
On Tue, 2016-02-16 at 14:17 +, Paul Durrant wrote:
> > -Original Message-
> > From: Ian Campbell [mailto:ian.campb...@citrix.com]
> > Sent: 16 February 2016 14:13
> > To: Paul Durrant; xen-de...@lists.xenproject.org
> > Cc: Ian Jackson; Jan Beulich; Keir (Xen.org); Tim (Xen.org)
> > Sub
> -Original Message-
> From: Ian Campbell [mailto:ian.campb...@citrix.com]
> Sent: 16 February 2016 14:13
> To: Paul Durrant; xen-de...@lists.xenproject.org
> Cc: Ian Jackson; Jan Beulich; Keir (Xen.org); Tim (Xen.org)
> Subject: Re: [PATCH v2] public/io/netif.h: make control ring hash prot
> -Original Message-
[snip]
> >
> > > > *
> > > > - * NETIF_CTRL_TYPE_SET_TOEPLITZ_MAPPING_ORDER
> > > > - * --
> > > > + * NETIF_CTRL_TYPE_SET_HASH_MAPPING_ORDER
> > >
> > > This one needs a similar "if the hash algorithm requires it" wording
> > >
>>> On 05.02.16 at 14:42, wrote:
> --- a/xen/include/asm-x86/processor.h
> +++ b/xen/include/asm-x86/processor.h
> @@ -574,6 +574,34 @@ void microcode_set_module(unsigned int);
> int microcode_update(XEN_GUEST_HANDLE_PARAM(const_void), unsigned long len);
> int microcode_resume_cpu(unsigned int
flight 82689 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/82689/
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 Tue, 2016-02-16 at 14:02 +, Paul Durrant wrote:
> > -Original Message-
> [snip]
> > >
> > > > > *
> > > > > - * NETIF_CTRL_TYPE_SET_TOEPLITZ_MAPPING_ORDER
> > > > > - * --
> > > > > + * NETIF_CTRL_TYPE_SET_HASH_MAPPING_ORDER
> > > >
> > > >
>>> On 05.02.16 at 14:42, wrote:
> Before c/s 44e24f8567 "x86: don't call generic_identify() redundantly", the
> commandline-provided masks would take effect in Xen's view of the features.
>
> As the masks got applied after the query for features, the redundant call to
> generic_identify() would
On 16/02/16 15:04, Jan Beulich wrote:
On 16.02.16 at 14:02, wrote:
>> Some constants defined in xen/include/public/xen.h are not usable in
>> assembler sources as they are either defined with "U" or "UL" suffixes
>> or they are inside #ifndef __ASSEMBLY__ areas.
>>
>> Change this as grub2 cou
1 - 100 of 162 matches
Mail list logo
