From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS, USER_AGENT_MUTT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id AC5F9C282C0 for ; Wed, 23 Jan 2019 08:00:29 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6EF53217F5 for ; Wed, 23 Jan 2019 08:00:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548230429; bh=BfJbx2cKGBYxo5GnVrlyCRc//7Rlr2l0SyAruRSkW64=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=MQMEYxMAU8tVxJUJMDh89/1ADLi95MWk34zMulRjlyM8x9rz0h2LwfiuvlvsFzK/O FwU/qVag1AFeu03UT+vkHHhVDNi4thuscny9kzLwmmCJa2AQFD7eD5QiwGsjLQSRPY /Up44+0frBTK9hEjzgU4arU3yjxymb3qGFIZIj8U= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726000AbfAWIA2 (ORCPT ); Wed, 23 Jan 2019 03:00:28 -0500 Received: from mail.kernel.org ([198.145.29.99]:53550 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725973AbfAWIA2 (ORCPT ); Wed, 23 Jan 2019 03:00:28 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id B85D521019; Wed, 23 Jan 2019 08:00:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548230428; bh=BfJbx2cKGBYxo5GnVrlyCRc//7Rlr2l0SyAruRSkW64=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=WGyYBEVednfwsx2KtJa7OApk8Vg3+BIx+D4Cgk1rs4ENbkNIVfqQBPy5qz8jfYqcm E5B8gDHadshTXOvgdwWJTUxlusV9+ZTTsYCVJ2Va5ksd2yg//Ekkne8ES7eQpUmpp2 ceO6e9LUcfi1lbKJB+ceyNZdPlC1eEF+4RtIfT3Y= Date: Wed, 23 Jan 2019 09:00:25 +0100 From: Greg KH To: Ajay Kaher Cc: kys@microsoft.com, haiyangz@microsoft.com, jloeser@microsoft.com, sthemmin@microsoft.com, sashal@kernel.org, mikelley@microsoft.com, decui@microsoft.com, stable@vger.kernel.org, srivatsab@vmware.com, amakhalov@vmware.com Subject: Re: [PATCH 0/3] PCI: hv: Use vPCI protocol version 1.2 for v4.9 Message-ID: <20190123080025.GB7597@kroah.com> References: <1548257912-18273-1-git-send-email-akaher@vmware.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1548257912-18273-1-git-send-email-akaher@vmware.com> User-Agent: Mutt/1.11.2 (2019-01-07) Sender: stable-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Wed, Jan 23, 2019 at 09:08:29PM +0530, Ajay Kaher wrote: > For now, please consider these patches for review and > suggest if these can be merged to mainline kernel v4.9. > > These patches add support for vPCI protocol version 1.2, > by backpotring from v4.14 to v4.9. > Individual patches are summarised below: > > Patch 1: PCI: hv: Allocate physically contiguous hypercall params buffer > Backported as is. > > Patch 2: PCI: hv: Add vPCI version protocol negotiation > Backported as is. > > Patch 3: PCI: hv: Use vPCI protocol version 1.2 for v4.9 > Change: Because v4.9 doesn't have hv_tmp_cpu_nr_to_vp_nr(), > so original patch from v4.14 fails to apply on v4.9. > To solve this, using vmbus_cpu_number_to_vp_number() > instead of hv_tmp_cpu_nr_to_vp_nr() in this patch. > > drivers/pci/host/pci-hyperv.c | 387 +++++++++++++++++++++++++++++++++--------- > 1 file changed, 311 insertions(+), 76 deletions(-) > > -- > 2.7.4 > This is not the correct way to submit patches for inclusion in the stable kernel tree. Please read: https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html for how to do this properly.