flight 172604 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172604/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a
test-amd64-i386-libvirt-raw 1 buil
[removing xen-users to avoid crossposting]
On 18.08.22 08:18, A Sudheer wrote:
Hi All
On XEN-4.16 with Ubuntu 22.04 Dom0 and HVM-DomU, I tried to do a USB mass
storage device passthrough to DomU.
I followed the PVUSB method mentioned in
https://wiki.xenproject.org/wiki/Xen_USB_Passthrough
Hi All
On XEN-4.16 with Ubuntu 22.04 Dom0 and HVM-DomU, I tried to do a USB mass
storage device passthrough to DomU.
I followed the PVUSB method mentioned in
https://wiki.xenproject.org/wiki/Xen_USB_Passthrough.
With 8GB sandisk pen drive, i am able to do USB passthrough to DomU.
But with 64GB sa
flight 172614 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172614/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
flight 172601 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172601/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 172123
build-i386-libvir
flight 172609 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172609/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
flight 172596 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172596/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172133
build-amd64-libvirt
flight 172606 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172606/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
flight 172591 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172591/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172128
build-amd64-libvirt
This is a huge performance improvement for two reasons:
1. It uses the filesystem’s asynchronous I/O support, rather than using
synchronous I/O.
2. It bypasses the page cache, removing a redundant layer of caching and
associated overhead.
---
tools/hotplug/Linux/block | 2 +-
1 file changed
flight 172605 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172605/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 1 build-check(1) blocked n/a
build-amd64-libvirt 6 lib
On Wed, Aug 17, 2022 at 10:16 AM Daniel P. Smith
wrote:
>
> On 8/16/22 13:43, Jason Andryuk wrote:
> > Hi,
> >
> > I think you should change the title to "xsm/flask: Boot-time labeling
> > for multiple domains". Refactor implies no functional change, and
> > this is a functional change. With thi
flight 172602 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172602/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
On 7/14/2022 10:07 PM, Chuck Zmudzinski wrote:
> On 7/14/2022 1:30 AM, Thorsten Leemhuis wrote:
>
> >
> > Sorry, have to ask: is this supposed to finally fix this regression?
> > https://lore.kernel.org/regressions/YnHK1Z3o99eMXsVK@mail-itl/
>
> Yes that's the first report I saw to lkml about this
flight 172599 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172599/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 1 build-check(1) blocked n/a
build-amd64-libvirt 6 lib
flight 172590 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172590/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-armhf-libvirt
On 17.08.2022 17:27, Marek Marczykowski-Górecki wrote:
> On Wed, Aug 17, 2022 at 05:08:35PM +0200, Jan Beulich wrote:
>> On 13.08.2022 03:39, Marek Marczykowski-Górecki wrote:
>>> --- a/xen/drivers/char/xhci-dbc.c
>>> +++ b/xen/drivers/char/xhci-dbc.c
>>> @@ -23,6 +23,7 @@
>>> #include
>>> #incl
On 17.08.2022 17:21, Anthony PERARD wrote:
> While we already have "--no-print-directory" added to the make flags
> in some cases, there's one case where the flags is missing, when doing
> an out-of-tree build with O=, e.g.
> cd xen; make O=build
>
> Without it, we just have loads of "Entering
On Wed, Aug 17, 2022 at 05:08:35PM +0200, Jan Beulich wrote:
> On 13.08.2022 03:39, Marek Marczykowski-Górecki wrote:
> > --- a/docs/misc/xen-command-line.pandoc
> > +++ b/docs/misc/xen-command-line.pandoc
> > @@ -724,7 +724,7 @@ Available alternatives, with their meaning, are:
> >
> > ### dbgp
On 17/08/2022 16:21, Anthony Perard wrote:
> While we already have "--no-print-directory" added to the make flags
> in some cases, there's one case where the flags is missing, when doing
> an out-of-tree build with O=, e.g.
> cd xen; make O=build
>
> Without it, we just have loads of "Entering
While we already have "--no-print-directory" added to the make flags
in some cases, there's one case where the flags is missing, when doing
an out-of-tree build with O=, e.g.
cd xen; make O=build
Without it, we just have loads of "Entering directory" and "Leaving
directory" with the same direc
On 17.08.2022 16:45, Rahul Singh wrote:
> @@ -363,6 +373,42 @@ int __init pci_host_bridge_mappings(struct domain *d)
> return 0;
> }
>
> +static int is_bar_valid(const struct dt_device_node *dev,
> +u64 addr, u64 len, void *data)
s/u64/uint64_t/g please.
> +{
> +
On 13.08.2022 03:39, Marek Marczykowski-Górecki wrote:
> --- a/docs/misc/xen-command-line.pandoc
> +++ b/docs/misc/xen-command-line.pandoc
> @@ -724,7 +724,7 @@ Available alternatives, with their meaning, are:
>
> ### dbgp
> > `= ehci[ | @pci:. ]`
> -> `= xhci[ | @pci:. ]`
> +> `= xhci[ | @p
is_memory_hole was implemented for x86 and not for ARM when introduced.
Replace is_memory_hole call to pci_check_bar as function should check
if device BAR is in defined memory range. Also, add an implementation
for ARM which is required for PCI passthrough.
On x86, pci_check_bar will call is_memo
Modify pci_find_host_bridge_node argument to const pdev to avoid
converting the dev to pdev in pci_find_host_bridge_node and also
constify the return.
Signed-off-by: Rahul Singh
---
Changes in v2:
- this patch is introduced in this version
---
xen/arch/arm/include/asm/pci.h | 3 ++-
xen/arc
This patch series is to implement something like is_memory_hole function for
ARM.
Rahul Singh (2):
xen/arm: pci: modify pci_find_host_bridge_node argument to const pdev
xen/pci: replace call to is_memory_hole to pci_check_bar
xen/arch/arm/include/asm/pci.h | 5 ++-
xen/arch/arm/pci/pci
On 13.08.2022 03:39, Marek Marczykowski-Górecki wrote:
> Add another work ring buffer for received data, and point IN TRB at it.
> Ensure there is always at least one pending IN TRB, so the controller
> has a way to send incoming data to the driver.
> Note that both "success" and "short packet" com
On 13.08.2022 03:38, Marek Marczykowski-Górecki wrote:
> @@ -1050,13 +1051,20 @@ static struct uart_driver dbc_uart_driver = {
> };
>
> /* Those are accessed via DMA. */
> -static struct xhci_trb evt_trb[DBC_TRB_RING_CAP];
> -static struct xhci_trb out_trb[DBC_TRB_RING_CAP];
> -static struct xh
On 17.08.2022 16:12, Anthony PERARD wrote:
> On Wed, Aug 17, 2022 at 12:38:36PM +0200, Jan Beulich wrote:
>> On 17.08.2022 11:15, Anthony PERARD wrote:
>>> --- a/xen/common/efi/efi-common.mk
>>> +++ b/xen/common/efi/efi-common.mk
>>> @@ -9,9 +9,9 @@ CFLAGS-y += -iquote $(srcdir)
>>> # e.g.: It tra
Hi Anthony,
> On 17 Aug 2022, at 10:15, Anthony PERARD wrote:
>
> We can't have a source file with the same name that exist in both the
> common code and in the arch specific code for efi/. This can lead to
> comfusion in make and it can pick up the wrong source file. This issue
> lead to a fail
On 8/16/22 13:43, Jason Andryuk wrote:
Hi,
I think you should change the title to "xsm/flask: Boot-time labeling
for multiple domains". Refactor implies no functional change, and
this is a functional change. With this, I think the commit message
should be re-written to focus on the "why" of th
On Wed, Aug 17, 2022 at 12:38:36PM +0200, Jan Beulich wrote:
> On 17.08.2022 11:15, Anthony PERARD wrote:
> > --- a/xen/common/efi/efi-common.mk
> > +++ b/xen/common/efi/efi-common.mk
> > @@ -9,9 +9,9 @@ CFLAGS-y += -iquote $(srcdir)
> > # e.g.: It transforms "dir/foo/bar" into successively
> > #
On 17/08/2022 12:02, Andrew Cooper wrote:
> On 17/08/2022 10:15, Anthony PERARD wrote:
>> We can't have a source file with the same name that exist in both the
>> common code and in the arch specific code for efi/. This can lead to
>> comfusion in make and it can pick up the wrong source file. This
On Wed, 17 Aug 2022 at 15:18, Jan Beulich wrote:
>
> On 17.08.2022 12:57, Leo Yan wrote:
> > On Arm64, when boot Dom0 with the Linux kernel, it reports the warning:
> >
> > [0.403737] [ cut here ]
> > [0.403738] WARNING: CPU: 30 PID: 0 at
> > drivers/irqchip/irq-gi
flight 172597 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172597/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
On 17.08.2022 12:57, Leo Yan wrote:
> On Arm64, when boot Dom0 with the Linux kernel, it reports the warning:
>
> [0.403737] [ cut here ]
> [0.403738] WARNING: CPU: 30 PID: 0 at
> drivers/irqchip/irq-gic-v3-its.c:3074 its_cpu_init+0x814/0xae0
> [0.403745] Modul
flight 172587 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172587/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 172123
build-i386-libvir
.init.text is a small section currently located amongst .text.entry
code. Move it above .text.entry.
This has no functional change but makes the code a bit more readable.
Suggested-by: Andrew Cooper
Signed-off-by: Jane Malalane
Reviewed-by: Jan Beulich
---
CC: Jan Beulich
CC: Andrew Cooper
C
flight 172588 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172588/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-multivcpu 20 guest-localmigrate/x10fail pass in 172575
Tests which did not succeed, but
On 09-08-22, 11:04, Viresh Kumar wrote:
> Hello,
>
> This patchset adds toolstack support for I2C and GPIO virtio devices. This is
> inspired from the work done by Oleksandr for the Disk device.
>
> This is developed as part of Linaro's Project Stratos, where we are working
> towards Hypervisor a
On 17/08/2022 10:15, Anthony PERARD wrote:
> We can't have a source file with the same name that exist in both the
> common code and in the arch specific code for efi/. This can lead to
> comfusion in make and it can pick up the wrong source file. This issue
> lead to a failure to build a pv-shim f
On Arm64, when boot Dom0 with the Linux kernel, it reports the warning:
[0.403737] [ cut here ]
[0.403738] WARNING: CPU: 30 PID: 0 at drivers/irqchip/irq-gic-v3-its.c:3074
its_cpu_init+0x814/0xae0
[0.403745] Modules linked in:
[0.403748] CPU: 30 PID: 0 Comm
flight 172595 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172595/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
flight 172581 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172581/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172133
build-amd64-libvirt
On 17.08.2022 11:15, Anthony PERARD wrote:
> --- a/xen/common/efi/efi-common.mk
> +++ b/xen/common/efi/efi-common.mk
> @@ -9,9 +9,9 @@ CFLAGS-y += -iquote $(srcdir)
> # e.g.: It transforms "dir/foo/bar" into successively
> # "dir foo bar", ".. .. ..", "../../.."
> $(obj)/%.c: $(srctree)/co
On 17.08.2022 10:56, Jane Malalane wrote:
> On 16/08/2022 14:06, Jan Beulich wrote:
>> On 16.08.2022 12:16, Jane Malalane wrote:
>>> On 05/08/2022 10:24, Jan Beulich wrote:
On 04.08.2022 17:04, Jane Malalane wrote:
> Suggested-by: Andrew Cooper
> Signed-off-by: Jane Malalane
>>>
On 16.08.2022 04:36, Penny Zheng wrote:
> The name of free_staticmem_pages is inappropriate, considering it is
> the opposite of function prepare_staticmem_pages.
>
> Rename free_staticmem_pages to unprepare_staticmem_pages.
>
> Signed-off-by: Penny Zheng
Acked-by: Jan Beulich
preferably, as s
On 16.08.2022 04:36, Penny Zheng wrote:
> @@ -2867,6 +2854,61 @@ int __init acquire_domstatic_pages(struct domain *d,
> mfn_t smfn,
>
> return 0;
> }
> +
> +/*
> + * Acquire nr_mfns contiguous pages, starting at #smfn, of static memory,
> + * then assign them to one specific domain #d.
> +
On 19.07.22 17:15, Borislav Petkov wrote:
On Fri, Jul 15, 2022 at 04:25:49PM +0200, Juergen Gross wrote:
Today PAT is usable only with MTRR being active, with some nasty tweaks
to make PAT usable when running as Xen PV guest, which doesn't support
MTRR.
The reason for this coupling is, that bot
We can't have a source file with the same name that exist in both the
common code and in the arch specific code for efi/. This can lead to
comfusion in make and it can pick up the wrong source file. This issue
lead to a failure to build a pv-shim for x86 out-of-tree, as this is
one example of an x8
Hi Jan,
On 17/08/2022 09:37, Jan Beulich wrote:
On 16.08.2022 20:59, Julien Grall wrote:
--- a/xen/arch/arm/setup.c
+++ b/xen/arch/arm/setup.c
@@ -75,10 +75,24 @@ domid_t __read_mostly max_init_domid;
static __used void init_done(void)
{
+int rc;
+
/* Must be done past setting
flight 172592 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/172592/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 172136
build-amd64-libvirt
On 16/08/2022 14:06, Jan Beulich wrote:
> On 16.08.2022 12:16, Jane Malalane wrote:
>> On 05/08/2022 10:24, Jan Beulich wrote:
>>> On 04.08.2022 17:04, Jane Malalane wrote:
Suggested-by: Andrew Cooper
Signed-off-by: Jane Malalane
>>>
>>> In the title you say "port", but then you don't s
On 16.08.2022 04:36, Penny Zheng wrote:
> Today when a domain unpopulates the memory on runtime, they will always
> hand the memory back to the heap allocator. And it will be a problem if domain
> is static.
>
> Pages as guest RAM for static domain shall be reserved to only this domain
> and not b
On 16.08.2022 20:59, Julien Grall wrote:
> --- a/xen/arch/arm/setup.c
> +++ b/xen/arch/arm/setup.c
> @@ -75,10 +75,24 @@ domid_t __read_mostly max_init_domid;
>
> static __used void init_done(void)
> {
> +int rc;
> +
> /* Must be done past setting system_state. */
> unregister_ini
Hi all
Sorry for that, please ignore this too. I sent the wrong email.
> -Original Message-
> From: jiaxie01
> Sent: Wednesday, August 17, 2022 10:07 AM
> To: Jiamei Xie ; xen-devel@lists.xenproject.org
> Cc: Oleksandr Tyshchenko ; Wei Liu
> ; Anthony PERARD ; George
> Dunlap ; Nick Ros
branch xen-unstable
xenbranch xen-unstable
job build-armhf-libvirt
testid libvirt-build
Tree: libvirt git://xenbits.xen.org/libvirt.git
Tree: libvirt_keycodemapdb https://gitlab.com/keycodemap/keycodemapdb.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: qemuu git://xenbits.xen.org/qemu
57 matches
Mail list logo