flight 170346 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170346/
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
flight 170348 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170348/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
flight 170349 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170349/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
Hello,
Following the meeting of the 14th April
[https://cryptpad.fr/pad/#/3/pad/edit/c4fdcd12de9a85e303fa0fd4d787b7de/], here
is a new Doodle link to schedule the next Xen Project Management Working Group
meeting:
https://doodle.com/meeting/organize/id/dyPg8MWb
Agenda:
- Jira demo
- Feedb
Hi Rahul,
On 11/05/2022 15:32, Rahul Singh wrote:
On 10 May 2022, at 1:32 pm, Julien Grall wrote:
+domain may toggle masked bits in the masked bit field and should clear the
+pending bit when an event has been processed
+
+Events are received by a domain via an interrupt from Xen to the domain
flight 170343 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170343/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-shadow 7 xen-install fail in 170314 pass in 170343
test-amd64-i386-migrupgrade 10
flight 170350 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170350/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
From: Penny Zheng
This commit introduces process_shm to cope with static shared memory in
domain construction.
DOMID_IO will be the default owner of memory pre-shared among multiple domains
at boot time, when no explicit owner is specified.
This commit only considers allocating static shared me
In safety-critical environment, it is not considered safe to
dynamically change important configurations at runtime. Everything
should be statically defined and statically verified.
In this case, if the system configuration knows a priori that there are
only 2 VMs and they need to communicate over
From: Penny Zheng
This patch serie introduces a new feature: setting up static
shared memory on a dom0less system, through device tree configuration.
This commit parses shared memory node at boot-time, and reserve it in
bootinfo.reserved_mem to avoid other use.
This commits proposes a new Kconf
If owner property is defined, then owner domain of a static shared memory
region is not the default dom_io anymore, but a specific domain.
This commit implements allocating static shared memory to a specific domain
when owner property is defined.
Coding flow for dealing borrower domain will be in
Later, we need to add the right amount of references, which should be
the number of borrower domains, to the owner domain. Since we only have
get_page() to increment the page reference by 1, a loop is needed per
page, which is inefficient and time-consuming.
To save the loop time, this commit intr
Borrower domain will fail to get a page ref using the owner domain
during allocation, when the owner is created after borrower.
So here, we decide to get and add the right amount of reference, which
is the number of borrowers, when the owner is allocated.
Signed-off-by: Penny Zheng
---
v3 change
From: Penny Zheng
To add statically shared memory nodes in Dom0, user shall put according
static shared memory configuration under /chosen node.
This commit adds shm-processing function process_shm in construct_dom0
to enable statically shared memory on Dom0.
Signed-off-by: Penny Zheng
Reviewe
This commit sets up shared memory foreign mapping for borrower domain.
If owner domain is the default dom_io, all shared domain are treated as
borrower domain.
Signed-off-by: Penny Zheng
Reviewed-by: Stefano Stabellini
---
v3 change:
- use map_regions_p2mt instead
---
v2 change:
- remove guest_
We expose the shared memory to the domU using the "xen,shared-memory-v1"
reserved-memory binding. See
Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt
in Linux for the corresponding device tree binding.
To save the cost of re-parsing shared memory device tree configuration w
flight 170351 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170351/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
On 12/05/2022 10:11, Penny Zheng wrote:
Later, we need to add the right amount of references, which should be
the number of borrower domains, to the owner domain. Since we only have
get_page() to increment the page reference by 1, a loop is needed per
page, which is inefficient and time-consum
flight 170352 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170352/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
On 12/05/2022 10:11, Penny Zheng wrote:
@@ -827,6 +858,37 @@ static int __init allocate_shared_memory(struct domain *d,
}
}
+/*
+ * Get the right amount of references per page, which is the number of
+ * borrow domains.
+ */
+ret = acquire_nr_borrower_do
flight 170354 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170354/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
Hi Stefano,
> On 11 May 2022, at 21:06, Stefano Stabellini wrote:
>
> On Wed, 11 May 2022, Bertrand Marquis wrote:
>>> I understand the patch is already written, so I was OK if you simply list
>>> of the commits with the authors/tags for this time.
>>
>> I would like to understand where this r
On Wed, May 11, 2022 at 3:25 PM Marek Marczykowski-Górecki
wrote:
>
> Hi,
>
> The reproducer is trivial:
>
> [user@dom0 ~]$ sudo xl block-attach work backend=sys-usb vdev=xvdi
> target=/dev/sdz
> [user@dom0 ~]$ xl block-list work
> Vdev BE handle state evt-ch ring-ref BE-path
> 51712 0 241
flight 170355 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170355/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
flight 170356 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170356/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
On Thu, May 5, 2022 at 4:27 AM Roger Pau Monné wrote:
>
> On Wed, Apr 27, 2022 at 11:34:19AM -0400, Tamas K Lengyel wrote:
> > Need to separately specify if the reset is for the memory or for the VM
> > state,
> > or both.
> >
> > Signed-off-by: Tamas K Lengyel
>
> Reviewed-by: Roger Pau Monné
On Wed, May 4, 2022 at 9:12 AM Tamas K Lengyel wrote:
>
> On Wed, Apr 27, 2022 at 11:51 AM Tamas K Lengyel
> wrote:
> >
> > Add monitor event that hooks the vmexit handler allowing for both sync and
> > async monitoring of events. With async monitoring an event is placed on the
> > monitor ring f
From: Masami Hiramatsu
commit f7919fd943abf0c77aed4441ea9897a323d132f5 upstream
Use __stringify() at __ASM_FORM() so that user can pass
code including macros to __ASM_FORM().
Signed-off-by: Masami Hiramatsu
Signed-off-by: Peter Zijlstra (Intel)
Cc: Juergen Gross
Cc: x...@kernel.org
Cc: Boris
This is a backport of a patch series for 5.4.x.
The patch series allows the x86 decoder to decode the Xen and KVM emulate
prefixes.
In particular this solves the following issue that appeared when commit
db6c6a0df840 ("objtool: Fix noreturn detection for ignored functions") was
backported to 5.4.
From: Masami Hiramatsu
commit b3dc0695fa40c3b280230fb6fb7fb7a94ce28bf4 upstream
Gather the emulate prefixes, which forcibly make the following
instruction emulated on virtualization, in one place.
Suggested-by: Peter Zijlstra
Signed-off-by: Masami Hiramatsu
Signed-off-by: Peter Zijlstra (Inte
From: Masami Hiramatsu
commit 4d65adfcd1196818659d3bd9b42dccab291e1751 upstream
Decode Xen and KVM's emulate-prefix signature by x86 insn decoder.
It is called "prefix" but actually not x86 instruction prefix, so
this adds insn.emulate_prefix_size field instead of reusing
insn.prefixes.
If x86
From: Masami Hiramatsu
commit 004e8dce9c5595697951f7cd0e9f66b35c92265e upstream
Prohibit probing on instruction which has XEN_EMULATE_PREFIX
or KVM's emulate prefix. Since that prefix is a marker for Xen
and KVM, if we modify the marker by kprobe's int3, that doesn't
work as expected.
Signed-of
On Thu, May 12, 2022 at 08:47:01AM -0400, Jason Andryuk wrote:
> On Wed, May 11, 2022 at 3:25 PM Marek Marczykowski-Górecki
> wrote:
> >
> > Hi,
> >
> > The reproducer is trivial:
> >
> > [user@dom0 ~]$ sudo xl block-attach work backend=sys-usb vdev=xvdi
> > target=/dev/sdz
> > [user@dom0 ~]$ xl
This is a note to let you know that I've just added the patch titled
x86/asm: Allow to pass macros to __ASM_FORM()
to the 5.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
x86-asm-a
This is a note to let you know that I've just added the patch titled
x86: xen: kvm: Gather the definition of emulate prefixes
to the 5.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
This is a note to let you know that I've just added the patch titled
x86: kprobes: Prohibit probing on instruction which has emulate prefix
to the 5.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the
This is a note to let you know that I've just added the patch titled
x86: xen: insn: Decode Xen and KVM emulate-prefix signature
to the 5.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
Hello,
first, I am sorry for stepping into the discussion so late.
I was busy with some other stuff and this patchset is far
from trivial.
Second, thanks a lot for putting so much effort into it.
Most of the changes look pretty good, especially all
the fixes of particular notifiers and split into
flight 170357 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170357/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
Hi Julien,
> On 12 May 2022, at 9:56 am, Julien Grall wrote:
>
> Hi Rahul,
>
> On 11/05/2022 15:32, Rahul Singh wrote:
>>> On 10 May 2022, at 1:32 pm, Julien Grall wrote:
+domain may toggle masked bits in the masked bit field and should clear the
+pending bit when an event has been p
Hi Daniel,
> On 11 May 2022, at 12:30 pm, Daniel P. Smith
> wrote:
>
> There are new capabilities, dom0less and hyperlaunch, that introduce internal
> hypervisor logic which needs to make resource allocation calls that are
> protected by XSM access checks. This creates an issue as a subset of t
Hi Daniel,
> On 11 May 2022, at 12:30 pm, Daniel P. Smith
> wrote:
>
> This commit implements full support for starting the idle domain privileged by
> introducing a new flask label xenboot_t which the idle domain is labeled with
> at creation. It then provides the implementation for the XSM h
Roger Pau Monne writes ("[PATCH] osstest: update Debian Buster install CD media
to 10.12"):
> Signed-off-by: Roger Pau Monné
Acked-by: Ian Jackson
Is this just a routine update, OOI, or was this to fix something ?
Thanks,
Ian.
flight 170358 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170358/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
> On Apr 14, 2022, at 4:49 PM, George Dunlap wrote:
>
> I’m pretty sure www-archive.xenproject.org is at least N-2 for websites; last
> updated nearly 9 years ago. As far as I can tell there’s nothing terribly
> interesting stored on the site itself. I’m going to pursue deleting it
> within
flight 170359 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170359/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
On Thu, May 12, 2022 at 01:56:47PM +, Maximilian Heyne wrote:
> This is a backport of a patch series for 5.4.x.
>
> The patch series allows the x86 decoder to decode the Xen and KVM emulate
> prefixes.
>
> In particular this solves the following issue that appeared when commit
> db6c6a0df840
flight 170360 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170360/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
Hi,
On 10/05/2022 07:52, Michal Orzel wrote:
On 06.05.2022 12:03, Jan Beulich wrote:
On 06.05.2022 11:42, Michal Orzel wrote:
Function unmap_common_complete (common/grant_table.c) defines and sets
a variable ld that is later on passed to a macro:
gnttab_host_mapping_get_page_type().
On Arm thi
flight 170363 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170363/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
On Thu, May 12, 2022 at 9:59 AM Roger Pau Monné wrote:
> Care to send a patch? :)
I will, but because of $reasons, it won't be out until next week.
Regards,
Jason
On May 12, 2022, at 11:55 AM, George Dunlap wrote:
>
>> On Apr 14, 2022, at 4:49 PM, George Dunlap wrote:
>>
>> I’m pretty sure www-archive.xenproject.org is at least N-2 for websites;
>> last updated nearly 9 years ago. As far as I can tell there’s nothing
>> terribly interesting stored on
On 5/7/22 2:19 PM, Oleksandr Tyshchenko wrote:
+
+/*
+ * Handling of free grants:
+ *
+ * Free grants are in a simple list anchored in gnttab_free_head. They are
+ * linked by grant ref, the last element contains GNTTAB_LIST_END. The number
+ * of free entries is stored in gnttab_free_count.
+
flight 170366 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170366/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
flight 170367 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170367/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
flight 170368 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170368/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
flight 170364 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170364/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm 1
> On May 12, 2022, at 8:44 PM, Rich Persaud wrote:
>
> On May 12, 2022, at 11:55 AM, George Dunlap wrote:
>>
>>> On Apr 14, 2022, at 4:49 PM, George Dunlap wrote:
>>>
>>> I’m pretty sure www-archive.xenproject.org is at least N-2 for websites;
>>> last updated nearly 9 years ago. As far a
flight 170369 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170369/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
On Thu, 12 May 2022, Rahul Singh wrote:
> > On 12 May 2022, at 9:56 am, Julien Grall wrote:
> >
> > Hi Rahul,
> >
> > On 11/05/2022 15:32, Rahul Singh wrote:
> >>> On 10 May 2022, at 1:32 pm, Julien Grall wrote:
> +domain may toggle masked bits in the masked bit field and should clear
> >
On Thu, 12 May 2022, Penny Zheng wrote:
> From: Penny Zheng
>
> This patch serie introduces a new feature: setting up static
> shared memory on a dom0less system, through device tree configuration.
>
> This commit parses shared memory node at boot-time, and reserve it in
> bootinfo.reserved_mem
On Thu, 12 May 2022, Penny Zheng wrote:
> From: Penny Zheng
>
> This commit introduces process_shm to cope with static shared memory in
> domain construction.
>
> DOMID_IO will be the default owner of memory pre-shared among multiple domains
> at boot time, when no explicit owner is specified.
>
On Thu, 12 May 2022, Penny Zheng wrote:
> If owner property is defined, then owner domain of a static shared memory
> region is not the default dom_io anymore, but a specific domain.
>
> This commit implements allocating static shared memory to a specific domain
> when owner property is defined.
>
On Thu, 12 May 2022, Penny Zheng wrote:
> We expose the shared memory to the domU using the "xen,shared-memory-v1"
> reserved-memory binding. See
> Documentation/devicetree/bindings/reserved-memory/xen,shared-memory.txt
> in Linux for the corresponding device tree binding.
>
> To save the cost of
flight 170371 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170371/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm 6 xen-buildfail REGR. vs. 168254
build-amd64
On Wed, 11 May 2022, Wei Chen wrote:
> In current code, when Xen is running in a multiple nodes
> NUMA system, it will set dma_bitsize in end_boot_allocator
> to reserve some low address memory as DMA zone.
>
> There are some x86 implications in the implementation.
> Because on x86, memory starts
On Wed, 11 May 2022, Wei Chen wrote:
> x86 is using compiler feature testing to decide EFI build
> enable or not. When EFI build is disabled, x86 will use an
> efi/stub.c file to replace efi/runtime.c for build objects.
> Following this idea, we introduce a stub file for Arm, but
> use CONFIG_ARM_E
On Mon, 9 May 2022, Stefano Stabellini wrote:
> On Mon, 9 May 2022, Bertrand Marquis wrote:
> > > On 6 May 2022, at 17:31, Stefano Stabellini
> > > wrote:
> > >
> > > Hi all,
> > >
> > > Roberto kindly provided the ECLAIR x86 results:
> > >
> > > https://eclairit.com:8443/job/XEN/Target=X86_64
flight 170362 qemu-mainline real [real]
flight 170372 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/170362/
http://logs.test-lab.xenproject.org/osstest/logs/170372/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-am
flight 170373 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170373/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 168254
build-amd64-xsm
On Wed, 11 May 2022, Julien Grall wrote:
> > +rc = xs_introduce_domain(xsh, info->domid,
> > +(GUEST_MAGIC_BASE >> XC_PAGE_SHIFT) + XENSTORE_PFN_OFFSET,
> > +xenstore_evtchn);
>
> I might be missing something here. In an ealier version, I pointed out that
> xs_introduce
On Wed, 11 May 2022, Julien Grall wrote:
> On 05/05/2022 01:16, Stefano Stabellini wrote:
> > From: Luca Miccio
> >
> > When xs_introduce_domain is called, send out a notification on the
> > xenstore event channel so that any (dom0less) domain waiting for the
> > xenstore interface to be ready ca
On Wed, 11 May 2022, Julien Grall wrote:
> > If dom0 is mandatory yes, we should still make sure that this code cannot be
> > reached so an ASSERT would be nice here at least in case someone tries to
> > activate this code without dom0 (which might happen when we will push the
> > serie for static
On Wed, 11 May 2022, Christoph Hellwig wrote:
> For historical reasons the switlb code paniced when the metadata could
> not be allocated, but just printed a warning when the actual main
> swiotlb buffer could not be allocated. Restore this somewhat unexpected
> behavior as changing it caused a bo
On Wed, 11 May 2022, Christoph Hellwig wrote:
> default_nslabs should only be used to initialize nslabs, after that we
> need to use the local variable that can shrink when allocations or the
> remap don't succeed.
>
> Fixes: 6424e31b1c05 ("swiotlb: remove swiotlb_init_with_tbl and
> swiotlb_init
On Wed, 11 May 2022, Christoph Hellwig wrote:
> nslabs can shrink when allocations or the remap don't succeed, so make
> sure to use it for all sizing. For that remove the bytes value that
> can get stale and replace it with local calculations and a boolean to
> indicate if the originally requeste
flight 170375 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170375/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 168254
build-amd64-xsm
Hi Julien
> -Original Message-
> From: Julien Grall
> Sent: Thursday, May 12, 2022 6:14 PM
> To: Penny Zheng ; xen-devel@lists.xenproject.org
> Cc: Wei Chen ; Stefano Stabellini
> ; Bertrand Marquis ;
> Volodymyr Babchuk
> Subject: Re: [PATCH v3 4/8] xen/arm: introduce put_page_nr and ge
Hi Julien
> -Original Message-
> From: Julien Grall
> Sent: Thursday, May 12, 2022 6:54 PM
> To: Penny Zheng ; xen-devel@lists.xenproject.org
> Cc: Wei Chen ; Stefano Stabellini
> ; Bertrand Marquis ;
> Volodymyr Babchuk
> Subject: Re: [PATCH v3 5/8] xen/arm: Add additional reference to
flight 170376 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170376/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 168254
build-amd64-xsm
flight 170365 linux-linus real [real]
flight 170377 linux-linus real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/170365/
http://logs.test-lab.xenproject.org/osstest/logs/170377/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-
On 12.05.22 22:01, Boris Ostrovsky wrote:
On 5/7/22 2:19 PM, Oleksandr Tyshchenko wrote:
+
+/*
+ * Handling of free grants:
+ *
+ * Free grants are in a simple list anchored in gnttab_free_head. They are
+ * linked by grant ref, the last element contains GNTTAB_LIST_END. The number
+ * of free
Kees Cook wrote:
> I'm happy to also point out that the conversions (patches 5+) are actually
> a net reduction in lines of code:
> 49 files changed, 154 insertions(+), 244 deletions(-)
That doesn't mean that it's actually code that's clearer to read. I would say
that it's actually less clea
Kees Cook wrote:
> struct afs_acl {
> - u32 size;
> - u8 data[];
> + DECLARE_FLEX_ARRAY_ELEMENTS_COUNT(u32, size);
> + DECLARE_FLEX_ARRAY_ELEMENTS(u8, data);
> };
Oof... That's really quite unpleasant syntax. Is it not possible to have
mem_to_flex_dup() and friends
flight 170378 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170378/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 168254
build-amd64-xsm
On 13.05.22 03:16, Stefano Stabellini wrote:
On Wed, 11 May 2022, Julien Grall wrote:
On 05/05/2022 01:16, Stefano Stabellini wrote:
From: Luca Miccio
When xs_introduce_domain is called, send out a notification on the
xenstore event channel so that any (dom0less) domain waiting for the
xensto
flight 170381 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/170381/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 6 xen-buildfail REGR. vs. 168254
build-amd64-xsm
87 matches
Mail list logo
