From: Gleb Natapov <gleb@redhat.com> To: Peter Maydell <peter.maydell@linaro.org> Cc: qemu-devel <qemu-devel@nongnu.org>, kvmarm@lists.cs.columbia.edu, "Andreas Färber" <afaerber@suse.de>, "KVM devel mailing list" <kvm@vger.kernel.org>, quintela@redhat.com Subject: Re: -cpu host (was Re: KVM call minutes for 2013-08-06) Date: Sun, 25 Aug 2013 16:55:23 +0300 [thread overview] Message-ID: <20130825135523.GS8218@redhat.com> (raw) In-Reply-To: <CAFEAcA9Xz=tWY95+iGiJ3z1zufdxS0uJoJg6FREVmhmR5GvXAA@mail.gmail.com> On Thu, Aug 08, 2013 at 07:20:41PM +0100, Peter Maydell wrote: > >> For ARM you can't get at feature info of the host from userspace > >> (unless you want to get into parsing /proc/cpuinfo), so my current > >> idea is to have KVM_ARM_VCPU_INIT support a target-cpu-type > >> which means "whatever host CPU is". Then when we've created the > >> vcpu we can populate QEMU's idea of what the CPU features are > >> by using the existing ioctls for reading the cp15 registers of > >> the vcpu. > > > > Sounds sane to me iff those cp15 registers all work with KVM and don't > > need any additional KVM/QEMU/device code. > > Yes; KVM won't tell us about CP15 registers unless they > are exposed to the guest VM (that is, we're querying the So why not implement something similar to x86 cpuid thing. Have separate ioctls to query what CP15 registers KVM can support and what is exposed to a guest? > VCPU, not the host CPU). More generally, the cp15 "tuple > list" code I landed a couple of months back makes the kernel > the authoritative source for which cp15 registers exist and > what their values are -- in -enable-kvm mode QEMU no longer > cares about them (its own list of which registers exist for > which CPU is used only for TCG). > -- Gleb.
WARNING: multiple messages have this Message-ID (diff)
From: Gleb Natapov <gleb@redhat.com> To: Peter Maydell <peter.maydell@linaro.org> Cc: qemu-devel <qemu-devel@nongnu.org>, kvmarm@lists.cs.columbia.edu, "Andreas Färber" <afaerber@suse.de>, "KVM devel mailing list" <kvm@vger.kernel.org>, quintela@redhat.com Subject: Re: [Qemu-devel] -cpu host (was Re: KVM call minutes for 2013-08-06) Date: Sun, 25 Aug 2013 16:55:23 +0300 [thread overview] Message-ID: <20130825135523.GS8218@redhat.com> (raw) In-Reply-To: <CAFEAcA9Xz=tWY95+iGiJ3z1zufdxS0uJoJg6FREVmhmR5GvXAA@mail.gmail.com> On Thu, Aug 08, 2013 at 07:20:41PM +0100, Peter Maydell wrote: > >> For ARM you can't get at feature info of the host from userspace > >> (unless you want to get into parsing /proc/cpuinfo), so my current > >> idea is to have KVM_ARM_VCPU_INIT support a target-cpu-type > >> which means "whatever host CPU is". Then when we've created the > >> vcpu we can populate QEMU's idea of what the CPU features are > >> by using the existing ioctls for reading the cp15 registers of > >> the vcpu. > > > > Sounds sane to me iff those cp15 registers all work with KVM and don't > > need any additional KVM/QEMU/device code. > > Yes; KVM won't tell us about CP15 registers unless they > are exposed to the guest VM (that is, we're querying the So why not implement something similar to x86 cpuid thing. Have separate ioctls to query what CP15 registers KVM can support and what is exposed to a guest? > VCPU, not the host CPU). More generally, the cp15 "tuple > list" code I landed a couple of months back makes the kernel > the authoritative source for which cp15 registers exist and > what their values are -- in -enable-kvm mode QEMU no longer > cares about them (its own list of which registers exist for > which CPU is used only for TCG). > -- Gleb.
next prev parent reply other threads:[~2013-08-25 13:55 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-08 12:51 -cpu host (was Re: [Qemu-devel] KVM call minutes for 2013-08-06) Peter Maydell 2013-08-08 12:51 ` [Qemu-devel] -cpu host (was " Peter Maydell 2013-08-08 15:55 ` Andreas Färber 2013-08-08 15:55 ` Andreas Färber 2013-08-08 18:20 ` Peter Maydell 2013-08-08 18:20 ` Peter Maydell 2013-08-08 18:39 ` Christoffer Dall 2013-08-08 18:39 ` Christoffer Dall 2013-08-08 19:05 ` Peter Maydell 2013-08-08 19:05 ` Peter Maydell 2013-08-08 19:29 ` Christoffer Dall 2013-08-08 19:29 ` Christoffer Dall 2013-08-08 20:48 ` Peter Maydell 2013-08-08 20:48 ` Peter Maydell 2013-08-08 20:57 ` Christoffer Dall 2013-08-08 20:57 ` Christoffer Dall 2013-08-08 21:16 ` Peter Maydell 2013-08-08 21:16 ` Peter Maydell 2013-08-09 17:53 ` Eduardo Habkost 2013-08-09 17:53 ` Eduardo Habkost 2013-08-25 13:49 ` Gleb Natapov 2013-08-25 13:49 ` Gleb Natapov 2013-08-25 13:55 ` Gleb Natapov [this message] 2013-08-25 13:55 ` Gleb Natapov 2013-08-25 13:14 ` Gleb Natapov 2013-08-25 13:14 ` Gleb Natapov 2013-08-09 13:12 ` Peter Maydell 2013-08-09 20:07 ` Andreas Färber 2013-08-09 20:07 ` Andreas Färber
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=20130825135523.GS8218@redhat.com \ --to=gleb@redhat.com \ --cc=afaerber@suse.de \ --cc=kvm@vger.kernel.org \ --cc=kvmarm@lists.cs.columbia.edu \ --cc=peter.maydell@linaro.org \ --cc=qemu-devel@nongnu.org \ --cc=quintela@redhat.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: linkBe 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.