From: Gerd Hoffmann <kraxel@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
libvir-list@redhat.com, qemu-devel@nongnu.org,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2 4/4] hw/display: Remove "rombar" hack from vga-pci and vmware_vga
Date: Mon, 9 Dec 2019 14:30:54 +0100 [thread overview]
Message-ID: <20191209133054.zxrwzjutefxxf7ar@sirius.home.kraxel.org> (raw)
In-Reply-To: <3ab730ea-658f-ff98-035d-f94ed7775f00@redhat.com>
On Mon, Dec 09, 2019 at 02:12:35PM +0100, Philippe Mathieu-Daudé wrote:
> On 12/9/19 1:52 PM, Thomas Huth wrote:
> > Now that the old pc-0.x machine types have been removed, we do not need
> > the old "rombar" hacks anymore.
> >
> > Signed-off-by: Thomas Huth <thuth@redhat.com>
> > ---
> > hw/display/vga-pci.c | 5 -----
> > hw/display/vga.c | 4 +---
> > hw/display/vmware_vga.c | 5 -----
> > 3 files changed, 1 insertion(+), 13 deletions(-)
> >
> > diff --git a/hw/display/vga-pci.c b/hw/display/vga-pci.c
> > index a27b88122d..cfe095713e 100644
> > --- a/hw/display/vga-pci.c
> > +++ b/hw/display/vga-pci.c
> > @@ -264,11 +264,6 @@ static void pci_std_vga_realize(PCIDevice *dev, Error **errp)
> > pci_register_bar(&d->dev, 2, PCI_BASE_ADDRESS_SPACE_MEMORY, &d->mmio);
> > }
> > -
> > - if (!dev->rom_bar) {
> > - /* compatibility with pc-0.13 and older */
> > - vga_init_vbe(s, OBJECT(dev), pci_address_space(dev));
> > - }
> > }
> > static void pci_std_vga_init(Object *obj)
> > diff --git a/hw/display/vga.c b/hw/display/vga.c
> > index 82ebe53610..636586a476 100644
> > --- a/hw/display/vga.c
> > +++ b/hw/display/vga.c
> > @@ -2304,9 +2304,7 @@ void vga_init(VGACommonState *s, Object *obj, MemoryRegion *address_space,
> > void vga_init_vbe(VGACommonState *s, Object *obj, MemoryRegion *system_memory)
> > {
> > - /* With pc-0.12 and below we map both the PCI BAR and the fixed VBE region,
> > - * so use an alias to avoid double-mapping the same region.
> > - */
> > + /* Use an alias to avoid double-mapping the same region */
>
> If I understand the comment correctly, we can now revert commit 8294a64d7f9
> and and remove the alias, isn't it?
Hmm, yes, I think so given that only isa-vga calls vga_init_vbe().
cheers,
Gerd
next prev parent reply other threads:[~2019-12-09 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 12:52 [PATCH v2 0/4] Remove deprecated pc-0.x machine types and related hacks Thomas Huth
2019-12-09 12:52 ` [PATCH v2 1/4] hw/i386: Remove the deprecated machines 0.12 up to 0.15 Thomas Huth
2019-12-09 12:52 ` [PATCH v2 2/4] hw/audio: Remove the "use_broken_id" hack from the AC97 device Thomas Huth
2019-12-09 12:52 ` [PATCH v2 3/4] hw/pci: Remove the "command_serr_enable" property Thomas Huth
2019-12-09 12:52 ` [PATCH v2 4/4] hw/display: Remove "rombar" hack from vga-pci and vmware_vga Thomas Huth
2019-12-09 13:12 ` Philippe Mathieu-Daudé
2019-12-09 13:30 ` Paolo Bonzini
2019-12-09 13:49 ` Thomas Huth
2019-12-09 13:30 ` Gerd Hoffmann [this message]
2019-12-09 13:06 ` [PATCH v2 0/4] Remove deprecated pc-0.x machine types and related hacks Paolo Bonzini
2019-12-09 18:18 ` [libvirt] " no-reply
2019-12-09 18:23 ` no-reply
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=20191209133054.zxrwzjutefxxf7ar@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=ehabkost@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 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).