On 14/01/16 17:08, Wei Liu wrote:
> On Thu, Jan 14, 2016 at 09:06:27AM -0700, Jan Beulich wrote:
> On 14.01.16 at 17:01, wrote:
>>> --- a/.gitignore
>>> +++ b/.gitignore
>>> @@ -48,6 +48,7 @@ docs/pdf/
>>> docs/txt/
>>> extras/mini-os*
>>> install/*
>>> +stubdom/libs-*
>>> stubdom/autom4te
On Thu, 2016-01-14 at 08:58 -0600, Doug Goldstein wrote:
> Currently OSSTest has 'XSM' tests but XSM and FLASK are two different
> options and OSSTests's 'XSM' test depends on FLASK so ensure that FLASK
> is enabled so that tests pass.
IMHO the xen/Kconfig should be arranged such that if XSM is en
Jan Beulich writes:
On 14.01.16 at 15:49, wrote:
>> --- a/xen/common/Kconfig
>> +++ b/xen/common/Kconfig
>> @@ -51,4 +51,63 @@ config KEXEC
>>
>>If unsure, say Y.
>>
>> +# Enable schedulers
>> +menu "Schedulers"
>> +visible if EXPERT = "y"
>> +
>> +config SCHED_CREDIT
>> +bo
Jan Beulich writes:
On 14.01.16 at 15:49, wrote:
>> --- a/xen/common/schedule.c
>> +++ b/xen/common/schedule.c
>> @@ -64,20 +64,9 @@ static void poll_timer_fn(void *data);
>> DEFINE_PER_CPU(struct schedule_data, schedule_data);
>> DEFINE_PER_CPU(struct scheduler *, scheduler);
>>
>> -stat
On Thu, Jan 14, 2016 at 05:18:15PM +0100, Juergen Gross wrote:
> On 14/01/16 17:08, Wei Liu wrote:
> > On Thu, Jan 14, 2016 at 09:06:27AM -0700, Jan Beulich wrote:
> > On 14.01.16 at 17:01, wrote:
> >>> --- a/.gitignore
> >>> +++ b/.gitignore
> >>> @@ -48,6 +48,7 @@ docs/pdf/
> >>> docs/txt/
I have to confess I'm quite confused now. Maybe there are many
underlying disagreements here but mostly I seem befogged. However,
here are some principles I currently believe in for how this should
all work:
* It should be possible to enable, or disable, all of the following
things by pullin
On Thu, 2016-01-14 at 10:23 -0600, Jonathan Creekmore wrote:
> Jan Beulich writes:
>
> > > > > On 14.01.16 at 15:49, wrote:
> > > --- a/xen/common/Kconfig
> > > +++ b/xen/common/Kconfig
> > > @@ -51,4 +51,63 @@ config KEXEC
> > >
> > > If unsure, say Y.
> > >
> > > +# Enable schedulers
> >
On 1/14/16 10:22 AM, Ian Campbell wrote:
> On Thu, 2016-01-14 at 08:58 -0600, Doug Goldstein wrote:
>> Currently OSSTest has 'XSM' tests but XSM and FLASK are two different
>> options and OSSTests's 'XSM' test depends on FLASK so ensure that FLASK
>> is enabled so that tests pass.
>
> IMHO the xen
On Do, 2016-01-14 at 14:50 +, Ian Campbell wrote:
> Hello,
>
> The xen.git development branch currently points to SeaBIOS rel-1.9.0, but
> Roger has tripped over a build issue which is fixed by 3b8c5378dfe2 "build:
> fix typo in buildversion.py".
>
> Is there any plan for either a 1.9.1 or a
On Thu, 14 Jan 2016, Markus Armbruster wrote:
> xen_hvm_init() returns -1 without cleaning up on some errors (harmless
> long as the caller exit()s on error), dies with hw_error() on others.
> hw_error() isn't approprate here. Clean up to exit() on all errors.
>
> Signed-off-by: Markus Armbruster
On Thu, 2016-01-14 at 17:36 +0100, Gerd Hoffmann wrote:
> On Do, 2016-01-14 at 14:50 +, Ian Campbell wrote:
> > Hello,
> >
> > The xen.git development branch currently points to SeaBIOS rel-1.9.0,
> > but
> > Roger has tripped over a build issue which is fixed by 3b8c5378dfe2
> > "build:
> > f
On Thu, 2016-01-14 at 14:44 +, Ian Campbell wrote:
> On Thu, 2016-01-14 at 06:00 -0700, Jan Beulich wrote:
> > > > > On 14.01.16 at 12:32, wrote:
> > > --- a/Config.mk
> > > +++ b/Config.mk
> > > @@ -255,9 +255,10 @@ MINIOS_UPSTREAM_REVISION ?=
> > > d25773c8afa2f4dbbb466116daeb60159ddd22bd
>
>>> On 14.01.16 at 17:34, wrote:
> On Thu, 2016-01-14 at 10:23 -0600, Jonathan Creekmore wrote:
>> Jan Beulich writes:
>>
>> > > > > On 14.01.16 at 15:49, wrote:
>> > > --- a/xen/common/Kconfig
>> > > +++ b/xen/common/Kconfig
>> > > @@ -51,4 +51,63 @@ config KEXEC
>> > >
>> > >If un
>>> On 14.01.16 at 17:25, wrote:
> I can do a follow-up patch for the whole file after that one goes in.
> Jan, let me know what you think.
Some further cleanup would be nice, but is not a requirement
for you to do imo.
Jan
___
Xen-devel mailing list
On Thu, 14 Jan 2016, Markus Armbruster wrote:
> xen_ram_alloc() dies with hw_error() on error, even though its caller
> ram_block_add() handles errors just fine. Add an Error **errp
> parameter and use it.
>
> Leave case RUN_STATE_INMIGRATE alone, because that looks like some
> kind of warning.
>
El 14/01/16 a les 17.44, Ian Campbell ha escrit:
> On Thu, 2016-01-14 at 14:44 +, Ian Campbell wrote:
>> On Thu, 2016-01-14 at 06:00 -0700, Jan Beulich wrote:
>> On 14.01.16 at 12:32, wrote:
--- a/Config.mk
+++ b/Config.mk
@@ -255,9 +255,10 @@ MINIOS_UPSTREAM_REVISION ?=
>>>
El 14/01/16 a les 17.44, Ian Campbell ha escrit:
> On Thu, 2016-01-14 at 14:44 +, Ian Campbell wrote:
>> On Thu, 2016-01-14 at 06:00 -0700, Jan Beulich wrote:
>> On 14.01.16 at 12:32, wrote:
--- a/Config.mk
+++ b/Config.mk
@@ -255,9 +255,10 @@ MINIOS_UPSTREAM_REVISION ?=
>>>
>>> On 14.01.16 at 17:44, wrote:
> On Thu, 2016-01-14 at 14:44 +, Ian Campbell wrote:
>> On Thu, 2016-01-14 at 06:00 -0700, Jan Beulich wrote:
>> > > > > On 14.01.16 at 12:32, wrote:
>> > > --- a/Config.mk
>> > > +++ b/Config.mk
>> > > @@ -255,9 +255,10 @@ MINIOS_UPSTREAM_REVISION ?=
>> > > d
On Thu, 2016-01-14 at 09:44 -0700, Jan Beulich wrote:
> > > > On 14.01.16 at 17:34, wrote:
> > On Thu, 2016-01-14 at 10:23 -0600, Jonathan Creekmore wrote:
> > > Jan Beulich writes:
> > >
> > > > > > > On 14.01.16 at 15:49, wrote:
> > > > > --- a/xen/common/Kconfig
> > > > > +++ b/xen/common/Kco
>>> On 25.12.15 at 03:53, wrote:
>> From: Xu, Quan
>> Sent: Wednesday, December 23, 2015 4:26 PM
>> --- 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 device_power_down(void)
>> {
>> +int rc;
>> +
>>
On Thu, 2016-01-14 at 17:56 +0100, Roger Pau Monné wrote:
> El 14/01/16 a les 17.44, Ian Campbell ha escrit:
> > On Thu, 2016-01-14 at 14:44 +, Ian Campbell wrote:
> > > On Thu, 2016-01-14 at 06:00 -0700, Jan Beulich wrote:
> > > > > > > On 14.01.16 at 12:32, wrote:
> > > > > --- a/Config.mk
>
On 1/14/16 10:27 AM, Ian Jackson wrote:
> I have to confess I'm quite confused now. Maybe there are many
> underlying disagreements here but mostly I seem befogged. However,
> here are some principles I currently believe in for how this should
> all work:
>
> * It should be possible to enable,
On 01/14/16 17:36, Gerd Hoffmann wrote:
> On Do, 2016-01-14 at 14:50 +, Ian Campbell wrote:
>> Hello,
>>
>> The xen.git development branch currently points to SeaBIOS rel-1.9.0, but
>> Roger has tripped over a build issue which is fixed by 3b8c5378dfe2 "build:
>> fix typo in buildversion.py".
>
>>> On 23.12.15 at 09:25, wrote:
> @@ -182,7 +186,7 @@ static int enter_state(u32 state)
> error = tboot_s3_resume();
> break;
> case ACPI_STATE_S5:
> -acpi_enter_sleep_state(ACPI_STATE_S5);
> +error = acpi_enter_sleep_state(ACPI_STATE_S5);
I can't see how t
Doug Goldstein writes ("Re: [Xen-devel] [xen-unstable test] 77945: regressions
- FAIL [and 2 more messages]"):
> On 1/14/16 10:27 AM, Ian Jackson wrote:
> > Is any of this of any use ?
> >
> > Thanks,
> > Ian.
> > (no less confused after writing this than I was before)
>
> The take away I see he
What is the outcome of this discussion?
Lars
On 06/01/2016 16:30, "Ian Jackson" wrote:
>Lars Kurth writes ("Re: [PATCH] MAINTAINERS: add myself for kconfig"):
>> As we have seen last year in the survey, in theory - aka according to
>>our
>> governance - committers should always act on the wishes
Hello,
I present the Xen Test Framework, a project for small, quick, component
tests of VM functionality.
Without repeating the history verbatim, this is the result of a project
started out of necessary while investigating XSA-106, which I considered
useful enough to pursue properly.
Documentati
IMNSHO we should apply the patch.
On Thu, 2016-01-14 at 17:19 +, Lars Kurth wrote:
> What is the outcome of this discussion?
> Lars
>
> On 06/01/2016 16:30, "Ian Jackson" wrote:
>
> > Lars Kurth writes ("Re: [PATCH] MAINTAINERS: add myself for kconfig"):
> > > As we have seen last year in t
On Thu, 2016-01-14 at 17:18 +, Ian Jackson wrote:
> Doug Goldstein writes ("Re: [Xen-devel] [xen-unstable test] 77945:
> regressions - FAIL [and 2 more messages]"):
> > On 1/14/16 10:27 AM, Ian Jackson wrote:
> > > Is any of this of any use ?
> > >
> > > Thanks,
> > > Ian.
> > > (no less confu
Jan Beulich writes:
On 14.01.16 at 17:34, wrote:
>> On Thu, 2016-01-14 at 10:23 -0600, Jonathan Creekmore wrote:
>>> Jan Beulich writes:
>>>
>>> > > > > On 14.01.16 at 15:49, wrote:
>>> > > --- a/xen/common/Kconfig
>>> > > +++ b/xen/common/Kconfig
>>> > > @@ -51,4 +51,63 @@ config KEXEC
>>
On Thu, 14 Jan 2016, Ian Campbell wrote:
> On Tue, 2016-01-12 at 16:52 +, Stefano Stabellini wrote:
> > PCI passthrough cannot work if QEMU is run as a non-root process today,
> > as QEMU needs to open /dev/mem to mmap the MSI-X table of the device and
> > read/write relevant nodes on sysfs.
>
Stefano Stabellini writes ("Re: [PATCH] QEMU as non-root and PCI passthrough do
not mix"):
> On Thu, 14 Jan 2016, Ian Campbell wrote:
> > What if b_info->device_model_user is NULL or == "root"? Doesn't this warn
> > even then?
>
> I meant to warn even if device_model_user is NULL because it is th
On Thu, Jan 14, 2016 at 12:04:45PM +, Will Deacon wrote:
> On Wed, Jan 13, 2016 at 12:58:22PM -0800, Leonid Yegoshin wrote:
> > On 01/13/2016 12:48 PM, Peter Zijlstra wrote:
> > >On Wed, Jan 13, 2016 at 11:02:35AM -0800, Leonid Yegoshin wrote:
> > >
> > >>I ask HW team about it but I have a que
On Thu, 2016-01-14 at 17:32 +, Stefano Stabellini wrote:
>
> > > +LOG(DEBUG, "QEMU needs to be run as root for PCI passthrough to
> > > work");
> >
> > Shouldn't there be an if here, and/or an error return?
>
> Unfortunately we cannot get the user used to run QEMU with from here.
> Howev
Ian Campbell writes ("Re: [PATCH] QEMU as non-root and PCI passthrough do not
mix"):
> That reminds me -- how does the qemu user selection work over migrate? Does
> it remember the specific user or does it try and pick it again on the other
> end? Do we require all hosts in a pool to have been set
Ian Campbell wrote:
> On Mon, 2016-01-11 at 10:00 -0700, Jim Fehlig wrote:
>> On 01/07/2016 10:13 AM, Ian Campbell wrote:
>>> On Tue, 2015-12-22 at 18:44 +, Ian Jackson wrote:
This allows code elsewhere in libxl to find out what options a device
model executable supports. This is don
No resulting change. The compiled binary is identical.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Tim Deegan
CC: Ian Campbell
v2: Remove the fencepost adjustment. All valid cpu ids are < NR_CPUS.
---
xen/common/spinlock.c | 8
xen/include/xen/spinlock.h | 6 --
From: "Edgar E. Iglesias"
Signed-off-by: Edgar E. Iglesias
---
xen/drivers/char/cadence-uart.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/xen/drivers/char/cadence-uart.c b/xen/drivers/char/cadence-uart.c
index 933672f..7f90f8d 100644
--- a/xen/drivers/char/cadence-uart.c
+++ b/xen/driv
On 1/14/16 11:18 AM, Ian Jackson wrote:
> Doug Goldstein writes ("Re: [Xen-devel] [xen-unstable test] 77945:
> regressions - FAIL [and 2 more messages]"):
>> On 1/14/16 10:27 AM, Ian Jackson wrote:
>>> Is any of this of any use ?
>>>
>>> Thanks,
>>> Ian.
>>> (no less confused after writing this th
flight 78065 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/78065/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 10 guest-start fail REGR. vs. 60684
Tests whic
On 01/14/2016 04:14 AM, Will Deacon wrote:
On Wed, Jan 13, 2016 at 02:26:16PM -0800, Leonid Yegoshin wrote:
Moreover, there are voices against guarantee that it will be in future
and that voices point me to Documentation/memory-barriers.txt section "DATA
DEPENDENCY BARRIERS" examples which
flight 78066 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/78066/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt-raw 6 xen-boot fail REGR. vs. 77871
Regressions which are reg
On 01/14/2016 08:16 AM, Paul E. McKenney wrote:
On Thu, Jan 14, 2016 at 12:04:45PM +, Will Deacon wrote:
On Wed, Jan 13, 2016 at 12:58:22PM -0800, Leonid Yegoshin wrote:
On 01/13/2016 12:48 PM, Peter Zijlstra wrote:
On Wed, Jan 13, 2016 at 11:02:35AM -0800, Leonid Yegoshin wrote:
I ask H
On 01/14/2016 04:04 AM, Will Deacon wrote:
Consequently, it's important that the architecture back-ends implement
these portable primitives (e.g. smp_mb()) in a way that satisfies the
kernel memory model so that core code doesn't need to worry about the
underlying architecture for synchronisati
XTL_NEW_LOGGER() makes a number of unreasonable assumptions about the symbols
visible in its scope, and as such is only usable by its sole caller.
Remove it.
Signed-off-by: Andrew Cooper
---
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
tools/libs/toollog/include/xentoollog.h | 21 ---
On Thu, Jan 14, 2016 at 11:42:02AM -0800, Leonid Yegoshin wrote:
> An the only point - please use an appropriate SYNC_* barriers instead of
> heavy bold hammer. That stuff was design explicitly to support the
> requirements of Documentation/memory-barriers.txt
That's madness. That document changes
On Thu, Jan 14, 2016 at 11:28:18AM -0800, Leonid Yegoshin wrote:
> On 01/14/2016 04:14 AM, Will Deacon wrote:
> >On Wed, Jan 13, 2016 at 02:26:16PM -0800, Leonid Yegoshin wrote:
> >
> >> Moreover, there are voices against guarantee that it will be in future
> >>and that voices point me to Docum
On Thu, Jan 14, 2016 at 09:15:13PM +0100, Peter Zijlstra wrote:
> On Thu, Jan 14, 2016 at 11:42:02AM -0800, Leonid Yegoshin wrote:
> > An the only point - please use an appropriate SYNC_* barriers instead of
> > heavy bold hammer. That stuff was design explicitly to support the
> > requirements of
On Thu, Jan 14, 2016 at 09:15:13PM +0100, Peter Zijlstra wrote:
> On Thu, Jan 14, 2016 at 11:42:02AM -0800, Leonid Yegoshin wrote:
> > An the only point - please use an appropriate SYNC_* barriers instead of
> > heavy bold hammer. That stuff was design explicitly to support the
> > requirements of
On 01/14/2016 12:15 PM, Peter Zijlstra wrote:
On Thu, Jan 14, 2016 at 11:42:02AM -0800, Leonid Yegoshin wrote:
An the only point - please use an appropriate SYNC_* barriers instead of
heavy bold hammer. That stuff was design explicitly to support the
requirements of Documentation/memory-barriers
On Thu, Jan 14, 2016 at 12:12:53PM -0800, Leonid Yegoshin wrote:
> On 01/14/2016 04:04 AM, Will Deacon wrote:
> >Consequently, it's important that the architecture back-ends
> >implement these portable primitives (e.g. smp_mb()) in a way that
> >satisfies the kernel memory model so that core code d
I need some time to understand your test examples. However,
On 01/14/2016 12:34 PM, Paul E. McKenney wrote:
The WRC+addr+addr is OK because data dependencies are not required to be
transitive, in other words, they are not required to flow from one CPU to
another without the help of an explicit
On 01/14/2016 12:48 PM, Paul E. McKenney wrote:
So SYNC_RMB is intended to implement smp_rmb(), correct?
Yes.
You could use SYNC_ACQUIRE() to implement read_barrier_depends() and
smp_read_barrier_depends(), but SYNC_RMB probably does not suffice.
If smp_read_barrier_depends() is used to sep
On Thu, Jan 14, 2016 at 12:46:43PM -0800, Leonid Yegoshin wrote:
> On 01/14/2016 12:15 PM, Peter Zijlstra wrote:
> >On Thu, Jan 14, 2016 at 11:42:02AM -0800, Leonid Yegoshin wrote:
> >>An the only point - please use an appropriate SYNC_* barriers instead of
> >>heavy bold hammer. That stuff was des
This patch makes the generation of the FLASK utilities and the policy
explicit. This drops the two control knobs that affect how the FLASK
policy and tools are generated and unifies it under one.
CC: Ian Jackson
CC: Stefano Stabellini
CC: Ian Campbell
CC: Wei Liu
CC: Daniel De Graaf
Signed-of
On 01/14/2016 01:29 PM, Paul E. McKenney wrote:
On 01/14/2016 12:34 PM, Paul E. McKenney wrote:
The WRC+addr+addr is OK because data dependencies are not required to be
transitive, in other words, they are not required to flow from one CPU to
another without the help of an explicit memory bar
On Thu, Jan 14, 2016 at 01:01:05PM -0800, Leonid Yegoshin wrote:
> I need some time to understand your test examples. However,
Understood.
> On 01/14/2016 12:34 PM, Paul E. McKenney wrote:
> >
> >
> >The WRC+addr+addr is OK because data dependencies are not required to be
> >transitive, in other
On 1/14/16 8:28 AM, Doug Goldstein wrote:
> If the test should build with XSM then supply --enable-xsmpolicy to the
> tools/configure script otherwise provide --disable-xsmpolicy. This will
> allow the default to change from --enable-xsmpolicy to
> --disable-xsmpolicy in the Xen tree without breaki
Change the default on the --{enable,disable}-xsmpolicy configure switch
to disabled by default but always build the necessary utilities for
FLASK. The result is that the tools will always be built (and can be
omitted by the packager) but the policy won't always be generated and
installed if the too
On Thu, 14 Jan 2016, Vitaly Kuznetsov wrote:
> > My suggestion is to just simply document that auto-onlining can add the
> > memory but fail to online it and the failure is silent to userspace. If
> > userspace cares, it can check the online status of the added memory blocks
> > itself.
>
> T
On 01/14/2016 01:34 PM, Paul E. McKenney wrote:
On Thu, Jan 14, 2016 at 12:46:43PM -0800, Leonid Yegoshin wrote:
On 01/14/2016 12:15 PM, Peter Zijlstra wrote:
On Thu, Jan 14, 2016 at 11:42:02AM -0800, Leonid Yegoshin wrote:
An the only point - please use an appropriate SYNC_* barriers instead
From: Ross Lagerwall
Signed-off-by: Ross Lagerwall
Signed-off-by: Konrad Rzeszutek Wilk
---
v2: Slim the list as we do not use all of them.
---
xen/include/xen/elfstructs.h | 8
1 file changed, 8 insertions(+)
diff --git a/xen/include/xen/elfstructs.h b/xen/include/xen/elfstructs.h
i
From: Ross Lagerwall
Add support for applying alternative sections within xsplice modules. At
module load time, apply an alternative sections that are found.
Signed-off-by: Ross Lagerwall
Signed-off-by: Konrad Rzeszutek Wilk
---
xen/arch/x86/Makefile | 2 +-
xen/arch/x86/alternat
The implementation does not actually do any patching.
It just adds the framework for doing the hypercalls,
keeping track of ELF payloads, and the basic operations:
- query which payloads exist,
- query for specific payloads,
- check*1, apply*1, replace*1, and unload payloads.
*1: Which of cour
The underlaying toolstack code to do the basic
operations when using the XEN_XSPLICE_op syscalls:
- upload the payload,
- get status of an payload,
- list all the payloads,
- apply, check, replace, and revert the payload.
Signed-off-by: Konrad Rzeszutek Wilk
Signed-off-by: Ross Lagerwall
---
in the keyhandler.h file. Otherwise on ARM builds if we
just use the keyhandler file - the compile will fail.
Signed-off-by: Konrad Rzeszutek Wilk
---
xen/include/xen/keyhandler.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/xen/include/xen/keyhandler.h b/xen/include/xen/keyhandler.h
inde
Changelog (since the RFC and the Seattle Xen presentation)
- Finished off some of the work around the build-id.
- Settled on the preemption mechanism.
- Cleaned the patches a lot up, broke them up to easy
review for maintainers.
v1 (http://lists.xenproject.org/archives/html/xen-devel/2015-09/
From: Ross Lagerwall
Add support for exception tables contained within xSplice payloads. If an
exception occurs search either the main exception table or a particular
active payload's exception table depending on the instruction pointer.
Signed-off-by: Ross Lagerwall
Signed-off-by: Konrad Rzesz
From: Ross Lagerwall
Add support for loading xsplice payloads. This is somewhat similar to
the Linux kernel module loader, implementing the following steps:
- Verify the elf file.
- Parse the elf file.
- Allocate a region of memory mapped within a free area of
[xen_virt_end, XEN_VIRT_END].
- Co
From: Ross Lagerwall
Implement support for the apply, revert and replace actions.
To perform and action on a payload, the hypercall sets up a data
structure to schedule the work. A hook is added in all the
return-to-guest paths to check for work to do and execute it if needed.
In this way, patc
From: Ross Lagerwall
Add Elf routines and data structures in preparation for loading an
xSplice payload.
We also add an macro that will print where we failed during
the ELF parsing.
Signed-off-by: Ross Lagerwall
Signed-off-by: Konrad Rzeszutek Wilk
---
v2: - With the #define ELFSIZE in the AR
A simple tool that allows an system admin to perform
basic xsplice operations:
- Upload a xsplice file (with an unique id)
- List all the xsplice payloads loaded.
- Apply, revert, replace, unload, or check the payload using the
unique id.
- Do all three - upload, check, and apply the
pay
From: Ross Lagerwall
Add support for handling bug frames contained with xsplice modules. If a
trap occurs search either the kernel bug table or an applied payload's
bug table depending on the instruction pointer.
Signed-off-by: Ross Lagerwall
Signed-off-by: Konrad Rzeszutek Wilk
---
v2:- s/mod
A mechanism is required to binarily patch the running hypervisor with new
opcodes that have come about due to primarily security updates.
This document describes the design of the API that would allow us to
upload to the hypervisor binary patches.
This document has been shaped by the input from:
This change demonstrates how to generate an xSplice ELF payload.
The idea here is that we want to patch in the hypervisor
the 'xen_version_extra' function with an function that will
return 'Hello World'. The 'xl info | grep extraversion'
will reflect the new value after the patching.
To generate
From: David Vrabel
Date: Thu, 14 Jan 2016 15:18:30 +
> - needed = xenvif_rx_ring_slots_needed(queue->vif);
> + skb = skb_peek(&queue->rx_queue);
> + if (!skb)
> + return false;
> +
> + needed = DIV_ROUND_UP(skb->len, XEN_PAGE_SIZE);
> + if (skb_is_gso(skb))
> +
On Thu, Jan 14, 2016 at 01:24:34PM -0800, Leonid Yegoshin wrote:
> On 01/14/2016 12:48 PM, Paul E. McKenney wrote:
> >
> >So SYNC_RMB is intended to implement smp_rmb(), correct?
> Yes.
> >
> >You could use SYNC_ACQUIRE() to implement read_barrier_depends() and
> >smp_read_barrier_depends(), but SY
On Thu, Jan 14, 2016 at 01:45:44PM -0800, Leonid Yegoshin wrote:
> On 01/14/2016 01:34 PM, Paul E. McKenney wrote:
> >On Thu, Jan 14, 2016 at 12:46:43PM -0800, Leonid Yegoshin wrote:
> >>On 01/14/2016 12:15 PM, Peter Zijlstra wrote:
> >>>On Thu, Jan 14, 2016 at 11:42:02AM -0800, Leonid Yegoshin wro
On Thu, Jan 14, 2016 at 01:36:50PM -0800, Leonid Yegoshin wrote:
> On 01/14/2016 01:29 PM, Paul E. McKenney wrote:
> >
> >>On 01/14/2016 12:34 PM, Paul E. McKenney wrote:
> >>>
> >>>The WRC+addr+addr is OK because data dependencies are not required to be
> >>>transitive, in other words, they are no
On 01/14/2016 02:24 PM, Paul E. McKenney wrote:
Actually, the Linux kernel doesn't have an acquire barrier, just an
smp_load_acquire(). Or did someone sneak one in while I wasn't looking?
That was an exactly starting point for this discussion. This patch just
pulls out from MIPS files smp_load_a
On 01/14/2016 02:55 PM, Paul E. McKenney wrote:
OK, so it looks like Will was asking not about WRC+addr+addr, but instead
about WRC+sync+addr.
(He actually asked twice about this and that too but skip this)
I am guessing that the manual's "Older instructions which must be globally
performed wh
flight 78081 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/78081/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 5 xen-install fail REGR.
vs. 77892
test-amd64
flight 78101 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/78101/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail REGR.
vs. 65543
test-amd64-amd64-
On Thu, Jan 14, 2016 at 03:33:40PM -0800, Leonid Yegoshin wrote:
> On 01/14/2016 02:55 PM, Paul E. McKenney wrote:
> >OK, so it looks like Will was asking not about WRC+addr+addr, but instead
> >about WRC+sync+addr.
> (He actually asked twice about this and that too but skip this)
Fair enough! ;-
Hello,
I'm confused by the use of idle_vcpu[] in Xen schedulers. In credit,
credit2 and rtds schedulers, they are used in conjunction with variable
"tasklet_work_scheduled" like this:
if ( tasklet_work_scheduled )
{
snext = #_VCPU(idle_vcpu[cpu]);
}
The idle_vcpu array is initia
On 01/14/2016 04:47 PM, Paul E. McKenney wrote:
On Thu, Jan 14, 2016 at 03:33:40PM -0800, Leonid Yegoshin wrote:
Don't be fooled here by words "ordered" and "completed" - it is HW
design items and actually written poorly.
Just assume that SYNC_MB is absolutely the same as SYNC for any CPU
and co
flight 78082 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/78082/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-rtds 9 debian-install fail like 77919
Tests which did not succeed,
flight 78109 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/78109/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 77918
Tests which did not succeed, but a
branch xen-unstable
xenbranch xen-unstable
job test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm
testid xen-install
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git
Tr
As the libxl_strdup allows us to unwind and free all
of the allocations, while strdup requires the callers
to remember to free (which they didn't seem too).
Suggested-by: Wei Liu
Signed-off-by: Konrad Rzeszutek Wilk
---
tools/libxl/libxl.c | 16
1 file changed, 8 insertions(+),
On 1/14/16 9:06 AM, Roger Pau Monne wrote:
> If sysconf(_SC_GETPW_R_SIZE_MAX) fails for any reason just use an initial
> buffer size of 2048. This is not a critical failure, and the code that
> makes use of this buffer is able to expand it later if required.
>
> Signed-off-by: Roger Pau Monné
> -
On January 14, 2016 9:33:49 PM EST, Konrad Rzeszutek Wilk
wrote:
>As the libxl_strdup allows us to unwind and free all
>of the allocations, while strdup requires the callers
>to remember to free (which they didn't seem too).
>
Gr.. Ignore it pls. I cherry picked it and had a preceding patch
On 01/14/2016 06:21 PM, Ian Campbell wrote:
> On Tue, 2016-01-12 at 09:40 +0800, Wen Congyang wrote:
>> On 01/09/2016 12:27 AM, Ian Campbell wrote:
>>> On Fri, 2016-01-08 at 14:38 +0800, Wen Congyang wrote:
For example: if the secondary host is down, and we fail to send the
data
to
>
flight 78134 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/78134/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail REGR.
vs. 65543
test-amd64-amd64-
From: Shannon Zhao
Add a new delivery type:
val[63:56] == 3: val[15:8] is flag: val[7:0] is a PPI.
To the flag, bit 0 stands the interrupt mode is edge(1) or level(0) and
bit 1 stands the interrupt polarity is active low(1) or high(0).
Signed-off-by: Shannon Zhao
---
include/xen/interface/hvm/
From: Shannon Zhao
This patch set adds ACPI support for Xen Dom0 on ARM64. The relevant Xen
ACPI on ARM64 design document could be found from [1].
This patch set adds a new FDT node "uefi" under /hypervisor to pass UEFI
information. Introduce a bus notifier of AMBA and Platform bus to map
the ne
From: Shannon Zhao
Add a new type of Xen map space for Dom0 to map device's MMIO region.
Signed-off-by: Shannon Zhao
---
include/xen/interface/memory.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/xen/interface/memory.h b/include/xen/interface/memory.h
index 2ecfe4f..9aa8988 100
From: Shannon Zhao
When it's a Xen domain0 booting with ACPI, it will supply a /chosen and
a /hypervisor node in DT. So check if it needs to enable ACPI.
Signed-off-by: Shannon Zhao
---
arch/arm64/kernel/acpi.c | 12
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/ar
From: Shannon Zhao
Add a new function to parse DT parameters for Xen specific UEFI just
like the way for normal UEFI. Then it could reuse the existing codes.
Signed-off-by: Shannon Zhao
---
drivers/firmware/efi/efi.c | 45 ++---
1 file changed, 38 insert
From: Shannon Zhao
Add a bus_notifier for platform bus device in order to map the device
mmio regions when DOM0 booting with ACPI.
Signed-off-by: Shannon Zhao
---
drivers/xen/Makefile | 1 +
drivers/xen/arm-device.c | 140 +++
2 files changed,
101 - 200 of 212 matches
Mail list logo
