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=-7.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 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 8611CC433DF for ; Thu, 28 May 2020 11:05:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 5EF84208DB for ; Thu, 28 May 2020 11:05:09 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="VeH6enC2" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388128AbgE1LFI (ORCPT ); Thu, 28 May 2020 07:05:08 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:40562 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2388045AbgE1LFF (ORCPT ); Thu, 28 May 2020 07:05:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1590663903; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Vz/KNQwtqPzPwwJ5/E8xlfolO32T1hV075nXyScUoSE=; b=VeH6enC26B3Ko3r6u0TN+QceYnguswzLVPDMHgH6jcpetRfqfZrw3ewEchamBMnH6Zcwb0 9TdsRmLH2KJvyIjuDtQT6rKBqPkkiK7ZLedomwE1Phf0ZwYv0l2q2E0Wu91Q1P2CaHWbJX uzGpYh6YzCkibVgUUDdLVlDzsePyT6M= Received: from mail-ej1-f72.google.com (mail-ej1-f72.google.com [209.85.218.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-451-s8nIGjpDP-qW12TYZUVXQA-1; Thu, 28 May 2020 07:05:00 -0400 X-MC-Unique: s8nIGjpDP-qW12TYZUVXQA-1 Received: by mail-ej1-f72.google.com with SMTP id i19so417756ejk.2 for ; Thu, 28 May 2020 04:05:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=Vz/KNQwtqPzPwwJ5/E8xlfolO32T1hV075nXyScUoSE=; b=Kwqg8cojwjzbgLSzHSGhthpaf0wvK9Lq5g4lYKEa7KRfIfxuJ+8Eqapf+xy5+JLG3I VTZuVYbMWUPV9SMAn/TyiBFvcbEhLCmPokuNXXQO0rjb0t502DTR0MdLIVNiP6UHDFWh +xvypl12tRalf5WB41uXo4M9TqTM1FFy6rVleBTUQVPj+I+AbYoMUbZTr/6pgykaBVT3 QNtHzounYW7nAV/w2qCcTTxF58HGo1qruzlBEDawX91C365fJV060jn3GJRjdCC4d42k ev/5e5bo0C4rjZWZA2bQn/0XH3wr1BCiq0TVwQMn7Rv8xjj4lGe3SuTKjY9xV4XoHR32 41jg== X-Gm-Message-State: AOAM532OcQlW3YMZBQnLouS/avoGOEQXzD2rhfPhsRYKnSJRiMRDlZSk bfFo3NS2YEfnurId/k3zneqiko/EPhFKkYMmbZTFglPZ4TFjbozKJTuGQjDwG+59Bp41VvRWo66 duybwzDJYh2BmZPLPJ1iaXANB X-Received: by 2002:a50:b2e1:: with SMTP id p88mr2514351edd.198.1590663899271; Thu, 28 May 2020 04:04:59 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzUxazYv/MMjFOoYXGoUSI8TzWHBa76vBlUwJk+N2FMgBjee032aatw377n1MJf50x2veTsRA== X-Received: by 2002:a50:b2e1:: with SMTP id p88mr2514320edd.198.1590663899011; Thu, 28 May 2020 04:04:59 -0700 (PDT) Received: from ?IPv6:2001:b07:6468:f312:3c1c:ffba:c624:29b8? ([2001:b07:6468:f312:3c1c:ffba:c624:29b8]) by smtp.gmail.com with ESMTPSA id g20sm5181115ejx.85.2020.05.28.04.04.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 28 May 2020 04:04:57 -0700 (PDT) Subject: Re: [PATCH v2 00/10] KVM: x86: Interrupt-based mechanism for async_pf 'page present' notifications To: Vitaly Kuznetsov , kvm@vger.kernel.org, x86@kernel.org Cc: Andy Lutomirski , Thomas Gleixner , Borislav Petkov , "H. Peter Anvin" , Wanpeng Li , Sean Christopherson , Jim Mattson , Vivek Goyal , Gavin Shan , Peter Zijlstra , linux-kernel@vger.kernel.org References: <20200525144125.143875-1-vkuznets@redhat.com> From: Paolo Bonzini Message-ID: <3be1df67-2e39-c7b7-b666-66cd4fe61406@redhat.com> Date: Thu, 28 May 2020 13:04:55 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <20200525144125.143875-1-vkuznets@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 25/05/20 16:41, Vitaly Kuznetsov wrote: > Concerns were expressed around (ab)using #PF for KVM's async_pf mechanism, > it seems that re-using #PF exception for a PV mechanism wasn't a great > idea after all. The Grand Plan is to switch to using e.g. #VE for 'page > not present' events and normal APIC interrupts for 'page ready' events. > This series does the later. > > Changes since v1: > - struct kvm_vcpu_pv_apf_data's fields renamed to 'flags' and 'token', > comments added [Vivek Goyal] > - 'type1/2' names for APF events dropped from everywhere [Vivek Goyal] > - kvm_arch_can_inject_async_page_present() renamed to > kvm_arch_can_dequeue_async_page_present [Vivek Goyal] > - 'KVM: x86: deprecate KVM_ASYNC_PF_SEND_ALWAYS' patch added. > > v1: https://lore.kernel.org/kvm/20200511164752.2158645-1-vkuznets@redhat.com/ > QEMU patches for testing: https://github.com/vittyvk/qemu.git (async_pf2_v2 branch) I'll do another round of review and queue patches 1-7; 8-9 will be queued later and separately due to the conflicts with the interrupt entry rework, but it's my job and you don't need to do anything else. Thanks, Paolo