Linus,
Please git pull the following tag:
git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git for-linus-5.4-rc2-tag
xen: fixes and cleanups for 5.4-rc2
It contains the following patches:
- a fix in the Xen balloon driver avoiding hitting a BUG_ON() in some
cases, plus a follow-on
On 03.10.19 22:56, Andrew Cooper wrote:
Various pieces of Sphinx documentation improvements intended for inclusion
into Xen 4.13. Rendered results can be viewed at
https://andrewcoop-xen.readthedocs.io/en/docs-devel/index.html
with
On 03.10.19 18:12, Lars Kurth wrote:
Specifically
* xen.org to xenproject.org
* http to https
* Replaced pages where page has moved
(including on xen pages as well as external pages)
* Removed some URLs (e.g. downloads for Linux PV drivers)
Tested-by: Lars Kurth
Signed-off-by: Lars Kurth
On 03.10.19 15:30, Ian Jackson wrote:
Paul Durrant writes ("Re: [Xen-devel] [PATCH-for-4.13 v2 0/2] libxl: fix assertion
failure"):
On Wed, 2 Oct 2019 at 17:04, Ian Jackson wrote:
I am continuing to look at the defaulting and config management here
with a view to getting rid of some of the
On 03.10.19 16:25, Andrew Cooper wrote:
The names in retpoline_safe() are copied from should_use_eager_fpu(). The
names in mds_calculations() come partly from Linux's intel-family.h, and
partly from conversations with Intel.
Signed-off-by: Andrew Cooper
Release-acked-by: Juergen Gross
On 03.10.19 12:47, Andrew Cooper wrote:
Linux has started using RDTSCP as of v5.1. This has highlighted a bug in Xen,
where virtual vmexit simply gives up.
(XEN) d1v1 Unhandled nested vmexit: reason 51
(XEN) domain_crash called from vvmx.c:2671
(XEN) Domain 1 (vcpu#1) crashed on
On 02.10.19 19:02, Julien Grall wrote:
+Juergen
Hi,
On 10/1/19 4:16 PM, Oleksandr wrote:
On 30.09.19 23:56, Stefano Stabellini wrote:
Hi Stefano
Some Device Trees may expose both legacy SMMU and generic IOMMU bindings
together. However, the SMMU driver in Xen is only supporting the legacy
On 03.10.19 20:12, Boris Ostrovsky wrote:
Currently execution of panic() continues until Xen's panic notifier
(xen_panic_event()) is called at which point we make a hypercall that
never returns.
This means that any notifier that is supposed to be called later as
well as significant part of
On 03.10.19 11:47, Sergey Dyasli wrote:
Hi Juergen,
Looks like we've hit the first Xen crash with core scheduling patches applied.
The log is below. From my analysis it seems that CSCHED_PCPU is NULL.
I suspect this is connected to commit bb128adb
("sched: populate cpupool0 only after all
flight 142221 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142221/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt 12 guest-start fail REGR. vs. 141822
I actually adding Juergen.
On Thu, 3 Oct 2019, Stefano Stabellini wrote:
> Hi all,
>
> This small patch series adds device assignment support to Dom0less.
> The last patch is the documentation.
>
> Cheers,
>
> Stefano
>
>
> The following changes since commit
We don't have a clear way to know how many virtual SPIs we need for the
dom0-less domains. Introduce a new option under xen,domain to specify
the number of SPIs to allocate for a domain.
The property is optional. When absent, we'll use the physical number of
GIC lines for dom0-less domains, or
Read the dtb fragment corresponding to a passthrough device from memory
at the location referred to by the "multiboot,device-tree" compatible
node.
Add a new field named dtb_bootmodule to struct kernel_info to keep track
of the dtb fragment location.
Copy the fragment to the guest dtb (only
Instead of always hard-coding the GIC phandle (GUEST_PHANDLE_GIC), store
it in a variable under kinfo. This way it can be dynamically chosen per
domain. Remove the fdt pointer argument to the make_*_domU_node
functions and oass a struct kernel_info * instead. The fdt pointer can
be accessed from
Detect "multiboot,device-tree" compatible nodes. Add them to the bootmod
array as BOOTMOD_GUEST_DTB. In kernel_probe, find the right
BOOTMOD_GUEST_DTB and store a pointer to it in dtb_bootmodule.
Signed-off-by: Stefano Stabellini
Acked-by: Julien Grall
---
Changes in v4:
- use uint32_t
-
Move the interrupt handling code out of handle_device to a new function
so that it can be reused for dom0less VMs (it will be used in later
patches).
Signed-off-by: Stefano Stabellini
Acked-by: Julien Grall
---
Changes in v4:
- rename handle_interrupts to handle_device_interrupts
- improve
They'll be used in later patches.
Signed-off-by: Stefano Stabellini
Acked-by: Julien Grall
---
Changes in v5:
- move declarations to xen/include/asm-arm/setup.h
Changes in v4:
- new patch
---
xen/arch/arm/bootfdt.c | 8
xen/include/asm-arm/setup.h | 6 ++
2 files changed,
Add info about the SPI used for the virtual pl011.
Signed-off-by: Stefano Stabellini
---
Changes in v9:
- clarify statement
Changes in v8:
- remove sentence about xen,path being optional
Changes in v7:
- add xen,force-assign-without-iommu
- clarify xen,reg and xen,path go together
- remove
Hi all,
This small patch series adds device assignment support to Dom0less.
The last patch is the documentation.
Cheers,
Stefano
The following changes since commit 7a4e674905b3cbbe48e81c3222361a7f3579:
xen/sched: move struct task_slice into struct sched_unit (2019-09-27 16:03:31
Scan the user provided dtb fragment at boot. For each device node, map
memory to guests, and route interrupts and setup the iommu.
The memory region to remap is specified by the "xen,reg" property.
The iommu is setup by passing the node of the device to assign on the
host device tree. The path
Both upstream [1] and downstream [2] Linux kernels use "brcm,bcm2711"
as the compatible string for Raspberry Pi 4. Add this string to our
platform compatible list.
The brcm,bcm2838 convention is abandoned. Remove it.
Rename the variables within the file to a rpi4_* prefix since the file
is meant
On Tuesday, September 17, 2019 7:05 AM, Julien Grall
wrote:
>Hi Stewart,
>
>On 9/14/19 2:22 AM, Stewart Hildebrand wrote:
>> On Friday, September 13, 2019 5:42 PM, Julien Grall
>> wrote:
>>> 2) Is the patch [1] merged? If so, which version?
>>
>> No.
>
>I would rather wait until the patch
On Thu, Oct 03, 2019 at 10:20:36PM +0100, Julien Grall wrote:
> Hi Brian,
>
> On 10/3/19 9:24 PM, Brian Woods wrote:
> >On Thu, Oct 03, 2019 at 07:23:23PM +, Julien Grall wrote:
> >There's a WARN_ON() between the two debug printks calls I shared above.
>
> Looking at the log, the MFN seems
flight 142220 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142220/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail REGR. vs.
140282
Hi Brian,
On 10/3/19 9:24 PM, Brian Woods wrote:
On Thu, Oct 03, 2019 at 07:23:23PM +, Julien Grall wrote:
There's a WARN_ON() between the two debug printks calls I shared above.
Looking at the log, the MFN seems to correspond to the one right after
Xen (0140 -
On 25/09/2019 10:27, Kateryna Razumova wrote:
> Hello xen,
> I would like to participate in Outreachy. I was registered on the site
> few days ago, filled some quite a big form but still can't see tasks'
> descriptions.
> Since, I like C programming I would like to know more about "Introduce
>
Put together an introduction page for the Sphinx/RST docs, along with a
glossary which will accumulate over time.
Signed-off-by: Andrew Cooper
---
CC: Lars Kurth
CC: George Dunlap
CC: Ian Jackson
CC: Jan Beulich
CC: Konrad Rzeszutek Wilk
CC: Stefano Stabellini
CC: Tim Deegan
CC: Wei Liu
This identifies various of areas technical debt, which either need to be, or
are being worked on, along with enough clarifying details for people to
follow.
Signed-off-by: Andrew Cooper
---
CC: Lars Kurth
CC: George Dunlap
CC: Ian Jackson
CC: Jan Beulich
CC: Konrad Rzeszutek Wilk
CC:
Creative Commons is a more common license than GPL for documentation purposes.
Switch to using CC-BY-4.0 to explicitly permit re-purposing and remixing of
the content.
Signed-off-by: Andrew Cooper
---
CC: Lars Kurth
CC: George Dunlap
CC: Ian Jackson
CC: Jan Beulich
CC: Konrad Rzeszutek Wilk
Various pieces of Sphinx documentation improvements intended for inclusion
into Xen 4.13. Rendered results can be viewed at
https://andrewcoop-xen.readthedocs.io/en/docs-devel/index.html
with
https://andrewcoop-xen.readthedocs.io/en/docs-devel/admin-guide/introduction.html
Sphinx, its linters, and RST modes in common editors, expect 3 spaces of
indentation. Some bits already conform to this expectation. Update the
rest to match.
Signed-off-by: Andrew Cooper
---
CC: Lars Kurth
CC: George Dunlap
CC: Ian Jackson
CC: Jan Beulich
CC: Konrad Rzeszutek Wilk
CC:
On Thu, Oct 03, 2019 at 07:23:23PM +, Julien Grall wrote:
> Hi,
>
> On 03/10/2019 19:15, Brian Woods wrote:
> > On Thu, Oct 03, 2019 at 06:08:45PM +0100, Julien Grall wrote:
> > (XEN) BW_DEBUG: .6 count_info=0x
> > (XEN) Domain heap initialised
> > (XEN) BW_DEBUG: 01
Hi,
On 03/10/2019 19:15, Brian Woods wrote:
> On Thu, Oct 03, 2019 at 06:08:45PM +0100, Julien Grall wrote:
> (XEN) BW_DEBUG: .6 count_info=0x
> (XEN) Domain heap initialised
> (XEN) BW_DEBUG: 01 count_info=0x0180
>
> Those debug messages sandwich end_boot_allocator()
On Thu, Oct 03, 2019 at 06:08:45PM +0100, Julien Grall wrote:
> Hi,
>
> On 03/10/2019 00:20, Brian Woods wrote:
> >On Wed, Oct 02, 2019 at 02:22:49PM -0700, Brian Woods wrote:
> >>That's odd. I know I copied your and Stefano's email addresses from the
> >>MAINTAINERS file but under my sent
Currently execution of panic() continues until Xen's panic notifier
(xen_panic_event()) is called at which point we make a hypercall that
never returns.
This means that any notifier that is supposed to be called later as
well as significant part of panic() code (such as pstore writes from
Hi,
On 03/10/2019 18:48, Stefano Stabellini wrote:
On Thu, 3 Oct 2019, Julien Grall wrote:
Hi Stefano,
On 02/10/2019 23:26, Stefano Stabellini wrote:
On Wed, 2 Oct 2019, Julien Grall wrote:
That was my reflection on whether it would be a good idea or a bad idea
to have a SERROR check on the
On Thu, 3 Oct 2019, Julien Grall wrote:
> Hi Stefano,
>
> On 02/10/2019 23:26, Stefano Stabellini wrote:
> > On Wed, 2 Oct 2019, Julien Grall wrote:
> > That was my reflection on whether it would be a good idea or a bad idea
> > to have a SERROR check on the fiq hypervisor entries. Not
On Thu, 3 Oct 2019, Julien Grall wrote:
> Hi Stefano,
>
> On 03/10/2019 02:35, Stefano Stabellini wrote:
> > Add info about the SPI used for the virtual pl011.
> >
> > Signed-off-by: Stefano Stabellini
> >
> > ---
> > Changes in v8:
> > - remove sentence about xen,path being optional
> >
> >
On Thu, 3 Oct 2019, Julien Grall wrote:
> Hi Stefano,
>
> On 03/10/2019 02:35, Stefano Stabellini wrote:
> > Scan the user provided dtb fragment at boot. For each device node, map
> > memory to guests, and route interrupts and setup the iommu.
> >
> > The memory region to remap is specified by
On Thu, 3 Oct 2019, Julien Grall wrote:
> Hi Stefano,
>
> A couple of comments below, mostly because I wasn't clear enough on the
> previous version. I am not sure if it is worth resending the series, maybe
> just resending this one would be sufficient?
>
> On 03/10/2019 02:35, Stefano
Hi,
On 03/10/2019 00:20, Brian Woods wrote:
On Wed, Oct 02, 2019 at 02:22:49PM -0700, Brian Woods wrote:
On Wed, Oct 02, 2019 at 08:59:28PM +0100, Julien Grall wrote:
Hi,
On 10/2/19 7:56 PM, Brian Woods wrote:
Hmmm, the first e-mail didn't land in my inbox directly (I have a filter
send to
Specifically
* xen.org to xenproject.org
* http to https
* Replaced pages where page has moved
(including on xen pages as well as external pages)
* Removed some URLs (e.g. downloads for Linux PV drivers)
Tested-by: Lars Kurth
Signed-off-by: Lars Kurth
---
Hi,
On 03/10/2019 16:55, Volodymyr Babchuk wrote:
Julien Grall writes:
Hi Stefano,
On 10/2/19 2:05 AM, Stefano Stabellini wrote:
On Tue, 24 Sep 2019, Julien Grall wrote:
The documentation is using a mix of ARM (old) and Arm (new). To stay
consistent, use only the new name.
Thank you for
flight 142228 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142228/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
Hi Julien,
Julien Grall writes:
> Hi Stefano,
>
> On 10/2/19 2:05 AM, Stefano Stabellini wrote:
>> On Tue, 24 Sep 2019, Julien Grall wrote:
>>> The documentation is using a mix of ARM (old) and Arm (new). To stay
>>> consistent, use only the new name.
>>
>> Thank you for the patch, it must have
On Thu, Oct 03, 2019 at 02:30:31PM +0100, Ian Jackson wrote:
> Paul Durrant writes ("Re: [Xen-devel] [PATCH-for-4.13 v2 0/2] libxl: fix
> assertion failure"):
> > On Wed, 2 Oct 2019 at 17:04, Ian Jackson wrote:
> > > I am continuing to look at the defaulting and config management here
> > > with
The names in retpoline_safe() are copied from should_use_eager_fpu(). The
names in mds_calculations() come partly from Linux's intel-family.h, and
partly from conversations with Intel.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Wei Liu
CC: Roger Pau Monné
CC: Juergen Gross
Only
On Wed, Oct 02, 2019 at 06:19:44PM +0200, Kateryna Razumova wrote:
> Dear Liu,
>
> oh, I thought that xen participates in Outreachy in order to get new
> contributors via easing the entrance process.
> But it seems that a potential contributor to xen should already have some
> knowledge of xen
Igor Druzhinin (2):
efi/boot: fix set_color function
efi/boot: make sure chosen mode is set even if firmware tell it is
xen/common/efi/boot.c | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
--
2.7.4
___
Xen-devel mailing list
- 0 is a possible and allowed value for a color mask accroding to
UEFI Spec 2.6 (11.9) especially for reserved mask
- add missing pointer dereference
Without these changes non-TrueColor modes won't work which will cause
GOP init to fail - observed while trying to boot EFI Xen with Cirrus VGA.
If a bootloader is using native driver instead of EFI GOP it might
reset graphics mode to be different from what firmware thinks it
currently is. Set chosen mode unconditionally to fix this possible
misalignment.
Observed with EFI GRUB2 compiled with all possible video drivers where
native
Paul Durrant writes ("Re: [Xen-devel] [PATCH-for-4.13 v2 0/2] libxl: fix
assertion failure"):
> On Wed, 2 Oct 2019 at 17:04, Ian Jackson wrote:
> > I am continuing to look at the defaulting and config management here
> > with a view to getting rid of some of the duplicated code and moving
> > it
flight 142217 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142217/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm
On 01.10.19 22:07, Julien Grall wrote:
Hi Oleksandr,
Hi Julien
On 10/1/19 5:07 PM, Oleksandr wrote:
On 01.10.19 18:36, Julien Grall wrote:
On 01/10/2019 16:25, Oleksandr wrote:
On 01.10.19 18:04, Julien Grall wrote:
> 1. Giving the IOMMU to Dom0 is a bad idea.
Please to try expand
Hi Stefano,
On 02/10/2019 23:26, Stefano Stabellini wrote:
On Wed, 2 Oct 2019, Julien Grall wrote:
Clang will throw an error if a function is unused unless you tell
to ignore it. This can be done using __maybe_unused.
While modifying the declaration, update it to match prototype of similar
Linux has started using RDTSCP as of v5.1. This has highlighted a bug in Xen,
where virtual vmexit simply gives up.
(XEN) d1v1 Unhandled nested vmexit: reason 51
(XEN) domain_crash called from vvmx.c:2671
(XEN) Domain 1 (vcpu#1) crashed on cpu#2:
Handle RDTSCP in the virtual vmexit hander
On 02/10/2019 23:26, Stefano Stabellini wrote:
On Wed, 2 Oct 2019, Julien Grall wrote:
Clang will throw an error if a function is unused unless you tell
to ignore it. This can be done using __maybe_unused.
While modifying the declaration, update it to match prototype of similar
functions
On Wed, 2019-10-02 at 15:52 +0100, Julien Grall wrote:
> On 10/2/19 3:43 PM, Juergen Gross wrote:
> > vcpu_wake() and vcpu_sleep() need to be made core scheduling aware:
> > [...]
> > Signed-off-by: Juergen Gross
> > Reviewed-by: Dario Faggioli
>
> Acked-by: Julien Grall
>
> Dario, can you
Hi Stefano,
On 02/10/2019 23:26, Stefano Stabellini wrote:
On Wed, 2 Oct 2019, Julien Grall wrote:
That was my reflection on whether it would be a good idea or a bad idea
to have a SERROR check on the fiq hypervisor entries. Not necessarely in
this patch. Probably not in this patch.
If you
Hi Stefano,
On 03/10/2019 02:35, Stefano Stabellini wrote:
Add info about the SPI used for the virtual pl011.
Signed-off-by: Stefano Stabellini
---
Changes in v8:
- remove sentence about xen,path being optional
Changes in v7:
- add xen,force-assign-without-iommu
- clarify xen,reg and
Hi Stefano,
On 03/10/2019 02:35, Stefano Stabellini wrote:
Scan the user provided dtb fragment at boot. For each device node, map
memory to guests, and route interrupts and setup the iommu.
The memory region to remap is specified by the "xen,reg" property.
The iommu is setup by passing the
In
other_revision_job_suffix: Take and pass referring runvar name
we updated main_revision_job_cond to pass a dummy 'x' for the new
parameter. But the parameter is a sql expression, not a value,
and so an extra pair of quotes are needed.
This error broke sg-check-tested and this fix fixes it.
Hi Juergen,
Looks like we've hit the first Xen crash with core scheduling patches applied.
The log is below. From my analysis it seems that CSCHED_PCPU is NULL.
I suspect this is connected to commit bb128adb
("sched: populate cpupool0 only after all cpus are up")
Could you take a look,
On 01.10.19 02:30, Stefano Stabellini wrote:
Hi Stefano
+
+/* If xen_force, we ignore IOMMU failures. */
+res = iommu_add_dt_device(node);
+if ( res < 0 )
+return xen_force ? 0 : -EINVAL;
Any specific reason to return -EINVAL if not forcing (why don't return
res)?
+
Hi Stefano,
On 03/10/2019 02:35, Stefano Stabellini wrote:
Add info about the SPI used for the virtual pl011.
Signed-off-by: Stefano Stabellini
Acked-by: Julien Grall
Cheers,
--
Julien Grall
___
Xen-devel mailing list
Hi Stefano,
A couple of comments below, mostly because I wasn't clear enough on the previous
version. I am not sure if it is worth resending the series, maybe just resending
this one would be sufficient?
On 03/10/2019 02:35, Stefano Stabellini wrote:
diff --git a/xen/arch/arm/domain_build.c
Hi Stefano,
On 02/10/2019 23:43, Stefano Stabellini wrote:
On Wed, 2 Oct 2019, Julien Grall wrote:
+if ( !found )
+{
+res = fdt_property(fdt, name, prop->data,
fdt32_to_cpu(prop->len));
+if ( res )
+return res;
+}
+}
+
+/*
Hi Stefano,
On 02/10/2019 23:48, Stefano Stabellini wrote:
On Wed, 2 Oct 2019, Stefano Stabellini wrote:
On Wed, 2 Oct 2019, Julien Grall wrote:
Hi Stefano,
On 10/1/19 12:30 AM, Stefano Stabellini wrote:
Scan the user provided dtb fragment at boot. For each device node, map
memory to
Hi Julien
Just to confirm - with this series, we are able to run xen master
(4.13-unstable) on R-Car H3:
* built using clang
* built using clang-based arm compiler (with further modifications
needed for armlink)
Note we didn't perform full testing, just start xen on its own.
-- Artem
On
branch xen-unstable
xenbranch xen-unstable
job test-amd64-i386-qemuu-rhel6hvm-intel
testid xen-boot
Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf
On 02.10.19 20:00, Julien Grall wrote:
Hi all,
After this series, I am able to build Xen on Arm64 with clang 7.0. There
are still some issues when building Xen on Arm32 and also using lld.
Cross-compilation is left outside for now, but this is still a good start
for clang (and armclang).
71 matches
Mail list logo
