On 23.07.2021 01:36, Stefano Stabellini wrote:
> --- a/xen/drivers/passthrough/device_tree.c
> +++ b/xen/drivers/passthrough/device_tree.c
> @@ -140,8 +140,13 @@ int iommu_add_dt_device(struct dt_device_node *np)
> if ( !ops )
> return -EINVAL;
>
> +/*
> + * Some Device Tree
On 21.07.2021 18:53, Paul Durrant wrote:
> On 21/07/2021 16:58, Jan Beulich wrote:
>> Paul,
>>
>> the description of this says
>>
>> "At the moment iommu_map() and iommu_unmap() take a page order rather than a
>> count, whereas iommu_iotlb_flush() takes a page count rather than an order.
>> Thi
flight 163922 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163922/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-debianhvm-amd64 12 debian-hvm-install fail REGR. vs.
163321
test-amd64
This adds an option to the xl domain configuration syntax for specifying
a build-time XSM security label for device-model stubdomains separate from
the run-time label specified by 'device_model_stubdomain_seclabel'. Fields
are also added to the 'libxl_domain_build_info' struct to contain the new
in
flight 163917 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163917/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 162359
test-amd64-amd64-xl-qemuu
flight 163916 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163916/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-intel 7 xen-install fail REGR. vs. 152332
test-amd64-i386-xl-
From: Brian Woods
Restructure some of the code and add supporting functions for adding
generic device tree (DT) binding support. This will allow for using
current Linux device trees with just modifying the chosen field to
enable Xen.
Signed-off-by: Brian Woods
Signed-off-by: Stefano Stabellini
From: Brian Woods
For the legacy path, arm_smmu_dt_add_device_legacy is called by
register_smmu_master scanning mmu-masters (a fwspec entry is also
created.) For the generic path, arm_smmu_dt_add_device_generic gets
called instead. Then, arm_smmu_dt_add_device_generic calls
arm_smmu_dt_add_device
From: Brian Woods
Modify the smmu driver so that it uses the iommu_fwspec helper
functions. This means both ARM IOMMU drivers will both use the
iommu_fwspec helper functions, making enabling generic device tree
bindings in the SMMU driver much cleaner.
Signed-off-by: Brian Woods
Signed-off-by:
If both legacy IOMMU bindings and generic bindings are present,
iommu_add_dt_device can be called twice. Do not return error in that
case, that way there is no need to check for -EEXIST at the call sites.
Remove the one existing -EEXIT check, now unneeded.
Signed-off-by: Stefano Stabellini
---
Ch
Hi all,
This series introduces support for the generic SMMU bindings to
xen/drivers/passthrough/arm/smmu.c.
Cheers,
Stefano
Brian Woods (3):
arm,smmu: switch to using iommu_fwspec functions
arm,smmu: restructure code in preparation to new bindings support
arm,smmu: add support
On Thu, 22 Jul 2021, Julien Grall wrote:
> Hi Stefano,
>
> On 17/07/2021 00:59, Stefano Stabellini wrote:
> > diff --git a/xen/drivers/passthrough/device_tree.c
> > b/xen/drivers/passthrough/device_tree.c
> > index 999b831d90..911f82a561 100644
> > --- a/xen/drivers/passthrough/device_tree.c
> > +
flight 163912 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163912/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-debianhvm-amd64 12 debian-hvm-install fail REGR. vs.
163321
test-amd64
branch xen-unstable
xenbranch xen-unstable
job test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict
testid debian-hvm-install
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tre
On Thu, 22 Jul 2021, Julien Grall wrote:
> > You can go and edit 76085aff29f585139a37a10ea0a7daa63f70872c to change
> > from 4K to any multiple of 4K, e.g. 8K, 12K, 16K, 20K. They should all
> > work the same.
> >
> > Looking at the boot logs on pastebin I noticed that Xen is not loaded at
> > a 2
On Sat, Jul 3, 2021 at 8:18 PM Julien Grall wrote:
>
>
> On 18/06/2021 13:19, Oleksandr Andrushchenko wrote:
> > Hi, all!
>
> Hi,
>
Hello Julien, all.
[sorry for the possible format issues]
I am sorry to jump into the conversation too late.
>
> Sorry for the late reply.
>
> > What do we need
flight 163907 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163907/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 162359
test-amd64-amd64-xl-qemuu
flight 163896 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163896/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-intel 7 xen-install fail REGR. vs. 152332
test-amd64-i386-xl-
This adds an option to the xl domain configuration file syntax for specifying
a kernel command line for device-model stubdomains. It is intended for use with
Linux-based stubdomains.
Signed-off-by: Scott Davis
Reviewed-by: Jason Andryuk
---
Changes in v2:
- add #define LIBXL_HAVE_BUILDINFO_DEVIC
flight 163890 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163890/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict 12 debian-hvm-install
fail REGR. vs. 163321
Am Tue, 20 Jul 2021 16:41:23 +0100
schrieb Anthony PERARD :
> Anyway Olaf, I've deleted the repo, feel free to try again, or let me
> now if you want me to set things up.
I'm sure if I create a fresh repo 'xen.git' in a "group" 'olafhering', I will
be unable to push there because it is empty.
No
flight 163888 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163888/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-rtds 20 guest-localmigrate/x10 fail in 163877 pass in
163888
test-amd64-amd64-examine
On 22/07/21 16:12, Anthony PERARD via wrote:
Reviewed-by: Anthony PERARD
I can't find a different way to set a default "accelerator" to a
machine, so this patch seems necessary.
I agree, and I'll be sending a pull request shortly.
Paolo
On Mon, Jul 12, 2021 at 10:15:52PM -0400, Jason Andryuk wrote:
> qemu can't start a xen vm after commit d8fb7d0969d5
> "vl: switch -M parsing to keyval" with:
>
> $ ./qemu-system-i386 -M xenfv
> Unexpected error in object_property_find_err() at ../qom/object.c:1298:
> qemu-system-i386: Property 'x
Hi Stefano,
On 17/07/2021 00:59, Stefano Stabellini wrote:
From: Brian Woods
For the legacy path, arm_smmu_dt_add_device_legacy is called by
register_smmu_master scanning mmu-masters (a fwspec entry is also
created.) For the generic path, arm_smmu_dt_add_device_generic gets
called instead. The
Hi Stefano,
On 17/07/2021 00:59, Stefano Stabellini wrote:
diff --git a/xen/drivers/passthrough/device_tree.c
b/xen/drivers/passthrough/device_tree.c
index 999b831d90..911f82a561 100644
--- a/xen/drivers/passthrough/device_tree.c
+++ b/xen/drivers/passthrough/device_tree.c
@@ -140,8 +140,12 @@
Hello Julien and Stefano,
This is actually a good point. There are two other possible issues:
1) The kernel and the hypervisor may overlaps each other.
2) The size of the kernel is not correctly provided.
I remember hitting such issues in the past and they will lead to weird
issues.
In f
flight 163889 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163889/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ovmf-amd64 12 debian-hvm-install fail REGR. vs. 162359
test-amd64-amd64-xl-qemuu
flight 163893 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/163893/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-amd64-libvirt
Hi Stefano and Oleksii,
On 22/07/2021 03:12, Stefano Stabellini wrote:
On Wed, 21 Jul 2021, Oleksii Moisieiev wrote:
Please see my answers below.
___
From: J
I suspect it is commit 40726f16a8d7 ("ld script expression parsing")
which broke the hypervisor build, by no longer accepting section names
with a dash in them inside ADDR() (and perhaps other script directives
expecting just a section name, not an expression): .note.gnu.build-id
is such a section.
On Wed, Jul 21, 2021 at 12:09:41PM +0200, Greg Kroah-Hartman wrote:
> On Tue, Jul 13, 2021 at 09:35:17PM +0200, Uwe Kleine-König wrote:
> > Hello,
> >
> > this is v4 of the final patch set for my effort to make struct
> > bus_type::remove return void.
> >
> > The first four patches contain cleanu
32 matches
Mail list logo
