qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dave@treblig.org>
To: Bernhard Beschow <shentey@gmail.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com, marcel.apfelbaum@gmail.com
Subject: Re: [PATCH] q35: Remove unused mch_mcfg_base
Date: Thu, 19 Sep 2024 19:53:09 +0000	[thread overview]
Message-ID: <ZuyBJfigS6jnUN6c@gallifrey> (raw)
In-Reply-To: <A4D1CDE0-9424-44EB-8E50-46FB84BAA509@gmail.com>

* Bernhard Beschow (shentey@gmail.com) wrote:
> 
> 
> Am 18. September 2024 00:51:32 UTC schrieb dave@treblig.org:
> >From: "Dr. David Alan Gilbert" <dave@treblig.org>
> >
> >mch_mcfg_base has been unused since it was added by
> >  6f1426ab0f ("ich9: APIs for pc guest info")
> >back in 2013.
> 
> Indeed.
> 
> >
> >Remove it.
> >
> >Signed-off-by: Dr. David Alan Gilbert <dave@treblig.org>
> 
> Reviewed-by: Bernhard Beschow <shentey@gmail.com>

Thanks!

> I'm curious: How do you detect such unused code?

I've got a very hacky script that looks for symbols that
are defined but nothing else uses; it generates a lot of
false positives so takes a lot of handholding to find
real cases.
See: https://lore.kernel.org/lkml/ZugliLgw5VFb9yau@gallifrey/

Dave

> >---
> > hw/pci-host/q35.c         | 10 ----------
> > include/hw/pci-host/q35.h |  2 --
> > 2 files changed, 12 deletions(-)
> >
> >diff --git a/hw/pci-host/q35.c b/hw/pci-host/q35.c
> >index d5a657a02a..f3e713318e 100644
> >--- a/hw/pci-host/q35.c
> >+++ b/hw/pci-host/q35.c
> >@@ -662,16 +662,6 @@ static void mch_realize(PCIDevice *d, Error **errp)
> >                                    OBJECT(&mch->smram));
> > }
> > 
> >-uint64_t mch_mcfg_base(void)
> >-{
> >-    bool ambiguous;
> >-    Object *o = object_resolve_path_type("", TYPE_MCH_PCI_DEVICE, &ambiguous);
> >-    if (!o) {
> >-        return 0;
> >-    }
> >-    return MCH_HOST_BRIDGE_PCIEXBAR_DEFAULT;
> >-}
> >-
> > static Property mch_props[] = {
> >     DEFINE_PROP_UINT16("extended-tseg-mbytes", MCHPCIState, ext_tseg_mbytes,
> >                        16),
> >diff --git a/include/hw/pci-host/q35.h b/include/hw/pci-host/q35.h
> >index 22fadfa3ed..ddafc3f2e3 100644
> >--- a/include/hw/pci-host/q35.h
> >+++ b/include/hw/pci-host/q35.h
> >@@ -181,8 +181,6 @@ struct Q35PCIHost {
> > #define MCH_PCIE_DEV                           1
> > #define MCH_PCIE_FUNC                          0
> > 
> >-uint64_t mch_mcfg_base(void);
> >-
> > /*
> >  * Arbitrary but unique BNF number for IOAPIC device.
> >  *
-- 
 -----Open up your eyes, open up your mind, open up your code -------   
/ Dr. David Alan Gilbert    |       Running GNU/Linux       | Happy  \ 
\        dave @ treblig.org |                               | In Hex /
 \ _________________________|_____ http://www.treblig.org   |_______/


  reply	other threads:[~2024-09-19 19:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18  0:51 [PATCH] q35: Remove unused mch_mcfg_base dave
2024-09-19 18:28 ` Bernhard Beschow
2024-09-19 19:53   ` Dr. David Alan Gilbert [this message]
2024-10-02 10:28 ` Thomas Huth

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=ZuyBJfigS6jnUN6c@gallifrey \
    --to=dave@treblig.org \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=shentey@gmail.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).