From: Cornelia Huck <cohuck@redhat.com>
To: Guoheyi <guoheyi@huawei.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Peter Maydell <peter.maydell@linaro.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marc Zyngier <marc.zyngier@arm.com>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
James Morse <james.morse@arm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
wanghaibin.wang@huawei.com, Dave Martin <Dave.Martin@arm.com>
Subject: Re: [RFC v2 11/14] linux-headers/kvm.h: add capability to forward hypercall
Date: Thu, 7 Nov 2019 13:12:10 +0100 [thread overview]
Message-ID: <20191107131210.26acf011.cohuck@redhat.com> (raw)
In-Reply-To: <da720295-2a84-e38b-9828-5287daefcfa2@huawei.com>
On Thu, 7 Nov 2019 19:57:22 +0800
Guoheyi <guoheyi@huawei.com> wrote:
> On 2019/11/7 16:57, Michael S. Tsirkin wrote:
> > On Thu, Nov 07, 2019 at 09:44:36AM +0800, Guoheyi wrote:
> >>
> >> On 2019/11/7 1:55, Cornelia Huck wrote:
> >>> On Tue, 5 Nov 2019 17:10:53 +0800
> >>> Heyi Guo <guoheyi@huawei.com> wrote:
> >>>
> >>>> To keep backward compatibility, we add new KVM capability
> >>>> "KVM_CAP_FORWARD_HYPERCALL" to probe whether KVM supports forwarding
> >>>> hypercall to userspace.
> >>>>
> >>>> The capability should be enabled explicitly, for we don't want user
> >>>> space application to deal with unexpected hypercall exits. After
> >>>> enabling this cap, all HVC calls unhandled by kvm will be forwarded to
> >>>> user space.
> >>>>
> >>>> Signed-off-by: Heyi Guo <guoheyi@huawei.com>
> >>>> Cc: Peter Maydell <peter.maydell@linaro.org>
> >>>> Cc: "Michael S. Tsirkin" <mst@redhat.com>
> >>>> Cc: Cornelia Huck <cohuck@redhat.com>
> >>>> Cc: Paolo Bonzini <pbonzini@redhat.com>
> >>>> Cc: Dave Martin <Dave.Martin@arm.com>
> >>>> Cc: Marc Zyngier <marc.zyngier@arm.com>
> >>>> Cc: Mark Rutland <mark.rutland@arm.com>
> >>>> Cc: James Morse <james.morse@arm.com>
> >>>> ---
> >>>> linux-headers/linux/kvm.h | 1 +
> >>>> target/arm/sdei.c | 16 ++++++++++++++++
> >>>> target/arm/sdei.h | 2 ++
> >>>> 3 files changed, 19 insertions(+)
> >>>>
> >>>> diff --git a/linux-headers/linux/kvm.h b/linux-headers/linux/kvm.h
> >>>> index 3d9b18f7f8..36c9b3859f 100644
> >>>> --- a/linux-headers/linux/kvm.h
> >>>> +++ b/linux-headers/linux/kvm.h
> >>>> @@ -1000,6 +1000,7 @@ struct kvm_ppc_resize_hpt {
> >>>> #define KVM_CAP_PMU_EVENT_FILTER 173
> >>>> #define KVM_CAP_ARM_IRQ_LINE_LAYOUT_2 174
> >>>> #define KVM_CAP_HYPERV_DIRECT_TLBFLUSH 175
> >>>> +#define KVM_CAP_FORWARD_HYPERCALL 176
> >>>> #ifdef KVM_CAP_IRQ_ROUTING
> >>> Is this cap upstream already? I would have thought your header sync
> >>> would have brought it in, then. (Saying this, that header sync looks
> >>> awfully small.)
> >>>
> >>> If it is not upstream yet, please split off this hunk into a separate
> >>> patch -- it's a bit annoying, but makes life easier for merging.
> >> No, it is not upstream yet. The whole framework and interfaces between KVM
> >> and qemu are still under discussion. I'll keep in mind of this when moving
> >> forward to next steps...
> >>
> >> Thanks,
> >> HG
> > It's best to add it in some other place meanwhile.
> Do you mean to split this patch from the whole patch set and send it
> separately? Sorry I'm not clear about maintainers' work and may bring
> you some trouble...
My preferred approach:
- add a commit entitled "placeholder for headers update" that contains
the not-yet-upstream changes in the header files you need
- base the rest of your work on that
...
<review happens, series looks good>
...
- if kernel changes are upstream: replace the placeholder patch with a
real update (may include separate patches, if you need an additional
header); maintainer merges
- if kernel changes are not yet upstream: maintainer merges with
placeholder to a feature branch, replaces with real update and merges
once kernel patches hit upstream
(not every maintainer does the second approach; they may ask you
instead to resend with a proper headers update once the kernel changes
are upstream)
next prev parent reply other threads:[~2019-11-07 12:14 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 9:10 [RFC v2 00/14] Add SDEI support for arm64 Heyi Guo
2019-11-05 9:10 ` [RFC v2 01/14] update-linux-headers.sh: import linux/arm_sdei.h to standard-headers Heyi Guo
2019-11-05 9:10 ` [RFC v2 02/14] standard-headers: import arm_sdei.h Heyi Guo
2019-11-06 17:52 ` Cornelia Huck
2019-11-07 1:40 ` Guoheyi
2019-11-07 8:50 ` Cornelia Huck
2019-11-07 8:55 ` Michael S. Tsirkin
2019-11-05 9:10 ` [RFC v2 03/14] arm/sdei: add virtual device framework Heyi Guo
2019-11-05 9:10 ` [RFC v2 04/14] arm: add CONFIG_SDEI build flag Heyi Guo
2019-11-05 9:10 ` [RFC v2 05/14] arm/sdei: add support to handle SDEI requests from guest Heyi Guo
2019-11-05 9:10 ` [RFC v2 06/14] arm/sdei: add system reset callback Heyi Guo
2019-11-05 9:10 ` [RFC v2 07/14] arm/sdei: add support to trigger event by GIC interrupt ID Heyi Guo
2019-11-05 9:10 ` [RFC v2 08/14] core/irq: add qemu_irq_remove_intercept interface Heyi Guo
2019-11-05 9:10 ` [RFC v2 09/14] arm/sdei: override qemu_irq handler when binding interrupt Heyi Guo
2019-11-05 9:10 ` [RFC v2 10/14] arm/sdei: add support to register interrupt bind notifier Heyi Guo
2019-11-05 9:10 ` [RFC v2 11/14] linux-headers/kvm.h: add capability to forward hypercall Heyi Guo
2019-11-06 17:55 ` Cornelia Huck
2019-11-07 1:44 ` Guoheyi
2019-11-07 8:57 ` Michael S. Tsirkin
2019-11-07 11:57 ` Guoheyi
2019-11-07 12:12 ` Cornelia Huck [this message]
2019-11-08 1:54 ` Guoheyi
2019-11-05 9:10 ` [RFC v2 12/14] arm/sdei: add stub to fix build failure when SDEI is not enabled Heyi Guo
2019-11-05 9:10 ` [RFC v2 13/14] arm/kvm: handle guest exit of hypercall Heyi Guo
2019-11-05 9:10 ` [RFC v2 14/14] virt/acpi: add SDEI table if SDEI is enabled Heyi Guo
2019-11-12 14:52 ` Igor Mammedov
2019-11-18 6:44 ` Guoheyi
2019-11-05 9:15 ` [RFC v2 00/14] Add SDEI support for arm64 Guoheyi
2019-11-05 9:36 ` no-reply
2019-11-05 9:38 ` no-reply
2019-11-18 6:55 ` Guoheyi
2019-11-18 13:35 ` Peter Maydell
2019-11-18 14:04 ` Guoheyi
2019-12-20 13:44 ` Peter Maydell
2019-12-23 8:20 ` Guoheyi
2020-02-04 8:26 ` Heyi Guo
2020-02-05 13:15 ` Marc Zyngier
2020-02-06 1:20 ` Heyi Guo
2020-02-06 17:30 ` Marc Zyngier
2020-02-07 10:52 ` James Morse
2020-02-07 11:08 ` Peter Maydell
2020-02-07 13:45 ` Heyi Guo
2020-02-07 13:17 ` Heyi Guo
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=20191107131210.26acf011.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=Dave.Martin@arm.com \
--cc=guoheyi@huawei.com \
--cc=james.morse@arm.com \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wanghaibin.wang@huawei.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: 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).