On 6/11/24 02:21, Alex Bennée wrote:
Pierrick Bouvier writes:
On 6/10/24 13:29, Manos Pitsidianakis wrote:
On Mon, 10 Jun 2024 22:37, Pierrick Bouvier wrote:
Hello Manos,
Excellent work, and thanks for posting this RFC!
IMHO, having patches 2 and 5 splitted is a bit confusing, and expo
On Tue, Jun 11, 2024 at 01:41:57PM +0300, Manos Pitsidianakis wrote:
> Date: Tue, 11 Jun 2024 13:41:57 +0300
> From: Manos Pitsidianakis
> Subject: Re: [RFC PATCH v1 0/6] Implement ARM PL011 in Rust
>
> > Currently, pl011 exclusively occupies a cargo as a package. In the
>
On Tue, Jun 11, 2024 at 03:16:19PM +0200, Paolo Bonzini wrote:
> On Tue, Jun 11, 2024 at 10:22 AM Daniel P. Berrangé
> wrote:
> >
> > On Mon, Jun 10, 2024 at 09:22:35PM +0300, Manos Pitsidianakis wrote:
> > > Hello everyone,
> > >
> > > This is an early draft of my work on implementing a very sim
On Tue, Jun 11, 2024 at 10:22 AM Daniel P. Berrangé wrote:
>
> On Mon, Jun 10, 2024 at 09:22:35PM +0300, Manos Pitsidianakis wrote:
> > Hello everyone,
> >
> > This is an early draft of my work on implementing a very simple device,
> > in this case the ARM PL011 (which in C code resides in hw/char
On Mon, Jun 10, 2024 at 10:47 PM Stefan Hajnoczi wrote:
> On Mon, 10 Jun 2024 at 16:27, Manos Pitsidianakis
> wrote:
> >
> > On Mon, 10 Jun 2024 22:59, Stefan Hajnoczi wrote:
> > >> What are the issues with not using the compiler, rustc, directly?
> > >> -
On Tue, Jun 11, 2024 at 01:51:13PM +0100, Alex Bennée wrote:
> Daniel P. Berrangé writes:
>
> > On Tue, Jun 11, 2024 at 01:58:10PM +0300, Manos Pitsidianakis wrote:
> >> On Tue, 11 Jun 2024 13:57, "Daniel P. Berrangé"
> >> wrote:
> >> > On Mon, Jun 10, 2024 at 11:29:36PM +0300, Manos Pitsidiana
Hello Antonio!
On Tue, 11 Jun 2024 15:45, Antonio Caggiano wrote:
Hi there :)
On 11/06/2024 12:58, Manos Pitsidianakis wrote:
On Tue, 11 Jun 2024 13:57, "Daniel P. Berrangé"
wrote:
On Mon, Jun 10, 2024 at 11:29:36PM +0300, Manos Pitsidianakis wrote:
On Mon, 10 Jun 2024 22:37, Pierrick Bouvi
Daniel P. Berrangé writes:
> On Tue, Jun 11, 2024 at 01:58:10PM +0300, Manos Pitsidianakis wrote:
>> On Tue, 11 Jun 2024 13:57, "Daniel P. Berrangé" wrote:
>> > On Mon, Jun 10, 2024 at 11:29:36PM +0300, Manos Pitsidianakis wrote:
>> > > On Mon, 10 Jun 2024 22:37, Pierrick Bouvier
>> > > wrote:
Hi there :)
On 11/06/2024 12:58, Manos Pitsidianakis wrote:
On Tue, 11 Jun 2024 13:57, "Daniel P. Berrangé"
wrote:
On Mon, Jun 10, 2024 at 11:29:36PM +0300, Manos Pitsidianakis wrote:
On Mon, 10 Jun 2024 22:37, Pierrick Bouvier
wrote:
> Hello Manos,
> > On 6/10/24 11:22, Manos Pitsidianakis
On Tue, 11 Jun 2024 14:09, "Daniel P. Berrangé" wrote:
On Tue, Jun 11, 2024 at 01:58:10PM +0300, Manos Pitsidianakis wrote:
On Tue, 11 Jun 2024 13:57, "Daniel P. Berrangé" wrote:
> On Mon, Jun 10, 2024 at 11:29:36PM +0300, Manos Pitsidianakis wrote:
> > On Mon, 10 Jun 2024 22:37, Pierrick Bouv
On Tue, Jun 11, 2024 at 01:58:10PM +0300, Manos Pitsidianakis wrote:
> On Tue, 11 Jun 2024 13:57, "Daniel P. Berrangé" wrote:
> > On Mon, Jun 10, 2024 at 11:29:36PM +0300, Manos Pitsidianakis wrote:
> > > On Mon, 10 Jun 2024 22:37, Pierrick Bouvier
> > > wrote:
> > > > Hello Manos,
> > > > > On
On Tue, 11 Jun 2024 13:57, "Daniel P. Berrangé" wrote:
On Mon, Jun 10, 2024 at 11:29:36PM +0300, Manos Pitsidianakis wrote:
On Mon, 10 Jun 2024 22:37, Pierrick Bouvier wrote:
> Hello Manos,
>
> On 6/10/24 11:22, Manos Pitsidianakis wrote:
> > Hello everyone,
> >
> > This is an early draft o
On Mon, Jun 10, 2024 at 11:29:36PM +0300, Manos Pitsidianakis wrote:
> On Mon, 10 Jun 2024 22:37, Pierrick Bouvier
> wrote:
> > Hello Manos,
> >
> > On 6/10/24 11:22, Manos Pitsidianakis wrote:
> > > Hello everyone,
> > >
> > > This is an early draft of my work on implementing a very simple dev
On Tue, 11 Jun 2024 11:18, "Daniel P. Berrangé" wrote:
On Mon, Jun 10, 2024 at 09:22:35PM +0300, Manos Pitsidianakis wrote:
What are the issues with not using the compiler, rustc, directly?
-
[whataretheissueswith] Back to [TOC]
1
On Tue, 11 Jun 2024 12:45, Zhao Liu wrote:
On Tue, Jun 11, 2024 at 09:22:44AM +0100, Daniel P. Berrangé wrote:
On Mon, Jun 10, 2024 at 09:22:35PM +0300, Manos Pitsidianakis wrote:
> Hello everyone,
>
> This is an early draft of my work on implementing a very simple device,
> in this case the
On Tue, 11 Jun 2024 11:22, "Daniel P. Berrangé" wrote:
On Mon, Jun 10, 2024 at 09:22:35PM +0300, Manos Pitsidianakis wrote:
Hello everyone,
This is an early draft of my work on implementing a very simple device,
in this case the ARM PL011 (which in C code resides in hw/char/pl011.c
and is us
On Tue, Jun 11, 2024 at 09:18:25AM +0100, Daniel P. Berrangé wrote:
> Date: Tue, 11 Jun 2024 09:18:25 +0100
> From: "Daniel P. Berrangé"
> Subject: Re: [RFC PATCH v1 0/6] Implement ARM PL011 in Rust
>
> On Mon, Jun 10, 2024 at 09:22:35PM +0300, Manos Pitsidianakis wrote
Stefan Hajnoczi writes:
> On Mon, 10 Jun 2024 at 16:27, Manos Pitsidianakis
> wrote:
>>
>> On Mon, 10 Jun 2024 22:59, Stefan Hajnoczi wrote:
>> >>
>> >> 1. Tooling
>> >>Mostly writing up the build-sys tooling to do so. Ideally we'd
>> >>compile everything without cargo but rustc direct
On Tue, Jun 11, 2024 at 09:22:44AM +0100, Daniel P. Berrangé wrote:
> Date: Tue, 11 Jun 2024 09:22:44 +0100
> From: "Daniel P. Berrangé"
> Subject: Re: [RFC PATCH v1 0/6] Implement ARM PL011 in Rust
>
> On Mon, Jun 10, 2024 at 09:22:35PM +0300, Manos Pitsidianakis
Pierrick Bouvier writes:
> On 6/10/24 13:29, Manos Pitsidianakis wrote:
>> On Mon, 10 Jun 2024 22:37, Pierrick Bouvier
>> wrote:
>>> Hello Manos,
>>>
>>> Excellent work, and thanks for posting this RFC!
>>>
>>> IMHO, having patches 2 and 5 splitted is a bit confusing, and exposing
>>> (tempora
Daniel P. Berrangé writes:
> On Mon, Jun 10, 2024 at 11:29:36PM +0300, Manos Pitsidianakis wrote:
>> On Mon, 10 Jun 2024 22:37, Pierrick Bouvier
>> wrote:
>> > > The staticlib artifact contains a bunch of mangled .o objects?
>> > > ==
On Mon, Jun 10, 2024 at 04:47:33PM -0400, Stefan Hajnoczi wrote:
> On Mon, 10 Jun 2024 at 16:27, Manos Pitsidianakis
> wrote:
> >
> > On Mon, 10 Jun 2024 22:59, Stefan Hajnoczi wrote:
> > >> Should QEMU use third-party dependencies?
> > >> -
> > >> [shouldq
On Mon, Jun 10, 2024 at 09:22:35PM +0300, Manos Pitsidianakis wrote:
> Hello everyone,
>
> This is an early draft of my work on implementing a very simple device,
> in this case the ARM PL011 (which in C code resides in hw/char/pl011.c
> and is used in hw/arm/virt.c).
looking at the diffstat:
On Mon, Jun 10, 2024 at 09:22:35PM +0300, Manos Pitsidianakis wrote:
> What are the issues with not using the compiler, rustc, directly?
> -
> [whataretheissueswith] Back to [TOC]
>
> 1. Tooling
>Mostly writing up the build-sys to
On 10/6/24 21:59, Stefan Hajnoczi wrote:
On Mon, 10 Jun 2024 at 14:23, Manos Pitsidianakis
wrote:
Should QEMU provide wrapping Rust APIs over QEMU internals?
---
[qemuprovidewrappingrustapis] Back to [TOC]
My personal opinion is no, wi
On Mon, Jun 10, 2024 at 11:29:36PM +0300, Manos Pitsidianakis wrote:
> On Mon, 10 Jun 2024 22:37, Pierrick Bouvier
> wrote:
> > > The staticlib artifact contains a bunch of mangled .o objects?
> > > ==
> > > [staticlibmangledobjects] Bac
On Tue, 11 Jun 2024 00:38, Pierrick Bouvier wrote:
Maybe it could be better if build.rs file was *not* needed for new
devices/folders, and could be abstracted as a detail of the python
wrapper script instead of something that should be committed.
That'd mean you cannot work on the rust files
On 6/10/24 13:29, Manos Pitsidianakis wrote:
On Mon, 10 Jun 2024 22:37, Pierrick Bouvier wrote:
Hello Manos,
On 6/10/24 11:22, Manos Pitsidianakis wrote:
Hello everyone,
This is an early draft of my work on implementing a very simple device,
in this case the ARM PL011 (which in C code reside
On Mon, 10 Jun 2024 at 16:27, Manos Pitsidianakis
wrote:
>
> On Mon, 10 Jun 2024 22:59, Stefan Hajnoczi wrote:
> >> What are the issues with not using the compiler, rustc, directly?
> >> -
> >> [whataretheissueswith] Back to [TOC]
>
On Mon, 10 Jun 2024 22:37, Pierrick Bouvier wrote:
Hello Manos,
On 6/10/24 11:22, Manos Pitsidianakis wrote:
Hello everyone,
This is an early draft of my work on implementing a very simple device,
in this case the ARM PL011 (which in C code resides in hw/char/pl011.c
and is used in hw/arm/vir
On Mon, 10 Jun 2024 22:59, Stefan Hajnoczi wrote:
What are the issues with not using the compiler, rustc, directly?
-
[whataretheissueswith] Back to [TOC]
1. Tooling
Mostly writing up the build-sys tooling to do so. Ideally we'd
On Mon, 10 Jun 2024 at 14:23, Manos Pitsidianakis
wrote:
>
> Hello everyone,
>
> This is an early draft of my work on implementing a very simple device,
> in this case the ARM PL011 (which in C code resides in hw/char/pl011.c
> and is used in hw/arm/virt.c).
>
> The device is functional, with copi
Hello Manos,
On 6/10/24 11:22, Manos Pitsidianakis wrote:
Hello everyone,
This is an early draft of my work on implementing a very simple device,
in this case the ARM PL011 (which in C code resides in hw/char/pl011.c
and is used in hw/arm/virt.c).
The device is functional, with copied logic fr
Hello everyone,
This is an early draft of my work on implementing a very simple device,
in this case the ARM PL011 (which in C code resides in hw/char/pl011.c
and is used in hw/arm/virt.c).
The device is functional, with copied logic from the C code but with
effort not to make a direct C to Ru
34 matches
Mail list logo
