Received: by 10.223.176.5 with SMTP id f5csp2936002wra; Mon, 29 Jan 2018 06:29:01 -0800 (PST) X-Google-Smtp-Source: AH8x224imYnlfQQEg+6ZFyHVr8ZRDen0YK9y1L/l1lAYX55jDx03Hq4p6u94RijBduzC4HFGpeLy X-Received: by 10.101.71.130 with SMTP id e2mr21618040pgs.396.1517236141525; Mon, 29 Jan 2018 06:29:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517236141; cv=none; d=google.com; s=arc-20160816; b=DwcJXBfG6emXKd+SatNHfQXsFgyhTEtCeBLESZhOFhYL8yUf/CcxUBLV01DzX2WQK3 nR0BS0c7OWG5fw0nD7ynw0/+Fco3BdNt2iASGn0WKhvkdIb426KKwJ6GVghftrUtm7JZ rbIr24M8xiSdc37sYzOrVA00BRXVrVbYL9DBaEoFlbP5RBlHE1hxypvY9xOzjKB5Yw6o YYxMaG3a0RydWV07bkAHxur4o6Wnfluf5XnzWFm7pyHJtO2MJe3IwK3YpJ6nYWYAvrCY vJOQGH+BBQu85VK2VzGyPHhn2ODU4+U3W6Mh+j0PH4pDv6u+PyeM9qpCy5p67vK8d0Wq 60dA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature :arc-authentication-results; bh=OUTvKNMxTKv9P8Kgcas6UEau7vGUGgutvJHCgN8gGtQ=; b=zU2CHYpLwFgPNOiwk3qHJmj6pShxv1bt7C0FWVUEIk9YIUEzceIfi4FyT3hPmc7tdI mwrpGnAregERyts2jNV1573a6pdq9dWJAqEnjdTgDuMX0n8DfOiate1L8uxZU53fp5uo nnjIvBBx5j3TTRmE1F/t8jfu+e4OjwOpKkcGrE0S0W9/f/L+Il1XvrtceisttpoufCip i3EnSCpYFYnNu3yQxfqO1vUgGIUS05K33xwcTGg9zluUR/YBJifWtBaAAa1geTNkV1Be vhgfdBscfif9ktMB7y11xG/RERNyxdgiSTFgAxjzA9lZUJ2AKVHaTKHuAJnuhSGoOCe2 XnUQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=aM7ikW/0; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k71si7542029pge.131.2018.01.29.06.28.45; Mon, 29 Jan 2018 06:29:01 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=aM7ikW/0; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751803AbeA2O2R (ORCPT + 99 others); Mon, 29 Jan 2018 09:28:17 -0500 Received: from mail-wm0-f65.google.com ([74.125.82.65]:40673 "EHLO mail-wm0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751256AbeA2O2P (ORCPT ); Mon, 29 Jan 2018 09:28:15 -0500 Received: by mail-wm0-f65.google.com with SMTP id v123so34061449wmd.5; Mon, 29 Jan 2018 06:28:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=OUTvKNMxTKv9P8Kgcas6UEau7vGUGgutvJHCgN8gGtQ=; b=aM7ikW/0zOCrwRmsMWMk4Z6Fjb6HKEm7hW5/wt6yHG6g94xyrEL0Gg6cda5TLAFftE AQNkdPCNAaleg3L8f6AF+7yjzFMuQ7bwSc4RS65nZ8yDKbKb+A9/hOCTpUeW1mEHEz5w szZFSiEwJwV1x0ZxepAke+v8hYbXBKNt7IRVFZ0zsrMOuBbSTlS4l5vZunHBy4WuMWoP tKWz9RMnkQYVI+XnsX0FNPOGPFjYSKbCVBIues34dv6QhUgkMmOUdIsYBeaR/tM1PWhx bCzFYf+eD/5ftgGLap8ZahPl0Jg2maZE54E1HPwb53wXXPhNE0Q2G2ZLUfnNbCnXnbpm 78SA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=OUTvKNMxTKv9P8Kgcas6UEau7vGUGgutvJHCgN8gGtQ=; b=qI5b1YdkuK2tu3c85B5yhiGAuZemBCpwSUhG5CsBTNSRX6ELuiLC/QTfYxcCINFJ+a /6lUFb/Amviruo9pRmkj9cPYA8cRENWKNjxxY8MBdJlgMfL4PajHur1B54MYMtH7SjDj 4EW9okG+fAhK5rhP0JzSRHSg3m/SZrCUmoRUGn+kPKsIm4yJfn/5em4rXejAaLgcsdQQ 4giaB0ugPlup+fUch72DwuyDehzk9YVKTbV6GHyF+i7YVttEATEV0VoCJ29+5qq3IB5s lxha6axPR/TmQiT4GRlLHzlYTcN00EGyeWeslhjoOzZtp3M+5hGJQpHHGmpcVdQgsTBj maNQ== X-Gm-Message-State: AKwxyte7ExfSKa0nRt4OhazSjuwxLgv5r9nh+dWBpCaIFV6Gi6/za/64 9wBO9xP/vnNykGfDoLQEST4= X-Received: by 10.28.128.136 with SMTP id b130mr17294946wmd.68.1517236094532; Mon, 29 Jan 2018 06:28:14 -0800 (PST) Received: from [10.221.13.245] (smb-adpcdg1-06.hotspot.hub-one.net. [213.174.99.134]) by smtp.googlemail.com with ESMTPSA id r42sm5126010wrb.56.2018.01.29.06.28.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Jan 2018 06:28:13 -0800 (PST) Subject: Re: [PATCH v2 0/3] Per-VCPU MSR bitmaps patches - topic branch for x86/pti To: David Woodhouse , linux-kernel@vger.kernel.org, kvm@vger.kernel.org Cc: =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , KarimAllah Ahmed References: <1517043027-7655-1-git-send-email-pbonzini@redhat.com> <1517230431.18619.12.camel@infradead.org> From: Paolo Bonzini Message-ID: <8b7c9826-7327-9675-8e36-53d0ea5c0059@redhat.com> Date: Mon, 29 Jan 2018 15:28:11 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <1517230431.18619.12.camel@infradead.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 29/01/2018 13:53, David Woodhouse wrote: > Hm, we are pushing the other bits through tip/x86/pti, which is still > based on 4.14 so that everything can be backported easily. I was > expecting to be able to pull a clean 4.14-based tree Anything 4.14-based would have had conflicts all over due to the changes that have already gone in for tip/x86/pti. These three patches do cherry-pick cleanly on top of 4.14. If you give me the tree and commit id that you want me to use as a base, I can rebase and give you a new topic branch. Thanks, Paolo > which you had > *also* pulled into the latest kvm.git and resolved any merge issues... > but I just pulled a whole bunch of unrelated post-4.14 changes into my > working tree. > > How do you want to handle this?