RE: [PATCH v2 0/8] x86emul: a few small steps towards disintegration

Henry Wang posted 8 patches 1 year, 9 months ago
Only 0 patches received!
There is a newer version of this series
RE: [PATCH v2 0/8] x86emul: a few small steps towards disintegration
Posted by Henry Wang 1 year, 9 months ago
Hi,

It seems that this series has been stale for nearly a month, with nothing heard
from maintainers. So I am sending this email as a gentle reminder for maintainers.
Thanks!

Kind regards,
Henry

> -----Original Message-----
> Subject: [PATCH v2 0/8] x86emul: a few small steps towards disintegration
> 
> ... of the huge monolithic source file. The series is largely code
> movement and hence has the intention of not incurring any functional
> change.
> 
> It has now been almost a year since the v1 submission, without having
> had any feedback. Some re-basing was necessary in the meantime, and a
> new patch (the last one) has been added - even if seemingly unrelated,
> it was in this context where I did think of that possible adjustment
> (which may want to be viewed somewhat RFC, as I know there are
> reservations against the use of -Os).
> 
> 1: split off opcode 0f01 handling
> 2: split off opcode 0fae handling
> 3: split off opcode 0fc7 handling
> 4: split off FPU opcode handling
> 5: split off insn decoding
> 6: move x86_emul_blk() to separate source file
> 7: move various utility functions to separate source files
> 8: build with -Os
> 
> Jan

Re: [PATCH v2 0/8] x86emul: a few small steps towards disintegration
Posted by Jan Beulich 1 year, 9 months ago
On 06.07.2022 09:31, Henry Wang wrote:
> It seems that this series has been stale for nearly a month, with nothing heard
> from maintainers. So I am sending this email as a gentle reminder for maintainers.

A month? That's only since v2 submission. See ...

>> -----Original Message-----
>> Subject: [PATCH v2 0/8] x86emul: a few small steps towards disintegration
>>
>> ... of the huge monolithic source file. The series is largely code
>> movement and hence has the intention of not incurring any functional
>> change.
>>
>> It has now been almost a year since the v1 submission, without having
>> had any feedback.

... here.

Jan

>> Some re-basing was necessary in the meantime, and a
>> new patch (the last one) has been added - even if seemingly unrelated,
>> it was in this context where I did think of that possible adjustment
>> (which may want to be viewed somewhat RFC, as I know there are
>> reservations against the use of -Os).
>>
>> 1: split off opcode 0f01 handling
>> 2: split off opcode 0fae handling
>> 3: split off opcode 0fc7 handling
>> 4: split off FPU opcode handling
>> 5: split off insn decoding
>> 6: move x86_emul_blk() to separate source file
>> 7: move various utility functions to separate source files
>> 8: build with -Os
>>
>> Jan
>
RE: [PATCH v2 0/8] x86emul: a few small steps towards disintegration
Posted by Henry Wang 1 year, 9 months ago
Hi Jan,

> -----Original Message-----
> From: Jan Beulich <jbeulich@suse.com>
> 
> On 06.07.2022 09:31, Henry Wang wrote:
> > It seems that this series has been stale for nearly a month, with nothing
> heard
> > from maintainers. So I am sending this email as a gentle reminder for
> maintainers.
> 
> A month? That's only since v2 submission. See ...

Oh, yes indeed. Thank you for the background information, normally I use
patchwork to track series I did missed the v1 as v1 is superseded by v2
there (thus "a month", but honestly this series is stale for more than a year...).

> 
> >> -----Original Message-----
> >> Subject: [PATCH v2 0/8] x86emul: a few small steps towards disintegration
> >>
> >> ... of the huge monolithic source file. The series is largely code
> >> movement and hence has the intention of not incurring any functional
> >> change.
> >>
> >> It has now been almost a year since the v1 submission, without having
> >> had any feedback.

To possibly make the ping better, I will try add Wei Liu's another 2 emails in the
CC list (I was once told by him in this way he will be more likely to notice the email)
and put Andrew as TO.

Kind regards,
Henry

> 
> ... here.
> 
> Jan
> 
> >> Some re-basing was necessary in the meantime, and a
> >> new patch (the last one) has been added - even if seemingly unrelated,
> >> it was in this context where I did think of that possible adjustment
> >> (which may want to be viewed somewhat RFC, as I know there are
> >> reservations against the use of -Os).
> >>
> >> 1: split off opcode 0f01 handling
> >> 2: split off opcode 0fae handling
> >> 3: split off opcode 0fc7 handling
> >> 4: split off FPU opcode handling
> >> 5: split off insn decoding
> >> 6: move x86_emul_blk() to separate source file
> >> 7: move various utility functions to separate source files
> >> 8: build with -Os
> >>
> >> Jan
> >