On 3/2/25 10:10, Alex Bennée wrote:
Peter Maydell writes:
On Wed, 29 Jan 2025 at 06:23, Thomas Huth wrote:
So unless someone complains immediately with a good reason, I'm also in
favor of marking it as deprecated now. If then someone complains during the
deprecation period, we still can reco
Peter Maydell writes:
> On Wed, 29 Jan 2025 at 06:23, Thomas Huth wrote:
>> So unless someone complains immediately with a good reason, I'm also in
>> favor of marking it as deprecated now. If then someone complains during the
>> deprecation period, we still can reconsider and remove the depreca
On Fri, Jan 31, 2025 at 06:08:32PM +0100, Paolo Bonzini wrote:
> Il ven 31 gen 2025, 17:46 Richard Henderson
> ha scritto:
>
> > On 1/29/25 04:47, Paolo Bonzini wrote:
> > > The difference with TCG of course is that TCG is in active development,
> > and therefore its
> > > 32-bit host support is
Il ven 31 gen 2025, 17:46 Richard Henderson
ha scritto:
> On 1/29/25 04:47, Paolo Bonzini wrote:
> > The difference with TCG of course is that TCG is in active development,
> and therefore its
> > 32-bit host support is not surviving passively in the same way that a
> random device is.
> > Still,
On 1/29/25 04:47, Paolo Bonzini wrote:
The difference with TCG of course is that TCG is in active development, and therefore its
32-bit host support is not surviving passively in the same way that a random device is.
Still, I think we can identify at least three different parts that should be t
On 1/29/25 13:23, Peter Maydell wrote:
I'm not really strongly opposed to dropping 32-bit host support,
but I don't think a thread on qemu-devel is exactly likely to
get the attention of the people who might be using this
functionality. (You could argue that functionality without
representation a
On Wed, 29 Jan 2025 at 06:23, Thomas Huth wrote:
> So unless someone complains immediately with a good reason, I'm also in
> favor of marking it as deprecated now. If then someone complains during the
> deprecation period, we still can reconsider and remove the deprecation note
> again.
Well, I m
On 28/01/2025 11.02, Philippe Mathieu-Daudé wrote:
On 28/1/25 11:01, Philippe Mathieu-Daudé wrote:
On 28/1/25 10:27, Daniel P. Berrangé wrote:
On Tue, Jan 28, 2025 at 10:17:33AM +0100, Philippe Mathieu-Daudé wrote:
On 28/1/25 10:02, Alex Bennée wrote:
Thomas Huth writes:
On 28/01/2025 01.4
On 1/28/25 01:27, Daniel P. Berrangé wrote:
I'm not sure that's the case here.
32-on-32 is already effectively unmaintained, so we're not suffering
in terms of keeping the 32-on-32 code reliable.
Correct.
As evidence, on i686, the absolutely easiest available 32-bit host, we have the followin
On 28/1/25 11:01, Philippe Mathieu-Daudé wrote:
On 28/1/25 10:27, Daniel P. Berrangé wrote:
On Tue, Jan 28, 2025 at 10:17:33AM +0100, Philippe Mathieu-Daudé wrote:
On 28/1/25 10:02, Alex Bennée wrote:
Thomas Huth writes:
On 28/01/2025 01.42, Richard Henderson wrote:
Time for our biennial a
On 28/1/25 10:27, Daniel P. Berrangé wrote:
On Tue, Jan 28, 2025 at 10:17:33AM +0100, Philippe Mathieu-Daudé wrote:
On 28/1/25 10:02, Alex Bennée wrote:
Thomas Huth writes:
On 28/01/2025 01.42, Richard Henderson wrote:
Time for our biennial attempt to kill ancient hosts.
I've been re-workin
On 28/1/25 10:02, Alex Bennée wrote:
Thomas Huth writes:
On 28/01/2025 01.42, Richard Henderson wrote:
Time for our biennial attempt to kill ancient hosts.
I've been re-working the tcg code generator a bit over the holidays.
One place that screams for a bit of cleanup is with 64-bit guest
add
On Tue, Jan 28, 2025 at 10:17:33AM +0100, Philippe Mathieu-Daudé wrote:
> On 28/1/25 10:02, Alex Bennée wrote:
> > Thomas Huth writes:
> >
> > > On 28/01/2025 01.42, Richard Henderson wrote:
> > > > Time for our biennial attempt to kill ancient hosts.
> > > > I've been re-working the tcg code gen
On Tue, Jan 28, 2025 at 09:02:48AM +, Alex Bennée wrote:
> Thomas Huth writes:
>
> > On 28/01/2025 01.42, Richard Henderson wrote:
> >> Time for our biennial attempt to kill ancient hosts.
> >> I've been re-working the tcg code generator a bit over the holidays.
> >> One place that screams fo
Thomas Huth writes:
> On 28/01/2025 01.42, Richard Henderson wrote:
>> Time for our biennial attempt to kill ancient hosts.
>> I've been re-working the tcg code generator a bit over the holidays.
>> One place that screams for a bit of cleanup is with 64-bit guest
>> addresses on 32-bit hosts. Of
On 28/01/2025 01.42, Richard Henderson wrote:
Time for our biennial attempt to kill ancient hosts.
I've been re-working the tcg code generator a bit over the holidays.
One place that screams for a bit of cleanup is with 64-bit guest
addresses on 32-bit hosts. Of course the best "cleanup" is to
Time for our biennial attempt to kill ancient hosts.
I've been re-working the tcg code generator a bit over the holidays.
One place that screams for a bit of cleanup is with 64-bit guest
addresses on 32-bit hosts. Of course the best "cleanup" is to not
have to handle such silliness at all.
Two y
17 matches
Mail list logo
