flight 44380 distros-debian-snapshot real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44380/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf 3 host-install(3) broken R
flight 93374 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93374/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-rtds 15 guest-start/debian.repeat fail REGR. vs. 93237
test-amd64-amd64-xl-qemuu-wi
>>> On 02.05.16 at 18:28, wrote:
> Been playing with the altp2m code and noticed that it's not behaving in Xen
> 4.7 tree.
> Two changesets have been identified as where the be behavior changes.
>
> The change is commit bd2239d9fa975a1ee5bcd27c218ae042cd0a57bc,
> x86/HVM: always intercept
flight 93379 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93379/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
test-amd64-amd64-xl-qemuu-ov
>>> On 29.04.16 at 18:12, wrote:
> On 04/09/16 08:54, Razvan Cojocaru wrote:
>> It is meaningless (and potentially dangerous - see
>> hvmemul_virtual_to_linear())
>> to set mem_access_emulate_each_rep before xc_monitor_enable() (which
>> allocates
>> vcpu->arch.vm_event) has been called, so retu
On 05/03/2016 11:14 AM, Jan Beulich wrote:
On 29.04.16 at 18:12, wrote:
>> On 04/09/16 08:54, Razvan Cojocaru wrote:
>>> It is meaningless (and potentially dangerous - see
>>> hvmemul_virtual_to_linear())
>>> to set mem_access_emulate_each_rep before xc_monitor_enable() (which
>>> allocates
>>> On 29.04.16 at 20:07, wrote:
> Add headers to the covered list.
>
> Signed-off-by: Tamas K Lengyel
While the rest of this series doesn't look like it wants to go in for 4.7,
I think this one can and should. Thoughts?
Jan
___
Xen-devel mailing l
On 05/03/2016 11:18 AM, Jan Beulich wrote:
On 29.04.16 at 20:07, wrote:
>> Add headers to the covered list.
>>
>> Signed-off-by: Tamas K Lengyel
>
> While the rest of this series doesn't look like it wants to go in for 4.7,
> I think this one can and should. Thoughts?
FWIW, I agree, and it
>>> On 03.05.16 at 10:20, wrote:
> On 05/03/2016 11:18 AM, Jan Beulich wrote:
> On 29.04.16 at 20:07, wrote:
>>> Add headers to the covered list.
>>>
>>> Signed-off-by: Tamas K Lengyel
>>
>> While the rest of this series doesn't look like it wants to go in for 4.7,
>> I think this one can a
On Tue, May 03, 2016 at 02:18:35AM -0600, Jan Beulich wrote:
> >>> On 29.04.16 at 20:07, wrote:
> > Add headers to the covered list.
> >
> > Signed-off-by: Tamas K Lengyel
>
> While the rest of this series doesn't look like it wants to go in for 4.7,
> I think this one can and should. Thoughts?
On 2016/4/30 22:14, Shannon Zhao wrote:
>> I already proposed when this patch was first under review to make the
>> > arm_enable_runtime_services() function bail early without error if the
>> > EFI_RUNTIME_SERVICES flag is already set, and the xen code could set
>> > that bit as well when it inst
On 02/05/16 13:55, Jan Beulich wrote:
> ... and hence should not live in the HVM part of the PV/HVM union. In
> fact it's not even architecture specific (there already is a per-arch
> extension type to it), so it gets moved out right to common struct
> domain.
>
> Signed-off-by: Jan Beulich
Yikes
>>> On 03.05.16 at 11:36, wrote:
> On 02/05/16 13:55, Jan Beulich wrote:
>> ... and hence should not live in the HVM part of the PV/HVM union. In
>> fact it's not even architecture specific (there already is a per-arch
>> extension type to it), so it gets moved out right to common struct
>> domain
On 03/05/16 10:59, Jan Beulich wrote:
On 03.05.16 at 11:36, wrote:
>> On 02/05/16 13:55, Jan Beulich wrote:
>>> ... and hence should not live in the HVM part of the PV/HVM union. In
>>> fact it's not even architecture specific (there already is a per-arch
>>> extension type to it), so it gets
On Tue, May 03, 2016 at 12:20:45AM +, osstest service owner wrote:
> flight 93364 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/93364/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-armhf-ar
On 03/05/16 11:18, Andrew Cooper wrote:
On 03/05/16 10:59, Jan Beulich wrote:
On 03.05.16 at 11:36, wrote:
On 02/05/16 13:55, Jan Beulich wrote:
... and hence should not live in the HVM part of the PV/HVM union. In
fact it's not even architecture specific (there already is a per-arch
extensio
(CC Wei for release-ack)
Hello Kyle,
On 28/04/16 18:14, Kyle Temkin wrote:
From: "Kyle J. Temkin"
The ARMv8 architecture has a SPSel ("stack pointer selection") machine
register that allows us to determine which exception level's stack
pointer is loaded when an exception occurs. As we don't w
On 29/04/16 17:16, Roger Pau Monne wrote:
>
> It has also been suggested that the privcmd driver simply doesn't translate
> error codes at all, and then let the applications figure out if the error
> code comes from Xen or from the OS. IMHO, this is impossible to achieve,
> because the ioctl sy
Currently FreeBSD lacks the ENODATA errno value, so the privcmd driver
always translates ENODATA to ENOENT, add a define to libxl in order to
correctly match ENODATA with ENOENT on FreeBSD.
Signed-off-by: Roger Pau Monné
---
Cc: Ian Jackson
Cc: Wei Liu
---
tools/libxl/libxl_osdeps.h | 7 ++
The errno values returned by libxc are already translated into the
underlying OS error space, so it's wrong to compare them against Xen error
codes.
Signed-off-by: Roger Pau Monné
---
Cc: Ian Jackson
Cc: Wei Liu
---
tools/libxl/libxl_dom_save.c | 2 +-
1 file changed, 1 insertion(+), 1 deletio
They are equivalent, but using ELFOSABI_NONE is more correct in this
context.
Signed-off-by: Roger Pau Monné
---
Cc: Konrad Rzeszutek Wilk
Cc: Ross Lagerwall
---
xen/common/xsplice_elf.c | 2 +-
xen/include/xen/elfstructs.h | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git
Hello,
This series contains bugfixes for xSplice, that popped up when testing it on
OSes != Linux. Patch 6/6 is a bugfix for the migration code, that was
incorrectly using a XEN_E* value.
I think they should all go into 4.7 on the basis that they are bugfixes.
Roger.
_
The calling convention used by the FreeBSD ELF OSABI is exactly the same as
the the one defined by System V, so payloads with a FreeBSD OSABI should be
accepted by the xsplice machinery.
Signed-off-by: Roger Pau Monné
---
Cc: Konrad Rzeszutek Wilk
Cc: Ross Lagerwall
---
xen/common/xsplice_elf.
Avoid using system errno values when comparing with Xen errno values.
Signed-off-by: Roger Pau Monné
---
Cc: Konrad Rzeszutek Wilk
Cc: Ross Lagerwall
Cc: Ian Jackson
Cc: Wei Liu
---
Using errno values inside of hypercall structs is not right IMHO, but there
are already several occurrences of
Some error paths incorrectly used rc instead of errno.
Signed-off-by: Roger Pau Monné
---
Cc: Konrad Rzeszutek Wilk
Cc: Ross Lagerwall
Cc: Ian Jackson
Cc: Wei Liu
---
Changes since v1:
- Fix error message.
---
tools/misc/xen-xsplice.c | 7 ---
1 file changed, 4 insertions(+), 3 deletion
On 29/04/16 15:28, Peng Fan wrote:
Hi Julien,
Hello Peng,
On Thu, Apr 28, 2016 at 02:14:58PM +0100, Julien Grall wrote:
Is there any big difference between XEN SMMU driver and linux SMMU driver?
I know that XEN only support Stage 2. But the initliaization flow is almost the
same.
The SMMU
On Tue, May 03, 2016 at 12:55:07PM +0200, Roger Pau Monne wrote:
> Avoid using system errno values when comparing with Xen errno values.
>
> Signed-off-by: Roger Pau Monné
Acked-by: Wei Liu
> ---
> Cc: Konrad Rzeszutek Wilk
> Cc: Ross Lagerwall
> Cc: Ian Jackson
> Cc: Wei Liu
> ---
> Using
On Tue, May 03, 2016 at 12:55:10PM +0200, Roger Pau Monne wrote:
> The errno values returned by libxc are already translated into the
> underlying OS error space, so it's wrong to compare them against Xen error
> codes.
>
> Signed-off-by: Roger Pau Monné
Acked-by: Wei Liu
Ian, this should be b
On Tue, May 03, 2016 at 12:55:05PM +0200, Roger Pau Monne wrote:
> Currently FreeBSD lacks the ENODATA errno value, so the privcmd driver
> always translates ENODATA to ENOENT, add a define to libxl in order to
> correctly match ENODATA with ENOENT on FreeBSD.
>
> Signed-off-by: Roger Pau Monné
Hi Tamas,
On 29/04/16 19:07, Tamas K Lengyel wrote:
The ARM SMC instructions are already configured to trap to Xen by default. In
this patch we allow a user-space process in a privileged domain to receive
notification of when such event happens through the vm_event subsystem by
introducing the P
On Tue, May 03, 2016 at 12:55:06PM +0200, Roger Pau Monne wrote:
> Some error paths incorrectly used rc instead of errno.
>
> Signed-off-by: Roger Pau Monné
Acked-by: Wei Liu
> ---
> Cc: Konrad Rzeszutek Wilk
> Cc: Ross Lagerwall
> Cc: Ian Jackson
> Cc: Wei Liu
> ---
> Changes since v1:
>
On 03/05/16 11:55, Roger Pau Monne wrote:
> The calling convention used by the FreeBSD ELF OSABI is exactly the same as
> the the one defined by System V, so payloads with a FreeBSD OSABI should be
> accepted by the xsplice machinery.
>
> Signed-off-by: Roger Pau Monné
> ---
> Cc: Konrad Rzeszutek
On 03/05/16 11:55, Roger Pau Monne wrote:
> They are equivalent, but using ELFOSABI_NONE is more correct in this
> context.
>
> Signed-off-by: Roger Pau Monné
Reviewed-by: Andrew Cooper
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.x
On 03/05/16 02:01, Jim Fehlig wrote:
> Hi all,
>
> This patch adds support for Xen migration stream V2 to the libvirt
> libxl driver. In the process it fixes save/restore and migration
> tests in OSSTest, which have been failing since libvirt commit
> e7440656.
>
> Patch1 changes the libxl API requ
Hi Jan,
On 02/05/16 13:55, Jan Beulich wrote:
... and hence should not live in the HVM part of the PV/HVM union. In
fact it's not even architecture specific (there already is a per-arch
extension type to it), so it gets moved out right to common struct
domain.
Signed-off-by: Jan Beulich
For
On April 29, 2016 12:11 AM, wrote:
> On April 28, 2016 11:13 PM, Jan Beulich wrote:
> > >>> On 25.04.16 at 10:40, wrote:
> > > With other patches also in place, still not work.
> > > Jianzhong has been left and Quan will take over the task.
> >
> > May I ask for another try, with current tip of
Hi Dario and George,
What is the status of this patch? It would be nice to have it for Xen
4.7 to avoid unwanted crash when secondary CPUs fails to come online.
Regards,
On 26/04/16 18:49, Dario Faggioli wrote:
On Tue, 2016-04-26 at 15:25 +0100, Julien Grall wrote:
Hi Dario,
Hi,
A coupl
Hi all
Xen 4.7 RC1 is tagged. You can check that out from xen.git:
git://xenbits.xen.org/xen.git 4.7.0-rc1
Please send bug reports and test reports to
xen-de...@lists.xenproject.org. When sending bug reports, please CC
relevant maintainers and me (wei.l...@citrix.com).
Thanks
Wei.
__
On Mon, May 02, 2016 at 07:01:17PM -0600, Jim Fehlig wrote:
> In LIBXL_API_VERSION 0x040400, the libxl_domain_create_restore API
> gained a parameter for specifying restore parameters. Switch to
> using version 0x040400, which will be useful in a subsequent commit
> to specify the Xen migration str
On Mon, May 02, 2016 at 07:01:16PM -0600, Jim Fehlig wrote:
> Hi all,
>
> This patch adds support for Xen migration stream V2 to the libvirt
> libxl driver. In the process it fixes save/restore and migration
> tests in OSSTest, which have been failing since libvirt commit
> e7440656.
>
> Patch1 c
On Tue, May 3, 2016 at 2:03 PM, Julien Grall wrote:
> Hi Dario and George,
>
> What is the status of this patch? It would be nice to have it for Xen 4.7 to
> avoid unwanted crash when secondary CPUs fails to come online.
Wei, can you put this on your release blockers list? (Julien, I take
it thi
Hi George,
On 03/05/16 14:20, George Dunlap wrote:
On Tue, May 3, 2016 at 2:03 PM, Julien Grall wrote:
Hi Dario and George,
What is the status of this patch? It would be nice to have it for Xen 4.7 to
avoid unwanted crash when secondary CPUs fails to come online.
Wei, can you put this on yo
On Tue, May 03, 2016 at 02:20:05PM +0100, George Dunlap wrote:
> On Tue, May 3, 2016 at 2:03 PM, Julien Grall wrote:
> > Hi Dario and George,
> >
> > What is the status of this patch? It would be nice to have it for Xen 4.7 to
> > avoid unwanted crash when secondary CPUs fails to come online.
>
>
On Tue, May 03, 2016 at 12:55:07PM +0200, Roger Pau Monne wrote:
> Avoid using system errno values when comparing with Xen errno values.
>
> Signed-off-by: Roger Pau Monné
Reviewed-by: Konrad Rzeszutek Wilk
And since Wei acked it I may as well put it in now after some tests.
> ---
> Cc: Konra
flight 93402 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93402/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 6 xen-boot fail REGR. vs. 93366
Tests which di
On Tue, May 03, 2016 at 09:27:23AM -0400, Konrad Rzeszutek Wilk wrote:
> On Tue, May 03, 2016 at 12:55:07PM +0200, Roger Pau Monne wrote:
> > Avoid using system errno values when comparing with Xen errno values.
> >
> > Signed-off-by: Roger Pau Monné
>
> Reviewed-by: Konrad Rzeszutek Wilk
>
>
On Tue, May 03, 2016 at 02:29:20PM +0100, Wei Liu wrote:
> On Tue, May 03, 2016 at 09:27:23AM -0400, Konrad Rzeszutek Wilk wrote:
> > On Tue, May 03, 2016 at 12:55:07PM +0200, Roger Pau Monne wrote:
> > > Avoid using system errno values when comparing with Xen errno values.
> > >
> > > Signed-off-
On Mon, May 02, 2016 at 06:55:35AM -0600, Jan Beulich wrote:
> ... and hence should not live in the HVM part of the PV/HVM union. In
> fact it's not even architecture specific (there already is a per-arch
> extension type to it), so it gets moved out right to common struct
> domain.
>
> Signed-off
On Tue, May 03, 2016 at 02:10:35PM +0100, Wei Liu wrote:
> Hi all
>
> Xen 4.7 RC1 is tagged. You can check that out from xen.git:
>
> git://xenbits.xen.org/xen.git 4.7.0-rc1
>
> Please send bug reports and test reports to
> xen-de...@lists.xenproject.org. When sending bug reports, please CC
>
On Tue, May 03, 2016 at 11:43:34AM +0100, Julien Grall wrote:
> (CC Wei for release-ack)
>
> Hello Kyle,
>
> On 28/04/16 18:14, Kyle Temkin wrote:
> >From: "Kyle J. Temkin"
> >
> >The ARMv8 architecture has a SPSel ("stack pointer selection") machine
> >register that allows us to determine which
>>> On 03.05.16 at 14:50, wrote:
> On April 29, 2016 12:11 AM, wrote:
>> On April 28, 2016 11:13 PM, Jan Beulich wrote:
>> > >>> On 25.04.16 at 10:40, wrote:
>> > > With other patches also in place, still not work.
>> > > Jianzhong has been left and Quan will take over the task.
>> >
>> > May
On 5/2/16 10:18 AM, Konrad Rzeszutek Wilk wrote:
> On Sun, May 01, 2016 at 11:10:42PM -0500, Doug Goldstein wrote:
>> Convert 'verbose', which was enabled by 'debug=y' to Kconfig as
>> CONFIG_VERBOSE_DEBUG which is enabled by default when CONFIG_DEBUG is
>> enabled.
>>
>> Signed-off-by: Doug Goldst
>>> On 17.03.16 at 09:03, wrote:
> Since such guests' kernel code runs in ring 1, their memory accesses,
> at the paging layer, are supervisor mode ones, and hence subject to
> SMAP/SMEP checks. Such guests cannot be expected to be aware of those
> two features though (and so far we also don't exp
This run is configured for baseline tests only.
flight 44381 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44381/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemuu-rhel6hvm-amd 9 redhat-i
On Tue, May 03, 2016 at 11:58:17AM +0100, Julien Grall wrote:
>On 29/04/16 15:28, Peng Fan wrote:
>>Hi Julien,
>
>Hello Peng,
>
>>On Thu, Apr 28, 2016 at 02:14:58PM +0100, Julien Grall wrote:
Is there any big difference between XEN SMMU driver and linux SMMU driver?
I know that XEN only sup
On 03/05/16 14:58, Jan Beulich wrote:
On 17.03.16 at 09:03, wrote:
>> Since such guests' kernel code runs in ring 1, their memory accesses,
>> at the paging layer, are supervisor mode ones, and hence subject to
>> SMAP/SMEP checks. Such guests cannot be expected to be aware of those
>> two fe
>>> On 03.05.16 at 12:55, wrote:
> They are equivalent, but using ELFOSABI_NONE is more correct in this
> context.
>
> Signed-off-by: Roger Pau Monné
Pick one of
{Acked,Suggested}-by: Jan Beulich
___
Xen-devel mailing list
Xen-devel@lists.xen.org
ht
>>> On 03.05.16 at 12:55, wrote:
> The calling convention used by the FreeBSD ELF OSABI is exactly the same as
> the the one defined by System V, so payloads with a FreeBSD OSABI should be
> accepted by the xsplice machinery.
Well, you realize that the ABI is more than just the calling convention
On 04/27/2016 10:14 AM, Razvan Cojocaru wrote:
> On 04/27/2016 09:22 AM, Jan Beulich wrote:
> On 26.04.16 at 19:23, wrote:
>>> On 04/26/16 19:03, George Dunlap wrote:
On 19/04/16 17:35, Jan Beulich wrote:
Razvan Cojocaru 04/19/16 1:01 PM >>>
>> I think this might be because
>>> On 03.05.16 at 16:10, wrote:
> On 03/05/16 14:58, Jan Beulich wrote:
> On 17.03.16 at 09:03, wrote:
>>> Since such guests' kernel code runs in ring 1, their memory accesses,
>>> at the paging layer, are supervisor mode ones, and hence subject to
>>> SMAP/SMEP checks. Such guests cannot be
This converts the debug options from xen/Rules.mk to Kconfig. I'm unsure
if I properly described PERF_ARRAYS but otherwise the other descriptions
have either been provided by maintainers or improved by maintainers so
I am confident about those.
The big departure from Rules.mk is how NDEBUG is turn
Convert the 'perfc' and 'perfc_arrays' options to Kconfig as
CONFIG_PERF_COUNTERS and CONFIG_PERF_ARRAYS to minimize code changes.
Signed-off-by: Doug Goldstein
---
CC: Jan Beulich
CC: Andrew Cooper
---
INSTALL | 2 --
xen/Kconfig.debug | 15 +
Convert 'verbose', which was enabled by 'debug=y' to Kconfig as
CONFIG_VERBOSE_DEBUG which is enabled by default when CONFIG_DEBUG is
enabled.
Signed-off-by: Doug Goldstein
---
CC: Stefano Stabellini
CC: Julien Grall
CC: Jan Beulich
CC: Andrew Cooper
CC: Daniel De Graaf
---
INSTALL
Converts the frame_pointer option to a Kconfig option.
Signed-off-by: Doug Goldstein
---
CC: Andrew Cooper
CC: George Dunlap
CC: Ian Jackson
CC: Jan Beulich
CC: Konrad Rzeszutek Wilk
CC: Stefano Stabellini
CC: Tim Deegan
CC: Wei Liu
---
INSTALL | 1 -
xen/Kconfig.debug | 8
This allows 'make debug=n' and 'make debug=y' work as it did previously
but only in the case of the user not having an existing .config file
from a 'make menuconfig'. This is because the command line 'debug' flag
can only be used to set the default value and if the user has already
built up a confi
Convert the 'lock_profile' option to Kconfig as CONFIG_LOCK_PROFILE.
Signed-off-by: Doug Goldstein
---
CC: Stefano Stabellini
CC: Julien Grall
CC: Jan Beulich
CC: Andrew Cooper
---
INSTALL| 1 -
xen/Kconfig.debug | 8
xen/Rules.mk | 2 --
There are a number of debugging options for Xen so the idea is to have a
menu to group them all together. Enabling this menu item will also
disable NDEBUG which will result in more debug prints. This was
previously wired into the 'debug=y' command line option.
Signed-off-by: Doug Goldstein
---
CC
>>> On 03.05.16 at 16:20, wrote:
> I've kept experimenting with the patch but can't quite figure out why
> minimizing the lock scope to the writeback part would not be sufficient,
> but it isn't.
>
> I.e. with this code:
>
> 3824 writeback:
> 3825 ops->smp_lock(lock_prefix);
> 3826 swit
Convert the crash_debug option to Kconfig as CONFIG_CRASH_DEBUG. This
was previously togglable on the command line so this adds a message for
users enabling it from the command line to tell them to enable it from
make menuconfig.
Signed-off-by: Doug Goldstein
---
CC: Jan Beulich
CC: Andrew Coope
>>> On 03.05.16 at 16:29, wrote:
> --- a/xen/include/xen/config.h
> +++ b/xen/include/xen/config.h
> @@ -81,4 +81,8 @@
> /* allow existing code to work with Kconfig variable */
> #define NR_CPUS CONFIG_NR_CPUS
>
> +#ifndef CONFIG_DEBUG
> +#define NDEBUG
> +#endif
At the same time you should d
On 5/3/16 9:38 AM, Jan Beulich wrote:
On 03.05.16 at 16:29, wrote:
>> --- a/xen/include/xen/config.h
>> +++ b/xen/include/xen/config.h
>> @@ -81,4 +81,8 @@
>> /* allow existing code to work with Kconfig variable */
>> #define NR_CPUS CONFIG_NR_CPUS
>>
>> +#ifndef CONFIG_DEBUG
>> +#define
On 05/03/2016 05:30 PM, Jan Beulich wrote:
On 03.05.16 at 16:20, wrote:
>> I've kept experimenting with the patch but can't quite figure out why
>> minimizing the lock scope to the writeback part would not be sufficient,
>> but it isn't.
>>
>> I.e. with this code:
>>
>> 3824 writeback:
>> 38
>>> On 03.05.16 at 16:29, wrote:
> Convert the crash_debug option to Kconfig as CONFIG_CRASH_DEBUG. This
> was previously togglable on the command line so this adds a message for
> users enabling it from the command line to tell them to enable it from
> make menuconfig.
>
> Signed-off-by: Doug Go
On 03/05/16 15:29, Doug Goldstein wrote:
> diff --git a/xen/Kconfig.debug b/xen/Kconfig.debug
> index e5179f4..04f672f 100644
> --- a/xen/Kconfig.debug
> +++ b/xen/Kconfig.debug
> @@ -5,3 +5,14 @@ menuconfig DEBUG
> If you want to debug Xen say Y and select any additional debugging
>
>>> On 03.05.16 at 16:29, wrote:
> --- a/xen/Kconfig.debug
> +++ b/xen/Kconfig.debug
> @@ -15,4 +15,11 @@ config CRASH_DEBUG
> If you want to be able to attach gdb to Xen to be able to debug
> Xen if it crashes then say Y.
>
> +config VERBOSE_DEBUG
> + bool "Verbose debug mes
On 5/3/16 9:43 AM, Jan Beulich wrote:
On 03.05.16 at 16:29, wrote:
>> Convert the crash_debug option to Kconfig as CONFIG_CRASH_DEBUG. This
>> was previously togglable on the command line so this adds a message for
>> users enabling it from the command line to tell them to enable it from
>> m
>>> On 03.05.16 at 16:29, wrote:
> --- a/xen/Kconfig.debug
> +++ b/xen/Kconfig.debug
> @@ -15,6 +15,14 @@ config CRASH_DEBUG
> If you want to be able to attach gdb to Xen to be able to debug
> Xen if it crashes then say Y.
>
> +config FRAME_POINTER
> + bool "Compile Xen with
>>> On 03.05.16 at 16:29, wrote:
> This allows 'make debug=n' and 'make debug=y' work as it did previously
> but only in the case of the user not having an existing .config file
> from a 'make menuconfig'. This is because the command line 'debug' flag
> can only be used to set the default value an
>>> On 03.05.16 at 16:29, wrote:
> Convert the 'perfc' and 'perfc_arrays' options to Kconfig as
> CONFIG_PERF_COUNTERS and CONFIG_PERF_ARRAYS to minimize code changes.
>
> Signed-off-by: Doug Goldstein
> ---
> CC: Jan Beulich
> CC: Andrew Cooper
Again too narrow a Cc list.
> --- a/xen/Kconfi
>>> On 03.05.16 at 16:29, wrote:
> Convert the 'lock_profile' option to Kconfig as CONFIG_LOCK_PROFILE.
>
> Signed-off-by: Doug Goldstein
Subject to transformations paralleling such requested on earlier
patches:
Reviewed-by: Jan Beulich
___
Xen-dev
>>> On 03.05.16 at 16:29, wrote:
> --- /dev/null
> +++ b/xen/Kconfig.debug
> @@ -0,0 +1,7 @@
> +
> +menuconfig DEBUG
> + bool "Debugging Options"
One more thing: In the unstable branch this should really default to
y, and the release check list should be adjusted to say that this
default need
On Thu, Mar 10, 2016 at 04:19:30PM +0100, Juergen Gross wrote:
> Add a backend for para-virtualized USB devices for xen domains.
>
> The backend is using host-libusb to forward USB requests from a
> domain via libusb to the real device(s) passed through.
>
> Signed-off-by: Juergen Gross
> ---
[
On Tue, May 03, Wei Liu wrote:
> Xen 4.7 RC1 is tagged. You can check that out from xen.git:
This is a release, and the release checklist should have been applied to
staging. Various things refer still to 4.6, like SONAMEs and pkgconfig
output.
Olaf
_
On Tue, May 03, 2016 at 05:09:14PM +0200, Olaf Hering wrote:
> On Tue, May 03, Wei Liu wrote:
>
> > Xen 4.7 RC1 is tagged. You can check that out from xen.git:
>
> This is a release, and the release checklist should have been applied to
> staging. Various things refer still to 4.6, like SONAMEs a
>>> On 03.05.16 at 16:41, wrote:
> On 05/03/2016 05:30 PM, Jan Beulich wrote:
> On 03.05.16 at 16:20, wrote:
>>> I've kept experimenting with the patch but can't quite figure out why
>>> minimizing the lock scope to the writeback part would not be sufficient,
>>> but it isn't.
>>>
>>> I.e. wi
flight 93381 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93381/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
build-i386-rumpuserxen6 xen-buildfail like 93337
build-amd64-rumpuserxen
>>> On 03.05.16 at 16:47, wrote:
> On 03/05/16 15:29, Doug Goldstein wrote:
>> diff --git a/xen/Kconfig.debug b/xen/Kconfig.debug
>> index e5179f4..04f672f 100644
>> --- a/xen/Kconfig.debug
>> +++ b/xen/Kconfig.debug
>> @@ -5,3 +5,14 @@ menuconfig DEBUG
>>If you want to debug Xen say Y and
On 03/05/16 16:05, Jan Beulich wrote:
On 03.05.16 at 16:29, wrote:
>> --- /dev/null
>> +++ b/xen/Kconfig.debug
>> @@ -0,0 +1,7 @@
>> +
>> +menuconfig DEBUG
>> +bool "Debugging Options"
> One more thing: In the unstable branch this should really default to
> y, and the release check list s
I want to test if my processor support VMFUNC which is described as:
>
>
> The IA32_VMX_VMFUNC MSR exists only on processors that support the
> 1-setting of the “activate secondary controls” VM-execution control (only if*
> bit 63 of the IA32_VMX_PROCBASED_CTLS MSR is 1*) and the 1-setting of the
>
>>> On 03.05.16 at 17:10, wrote:
> On 03/05/16 16:05, Jan Beulich wrote:
> On 03.05.16 at 16:29, wrote:
>>> --- /dev/null
>>> +++ b/xen/Kconfig.debug
>>> @@ -0,0 +1,7 @@
>>> +
>>> +menuconfig DEBUG
>>> + bool "Debugging Options"
>> One more thing: In the unstable branch this should really d
>>> On 03.05.16 at 16:48, wrote:
> On 5/3/16 9:43 AM, Jan Beulich wrote:
> On 03.05.16 at 16:29, wrote:
>>> Convert the crash_debug option to Kconfig as CONFIG_CRASH_DEBUG. This
>>> was previously togglable on the command line so this adds a message for
>>> users enabling it from the command
On Thu, Mar 10, 2016 at 04:19:29PM +0100, Juergen Gross wrote:
> Introduce a new dummy system device serving as parent for virtual
> buses. This will enable new pv backends to introduce virtual buses
> which are removable again opposed to system buses which are meant
> to stay once added.
>
> Sign
flight 93406 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93406/
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 Tue, May 03, 2016 at 11:01:32PM +0800, Big Strong wrote:
> I want to test if my processor support VMFUNC which is described as:
> >
> >
> > The IA32_VMX_VMFUNC MSR exists only on processors that support the
> > 1-setting of the “activate secondary controls” VM-execution control (only
> > if*
>
From systemd change log, since version 209, libsystemd.so contain
everything, including libsystemd-daemon.so. Distro may, or may not provide
the compatibility libraries which libsystemd-daemon is part of.
So, if libsystemd-daemon is not available, check for the presence of
a recent enough libsyste
When showing the CPU state (e.g., after a crash) the dump of code
around RIP is incorrect.
Incorrect:
Xen code around (...):
00 c6 c1 ee 08 48 c1 e0 <04> 03 04 f1 8b ...
^^ Uninitialized ^^ Missing 0x48
Correct:
Xen code around (...):
c6 c1 ee 08 48 c1 e0 04 <48
On Fri, Apr 01, 2016 at 12:45:26PM -0400, Konrad Rzeszutek Wilk wrote:
Hey Wei, Ian,
We really need this for Xen 4.7 - otherwise you cannot build qemu-trad under
Fedora Core 23:
home/konrad/ssd/konrad/xen/tools/qemu-xen-traditional-dir/hw/usb-net.c: In
function ‘usbnet_receive’:
/home/konrad/ss
On 03/05/16 17:15, David Vrabel wrote:
> When showing the CPU state (e.g., after a crash) the dump of code
> around RIP is incorrect.
>
> Incorrect:
>
> Xen code around (...):
> 00 c6 c1 ee 08 48 c1 e0 <04> 03 04 f1 8b ...
> ^^ Uninitialized ^^ Missing 0x48
>
> Correct:
>
>
On Tue, May 03, 2016 at 05:19:26PM +0100, Andrew Cooper wrote:
> On 03/05/16 17:15, David Vrabel wrote:
> > When showing the CPU state (e.g., after a crash) the dump of code
> > around RIP is incorrect.
> >
> > Incorrect:
> >
> > Xen code around (...):
> > 00 c6 c1 ee 08 48 c1 e0 <04> 03
flight 93388 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93388/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt 14 guest-saverestore fail REGR. vs. 91479
test-amd64-amd64-libvirt-
1 - 100 of 147 matches
Mail list logo
