[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20161221125920.GG15917@rkaganb.sw.ru>
Date: Wed, 21 Dec 2016 15:59:20 +0300
From: Roman Kagan <rkagan@...tuozzo.com>
To: Christoph Hellwig <hch@...radead.org>
CC: Stephen Hemminger <stephen@...workplumber.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Radim Krčmář <rkrcmar@...hat.com>,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>, <kvm@...r.kernel.org>,
"Denis V . Lunev" <den@...nvz.org>,
Haiyang Zhang <haiyangz@...rosoft.com>, <x86@...nel.org>,
<linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, <devel@...uxdriverproject.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 12/15] hyperv: move VMBus connection ids to uapi
On Wed, Dec 21, 2016 at 04:18:58AM -0800, Christoph Hellwig wrote:
> On Wed, Dec 21, 2016 at 09:29:39AM +0300, Roman Kagan wrote:
> > QEMU in particular. We're planning to implement VMBus devices in QEMU
> > and would like to have the definitions shared with the Linux guest
> > drivers for Hyper-V.
>
> And that's everything but a userspace API. The way to go for protocol
> constants is to have a normal kernel header that is not exported, and
> a copy of it wherever else you need it.
That's fine by me.
I guess the series should then start with a complete move
arch/x86/include/uapi/asm/hyperv.h ->
arch/x86/include/asm/hyperv_proto.h, and the remaining patches have to
change the latter instead of the former?
Thanks,
Roman.
Powered by blists - more mailing lists