flight 181953 xen-unstable real [real]
flight 181967 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/181953/
http://logs.test-lab.xenproject.org/osstest/logs/181967/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be r
Hello, Stefano,
Hello, Julien,
Thanks for your suggestions. I gave each of them a try, but it doesn't
look like it brings me anywhere at the moment.
On 21/07/2023 02:25, Stefano Stabellini wrote:
>
> On Thu, 20 Jul 2023, Julien Grall wrote:
> > (+ Juergen)
> >
> > On 19/07/2023 17:13, Andrei Ch
Hi,
I notice a regression report on Bugzilla [1]. Quoting from it:
> Hi Kernel Team,
>
> I rebuild today latest version from mainline repo.
> And i notice issue regarding xen-netfront.c.
>
> Error:
> [3.477400]
> =
flight 181952 qemu-mainline real [real]
flight 181965 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/181952/
http://logs.test-lab.xenproject.org/osstest/logs/181965/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-ar
Hi Andrew, Oleksii,
Please see below.
It looks like you have configured your personal repositories to mirror
upstream Xen:
https://gitlab.com/xen-project/people/olkur/xen
https://gitlab.com/xen-project/people/andyhhp/xen
Make sure that the option "Trigger pipelines for mirror updates" is
unsele
On Fri, Jul 21, 2023 at 05:49:49PM -0700, Stefano Stabellini wrote:
> On Sat, 22 Jul 2023, Marek Marczykowski-Górecki wrote:
> > On Fri, Jul 21, 2023 at 05:14:01PM -0700, Stefano Stabellini wrote:
> > > On Sat, 22 Jul 2023, Marek Marczykowski-Górecki wrote:
> > > > On Fri, Jul 21, 2023 at 04:42:11P
On Sat, 22 Jul 2023, Marek Marczykowski-Górecki wrote:
> On Fri, Jul 21, 2023 at 05:14:01PM -0700, Stefano Stabellini wrote:
> > On Sat, 22 Jul 2023, Marek Marczykowski-Górecki wrote:
> > > On Fri, Jul 21, 2023 at 04:42:11PM -0700, Stefano Stabellini wrote:
> > > > On Mon, 17 Jul 2023, Marek Marczy
On Fri, Jul 21, 2023 at 05:14:01PM -0700, Stefano Stabellini wrote:
> On Sat, 22 Jul 2023, Marek Marczykowski-Górecki wrote:
> > On Fri, Jul 21, 2023 at 04:42:11PM -0700, Stefano Stabellini wrote:
> > > On Mon, 17 Jul 2023, Marek Marczykowski-Górecki wrote:
> > > > On Mon, Jul 17, 2023 at 02:14:14P
On Sat, 22 Jul 2023, Marek Marczykowski-Górecki wrote:
> On Fri, Jul 21, 2023 at 04:42:11PM -0700, Stefano Stabellini wrote:
> > On Mon, 17 Jul 2023, Marek Marczykowski-Górecki wrote:
> > > On Mon, Jul 17, 2023 at 02:14:14PM +0100, Andrew Cooper wrote:
> > > > On 17/07/2023 2:09 pm, Marek Marczykow
On Fri, Jul 21, 2023 at 04:42:11PM -0700, Stefano Stabellini wrote:
> On Mon, 17 Jul 2023, Marek Marczykowski-Górecki wrote:
> > On Mon, Jul 17, 2023 at 02:14:14PM +0100, Andrew Cooper wrote:
> > > On 17/07/2023 2:09 pm, Marek Marczykowski-Górecki wrote:
> > > > "staging" branch is mirrored (automa
On Mon, 17 Jul 2023, Marek Marczykowski-Górecki wrote:
> On Mon, Jul 17, 2023 at 02:14:14PM +0100, Andrew Cooper wrote:
> > On 17/07/2023 2:09 pm, Marek Marczykowski-Górecki wrote:
> > > "staging" branch is mirrored (automatically or manually) to several
> > > repositories. Avoid building it severa
(You might want to check your email settings because it looks like you
sent an html email)
On Thu, 20 Jul 2023, Christopher Clark wrote:
> > +struct boot_info {
>
> This is what we call struct bootmodules on ARM right? Would it help if
> we used the same name?
>
> I am no
The same way we already do in xenbus_init.
Fixes the following warning:
[ 352.175563] Trying to free already-free IRQ 0
[ 352.177355] WARNING: CPU: 1 PID: 88 at kernel/irq/manage.c:1893
free_irq+0xbf/0x350
[...]
[ 352.213951] Call Trace:
[ 352.214390]
[ 352.214717] ? __warn+0x81/0x170
[
On Fri, 21 Jul 2023, Nicola Vetrini wrote:
> Rule 5.3 has the following headline:
> "An identifier declared in an inner scope shall not hide an
> identifier declared in an outer scope"
>
> The renaming s/sched_id/scheduler_id of the function defined in
> 'xen/common/sched/core.c' prevents any hidi
On Fri, 21 Jul 2023, Nicola Vetrini wrote:
> Rule 5.3 has the following headline:
> "An identifier declared in an inner scope shall not hide an
> identifier declared in an outer scope"
>
> To avoid any confusion resulting from the parameter 'debug'
> hiding the homonymous function declared at
> 'x
On Fri, 21 Jul 2023, Nicola Vetrini wrote:
> Rule 5.3 has the following headline:
> "An identifier declared in an inner scope shall not hide an
> identifier declared in an outer scope"
>
> The function parameters renamed in this patch are hiding a variable defined
> in an enclosing scope or a func
On Fri, 21 Jul 2023, Federico Serafini wrote:
> Give a name to unnamed parameters thus addressing violations of
> MISRA C:2012 Rule 8.2 ("Function types shall be in prototype form with
> named parameters").
> Keep consistency between parameter names and types used in function
> declarations and the
On Fri, 21 Jul 2023, Federico Serafini wrote:
> Change parameter names in function declarations to be consistent with
> the ones used in the correponding definitions, thus addressing
> violations of MISRA C:2012 Rule 8.3: "All declarations of an object or
> function shall use the same names and typ
On Fri, 21 Jul 2023, Simone Ballarin wrote:
> Il giorno ven 21 lug 2023 alle ore 00:29 Stefano Stabellini
> ha scritto:
>
> Patchew automatically picked it up from xen-devel and started a pipeline
> here:
>
> https://gitlab.com/xen-project/patchew/xen/-/pipelines/939440592
>
From: Stefano Stabellini
Rule 1.1 is uncontroversial and we are already following it.
Rule 5.6 has been deemed a good rule to have by the MISRA C group.
However, we do have a significant amount of violations that will take
time to resolve and might require partial deviations in the form of
in-co
On Fri, 21 Jul 2023, Jan Beulich wrote:
> On 21.07.2023 00:12, Christopher Clark wrote:
> > On Thu, Jul 13, 2023 at 11:51 PM Christopher Clark <
> > christopher.w.cl...@gmail.com> wrote:
> >
> >>
> >>
> >> On Sat, Jul 8, 2023 at 11:47 AM Stefano Stabellini
> >> wrote:
> >>
> >>> On Sat, 1 Jul 202
On Fri, 21 Jul 2023, Andrei Cherechesu (OSS) wrote:
> > I am really confused. I would try with regular Linux instead of Linux RT
> > and also would try to replace all the barriers in
> > drivers/tty/hvc/hvc_xen.c with their virt_* version to see if we can
> > narrow down the problem a bit.
> >
>
flight 181945 xen-4.17-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/181945/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemuu-win7-amd64 19 guest-stop fail like 181861
test-amd64-i386-xl-qemut-win7-am
flight 181943 libvirt real [real]
flight 181964 libvirt real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/181943/
http://logs.test-lab.xenproject.org/osstest/logs/181964/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-armhf-li
Hi Alejandro,
On 21/07/2023 16:09, Alejandro Vallejo wrote:
On Thu, Jul 20, 2023 at 09:05:55PM +0100, Julien Grall wrote:
Hi Alejandro,
On 17/07/2023 17:03, Alejandro Vallejo wrote:
arm32 merely covers the XENHEAP, whereas arm64 currently covers anything in
the frame table. These comments hig
On 20.07.23 12:41, Viresh Kumar wrote:
Hello Viresh
> On 13-07-23, 14:40, Oleksandr Tyshchenko wrote:
>> Viresh, great work!
>
> Thanks Oleksandr.
>
>> Do you perhaps have corresponding users-space (virtio backend) example
>> adopted for that feature (I would like to take a look at it if poss
Hi Alejandro,
On 17/07/2023 17:03, Alejandro Vallejo wrote:
Regions must be occasionally validated for pdx compression validity. That
is, whether any of the machine addresses spanning the region have a bit set
in the pdx "hole" (which is expected to always contain zeroes). There are
a few such t
Hello all,
This series adds support for early serial printing on Power, as well as
a simple CI smoke test modeled after the riscv one.
The first patch is responsible for setting up a basic C environment with
an initial stack while the second sets up an Open Firmware serial console
and primitive e
On typical Power VMs (e.g. QEMU's -M pseries), a variety of services
including an early serial console are provided by Open Firmware.
Implement the required interfaces to call into Open Firmware and write
to the serial console.
Since Open Firmware runs in 32-bit Big Endian mode and Xen runs in
64-
Move a few more macros which have no dependencies on other headers from
xen/lib.h to xen/macros.h. Notably, this includes BUILD_BUG_ON* and
ARRAY_SIZE.
Signed-off-by: Shawn Anastasio
Reviewed-by: Jan Beulich
---
xen/include/xen/lib.h| 28
xen/include/xen/macros.
Add an initial smoke test that boots xen on a ppc64/pseries machine and
checks for a magic string. Based on the riscv smoke test.
Eventually the powernv9 (POWER9 bare metal) machine type will want to be
tested as well, but for now we only boot on pseries.
Signed-off-by: Shawn Anastasio
Reviewed-
Update ppc64/head.S to set up an initial boot stack, zero the .bss
section, and jump to C. The required setup is done using 32-bit
immediate address loads for now, but they will be changed to
TOC-relative loads once the position-independent code model is enabled.
Additionally, move the cpu0_boot_s
On 7/19/23 9:05 AM, Jan Beulich wrote:
> On 18.07.2023 22:20, Shawn Anastasio wrote:
>> +void __init boot_of_init(unsigned long vec)
>> +{
>> +int bof_chosen;
>> +
>> +of_vec = vec;
>> +
>> +/* Get a handle to the default console */
>> +bof_chosen = of_finddevice("/chosen");
>> +
> On 21 Jul 2023, at 14:24, Jan Beulich wrote:
>
> On 21.07.2023 14:16, Luca Fancellu wrote:
>> The Linux commit 33629d35090f5ce2b1b4ce78aa39954c603536d5 has
>> removed the 'snps,dwc-ahci' compatible from the generic
>> AHCI-platform driver control module selected by
>> CONFIG_SATA_AHCI_PLATFOR
On 21/07/2023 17:15, Federico Serafini wrote:
Hello Julien,
Hi,
On 21/07/23 17:44, Julien Grall wrote:> Title:
Please add "xen/arm: " to clarify this is a patch touching the Arm code.
Ok.
On 21/07/2023 16:37, Federico Serafini wrote:
Change parameter name from 'ptr' to 'v' in the funct
Hello Julien,
On 21/07/23 17:44, Julien Grall wrote:> Title:
Please add "xen/arm: " to clarify this is a patch touching the Arm code.
Ok.
On 21/07/2023 16:37, Federico Serafini wrote:
Change parameter name from 'ptr' to 'v' in the function definition thus
addressing violations of MISRA C:2
Hi Alejandro,
On 17/07/2023 17:03, Alejandro Vallejo wrote:
This patch factors out the pdx compression logic hardcoded in both ports
for the maddr<->vaddr conversion functions.
Touches both x86 and arm ports.
Signed-off-by: Alejandro Vallejo
---
xen/arch/arm/include/asm/mm.h | 3 +
Hi,
On 21/07/2023 16:22, Nicola Vetrini wrote:
Rule 5.3 has the following headline:
"An identifier declared in an inner scope shall not hide an
identifier declared in an outer scope"
The function parameters renamed in this patch are hiding a variable defined
in an enclosing scope or a function
Hi,
Title:
Please add "xen/arm: " to clarify this is a patch touching the Arm code.
On 21/07/2023 16:37, Federico Serafini wrote:
Change parameter name from 'ptr' to 'v' in the function definition thus
addressing violations of MISRA C:2012 Rule 8.3: "All declarations of an
object or function s
Change parameter name from 'ptr' to 'v' in the function definition thus
addressing violations of MISRA C:2012 Rule 8.3: "All declarations of an
object or function shall use the same names and type qualifiers".
No functional changes.
Signed-off-by: Federico Serafini
---
xen/arch/arm/include/asm/
Rule 5.3 has the following headline:
"An identifier declared in an inner scope shall not hide an
identifier declared in an outer scope"
The renaming s/sched_id/scheduler_id of the function defined in
'xen/common/sched/core.c' prevents any hiding of that function
by the many instances of omonymous
Rule 5.3 has the following headline:
"An identifier declared in an inner scope shall not hide an
identifier declared in an outer scope"
To avoid any confusion resulting from the parameter 'debug'
hiding the homonymous function declared at
'xen/arch/x86/include/asm/processor.h:428'
the rename of pa
Rule 5.3 has the following headline:
"An identifier declared in an inner scope shall not hide an
identifier declared in an outer scope"
The function parameters renamed in this patch are hiding a variable defined
in an enclosing scope or a function identifier.
The following rename is made:
- s/cfg
Rule 5.3 has the following headline:
"An identifier declared in an inner scope shall not hide an
identifier declared in an outer scope"
The function parameters renamed in this patch are hiding a variable defined
in an enclosing scope or a function identifier.
The following renames have been made:
Il giorno ven 21 lug 2023 alle ore 00:29 Stefano Stabellini <
sstabell...@kernel.org> ha scritto:
>
> Patchew automatically picked it up from xen-devel and started a pipeline
> here:
>
> https://gitlab.com/xen-project/patchew/xen/-/pipelines/939440592
>
> However the eclair-x86_64 job failed with:
Hi Julian,
On Thu, Jul 20, 2023 at 09:05:55PM +0100, Julien Grall wrote:
> Hi Alejandro,
>
> On 17/07/2023 17:03, Alejandro Vallejo wrote:
> > arm32 merely covers the XENHEAP, whereas arm64 currently covers anything in
> > the frame table. These comments highlight why arm32 doesn't need to accoun
Hi Jan,
> On 21 Jul 2023, at 16:24, Jan Beulich wrote:
>
> On 21.07.2023 16:07, Bertrand Marquis wrote:
>>> On 21 Jul 2023, at 15:08, Jan Beulich wrote:
>>> On 21.07.2023 14:27, Bertrand Marquis wrote:
So what should i keep or remove here ?
>>>
>>> My understanding so far was that "visibi
Give a name to unnamed parameters thus addressing violations of
MISRA C:2012 Rule 8.2 ("Function types shall be in prototype form with
named parameters").
Keep consistency between parameter names and types used in function
declarations and the ones used in the corresponding function
definitions, th
On 21.07.2023 16:07, Bertrand Marquis wrote:
>> On 21 Jul 2023, at 15:08, Jan Beulich wrote:
>> On 21.07.2023 14:27, Bertrand Marquis wrote:
>>> So what should i keep or remove here ?
>>
>> My understanding so far was that "visibility" merely hides all prompts
>> underneath (but then I use the com
flight 181956 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/181956/
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 Thu, Jul 20, 2023 at 12:32:34AM +, Volodymyr Babchuk wrote:
> From: Oleksandr Andrushchenko
>
> There are three originators for the PCI configuration space access:
> 1. The domain that owns physical host bridge: MMIO handlers are
> there so we can update vPCI register handlers with the va
Hi Jan,
> On 21 Jul 2023, at 15:08, Jan Beulich wrote:
>
> On 21.07.2023 14:27, Bertrand Marquis wrote:
>> Hi Jan,
>>
>>> On 21 Jul 2023, at 12:45, Jan Beulich wrote:
>>>
>>> On 21.07.2023 11:02, Bertrand Marquis wrote:
> On 21 Jul 2023, at 10:52, Jan Beulich wrote:
> On 21.07.2023 1
On Thu, Jul 20, 2023 at 12:32:33AM +, Volodymyr Babchuk wrote:
> From: Oleksandr Andrushchenko
>
> Assign SBDF to the PCI devices being passed through with bus 0.
> The resulting topology is where PCIe devices reside on the bus 0 of the
> root complex itself (embedded endpoints).
> This imple
On Thu, Jul 20, 2023 at 12:32:33AM +, Volodymyr Babchuk wrote:
> From: Oleksandr Andrushchenko
> diff --git a/xen/include/xen/sched.h b/xen/include/xen/sched.h
> index 80dd150bbf..478bd21f3e 100644
> --- a/xen/include/xen/sched.h
> +++ b/xen/include/xen/sched.h
> @@ -461,6 +461,14 @@ struct do
On Fri, Jul 21, 2023 at 03:32:27PM +0200, Roger Pau Monné wrote:
> On Thu, Jul 20, 2023 at 12:32:33AM +, Volodymyr Babchuk wrote:
> > From: Oleksandr Andrushchenko
> > +/*
> > + * According to "PCI LOCAL BUS SPECIFICATION, REV. 3.0", section "6.2.2
> > + * Device Control" the reset
flight 181934 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/181934/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-multivcpu 22 guest-start/debian.repeat fail REGR. vs.
180278
test-amd64-amd64
On Thu, Jul 20, 2023 at 12:32:33AM +, Volodymyr Babchuk wrote:
> From: Oleksandr Andrushchenko
>
> Reset the command register when assigning a PCI device to a guest:
> according to the PCI spec the PCI_COMMAND register is typically all 0's
> after reset, but this might not be true for the gue
On Thu, Jul 20, 2023 at 12:32:33AM +, Volodymyr Babchuk wrote:
> From: Oleksandr Andrushchenko
>
> Xen and/or Dom0 may have put values in PCI_COMMAND which they expect
> to remain unaltered. PCI_COMMAND_SERR bit is a good example: while the
> guest's view of this will want to be zero initiall
On 21.07.2023 14:16, Luca Fancellu wrote:
> The Linux commit 33629d35090f5ce2b1b4ce78aa39954c603536d5 has
> removed the 'snps,dwc-ahci' compatible from the generic
> AHCI-platform driver control module selected by
> CONFIG_SATA_AHCI_PLATFORM.
>
> A new driver, the DWC AHCI SATA platform driver is
On 21.07.2023 14:27, Bertrand Marquis wrote:
> Hi Jan,
>
>> On 21 Jul 2023, at 12:45, Jan Beulich wrote:
>>
>> On 21.07.2023 11:02, Bertrand Marquis wrote:
On 21 Jul 2023, at 10:52, Jan Beulich wrote:
On 21.07.2023 10:02, Bertrand Marquis wrote:
> --- a/xen/arch/arm/tee/Kconfig
>>>
On Thu, Jul 20, 2023 at 12:32:33AM +, Volodymyr Babchuk wrote:
> From: Oleksandr Andrushchenko
>
> Take into account guest's BAR view and program its p2m accordingly:
> gfn is guest's view of the BAR and mfn is the physical BAR value as set
> up by the PCI bus driver in the hardware domain.
Hi Julien,
> On 21 Jul 2023, at 14:44, Julien Grall wrote:
>
> Hi,
>
> On 21/07/2023 13:28, Bertrand Marquis wrote:
>>> On 21 Jul 2023, at 12:00, Julien Grall wrote:
>>>
>>> Hi Bertrand,
>>>
>>> On 21/07/2023 10:23, Bertrand Marquis wrote:
Rework TEE mediators to put them under a submen
On Thu 2023-07-20 16:31:16, Stefano Stabellini wrote:
> On Thu, 20 Jul 2023, Petr Mladek wrote:
> > On Wed 2023-07-19 18:46:08, Stefano Stabellini wrote:
> > > On Wed, 19 Jul 2023, Petr Mladek wrote:
> > > > I see the following warning from free_irq() in 6.5-rc2 when running
> > > > livepatching se
Hi,
On 21/07/2023 13:28, Bertrand Marquis wrote:
On 21 Jul 2023, at 12:00, Julien Grall wrote:
Hi Bertrand,
On 21/07/2023 10:23, Bertrand Marquis wrote:
Rework TEE mediators to put them under a submenu in Kconfig.
The submenu is only visible if UNSUPPORTED is activated as all currently
exist
On Fri, Jul 21, 2023 at 01:16:27PM +0100, Luca Fancellu wrote:
> The Linux commit 33629d35090f5ce2b1b4ce78aa39954c603536d5 has
> removed the 'snps,dwc-ahci' compatible from the generic
> AHCI-platform driver control module selected by
> CONFIG_SATA_AHCI_PLATFORM.
>
> A new driver, the DWC AHCI SAT
Hi,
> On 21 Jul 2023, at 12:00, Julien Grall wrote:
>
> Hi Bertrand,
>
> On 21/07/2023 10:23, Bertrand Marquis wrote:
>> Rework TEE mediators to put them under a submenu in Kconfig.
>> The submenu is only visible if UNSUPPORTED is activated as all currently
>> existing mediators are UNSUPPORTED
Hi Jan,
> On 21 Jul 2023, at 12:45, Jan Beulich wrote:
>
> On 21.07.2023 11:02, Bertrand Marquis wrote:
>>> On 21 Jul 2023, at 10:52, Jan Beulich wrote:
>>> On 21.07.2023 10:02, Bertrand Marquis wrote:
--- a/xen/arch/arm/tee/Kconfig
+++ b/xen/arch/arm/tee/Kconfig
@@ -1,7 +1,17 @@
The Linux commit 33629d35090f5ce2b1b4ce78aa39954c603536d5 has
removed the 'snps,dwc-ahci' compatible from the generic
AHCI-platform driver control module selected by
CONFIG_SATA_AHCI_PLATFORM.
A new driver, the DWC AHCI SATA platform driver is now implemented
and handles the above compatible when
On Fri, Jul 21, 2023 at 12:50:23PM +0200, Jan Beulich wrote:
> On 21.07.2023 12:36, Rahul Singh wrote:
> >> On 20 Jul 2023, at 1:32 am, Volodymyr Babchuk
> >> wrote:
> >> @@ -599,34 +681,50 @@ static int cf_check init_bars(struct pci_dev *pdev)
> >> bars[i].size = size;
> >> bars[
On Thu, Jul 20, 2023 at 12:32:32AM +, Volodymyr Babchuk wrote:
> From: Oleksandr Andrushchenko
>
> Instead of handling a single range set, that contains all the memory
> regions of all the BARs and ROM, have them per BAR.
> As the range sets are now created when a PCI device is added and dest
On 21.07.2023 12:36, Rahul Singh wrote:
>> On 20 Jul 2023, at 1:32 am, Volodymyr Babchuk
>> wrote:
>> @@ -599,34 +681,50 @@ static int cf_check init_bars(struct pci_dev *pdev)
>> bars[i].size = size;
>> bars[i].prefetchable = val & PCI_BASE_ADDRESS_MEM_PREFETCH;
>
> I think there
On 21.07.2023 11:02, Bertrand Marquis wrote:
>> On 21 Jul 2023, at 10:52, Jan Beulich wrote:
>> On 21.07.2023 10:02, Bertrand Marquis wrote:
>>> --- a/xen/arch/arm/tee/Kconfig
>>> +++ b/xen/arch/arm/tee/Kconfig
>>> @@ -1,7 +1,17 @@
>>> +menu "TEE mediators"
>>> + visible if UNSUPPORTED
>>
>> With
flight 181948 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/181948/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64-xsm 6 xen-buildfail REGR. vs. 181941
Tests which
flight 181927 xen-unstable real [real]
flight 181950 xen-unstable real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/181927/
http://logs.test-lab.xenproject.org/osstest/logs/181950/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd6
Hi Volodymyr,
> On 20 Jul 2023, at 1:32 am, Volodymyr Babchuk
> wrote:
>
> From: Oleksandr Andrushchenko
>
> Add relevant vpci register handlers when assigning PCI device to a domain
> and remove those when de-assigning. This allows having different
> handlers for different domains, e.g. hwdo
On Fri, Jul 14, 2023 at 11:45:34AM -0600, Rob Herring wrote:
> The DT of_device.h and of_platform.h date back to the separate
> of_platform_bus_type before it as merged into the regular platform bus.
> As part of that merge prepping Arm DT support 13 years ago, they
> "temporarily" include each oth
Hi,
On 21/07/2023 08:28, Nicola Vetrini wrote:
On 20/07/23 17:54, Julien Grall wrote:
Hi Nicola,
On 20/07/2023 15:29, Nicola Vetrini wrote:
The local variables with type 'struct arm_smccc_res' are initialized
just after the declaration to avoid any possible read usage prior
to any write usage
Hi Nicola,
I would add "to please ECLAIR" in the commit title.
On 21/07/2023 07:49, Nicola Vetrini wrote:
This function is refactored to avoid using a
local dummy variable that served as a fallback
if the parameter 't' is NULL.
Storing the address of that variable into 't' caused
static analys
Hi Bertrand,
On 21/07/2023 10:23, Bertrand Marquis wrote:
Rework TEE mediators to put them under a submenu in Kconfig.
The submenu is only visible if UNSUPPORTED is activated as all currently
existing mediators are UNSUPPORTED.
While there rework a bit the configuration so that OP-TEE and FF-A
Rework TEE mediators to put them under a submenu in Kconfig.
The submenu is only visible if UNSUPPORTED is activated as all currently
existing mediators are UNSUPPORTED.
While there rework a bit the configuration so that OP-TEE and FF-A
mediators are selecting the generic TEE interface instead of
Hi Bertrand,
On 21/07/2023 10:07, Bertrand Marquis wrote:
On 21 Jul 2023, at 10:52, Julien Grall wrote:
+
config OPTEE
- bool "Enable OP-TEE mediator"
+ bool "Enable OP-TEE mediator (UNSUPPORTED)" if UNSUPPORTED
Given this is under 'TEE mediators', do we still need the 'if UNSUPPORTED'?
Hi Julien,
> On 21 Jul 2023, at 10:52, Julien Grall wrote:
>
> Hi Bertrand,
>
> On 21/07/2023 09:02, Bertrand Marquis wrote:
>> Rework TEE mediators to put them under a submenu in Kconfig.
>> The submenu is only visible if UNSUPPORTED is activated as all currently
>> existing mediators are UNSU
Change parameter names in function declarations to be consistent with
the ones used in the correponding definitions, thus addressing
violations of MISRA C:2012 Rule 8.3: "All declarations of an object or
function shall use the same names and type qualifiers".
No functional changes.
Signed-off-by:
Hi Jan,
> On 21 Jul 2023, at 10:52, Jan Beulich wrote:
>
> On 21.07.2023 10:02, Bertrand Marquis wrote:
>> --- a/xen/arch/arm/tee/Kconfig
>> +++ b/xen/arch/arm/tee/Kconfig
>> @@ -1,7 +1,17 @@
>> +menu "TEE mediators"
>> + visible if UNSUPPORTED
>
> With this ...
>
>> +config TEE
>> + bool
>> +
On 21.07.2023 10:02, Bertrand Marquis wrote:
> --- a/xen/arch/arm/tee/Kconfig
> +++ b/xen/arch/arm/tee/Kconfig
> @@ -1,7 +1,17 @@
> +menu "TEE mediators"
> + visible if UNSUPPORTED
With this ...
> +config TEE
> + bool
> + default n
> + help
> + This option enables generic TE
Hi Bertrand,
On 21/07/2023 09:02, Bertrand Marquis wrote:
Rework TEE mediators to put them under a submenu in Kconfig.
The submenu is only visible if UNSUPPORTED is activated as all currently
existing mediators are UNSUPPORTED.
While there rework a bit the configuration so that OP-TEE and FF-A
On 21.07.2023 09:43, Roger Pau Monné wrote:
> On Fri, Jul 21, 2023 at 08:02:33AM +0200, Jan Beulich wrote:
>> On 20.07.2023 18:14, Roger Pau Monné wrote:
>>> Strictly speaking however the init
>>> handlers don't require the lock in write mode unless we use such
>>> locking to get exclusive access
Hi Stewart,
> On 21 Jul 2023, at 5:54 am, Stewart Hildebrand
> wrote:
>
> On 7/7/23 07:04, Rahul Singh wrote:
>> Hi Stewart,
>>
>>> On 7 Jul 2023, at 2:47 am, Stewart Hildebrand
>>> wrote:
>>>
>>> Remove is_hardware_domain check in has_vpci, and select
>>> HAS_VPCI_GUEST_SUPPORT
>>> in Kco
Hello, Julien, Stefano,
Thank you for your replies.
On 21/07/2023 02:25, Stefano Stabellini wrote:
>
> On Thu, 20 Jul 2023, Julien Grall wrote:
>> (+ Juergen)
>>
>> On 19/07/2023 17:13, Andrei Cherechesu (OSS) wrote:
>>> Hello,
>>
>> Hi Andrei,
>>
>>> As we're running Xen 4.17 (with platform-rel
On Thu, Jul 6, 2023 at 8:29 AM Viresh Kumar wrote:
> Currently, the grant mapping related device tree properties are added if
> the backend domain is not Dom0. While Dom0 is privileged and can do
> foreign mapping for the entire guest memory, it is still desired for
> Dom0 to access guest's memor
Rework TEE mediators to put them under a submenu in Kconfig.
The submenu is only visible if UNSUPPORTED is activated as all currently
existing mediators are UNSUPPORTED.
While there rework a bit the configuration so that OP-TEE and FF-A
mediators are selecting the generic TEE interface instead of
flight 181944 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/181944/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 925c445fd37bf529ca78f9d6c416cca37c7e6da5
baseline version:
ovmf c6b512962e92ae54a895b
On Fri, Jul 21, 2023 at 08:02:33AM +0200, Jan Beulich wrote:
> On 20.07.2023 18:14, Roger Pau Monné wrote:
> > Strictly speaking however the init
> > handlers don't require the lock in write mode unless we use such
> > locking to get exclusive access to all the devices assigned to the
> > domain B
On 20/07/23 17:54, Julien Grall wrote:
Hi Nicola,
On 20/07/2023 15:29, Nicola Vetrini wrote:
The local variables with type 'struct arm_smccc_res' are initialized
just after the declaration to avoid any possible read usage prior
to any write usage, which would constitute a violation of
MISRA
Hi Julien,
> On 21 Jul 2023, at 00:29, Julien Grall wrote:
>
> Hi Bertrand,
>
> On 20/07/2023 11:20, Bertrand Marquis wrote:
>> Hi Jens,
>>> On 17 Jul 2023, at 09:20, Jens Wiklander wrote:
>>>
>>> Adds a FF-A version 1.1 [1] mediator to communicate with a Secure
>>> Partition in secure world.
95 matches
Mail list logo
