On 12/04/2024 11:35, Edgar E. Iglesias wrote:
> On Fri, Apr 12, 2024 at 1:23 AM Stefano Stabellini
> wrote:
>
> -Vikram +Edgar
>
> On Thu, 11 Apr 2024, Andrei Cherechesu wrote:
>>> I've managed to successfully get a DomU up and running with the rootfs
>>> b
full logs for the "xl create" command [0] and for DomU's dmesg [1].
Any ideas as to why that might happen, some debugging insights, or maybe some
configuration details I could have overlooked?
Thank you very much for your help once again.
Regards,
Andrei Cherechesu
[0]
https://p
, and we're also looking
forward to the progress on the rust-vmm initiative.
Regards,
Andrei Cherechesu,
NXP Semiconductors
[0] https://github.com/xen-troops/virtio-disk
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,
&g
is
reachable via SSH and can continue to process the workload.
We've not been able so far to figure out why this happens, so any help would be
appreciated. If you need other Domain configuration details or any inputs from
our side, let us know.
Thank you,
Andrei Cherechesu
Hi Julien,
On 21/03/2023 18:56, Julien Grall wrote:
> Hi Andrei,
>
> I realized this has already been merged. But I would like to point out a
> few things for future series.
>
> On 13/03/2023 13:08, Andrei Cherechesu (OSS) wrote:
>> From: Andrei Cherechesu
&g
From: Andrei Cherechesu
This 2-patch series fixes the parsing of the ARM Generic Timer
interrupts from the device tree.
If the generic timer interrupts order in the DT was different than
the expected order in Xen code, these interrupts would no longer be
correctly parsed and registered by Xen
From: Andrei Cherechesu
Moved implementation for the function which parses the IRQs of a DT
node by the "interrupt-names" property from the SMMU-v3 driver
to the IRQ core code and made it non-static to be used as helper.
Also changed it to receive a "struct dt_device_node*"
From: Andrei Cherechesu
Added support for parsing the ARM generic timer interrupts DT
node by the "interrupt-names" property, if it is available.
If not available, the usual parsing based on the expected
IRQ order is performed.
Also treated returning 0 as an error case for the
platfo
From: Andrei Cherechesu
Added support for parsing the ARM generic timer interrupts DT
node by the "interrupt-names" property, if it is available.
If not available, the usual parsing based on the expected
IRQ order is performed.
Also changed to treating returning 0 as an
From: Andrei Cherechesu
Moved implementation for the function which parses the IRQs of a DT
node by the "interrupt-names" property from the SMMU-v3 driver
to the IRQ core code and made it non-static to be used as helper.
Also changed it to receive a "struct dt_device_node*"
From: Andrei Cherechesu
This 2-patch series fixes the parsing of the ARM Generic Timer
interrupts from the device tree.
If the generic timer interrupts order in the DT was different than
the expected order in Xen code, these interrupts would no longer be
correctly parsed and registered by Xen
:
>>>>>>
>>>>>>
>>>>>> Hi Michal,
>>>>>>
>>>>>>> On 9 Mar 2023, at 11:05, Michal Orzel wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>&g
On 07/03/2023 17:38, Bertrand Marquis wrote:
> Hi Andrei,
>
>> On 7 Mar 2023, at 11:09, Andrei Cherechesu (OSS)
>> wrote:
>>
>> From: Andrei Cherechesu
>>
>> Added support for parsing the ARM generic timer interrupts DT
>> node by th
ainers in CC. I added them now.
>
>> On 7 Mar 2023, at 11:09, Andrei Cherechesu (OSS)
>> wrote:
>>
>> From: Andrei Cherechesu
>>
>> This 2-patch series fixes the parsing of the ARM Generic Timer
>> interrupts from the device tree.
>>
>
From: Andrei Cherechesu
Added support for parsing the ARM generic timer interrupts DT
node by the "interrupt-names" property, if it is available.
If not available, the usual parsing based on the expected
IRQ order is performed.
Also added the "hyp-virt" PPI to the timer P
From: Andrei Cherechesu
Moved implementation for the function which parses the IRQs of a DT
node by the "interrupt-names" property from the SMMU-v3 driver
to the IRQ core code and made it non-static to be used as helper.
Also changed it to receive a "struct dt_device_node*"
From: Andrei Cherechesu
This 2-patch series fixes the parsing of the ARM Generic Timer
interrupts from the device tree.
If the generic timer interrupts order in the DT was different than
the expected order in Xen code, these interrupts would no longer be
correctly parsed and registered by Xen
From: Andrei Cherechesu
Normally, the Imagebuilder would precompute the sizes of the loaded
binaries and addresses where they are loaded before generating the
script, and the sizes and addresses that needed to be provided to
Xen via /chosen would be hardcoded in the boot script.
Added an option
From: Andrei Cherechesu
This sent patch adds support for dynamically computing the addresses
and sizes for loaded binaries via the boot script generated by
Imagebuilder.
Compared to the v3 version of the patch, this includes Stefano's
suggestions of not adding as many "if"
From: Andrei Cherechesu
If the "BOOT_CMD" variable is set to "none" inside the config
file, the boot command (i.e. "booti") will not by added to the
generated script, to allow the user to customize the u-boot env
or the device-tree after executing the script comman
From: Andrei Cherechesu
Added the parsing for APPEND_EXTRA_CMDS variable, which enables the
user to specify the path to a text file that contains, on each line,
u-boot commands that will be added to the generated script as
"fixups", before the boot command.
The file
From: Andrei Cherechesu
Hello,
This the v3 version for the patches which have not yet been commited.
Changes in v3:
- Dropped the [PATCH v2 1/4] from the previous series since it's already
been commited
- For PATCH 1/3: No changes
- For PATCH 2/3: Dropped the "-a" parameter and inste
From: Andrei Cherechesu
Normally, the script would precompute the sizes of the loaded binaries
and addresses where they are loaded before generating the script,
and the sizes and addresses that needed to be provided to Xen via
/chosen would be hardcoded in the boot script.
Added option via &qu
From: Andrei Cherechesu
Added the "-a" parameter which stands for APPEND_EXTRA_CMDS option,
which enables the user to specify the path to a text file that contains,
on each line, u-boot commands that will be added to the generated script as
"fixups", before the boot command.
From: Andrei Cherechesu
Normally, the script would precompute the sizes of the loaded binaries
and addresses where they are loaded before generating the script,
and the sizes and addresses that needed to be provided to Xen via
/chosen would be hardcoded in the boot script.
Added option via &qu
From: Andrei Cherechesu
Hello,
Sorry for the late re-submission of patches, but I had some
company internal work to take care of. I managed to include the
changes mentioned by Stefano S. and Ayan K. H. in the discussions
for the first version of patches.
Changes in v2:
- Dropped the patch
From: Andrei Cherechesu
Added support for prepending path to file names in the final generated
u-boot script, for the use-case where we have the files in a separate
folder that can be accessed with a given $LOAD_CMD.
For example, we can have "fatload mmc 0:2" as LOAD_CMD but the
f
From: Andrei Cherechesu
If the "BOOT_CMD" variable is set to "none" inside the config
file, the boot command (i.e. "booti") will not by added to the
generated script, to allow the user to customize the u-boot env
or the device-tree after executing the script comman
atic IP configuration for DomU in the config file,
and because it automatically enables eth0 at boot time, I no longer get the
oops, but a panic directly.
Thank you very much for your help,
Andrei Cherechesu,
NXP Semiconductors
hat it hangs in:
console_init_preirq() -> __putstr(xen_banner()) -> sercon_puts() ->
serial_puts() -> __serial_putc(),
where it spins at line 178:
/* Synchronous finite-capacity transmitter. */
while ( !(n = port->driver->tx_ready(port)) )
cpu_relax();
Which is a bit strange, considering that my serial device is asynchronous,
I think it should not get there. But it gets on that "else" branch because
port->txbuf is actually NULL at line 120 when it performs the check, and
it does not enter the branch for asynchronous transmitters.
Thanks,
Andrei Cherechesu,
NXP Semiconductors
t_used_by(dev, DOMID_XEN);
>
> Devices that are marked as "used by Xen" are not exposed to dom0, so you
> shouldn't see the ttyLF0 device come up in Linux at all.
I've checked my Xen UART Driver and that call is there. So ttyLF0 should be
marked for Xen to use.
I don't have any ideas why this happens.
I've attached the driver [0], if you want to take a look.
[0] https://pastebin.com/PuXi50H0
Thanks,
Andrei Cherechesu,
NXP Semiconductors
> On Thu, 13 Feb 2020, Andrei Cherechesu wrote:
> > Hello,
> >
> > I used the Xen from Stefano's tree and made the updates to the partial
> > dtb that he specified.
> >
> > > This is mostly likely because Linux is trying to access a region
> >
-Original Message-
From: Julien Grall
Sent: Thursday, February 13, 2020 00:03
To: Stefano Stabellini ; Andrei Cherechesu
Cc: Jorge Pereira ; xen-devel@lists.xenproject.org
Subject: Re: [Xen-devel] Having a DOM-U guest with 1:1 mapping in the second
stage MMU.
Hello,
I used the Xen
[[ Sorry. Needed to send another mail because I forgot to add xen-devel lists
to CC. ]]
Hello,
I applied your direct-map patch, Stefano, on top of RELEASE-4.13.0
Xen.
I also took your advice and used the Imagebuilder tool to setup my
u-boot environment. I modified the tool to allow SDCard
> On Mon, 16 Dec 2019, Julien Grall wrote:
> > On 16/12/2019 23:05, Stefano Stabellini wrote:
> > > On Mon, 16 Dec 2019, Julien Grall wrote:
> > > > On 16/12/2019 18:02, Andrei Cherechesu wrote:
> > > > But even with this patch, RAM in DomU is not
Hello,
My name is Andrei Cherechesu and I'm a Software Engineer at NXP
Semiconductors in the Automotive department, Linux BSP Team.
I would like to tell you have done a great job so far with Xen.
Thus, we have ported and integrated Xen ARM in the Linux BSP for our
boards.
Currently, we
37 matches
Mail list logo
