From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Tianyu Lan <Tianyu.Lan@microsoft.com>,
"lantianyu1986\@gmail.com" <lantianyu1986@gmail.com>
Cc: "qemu-devel\@nongnu.org" <qemu-devel@nongnu.org>,
"kvm\@vger.kernel.org" <kvm@vger.kernel.org>,
"mst\@redhat.com" <mst@redhat.com>,
"cohuck\@redhat.com" <cohuck@redhat.com>,
"pbonzini\@redhat.com" <pbonzini@redhat.com>,
"rth\@twiddle.net" <rth@twiddle.net>,
"ehabkost\@redhat.com" <ehabkost@redhat.com>,
"mtosatti\@redhat.com" <mtosatti@redhat.com>,
Roman Kagan <rkagan@virtuozzo.com>
Subject: Re: [PATCH] target/i386/kvm: Add Hyper-V direct tlb flush support
Date: Mon, 14 Oct 2019 16:57:14 +0200 [thread overview]
Message-ID: <875zkr5q9h.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <KL1P15301MB02611D1F7C54C4A599766B8D92900@KL1P15301MB0261.APCP153.PROD.OUTLOOK.COM>
Tianyu Lan <Tianyu.Lan@microsoft.com> writes:
>> > --- a/linux-headers/linux/kvm.h
>> > +++ b/linux-headers/linux/kvm.h
>> > @@ -995,6 +995,7 @@ struct kvm_ppc_resize_hpt {
>> > #define KVM_CAP_ARM_SVE 170
>> > #define KVM_CAP_ARM_PTRAUTH_ADDRESS 171
>> > #define KVM_CAP_ARM_PTRAUTH_GENERIC 172
>> > +#define KVM_CAP_HYPERV_DIRECT_TLBFLUSH 174
>>
>> I was once told that scripts/update-linux-headers.sh script is supposed
>> to be used instead of cherry-picking stuff you need (adn this would be a
>> separate patch - update linux headers to smth).
>>
>
> Thanks for suggestion. I just try the update-linux-headers.sh and there are a lot
> of changes which are not related with my patch. I also include these
> changes in my patch, right?
>
Yes, see e.g.
commit d9cb4336159a00bd0d9c81b93f02874ef3626057
Author: Cornelia Huck <cohuck@redhat.com>
Date: Thu May 16 19:10:36 2019 +0200
linux headers: update against Linux 5.2-rc1
as an example.
--
Vitaly
WARNING: multiple messages have this Message-ID (diff)
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Tianyu Lan <Tianyu.Lan@microsoft.com>,
"lantianyu1986\@gmail.com" <lantianyu1986@gmail.com>
Cc: "mtosatti@redhat.com" <mtosatti@redhat.com>,
"ehabkost@redhat.com" <ehabkost@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"mst@redhat.com" <mst@redhat.com>,
"cohuck@redhat.com" <cohuck@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Roman Kagan <rkagan@virtuozzo.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"rth@twiddle.net" <rth@twiddle.net>
Subject: Re: [PATCH] target/i386/kvm: Add Hyper-V direct tlb flush support
Date: Mon, 14 Oct 2019 16:57:14 +0200 [thread overview]
Message-ID: <875zkr5q9h.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <KL1P15301MB02611D1F7C54C4A599766B8D92900@KL1P15301MB0261.APCP153.PROD.OUTLOOK.COM>
Tianyu Lan <Tianyu.Lan@microsoft.com> writes:
>> > --- a/linux-headers/linux/kvm.h
>> > +++ b/linux-headers/linux/kvm.h
>> > @@ -995,6 +995,7 @@ struct kvm_ppc_resize_hpt {
>> > #define KVM_CAP_ARM_SVE 170
>> > #define KVM_CAP_ARM_PTRAUTH_ADDRESS 171
>> > #define KVM_CAP_ARM_PTRAUTH_GENERIC 172
>> > +#define KVM_CAP_HYPERV_DIRECT_TLBFLUSH 174
>>
>> I was once told that scripts/update-linux-headers.sh script is supposed
>> to be used instead of cherry-picking stuff you need (adn this would be a
>> separate patch - update linux headers to smth).
>>
>
> Thanks for suggestion. I just try the update-linux-headers.sh and there are a lot
> of changes which are not related with my patch. I also include these
> changes in my patch, right?
>
Yes, see e.g.
commit d9cb4336159a00bd0d9c81b93f02874ef3626057
Author: Cornelia Huck <cohuck@redhat.com>
Date: Thu May 16 19:10:36 2019 +0200
linux headers: update against Linux 5.2-rc1
as an example.
--
Vitaly
next prev parent reply other threads:[~2019-10-14 14:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 3:41 [PATCH] target/i386/kvm: Add Hyper-V direct tlb flush support lantianyu1986
2019-10-13 8:49 ` Vitaly Kuznetsov
2019-10-13 8:49 ` Vitaly Kuznetsov
2019-10-14 13:29 ` Tianyu Lan
2019-10-14 13:48 ` Cornelia Huck
2019-10-14 13:48 ` Cornelia Huck
2019-10-14 14:26 ` Tianyu Lan
2019-10-14 14:57 ` Vitaly Kuznetsov [this message]
2019-10-14 14:57 ` Vitaly Kuznetsov
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=875zkr5q9h.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=cohuck@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lantianyu1986@gmail.com \
--cc=mst@redhat.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=rth@twiddle.net \
/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.