Comment 2 for bug 1872931

[11:23] <cpaelzer> wgrant: does enabling rsicv have a general FFe?
[11:23] <cpaelzer> or do we need such processing for every change (I'd hope not)
[11:54] <wgrant> It hasn't been suggested to me that an FFe was required for changes that were limited to riscv64.
[11:55] <cpaelzer> I thought enabling another arch usually would fall under that category
[11:55] <cpaelzer> wgrant: what is the immediate use case for this in 20.04 - will people really use it as a host?
[11:56] <wgrant> cpaelzer: qemu-utils
[11:57] <wgrant> qemu-img, etc.
[11:57] <wgrant> And unblocking libvirt and its rdeps
[11:57] <wgrant> libvirt is the fifth most common missing build dependency at present
[11:57] <cpaelzer> xnox: to get a third opinion - do you happen to know if we'd need an FFe (or wait for 20.10) with that?
[12:06] <xnox> cpaelzer: hwe exception. We have standing exception for hardware enablement.
[12:06] <cpaelzer> xnox: I know that for SRUs, are you saying this applies to FFe as well then?
[12:07] <xnox> cpaelzer: we need qemu-utils to build images. Ideally sooner than later.
[12:07] <cpaelzer> well, ok under that banner I can work
[12:07] <cpaelzer> thank you
[12:07] <xnox> cpaelzer: also applies to ffe.