flight 88669 linux-3.16 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88669/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-pair 21 guest-migrate/src_host/dst_host fail REGR. vs.
85048
Tests which are
Thanks, Tim.
On 4/4/2016 4:25 PM, Tim Deegan wrote:
At 18:53 +0800 on 31 Mar (1459450418), Yu Zhang wrote:
A new HVMOP - HVMOP_map_mem_type_to_ioreq_server, is added to
let one ioreq server claim/disclaim its responsibility for the
handling of guest pages with p2m type p2m_ioreq_server. Users
o
On Mon, Apr 04, 2016 at 09:51:56AM -0600, Jan Beulich wrote:
> >>> On 31.03.16 at 10:57, wrote:
> > xsaves will not be used until supervised state is introduced in hypervisor.
> > And XSTATE_XSAVES_ONLY (indicates supervised state is understood in xen)
> > is instroduced, the use of xsaves depend
On 04/05/2016 01:34 AM, Wei Liu wrote:
Wei Liu (5):
libxc: colo: don't leak pfns and iov in send_checkpoint_dirty_pfn_list
libxl: colo: simplify colo_proxy_async_wait_for_checkpoint
libxl: colo: add missing break in qemu_disk_scsi_drive_string
libxl: colo: fix indentation of abort()
Add generic virtualization support for pinning the current vcpu to a
specified physical cpu. As this operation isn't performance critical
(a very limited set of operations like BIOS calls and SMIs is expected
to need this) just add a hypervisor specific indirection.
Signed-off-by: Juergen Gross
-
Some hardware models (e.g. Dell Studio 1555 laptops) require calls to
the firmware to be issued on cpu 0 only. As Dom0 might have to use
these calls, add xen_pin_vcpu() to achieve this functionality.
In case either the domain doesn't have the privilege to make the
related hypercall or the hypervis
Use the smp_call_on_cpu() function to call system management
mode on cpu 0.
Make call secure by adding get_online_cpus() to avoid e.g. suspend
resume cycles in between.
Signed-off-by: Juergen Gross
---
V4: add call to get_online_cpus()
---
drivers/hwmon/dell-smm-hwmon.c | 35
Some hardware (e.g. Dell Studio laptops) require special functions to
be called on physical cpu 0 in order to avoid occasional hangs. When
running as dom0 under Xen this could be achieved only via special boot
parameters (vcpu pinning) limiting the hypervisor in it's scheduling
decisions.
This pat
On some hardware models (e.g. Dell Studio 1555 laptop) some hardware
related functions (e.g. SMIs) are to be executed on physical cpu 0
only. Instead of open coding such a functionality multiple times in
the kernel add a service function for this purpose. This will enable
the possibility to take sp
Use smp_call_on_cpu() to raise SMI on cpu 0.
Make call secure by adding get_online_cpus() to avoid e.g. suspend
resume cycles in between.
Signed-off-by: Juergen Gross
---
V4: add call to get_online_cpus()
---
drivers/firmware/dcdbas.c | 51 ---
1 file
Import the actual version of include/xen/interface/sched.h from Xen.
Signed-off-by: Juergen Gross
---
include/xen/interface/sched.h | 100 ++
1 file changed, 82 insertions(+), 18 deletions(-)
diff --git a/include/xen/interface/sched.h b/include/xen/interf
flight 88667 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88667/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-i386 10 guest-start fail REGR. vs. 86454
test-amd64-i386-fre
On 04/04/16 18:48, Boris Ostrovsky wrote:
> On 04/04/2016 12:30 PM, David Vrabel wrote:
>> On 04/04/16 17:21, Julien Grall wrote:
>>> (CC Stefano new e-mail address)
>>>
>>> Hello Anna-Maria,
>>>
>>> On 04/04/2016 13:32, Anna-Maria Gleixner wrote:
Xen guests do not offline/online CPUs during s
On Wed, Feb 17, 2016 at 12:46 PM, Andy Lutomirski wrote:
> On Fri, Feb 5, 2016 at 5:17 PM, Fengguang Wu wrote:
>> On Fri, Feb 05, 2016 at 12:10:56PM -0800, Andy Lutomirski wrote:
>>> On Feb 4, 2016 7:11 PM, "Fengguang Wu" wrote:
>>> >
>>> > Hi Andy,
>>> >
>>> > CC more people on Xen testing -- i
Add earlycon=xenboot option to Documentation/kernel-parameters.txt.
Signed-off-by: Chris Patterson
---
Documentation/kernel-parameters.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/kernel-parameters.txt
b/Documentation/kernel-parameters.txt
index ecc74fa..e01ec39 10064
flight 88655 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88655/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-rumpuserxen6 xen-build fail REGR. vs. 59254
test-amd64-amd64-xl-c
On Mon, Apr 04, 2016 at 03:44:44PM -0400, Konrad Rzeszutek Wilk wrote:
> On Fri, Apr 01, 2016 at 03:18:45AM -0600, Jan Beulich wrote:
> > >>> On 31.03.16 at 23:26, wrote:
> > >> Also - how well will this O(n^2) lookup work once there are enough
> > >> payloads? I think this calls for the alternat
On Mon, Apr 4, 2016 at 9:07 PM, Chong Li wrote:
> Commit f7b87b0745b4 ("enable per-VCPU parameter for RTDS") introduced
> a bug: it made it possible, in Credit and Credit2, when doing domain
> or vcpu parameters' manipulation, to leave the hypervisor with a
> spinlock held and interrupts disabled.
> -Original Message-
> From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of Konrad
> Rzeszutek Wilk
> Sent: Friday, April 1, 2016 11:55 PM
> To: Hao, Xudong
> Cc: samuel.thiba...@ens-lyon.org; xen-devel@lists.xen.org; Wei Liu
> ; stefano.stabell...@eu.citrix.com
> Subject:
Commit f7b87b0745b4 ("enable per-VCPU parameter for RTDS") introduced
a bug: it made it possible, in Credit and Credit2, when doing domain
or vcpu parameters' manipulation, to leave the hypervisor with a
spinlock held and interrupts disabled.
Fix it.
Signed-off-by: Chong Li
Acked-by: Dario Fagg
On 04/04/2016 23:45, Chong Li wrote:
> From: Chong-Li
>
> Commit f7b87b0745b4 ("enable per-VCPU parameter for RTDS") introduced
> a bug: it made it possible, in Credit and Credit2, when doing domain
> or vcpu parameters' manipulation, to leave the hypervisor with a
> spinlock held.
And interrup
On 04/04/2016 19:48, Benjamin Sanda wrote:
> Moved get_pg_owner() and put_pg_owner() from the arch specific x86
> mm.c source files into the common page_alloc.c source. This was done
> as theses functions are now needed by both architectures to support
> xentrace on the ARM platform. Forward declar
From: Chong-Li
Commit f7b87b0745b4 ("enable per-VCPU parameter for RTDS") introduced
a bug: it made it possible, in Credit and Credit2, when doing domain
or vcpu parameters' manipulation, to leave the hypervisor with a
spinlock held.
Fix it.
Signed-off-by: Chong Li
Signed-off-by: Meng Xu
Si
On Mon, 2016-04-04 at 16:21 -0500, Chong Li wrote:
> From: Chong-Li
>
> Fix a bug in sched_credit.c and sched_credit2.c: in the default case
> of csched_dom_cntl and csched2_dom_cntl, function returns without
> unlocking prv->lock.
>
This should mention what commit introduced the bug. Of course,
On Mon, Apr 04, 2016 at 02:31:46PM -0700, Andy Lutomirski wrote:
> Could you do it by moving just the earlyprintk stuff a la
> fpu__init_parse_early_param()?
Yeah, something like that. I'll play with this more tomorrow. Btw, no
need to make any of this part of your patchset - I'd like early change
flight 88639 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88639/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 3 host-install(3) broken in 87395 REGR. vs. 66399
build-amd64-rumpuserxen
On Mon, Apr 4, 2016 at 12:38 PM, Borislav Petkov wrote:
> On Mon, Apr 04, 2016 at 06:00:42PM +0200, Peter Zijlstra wrote:
>> On Mon, Apr 04, 2016 at 08:32:21AM -0700, Andy Lutomirski wrote:
>>
>> > Adding locking would be easy enough, wouldn't it?
>>
>> See patch in this thread..
>>
>> > But do an
From: Chong-Li
Fix a bug in sched_credit.c and sched_credit2.c: in the default case
of csched_dom_cntl and csched2_dom_cntl, function returns without
unlocking prv->lock.
Signed-off-by: Chong Li
Signed-off-by: Meng Xu
Signed-off-by: Sisu Xi
---
CC:
CC:
CC:
CC:
CC:
CC:
---
xen/common/s
flight 88641 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88641/
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
ioreq server list needs to be initialized for PVH guests. This list is
walked in handle_hvm_io_completion() by all guests in HVM containers and
leaving it uninitialized may cause PVH guests to crash there.
Signed-off-by: Boris Ostrovsky
---
xen/arch/x86/hvm/hvm.c | 4 ++--
xen/arch/x86/hvm/ior
flight 88699 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88699/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
build-amd64-libvirt 5 libvirt-buildfail like 88680
Tests which did not suc
On Mon, Apr 04, 2016 at 09:00:00AM -0600, Jan Beulich wrote:
> >>> On 24.03.16 at 21:00, wrote:
> > @@ -929,6 +932,33 @@ being loaded and requires an hypervisor build-id to
> > match against.
> > The old code allows much more flexibility and an additional guard,
> > but is more complex to imple
On Mon, Apr 04, 2016 at 09:06:47AM -0600, Jan Beulich wrote:
> >>> On 24.03.16 at 21:00, wrote:
> > --- a/xen/common/xsplice.c
> > +++ b/xen/common/xsplice.c
> > @@ -566,6 +566,27 @@ static int prepare_payload(struct payload *payload,
> > if ( !payload->id.len || !payload->id.p )
> >
On Fri, Apr 01, 2016 at 03:18:45AM -0600, Jan Beulich wrote:
> >>> On 31.03.16 at 23:26, wrote:
> >> Also - how well will this O(n^2) lookup work once there are enough
> >> payloads? I think this calls for the alternative vmap() extension I've
> >> been suggesting earlier.
> >
> > Could you elab
On Mon, Apr 04, 2016 at 06:00:42PM +0200, Peter Zijlstra wrote:
> On Mon, Apr 04, 2016 at 08:32:21AM -0700, Andy Lutomirski wrote:
>
> > Adding locking would be easy enough, wouldn't it?
>
> See patch in this thread..
>
> > But do any platforms really boot a second CPU before switching to real
>
flight 88588 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88588/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-pair 21 guest-migrate/src_host/dst_host fail REGR. vs.
86491
test-amd64-am
Modified to provide building of the xenalyze binary for both ARM and
x86 platforms. The xenalyze binary is now built as part of the BIN
list for both platforms.
Signed-off-by: Benjamin Sanda
Acked-by: Wei Liu
---
Changed since v2:
* No changes.
---
Changed since v1:
* Changed xenalyze targ
Moved get_cycles() to time.c and modified to return the core timestamp
tick count for use by the trace buffer timestamping routines in
xentrace. get_cycles() was moved to the C file to avoid including the
register specific header file in time.h and to commonize it with the
get_s_time() function. Al
Added call to init_trace_bufs() to initialize the trace buffers for
use by xentrace.
Signed-off-by: Benjamin Sanda
---
Changed since v2:
* No changes
---
Changed since v1:
* No changes
---
xen/arch/arm/setup.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/xen/arch/arm/setup.c b/xe
Moved get_pg_owner() and put_pg_owner() from the arch specific x86
mm.c source files into the common page_alloc.c source. This was done
as theses functions are now needed by both architectures to support
xentrace on the ARM platform. Forward declarations were added to mm.h.
One conditional compila
This patch set adds support for xentrace/xenalyze to the ARM platform.
The Xen heap memory mapping, timestamping, and P2M translation needed
by xentrace is corrected for operation on the ARM platform using the
x86 platform as reference. Trace buffer initialization is added to
setup.c, XENMAPSPACE_
Modified ARM arch specific p2m.c and mm.c files to provide support for
xentrace. Case for DOMID_XEN added xenmem_add_to_physmap_one() when
XENMAPSPACE_gmfn_foreign domain requested via get_pg_owner. This
provides correct calls to rcu_lock_domain() when DOMID_XEN is
requested.
Check for DOMID_XEN a
On 04/04/16 11:24, Luis R. Rodriguez wrote:
> On Mon, Apr 04, 2016 at 09:01:06AM -0700, H. Peter Anvin wrote:
>> On 03/31/16 13:03, Luis R. Rodriguez wrote:
>>> Andy S, Peter, Thomas, Jiang (or who might know),
>>>
>>> Do Intel MID platforms exist with PNP BIOS support? What abot CE4100?
>>> As it
On Sat, Apr 02, 2016 at 10:22:44PM +0200, Takashi Iwai wrote:
> On Sat, 02 Apr 2016 20:05:21 +0200,
> Andy Lutomirski wrote:
> >
> > On Apr 2, 2016 12:07 PM, "Takashi Iwai" wrote:
> > >
> > > On Sat, 02 Apr 2016 14:57:44 +0200,
> > > Andy Lutomirski wrote:
> > > >
> > > > On Fri, Apr 1, 2016 at 1
On Mon, Apr 04, 2016 at 09:01:06AM -0700, H. Peter Anvin wrote:
> On 03/31/16 13:03, Luis R. Rodriguez wrote:
> > Andy S, Peter, Thomas, Jiang (or who might know),
> >
> > Do Intel MID platforms exist with PNP BIOS support? What abot CE4100?
> > As it stands I don't see anything that would prevent
flight 88680 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88680/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144
Tests which di
Signed-off-by: Wei Liu
---
tools/libxl/libxl_dm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c
index 67f308d..51be98a 100644
--- a/tools/libxl/libxl_dm.c
+++ b/tools/libxl/libxl_dm.c
@@ -818,7 +818,7 @@ static char *qemu_disk_
Signed-off-by: Wei Liu
---
tools/libxl/libxl_dm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/libxl/libxl_dm.c b/tools/libxl/libxl_dm.c
index 5b79aa2..67f308d 100644
--- a/tools/libxl/libxl_dm.c
+++ b/tools/libxl/libxl_dm.c
@@ -816,6 +816,7 @@ static char *qemu_disk_scsi_drive_strin
Signed-off-by: Wei Liu
---
tools/libxc/xc_sr_restore.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/libxc/xc_sr_restore.c b/tools/libxc/xc_sr_restore.c
index 728edbc..3549f0a 100644
--- a/tools/libxc/xc_sr_restore.c
+++ b/tools/libxc/xc_sr_restore.c
@@ -494,6 +494,8 @@ static int s
Signed-off-by: Wei Liu
---
tools/libxl/libxl_colo_nic.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/tools/libxl/libxl_colo_nic.c b/tools/libxl/libxl_colo_nic.c
index 2e00c28..5e0968c 100644
--- a/tools/libxl/libxl_colo_nic.c
+++ b/tools/libxl/libxl_colo_nic.c
@@ -219,11 +219,6 @@ stat
Signed-off-by: Wei Liu
---
tools/libxl/libxl_colo_save.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/tools/libxl/libxl_colo_save.c b/tools/libxl/libxl_colo_save.c
index e2fdc4b..26b3afd 100644
--- a/tools/libxl/libxl_colo_save.c
+++ b/tools/libxl/libxl_colo_save.c
Wei Liu (5):
libxc: colo: don't leak pfns and iov in send_checkpoint_dirty_pfn_list
libxl: colo: simplify colo_proxy_async_wait_for_checkpoint
libxl: colo: add missing break in qemu_disk_scsi_drive_string
libxl: colo: fix indentation of abort()
libxl: colo: remove dead code in colo_save_s
On Mon, Apr 4, 2016 at 11:47 AM, Wei Liu wrote:
> On Mon, Apr 04, 2016 at 06:32:48PM +0200, Dario Faggioli wrote:
>> On Mon, 2016-04-04 at 17:05 +0100, George Dunlap wrote:
>> > On 04/04/16 16:58, Chong Li wrote:
>> > > On Mon, Apr 4, 2016 at 10:14 AM, Andrew Cooper
>> > > wrote:
>> > > > On 01/0
On 04/04/16 18:11, Andrew Cooper wrote:
> On 04/04/16 17:59, Ian Jackson wrote:
>> George Dunlap writes ("Re: [PATCH v3 5/9] libxl: Rearrange qemu upstream
>> disk argument code"):
>>> I looked through the patch in the branch provided in your reply to 0/9
>>> [1], and it looks correct; morever, I
Konrad Rzeszutek Wilk writes ("Re: [Xen-devel] XSM permissive by default."):
> I presume this patch would be to folks +1:
>
> From 3373a50f386b41eea6ecede4b430e4fa09b2fe7e Mon Sep 17 00:00:00 2001
> From: Konrad Rzeszutek Wilk
> Date: Thu, 10 Mar 2016 12:05:29 -0500
> Subject: [PATCH] flask: By d
On 04/04/16 17:59, Ian Jackson wrote:
> George Dunlap writes ("Re: [PATCH v3 5/9] libxl: Rearrange qemu upstream disk
> argument code"):
>> I looked through the patch in the branch provided in your reply to 0/9
>> [1], and it looks correct; morever, I tested it and it and the basic
>> functionalit
George Dunlap writes ("Re: [PATCH v3 5/9] libxl: Rearrange qemu upstream disk
argument code"):
> I looked through the patch in the branch provided in your reply to 0/9
> [1], and it looks correct; morever, I tested it and it and the basic
> functionality (using the "dummy" block script) still work
Olaf Hering writes ("Re: [Xen-devel] [PATCH v13 03/26] tools/libxl: Add back
channel to allow migration target send data back"):
> On Mon, Apr 04, Wei Liu wrote:
> > The fix is to patch libvirt. Looking at libvirt code I think I need to
> > patch Makefile.in to pass in an explicit LIBXL_API_VERSIO
Ian Jackson writes ("Policy for force pushing smoke branch Was: Re: [Xen-devel]
[xen-unstable-smoke test] 88656: regressions - FAIL"):
> Wei Liu writes ("Policy for force pushing smoke branch Was: Re: [Xen-devel]
> [xen-unstable-smoke test] 88656: regressions - FAIL"):
> > It would take some time
On 04/04/2016 12:30 PM, David Vrabel wrote:
On 04/04/16 17:21, Julien Grall wrote:
(CC Stefano new e-mail address)
Hello Anna-Maria,
On 04/04/2016 13:32, Anna-Maria Gleixner wrote:
Xen guests do not offline/online CPUs during suspend/resume and
therefore FROZEN notifier transitions are not re
On Mon, Apr 04, 2016 at 06:32:48PM +0200, Dario Faggioli wrote:
> On Mon, 2016-04-04 at 17:05 +0100, George Dunlap wrote:
> > On 04/04/16 16:58, Chong Li wrote:
> > > On Mon, Apr 4, 2016 at 10:14 AM, Andrew Cooper
> > > wrote:
> > > > On 01/04/16 05:59, Chong Li wrote:
> > > > >
> > > > > --- a/x
On Mon, Apr 4, 2016 at 9:33 AM, David Vrabel wrote:
> On 02/04/16 15:01, Andy Lutomirski wrote:
>> This adds paravirt hooks for unsafe MSR access. On native, they
>> call native_{read,write}_msr. On Xen, they use
>> xen_{read,write}_msr_safe.
>>
>> Nothing uses them yet for ease of bisection. T
On Mon, 2016-04-04 at 17:05 +0100, George Dunlap wrote:
> On 04/04/16 16:58, Chong Li wrote:
> > On Mon, Apr 4, 2016 at 10:14 AM, Andrew Cooper
> > wrote:
> > > On 01/04/16 05:59, Chong Li wrote:
> > > >
> > > > --- a/xen/common/sched_credit2.c
> > > > +++ b/xen/common/sched_credit2.c
> > > > @@
On 02/04/16 15:01, Andy Lutomirski wrote:
> This adds paravirt hooks for unsafe MSR access. On native, they
> call native_{read,write}_msr. On Xen, they use
> xen_{read,write}_msr_safe.
>
> Nothing uses them yet for ease of bisection. The next patch will
> use them in rdmsrl, wrmsrl, etc.
>
>
On 04/04/16 17:21, Julien Grall wrote:
> (CC Stefano new e-mail address)
>
> Hello Anna-Maria,
>
> On 04/04/2016 13:32, Anna-Maria Gleixner wrote:
>> Xen guests do not offline/online CPUs during suspend/resume and
>> therefore FROZEN notifier transitions are not required. Add this
>> explanation
flight 88622 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88622/
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. 60684
build-amd6
On Mon, Apr 04, 2016 at 03:57:02PM +0100, Ian Jackson wrote:
> Coverity is complaining (eg, CID 1358114) about this code in
> _libxl_types.c:
>
> *** CID 1358114: Code maintainability issues (UNUSED_VALUE)
> /tools/libxl/_libxl_types.c: 11035 in libxl__device_usbdev_parse_json()
> 11029 x
On Sat, Apr 02, 2016 at 07:01:31AM -0700, Andy Lutomirski wrote:
> There are two parts here:
>
> * FIRST PART: EARLY EXCEPTIONS *
>
> The first few patches move some early panic code into C, add pt_regs
> to early exception handling, and make fancy exception handlers work early.
>
>
(CC Stefano new e-mail address)
Hello Anna-Maria,
On 04/04/2016 13:32, Anna-Maria Gleixner wrote:
Xen guests do not offline/online CPUs during suspend/resume and
therefore FROZEN notifier transitions are not required. Add this
explanation as a comment in the code to get not confused why
CPU_TAS
On Mon, Apr 04, 2016 at 08:46:22AM -0700, Andy Lutomirski wrote:
> Borislav asked for a comment explaining why all exception handlers are
> allowed early.
>
> Signed-off-by: Andy Lutomirski
> ---
> arch/x86/mm/extable.c | 14 ++
> 1 file changed, 14 insertions(+)
>
> diff --git a/ar
On 04/04/16 16:58, Chong Li wrote:
> On Mon, Apr 4, 2016 at 10:14 AM, Andrew Cooper
> wrote:
>> On 01/04/16 05:59, Chong Li wrote:
>>> diff --git a/xen/common/sched_credit.c b/xen/common/sched_credit.c
>>> index 305889a..e5d15d8 100644
>>> --- a/xen/common/sched_credit.c
>>> +++ b/xen/common/sched
On 04/04/16 16:50, Ben Sanda wrote:
> Julien and Wei,
>
>>> You patches all have the same subject line. Please make them more
>>> specific. See my reply to #1 for example.
>> +1
>>
>> Also, you should at least check that Xen still builds after applying
>> each patch. Ideally, you also need to be
On 03/31/16 13:03, Luis R. Rodriguez wrote:
> Andy S, Peter, Thomas, Jiang (or who might know),
>
> Do Intel MID platforms exist with PNP BIOS support? What abot CE4100?
> As it stands I don't see anything that would prevent this but I would
> suspect a possibility might be that it doesn't. I'm sa
On 04/01/2016 03:54 AM, Paul Durrant wrote:
The code in hvm/hvm.c related to handling I/O emulation using the ioreq
server framework is large and mostly self-contained.
This patch separates the ioreq server code into a new hvm/ioreq.c source
module and accompanying asm-x86/hvm/ioreq.h header fil
On Mon, Apr 04, 2016 at 08:32:21AM -0700, Andy Lutomirski wrote:
> Adding locking would be easy enough, wouldn't it?
See patch in this thread..
> But do any platforms really boot a second CPU before switching to real
> printk?
I _only_ use early_printk() as printk() is a quagmire of fail :-)
>>> On 31.03.16 at 10:57, wrote:
Considering this isn't the last patch in the series, the subject isn't
really nice (apart from being mis-spelled). If you e.g. replaced
"remained" by "miscellaneous", I wouldn't insist on splitting.
> 1. get_xsave_addr() will only be called when
> xsave_area_comp
On Mon, Apr 04, 2016 at 03:50:35PM +, Ben Sanda wrote:
> Julien and Wei,
>
> >> You patches all have the same subject line. Please make them more
> >> specific. See my reply to #1 for example.
> >
> > +1
> >
> > Also, you should at least check that Xen still builds after applying
> > each p
On Mon, Apr 4, 2016 at 10:14 AM, Andrew Cooper
wrote:
> On 01/04/16 05:59, Chong Li wrote:
>> diff --git a/xen/common/sched_credit.c b/xen/common/sched_credit.c
>> index 305889a..e5d15d8 100644
>> --- a/xen/common/sched_credit.c
>> +++ b/xen/common/sched_credit.c
>> @@ -1080,15 +1080,13 @@ csched_
flight 88672 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/88672/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 5 libvirt-build fail REGR. vs. 88144
Tests which di
Julien and Wei,
>> You patches all have the same subject line. Please make them more
>> specific. See my reply to #1 for example.
>
> +1
>
> Also, you should at least check that Xen still builds after applying
> each patch. Ideally, you also need to be careful to not break any
> feature current
>>> On 31.03.16 at 10:57, wrote:
> xsaves will not be used until supervised state is introduced in hypervisor.
> And XSTATE_XSAVES_ONLY (indicates supervised state is understood in xen)
> is instroduced, the use of xsaves depend on whether XSTATE_XSAVES_ONLY
There's still a spelling mistake here,
On Sun, Apr 3, 2016 at 7:10 AM, Borislav Petkov wrote:
> On Sun, Apr 03, 2016 at 06:55:00AM -0700, Andy Lutomirski wrote:
>> > No, please don't fail at early boot.
>> >
>> > Early boot is just about the *worst* situation to try to debug odd
>> > failures, exactly since things like printk may not b
Borislav asked for a comment explaining why all exception handlers are
allowed early.
Signed-off-by: Andy Lutomirski
---
arch/x86/mm/extable.c | 14 ++
1 file changed, 14 insertions(+)
diff --git a/arch/x86/mm/extable.c b/arch/x86/mm/extable.c
index 98b5f45d9d79..36fe03bc81ee 100644
Hi Julien,
On 01.04.2016 18:34, Julien Grall wrote:
On 31/03/16 18:41, Dirk Behme wrote:
Hello Julien,
Hello Dirk,
On 29.03.2016 20:53, Julien Grall wrote:
On 23/03/16 17:24, Dirk Behme wrote:
trying to bring up Xen on a new ARMv8 64-bit Cortex A57 eval board, I
get [1] and then its han
On 4/4/2016 8:32 AM, Andy Lutomirski wrote:
Adding locking would be easy enough, wouldn't it?
But do any platforms really boot a second CPU before switching to real
printk? Given that I see all the smpboot stuff in dmesg, I guess real
printk happens first. I admit I haven't actually checked.
On Apr 4, 2016 4:51 AM, "Jan Kara" wrote:
>
> On Sat 02-04-16 13:58:19, Andy Lutomirski wrote:
> > [cc Jan Kara]
> >
> > On Sat, Apr 2, 2016 at 1:47 PM, Borislav Petkov wrote:
> > > On Sat, Apr 02, 2016 at 01:13:37PM -0700, Andy Lutomirski wrote:
> > >> Given that I this isn't really a regression
On Mon, Apr 04, Wei Liu wrote:
> The fix is to patch libvirt. Looking at libvirt code I think I need to
> patch Makefile.in to pass in an explicit LIBXL_API_VERSION number.
That might be true.
But shouldnt at the same time libxl.h get a change to recognize
0x040700? Perhaps this will be part of
>>> On 24.03.16 at 21:00, wrote:
> Shadow variables are a piece of infrastructure to be used by xsplice
> modules. They are used to attach a new piece of data to an existing
> structure in memory.
An already known question again: Out of recent XSAs, how many
needed such? I.e. can#t we put this of
We must set rc before using `goto out'.
Bug introduced in bf7628f0 "libxl: add pvusb API".
CID: 1358113
Signed-off-by: Ian Jackson
CC: cover...@xenproject.org
CC: Simon Cao
CC: George Dunlap
CC: Chunyan Liu
---
tools/libxl/libxl_pvusb.c |1 +
1 file changed, 1 insertion(+)
diff --git a/
Bug introduced in bc023ecd
"libxl_utils: add internal function to read sysfs file contents"
CID: 1358108
Signed-off-by: Ian Jackson
CC: cover...@xenproject.org
CC: Chunyan Liu
---
tools/libxl/libxl_utils.c |1 +
1 file changed, 1 insertion(+)
diff --git a/tools/libxl/libxl_utils.c b/tools/
On 01/04/16 05:59, Chong Li wrote:
> diff --git a/xen/common/sched_credit.c b/xen/common/sched_credit.c
> index 305889a..e5d15d8 100644
> --- a/xen/common/sched_credit.c
> +++ b/xen/common/sched_credit.c
> @@ -1080,15 +1080,13 @@ csched_dom_cntl(
> * lock. Runq lock not needed anywhere in her
On 01/04/16 15:31, Ian Jackson wrote:
> George Dunlap writes ("[PATCH v3 5/9] libxl: Rearrange qemu upstream disk
> argument code"):
>> Reorganize the qemuu disk argument code to make a clean separation
>> between finding a file to use, and constructing the parameters:
>
> This didn't apply to st
scan-ad...@coverity.com writes ("New Defects reported by Coverity Scan for
XenProject"):
> Please find the latest report on new defect(s) introduced to XenProject found
> with Coverity Scan.
>
> 35 new defect(s) introduced to XenProject found with Coverity Scan.
> 2 defect(s), reported by Coverit
In libxl_usb.c, usbintf_get_drvpath calls stat(2) on the driver sysfs
path, and then realpath on the same path.
And bind_usbintf calls stat(2) on the driver directory path, and then
open(2) on a file in that directory.
It seems to be that in both cases, libxl could simply directly access
the targ
>>> On 24.03.16 at 21:00, wrote:
> --- a/xen/common/xsplice.c
> +++ b/xen/common/xsplice.c
> @@ -566,6 +566,27 @@ static int prepare_payload(struct payload *payload,
> if ( !payload->id.len || !payload->id.p )
> return -EINVAL;
> }
> +/* Make sure it is not a duplica
>>> On 24.03.16 at 21:00, wrote:
> --- a/xen/common/xsplice.c
> +++ b/xen/common/xsplice.c
> @@ -1514,6 +1514,11 @@ static void xsplice_printall(unsigned char key)
> if ( !(i % 100) )
> process_pending_softirqs();
> }
> +if ( data->id.len )
> +
Hello,
On 04/04/2016 15:11, Wei Liu wrote:
On Fri, Apr 01, 2016 at 04:33:44PM -0400, Benjamin Sanda wrote:
---
Changed since v1:
* Removed Flask changes as deemed uncessesary and unclear in
purpose
* Corrected all commit messages to be line limited to 72 chars
* Implimented v1 rev
Coverity complains, rightly, as follows:
> *** CID 1358110: Incorrect expression (SIZEOF_MISMATCH)
> /tools/libxl/libxl_pvusb.c: 1068 in bind_usbintf()
> 1062 if (fd < 0) {
> 1063 LOGE(ERROR, "open file failed: '%s'", path);
> 1064 rc = ERROR_FAIL;
> 1065
>>> On 24.03.16 at 21:00, wrote:
> @@ -929,6 +932,33 @@ being loaded and requires an hypervisor build-id to
> match against.
> The old code allows much more flexibility and an additional guard,
> but is more complex to implement.
>
> +The second option which requires an build-id of the hyperv
Coverity is complaining (eg, CID 1358114) about this code in
_libxl_types.c:
*** CID 1358114: Code maintainability issues (UNUSED_VALUE)
/tools/libxl/_libxl_types.c: 11035 in libxl__device_usbdev_parse_json()
11029 x = libxl__json_map_get("hostaddr", x, JSON_INTEGER);
11030 if (x) {
1 - 100 of 150 matches
Mail list logo
