On Thu, Sep 01, 2016 at 01:40:11AM -0600, Jan Beulich wrote:
> >>> On 31.08.16 at 19:07, wrote:
> > On Wed, Aug 31, 2016 at 06:49:51AM -0600, Jan Beulich wrote:
> >> >>> On 30.08.16 at 21:32, wrote:
> >> > On Thu, Aug 25, 2016 at 06:59:54AM
Hey Julien,
On Thu, Sep 01, 2016 at 01:47:05PM +0100, Julien Grall wrote:
> Hi Daniel,
>
> I have heard you became co-maintainer of GRUB. Congratulations for that :).
Thanks a lot!
> We have a couple series (this series and [1]) to allow grub booting
> Xen on ARM that have been waiting on the
This run is configured for baseline tests only.
flight 67622 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67622/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf b10d5ddc0385f39d2c2c62843710b7609a4ca169
baseline
On Thu, Sep 01, 2016 at 01:46:24AM -0600, Jan Beulich wrote:
> >>> On 31.08.16 at 22:50, wrote:
> > On Wed, Aug 31, 2016 at 09:46:31AM -0600, Jan Beulich wrote:
> >> >>> On 31.08.16 at 16:59, wrote:
> >> > On Thu, Aug 25, 2016 at 08:41:39AM
On Thu, Sep 01, 2016 at 01:41:26AM -0600, Jan Beulich wrote:
> >>> On 31.08.16 at 21:31, wrote:
> > On Wed, Aug 31, 2016 at 07:01:10AM -0600, Jan Beulich wrote:
> >> >>> On 30.08.16 at 21:58, wrote:
> >> > On Thu, Aug 25, 2016 at 07:27:21AM
"Old" tested version had not actually been tested; therefore in this
flight we test it, rather than a new candidate. The baseline, if
any, is the most recent actually tested revision.
flight 100704 qemu-upstream-4.7-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100704/
>>> On 31.08.16 at 20:39, wrote:
> On 24/08/16 09:01, Jan Beulich wrote:
>> Non-debugging message text should be (and is here) distinguishable
>> without also logging function names.
>>
>> Signed-off-by: Jan Beulich
>>
>> ---
>>> On 31.08.16 at 22:50, wrote:
> On Wed, Aug 31, 2016 at 09:46:31AM -0600, Jan Beulich wrote:
>> >>> On 31.08.16 at 16:59, wrote:
>> > On Thu, Aug 25, 2016 at 08:41:39AM -0600, Jan Beulich wrote:
>> >> >>> On 20.08.16 at 00:43,
>>> On 31.08.16 at 05:56, wrote:
> +void vmx_pi_desc_fixup(int cpu)
unsigned int
> +{
> +unsigned int new_cpu, dest;
> +unsigned long flags;
> +struct arch_vmx_struct *vmx, *tmp;
> +spinlock_t *new_lock, *old_lock = _cpu(vmx_pi_blocking, cpu).lock;
> +
On 31/08/16 10:30, Wei Liu wrote:
> This email only tracks big items for xen.git tree. Please reply for items you
> woulk like to see in 4.8 so that people have an idea what is going on and
> prioritise accordingly.
>
> You're welcome to provide description and use cases of the feature you're
>
>>> On 31.08.16 at 21:31, wrote:
> On Wed, Aug 31, 2016 at 07:01:10AM -0600, Jan Beulich wrote:
>> >>> On 30.08.16 at 21:58, wrote:
>> > On Thu, Aug 25, 2016 at 07:27:21AM -0600, Jan Beulich wrote:
>> >> >>> On 20.08.16 at 00:43,
On 09/01/2016 10:58 AM, Jan Beulich wrote:
On 01.09.16 at 09:26, wrote:
>> On 09/01/16 02:52, Tamas K Lengyel wrote:
>>> --- a/xen/include/public/vm_event.h
>>> +++ b/xen/include/public/vm_event.h
>>> @@ -226,6 +226,13 @@ struct vm_event_mov_to_msr {
>>>
>>>
>>> On 31.08.16 at 05:56, wrote:
> --- a/xen/arch/x86/hvm/vmx/vmx.c
> +++ b/xen/arch/x86/hvm/vmx/vmx.c
> @@ -219,8 +219,19 @@ void vmx_pi_hooks_assign(struct domain *d)
>
> ASSERT(!d->arch.hvm_domain.vmx.vcpu_block);
>
> +/*
> + * Pausing the domain can make
flight 100684 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100684/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-raw 16 guest-localmigrate/x10 fail REGR. vs. 100674
Regressions which
>>> On 31.08.16 at 19:07, wrote:
> On Wed, Aug 31, 2016 at 06:49:51AM -0600, Jan Beulich wrote:
>> >>> On 30.08.16 at 21:32, wrote:
>> > On Thu, Aug 25, 2016 at 06:59:54AM -0600, Jan Beulich wrote:
>> >> >>> On 20.08.16 at 00:43,
With livepatch the alternatives that should be patched are outside of
the Xen hypervisor _start -> _end. The current code is assuming that
only Xen could be patched and therefore will explode when a payload
contains alternatives.
Given that alt_instr contains a relative offset, the function
Hi all,
> === ARM ===
>
> * Altp2m for ARM
> - Sergej Proskurin
>
We have submitted a patch-series version 3 and still waiting for
remaining reviews.
Cheers,
~Sergej
___
Xen-devel mailing list
Xen-devel@lists.xen.org
>>> On 01.09.16 at 09:26, wrote:
> On 09/01/16 02:52, Tamas K Lengyel wrote:
>> --- a/xen/include/public/vm_event.h
>> +++ b/xen/include/public/vm_event.h
>> @@ -226,6 +226,13 @@ struct vm_event_mov_to_msr {
>>
>> struct vm_event_cpuid {
>> uint32_t insn_length;
flight 67618 distros-debian-wheezy real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67618/
Perfect :-)
All tests in this flight passed as required
baseline version:
flight 67592
jobs:
build-amd64 pass
On 09/01/16 02:52, Tamas K Lengyel wrote:
> Extend the CPUID monitor event to include EAX and ECX values that were used
> when CPUID was executed. This is useful in identifying which leaf was queried.
> We also adjust the xen-access output format to more closely resemble the
> output
> of the
>>> On 01.09.16 at 01:52, wrote:
> --- a/xen/arch/x86/hvm/vmx/vmx.c
> +++ b/xen/arch/x86/hvm/vmx/vmx.c
> @@ -2402,12 +2402,17 @@ static void vmx_cpuid_intercept(
> static int vmx_do_cpuid(struct cpu_user_regs *regs)
> {
> unsigned int eax, ebx, ecx, edx;
> +
>>> On 31.08.16 at 05:56, wrote:
> This patch handles some concern cases when the last assigned device
> is removed from the domain. In this case we should carefully handle
> pi descriptor and the per-cpu blocking list, to make sure:
> - all the PI descriptor are in the right
On 30/08/16 23:38, Samuel Thibault wrote:
> Hello,
>
> Juergen Gross, on Tue 30 Aug 2016 13:51:23 +0200, wrote:
>> @@ -51,7 +51,7 @@ endif
>>
>> libc = $(stubdom)
>>
>> -XEN_INTERFACE_VERSION := 0x00030205
>> +XEN_INTERFACE_VERSION ?= 0x00030205
>
> Why making it overridable? AIUI changing
>>> On 31.08.16 at 20:36, wrote:
> On this note, I have a series I never really started properly, which
> introduces a single pci_sbdf_t, totalling 32 bits of bitfields, and a
> custom %p handler. The register shuffling required in all the function
> calls taking 4
>>> On 31.08.16 at 20:43, wrote:
> On 24/08/16 09:02, Jan Beulich wrote:
>> Non-debugging message text should be (and is in the cases here)
>> distinguishable without also logging function names. Debugging message
>> text, otoh, already includes file name and line
>>> On 31.08.16 at 21:39, wrote:
> I understood that you need reloc.c after this patch but it looks
> that I was wrong. So, here it is after applying whole series.
Thanks. Here are my notes:
All callers of alloc_mem() cast the result to a pointer. While most of
them
flight 100686 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100686/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 5 xen-buildfail REGR. vs. 100671
build-amd64
>>> On 31.08.16 at 05:56, wrote:
> --- a/xen/arch/x86/hvm/vmx/vmx.c
> +++ b/xen/arch/x86/hvm/vmx/vmx.c
> @@ -207,8 +207,6 @@ void vmx_pi_hooks_assign(struct domain *d)
> ASSERT(!d->arch.hvm_domain.vmx.vcpu_block);
>
> d->arch.hvm_domain.vmx.vcpu_block =
>>> On 31.08.16 at 05:56, wrote:
> We don't set the affinity for posted format IRTE, since the
> destination of these interrupts is vCPU and the vCPU affinity
> is set during vCPU scheduling.
So is this based on the assumption that after initial setup the function
would only
flight 100687 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100687/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 950a3bc788b5b101729b26aed3ff75fd2a64a570
baseline version:
ovmf
flight 100690 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100690/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf 4 host-build-prep fail REGR. vs. 100674
Regressions which
Windows 8, 10 and Server 2012 guests hang intermittently while booting
on Xen 4.5.3 with 1 vCPU and 4 e1000 vNICs, shortly after the Windows
logo appears and the little dots start spinning.
Running strace on qemu shows its main thread doing the following every
couple of milliseconds:
Hi all,
just a quick reminder that tomorrow, Friday the 2nd of September, at 9AM
PST / 5PM UK, there will be a technical community call on PV Calls.
To join the call, visit:
https://www.uberconference.com/stefano-aporeto
The webpage contains information on how to join the call via PC or
flight 100703 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100703/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf b10d5ddc0385f39d2c2c62843710b7609a4ca169
baseline version:
ovmf
cpufeat_mask() yields an unsigned integer constant. As a result, taking its
complement causes zero extention rather than sign extention.
The result is that, when a guest OS has OXSAVE disabled, all features in 1d
are hidden from native CPUID. Amongst other things, this causes the early
code in
On 09/01/2016 03:35 PM, Andrew Cooper wrote:
> On 01/09/16 20:27, Boris Ostrovsky wrote:
>> Newer gcc (6.1.1 is what I am using with Fedora 24) is having trouble
>> compiling ipxe that is fetched by Xen, mostly due to stricter checks.
>>
>> I have a patch that fixes all these warnings but do we
This run is configured for baseline tests only.
flight 67621 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67621/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 5322ee484b54bc78023383a546971b601dcc4ce1
baseline
* Use %pv or just d%d in preference to the multiple current ways of
presenting the same information.
* Use PRI_mfn instead of opencoding it.
* Drop all explicit use of __func__ from SHADOW_{PRINTK,DEBUG}() calls. The
wrappers already include it.
* Use hex rather than decimal for
This allows printf format checking to be performed, and for
debugtrace_printk() to evaluate its arguments, even if debugtrace is disabled
at compile time.
No intended change.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Tim Deegan
Newer gcc (6.1.1 is what I am using with Fedora 24) is having trouble
compiling ipxe that is fetched by Xen, mostly due to stricter checks.
I have a patch that fixes all these warnings but do we want it or should
we instead upgrade to latest ipxe version? (It builds fine but I haven't
tested it).
On 01/09/16 20:27, Boris Ostrovsky wrote:
> Newer gcc (6.1.1 is what I am using with Fedora 24) is having trouble
> compiling ipxe that is fetched by Xen, mostly due to stricter checks.
>
> I have a patch that fixes all these warnings but do we want it or should
> we instead upgrade to latest ipxe
On 01/09/16 20:40, Boris Ostrovsky wrote:
> On 09/01/2016 03:35 PM, Andrew Cooper wrote:
>> On 01/09/16 20:27, Boris Ostrovsky wrote:
>>> Newer gcc (6.1.1 is what I am using with Fedora 24) is having trouble
>>> compiling ipxe that is fetched by Xen, mostly due to stricter checks.
>>>
>>> I have a
On 01/09/16 08:13, Jan Beulich wrote:
On 31.08.16 at 20:39, wrote:
>> On 24/08/16 09:01, Jan Beulich wrote:
>>> Non-debugging message text should be (and is here) distinguishable
>>> without also logging function names.
>>>
>>> Signed-off-by: Jan Beulich
On 24/08/16 16:31, Jan Beulich wrote:
> Another place where we should try to behave like real hardware; see
> the code comments.
>
> Signed-off-by: Jan Beulich
>
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -3358,6 +3358,31 @@ void hvm_cpuid(unsigned int
These were relevant only for 32-bit builds on Xen.
Signed-off-by: Jan Beulich
--- a/xen/arch/x86/traps.c
+++ b/xen/arch/x86/traps.c
@@ -2200,10 +2200,8 @@ void guest_io_write(unsigned int port, u
}
/* I/O emulation support. Helper routines for, and type of, the stack
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, September 1, 2016 5:23 PM
> To: Wu, Feng
> Cc: andrew.coop...@citrix.com; dario.faggi...@citrix.com;
> george.dun...@eu.citrix.com; Tian, Kevin ; xen-
>
>>> On 01.09.16 at 11:22, wrote:
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Thursday, September 1, 2016 4:21 PM
>> >>> On 31.08.16 at 05:56, wrote:
>> > This patch handles some concern cases when the last assigned device
>> > is removed from
On 17/08/16 18:19, Dario Faggioli wrote:
For get_fallback_cpu(), by putting in place the "usual"
two steps (soft affinity step and hard affinity step)
loop. We just move the core logic of the function inside
the body of the loop itself.
For csched2_cpu_pick(), what is important is to find
the
>>> On 31.08.16 at 11:49, wrote:
> --- a/docs/misc/xen-command-line.markdown
> +++ b/docs/misc/xen-command-line.markdown
> @@ -1433,6 +1433,7 @@ Set the serial transmit buffer size.
> > Default: `true`
>
> Flag to enable Supervisor Mode Execution Protection
> +Use
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, September 1, 2016 4:17 PM
> To: Wu, Feng
> Cc: andrew.coop...@citrix.com; dario.faggi...@citrix.com;
> george.dun...@eu.citrix.com; Tian, Kevin ; xen-
>
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, September 1, 2016 4:21 PM
> To: Wu, Feng
> Cc: andrew.coop...@citrix.com; dario.faggi...@citrix.com;
> george.dun...@eu.citrix.com; Tian, Kevin ; xen-
>
It is possible, when normalising a PV pagetable that the table has been freed
and reused for something else by the guest.
In such a case, data read might no longer be a pagetable, and fail the
truncation check. However, this should only be fatal if we encounter such a
page in the paused phase.
On 17/08/16 18:19, Dario Faggioli wrote:
This is done by means of the "usual" two steps loop:
- soft affinity balance step;
- hard affinity balance step.
The entire logic implemented in runq_tickle() is
applied, during the first step, considering only the
CPUs in the vcpu's soft affinity.
This run is configured for baseline tests only.
flight 67619 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67619/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 950a3bc788b5b101729b26aed3ff75fd2a64a570
baseline
>>> On 01.09.16 at 11:13, wrote:
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Thursday, September 1, 2016 4:17 PM
>> >>> On 31.08.16 at 05:56, wrote:
>> > --- a/xen/arch/x86/hvm/vmx/vmx.c
>> > +++ b/xen/arch/x86/hvm/vmx/vmx.c
>> > @@ -207,8
On 01/09/16 10:08, Jan Beulich wrote:
> These were relevant only for 32-bit builds on Xen.
>
> Signed-off-by: Jan Beulich
Reviewed-by: Andrew Cooper
___
Xen-devel mailing list
Xen-devel@lists.xen.org
It is possible, when normalising a PV pagetable that the table has been freed
and reused for something else by the guest.
In such a case, data read might no longer be a pagetable, and fail the
truncation check. However, this should only be fatal if we encounter such a
page in the paused phase.
On 01/09/16 08:17, Jan Beulich wrote:
On 31.08.16 at 20:43, wrote:
>> On 24/08/16 09:02, Jan Beulich wrote:
>>> Non-debugging message text should be (and is in the cases here)
>>> distinguishable without also logging function names. Debugging message
>>> text,
Contrary to c/s b2507fe7 "x86/domctl: Update PV domain cpumasks when setting
cpuid policy", Intel CPUID masks are applied after fast forwarding hardware
state, rather than before. (All behaviour in this regard appears completely
undocumented by both Intel and AMD).
Therefore, a set bit in the
>>> On 01.09.16 at 12:25, wrote:
> Contrary to c/s b2507fe7 "x86/domctl: Update PV domain cpumasks when setting
> cpuid policy", Intel CPUID masks are applied after fast forwarding hardware
> state, rather than before. (All behaviour in this regard appears completely
>
Fix some typos in docs/man/xl.cfg.pod.5.in
Signed-off-by: Juergen Gross
---
docs/man/xl.cfg.pod.5.in | 26 +-
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/docs/man/xl.cfg.pod.5.in b/docs/man/xl.cfg.pod.5.in
index 6feee52..77a1be3
On 29/08/16 14:57, Jan Beulich wrote:
> - There's no 32-bit displacement in 16-bit addressing mode.
> - It is wrong to ASSERT() anything on parts of an instruction fetched
> from guest memory.
> - The two scaling bits of a SIB byte don't affect whether there is no
> scaled index register.
>
>
Hi Stefano,
On 31/08/16 20:33, Stefano Stabellini wrote:
On Wed, 31 Aug 2016, Julien Grall wrote:
@@ -236,28 +238,99 @@ static lpae_t *p2m_get_root_pointer(struct
p2m_domain *p2m,
/*
* Lookup the MFN corresponding to a domain's GFN.
+ * Lookup mem access in the ratrix tree.
+ * The entries
On Thu, 1 Sep 2016, Konrad Rzeszutek Wilk wrote:
> On Thu, Sep 01, 2016 at 02:11:31PM +0200, Olaf Hering wrote:
> > Implement SUSE specific unplug protocol for emulated PCI devices
> > in PVonHVM guests. Its a simple 'outl(1, (ioaddr + 4));'.
> > This protocol was implemented and used since Xen
flight 100706 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100706/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 14 guest-stop fail REGR. vs. 100674
Regressions which
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, September 1, 2016 4:30 PM
> To: Wu, Feng
> Cc: andrew.coop...@citrix.com; dario.faggi...@citrix.com;
> george.dun...@eu.citrix.com; Tian, Kevin ; xen-
>
flight 100708 qemu-upstream-4.7-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100708/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale 15 guest-start/debian.repeat fail REGR. vs. 100704
Hello.
I'm recently trying to utilize the virtualization exception (#VE) feature.
As the document says, #VE is handled by guest interrupt handler. The IRQ
number of #VE is 20. However, when I tried to register an IRQ handler for
#VE, it returns errno -22, which means invalid arguments.
On 08/31/2016 12:15 PM, Sebastian Andrzej Siewior wrote:
> On 2016-08-26 15:37:38 [-0400], Boris Ostrovsky wrote:
>>> If you do find the time, you might manage to rework the code to avoid
>>> using the _nocalls() function. If see this right, you use
>>> xen_setup_vcpu_info_placement() for the init
From: Shannon Zhao
Since the existing configuration option "u.hvm.acpi" is x86 specific and
we want to reuse it on ARM as well, add a unified option "acpi" for
x86 and ARM, and for ARM it's disabled by default.
Signed-off-by: Shannon Zhao
---
From: Shannon Zhao
It uses static DSDT table like the way x86 uses. Currently the DSDT
table only contains processor device objects and it generates the
maximal objects which so far is 128.
While the GUEST_MAX_VCPUS is defined under __XEN__ or __XEN_TOOLS__, it
needs to
From: Shannon Zhao
According to the GIC version, construct the MADT table.
Signed-off-by: Shannon Zhao
---
tools/libxl/libxl_arm_acpi.c | 84
1 file changed, 84 insertions(+)
diff --git
From: Shannon Zhao
Signed-off-by: Shannon Zhao
---
tools/libxl/libxl_arm_acpi.c | 23 +++
1 file changed, 23 insertions(+)
diff --git a/tools/libxl/libxl_arm_acpi.c b/tools/libxl/libxl_arm_acpi.c
index d3358b3..407f9d5
From: Shannon Zhao
Add the ARM Multiboot module for ACPI, so UEFI or DomU can get the base
address of ACPI tables from it.
Signed-off-by: Shannon Zhao
Acked-by: Julien Grall
---
docs/misc/arm/device-tree/acpi.txt | 24
From: Shannon Zhao
Rename finalise_one_memory_node to finalise_one_node and pass the node
name via function parameter.
This is useful for adding ACPI module which will be added by a later
patch.
Signed-off-by: Shannon Zhao
Acked-by: Julien
From: Shannon Zhao
Copy the static DSDT table into ACPI blob.
Signed-off-by: Shannon Zhao
---
tools/libxl/libxl_arm_acpi.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/tools/libxl/libxl_arm_acpi.c
From: Shannon Zhao
Factor MPIDR computing codes out as a helper, so it could be shared
between DT and ACPI.
Signed-off-by: Shannon Zhao
Acked-by: Julien Grall
---
tools/libxl/libxl_arm.c | 8 +---
On 2016/9/1 20:53, Boris Ostrovsky wrote:
> On 08/31/2016 11:18 PM, Shannon Zhao wrote:
>> >
>> > On 2016/8/30 1:46, Julien Grall wrote:
>>> diff --git a/tools/libacpi/Makefile b/tools/libacpi/Makefile
>>> index d741ac5..7f50a33 100644
>>> --- a/tools/libacpi/Makefile
>>> +++
On 09/01/2016 08:55 PM, Shannon Zhao wrote:
>
> On 2016/9/1 20:53, Boris Ostrovsky wrote:
>> On 08/31/2016 11:18 PM, Shannon Zhao wrote:
On 2016/8/30 1:46, Julien Grall wrote:
diff --git a/tools/libacpi/Makefile b/tools/libacpi/Makefile
index d741ac5..7f50a33 100644
Hello,
Juergen Gross, on Thu 01 Sep 2016 08:21:33 +0200, wrote:
> I stumbled over the problem with xenstore-stubdom: xenstore is using
> __XEN_LATEST_INTERFACE_VERSION__ when being compiled. This produced a
> build error with Mini-OS (console_evtchn in include/console.h was
> #define'd to
Wei Liu, on Tue 30 Aug 2016 14:57:50 +0100, wrote:
> On Tue, Aug 30, 2016 at 01:51:23PM +0200, Juergen Gross wrote:
> > Mini-OS applications being compiled using Mini-OS headers without
> > being integrated in the make environment of Mini-OS need a way to set
> > CONFIG_* defines according to
On Thu, Sep 01, 2016 at 02:11:31PM +0200, Olaf Hering wrote:
> Implement SUSE specific unplug protocol for emulated PCI devices
> in PVonHVM guests. Its a simple 'outl(1, (ioaddr + 4));'.
> This protocol was implemented and used since Xen 3.0.4.
> It is used in all SUSE/SLES/openSUSE releases up
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, September 1, 2016 4:39 PM
> To: Wu, Feng
> Cc: andrew.coop...@citrix.com; dario.faggi...@citrix.com;
> george.dun...@eu.citrix.com; Tian, Kevin ; xen-
>
flight 100709 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100709/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 3ef3209d3028b77af9f56f183370e7b67cd7c849
baseline version:
ovmf
From: Shannon Zhao
The design of this feature is described as below.
Firstly, the toolstack (libxl) generates the ACPI tables according the
number of vcpus and gic controller.
Then, it copies these ACPI tables to DomU non-RAM memory map space and
passes them to UEFI
From: Shannon Zhao
Construct GTDT table with the interrupt information of timers.
Signed-off-by: Shannon Zhao
---
tools/libxl/libxl_arm_acpi.c | 38 ++
1 file changed, 38 insertions(+)
diff --git
From: Shannon Zhao
Signed-off-by: Shannon Zhao
---
tools/libxl/libxl_arm_acpi.c | 30 ++
1 file changed, 30 insertions(+)
diff --git a/tools/libxl/libxl_arm_acpi.c b/tools/libxl/libxl_arm_acpi.c
index
From: Shannon Zhao
Here it adds the ACPI tables size to set the target maxmem to avoid
providing less available memory for guest.
Signed-off-by: Shannon Zhao
---
tools/libxl/libxl_arch.h| 2 +-
tools/libxl/libxl_arm.c | 18
From: Shannon Zhao
Add macros for HVM_PARAM_CALLBACK_TYPE_PPI operation values and update
them in evtchn_fixup().
Also use HVM_PARAM_CALLBACK_IRQ_TYPE_SHIFT in hvm_set_callback_via().
Cc: Jan Beulich
Cc: Andrew Cooper
From: Shannon Zhao
Construct ACPI RSDP table and add a helper to calculate the ACPI table
checksum.
Signed-off-by: Shannon Zhao
---
tools/libxl/libxl_arm_acpi.c | 39 +++
1 file changed, 39 insertions(+)
From: Shannon Zhao
Estimate the size of ACPI tables and reserve a memory map space for ACPI
tables.
Signed-off-by: Shannon Zhao
---
tools/libxl/libxl_arm_acpi.c | 98
1 file changed, 98
From: Shannon Zhao
It only constructs the ACPI tables for 64-bit ARM DomU when user enables
acpi because 32-bit DomU doesn't support ACPI. And the generation codes
are only built for 64-bit toolstack.
Signed-off-by: Shannon Zhao
---
From: Shannon Zhao
The guest kernel will get the event channel interrupt information via
domain param HVM_PARAM_CALLBACK_IRQ. Initialize it here.
Signed-off-by: Shannon Zhao
---
tools/libxl/libxl_arm.c | 13 +
1 file changed, 13
>>> On 01.09.16 at 13:23, wrote:
> On 24/08/16 16:31, Jan Beulich wrote:
>> Another place where we should try to behave like real hardware; see
>> the code comments.
>>
>> Signed-off-by: Jan Beulich
>>
>> --- a/xen/arch/x86/hvm/hvm.c
>> +++
Hi Konrad,
On 25/08/16 14:37, Konrad Rzeszutek Wilk wrote:
Which is only used by Livepatch code. The purpose behind
this call is to modify the page table entries flags.
Specifically the .ro and .nx flags. The current mechanism
puts cache attributes in the flags and the .ro and .nx are
locked
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, September 1, 2016 6:24 PM
> To: Wu, Feng
> Cc: andrew.coop...@citrix.com; dario.faggi...@citrix.com;
> george.dun...@eu.citrix.com; Tian, Kevin ; xen-
>
flight 100697 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100697/
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
flight 100695 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100695/
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
Hi,
Your series seems to have some coding style problems. See output below for
more information:
Subject: [Qemu-devel] [PATCH 0/2] Xen HVM unplug changes
Type: series
Message-id: 20160901121131.16007-1-o...@aepfle.de
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=base
n=1
total=$(git log --oneline
On 01/09/16 12:31, Andrew Cooper wrote:
> On 29/08/16 14:57, Jan Beulich wrote:
>> - There's no 32-bit displacement in 16-bit addressing mode.
>> - It is wrong to ASSERT() anything on parts of an instruction fetched
>> from guest memory.
>> - The two scaling bits of a SIB byte don't affect
1 - 100 of 138 matches
Mail list logo