From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
qemu-devel@nongnu.org, "Bernhard Beschow" <shentey@gmail.com>,
pbonzini@redhat.com, devel@lists.libvirt.org,
richard.henderson@linaro.org, mst@redhat.com,
qemu-trivial@nongnu.org
Subject: Re: [PATCH for-9.0] docs/about: Mark the iaspc machine type as deprecated
Date: Wed, 27 Mar 2024 10:49:43 +0000 [thread overview]
Message-ID: <ZgP5x3ECYGevla1-@redhat.com> (raw)
In-Reply-To: <20240326171632.3cc7533d@imammedo.users.ipa.redhat.com>
On Tue, Mar 26, 2024 at 05:16:32PM +0100, Igor Mammedov wrote:
> On Tue, 26 Mar 2024 14:29:58 +0100
> Philippe Mathieu-Daudé <philmd@linaro.org> wrote:
>
> > Hi Igor,
> >
> > On 26/3/24 14:08, Thomas Huth wrote:
> > >
> > > s/iaspc/isapc/ in the subject
> > >
> > > On 26/03/2024 13.51, Igor Mammedov wrote:
> > >> ISAPC machine was introduced 25 years ago and it's a lot of time since
> > >> such machine was around with real ISA only PC hardware practically
> > >> defunct.
> > >> Also it's slowly bit-rots (for example: I was able to boot RHEL6 on
> > >> RHEL9 host
> > >> in only TCG mode, while in KVM mode it hung in the middle of boot)
> >
> > I'm quite opposed to this patch. QEMU models various very-old /
> > defunct hardware. I'm pretty sure Bernhard and myself are OK to
> > keep maintaining it, besides we are working in separating it from
> > the i440fx+piix machine. Also, this machine is particularly
> > interesting for my single-binary experiments.
>
> it would not be fair to ask you or Bernard to deal with every
> case where ISAPC related code gets in a way, nor it's fair to
> ask other contributors to ensure that their patches don't break
> semi-working ISAPC or refactor code that relates to it.
>
> [
> for example I'd like to refactor smbios parts in the image
> ACPI table builder, but the I'd have to do it for legacy
> part as well without means to verify that. Sure it can be
> done but at cost of extra time spent to rewrite something
> that would never be used and to find test env to verify
> touched code.
> ]
Is SMBIOS even relevant for isapc ? IIUC, the first SMBIOS spec
is from 1999, while PCI has been around since 1992.
IOW, we shouldn't even be exposing SMBIOS with the isapc
machine type. If we address that, then isapc has no impact
on your ability to refactor SMBIOS code.
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 :|
next prev parent reply other threads:[~2024-03-27 10:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-26 12:51 [PATCH for-9.0] docs/about: Mark the iaspc machine type as deprecated Igor Mammedov
2024-03-26 13:03 ` Ani Sinha
2024-03-26 13:08 ` Thomas Huth
2024-03-26 13:29 ` Philippe Mathieu-Daudé
2024-03-26 13:37 ` Thomas Huth
2024-03-26 14:00 ` Philippe Mathieu-Daudé
2024-03-26 16:16 ` Igor Mammedov
2024-03-27 10:49 ` Daniel P. Berrangé [this message]
2024-03-27 13:09 ` Igor Mammedov
2024-03-27 13:14 ` Thomas Huth
2024-03-27 13:22 ` Daniel P. Berrangé
2024-03-27 13:27 ` Peter Maydell
2024-03-27 13:29 ` Daniel P. Berrangé
2024-03-27 13:26 ` Philippe Mathieu-Daudé
2024-03-27 20:39 ` Paolo Bonzini
2024-03-27 13:51 ` Daniel P. Berrangé
2024-03-27 20:47 ` Bernhard Beschow
2024-03-26 13:30 ` Mark Cave-Ayland
2024-03-26 16:20 ` Igor Mammedov
2024-03-26 16:22 ` Igor Mammedov
2024-03-27 7:09 ` Gerd Hoffmann
2024-03-28 14:09 ` Mark Cave-Ayland
2024-03-29 10:19 ` Bernhard Beschow
2024-04-02 8:53 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZgP5x3ECYGevla1-@redhat.com \
--to=berrange@redhat.com \
--cc=devel@lists.libvirt.org \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shentey@gmail.com \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.