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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0265BECAAD4 for ; Tue, 30 Aug 2022 21:42:21 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231547AbiH3VmV (ORCPT ); Tue, 30 Aug 2022 17:42:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43012 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230456AbiH3VmT (ORCPT ); Tue, 30 Aug 2022 17:42:19 -0400 Received: from mail-pl1-x62d.google.com (mail-pl1-x62d.google.com [IPv6:2607:f8b0:4864:20::62d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E56ED7D1DF for ; Tue, 30 Aug 2022 14:42:15 -0700 (PDT) Received: by mail-pl1-x62d.google.com with SMTP id d12so12360045plr.6 for ; Tue, 30 Aug 2022 14:42:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc; bh=3XqpzaqQIPLLyGi5qlAgQvhm1XAd7i62on0gjzVN0C0=; b=ar6AR/LJiMEdz55YDLufQJ3SK+VbOZr+1+ygsp7jTCPgahrZtANpZGSAWrK0j8oW2O HPW8Ptl5kt1nH68P0ZJqaETs5MU95uYWBJhnR6feye0basU1oqcjeGccAW4cuamX7Vbc hOnKZDpaJPurhUdok02WSfXdMqeQ9nKyeaFQuH1B0pjPw+5fllW/yYFRVmWNJNYttpUH /CcBeXKcrp6Ol09QNnUGgk8Du5bFnbl1su9uL5gskz3A6YhEECrAh43HruBf8sfbSp8V 5BnKj1iJD/+bxSrHd6jeBDrO27OBBuOoBGfBcu9jRouHWQqcdMWb0WaPveNuAVG0Bift ZI7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc; bh=3XqpzaqQIPLLyGi5qlAgQvhm1XAd7i62on0gjzVN0C0=; b=MwvtXXQa10fPaHJieqwYjASAal2myNLQix537aheZonG8IIHHwv25EorN1UVSXb/lg g4DJoFEHwvD1oOWJTBFehOAT/Z7bnAlwvhHLBrPK387CpHhwvUFmYfatZxCsTvqbOrIu 0xdiOq/m4NguidFs/FwRHIzHEtW/2H3v/imh1uMqfOK8arNMMcwUH1NBqYjxcozA51Vr +lQElfOdrshkqyimC8SNkUGmRjeS+P7EW/ZVJaGrAarcbwCteuoNAMQJovCT9GZz6WIU ck3XYO6l+cDjZQt/hwDJw7wr+puUNzmoBg6MLoxqrXs3ECPuugkK/nYf6FdMdlsGi4FK FA3Q== X-Gm-Message-State: ACgBeo0U3lPJAMu7W9MaqCnXwOfV/V+n1yKyXT7RLKWSqttqHhnlVQfY bypNmfc3SOH4K5rLKKqyEOI4zg== X-Google-Smtp-Source: AA6agR4vORPDKq/5w5NFBDKnl2wG/K63gRfZITOVeW2rgAZxnZ3bxwSzqUcDyBR92DYtTI4LoE3phQ== X-Received: by 2002:a17:90b:46c2:b0:1fd:7fe4:2217 with SMTP id jx2-20020a17090b46c200b001fd7fe42217mr43488pjb.146.1661895735212; Tue, 30 Aug 2022 14:42:15 -0700 (PDT) Received: from google.com (7.104.168.34.bc.googleusercontent.com. [34.168.104.7]) by smtp.gmail.com with ESMTPSA id d144-20020a621d96000000b00537a6c78ef1sm9776401pfd.190.2022.08.30.14.42.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 30 Aug 2022 14:42:14 -0700 (PDT) Date: Tue, 30 Aug 2022 21:42:10 +0000 From: Sean Christopherson To: Wonhyuk Yang Cc: Paolo Bonzini , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , x86@kernel.org, "H. Peter Anvin" , Baik Song An , Hong Yeon Kim , Taeung Song , linuxgeek@linuxgeek.io, kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] KVM: Add extra information in kvm_page_fault trace point Message-ID: References: <20220510071001.87169-1-vvghjk1234@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220510071001.87169-1-vvghjk1234@gmail.com> Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Tue, May 10, 2022, Wonhyuk Yang wrote: > Currently, kvm_page_fault trace point provide fault_address and error > code. However it is not enough to find which cpu and instruction > cause kvm_page_faults. So add vcpu id and instruction pointer in > kvm_page_fault trace point. > > Cc: Baik Song An > Cc: Hong Yeon Kim > Cc: Taeung Song > Cc: linuxgeek@linuxgeek.io > Signed-off-by: Wonhyuk Yang > --- Pushed to branch `for_paolo/6.1` at: https://github.com/sean-jc/linux.git Unless you hear otherwise, it will make its way to kvm/queue "soon". Note, the commit IDs are not guaranteed to be stable.