From: Rusty Russell <rusty@rustcorp.com.au>
To: Peter Maydell <peter.maydell@linaro.org>,
Rusty Russell <rusty.russell@linaro.org>
Cc: Marc Zyngier <marc.zyngier@arm.com>,
Christoffer Dall <c.dall@virtualopensystems.com>,
Peter Maydell <Peter.Maydell@arm.com>,
kvm@vger.kernel.org, android-virt@lists.cs.columbia.edu
Subject: Re: [Android-virt] [PATCH] ARM: KVM: Emulate ID_DFR0 to say we don't support anything.
Date: Sat, 24 Mar 2012 09:53:45 +1030 [thread overview]
Message-ID: <87d3829a0u.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CAFEAcA8pTPDjXmwgpWEKwxe-98VnqTTmtAzoMK8pXnxZe9jtSA@mail.gmail.com>
On Fri, 23 Mar 2012 09:04:27 +0000, Peter Maydell <peter.maydell@linaro.org> wrote:
> On 23 March 2012 00:38, Rusty Russell <rusty.russell@linaro.org> wrote:
> > The guest should be checking this before trying to use performance monitors,
> > for example.
> >
> > Signed-off-by: Rusty Russell <rusty.russell@linaro.org>
>
> Does this code get used currently? I thought we hadn't enabled
> trapping for feature register reads because of that use of one
> of the MMFR registers in a hot path for page allocation...
True (I mis-labelled the patches, they should have been RFC, since this
is tied to the host-side probing patch).
So maybe not today, but we're going to end up doing this eventually.
Everyone expects their virtual machines to work fine with the next model
of ARM CPUs, which means we need to hide more and more host features
over time.
Cheers,
Rusty.
--
How could I marry someone with more hair than me? http://baldalex.org
prev parent reply other threads:[~2012-03-23 23:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F590411.9060201@arm.com>
[not found] ` <87ty1g88dv.fsf@rustcorp.com.au>
2012-03-23 0:38 ` [PATCH] ARM: KVM: Emulate ID_DFR0 to say we don't support anything Rusty Russell
2012-03-23 9:04 ` [Android-virt] " Peter Maydell
2012-03-23 23:23 ` Rusty Russell [this message]
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=87d3829a0u.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=Peter.Maydell@arm.com \
--cc=android-virt@lists.cs.columbia.edu \
--cc=c.dall@virtualopensystems.com \
--cc=kvm@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=peter.maydell@linaro.org \
--cc=rusty.russell@linaro.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