From: Thomas Huth <thuth@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
libvir-list@redhat.com, qemu-devel@nongnu.org,
Gerd Hoffmann <kraxel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 0/3] Remove deprecated pc-0.x machine types and related hacks
Date: Fri, 6 Dec 2019 09:29:29 +0100 [thread overview]
Message-ID: <a25c0ae9-38cf-8a8f-730e-b618ad05bb7b@redhat.com> (raw)
In-Reply-To: <874kyeosmg.fsf@dusky.pond.sub.org>
On 06/12/2019 07.49, Markus Armbruster wrote:
> Thomas Huth <thuth@redhat.com> writes:
>
>> These have been on the deprecation list since a year now, so it's
>> time to finally remove the pc-0.x machine types.
>>
>> We then can also remove some compatibility hacks in the devices, i.e.
>> the "use_broken_id" in ac97 and "command_serr_enable" in PCI devices.
>>
>> Note that there is also the "rombar" property of the PCI devices which
>> is now not required for the x86 machine types anymore. But it seems to
>> me like this is still used by various people to bypass the ROM loading
>> for PCI devices in certain cases, so I did not remove that property here
>> yet.
>
> With this series applied:
>
> $ git-grep pc-0
> hw/display/vga-pci.c: /* compatibility with pc-0.13 and older */
> hw/display/vga.c: /* With pc-0.12 and below we map both the PCI BAR and the fixed VBE region,
> hw/display/vmware_vga.c: /* compatibility with pc-0.13 and older */
These are the "rombar" hacks that I've mentioned above. The question is
whether we want to remove them or whether I should just adjust the comments?
> hw/i386/pc_piix.c:/* PC compat function
Right, the comment still needs to be adjusted.
Thomas
next prev parent reply other threads:[~2019-12-06 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 16:06 [PATCH 0/3] Remove deprecated pc-0.x machine types and related hacks Thomas Huth
2019-12-05 16:06 ` [PATCH 1/3] hw/i386: Remove the deprecated machines 0.12 up to 0.15 Thomas Huth
2019-12-05 22:00 ` [libvirt] " Eric Blake
2019-12-06 5:04 ` Thomas Huth
2019-12-06 5:51 ` Philippe Mathieu-Daudé
2019-12-05 16:06 ` [PATCH 2/3] hw/audio: Remove the "use_broken_id" hack from the AC97 device Thomas Huth
2019-12-06 5:52 ` Philippe Mathieu-Daudé
2019-12-05 16:06 ` [PATCH 3/3] hw/pci: Remove the "command_serr_enable" property Thomas Huth
2019-12-06 10:21 ` Paolo Bonzini
2019-12-06 6:49 ` [PATCH 0/3] Remove deprecated pc-0.x machine types and related hacks Markus Armbruster
2019-12-06 8:29 ` Thomas Huth [this message]
2019-12-06 10:57 ` 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=a25c0ae9-38cf-8a8f-730e-b618ad05bb7b@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kraxel@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).