linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: KY Srinivasan <kys@microsoft.com>
To: "Roman Kagan" <rkagan@virtuozzo.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"Vitaly Kuznetsov" <vkuznets@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	"x86@kernel.org" <x86@kernel.org>,
	"Haiyang Zhang" <haiyangz@microsoft.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"Denis V . Lunev" <den@openvz.org>
Subject: RE: [PATCH 02/15] hyperv: uapi-fy synic event flags definitions
Date: Wed, 21 Dec 2016 18:58:38 +0000	[thread overview]
Message-ID: <DM5PR03MB24905708A8952D8A59265CAAA0930@DM5PR03MB2490.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20161220155602.6298-3-rkagan@virtuozzo.com>



> -----Original Message-----
> From: Roman Kagan [mailto:rkagan@virtuozzo.com]
> Sent: Tuesday, December 20, 2016 7:56 AM
> To: Paolo Bonzini <pbonzini@redhat.com>; Radim Krčmář
> <rkrcmar@redhat.com>; KY Srinivasan <kys@microsoft.com>; Vitaly
> Kuznetsov <vkuznets@redhat.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>; Ingo Molnar
> <mingo@redhat.com>; H. Peter Anvin <hpa@zytor.com>; x86@kernel.org;
> Haiyang Zhang <haiyangz@microsoft.com>; kvm@vger.kernel.org; linux-
> kernel@vger.kernel.org; devel@linuxdriverproject.org; Denis V . Lunev
> <den@openvz.org>; Roman Kagan <rkagan@virtuozzo.com>
> Subject: [PATCH 02/15] hyperv: uapi-fy synic event flags definitions
> 
> Move definitions related to the Hyper-V SynIC event flags to a header
> where they can be consumed by userspace.
> 
> While doing so, also clean up their use by switching to standard bitops
> and struct-based dereferencing.  The latter is also done for message
> pages.

Please breakup this patch.
> 
> Signed-off-by: Roman Kagan <rkagan@virtuozzo.com>
> ---
>  arch/x86/include/uapi/asm/hyperv.h | 13 +++++++++
>  drivers/hv/hyperv_vmbus.h          | 24 ++--------------
>  drivers/hv/channel_mgmt.c          | 10 +++----
>  drivers/hv/connection.c            | 47 ++++++++++---------------------
>  drivers/hv/vmbus_drv.c             | 57 ++++++++++++++------------------------
>  5 files changed, 54 insertions(+), 97 deletions(-)
> 
> diff --git a/arch/x86/include/uapi/asm/hyperv.h
> b/arch/x86/include/uapi/asm/hyperv.h
> index 6098ab5..af542a3 100644
> --- a/arch/x86/include/uapi/asm/hyperv.h
> +++ b/arch/x86/include/uapi/asm/hyperv.h
> @@ -363,4 +363,17 @@ struct hv_timer_message_payload {
>  #define HV_STIMER_AUTOENABLE		(1ULL << 3)
>  #define HV_STIMER_SINT(config)		(__u8)(((config) >> 16) &
> 0x0F)
> 
> +/* Define synthetic interrupt controller flag constants. */
> +#define HV_EVENT_FLAGS_COUNT		(256 * 8)
> +
> +/* Define the synthetic interrupt controller event flags format. */
> +struct hv_synic_event_flags {
> +	__u64 flags[HV_EVENT_FLAGS_COUNT / 64];
> +};
> +
> +/* Define the synthetic interrupt flags page layout. */
> +struct hv_synic_event_flags_page {
> +	struct hv_synic_event_flags
> sintevent_flags[HV_SYNIC_SINT_COUNT];
> +};
> +
>  #endif
> diff --git a/drivers/hv/hyperv_vmbus.h b/drivers/hv/hyperv_vmbus.h
> index 4516498..4fab154 100644
> --- a/drivers/hv/hyperv_vmbus.h
> +++ b/drivers/hv/hyperv_vmbus.h
> @@ -26,7 +26,6 @@
>  #define _HYPERV_VMBUS_H
> 
>  #include <linux/list.h>
> -#include <asm/sync_bitops.h>
>  #include <linux/atomic.h>
>  #include <linux/hyperv.h>
> 
> @@ -75,11 +74,6 @@ enum hv_cpuid_function {
> 
>  #define HV_ANY_VP			(0xFFFFFFFF)
> 
> -/* Define synthetic interrupt controller flag constants. */
> -#define HV_EVENT_FLAGS_COUNT		(256 * 8)
> -#define HV_EVENT_FLAGS_BYTE_COUNT	(256)
> -#define HV_EVENT_FLAGS_DWORD_COUNT	(256 / sizeof(u32))
> -
>  /* Define invalid partition identifier. */
>  #define HV_PARTITION_ID_INVALID		((u64)0x0)
> 
> @@ -146,20 +140,6 @@ union hv_timer_config {
>  	};
>  };
> 
> -/* Define the number of message buffers associated with each port. */
> -#define HV_PORT_MESSAGE_BUFFER_COUNT	(16)
> -
> -/* Define the synthetic interrupt controller event flags format. */
> -union hv_synic_event_flags {
> -	u8 flags8[HV_EVENT_FLAGS_BYTE_COUNT];
> -	u32 flags32[HV_EVENT_FLAGS_DWORD_COUNT];
> -};
> -
> -/* Define the synthetic interrupt flags page layout. */
> -struct hv_synic_event_flags_page {
> -	union hv_synic_event_flags
> sintevent_flags[HV_SYNIC_SINT_COUNT];
> -};
> -
>  /* Define SynIC control register. */
>  union hv_synic_scontrol {
>  	u64 as_uint64;
> @@ -434,8 +414,8 @@ struct hv_context {
> 
>  	bool synic_initialized;
> 
> -	void *synic_message_page[NR_CPUS];
> -	void *synic_event_page[NR_CPUS];
> +	struct hv_message_page *synic_message_page[NR_CPUS];
> +	struct hv_synic_event_flags_page *synic_event_page[NR_CPUS];
>  	/*
>  	 * Hypervisor's notion of virtual processor ID is different from
>  	 * Linux' notion of CPU ID. This information can only be retrieved
> diff --git a/drivers/hv/channel_mgmt.c b/drivers/hv/channel_mgmt.c
> index 26b4192..49eaae2 100644
> --- a/drivers/hv/channel_mgmt.c
> +++ b/drivers/hv/channel_mgmt.c
> @@ -654,7 +654,6 @@ static void init_vp_index(struct vmbus_channel
> *channel, u16 dev_type)
>  static void vmbus_wait_for_unload(void)
>  {
>  	int cpu;
> -	void *page_addr;
>  	struct hv_message *msg;
>  	struct vmbus_channel_message_header *hdr;
>  	u32 message_type;
> @@ -673,9 +672,8 @@ static void vmbus_wait_for_unload(void)
>  			break;
> 
>  		for_each_online_cpu(cpu) {
> -			page_addr = hv_context.synic_message_page[cpu];
> -			msg = (struct hv_message *)page_addr +
> -				VMBUS_MESSAGE_SINT;
> +			msg = &hv_context.synic_message_page[cpu]->
> +
> 	sint_message[VMBUS_MESSAGE_SINT];
> 
>  			message_type = READ_ONCE(msg-
> >header.message_type);
>  			if (message_type == HVMSG_NONE)
> @@ -699,8 +697,8 @@ static void vmbus_wait_for_unload(void)
>  	 * messages after we reconnect.
>  	 */
>  	for_each_online_cpu(cpu) {
> -		page_addr = hv_context.synic_message_page[cpu];
> -		msg = (struct hv_message *)page_addr +
> VMBUS_MESSAGE_SINT;
> +		msg = &hv_context.synic_message_page[cpu]->
> +				sint_message[VMBUS_MESSAGE_SINT];
>  		msg->header.message_type = HVMSG_NONE;
>  	}
>  }
> diff --git a/drivers/hv/connection.c b/drivers/hv/connection.c
> index 6ce8b87..aaa2103 100644
> --- a/drivers/hv/connection.c
> +++ b/drivers/hv/connection.c
> @@ -381,17 +381,12 @@ static void process_chn_event(u32 relid)
>   */
>  void vmbus_on_event(unsigned long data)
>  {
> -	u32 dword;
> -	u32 maxdword;
> -	int bit;
> -	u32 relid;
> -	u32 *recv_int_page = NULL;
> -	void *page_addr;
> +	u32 relid, max_relid;
> +	unsigned long *recv_int_page;
>  	int cpu = smp_processor_id();
> -	union hv_synic_event_flags *event;
> 
>  	if (vmbus_proto_version < VERSION_WIN8) {
> -		maxdword = MAX_NUM_CHANNELS_SUPPORTED >> 5;
> +		max_relid = MAX_NUM_CHANNELS_SUPPORTED;
>  		recv_int_page = vmbus_connection.recv_int_page;
>  	} else {
>  		/*
> @@ -399,36 +394,22 @@ void vmbus_on_event(unsigned long data)
>  		 * can be directly checked to get the id of the channel
>  		 * that has the interrupt pending.
>  		 */
> -		maxdword = HV_EVENT_FLAGS_DWORD_COUNT;
> -		page_addr = hv_context.synic_event_page[cpu];
> -		event = (union hv_synic_event_flags *)page_addr +
> -						 VMBUS_MESSAGE_SINT;
> -		recv_int_page = event->flags32;
> +		struct hv_synic_event_flags *event =
> +			&hv_context.synic_event_page[cpu]->
> +				sintevent_flags[VMBUS_MESSAGE_SINT];
> +		max_relid = HV_EVENT_FLAGS_COUNT;
> +		recv_int_page = (unsigned long *)event->flags;
>  	}
> 
> -
> -
>  	/* Check events */
>  	if (!recv_int_page)
>  		return;
> -	for (dword = 0; dword < maxdword; dword++) {
> -		if (!recv_int_page[dword])
> -			continue;
> -		for (bit = 0; bit < 32; bit++) {
> -			if (sync_test_and_clear_bit(bit,
> -				(unsigned long *)&recv_int_page[dword])) {
> -				relid = (dword << 5) + bit;
> -
> -				if (relid == 0)
> -					/*
> -					 * Special case - vmbus
> -					 * channel protocol msg
> -					 */
> -					continue;
> -
> -				process_chn_event(relid);
> -			}
> -		}
> +
> +	/* relid == 0 is vmbus channel protocol msg */
> +	relid = 1;
> +	for_each_set_bit_from(relid, recv_int_page, max_relid) {
> +		clear_bit(relid, recv_int_page);

We are using this test_and_clear_bit paradigm for locking. The current code
used the sync variant to ensure the host saw the changes we were making
here (clearing the bit). You may want to add a barrier here or use the sync
variant.
 
> +		process_chn_event(relid);
>  	}
>  }
> 
> diff --git a/drivers/hv/vmbus_drv.c b/drivers/hv/vmbus_drv.c
> index 230c62e..13dd210 100644
> --- a/drivers/hv/vmbus_drv.c
> +++ b/drivers/hv/vmbus_drv.c
> @@ -872,9 +872,8 @@ static void hv_process_timer_expiration(struct
> hv_message *msg, int cpu)
>  void vmbus_on_msg_dpc(unsigned long data)
>  {
>  	int cpu = smp_processor_id();
> -	void *page_addr = hv_context.synic_message_page[cpu];
> -	struct hv_message *msg = (struct hv_message *)page_addr +
> -				  VMBUS_MESSAGE_SINT;
> +	struct hv_message *msg = &hv_context.synic_message_page[cpu]-
> >
> +
> 	sint_message[VMBUS_MESSAGE_SINT];
>  	struct vmbus_channel_message_header *hdr;
>  	struct vmbus_channel_message_table_entry *entry;
>  	struct onmessage_work_context *ctx;
> @@ -911,54 +910,40 @@ void vmbus_on_msg_dpc(unsigned long data)
>  static void vmbus_isr(void)
>  {
>  	int cpu = smp_processor_id();
> -	void *page_addr;
>  	struct hv_message *msg;
> -	union hv_synic_event_flags *event;
> -	bool handled = false;
> +	struct hv_synic_event_flags *event;
> 
> -	page_addr = hv_context.synic_event_page[cpu];
> -	if (page_addr == NULL)
> +	if (!hv_context.synic_event_page[cpu])
>  		return;
> 
> -	event = (union hv_synic_event_flags *)page_addr +
> -					 VMBUS_MESSAGE_SINT;
> +	event = &hv_context.synic_event_page[cpu]->
> +			sintevent_flags[VMBUS_MESSAGE_SINT];
>  	/*
>  	 * Check for events before checking for messages. This is the order
>  	 * in which events and messages are checked in Windows guests on
>  	 * Hyper-V, and the Windows team suggested we do the same.
>  	 */
> 
> -	if ((vmbus_proto_version == VERSION_WS2008) ||
> -		(vmbus_proto_version == VERSION_WIN7)) {
> -
> +	/* On win8 and above the channel interrupts are signaled directly in
> +	 * the event page and will be checked in the .event_dpc
> +	 */
> +	if (vmbus_proto_version >= VERSION_WIN8 ||
>  		/* Since we are a child, we only need to check bit 0 */
> -		if (sync_test_and_clear_bit(0,
> -			(unsigned long *) &event->flags32[0])) {
> -			handled = true;
> -		}
> -	} else {
> -		/*
> -		 * Our host is win8 or above. The signaling mechanism
> -		 * has changed and we can directly look at the event page.
> -		 * If bit n is set then we have an interrup on the channel
> -		 * whose id is n.
> -		 */
> -		handled = true;
> -	}
> -
> -	if (handled)
> +	    test_and_clear_bit(0, (unsigned long *)event->flags))

Don't we need the sync variant of test_and_clear_bit here.

>  		tasklet_schedule(hv_context.event_dpc[cpu]);
> 
> -
> -	page_addr = hv_context.synic_message_page[cpu];
> -	msg = (struct hv_message *)page_addr + VMBUS_MESSAGE_SINT;
> +	msg = &hv_context.synic_message_page[cpu]->
> +			sint_message[VMBUS_MESSAGE_SINT];
> 
>  	/* Check if there are actual msgs to be processed */
> -	if (msg->header.message_type != HVMSG_NONE) {
> -		if (msg->header.message_type == HVMSG_TIMER_EXPIRED)
> -			hv_process_timer_expiration(msg, cpu);
> -		else
> -			tasklet_schedule(hv_context.msg_dpc[cpu]);
> +	switch (READ_ONCE(msg->header.message_type)) {
> +	case HVMSG_NONE:
> +		break;
> +	case HVMSG_TIMER_EXPIRED:
> +		hv_process_timer_expiration(msg, cpu);
> +		break;
> +	default:
> +		tasklet_schedule(hv_context.msg_dpc[cpu]);
>  	}
> 
>  	add_interrupt_randomness(HYPERVISOR_CALLBACK_VECTOR, 0);
> --
> 2.9.3

  parent reply	other threads:[~2016-12-21 18:58 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-20 15:55 [PATCH 00/15] hyperv: more stuff to uapi + cleanup Roman Kagan
2016-12-20 15:55 ` [PATCH 01/15] hyperv: consolidate TSC ref page definitions Roman Kagan
2016-12-20 20:57   ` KY Srinivasan
2016-12-21  6:25     ` Roman Kagan
2016-12-20 15:55 ` [PATCH 02/15] hyperv: uapi-fy synic event flags definitions Roman Kagan
2016-12-20 17:24   ` Stephen Hemminger
2016-12-21  6:33     ` Roman Kagan
2016-12-21 10:58   ` kbuild test robot
2016-12-21 18:58   ` KY Srinivasan [this message]
2016-12-20 15:55 ` [PATCH 03/15] hyperv: use standard bitops Roman Kagan
2016-12-21 12:00   ` Olaf Hering
2016-12-21 13:23     ` Roman Kagan
2016-12-22 12:33       ` Paolo Bonzini
2016-12-21 19:08   ` KY Srinivasan
2016-12-20 15:55 ` [PATCH 04/15] hyperv: define VMBus message type Roman Kagan
2016-12-20 15:55 ` [PATCH 05/15] hyperv: GFP_ATOMIC -> GFP_KERNEL Roman Kagan
2016-12-20 15:55 ` [PATCH 06/15] hyperv: avoid unnecessary vmalloc Roman Kagan
2016-12-21 19:19   ` KY Srinivasan
2016-12-20 15:55 ` [PATCH 07/15] hyperv: dedup cpuid definitions Roman Kagan
2016-12-20 15:55 ` [PATCH 08/15] hyperv: dedup crash msr related definitions Roman Kagan
2016-12-20 15:55 ` [PATCH 09/15] hyperv: unify Hyper-V msr definitions Roman Kagan
2016-12-20 15:55 ` [PATCH 10/15] hyperv: uapi-fy PostMessage and SignalEvent hypercall structures Roman Kagan
2016-12-21 19:27   ` KY Srinivasan
2016-12-20 15:55 ` [PATCH 11/15] hyperv: uapi-fy monitored notification structures Roman Kagan
2016-12-20 15:55 ` [PATCH 12/15] hyperv: move VMBus connection ids to uapi Roman Kagan
2016-12-20 17:25   ` Stephen Hemminger
2016-12-21  6:29     ` Roman Kagan
2016-12-21 12:18       ` Christoph Hellwig
2016-12-21 12:59         ` Roman Kagan
2016-12-21 14:26           ` Christoph Hellwig
2016-12-21 14:39             ` Roman Kagan
2016-12-21 15:39             ` Paolo Bonzini
2016-12-21 15:43               ` Christoph Hellwig
2016-12-21 17:25                 ` Paolo Bonzini
2016-12-21 17:50                 ` Stephen Hemminger
2016-12-21 17:53                   ` Paolo Bonzini
2016-12-21 17:58                   ` Christoph Hellwig
2016-12-21 18:02                     ` Stephen Hemminger
2016-12-21 19:54                       ` KY Srinivasan
2016-12-28 17:09                         ` Roman Kagan
2016-12-29 18:29                           ` Stephen Hemminger
2017-01-02  8:19                           ` Paolo Bonzini
2017-01-09  8:32                             ` Roman Kagan
2017-01-09  8:40                               ` hpa
2017-01-09  8:58                                 ` Roman Kagan
2017-01-09  9:02                                 ` Paolo Bonzini
2017-01-02 19:39                           ` Stephen Hemminger
2017-01-03  9:32                             ` Paolo Bonzini
2016-12-20 15:56 ` [PATCH 13/15] hyperv: move function close to its only callsite Roman Kagan
2016-12-20 15:56 ` [PATCH 14/15] hyperv_vmbus: drop unused definitions Roman Kagan
2016-12-20 15:56 ` [PATCH 15/15] hyperv: redefine hv_message without bitfields Roman Kagan
2016-12-21 18:00 ` [PATCH 00/15] hyperv: more stuff to uapi + cleanup KY Srinivasan
2016-12-28 16:57   ` Roman Kagan
2016-12-30 19:45     ` KY Srinivasan

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=DM5PR03MB24905708A8952D8A59265CAAA0930@DM5PR03MB2490.namprd03.prod.outlook.com \
    --to=kys@microsoft.com \
    --cc=den@openvz.org \
    --cc=devel@linuxdriverproject.org \
    --cc=haiyangz@microsoft.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkagan@virtuozzo.com \
    --cc=rkrcmar@redhat.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;
as well as URLs for NNTP newsgroup(s).