flight 93425 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93425/
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
flight 93415 qemu-upstream-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93415/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-xl-rtds 11 guest-startfail in 93389 pass in 93415
On 5/3/16 9:50 AM, Jan Beulich wrote:
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
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
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Tuesday, May 3, 2016 9:59 PM
> Cc: Andrew Cooper ; Wei Liu
> ; George Dunlap ; Ian
> Jackson ; Wu, Feng
On 5/3/16 10:18 AM, Jan Beulich wrote:
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
On May 04, 2016 10:02 AM, Tian, Kevin wrote:
> > From: Xu, Quan
> > Sent: Friday, April 29, 2016 5:25 PM
> > diff --git a/xen/drivers/passthrough/vtd/iommu.c
> > b/xen/drivers/passthrough/vtd/iommu.c
> > index cf847ec..bfee299 100644
> > ---
On May 04, 2016 10:00 AM, Tian, Kevin wrote:
> > From: Xu, Quan
> > Sent: Friday, April 29, 2016 5:25 PM
> > diff --git a/xen/arch/x86/acpi/power.c b/xen/arch/x86/acpi/power.c
> > index 2885e31..9097333 100644
> > --- a/xen/arch/x86/acpi/power.c
> > +++
> From: Xu, Quan
> Sent: Friday, April 29, 2016 5:25 PM
> diff --git a/xen/drivers/passthrough/vtd/iommu.c
> b/xen/drivers/passthrough/vtd/iommu.c
> index cf847ec..bfee299 100644
> --- a/xen/drivers/passthrough/vtd/iommu.c
> +++ b/xen/drivers/passthrough/vtd/iommu.c
> @@ -1301,7 +1301,7 @@ int
> From: Xu, Quan
> Sent: Friday, April 29, 2016 5:25 PM
> diff --git a/xen/arch/x86/acpi/power.c b/xen/arch/x86/acpi/power.c
> index 2885e31..9097333 100644
> --- a/xen/arch/x86/acpi/power.c
> +++ b/xen/arch/x86/acpi/power.c
> @@ -45,6 +45,8 @@ void do_suspend_lowlevel(void);
>
> static int
> From: Xu, Quan
> Sent: Friday, April 29, 2016 5:25 PM
>
> Propagate the IOMMU Device-TLB flush error up to the ept_set_entry(),
> when VT-d shares EPT page table.
>
> Signed-off-by: Quan Xu
>
Acked-by: Kevin Tian
> From: Xu, Quan
> Sent: Friday, April 29, 2016 5:25 PM
>
> Propagate the IOMMU Device-TLB flush error up to the iommu_iotlb_flush{,_all}.
>
> This patch fixes the leaf ones.
>
> Signed-off-by: Quan Xu
>
> CC: Stefano Stabellini
> CC: Julien Grall
flight 93408 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93408/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 9 debian-hvm-install fail pass in
93381
Regressions which are
> From: Xu, Quan
> Sent: Friday, April 29, 2016 5:25 PM
>
> When IOMMU mapping is failed, we issue a best effort rollback, stopping
> IOMMU mapping, unmapping the previous IOMMU maps and then reporting the
> error up to the call trees. When rollback is not feasible (in early
> initialization
> From: Quan Xu
> Sent: Friday, April 29, 2016 5:25 PM
>
> Treat IOMMU mapping and unmapping failures as a fatal to the domain
> (with the exception of the hardware domain).
>
> If IOMMU mapping and unmapping failed, crash the domain (with the
> exception of the hardware domain) and propagate
On Tue, May 03, 2016 at 11:46:27PM +0200, Dario Faggioli wrote:
> Hi,
>
> This small series contains some bugfixes for various schedulers. They're all
> bugfixes, so I think all should be considered for 4.7. Here's some more
> detailed analysis.
>
> Patch 1 and 3 are for Credit2. Patch 1 is a
> From: Xu, Quan
> Sent: Friday, April 29, 2016 5:25 PM
>
> The propagation value from IOMMU flush interfaces may be positive, which
> indicates callers need to flush cache, not one of faliures.
>
> when the propagation value is positive, this patch fixes this flush issue
> as follows:
> -
> From: Tamas K Lengyel [mailto:ta...@tklengyel.com]
> Sent: Saturday, April 30, 2016 2:08 AM
>
> Mechanical renaming to better describe that the code in hvm/event is part of
> the monitor subsystem.
>
> Signed-off-by: Tamas K Lengyel
Acked-by: Kevin Tian
> From: Razvan Cojocaru [mailto:rcojoc...@bitdefender.com]
> Sent: Friday, April 29, 2016 2:04 PM
>
> Previously, subscribing to MSR write events was an all-or-none
> approach, with special cases for introspection MSR-s. This patch
> allows the vm_event consumer to specify exactly what MSR-s it
This run is configured for baseline tests only.
flight 44382 xen-unstable real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/44382/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-qcow2 9
flight 93414 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93414/
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
On Tue, 2016-05-03 at 14:23 +0100, Wei Liu wrote:
> 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
Hi,
This small series contains some bugfixes for various schedulers. They're all
bugfixes, so I think all should be considered for 4.7. Here's some more
detailed analysis.
Patch 1 and 3 are for Credit2. Patch 1 is a lot more important, as we have an
ASSERT triggering without it. Patch 2 is
The scheduling hooks API is now used properly, and no
initialization or de-initialization happen in
alloc/free_pdata any longer.
In fact, just like it is for Credit2, there is no real
need for implementing alloc_pdata and free_pdata.
This also made it possible to improve the replenishment
timer
In fact, interrupts are already disabled when calling
the hook from schedule_cpu_switch(), and hence using
anything different than just spin_lock() is wrong (and
ASSERT()-s in debug builds) or unnecessary.
Signed-off-by: Dario Faggioli
---
Cc: George Dunlap
All calculations that involve load_last_update uses quantities
shifted by LOADAVG_GRANULARITY_SHIFT, so make sure that this
is true even when the field is assigned a value for the first
time, during vcpu allocation.
Also, during migration, while the loads of both the source and
destination
commit 64269d9365 "sched: implement .init_pdata in Credit,
Credit2 and RTDS" helped fixing Credit2 runqueues, and
the races we had in switching scheduler for pCPUs, but
introduced another issue. In fact, if CPU bringup fails
during __cpu_up() (and, more precisely, after CPU_UP_PREPARE,
but before
flight 93412 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93412/
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 3, 2016 at 12:55 PM, Konrad Rzeszutek Wilk
wrote:
> On Tue, May 3, 2016 at 12:47 PM, Konrad Rzeszutek Wilk
> wrote:
>>
>> The host has 240 CPUs and the HVM guests config looks as follow:
>>
>> -bash-4.1# cat /hvm.cfg
>> memory=64000
You can
On Tue, May 3, 2016 at 5:31 AM, Julien Grall wrote:
> 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
On Tue, May 3, 2016 at 2:18 AM, Razvan Cojocaru
wrote:
> 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
>
On Tue, May 03, 2016 at 10:10:24AM -0700, Luis R. Rodriguez wrote:
> On Tue, May 3, 2016 at 10:07 AM, Luis R. Rodriguez wrote:
> > Thanks! Can you confirm if any Android or Brillo builds are already using
> > it?
>
> Also more importantly, any chance you can provide any
flight 93389 qemu-upstream-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93389/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-xsm 3 host-install(3) broken in 93371
flight 93395 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/93395/
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
On Tue, May 3, 2016 at 10:10 AM, Luis R. Rodriguez wrote:
> On Tue, May 3, 2016 at 10:07 AM, Luis R. Rodriguez wrote:
>> Thanks! Can you confirm if any Android or Brillo builds are already using it?
>
> Also more importantly, any chance you can provide any
On Tue, May 3, 2016 at 10:10 AM, Luis R. Rodriguez wrote:
> or it was decided
Sorry I meant to say: 'or _why_ it was decided to not use initramfs on
these systems?'
Luis
___
Xen-devel mailing list
Xen-devel@lists.xen.org
On Tue, May 3, 2016 at 10:07 AM, Luis R. Rodriguez wrote:
> Thanks! Can you confirm if any Android or Brillo builds are already using it?
Also more importantly, any chance you can provide any technical
reasons why initramfs cannot be used, or it was decided to not use it
on
On Mon, May 2, 2016 at 11:41 AM, Greg KH wrote:
> On Mon, May 02, 2016 at 11:34:33AM -0700, Kees Cook wrote:
>> On Mon, Feb 29, 2016 at 10:56 AM, Luis R. Rodriguez wrote:
>> > On Mon, Feb 29, 2016 at 10:12:50AM +, David Woodhouse wrote:
>> >> On
On Mon, May 2, 2016 at 11:34 AM, Kees Cook wrote:
> On Mon, Feb 29, 2016 at 10:56 AM, Luis R. Rodriguez wrote:
>> On Mon, Feb 29, 2016 at 10:12:50AM +, David Woodhouse wrote:
>>> On Fri, 2016-02-19 at 05:45 -0800, Luis R. Rodriguez wrote:
>>> > This
On Tue, 2016-05-03 at 11:34 +0100, Wei Liu wrote:
> 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
On Tue, May 3, 2016 at 12:47 PM, Konrad Rzeszutek Wilk
wrote:
>
> The host has 240 CPUs and the HVM guests config looks as follow:
>
> -bash-4.1# cat /hvm.cfg
> memory=64000
> name="big64"
> vcpus = 64
> disk= ['file:/isos/root_image.iso,hdc:cdrom,r']
> builder="hvm"
If I
On Tue, May 03, 2016 at 12:49:07PM -0400, Konrad Rzeszutek Wilk wrote:
> On Tue, May 03, 2016 at 05:35:45PM +0100, Wei Liu wrote:
> > The original patch seems to malformed.
> >
> > I skim the code, the refactoring parts look correct to me. What I'm not
> > sure is whether the replacement is
On Fri, Apr 29, 2016 at 3:49 PM, Jan Beulich wrote:
> Signed-off-by: Jan Beulich
Acked-by: George Dunlap
>
> --- a/xen/arch/x86/mm/p2m.c
> +++ b/xen/arch/x86/mm/p2m.c
> @@ -618,9 +618,11 @@ void p2m_teardown(struct p2m_domain
On Tue, May 03, 2016 at 05:35:45PM +0100, Wei Liu wrote:
> The original patch seems to malformed.
>
> I skim the code, the refactoring parts look correct to me. What I'm not
> sure is whether the replacement is correct or not.
>
> The reference to gnutls_priority_set_direct in [0] is from a
The host has 240 CPUs and the HVM guests config looks as follow:
-bash-4.1# cat /hvm.cfg
memory=64000
name="big64"
vcpus = 64
disk= ['file:/isos/root_image.iso,hdc:cdrom,r']
builder="hvm"
serial='pty'
usb=1
vnclisten="0.0.0.0:64"
-bash-4.1# xl list | grep big64
big64
On Tue, May 3, 2016 at 5:44 PM, George Dunlap
wrote:
> On Fri, Apr 29, 2016 at 3:49 PM, Jan Beulich wrote:
>> Signed-off-by: Jan Beulich
>
> Acked-by: George Dunlap
And I guess this is a candidate for
The original patch seems to malformed.
I skim the code, the refactoring parts look correct to me. What I'm not
sure is whether the replacement is correct or not.
The reference to gnutls_priority_set_direct in [0] is from a section
called "Upgrading to 3.4.x from 3.3.x", while the version check
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
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
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 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’:
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
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
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 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
>>> 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
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 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.
>
>
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
>>> 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
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: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
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
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 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 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
>>> 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
>>> 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:
>>> 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
>>> 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
> +
>>> 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
> +
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
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:
> 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.
>
>
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:
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
>>> 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
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
>>> 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
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
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
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
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
---
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
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
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
>>> 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
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
>>> 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
>>> 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
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
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
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
>>> 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
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
>>> 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.
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
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 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.
>
>
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.
> > >
> > >
1 - 100 of 146 matches
Mail list logo