From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 1/4] arm/arm64: KVM: Add KVM_GET/SET_VCPU_EVENTS
Date: Wed, 11 Jul 2018 08:45:11 +0100 [thread overview]
Message-ID: <1cbb0f3f-1bc4-5205-d28c-1843d09a702e@arm.com> (raw)
In-Reply-To: <b0eb95f3-7905-8aab-f816-529c17f07e04@huawei.com>
On 11/07/18 07:48, gengdongjiu wrote:
> Hi, James,
>
> [...]
>> diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt
>> index d10944e619d3..e3940f8715a5 100644
>> --- a/Documentation/virtual/kvm/api.txt
>> +++ b/Documentation/virtual/kvm/api.txt
>> @@ -835,11 +835,13 @@ struct kvm_clock_data {
>>
>> Capability: KVM_CAP_VCPU_EVENTS
>> Extended by: KVM_CAP_INTR_SHADOW
>> -Architectures: x86
>> -Type: vm ioctl
>> +Architectures: x86, arm64
>
> In my previous patch, I only add the arm64 support, now you add patches to support arm32 platform,
> so you can add "ARM" to the Architectures, for example: "Architectures: x86, ARM, arm64"
That should be the job of the last patch, shouldn't it? At this point in
the series, there is no 32bit support whatsoever.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2018-07-11 7:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 16:49 [PATCH v7 0/4] support exception state migration and set VSESR_EL2 by user space James Morse
2018-07-10 16:49 ` [PATCH v7 1/4] arm/arm64: KVM: Add KVM_GET/SET_VCPU_EVENTS James Morse
2018-07-11 6:48 ` gengdongjiu
2018-07-11 7:45 ` Marc Zyngier [this message]
2018-07-10 16:49 ` [PATCH v7 2/4] arm64: KVM: export the capability to set guest SError syndrome James Morse
2018-07-10 16:49 ` [PATCH v7 3/4] KVM: arm64: Share the parts of get/set events useful to 32bit James Morse
2018-07-11 7:16 ` gengdongjiu
2018-07-13 15:27 ` James Morse
2018-07-10 16:49 ` [PATCH v7 4/4] KVM: arm: Add 32bit get/set events support James Morse
2018-07-11 3:14 ` [PATCH v7 0/4] support exception state migration and set VSESR_EL2 by user space gengdongjiu
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=1cbb0f3f-1bc4-5205-d28c-1843d09a702e@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).