On Sun, 29 Sep 2019, Julien Grall wrote:
> Hi,
>
> On 9/27/19 12:11 AM, 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
Add info about the SPI used for the virtual pl011.
Signed-off-by: Stefano Stabellini
Acked-by: Julien Grall
---
Changes in v6:
- fix nr_spis description
- add ack
Changes in v5:
- improve wording
Changes in v4:
- fix spelling
- add "multiboot,module"
- improve commit message
- improve doc
-
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
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,
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
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
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
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
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
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
-
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
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,
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
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
On Sun, 29 Sep 2019, Julien Grall wrote:
> Clang 8.0 will fail to build domain_build.c on Arm32 because of the
> following error:
>
> domain_build.c:448:21: error: implicit conversion from 'unsigned long long'
> to 'unsigned long' changes value from 1090921693184 to 0
>
On Sun, 29 Sep 2019, Julien Grall wrote:
> Signed-off-by: Julien Grall
Acked-by: Stefano Stabellini
> ---
> xen/arch/arm/domain_build.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c
> index
On Mon, Sep 30, 2019 at 3:19 AM Andrew Cooper wrote:
>
> On 28/09/2019 04:07, Roman Shaposhnik wrote:
> > On Thu, Sep 26, 2019 at 12:44 AM Jan Beulich wrote:
> >> On 26.09.2019 00:31, Roman Shaposhnik wrote:
> >>> Jan, Roger, thank you so much for the initial ideas. I tried a few of
> >>> those
flight 142072 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142072/
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. 142054
Tests which
When qemu is running in stubdomain, handling "pci-ins" command will fail
if pcifront is not initialized already. Fix this by sending such command
only after confirming that pciback/front is running.
Signed-off-by: Marek Marczykowski-Górecki
Reviewed-by: Anthony PERARD
---
Changes in v2:
- Fixed
On 01.10.19 02:57, Stefano Stabellini wrote:
On Mon, 30 Sep 2019, Andrew Cooper wrote:
On 30/09/2019 19:44, Julien Grall wrote:
GAS 2.25.0 throws multiple errors when building arm32/head.S:
arm32/head.S: Assembler messages:
arm32/head.S:452: Error: invalid constant (f7f) after fixup
flight 142022 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142022/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-examine11 examine-serial/bootloader fail REGR. vs. 141979
Tests which did not
Btw, forgot to attach the patch with maxcpus=2 -- interestingly enough
Xen seems to hang much further down than before (basically after
attempting to build out Dom0)
On Mon, Sep 30, 2019 at 3:16 PM Roman Shaposhnik wrote:
>
> On Mon, Sep 30, 2019 at 2:56 AM Jan Beulich wrote:
> >
> > On
On Sun, 29 Sep 2019, Julien Grall wrote:
> Hi,
>
> Sorry, I am picking up this series again.
>
> On 4/18/19 7:03 PM, Stefano Stabellini wrote:
> > On Wed, 17 Apr 2019, Julien Grall wrote:
> > > Hi,
> > >
> > > On 4/17/19 9:45 PM, Stefano Stabellini wrote:
> > > > On Wed, 27 Mar 2019, Julien
On 30/09/2019 23:01, Roman Shaposhnik wrote:
> On Mon, Sep 30, 2019 at 3:19 AM Andrew Cooper
> wrote:
>> On 28/09/2019 04:07, Roman Shaposhnik wrote:
>>> On Thu, Sep 26, 2019 at 12:44 AM Jan Beulich wrote:
On 26.09.2019 00:31, Roman Shaposhnik wrote:
> Jan, Roger, thank you so much for
On Mon, Sep 30, 2019 at 2:56 AM Jan Beulich wrote:
>
> On 28.09.2019 05:07, Roman Shaposhnik wrote:
> > On Thu, Sep 26, 2019 at 12:44 AM Jan Beulich wrote:
> >>
> >> On 26.09.2019 00:31, Roman Shaposhnik wrote:
> >>> Jan, Roger, thank you so much for the initial ideas. I tried a few of
> >>>
flight 142019 linux-4.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142019/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvshim 20 guest-start/debian.repeat fail REGR. vs. 139698
Tests which are
On 30/09/2019 21:17, Julien Grall wrote:
> Hi,
>
> On 9/30/19 7:24 PM, Andrew Cooper wrote:
>> The code generation for barrier_nospec_true() is not correct. We are
>> taking a
>> perf it from the added fences, but not gaining any speculative safety.
>
> s/it/hit/?
Yes.
>
>>
>> This is caused by
On Mon, 30 Sep 2019, Andrew Cooper wrote:
> On 30/09/2019 19:44, Julien Grall wrote:
> > GAS 2.25.0 throws multiple errors when building arm32/head.S:
> >
> > arm32/head.S: Assembler messages:
> > arm32/head.S:452: Error: invalid constant (f7f) after fixup
> > arm32/head.S:453: Error: invalid
flight 142013 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142013/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-i386 11 guest-startfail REGR. vs. 140282
flight 142054 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142054/
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
flight 142011 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142011/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadowbroken
test-amd64-amd64-libvirt
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
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
Add info about the SPI used for the virtual pl011.
Signed-off-by: Stefano Stabellini
---
Changes in v7:
- add xen,force-assign-without-iommu
- clarify xen,reg and xen,path go together
- remove acked-by due to changes
Changes in v6:
- fix nr_spis description
- add ack
Changes in v5:
- improve
On Mon, 30 Sep 2019, Stefano Stabellini wrote:
> On Sun, 29 Sep 2019, Julien Grall wrote:
> > Hi,
> >
> > Sorry, I am picking up this series again.
> >
> > On 4/18/19 7:03 PM, Stefano Stabellini wrote:
> > > On Wed, 17 Apr 2019, Julien Grall wrote:
> > > > Hi,
> > > >
> > > > On 4/17/19 9:45
On Mon, 30 Sep 2019, Julien Grall wrote:
> Hi Oleksandr,
>
> On 30/09/2019 10:34, Oleksandr wrote:
> > On 28.09.19 02:28, Stefano Stabellini wrote:
> > > > > I have to admit that I don't know about dom0less feature enough ...
> > > > >
> > > > >
> > > > > But, shouldn't we check if the device
On Sun, 29 Sep 2019, Julien Grall wrote:
> Signed-off-by: Julien Grall
Acked-by: Stefano Stabellini
> ---
> xen/arch/arm/p2m.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/xen/arch/arm/p2m.c b/xen/arch/arm/p2m.c
> index 5ff6ce15f6..4a429dc1be 100644
> ---
Inspired by Linux commit c49a0a80137c7ca7d6ced4c812c9e07a949f6f24:
There have been reports of RDRAND issues after resuming from suspend on
some AMD family 15h and family 16h systems. This issue stems from a BIOS
not performing the proper steps during resume to ensure RDRAND continues
On Sat, Sep 28, 2019 at 04:20:36PM +0200, Marek Marczykowski-Górecki wrote:
> When qemu is running in stubdomain, handling "pci-ins" command will fail
> if pcifront is not initialized already. Fix this by sending such command
> only after confirming that pciback/front is running.
>
>
hvm_select_ioreq_server and hvm_send_ioreq where both using
hvm_ioreq_server directly, switch to use ioservid_t in order to select
and forward ioreqs.
This is a preparatory change, since future patches will use the ioreq
server id in order to differentiate between internal and external
ioreq
Do not forward accesses to cf8 to external emulators, decoding of PCI
accesses is handled by Xen, and emulators can request handling of
config space accesses of devices using the provided ioreq interface.
Fully terminate cf8 accesses at the hypervisor level, by improving the
existing
Such internal servers are implemented by a single function that handles
ioreqs inside the hypervisor.
The motivation behind this change is to switch vPCI to become an
internal ioreq server, so that accesses to the PCI config space can be
multiplexed between devices handled by vPCI and devices
...and switch vPCI to use this infrastructure for long running
physmap modification operations.
This allows to get rid of the vPCI specific modifications done to
handle_hvm_io_completion and allows generalizing the support for
long-running operations to other internal ioreq servers. Such support
Add support for internal ioreq servers to initialization and
deinitialization routines, prevent some functions from being executed
against internal ioreq servers and add guards to only allow internal
callers to modify internal ioreq servers. External callers (ie: from
hypercalls) are only allowed
Provide a routine to register the handler for an internal ioreq
server.
Signed-off-by: Roger Pau Monné
---
Changes since v2:
- s/hvm_add_ioreq_handler/hvm_set_ioreq_handler.
- Do not goto the out label if ioreq is not internal.
Changes since v1:
- Allow to provide an opaque data parameter to
Switch vPCI to become an internal ioreq server, and hence drop all the
vPCI specific decoding and trapping to PCI IO ports and MMCFG regions.
This allows to unify the vPCI code with the ioreq infrastructure,
opening the door for domains having PCI accesses handled by vPCI and
other ioreq servers
Internal ioreq servers are plain function handlers implemented inside
of the hypervisor. Note that most fields used by current (external)
ioreq servers are not needed for internal ones, and hence have been
placed inside of a struct and packed in an union together with the
only internal specific
Place the code that converts a PIO/COPY ioreq into a PCI_CONFIG one
into a separate function, and adjust the code to make use of this
newly introduced function.
No functional change intended.
Signed-off-by: Roger Pau Monné
---
Changes since v1:
- New in this version.
---
Pick up on the infrastructure already added for vPCI and allow ioreq
to decode accesses to MMCFG regions registered for a domain. This
infrastructure is still only accessible from internal callers, so
MMCFG regions can only be registered from the internal domain builder
used by PVH dom0.
Note
Internal ioreq servers will be processed first due to the implementation
of FOR_EACH_IOREQ_SERVER, and ioreqs are dispatched simply by calling
the handler function.
Signed-off-by: Roger Pau Monné
Reviewed-by: Paul Durrant
---
Changes since v2:
- Have a single condition for buffered ioreqs.
On Sat, Sep 28, 2019 at 04:20:34PM +0200, Marek Marczykowski-Górecki wrote:
> When libxl__device_pci_add() is called, stubdomain is already running,
> even when still constructing the target domain. Previously, do_pci_add()
> was called with 'starting' hardcoded to false, but now do_pci_add()
ASM_CALL_CONSTRAINT is defined there.
No functional change.
Signed-off-by: Wei Liu
Reviewed-by: Roger Pau Monné
---
xen/include/asm-x86/guest/hypercall.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/xen/include/asm-x86/guest/hypercall.h
b/xen/include/asm-x86/guest/hypercall.h
index
The only user is Xen specific code in PV shim. We can therefore export
the variable directly.
Signed-off-by: Wei Liu
Reviewed-by: Roger Pau Monné
---
xen/arch/x86/guest/xen/xen.c| 7 +--
xen/arch/x86/pv/shim.c | 2 +-
xen/include/asm-x86/guest/xen.h | 2 +-
3 files changed, 3
We will soon implement Hyper-V support for Xen. Add a framework for
that.
This requires moving some of the hypervisor_* functions from xen.h to
hypervisor.h.
Signed-off-by: Wei Liu
---
xen/arch/x86/guest/Makefile| 2 +
xen/arch/x86/guest/hypervisor.c| 45
Hi all
This is version 2 of the patch series.
This is the very first stage for porting Xen to run on Hyper-V with all the
goodies Hyper-V has to offer. With this series, Xen can successfully detect
Hyper-V and prints out a message. I would like to first get the code structure
and kconfig
We use the same code structure as we die for Xen.
As starters, detect Hyper-V in probe routine. More complex
functionalities will be added later.
Signed-off-by: Wei Liu
---
xen/arch/x86/Kconfig | 9
xen/arch/x86/guest/Makefile| 1 +
Xen is able to run as a guest on Xen. We plan to make it able to run
on Hyper-V as well.
Introduce CONFIG_GUEST which is set to true if either running on Xen
or Hyper-V is desired. Restructure code hierarchy for new code to
come.
No functional change intended.
Signed-off-by: Wei Liu
We need ASSERT_UNREACHABLE.
Signed-off-by: Wei Liu
---
xen/include/asm-x86/guest/hypercall.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/xen/include/asm-x86/guest/hypercall.h
b/xen/include/asm-x86/guest/hypercall.h
index c9deca6ffc..d0d2f5022d 100644
---
Take the chance to change probe_hypervisor to hypervisor_probe.
Signed-off-by: Wei Liu
---
xen/arch/x86/guest/hypervisor.c | 31 +--
xen/arch/x86/guest/xen/pvh-boot.c | 2 +-
xen/arch/x86/guest/xen/xen.c | 26 ++
xen/arch/x86/setup.c
Signed-off-by: Wei Liu
---
xen/arch/x86/guest/hypervisor.c| 5 +
xen/arch/x86/setup.c | 6 +-
xen/include/asm-x86/guest/hypervisor.h | 2 ++
3 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/xen/arch/x86/guest/hypervisor.c
They are used in Xen code only.
No functional change.
Signed-off-by: Wei Liu
---
xen/arch/x86/guest/xen/xen.c| 6 +++---
xen/arch/x86/pv/shim.c | 4 ++--
xen/include/asm-x86/guest/xen.h | 4 ++--
3 files changed, 7 insertions(+), 7 deletions(-)
diff --git
Hi all
In case you're wondering, I can already run a fully fledged Xen system on
Hyper-V with emulated disk and network.
This is the very first stage for porting Xen to run on Hyper-V with all the
goodies Hyper-V has to offer. With this series, Xen can successfully detect
Hyper-V and prints out
On Mon, Sep 30, 2019 at 11:32:53AM +0100, Hongyan Xia wrote:
> From: Wei Liu
>
> Defer the call to clear_page to the point when we're sure the page is
> going to become a page table.
>
> This is a minor optimisation. No functional change.
>
> Signed-off-by: Wei Liu
The benefit of this patch
On Mon, Sep 30, 2019 at 04:00:43PM +0100, Wei Liu wrote:
> We use the same code structure as we die for Xen.
Urgh. There is a rather unfortunate typo. No software is worth dying
for. :-)
Wei.
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
On 30.09.2019 16:30, Chao Gao wrote:
> On Mon, Sep 30, 2019 at 11:18:05AM +0200, Jan Beulich wrote:
>> On 29.09.2019 23:24, Chao Gao wrote:
>>> --- a/xen/arch/x86/msi.c
>>> +++ b/xen/arch/x86/msi.c
>>> @@ -1265,7 +1265,13 @@ int pci_msi_conf_write_intercept(struct pci_dev
>>> *pdev, unsigned int
We are going to need this to sort out bisection for freebsd's
recursive builds.
Signed-off-by: Ian Jackson
---
Osstest.pm| 6 +++---
cs-bisection-step | 17 +
2 files changed, 12 insertions(+), 11 deletions(-)
diff --git a/Osstest.pm b/Osstest.pm
index
On 9/28/19 4:13 PM, Pawel Wieczorkiewicz wrote:
Extend the XC python bindings library to support also all common
livepatch operations and actions.
Add the python bindings for the following operations:
- status (pyxc_livepatch_status):
Requires a payload name as an input.
Returns a status
> -Original Message-
> From: Paul Durrant
> Sent: 30 September 2019 13:48
> To: 'Jürgen Groß' ; Jan Beulich
> Cc: xen-devel@lists.xenproject.org; osstest service owner
>
> Subject: RE: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
>
> > -Original Message-
> > From:
On Mon, Sep 30, 2019 at 11:09:58AM +0200, Roger Pau Monné wrote:
>On Mon, Sep 30, 2019 at 05:24:31AM +0800, Chao Gao wrote:
>> Current, Xen isn't aware of device reset (initiated by dom0). Xen may
>> access the device while device cannot respond to config requests
>> normally (e.g. after device
On Mon, Sep 30, 2019 at 11:18:05AM +0200, Jan Beulich wrote:
>On 29.09.2019 23:24, Chao Gao wrote:
>> --- a/xen/arch/x86/msi.c
>> +++ b/xen/arch/x86/msi.c
>> @@ -1265,7 +1265,13 @@ int pci_msi_conf_write_intercept(struct pci_dev
>> *pdev, unsigned int reg,
>> pos = entry ?
On 9/24/19 1:33 AM, Nicholas Rosbrook wrote:
> Hi George,
>
> I made the changes that we discussed WRT C to Go type marshaling. See [1] for
> generated code.
>
> In addition, I took a pass at implementing Go to C type marshaling. The
> generated toC functions are also in [1].
>
> Finally, I
> -Original Message-
> From: Jürgen Groß
> Sent: 30 September 2019 10:30
> To: Paul Durrant ; Jan Beulich
> Cc: xen-devel@lists.xenproject.org; osstest service owner
>
> Subject: Re: [Xen-devel] [xen-unstable test] 141990: regressions - FAIL
>
> On 30.09.19 11:17, Paul Durrant wrote:
On 27.09.2019 18:12, Chao Gao wrote:
> @@ -105,23 +110,40 @@ void __init microcode_set_module(unsigned int idx)
> }
>
> /*
> - * The format is '[|scan]'. Both options are optional.
> - * If the EFI has forced which of the multiboot payloads is to be used,
> - * no parsing will be attempted.
>
other_revision_job_suffix contains ad-hoc code which returns an
identifier distinguishing certain jobs which are expected to refer to
different revisions within their flight.
Add the special case for freebsdbuildjob's recursion.
After this change we are now willing to tolerate the fact that a
> -Original Message-
> From: Xen-devel On Behalf Of Julien
> Grall
> Sent: 30 September 2019 17:45
> To: xen-devel@lists.xenproject.org
> Cc: jgr...@suse.com; jul...@xen.org; Julien Grall ;
> volodymyr_babc...@epam.com
> Subject: [Xen-devel] [PATCH] Update my e-mail in MAINTAINERS
>
>
On 30/09/2019 17:48, Paul Durrant wrote:
-Original Message-
From: Xen-devel On Behalf Of Julien
Grall
Sent: 30 September 2019 17:45
To: xen-devel@lists.xenproject.org
Cc: jgr...@suse.com; jul...@xen.org; Julien Grall ;
volodymyr_babc...@epam.com
Subject: [Xen-devel] [PATCH] Update
flight 142006 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142006/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 7 xen-boot fail REGR. vs.
133580
Before the problematic commit, libxl used to ignore error when
destroying (force == true) a passthrough device. If the DM failed to
detach the pci device within the allowed time, the timed out error
raised skip part of pci_remove_*, but also raise the error up to the
caller of
Fixes: 11db56f9a6291
Signed-off-by: Anthony PERARD
---
tools/libxl/libxl_pci.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/libxl/libxl_pci.c b/tools/libxl/libxl_pci.c
index 47258177bc71..3b31cfd417be 100644
--- a/tools/libxl/libxl_pci.c
+++ b/tools/libxl/libxl_pci.c
@@ -1694,6
Patch series available in this git branch:
https://xenbits.xen.org/git-http/people/aperard/xen-unstable.git
br.fixes-for-pci-pt-libxl-v1
Hi,
Some fixes following the recent changes to use ev_qmp in libxl.
Anthony PERARD (2):
libxl_pci: Don't ignore PCI PT error at guest creation
libxl_pci:
flight 142017 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142017/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf f835e1d4c187014742fbd766ec2fbc07ef5384ba
baseline version:
ovmf
On 30/09/2019 19:23, Anthony PERARD wrote:
> Before the problematic commit, libxl used to ignore error when
> destroying (force == true) a passthrough device. If the DM failed to
> detach the pci device within the allowed time, the timed out error
> raised skip part of pci_remove_*, but also raise
The code generation for barrier_nospec_true() is not correct. We are taking a
perf it from the added fences, but not gaining any speculative safety.
This is caused by inline assembly trying to fight the compiler optimiser, and
the optimiser winning. There is no clear way to achieve safety, so
There are legitimate circumstance where array hardening is not wanted or
needed. Allow it to be turned off.
Signed-off-by: Andrew Cooper
---
CC: Jan Beulich
CC: Wei Liu
CC: Roger Pau Monné
CC: Juergen Gross
---
xen/common/Kconfig | 21 +
xen/include/xen/nospec.h |
The main purpose is patch 2. The "l1tf-barrier" work currently causes a perf
hit and gains no safety, and is therefore unfit for inclusion into Xen 4.13 at
this time.
Andrew Cooper (2):
xen/nospec: Introduce CONFIG_SPECULATIVE_ARRAY_HARDEN
xen/nospec: Introduce
Am Tue, 24 Sep 2019 15:17:43 +0100
schrieb Ian Jackson :
> I might be open to argument on that for specific target operating systems if
> the appropriate distro maintainers were to make a case.
I provided reasons why the current default is not appropriate, and the change
should be applied.
I will soon lose access to my Arm e-mail address. Update it to
jul...@xen.org
Signed-off-by: Julien Grall
Cc: jul...@xen.org
---
Changes in v2:
- Use the correct e-mail address
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS
flight 142038 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142038/
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 Sun, Sep 29, 2019 at 08:27:10PM +0200, Sander Eikelenboom wrote:
> Hi Anthony,
>
> While testing I encountered a problem with my HVM guests which use pci
> passthrough.
> When trying to shutdown the guest it will stay in the "---s--" runstate
> indefinitely.
>
> On the guest console I get:
flight 142023 freebsd-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142023/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-freebsd 7 freebsd-buildfail REGR. vs. 141501
Tests which did
I will soon lose access to my Arm e-mail address. Update it to
jul...@xen.org
Signed-off-by: Julien Grall
Cc: jul...@xen.org
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 718f0a4ca1..1d247231d6 100644
--- a/MAINTAINERS
Olaf Hering writes ("Re: [PATCH RESEND v1 2/8] tools: move scripts from etc to
libexec"):
> Am Tue, 24 Sep 2019 15:17:43 +0100
> schrieb Ian Jackson :
> > I think the ability of the admin to edit these scripts is important and I
> > have used it myself in the past.
>
> Since they are scripts,
I will soon lose access to my Arm e-mail address. Update it to
jul...@xen.org
Signed-off-by: Julien Grall
Cc: jul...@xen.org
---
Changes in v2:
- Use the correct e-mail address
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS
Julien Grall writes ("[RESEND PATCH v2] Update my e-mail in MAINTAINERS"):
> I will soon lose access to my Arm e-mail address. Update it to
> jul...@xen.org
>
> Signed-off-by: Julien Grall
> Cc: jul...@xen.org
Acked-by: Ian Jackson
and pushed.
Sorry for you having to resend it.
Ian.
Hi George,
> Just going through in detail, I notice one thing about your
> implementation of Defbool: you simply copy over the value of
> libxl_defbool. The header says of libxl_defbool:
>
> * Users should treat this struct as opaque and use the following
> * defined macros and accessor
GAS 2.25.0 throws multiple errors when building arm32/head.S:
arm32/head.S: Assembler messages:
arm32/head.S:452: Error: invalid constant (f7f) after fixup
arm32/head.S:453: Error: invalid constant (f7f) after fixup
arm32/head.S:495: Error: invalid constant (f7f) after fixup
arm32/head.S:510:
On 30/09/2019 19:44, Julien Grall wrote:
> GAS 2.25.0 throws multiple errors when building arm32/head.S:
>
> arm32/head.S: Assembler messages:
> arm32/head.S:452: Error: invalid constant (f7f) after fixup
> arm32/head.S:453: Error: invalid constant (f7f) after fixup
> arm32/head.S:495: Error:
Clang in particular has a habit of out-of-lining these and creating multiple
local copies of _mfn() and mfn_x(), etc. Override this behaviour.
Adjust bool_t to bool for the *_eq() helpers.
Signed-off-by: Andrew Cooper
---
CC: George Dunlap
CC: Ian Jackson
CC: Jan Beulich
CC: Konrad
1 - 100 of 232 matches
Mail list logo
