From: Marc Zyngier <marc.zyngier@arm.com>
To: Timur Tabi <timur@codeaurora.org>
Cc: Suzuki Poulose <Suzuki.Poulose@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"christoffer.dall@linaro.org" <christoffer.dall@linaro.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"shankerd@codeaurora.org" <shankerd@codeaurora.org>,
"vgandhi@codeaurora.org" <vgandhi@codeaurora.org>
Subject: Re: [PATCH] arm64/kvm: Add generic v8 KVM target
Date: Mon, 22 Jun 2015 07:47:59 +0100 [thread overview]
Message-ID: <20150622074759.01d677a3@arm.com> (raw)
In-Reply-To: <55847C1F.1090606@codeaurora.org>
On Fri, 19 Jun 2015 21:31:27 +0100
Timur Tabi <timur@codeaurora.org> wrote:
> On 06/17/2015 04:00 AM, Suzuki K. Poulose wrote:
> > &genericv8_target_table);
> > kvm_register_target_sys_reg_table(KVM_ARM_TARGET_XGENE_POTENZA,
> > &genericv8_target_table);
> > +
> > kvm_register_target_sys_reg_table(KVM_ARM_TARGET_GENERIC_V8,
> > + &genericv8_target_table);
> >
>
> Shouldn't you also remove all of the previous lines that return
> &genericv8_target_table?
No. KVM_ARM_TARGET_* are part of the uapi, and existing userspace knows
about them. You can't just drop them.
What you *could* do would be to map the existing targets to the generic
one in a way that leaves userspace blissfully unaware of the underlying
change (for example, KVM_ARM_PREFERRED_TARGET should still return
KVM_ARM_TARGET_XGENE_POTENZA on an XGene platform, and
KVM_ARM_VCPU_INIT should still be accept it).
What would be the gain of such a mapping? Added complexity, hardly
anything else. We're much better off considering the generic target as
a new one, both inside the kernel and in the view we export to
userspace.
Thanks,
M.
--
Jazz is not dead. It just smells funny.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
WARNING: multiple messages have this Message-ID (diff)
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64/kvm: Add generic v8 KVM target
Date: Mon, 22 Jun 2015 07:47:59 +0100 [thread overview]
Message-ID: <20150622074759.01d677a3@arm.com> (raw)
In-Reply-To: <55847C1F.1090606@codeaurora.org>
On Fri, 19 Jun 2015 21:31:27 +0100
Timur Tabi <timur@codeaurora.org> wrote:
> On 06/17/2015 04:00 AM, Suzuki K. Poulose wrote:
> > &genericv8_target_table);
> > kvm_register_target_sys_reg_table(KVM_ARM_TARGET_XGENE_POTENZA,
> > &genericv8_target_table);
> > +
> > kvm_register_target_sys_reg_table(KVM_ARM_TARGET_GENERIC_V8,
> > + &genericv8_target_table);
> >
>
> Shouldn't you also remove all of the previous lines that return
> &genericv8_target_table?
No. KVM_ARM_TARGET_* are part of the uapi, and existing userspace knows
about them. You can't just drop them.
What you *could* do would be to map the existing targets to the generic
one in a way that leaves userspace blissfully unaware of the underlying
change (for example, KVM_ARM_PREFERRED_TARGET should still return
KVM_ARM_TARGET_XGENE_POTENZA on an XGene platform, and
KVM_ARM_VCPU_INIT should still be accept it).
What would be the gain of such a mapping? Added complexity, hardly
anything else. We're much better off considering the generic target as
a new one, both inside the kernel and in the view we export to
userspace.
Thanks,
M.
--
Jazz is not dead. It just smells funny.
next prev parent reply other threads:[~2015-06-22 6:47 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 9:00 [PATCH] arm64/kvm: Add generic v8 KVM target Suzuki K. Poulose
2015-06-17 9:00 ` Suzuki K. Poulose
2015-06-19 20:31 ` Timur Tabi
2015-06-19 20:31 ` Timur Tabi
2015-06-22 6:47 ` Marc Zyngier [this message]
2015-06-22 6:47 ` Marc Zyngier
2015-06-22 8:44 ` Peter Maydell
2015-06-22 8:44 ` Peter Maydell
2015-06-23 12:39 ` Christoffer Dall
2015-06-23 12:39 ` Christoffer Dall
2015-06-23 14:03 ` Suzuki K. Poulose
2015-06-23 14:03 ` Suzuki K. Poulose
2015-06-23 14:16 ` Peter Maydell
2015-06-23 14:16 ` Peter Maydell
2015-06-24 8:29 ` Marc Zyngier
2015-06-24 8:29 ` Marc Zyngier
2015-06-24 8:51 ` Christoffer Dall
2015-06-24 8:51 ` Christoffer Dall
2015-06-24 9:32 ` Marc Zyngier
2015-06-24 9:32 ` Marc Zyngier
2015-06-25 12:30 ` Christoffer Dall
2015-06-25 12:30 ` Christoffer Dall
2015-06-25 12:40 ` Marc Zyngier
2015-06-25 12:40 ` Marc Zyngier
2015-06-25 13:44 ` Marc Zyngier
2015-06-25 13:44 ` Marc Zyngier
2015-06-25 13:49 ` Peter Maydell
2015-06-25 13:49 ` Peter Maydell
2015-06-26 9:53 ` Christoffer Dall
2015-06-26 9:53 ` Christoffer Dall
2015-06-29 17:13 ` Chalamarla, Tirumalesh
2015-06-29 17:13 ` Chalamarla, Tirumalesh
2015-06-29 17:30 ` Marc Zyngier
2015-06-29 17:30 ` Marc Zyngier
2015-06-29 17:38 ` Peter Maydell
2015-06-29 17:38 ` Peter Maydell
2015-06-29 17:52 ` Marc Zyngier
2015-06-29 17:52 ` Marc Zyngier
2015-06-29 18:39 ` Chalamarla, Tirumalesh
2015-06-29 18:39 ` Chalamarla, Tirumalesh
2015-07-02 20:29 ` Chalamarla, Tirumalesh
2015-07-03 8:08 ` Marc Zyngier
2015-07-03 8:08 ` Marc Zyngier
2015-07-03 8:12 ` Peter Maydell
2015-07-03 8:12 ` Peter Maydell
2015-07-03 8:28 ` Marc Zyngier
2015-07-03 8:28 ` Marc Zyngier
2015-07-03 9:34 ` Peter Maydell
2015-07-03 9:34 ` Peter Maydell
2015-07-03 10:10 ` Marc Zyngier
2015-07-03 10:10 ` Marc Zyngier
2015-07-17 9:33 ` Christoffer Dall
2015-07-17 9:33 ` Christoffer Dall
2015-07-17 9:56 ` Marc Zyngier
2015-07-17 9:56 ` Marc Zyngier
2015-07-17 10:15 ` Christoffer Dall
2015-07-17 10:15 ` Christoffer Dall
2015-07-17 10:19 ` Marc Zyngier
2015-07-17 10:19 ` Marc Zyngier
2015-07-17 17:56 ` Chalamarla, Tirumalesh
2015-07-17 17:56 ` Chalamarla, Tirumalesh
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=20150622074759.01d677a3@arm.com \
--to=marc.zyngier@arm.com \
--cc=Suzuki.Poulose@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=shankerd@codeaurora.org \
--cc=timur@codeaurora.org \
--cc=vgandhi@codeaurora.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.