From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Stephen Hemminger" <sthemmin@microsoft.com>,
kvm@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
"Michael Kelley (EOSG)" <Michael.H.Kelley@microsoft.com>,
"Roman Kagan" <rkagan@virtuozzo.com>,
"Andy Lutomirski" <luto@kernel.org>,
devel@linuxdriverproject.org,
"Mohammed Gamal" <mmorsy@redhat.com>
Subject: Re: [PATCH v2 0/7] x86/kvm/hyperv: stable clocksorce for L2 guests when running nested KVM on Hyper-V
Date: Wed, 03 Jan 2018 15:57:58 +0100 [thread overview]
Message-ID: <87373nt2fd.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <87r2rw2v8x.fsf@vitty.brq.redhat.com> (Vitaly Kuznetsov's message of "Fri, 15 Dec 2017 10:30:54 +0100")
Vitaly Kuznetsov <vkuznets@redhat.com> writes:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>>
>> Patches 5-7 are
>>
>> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
>>
>> I would appreciate if the Hyper-V folks can provide a topic branch to be
>> merged in both HV and KVM trees.
>>
>
> There's no such thing as Hyper-V tree, patches are usually getting
> merged through 'tip' tree when the majority of changes go to arch/x86 or
> Greg's char-misc tree when changes are drivers/hv heavy (+ net, scsi,
> pci, hid, ... trees for individual drivers).
>
> In this particular case the series is x86-heavy and I believe it should
> go through x86 'tip' tree.
>
> Thomas, Ingo, Peter, could you please take a look? Thanks!
Gentle ping after the holidays season :-)
--
Vitaly
prev parent reply other threads:[~2018-01-03 14:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 15:09 Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 1/7] x86/hyper-v: check for required priviliges in hyperv_init() Vitaly Kuznetsov
2018-01-14 20:32 ` Thomas Gleixner
2017-12-13 15:09 ` [PATCH v2 2/7] x86/hyper-v: add a function to read both TSC and TSC page value simulateneously Vitaly Kuznetsov
2018-01-14 20:35 ` Thomas Gleixner
2018-01-15 10:45 ` Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 3/7] x86/hyper-v: reenlightenment notifications support Vitaly Kuznetsov
2018-01-14 20:42 ` Thomas Gleixner
2017-12-13 15:09 ` [PATCH v2 4/7] x86/hyper-v: redirect reenlightment notifications on CPU offlining Vitaly Kuznetsov
2018-01-14 20:44 ` Thomas Gleixner
2018-01-15 10:44 ` Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 5/7] x86/irq: Count Hyper-V reenlightenment interrupts Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 6/7] x86/kvm: pass stable clocksource to guests when running nested on Hyper-V Vitaly Kuznetsov
2017-12-13 15:09 ` [PATCH v2 7/7] x86/kvm: support Hyper-V reenlightenment Vitaly Kuznetsov
2017-12-15 9:01 ` [PATCH v2 0/7] x86/kvm/hyperv: stable clocksorce for L2 guests when running nested KVM on Hyper-V Paolo Bonzini
2017-12-15 9:30 ` Vitaly Kuznetsov
2018-01-03 14:57 ` Vitaly Kuznetsov [this message]
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=87373nt2fd.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=Michael.H.Kelley@microsoft.com \
--cc=devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=mmorsy@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rkagan@virtuozzo.com \
--cc=rkrcmar@redhat.com \
--cc=sthemmin@microsoft.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
Powered by JetHome