Re: Guidance on individual packages requiring x86_64-v2 baseline ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jun 20, 2024 at 10:51:56AM -0400, Stephen Gallagher wrote:
> On Thu, Jun 20, 2024 at 10:49 AM Daniel P. Berrangé <berrange@xxxxxxxxxx> wrote:
> >
> > On Thu, Jun 20, 2024 at 03:24:18PM +0100, Tom Hughes via devel wrote:
> > > On 20/06/2024 15:03, Stephen Gallagher wrote:
> > >
> > > > Honestly, I'd like to pitch that we retarget Fedora at x86_64-v3 (yes,
> > > > three) and recommend creation of a Fedora "Hardware Life Extension"
> > > > Remix that can provide rebuilds of (a subset of) Fedora that they want
> > > > to run on ancient hardware. It could be something similar to Fedora
> > > > ELN, where a subset of the main repo that might be useful on old
> > > > hardware can be rebuilt (though unlike ELN, I suggest that this should
> > > > be an entirely separate infrastructure not maintained by the Fedora
> > > > Project). Such a project could then live or die based on willingness
> > > > to maintain it and stop holding back Fedora as a whole.
> > >
> > > I definitely think going to v2 would be reasonable bit I tink
> > > forcing v3 might be a step too far.
> >
> > If going to v3, compared v2....
> >
> > For AMD, we would loose Opteron Gen4 and Opteron Gen5 models, but
> > keep EPYC/Ryzen all generations.
> >
> > For Intel, we would loose Denverton, IvyBridge, Nehalem,
> > SandyBridge, Snowridge, Westmere, but keep Skylake,
> > SapphireRapids, Icelake, Haswell, GraniteRapids, Cooperlake,
> > Cascadelake, Broadwell.
> >
> >
> > Personally I'd say v2 is the better first step, as plenty of
> > those generations we'd loose are still pretty relevant, even
> > if not the state of the art shipping today.
> >
> 
> 
> OK, I think I got my baselines mixed up. Sorry about that. I could
> have sworn what you were describing above was the effect of moving to
> -v4.

This table is specifically referring to named QEMU CPU models, but the
names & impls match vendor generations closely enough that this is a
decent crib-sheet to get an overview of the compatibility matrix:

  https://www.qemu.org/docs/master/system/i386/cpu.html#abi-compatibility-levels-for-cpu-models

With regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux