Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp2350894ybt; Tue, 16 Jun 2020 03:55:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwvlq/m8XhQqeZor4ujmUsSgm9LMIm5p2GQDuKro8+t3Jq+9BfcverqJ8FQOPoPArsv4F74 X-Received: by 2002:a17:907:40c0:: with SMTP id nu24mr2300099ejb.141.1592304919006; Tue, 16 Jun 2020 03:55:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1592304919; cv=none; d=google.com; s=arc-20160816; b=pIab4LSYGohwN/k+PetvbdbWdP0eMUGdToUCS7raV/fxtZxlUpyHEVwsEDNkBLe13O 4j9HvQG8AcoM9/TSROxe1lWAUdO/bQDSXzLXQ+SrfVDFQJjVP+KNQS0LRSmtfLmGGAhV dmaQjgyz2oxPF4ile6tzd8rBhrSb8SfShd9/pxRVUXkseWJeRKGRruU5X48CjUutRBpp QflWi3L3d6syVtTOlZPrwxEFBC9T3l8jxvIa2mxZeqfsz/N0inHIFlUU5nb6sUh5FJ4Q BIhdnfCQ1jOyf5qiU6AGUpKqp1cj354g2ZbRjCC2P1KAfjbWOeJ4IcAHFBWo0PJ8lRok c75w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:dkim-signature; bh=9Vs0qBJGF5Skn7e+ab03WoozZDmoJ3wPcLfeh/kmlAk=; b=FwDI6u9RXurehQuGRo0cDjwwwUUvhAylI6lF3ufZSU4Pg7pDfjNti5ctnSmDV1r8Bl DGhkvqS+73eIc46epKf2hoRUNetJ0XRPMVRL9LypFoFNkRFcH8dxQaI3TIgANlrP4coa HUAdchPSUZHy5nq8ZxMreg+PumV9SvNm9MD5lMR/+3IYg2Nrvv7egZPHwDCEQttOe/kB p1V3Fy/8XfWZlJBRK40P6sWx+CfL/fMzNIoMJUi1j43aZiTY86Q8DGjTZ8DvLAHZXkkM WauNq8VCUbtFe8vaEISA65EpEk26Vy/29PlbcSpS5ebmsehTn8BEhpgbGi1nfQS+iHvW CQKQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=N36N90sz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dj11si4234681edb.333.2020.06.16.03.54.56; Tue, 16 Jun 2020 03:55:18 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=N36N90sz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728517AbgFPKuq (ORCPT + 99 others); Tue, 16 Jun 2020 06:50:46 -0400 Received: from us-smtp-1.mimecast.com ([205.139.110.61]:44916 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725775AbgFPKup (ORCPT ); Tue, 16 Jun 2020 06:50:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1592304644; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=9Vs0qBJGF5Skn7e+ab03WoozZDmoJ3wPcLfeh/kmlAk=; b=N36N90szDLVU3v0W0oDci0GxFYLKJTx7kfAvVSu1oBl2nBhZjWYmyFn8jwQAi8rC0ec95Y NycY4FiyI88PNJVJq6vqJxLs4DEIrpzrkNAFBNDv86VGBaOPjsg7FC4h/1LQ11lVZ9xBMk sWG5TzZFcWiRpgmE8ncd3eZiq4hwTIA= Received: from mail-ed1-f72.google.com (mail-ed1-f72.google.com [209.85.208.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-38-BX2c0wa9PM60QvBzNOiUhA-1; Tue, 16 Jun 2020 06:50:36 -0400 X-MC-Unique: BX2c0wa9PM60QvBzNOiUhA-1 Received: by mail-ed1-f72.google.com with SMTP id bs22so5997525edb.0 for ; Tue, 16 Jun 2020 03:50:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=9Vs0qBJGF5Skn7e+ab03WoozZDmoJ3wPcLfeh/kmlAk=; b=ZmKeG1L1bZ1mK7o41AcqaANExC4xyV8MzbIx/YbYbMX1tHabpfpdTPa3bHeMOK9prc cqbarfcAsz09Dfoq+rH761BdSbdKInGWc6JOOg8D14fMq3mYe8a0bUNosfuVsD/vNjrX ijQssRrE7GQF+3DvVB80fv63kw8fT5WenTppFMLZafg6qxO90iHdy6ZOThBar7NCcQKX /AlOrLH8bI7Byx/5Wo9qmJzHu60PuhMH3BGb8YCynYXX8h4cszb9AXANaRLK5qEyhuNc FcYF3z8uxgFLgUBr8+9ImE+7ex6F6yIClviQRwq3Olm/yDk3yPXQ2w2Ce8Xz4C8/GlWD aoXA== X-Gm-Message-State: AOAM5328/V0+CE3P5ZF7d/jW1T/cM6oqOBUIbfmmNWdTJOeqvNEbuK0G LdX+0yYGFDQMDBYhBUWugHE/Xla/eDHG4swK3i27VYOTfETeoSzvshBrKcezpR/Mset3zLsgkq3 8Uj8MwMntl/BhZq6eFL10QwUZ X-Received: by 2002:a17:906:8401:: with SMTP id n1mr2101716ejx.479.1592304635675; Tue, 16 Jun 2020 03:50:35 -0700 (PDT) X-Received: by 2002:a17:906:8401:: with SMTP id n1mr2101700ejx.479.1592304635422; Tue, 16 Jun 2020 03:50:35 -0700 (PDT) Received: from vitty.brq.redhat.com (g-server-2.ign.cz. [91.219.240.2]) by smtp.gmail.com with ESMTPSA id lx26sm10821467ejb.112.2020.06.16.03.50.34 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 16 Jun 2020 03:50:34 -0700 (PDT) From: Vitaly Kuznetsov To: Christoph Hellwig Cc: Dexuan Cui , Christoph Hellwig , Stephen Hemminger , Andy Lutomirski , Peter Zijlstra , Andy Lutomirski , Michael Kelley , Ju-Hyoung Lee , "x86\@kernel.org" , "linux-hyperv\@vger.kernel.org" , "linux-kernel\@vger.kernel.org" , KY Srinivasan Subject: Re: hv_hypercall_pg page permissios In-Reply-To: <20200616100810.GA28973@lst.de> References: <20200407073830.GA29279@lst.de> <87y2ooiv5k.fsf@vitty.brq.redhat.com> <87blljicjm.fsf@vitty.brq.redhat.com> <20200616093341.GA26400@lst.de> <20200616095549.GA27917@lst.de> <20200616100810.GA28973@lst.de> Date: Tue, 16 Jun 2020 12:50:33 +0200 Message-ID: <878sgni8sm.fsf@vitty.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Christoph Hellwig writes: > On Tue, Jun 16, 2020 at 11:55:49AM +0200, Christoph Hellwig wrote: >> Actually, what do you think of this one: > I see Peter has some concerns but if vmalloc_exec() used to work then open-coding it with the right flags should do. I've also tested your patch with Hyper-V, it works, so: Tested-by: Vitaly Kuznetsov > Plus this whole series to kill of vmalloc_exec entirely: > > http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/vmalloc_exec-fixes > FWIW, the vmalloc_exec() doing W+X allocation is misleading indeed, thus killing it makes perfect sense. -- Vitaly