From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Pavel Fedin <p.fedin@samsung.com>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
kvm-devel <kvm@vger.kernel.org>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [RFC] Handling CP15 timer without in-kernel irqchip
Date: Fri, 2 Oct 2015 12:18:34 +0200 [thread overview]
Message-ID: <560E59FA.9070205@redhat.com> (raw)
In-Reply-To: <CAFEAcA9xuaE6DmpZGD1g9DXTSctiawwrV1iq1xXv+EO7qDR+xA@mail.gmail.com>
On 02/10/2015 12:16, Peter Maydell wrote:
> On 2 October 2015 at 11:05, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> On 02/10/2015 11:58, Peter Maydell wrote:
>>> I definitely dislike the latter -- userspace ends up having to
>>> emulate part of the CPU even though that CPU support is really
>>> there in hardware. Also it requires us to edit the device tree,
>>> which means it won't work at all on boards other than 'virt'
>>> where we use the kernel's device tree rather than creating our
>>> own. Better for the kernel to forward the timer
>>> interrupts back out to userspace's irq controller.
>>
>> How do boards other than 'virt' work when emulated without KVM? It must
>> be possible to emulate the physical timer in QEMU.
>
> Without KVM is easy -- we emulate the physical timer as just
> one of the parts of the emulated CPU. With KVM, we don't emulate
> the CPU at all. We don't try to handle a "half TCG half KVM" setup.
I mean in the device tree. Does the boot loader realize it's under a
hypervisor, and provide different device trees to the kernel?
Paolo
next prev parent reply other threads:[~2015-10-02 10:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 7:28 [RFC] Handling CP15 timer without in-kernel irqchip Pavel Fedin
2015-10-02 9:30 ` Paolo Bonzini
2015-10-02 9:41 ` Pavel Fedin
2015-10-02 9:58 ` Peter Maydell
2015-10-02 10:05 ` Paolo Bonzini
2015-10-02 10:16 ` Peter Maydell
2015-10-02 10:18 ` Paolo Bonzini [this message]
2015-10-02 10:22 ` Pavel Fedin
2015-10-02 10:23 ` Peter Maydell
2015-10-02 10:18 ` Pavel Fedin
2015-10-02 10:22 ` Marc Zyngier
2015-10-02 10:22 ` Marc Zyngier
2015-10-02 10:33 ` Pavel Fedin
2015-10-02 14:54 ` Pavel Fedin
2015-10-02 20:26 ` Christoffer Dall
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=560E59FA.9070205@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=marc.zyngier@arm.com \
--cc=p.fedin@samsung.com \
--cc=peter.maydell@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.