On 26 July 2018 at 20:49, Daniel P. Berrangé <berra...@redhat.com> wrote: > On Thu, Jul 26, 2018 at 02:23:46PM +0200, Laszlo Ersek wrote: >> On 07/26/18 13:13, Andrew Jones wrote: >> > On Thu, Jul 26, 2018 at 12:56:22PM +0200, Ard Biesheuvel wrote: >> >> On 26 July 2018 at 12:52, Peter Maydell <peter.mayd...@linaro.org> wrote: >> >>> On 26 July 2018 at 11:46, Andrew Jones <drjo...@redhat.com> wrote: >> >>>> i440fx and q35 are specific machine types. 'sbsa' is a generic machine >> >>>> type that conforms to the SBSA specification. If you weren't trying to >> >>>> memory map AHCI and EHCI controllers, or if memory mapped AHCI and EHCI >> >>>> controllers were mandated in the SBSA spec, then there wouldn't be >> >>>> anything to discuss. But that's not the case. You're attempting to >> >>>> hard code one instance of a generic class of SBSA machines, but then >> >>>> just call it 'sbsa'. >> >>> >> >>> Modelling a 'generic SBSA machine' is not the goal here (I'm >> >>> not sure that's even possible or useful), so let's just >> >>> stipulate that we'll call the machine type something else >> >>> and move on ? >> >>> >> >> >> >> Fine with me. Care to suggest a name? :-) >> >> >> > >> > Also fine by me, but I'm not going to suggest the name. I fear the >> > backlash I'd receive after this mail thread! >> > >> >> I suggest "showcase2018". (Dead serious.) > > Further suggestions > > "refplatform" > "sbsareference" > "sbsademo" > "phys" (physical counterpart to "virt") > I like "sbsareference", some people still like the letters "sbsa" in the name, and the "reference" sounds good too. the only drawback is the string seems a bit long, I like this format "sbsa-reference" but it is longer, "sbsa-ref"?
> > 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 :|