From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] of apci_1_compatible in CPUHotplugFeatures
Date: Fri, 25 Jan 2019 09:41:19 +0000 [thread overview]
Message-ID: <20190125094118.GB2695@work-vm> (raw)
In-Reply-To: <20190125092605.2d40dce8@redhat.com>
* Igor Mammedov (imammedo@redhat.com) wrote:
> On Wed, 23 Jan 2019 18:28:59 +0000
> "Dr. David Alan Gilbert" <dgilbert@redhat.com> wrote:
>
> > * Michael S. Tsirkin (mst@redhat.com) wrote:
> > > On Tue, Jan 22, 2019 at 08:07:41PM +0000, Dr. David Alan Gilbert wrote:
> > > > Hi,
> > > > I noticed that the acpi_1_compatible flag was misspelt as
> > > > apci_1_compatible
> > > >
> > > > so have a trivial patch to fix that,
> pls post it.
Done.
> > > > but looking at it - are
> > > > thre any cases where a[cp]i_1_compatible can possibly be false?
> ATM it's not possible, but I've wrote it with intent to reuse
> build_cpus_aml() in arm/virt board and there we shall use newer
> aml_device() instead of legacy aml_processor(), hence a feature flag
> to toggle behavior.
OK, that's fine, I just couldn't see why the flag was there given the
current uses.
Dave
>
> > > >
> > > > Dave
> > >
> > > legacy_cpu_hotplug so machine 2.6 and older - no?
> >
> > That doesn't seem to affect that flag by my reading;
> > the only place I see legacy_cpu_hotplug checked is
> > acpi-build.c:build_dsdt and we have:
> >
> > if (pcmc->legacy_cpu_hotplug) {
> > build_legacy_cpu_hotplug_aml(dsdt, machine, pm->cpu_hp_io_base);
> > } else {
> > CPUHotplugFeatures opts = {
> > .acpi_1_compatible = true, .has_legacy_cphp = true
> > };
> > build_cpus_aml(dsdt, machine, opts, pm->cpu_hp_io_base,
> > "\\_SB.PCI0", "\\_GPE._E02");
> > }
> >
> > so the 'opts' field is only used in the non-legacy case.
> >
> > That's the only caller of build_cpus_aml, and I'm not seeing another
> > user of CPUHotplugFeatures.
> >
> > Dave
> >
> > > > --
> > > > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
> > --
> > Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-01-25 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 20:07 [Qemu-devel] of apci_1_compatible in CPUHotplugFeatures Dr. David Alan Gilbert
2019-01-23 3:00 ` Michael S. Tsirkin
2019-01-23 18:28 ` Dr. David Alan Gilbert
2019-01-25 8:26 ` Igor Mammedov
2019-01-25 9:41 ` Dr. David Alan Gilbert [this message]
2019-01-25 19:49 ` Michael S. Tsirkin
2019-01-28 10:41 ` Igor Mammedov
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=20190125094118.GB2695@work-vm \
--to=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@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).