On 2016/3/24 23:37, Julien Grall wrote:
> Hi Shannon,
>
> On 24/03/16 15:01, Shannon Zhao wrote:
>> On 2016年03月23日 02:18, Julien Grall wrote:
>>>
+ * Dom0 configures the interrupt, set the interrupt type and
route it to
+ * Dom0.
+ */
+for( i = NR_LOCAL_I
On 2016/3/24 23:08, Rafael J. Wysocki wrote:
> On Thu, Mar 24, 2016 at 3:44 PM, Shannon Zhao wrote:
>> > +static void acpi_get_spcr_uart_addr(void)
> static void __init acpi_get_spcr_uart_addr(void)
>
> I suppose?
>
> Apart from this it looks fine.
>
Thanks, I'll update this one and resend it
flight 87181 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87181/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-xsm3 host-install(3) broken REGR. vs. 86491
test-amd64-i386-xl-q
From: Shannon Zhao
ACPI 6.0 introduces a new table STAO to list the devices which are used
by Xen and can't be used by Dom0. On Xen virtual platforms, the physical
UART is used by Xen. So here it hides UART from Dom0.
CC: "Rafael J. Wysocki" (supporter:ACPI)
CC: Len Brown (supporter:ACPI)
CC:
On 24/03/16 12:38, George Dunlap wrote:
> On Thu, Mar 24, 2016 at 11:23 AM, Andrew Cooper
> wrote:
>> On 24/03/16 10:58, Juergen Gross wrote:
>>> I've searched a little bit in git history in order to understand why
>>> xen-detect has been invented and/or has all the options which clearly
>>> are m
On March 18, 2016 6:20pm, wrote:
> >>> On 17.03.16 at 07:54, wrote:
> > --- a/xen/drivers/passthrough/amd/iommu_init.c
> > +++ b/xen/drivers/passthrough/amd/iommu_init.c
> > @@ -1339,12 +1339,14 @@ static void invalidate_all_devices(void)
> > iterate_ivrs_mappings(_invalidate_all_devices);
>
flight 87204 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87204/
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. 66399
build-i386-rumpuserxen
flight 87216 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87216/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
test-amd64-i386-xl-qemuu-ovm
On March 24, 2016 7:31pm, wrote:
> Recursive locks know their current owner, and since we use the function solely
> to determine whether a particular lock is being held by the current CPU (which
> so far has been an imprecise check), make actually check the owner for
> recusrively acquired locks.
On Fri, Mar 25, 2016 at 02:09:04PM +0800, Changlong Xie wrote:
> On 03/25/2016 12:05 AM, Ian Jackson wrote:
> >Changlong Xie writes ("[PATCH v12 23/26] COLO nic: implement COLO nic
> >subkind"):
> >>From: Wen Congyang
> >>
> >>implement COLO nic subkind.
> >...
> >>diff --git a/tools/libxl/libxl_
On 03/24/2016 10:53 PM, Steven Haigh wrote:
Hi all,
Firstly, I've cross-posted this to xen-devel and the lkml - as this
problem seems to only exist when using kernel 4.4 as a Xen DomU kernel.
I have also CC'ed Greg KH for his awesome insight as maintainer.
Please CC myself into replies - as I'm
On Fri, Mar 25, 2016 at 02:10:23PM +0800, Changlong Xie wrote:
> On 03/25/2016 12:12 AM, Ian Jackson wrote:
> >Changlong Xie writes ("[PATCH v12 26/26] cmdline switches and config vars to
> >control colo-proxy"):
> >>From: Wen Congyang
> >>
> >>Add cmdline switches to 'xl migrate-receive' command
On Fri, Mar 25, 2016 at 02:44:30PM +0800, Changlong Xie wrote:
[...]
> diff --git a/tools/libxl/libxl_types.idl b/tools/libxl/libxl_types.idl
> index 0470423..6893732 100644
> --- a/tools/libxl/libxl_types.idl
> +++ b/tools/libxl/libxl_types.idl
> @@ -600,6 +600,7 @@ libxl_device_nic = Struct("devi
CC Samuel
On Wed, Mar 23, 2016 at 02:26:51PM -0700, Sarah Newman wrote:
> 7c8f3483 introduced a break within a loop in netfront.c such that
> cons and nr_consumed were no longer always being incremented. The
> offset at cons will be processed multiple times with the break in
> place.
>
> Remove t
flight 87236 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87236/
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
build-amd64-rumpuserx
On Thu, Mar 24, 2016 at 09:24:01PM +, Wei Liu wrote:
> On Thu, Mar 24, 2016 at 04:00:14PM -0400, Konrad Rzeszutek Wilk wrote:
> [...]
> > +
> > +static int libxl__xc_version_wrapper(libxl__gc *gc, unsigned int cmd, char
> > *buf, ssize_t len, char **dst)
>
> Please wrap this long line.
>
> >
On Thu, Mar 24, 2016 at 04:00:33PM -0400, Konrad Rzeszutek Wilk wrote:
> If the hypervisor is built with we will display it.
>
> Signed-off-by: Konrad Rzeszutek Wilk
> Acked-by: Wei Liu
Hey Wei,
It has you Ack, but I think when I carried over the change (it used
to be its own function with swi
On Wed, Mar 23, 2016 at 12:35:36PM +, George Dunlap wrote:
> On 12/03/16 11:33, Dario Faggioli wrote:
> > (i.e., domain creation and destruction) so the
> > trace will show properly decoded info, rather
> > than just a bunch of hex codes.
> > ---
>
> For some reason git won't apply your 'v2',
Estimate the memory required for loading acpi/efi tables in Dom0. Make
the length of each table aligned with 64bit. Alloc the pages to store
the new created EFI and ACPI tables and free these pages when
destroying domain.
Signed-off-by: Shannon Zhao
---
v7: address several comments from Julien
--
Create STAO table for Dom0. This table is used to tell Dom0 whether it
should ignore UART defined in SPCR table or the ACPI namespace names.
Look at below url for details:
http://wiki.xenproject.org/mediawiki/images/0/02/Status-override-table.pdf
Signed-off-by: Parth Dixit
Signed-off-by: Shannon
Copy RSDP table and replace rsdp->xsdt_physical_address with the address
of XSDT table, so it can point to the right XSDT table.
Signed-off-by: Shannon Zhao
Acked-by: Stefano Stabellini
Acked-by: Julien Grall
---
xen/arch/arm/domain_build.c | 38 ++
1 file c
Copy and modify FADT table before passing it to Dom0. Set PSCI_COMPLIANT
and PSCI_USE_HVC.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
Acked-by: Julien Grall
---
xen/arch/arm/domain_build.c | 43 +++
1 file changed, 43 insertions(+)
diff
Copy main MADT table contents and distributor subtable from physical
ACPI MADT table. Make other subtables through the callback of
gic_hw_ops.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
Acked-by: Julien Grall
---
xen/arch/arm/domain_build.c | 60 +++
Map all other ACPI tables into Dom0 using 1:1 mappings.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
v7: Fix comments and printk log
---
xen/arch/arm/domain_build.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/xen/arch/arm/domain_build.c b/x
These patches are Part 4 (and last part) of the previous patch set I
sent which adds ACPI support for arm64 on Xen[1]. Split them as an
individual set for convenient reviewing.
These patches create UEFI and ACPI tables which are mapped to Dom0's
space and add other preparations for Dom0 to use ACP
Copy and modify XSDT table before passing it to Dom0. Replace the entry
value of the copied table. Add a new entry for STAO table as well. And
keep entry value of other reused tables unchanged.
Signed-off-by: Shannon Zhao
Acked-by: Stefano Stabellini
Acked-by: Julien Grall
---
xen/arch/arm/dom
Prepare EFI system table for Dom0 to describe the information of UEFI.
Signed-off-by: Parth Dixit
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
v7: use domain as parameter
---
xen/arch/arm/domain_build.c | 1 +
xen/arch/arm/efi/efi-dom0.c | 45 +++
Create a DT for Dom0 for ACPI-case only. DT contains minimal required
informations such as Dom0 bootargs, initrd, efi description table and
address of uefi memory table.
Also document this device tree bindings of "hypervisor" and
"hypervisor/uefi" node.
Signed-off-by: Naresh Bhat
Signed-off-by:
Add a new member in gic_hw_operations which is used to create MADT table
for Dom0.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
v7: make other fields of GICC zero
---
xen/arch/arm/gic-v2.c | 42 +++
xen/arch/arm/gic-v3.c | 56 ++
From: Parth Dixit
Create a helper function for mapping with cached attributes and
read-write range.
Signed-off-by: Parth Dixit
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
v7: rename to map_regions_rw_cache
---
xen/arch/arm/p2m.c| 26 ++
xen
These tables are aligned with 64bit.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
v7: add commnets to explain what thsi function does
---
xen/arch/arm/acpi/lib.c| 20
xen/include/asm-arm/acpi.h | 2 ++
2 files changed, 22 insertions(+)
diff --git a/
Store the event-channel interrupt number and flag in HVM parameter
HVM_PARAM_CALLBACK_IRQ. Then Dom0 could get it through hypercall
HVMOP_get_param.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
xen/arch/arm/domain_build.c | 14 ++
1 file changed, 14 insertions(+)
This new delivery type which is for ARM shares the same value with
HVM_PARAM_CALLBACK_TYPE_VECTOR which is for x86.
val[15:8] is flag: val[7:0] is a PPI.
To the flag, bit 8 stands the interrupt mode is edge(1) or level(0) and
bit 9 stands the interrupt polarity is active low(1) or high(0).
Cc: Ia
Create EFI memory descriptors to tell Dom0 the RAM region information,
ACPI table regions and EFI tables reserved regions.
Signed-off-by: Parth Dixit
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
v7: check the size
---
xen/arch/arm/domain_build.c | 1 +
xen/arch/arm/efi/efi-
Allow DOM0 to use all SPIs but the ones used by Xen. Then when Dom0
configures the interrupt, it could set the interrupt type and route it
to Dom0.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
v7: add a TODO for SMMU used SPIs
---
xen/arch/arm/domain_build.c | 35
Interrupt information is described in DSDT and is not available at the
time of booting. Check if the interrupt is permitted to access and set
the interrupt type, route it to guest dynamically only for SPI
and Dom0.
Signed-off-by: Parth Dixit
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabe
Map the UEFI and ACPI tables which we created to non-RAM space in Dom0.
Signed-off-by: Shannon Zhao
Reviewed-by: Stefano Stabellini
---
v7: flush the cache
---
xen/arch/arm/domain_build.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/xen/arch/arm/domain_build.c b/xen/
Add ACPI support on arm64 xen hypervisor. Enable EFI support on ARM.
Cc: Jan Beulich
Signed-off-by: Shannon Zhao
Acked-by: Jan Beulich
Reviewed-by: Stefano Stabellini
---
v7: Drop CONFIG_ACPI_BOOT
---
xen/arch/arm/Kconfig | 9 +
xen/common/efi/runtime.c | 12 +++-
2 files
Firstly it permits full MMIO capabilities for Dom0. Then deny MMIO
access of Xen used devices, such as UART, GIC, SMMU. Currently, it only
denies the MMIO access of UART and GIC regions. For other Xen used
devices it could be added later when they are supported.
Signed-off-by: Shannon Zhao
Review
It needs to map platform or amba device mmio to Dom0 on ARM. But when
booting with ACPI, it can't get the mmio region in Xen due to lack of
AML interpreter to parse DSDT table. Therefore, let Dom0 call a
hypercall to map mmio region when it adds the devices.
Here we add a new map space like the XE
Hi,
This regards bite-size task for Outreachy program [0].
I followed the patches prepared by Harmandeep [1] where functions in
xl_cmdimpl.c have the pattern:
"*main_foo() is treated somewhat as a regular main(), it is changed to
return EXIT_SUCCESS or EXIT_FAILURE.
*Functions that are not main
Add a new member in gic_hw_operations which is used to deny Dom0 access
to GIC regions.
Signed-off-by: Shannon Zhao
---
v7: move them out of CONFIG_ACPI
---
xen/arch/arm/gic-v2.c | 27 +++
xen/arch/arm/gic-v3.c | 41 +
xen/a
On 25/03/2016 11:23 PM, Boris Ostrovsky wrote:
> On 03/24/2016 10:53 PM, Steven Haigh wrote:
>> Hi all,
>>
>> Firstly, I've cross-posted this to xen-devel and the lkml - as this
>> problem seems to only exist when using kernel 4.4 as a Xen DomU kernel.
>> I have also CC'ed Greg KH for his awesome i
On 03/25/2016 10:05 AM, Steven Haigh wrote:
On 25/03/2016 11:23 PM, Boris Ostrovsky wrote:
On 03/24/2016 10:53 PM, Steven Haigh wrote:
Hi all,
Firstly, I've cross-posted this to xen-devel and the lkml - as this
problem seems to only exist when using kernel 4.4 as a Xen DomU kernel.
I have al
flight 87264 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87264/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt 6 xen-boot fail REGR. vs. 87134
test-armhf-armhf-libvirt-
On Thu, Mar 17, 2016 at 09:03:24AM -0400, Boris Ostrovsky wrote:
> Currently Xen uses default_cpu_present_to_apicid() which will always
> report BAD_APICID for PV guests since x86_bios_cpu_apic_id is initialised
> to that value and is never updated.
>
> With commit 1f12e32f4cd5 ("x86/topology: Cre
On Thu, Mar 17, 2016 at 09:03:25AM -0400, Boris Ostrovsky wrote:
> This call has always been missing from xen_play dead() but until
> recently this was rather benign. With new cpu hotplug framework
> however this call is required, otherwise a hot-plugged CPU will not
Could you include the commit i
On 03/16/2016 03:18 PM, Doug Goldstein wrote:
Rather than have XSM_MAGIC set in the global xen/config.h and set in
xsm.h if it's unset, just set it once in xsm.h since its only used in
files that already include xsm.h
Signed-off-by: Doug Goldstein
Acked-by: Daniel De Graaf
_
On 03/25/2016 10:53 AM, Konrad Rzeszutek Wilk wrote:
On Thu, Mar 17, 2016 at 09:03:25AM -0400, Boris Ostrovsky wrote:
This call has always been missing from xen_play dead() but until
recently this was rather benign. With new cpu hotplug framework
however this call is required, otherwise a hot-pl
On Thu, Mar 17, 2016 at 09:33:32AM -0400, Boris Ostrovsky wrote:
> Commit ce0d3c0a6fb1 ("genirq: Revert sparse irq locking around
> __cpu_up() and move it to x86 for now") reverted irq locking
> introduced by commit a89941816726 ("hotplug: Prevent alloc/free
> of irq descriptors during cpu up/down"
flight 87241 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87241/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 9 debian-hvm-install fail
REGR. vs. 86454
test
On 03/25/2016 11:10 AM, Konrad Rzeszutek Wilk wrote:
On Thu, Mar 17, 2016 at 09:33:32AM -0400, Boris Ostrovsky wrote:
Commit ce0d3c0a6fb1 ("genirq: Revert sparse irq locking around
__cpu_up() and move it to x86 for now") reverted irq locking
introduced by commit a89941816726 ("hotplug: Prevent
On Fri, Mar 25, 2016 at 09:25:22AM -0400, Konrad Rzeszutek Wilk wrote:
> On Thu, Mar 24, 2016 at 04:00:33PM -0400, Konrad Rzeszutek Wilk wrote:
> > If the hypervisor is built with we will display it.
> >
> > Signed-off-by: Konrad Rzeszutek Wilk
> > Acked-by: Wei Liu
>
> Hey Wei,
>
> It has you
On Fri, Mar 25, 2016 at 11:07:19AM -0400, Daniel De Graaf wrote:
> On 03/16/2016 03:18 PM, Doug Goldstein wrote:
> >Rather than have XSM_MAGIC set in the global xen/config.h and set in
> >xsm.h if it's unset, just set it once in xsm.h since its only used in
> >files that already include xsm.h
> >
>
On Fri, Mar 25, 2016 at 11:08:32AM -0400, Boris Ostrovsky wrote:
> On 03/25/2016 10:53 AM, Konrad Rzeszutek Wilk wrote:
> >On Thu, Mar 17, 2016 at 09:03:25AM -0400, Boris Ostrovsky wrote:
> >>This call has always been missing from xen_play dead() but until
> >>recently this was rather benign. With
On Fri, Mar 25, 2016 at 02:44:07PM +0800, Changlong Xie wrote:
> This patchset implemented the COLO feature for Xen.
> For detail/install/use of COLO feature, refer to:
> http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
>
> You can get the codes from here:
> https://github.com/Pating/xen
On Wed, Mar 23, 2016 at 01:45:37PM -0400, Zhigang Wang wrote:
> There should be 6 instead of 7 arguments now for tmem_control().
>
> Signed-off-by: Zhigang Wang
Acked-by: Wei Liu
> ---
> tools/python/xen/lowlevel/xc/xc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git
On 26/03/2016 1:44 AM, Boris Ostrovsky wrote:
> On 03/25/2016 10:05 AM, Steven Haigh wrote:
>> On 25/03/2016 11:23 PM, Boris Ostrovsky wrote:
>>> On 03/24/2016 10:53 PM, Steven Haigh wrote:
Hi all,
Firstly, I've cross-posted this to xen-devel and the lkml - as this
problem seems
On Thu, Mar 17, 2016 at 06:10:59PM -0400, Ross Philipson wrote:
> It seems the logic is meant to detect sector unaligned buffers for block
> writes. The NOTing of the logic instead masks off any unaligned bits and
> also would cause the function to always fail. It seems the function is not
> used i
On 03/25/2016 12:04 PM, Steven Haigh wrote:
It may not actually be the full logs. Once the system gets really upset,
you can't run anything - as such, grabbing anything from dmesg is not
possible.
The logs provided above is all that gets spat out to the syslog server.
I'll try tinkering with a
On 03/24/2016 04:00 PM, Konrad Rzeszutek Wilk wrote:
The VERSION hypercall provides the flexibility to expose
the size of the build-id (so the callers can allocate the
proper size before trying to retrieve it). It also allows
in one nice swoop to retrieve the hypervisor build-id in the
provided b
On Fri, Mar 18, 2016 at 06:00:23PM +0100, Daniel Kiper wrote:
> Add grub_relocator64_efi relocator. It will be used on EFI 64-bit platforms
> when multiboot2 compatible image requests MULTIBOOT_TAG_TYPE_EFI_BS. Relocator
> will set lower parts of %rax and %rbx accordingly to multiboot2 specificatio
On 03/25/2016 12:11 PM, Wei Liu wrote:
> On Thu, Mar 17, 2016 at 06:10:59PM -0400, Ross Philipson wrote:
>> It seems the logic is meant to detect sector unaligned buffers for block
>> writes. The NOTing of the logic instead masks off any unaligned bits and
>> also would cause the function to always
On Fri, Mar 25, 2016 at 12:34:29PM -0400, Ross Philipson wrote:
> On 03/25/2016 12:11 PM, Wei Liu wrote:
> > On Thu, Mar 17, 2016 at 06:10:59PM -0400, Ross Philipson wrote:
> >> It seems the logic is meant to detect sector unaligned buffers for block
> >> writes. The NOTing of the logic instead mas
On Fri, Mar 18, 2016 at 06:00:27PM +0100, Daniel Kiper wrote:
> Currently multiboot2 protocol loads image exactly at address specified in
> ELF or multiboot2 header. This solution works quite well on legacy BIOS
> platforms. It is possible because memory regions are placed at predictable
> addresse
On Friday, March 25, 2016 04:05:49 PM Shannon Zhao wrote:
> From: Shannon Zhao
>
> ACPI 6.0 introduces a new table STAO to list the devices which are used
> by Xen and can't be used by Dom0. On Xen virtual platforms, the physical
> UART is used by Xen. So here it hides UART from Dom0.
>
> CC: "R
On Fri, Mar 25, 2016 at 04:05:49PM +0800, Shannon Zhao wrote:
> From: Shannon Zhao
>
> ACPI 6.0 introduces a new table STAO to list the devices which are used
> by Xen and can't be used by Dom0. On Xen virtual platforms, the physical
> UART is used by Xen. So here it hides UART from Dom0.
>
> CC
flight 87263 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87263/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt 15 guest-saverestore.2 fail REGR. vs. 60684
build-amd6
Hi.
Previously I was using debian 8 to compile my xen 4.6 with hvm
stubdomain support. We recently switched to ubuntu servers, thus I
needed to change my compilation environment not to have lib dependency
issues.
My problem is: I get the staging 4.6 xen
(http://xenbits.xen.org/gitweb/?p=xen.git;a
> @@ -174,10 +174,61 @@ compat_bad_hypercall:
> /* %rbx: struct vcpu, interrupts disabled */
> ENTRY(compat_restore_all_guest)
> ASSERT_INTERRUPTS_DISABLED
> +.Lcr4_orig:
> +ASM_NOP8 /* testb $3,UREGS_cs(%rsp) */
> +ASM_NOP2 /* jpe .Lcr4_alt_end */
> +ASM_NOP8 /
On Thu, Mar 17, 2016 at 02:04:25AM -0600, Jan Beulich wrote:
> This is slightly more efficient than loading 64-bit quantities.
>
> Signed-off-by: Jan Beulich
> Reviewed-by: Andrew Cooper
Reviewed-by: Konrad Rzeszutek Wilk
___
Xen-devel mailing list
On Mon, Mar 21, 2016 at 11:25 AM, Jan Beulich wrote:
On 21.03.16 at 17:03, wrote:
>> On Mon, Mar 21, 2016 at 10:49 AM, Jan Beulich wrote:
>> On 21.03.16 at 16:18, wrote:
On Mon, Mar 21, 2016 at 8:35 AM, Jan Beulich wrote:
On 18.03.16 at 22:26, wrote:
>> --- a/xen/in
flight 87332 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87332/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 12
Wei Liu, on Fri 25 Mar 2016 13:09:07 +, wrote:
> CC Samuel
Thanks.
> On Wed, Mar 23, 2016 at 02:26:51PM -0700, Sarah Newman wrote:
> > 7c8f3483 introduced a break within a loop in netfront.c such that
> > cons and nr_consumed were no longer always being incremented. The
> > offset at cons wil
On Thu, Mar 17, 2016 at 10:14:22AM -0600, Jan Beulich wrote:
Something is off with your patch. This is 5/4 :-)
> Instead of addressing these fields via the base of the stack (which
> uniformly requires 4-byte displacements), address them from the end
> (which for everything other than guest_cpu_u
On Wed, Mar 02, 2016 at 07:16:40AM +, Hao, Xudong wrote:
> Hi,
> For Xen upstream master branch with commit 1949868d, After updating qemu-xen
> version from fcf6ac57 to 2ce1d30e, booting a pv-grub guest will fail.
> Attach the guest config file and Xen log.
Is this still an issue? I saw an Mi
On 03/25/2016 11:33 AM, Samuel Thibault wrote:
> Wei Liu, on Fri 25 Mar 2016 13:09:07 +, wrote:
>> CC Samuel
>
> Thanks.
>
>> On Wed, Mar 23, 2016 at 02:26:51PM -0700, Sarah Newman wrote:
>>> 7c8f3483 introduced a break within a loop in netfront.c such that
>>> cons and nr_consumed were no lo
On Wed, Mar 16, 2016 at 01:51:34PM -0700, Benjamin Sanda wrote:
> From: bensanda
>
> Modified to provide support for xentrace on the ARM platform. Added flask
> credential to allow dom0 dom_xen mapping and write access for trace buffers.
So .. what does that mean?
Is that something xentrace re
On Wed, Mar 16, 2016 at 01:51:39PM -0700, Benjamin Sanda wrote:
> From: bensanda
>
> Modified to provide support for xentrace on the ARM platform. Changed
> get_cycles() to return the core timestamp tick count for use by the trace
> buffer timestamping routines in xentrace.
>
> Signed-off-by:
Sarah Newman, on Fri 25 Mar 2016 12:19:23 -0700, wrote:
> I have no objections to backing out additional changes made in 7c8f3483,
? My patch doesn't really back out more than what you proposed actually.
> The patch tests OK with GNT_DEBUG enabled.
Good :)
Samuel
__
On Thu, Mar 24, 2016 at 11:48:18AM -0500, Doug Goldstein wrote:
> There are a number of debugging options for Xen so the idea is to have a
> menu to group them all together.
>
> Signed-off-by: Doug Goldstein
> ---
> This is more of an RFC than a merge request. If this seems reasonable I'll
> add
On Thu, Mar 24, 2016 at 11:48:19AM -0500, Doug Goldstein wrote:
> Convert the crash_debug option to Kconfig as CONFIG_CRASH_DEBUG. This
> was previously togglable on the command line so this adds a message for
> users enabling it from the command line to tell them to enable it from
> make menuconfi
On Thu, Mar 24, 2016 at 05:17:21PM +, George Dunlap wrote:
> Return failure when the command failed for more xl commands:
> - mem-set
> - cd-insert
>
> This makes xl more useful for scripting.
>
> In the case of mem-set, it means first cleaning up
> libxl_set_memory_target() to return useful
On 03/25/2016 12:32 PM, Samuel Thibault wrote:
> Sarah Newman, on Fri 25 Mar 2016 12:19:23 -0700, wrote:
>> I have no objections to backing out additional changes made in 7c8f3483,
>
> ? My patch doesn't really back out more than what you proposed actually.
It also backs out the #ifdef's on HAVE_
On Thu, Mar 24, 2016 at 01:57:58PM +0800, Quan Xu wrote:
Hey!
Thanks for the patch!
I see that you have __must_check..
But if you check the callchain:
iommu_flush_iec_[index|global] ->
__iommu_flush_iec->invalidate_sync-> queue_invalidate_wait
you will see that the callers of iommu_flush
On Thu, Mar 24, 2016 at 01:57:59PM +0800, Quan Xu wrote:
> If Device-TLB flush timed out, we would hide the target ATS
> device and crash the domain owning this ATS device. If impacted
> domain is hardware domain, just throw out a warning.
>
> The hidden device should be disallowed to be further a
On Thu, Mar 24, 2016 at 04:38:05PM +0100, Dario Faggioli wrote:
> On Thu, 2016-03-24 at 13:57 +0800, Quan Xu wrote:
> > If Device-TLB flush timed out, we would hide the target ATS
> > device and crash the domain owning this ATS device. If impacted
> > domain is hardware domain, just throw out a war
On Fri, Mar 25, 2016 at 12:28:46PM -0400, Konrad Rzeszutek Wilk wrote:
> On Fri, Mar 18, 2016 at 06:00:23PM +0100, Daniel Kiper wrote:
> > Add grub_relocator64_efi relocator. It will be used on EFI 64-bit platforms
> > when multiboot2 compatible image requests MULTIBOOT_TAG_TYPE_EFI_BS.
> > Reloca
On 3/25/16 2:42 PM, Konrad Rzeszutek Wilk wrote:
> On Thu, Mar 24, 2016 at 11:48:18AM -0500, Doug Goldstein wrote:
>> There are a number of debugging options for Xen so the idea is to have a
>> menu to group them all together.
>>
>> Signed-off-by: Doug Goldstein
>> ---
>> This is more of an RFC th
On 03/18/2016 05:48 AM, Fu Wei wrote:
Hi Jan,
On 18 March 2016 at 16:24, Jan Beulich wrote:
On 18.03.16 at 08:41, wrote:
--- a/xen/arch/arm/bootfdt.c
+++ b/xen/arch/arm/bootfdt.c
@@ -163,6 +163,36 @@ static void __init process_memory_node(const void *fdt,
int node,
}
}
+static bool
On 3/25/16 2:49 PM, Konrad Rzeszutek Wilk wrote:
> On Thu, Mar 24, 2016 at 11:48:19AM -0500, Doug Goldstein wrote:
>> Convert the crash_debug option to Kconfig as CONFIG_CRASH_DEBUG. This
>> was previously togglable on the command line so this adds a message for
>> users enabling it from the comman
On 26/03/2016 3:20 AM, Boris Ostrovsky wrote:
> On 03/25/2016 12:04 PM, Steven Haigh wrote:
>> It may not actually be the full logs. Once the system gets really upset,
>> you can't run anything - as such, grabbing anything from dmesg is not
>> possible.
>>
>> The logs provided above is all that get
Hi, there is a question.
I need to observe some Xen internals, so i thought debugging might be useful. i
tried using gdb, kdb, ... but they are complicated and not obvious. there is a
debugging
tool, GNU DDD, which may be suitable (although some simple) for that. but
unfortunately i can not fi
flight 87287 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87287/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-win7-amd64 12 guest-saverestore fail REGR. vs. 86491
test-amd64-i386-xl-q
flight 87360 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87360/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 15 guest-start/debian.repeat fail REGR. vs. 87332
Tests which di
flight 87376 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87376/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 12
flight 87299 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87299/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65543
test-amd64-i386-xl-qemuu-ovm
flight 87295 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87295/
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. 66399
build-i386-rumpuserxen
flight 87315 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/87315/
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
build-amd64-rumpuserx
99 matches
Mail list logo
