From: Salil Mehta <salil.mehta@huawei.com>
To: Andrew Jones <drjones@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"gshan@redhat.com" <gshan@redhat.com>,
"mst@redhat.com" <mst@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
Igor Mammedov <imammedo@redhat.com>
Subject: RE: [Question] Regarding PMU initialization within the QEMU for ARM VCPUs
Date: Wed, 3 Jun 2020 14:53:21 +0000 [thread overview]
Message-ID: <70ab2e21085844999f5f8615b32dde1d@huawei.com> (raw)
In-Reply-To: <20200603143655.vk3uqw5lvgv6sm5p@kamzik.brq.redhat.com>
> From: Qemu-arm [mailto:qemu-arm-bounces+salil.mehta=huawei.com@nongnu.org]
> On Behalf Of Andrew Jones
> Sent: Wednesday, June 3, 2020 3:37 PM
> To: Salil Mehta <salil.mehta@huawei.com>
> Cc: Peter Maydell <peter.maydell@linaro.org>; mst@redhat.com;
> qemu-devel@nongnu.org; eric.auger@redhat.com; qemu-arm@nongnu.org; Igor
> Mammedov <imammedo@redhat.com>
> Subject: Re: [Question] Regarding PMU initialization within the QEMU for ARM
> VCPUs
>
> On Wed, Jun 03, 2020 at 01:48:10PM +0000, Salil Mehta wrote:
> > (Maybe I should float the ARM VCPU Hotplug patches and let this
> > discussion be held over there?)
> >
>
> Yes, I think that would be best. Keep in mind that the 'pmu' CPU property
> is just one CPU property that we require all CPUs to have, if any have it.
> 'aarch64' and 'sve' are two other examples. And, likely any CPU feature
> that comes down the line that we want to use with KVM will fit that
> pattern. I think the hotplug patch series will need to handle those
> features in some way other than to push them all into machine properties.
Sure, I do have realization about that. I have for now used a per virt
machine flag for PMU to do a workaround of the problem I discussed.
Maybe once I float the patches further comments on the ways to improve
the design would be very helpful. So for now I will keep the flag and
use this approach and invite everyone for open discussion about this
and we could evolve the design as we discuss there.
Many thanks
Salil.
next prev parent reply other threads:[~2020-06-03 15:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-01 15:04 [Question] Regarding PMU initialization within the QEMU for ARM VCPUs Salil Mehta
2020-06-03 9:37 ` Andrew Jones
2020-06-03 9:59 ` Auger Eric
2020-06-03 10:21 ` Andrew Jones
2020-06-03 11:39 ` Auger Eric
2020-06-05 15:24 ` Igor Mammedov
2020-06-03 11:50 ` Salil Mehta
2020-06-03 11:45 ` Salil Mehta
2020-06-03 12:16 ` Andrew Jones
2020-06-03 13:48 ` Salil Mehta
2020-06-03 14:36 ` Andrew Jones
2020-06-03 14:53 ` Salil Mehta [this message]
2020-06-05 15:31 ` Igor Mammedov
2020-06-05 16:38 ` Salil Mehta
2020-06-08 12:00 ` Igor Mammedov
2020-06-08 13:49 ` Salil Mehta
2020-06-03 8:38 Salil Mehta
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=70ab2e21085844999f5f8615b32dde1d@huawei.com \
--to=salil.mehta@huawei.com \
--cc=drjones@redhat.com \
--cc=eric.auger@redhat.com \
--cc=gshan@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--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).