* h...@zytor.com wrote:
> On March 1, 2017 2:27:54 AM PST, Ingo Molnar wrote:
> >
> >* Thomas Gleixner wrote:
> >
> >> On Wed, 1 Mar 2017, Ingo Molnar wrote:
> >> >
> >> > * Jiri Slaby wrote:
> >> >
> >> > > This is a start of series to unify use of ENTRY, ENDPROC, GLOBAL,
> >END,
> >> > >
> Hello.
>
> On 03/06/2017 05:20 PM, Elena Reshetova wrote:
>
> > refcount_t type and corresponding API should be
> > used instead of atomic_t when the variable is used as
> > a reference counter. This allows to avoid accidental
> > refcounter overflows that might lead to use-after-free
> > situa
> On 03/06/2017 03:21 PM, Elena Reshetova wrote:
> > refcount_t type and corresponding API should be
> > used instead of atomic_t when the variable is used as
> > a reference counter. This allows to avoid accidental
> > refcounter overflows that might lead to use-after-free
> > situations.
>
> The
Add $DISTRO = "CentOS"
to the rpm installation targets
complementing Fedora
Signed-off-by: Géza Gémes
---
lib/common-functions.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/common-functions.sh b/lib/common-functions.sh
index 19434c2..d4476f3 100644
--- a/lib/comm
Extend the existing Fedora case with CentOS in the install_package function
Géza Gémes (1):
Allow installation on CentOS
lib/common-functions.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.7.4
___
Xen-devel mailing list
Xen-dev
2017-03-02 02:16 keltezéssel, Stefano Stabellini írta:
On Wed, 1 Mar 2017, Gémes Géza wrote:
2017-03-01 20:48 keltezéssel, Stefano Stabellini írta:
On Wed, 1 Mar 2017, Gémes Géza wrote:
2017-02-27 23:52 keltezéssel, Stefano Stabellini írta:
On Wed, 22 Feb 2017, Géza Gémes wrote:
On 2017-02-2
Signed-off-by: Géza Gémes
---
lib/commands.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/commands.sh b/lib/commands.sh
index be445a7..5b653b3 100755
--- a/lib/commands.sh
+++ b/lib/commands.sh
@@ -70,7 +70,7 @@ function unraise() {
function install() {
# need
There is a small typo in the install function causing it ignoring rpms
Géza Gémes (1):
Fix typo in function install
lib/commands.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.7.4
___
Xen-devel mailing list
Xen-devel@lists.xen.org
There is a small typo in the install function causing it ignoring rpms
Géza Gémes (1):
Fix typo in function install
lib/commands.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.7.4
___
Xen-devel mailing list
Xen-devel@lists.xen.org
Signed-off-by: Géza Gémes
---
lib/commands.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/commands.sh b/lib/commands.sh
index be445a7..5b653b3 100755
--- a/lib/commands.sh
+++ b/lib/commands.sh
@@ -70,7 +70,7 @@ function unraise() {
function install() {
# need
flight 106504 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106504/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-xtf-amd64-amd64-5 34 xtf/test-hvm32pae-swint-emulation fail REGR. vs.
106482
test-xtf-amd64
flight 106506 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106506/
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. 105963
test-amd64-amd64-xl-qemuu-
On Mon, Mar 06, 2017 at 04:27:11PM +0100, Johannes Thumshirn wrote:
> On 03/06/2017 03:21 PM, Elena Reshetova wrote:
> > refcount_t type and corresponding API should be
> > used instead of atomic_t when the variable is used as
> > a reference counter. This allows to avoid accidental
> > refcounter
This run is configured for baseline tests only.
flight 68640 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/68640/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-midway 11 guest-start
On 03/06/2017 10:31 PM, Konrad Rzeszutek Wilk wrote:
On Mon, Mar 06, 2017 at 10:59:18AM +0800, Zhang Chen wrote:
Because of some reason, We no longer support COLO kernel proxy.
However the #7 talks about kernel colo proxy? Is this description
out-dated?
In patch 7/8, the comments:
We use k
flight 106499 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106499/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-intel 11 guest-start fail REGR. vs. 59254
test-armhf-armhf-xl
Write the limits of the backend to xenstore. Connect to the frontend.
Upon connection, allocate the rings according to the protocol
specification.
Initialize a QEMUBH to schedule work upon receiving an event channel
notification from the frontend.
Signed-off-by: Stefano Stabellini
CC: anthony.pe
Once a request is completed, xen_9pfs_push_and_notify gets called. In
xen_9pfs_push_and_notify, update the indexes (data has already been
copied to the sg by the common code) and send a notification to the
frontend.
Schedule the bottom-half to check if we already have any other requests
pending.
Implement xen_9pfs_init_in/out_iov_from_pdu and
xen_9pfs_pdu_vmarshal/vunmarshall by creating new sg pointing to the
data on the ring.
This is safe as we only handle one request per ring at any given time.
Signed-off-by: Stefano Stabellini
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
CC: An
Introduce the Xen 9pfs backend: add struct XenDevOps to register as a
Xen backend and add struct V9fsTransport to register as v9fs transport.
All functions are empty stubs for now.
Signed-off-by: Stefano Stabellini
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
CC: Aneesh Kumar K.V
CC: Greg
Hi all,
This patch series implements a new transport for 9pfs, aimed at Xen
systems.
The transport is based on a traditional Xen frontend and backend drivers
pair. This patch series implements the backend, which typically runs in
Dom0. I sent another series to implement the frontend in Linux
(htt
Signed-off-by: Stefano Stabellini
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
CC: Aneesh Kumar K.V
CC: Greg Kurz
---
hw/9pfs/Makefile.objs| 1 +
hw/xen/xen_backend.c | 1 +
include/hw/xen/xen_backend.h | 1 +
3 files changed, 3 insertions(+)
diff --git a/hw/9pfs/Makefile.
Upon receiving an event channel notification from the frontend, schedule
the bottom half. From the bottom half, read one request from the ring,
create a pdu and call pdu_submit to handle it.
For now, only handle one request per ring at a time.
Signed-off-by: Stefano Stabellini
CC: anthony.per...
Do not use the ring.h header installed on the system. Instead, import
the header into the QEMU codebase. This avoids problems when QEMU is
built against a Xen version too old to provide all the ring macros.
Signed-off-by: Stefano Stabellini
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
---
NB
It uses the new ring.h macros to declare rings and interfaces.
Signed-off-by: Stefano Stabellini
CC: anthony.per...@citrix.com
CC: jgr...@suse.com
---
hw/9pfs/xen_9pfs.h | 20
1 file changed, 20 insertions(+)
create mode 100644 hw/9pfs/xen_9pfs.h
diff --git a/hw/9pfs/xen_9
flight 106507 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106507/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xtf 83af19a3154af85815e4c8ffd170839b99685adc
baseline version:
xtf 1d68cab2189bd035002ecc
On Wed, Feb 22, 2017 at 09:04:17AM -0800, Doug Goldstein wrote:
[...]
> I'm currently at ELC and then on vacation so I don't have access to any
> of the machines currently myself. However the machine I most use to test
> is a NUC5i5MYHE and a NUC5i3MYHE if you want to ask around if someone
> has
flight 106505 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106505/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a
build-arm64 5 xen
. For hibernation, the main processor returns with the
original GDT and switches back to the remapping at completion.
This patch was tested on both architectures. Hibernation and KVM were
both tested specially for their usage of the GDT.
Signed-off-by: Thomas Garnier
---
Based on next-20170306
address does not provide enough space for the kernel
to support a large number of processors.
Signed-off-by: Thomas Garnier
---
Based on next-20170306
---
Documentation/x86/x86_64/mm.txt | 5 -
arch/x86/include/asm/pgtable_64_types.h | 3 ++-
arch/x86/kernel/module.c| 1
original GDT.
Instead of reloading the previous GDT, VMX will reload the fixmap GDT as
expected. For testing, VMs were started and restored on multiple
configurations.
Signed-off-by: Thomas Garnier
---
Based on next-20170306
---
arch/x86/include/asm/desc.h | 106
On 03/06/2017 04:36 PM, Stefano Stabellini wrote:
> On Mon, 6 Mar 2017, Boris Ostrovsky wrote:
>>> + uint32_t size;
>>> + uint8_t id;
>>> + uint16_t tag;
>> I realize that this is in the spec now and it's probably too late to ask
>> this question but wouldn't it be better if id and tag were s
On Mon, 6 Mar 2017, Boris Ostrovsky wrote:
> > + uint32_t size;
> > + uint8_t id;
> > + uint16_t tag;
>
> I realize that this is in the spec now and it's probably too late to ask
> this question but wouldn't it be better if id and tag were swapped? No
> need to pack and potentially faster ac
flight 106491 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106491/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stopfail like 106474
test-amd64-i386-xl-qemuu-w
> +struct xen_9pfs_header {
> + uint32_t size;
> + uint8_t id;
> + uint16_t tag;
I realize that this is in the spec now and it's probably too late to ask
this question but wouldn't it be better if id and tag were swapped? No
need to pack and potentially faster access to tag.
-boris
flight 106503 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106503/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-xtf-amd64-amd64-23 host-install(3)broken REGR. vs. 106496
versio
> +static int xen_p4d_walk(struct mm_struct *mm, p4d_t *p4d,
> + int (*func)(struct mm_struct *mm, struct page *, enum pt_level),
> + bool last, unsigned long limit)
> +{
> + int i, nr, flush = 0;
> +
> + nr = last ? p4d_index(limit) + 1 : PTRS_PER_P4D;
> + for
flight 106487 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106487/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-pvh-intel 11 guest-start fail like 106486
test-armhf-armhf-xl-rtds
On Mon, Mar 06, 2017 at 03:05:49PM -0500, Boris Ostrovsky wrote:
>
> > diff --git a/arch/x86/include/asm/pgtable_64.h
> > b/arch/x86/include/asm/pgtable_64.h
> > index 9991224f6238..c9e41f1599dd 100644
> > --- a/arch/x86/include/asm/pgtable_64.h
> > +++ b/arch/x86/include/asm/pgtable_64.h
> > @@
flight 106489 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106489/
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. 105963
test-amd64-amd64-xl-qemuu-
> diff --git a/arch/x86/include/asm/pgtable_64.h
> b/arch/x86/include/asm/pgtable_64.h
> index 9991224f6238..c9e41f1599dd 100644
> --- a/arch/x86/include/asm/pgtable_64.h
> +++ b/arch/x86/include/asm/pgtable_64.h
> @@ -14,15 +14,17 @@
> #include
> #include
>
> +extern p4d_t level4_kernel_pg
It uses the new ring.h macros to declare rings and interfaces.
Signed-off-by: Stefano Stabellini
CC: konrad.w...@oracle.com
CC: boris.ostrov...@oracle.com
CC: jgr...@suse.com
---
include/xen/interface/io/9pfs.h | 40
1 file changed, 40 insertions(+)
crea
Sync the ring.h file with upstream Xen, to introduce the new ring macros.
They will be used by the Xen transport for 9pfs.
Signed-off-by: Stefano Stabellini
CC: konrad.w...@oracle.com
CC: boris.ostrov...@oracle.com
CC: jgr...@suse.com
---
NB: The new macros have not been committed to Xen yet. Do
Implement functions to handle the xenbus handshake. Upon connection,
allocate the rings according to the protocol specification.
Initialize a work_struct and a wait_queue. The work_struct will be used
to schedule work upon receiving an event channel notification from the
backend. The wait_queue wi
This patch adds a Kconfig option and Makefile support for building the
9pfs Xen driver.
Signed-off-by: Stefano Stabellini
CC: boris.ostrov...@oracle.com
CC: jgr...@suse.com
CC: Eric Van Hensbergen
CC: Ron Minnich
CC: Latchesar Ionkov
CC: v9fs-develo...@lists.sourceforge.net
---
net/9p/Kconfig
Upon receiving a notification from the backend, schedule the
p9_xen_response work_struct. p9_xen_response checks if any responses are
available, if so, it reads them one by one, calling p9_client_cb to send
them up to the 9p layer (p9_client_cb completes the request). Handle the
ring following the
Implement struct p9_trans_module create and close functions by looking
at the available Xen 9pfs frontend-backend connections. We don't expect
many frontend-backend connections, thus walking a list is OK.
Send requests to the backend by copying each request to one of the
available rings (each fron
Introduce the Xen 9pfs transport driver: add struct xenbus_driver to
register as a xenbus driver and add struct p9_trans_module to register
as v9fs driver.
All functions are empty stubs for now.
Signed-off-by: Stefano Stabellini
CC: boris.ostrov...@oracle.com
CC: jgr...@suse.com
CC: Eric Van Hen
Hi all,
This patch series implements a new transport for 9pfs, aimed at Xen
systems.
The transport is based on a traditional Xen frontend and backend drivers
pair. This patch series implements the frontend, which typically runs in
a regular unprivileged guest.
I'll follow up with another series
flight 106497 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106497/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 1 build-check(1) blocked n/a
build-arm64 5 xen
On Mon, 6 Mar 2017, Paul Durrant wrote:
> > -Original Message-
> > From: Qemu-devel [mailto:qemu-devel-
> > bounces+paul.durrant=citrix@nongnu.org] On Behalf Of Paul Durrant
> > Sent: 06 March 2017 09:15
> > To: 'Stefano Stabellini'
> > Cc: Anthony Perard ; xen-
> > de...@lists.xenproj
On 06/03/17 18:33, Andrew Cooper wrote:
> On 06/03/17 18:28, George Dunlap wrote:
>> On 27/02/17 14:03, Andrew Cooper wrote:
>>> The existing pagetable walker has complicated return semantics, which
>>> squeeze
>>> multiple pieces of information into single integer. This would be fine if
>>> the
On 06/03/17 18:28, George Dunlap wrote:
> On 27/02/17 14:03, Andrew Cooper wrote:
>> The existing pagetable walker has complicated return semantics, which squeeze
>> multiple pieces of information into single integer. This would be fine if
>> the
>> information didn't overlap, but it does.
>>
>>
On 27/02/17 14:03, Andrew Cooper wrote:
> The existing pagetable walker has complicated return semantics, which squeeze
> multiple pieces of information into single integer. This would be fine if the
> information didn't overlap, but it does.
>
> Specifically, _PAGE_INVALID_BITS for 3-level guest
flight 106496 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106496/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-xtf-amd64-amd64-5 34 xtf/test-hvm32pae-swint-emulation fail in 106493
pass in 106496
test-xtf-amd64-amd64-5 38 xtf
On 27/02/17 14:03, Andrew Cooper wrote:
> hap_p2m_ga_to_gfn() and sh_page_fault() currently use guest_l1e_get_gfn() to
> obtain the translation of a pagewalk. This is conceptually wrong (the
> semantics of gw.l1e is an internal detail), and will actually be wrong when
> PSE36 superpage support is
flight 106486 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106486/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-intel 11 guest-start fail REGR. vs. 59254
test-armhf-armhf-xl
On 03/06/2017 11:42 AM, Roger Pau Monne wrote:
> There where a couple of unneeded packed attributes in several x86-specific
> structures, that are obviously aligned. The only non-trivial one is
> vmcb_struct, which has been checked to have the same layout with and without
> the packed attribute usi
On Mon, Mar 06, 2017 at 09:57:23AM -0700, Jan Beulich wrote:
> >>> On 06.03.17 at 17:42, wrote:
> > There where a couple of unneeded packed attributes in several x86-specific
> > structures, that are obviously aligned. The only non-trivial one is
> > vmcb_struct, which has been checked to have the
On 03/06/2017 09:21 AM, Elena Reshetova wrote:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> situations.
>
> Signed-off-by: E
>>> On 06.03.17 at 17:42, wrote:
> There where a couple of unneeded packed attributes in several x86-specific
> structures, that are obviously aligned. The only non-trivial one is
> vmcb_struct, which has been checked to have the same layout with and without
> the packed attribute using pahole. In
On Mon, Mar 06, 2017 at 09:43:43AM -0700, Jan Beulich wrote:
> >>> On 23.02.17 at 12:52, wrote:
> > And then remove hvm_vioapic (since it just contains a hvm_hw_ioapic struct
> > now). This is a preparatory change for introducing support for multiple vIO
> > APICs per domain.
>
> Having gone thro
>>> On 23.02.17 at 12:52, wrote:
> And then remove hvm_vioapic (since it just contains a hvm_hw_ioapic struct
> now). This is a preparatory change for introducing support for multiple vIO
> APICs per domain.
Having gone through the rest of this series, I think the replacing of
vioapic pointers by
There where a couple of unneeded packed attributes in several x86-specific
structures, that are obviously aligned. The only non-trivial one is
vmcb_struct, which has been checked to have the same layout with and without
the packed attribute using pahole. In that case add a build-time size check to
Signed-off-by: Andrew Cooper
---
tests/pagetable-emulation/Makefile | 11 +
tests/pagetable-emulation/main.c | 1119
tests/pagetable-emulation/stubs.S | 94 +++
tests/pagetable-emulation/stubs.h | 25 +
4 files changed, 1249 insertions(+)
create mod
flight 106493 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106493/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-xtf-amd64-amd64-5 34 xtf/test-hvm32pae-swint-emulation fail REGR. vs.
106490
test-xtf-amd64-amd64-5
Hello.
On 03/06/2017 05:20 PM, Elena Reshetova wrote:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Ele
On Mon, Mar 6, 2017 at 2:28 AM, Razvan Cojocaru
wrote:
> Currently, p2m_mem_access_emulate_check() uses p2m_get_mem_access()
> to check if the page restrictions have been lifted between the time
> of sending the vm_event out and the reception of the reply - in
> which case emulation is no longer r
>>> On 23.02.17 at 12:52, wrote:
> int vioapic_init(struct domain *d)
> {
> +unsigned int i, nr_vioapics = is_hardware_domain(d) ? nr_ioapics : 1;
Considering this ...
> @@ -646,24 +656,41 @@ int vioapic_init(struct domain *d)
>
> if ( (d->arch.hvm_domain.vioapic == NULL) &&
>
Hello,
I'm Saurav Sachidanand, and I'm a CS sophomore studying in India. For
more than year I've been programming in Rust and have published some
personal projects in it (few involving the Rust-C FFI) and have
contributed a some code to Servo (github.com/saurvs). I've also
played around a bit with
On 06/03/17 15:16, Tim Deegan wrote:
> At 14:36 + on 06 Mar (1488811016), George Dunlap wrote:
>> On 06/03/17 13:58, Jan Beulich wrote:
>> On 06.03.17 at 13:31, wrote:
--- a/Config.mk
+++ b/Config.mk
@@ -216,6 +216,7 @@ $(call
cc-option-add,HOSTCFLAGS,HOSTCC,-Wdeclarat
On 03/06/2017 03:21 PM, Elena Reshetova wrote:
> refcount_t type and corresponding API should be
> used instead of atomic_t when the variable is used as
> a reference counter. This allows to avoid accidental
> refcounter overflows that might lead to use-after-free
> situations.
The subject is wron
On Mon, Mar 06, 2017 at 05:52:14AM -0700, Jan Beulich wrote:
> >>> On 06.03.17 at 13:31, wrote:
> > There seems to be some weird bug in clang 4.0 that prevents xsm_pmu_op from
> > working as expected, and vpmu.o ends up with a reference to
> > __xsm_action_mismatch_detected which makes the build f
At 14:36 + on 06 Mar (1488811016), George Dunlap wrote:
> On 06/03/17 13:58, Jan Beulich wrote:
> On 06.03.17 at 13:31, wrote:
> >> --- a/Config.mk
> >> +++ b/Config.mk
> >> @@ -216,6 +216,7 @@ $(call
> >> cc-option-add,HOSTCFLAGS,HOSTCC,-Wdeclaration-after-statement)
> >> $(call cc-opt
On 03/06/2017 09:54 AM, Jan Beulich wrote:
On 06.03.17 at 15:42, wrote:
>> On 03/06/2017 07:52 AM, Jan Beulich wrote:
>> On 06.03.17 at 13:31, wrote:
There seems to be some weird bug in clang 4.0 that prevents xsm_pmu_op from
working as expected, and vpmu.o ends up with a refer
>>> On 06.03.17 at 15:51, wrote:
> On Wed, Mar 01, 2017 at 04:21:35AM -0700, Jan Beulich wrote:
>> >>> On 01.03.17 at 11:51, wrote:
>> > On Wed, Mar 01, 2017 at 03:34:47AM -0700, Jan Beulich wrote:
>> >> >>> On 01.03.17 at 11:13, wrote:
>> >> > On Wed, Mar 01, 2017 at 02:05:39AM -0700, Jan Beuli
On Fri 03-03-17 18:34:22, Igor Mammedov wrote:
> On Fri, 3 Mar 2017 09:27:23 +0100
> Michal Hocko wrote:
>
> > On Thu 02-03-17 18:03:15, Igor Mammedov wrote:
> > > On Thu, 2 Mar 2017 15:28:16 +0100
> > > Michal Hocko wrote:
> > >
> > > > On Thu 02-03-17 14:53:48, Igor Mammedov wrote:
> > > >
>>> On 06.03.17 at 15:42, wrote:
> On 03/06/2017 07:52 AM, Jan Beulich wrote:
> On 06.03.17 at 13:31, wrote:
>>> There seems to be some weird bug in clang 4.0 that prevents xsm_pmu_op from
>>> working as expected, and vpmu.o ends up with a reference to
>>> __xsm_action_mismatch_detected which
On Wed, Mar 01, 2017 at 04:21:35AM -0700, Jan Beulich wrote:
> >>> On 01.03.17 at 11:51, wrote:
> > On Wed, Mar 01, 2017 at 03:34:47AM -0700, Jan Beulich wrote:
> >> >>> On 01.03.17 at 11:13, wrote:
> >> > On Wed, Mar 01, 2017 at 02:05:39AM -0700, Jan Beulich wrote:
> >> >> >>> On 21.02.17 at 20:
On 06/03/17 13:21, Julien Grall wrote:
> Hi Jan,
>
> On 06/03/17 12:41, Jan Beulich wrote:
> On 06.03.17 at 12:42, wrote:
>>> I thought a bit more about those params. I think the name should be
>>> generic and not tie to pl011 because we may want to emulate different
>>> UART for the guest in
flight 106490 xtf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/106490/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xtf 4d06734fbb48879be65bab9fefda51dcb253541c
baseline version:
xtf f02259db8c737220b4e6ae
On 03/06/2017 07:52 AM, Jan Beulich wrote:
On 06.03.17 at 13:31, wrote:
>> There seems to be some weird bug in clang 4.0 that prevents xsm_pmu_op from
>> working as expected, and vpmu.o ends up with a reference to
>> __xsm_action_mismatch_detected which makes the build fail:
>>
>> [...]
>> ld
On 06/03/17 13:58, Jan Beulich wrote:
On 06.03.17 at 13:31, wrote:
>> --- a/Config.mk
>> +++ b/Config.mk
>> @@ -216,6 +216,7 @@ $(call
>> cc-option-add,HOSTCFLAGS,HOSTCC,-Wdeclaration-after-statement)
>> $(call cc-option-add,CFLAGS,CC,-Wdeclaration-after-statement)
>> $(call cc-option-add,
On Mon, Mar 06, 2017 at 10:59:18AM +0800, Zhang Chen wrote:
> Because of some reason, We no longer support COLO kernel proxy.
However the #7 talks about kernel colo proxy? Is this description
out-dated?
> V4:
One usually adds these comments to the patches. That is
right after the '---' you say:
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
On 03/03/2017, 07:20 PM, h...@zytor.com wrote:
> On March 1, 2017 2:27:54 AM PST, Ingo Molnar wrote:
>>
>> * Thomas Gleixner wrote:
>>
>>> On Wed, 1 Mar 2017, Ingo Molnar wrote:
* Jiri Slaby wrote:
> This is a start of series to unify use of ENTRY, ENDPROC, GLOBAL,
>> END,
>>>
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
refcount_t type and corresponding API should be
used instead of atomic_t when the variable is used as
a reference counter. This allows to avoid accidental
refcounter overflows that might lead to use-after-free
situations.
Signed-off-by: Elena Reshetova
Signed-off-by: Hans Liljestrand
Signed-off-
1 - 100 of 165 matches
Mail list logo
