From: "K. Y. Srinivasan" <kys@microsoft.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
vkuznets@redhat.com, jasowang@redhat.com,
leann.ogasawara@canonical.com, rkagan@virtuozzo.com,
x86@kernel.org, tglx@linutronix.de, hpa@zytor.com
Cc: "K. Y. Srinivasan" <kys@microsoft.com>
Subject: [PATCH 00/18] Drivers: hv: vmbus: Restructure architecture specific code
Date: Fri, 30 Dec 2016 13:34:22 -0800 [thread overview]
Message-ID: <1483133662-29697-1-git-send-email-kys@microsoft.com> (raw)
The current Hyper-V code under drivers/hv has bunch of X86 specific code.
Restructure the code and move al architecture specific code to the
appropriate files.
As I was working on this restructuring, Roman Kagan <rkagan@virtuozzo.com>
has submitted patches to restructure the Hyper-V header files to address
a different need - to share the definitions across all Hyper-V drivers
including QEMU based drivers. Roman and I will coordinate our work.
K. Y. Srinivasan (18):
Drivers: hv: vmbus: Move the definition of
hv_x64_msr_hypercall_contents
Drivers: hv: vmbus: Move the definition of generate_guest_id()
Drivers: hv vmbus: Move Hypercall page setup out of common code
Drivers: hv: vmbus: Move Hypercall invocation code out of common code
Drivers: hv: vmbus: Consolidate all Hyper-V specific clocksource code
Drivers: hv: vmbus: Move the extracting of Hypervisor version
information
Drivers: hv: vmbus: Move the crash notification function
Drivers: hv: vmbus: Move the check for hypercall page setup
Drivers: hv: vmbus: Move the code to signal end of message
Drivers: hv: vmbus: Restructure the clockevents code
Drivers: hv: util: Use hv_get_current_tick() to get current tick
Drivers: hv: vmbus: Get rid of an unsused variable
Drivers: hv: vmbus: Define APIs to manipulate the message page
Drivers: hv: vmbus: Define APIs to manipulate the event page
Drivers: hv: vmbus: Define APIs to manipulate the synthetic interrupt
controller
Drivers: hv: vmbus: Define an API to retrieve virtual processor index
Drivers: hv: vmbus: Define an APIs to manage interrupt state
Drivers: hv: vmbus: Cleanup hyperv_vmbus.h
arch/x86/Kbuild | 3 +
arch/x86/hyperv/Makefile | 1 +
arch/x86/hyperv/hv_init.c | 251 ++++++++++++++++++++++++++++++
arch/x86/include/asm/mshyperv.h | 147 ++++++++++++++++++
arch/x86/include/uapi/asm/hyperv.h | 8 +
arch/x86/kernel/cpu/mshyperv.c | 50 ++++---
drivers/hv/channel_mgmt.c | 1 +
drivers/hv/connection.c | 7 +-
drivers/hv/hv.c | 296 ++++--------------------------------
drivers/hv/hv_util.c | 3 +-
drivers/hv/hyperv_vmbus.h | 291 +-----------------------------------
drivers/hv/vmbus_drv.c | 25 ---
12 files changed, 472 insertions(+), 611 deletions(-)
create mode 100644 arch/x86/hyperv/Makefile
create mode 100644 arch/x86/hyperv/hv_init.c
--
1.7.4.1
next reply other threads:[~2016-12-30 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 21:34 K. Y. Srinivasan [this message]
2016-12-30 21:35 kys
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=1483133662-29697-1-git-send-email-kys@microsoft.com \
--to=kys@microsoft.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jasowang@redhat.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=rkagan@virtuozzo.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--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