From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pj1-f73.google.com (mail-pj1-f73.google.com [209.85.216.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 189DA31985D for ; Thu, 25 Jun 2026 18:37:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.216.73 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782412640; cv=none; b=MZjjqiWfyzbRh07RO2ExFct/pgju3wvN98LHsboe7GWaw753dGJCUSef0Ap1eAwnXzDwVsiIzFLLsWCNyUwPEi4EnDUUOo3rTFGPYTF1fOFgcbVVl6XvxbbsqrN4622KUIHYDocnSWkWvIZRZ1oICgw9tLtDboj7X+RRXwJ6Fac= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1782412640; c=relaxed/simple; bh=XGF2VYl68rxHrrb3+celOOH/NDrS3MYyMHWdfsQBzvU=; h=Date:In-Reply-To:Mime-Version:References:Message-ID:Subject:From: To:Cc:Content-Type; b=TLjiWuzRyWqTrTgQNIkMo6jaO10aMV2SE8Ct0NQMU9ozR8q6TbYmrqS+VjxXplk0IJBqJgVvkAFUAiuC8H3OoewOtkmrUIOqaN2IZBXdxnAMS/t9G3aWiU3No3j02PJV1phy02BEA2mwwMsi/paPCjKrqcisnfqy9R9XFz3+al8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com; spf=pass smtp.mailfrom=flex--seanjc.bounces.google.com; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b=X8aWhkmN; arc=none smtp.client-ip=209.85.216.73 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=flex--seanjc.bounces.google.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="X8aWhkmN" Received: by mail-pj1-f73.google.com with SMTP id 98e67ed59e1d1-37df0ae3ca8so78222a91.3 for ; Thu, 25 Jun 2026 11:37:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20251104; t=1782412638; x=1783017438; darn=vger.kernel.org; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=k1CLBFjHRtepPsR7OTGTpvVtcvQrDt/pUW+o4gNlp90=; b=X8aWhkmNeHj5B+S2ARCMB1eYjl8r4K4etZG/HFXM6FdnlaRlqdY4o98YfqE28CTDcR h/5o4uydtcCJZiCzbK9sKcrbpGEB+T9aiDdWY3gbAEdzDlZbZa/q2KSuRVZ+rLox9d3p G4TtUWznQjge07RTSOIla9Pcp/rxD06QJ6XKnXaUvB6LS0sDQD0KiwbF/nSfSJ/UctIs eiYqmaiFp2MeO9M8BJQa/JwucCl/DUMXIcHS7haA2iKr7vI3h4lbwnYwrAqjdla0TWWq ju4VtRWlsKfyNNN3B70xbms6qUr002QyNhVZPOSpZvIhg13Wsch+aShIcJyNNQcyyMMd Ol+A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1782412638; x=1783017438; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=k1CLBFjHRtepPsR7OTGTpvVtcvQrDt/pUW+o4gNlp90=; b=RIBb1neP0vhLWif1dh9ZN07kqz8yzf/fORTsK5ivQ6W+67B9XVCjN07IPSrnyn7fsf xfErr4frnucWmcj+hnBbol2SgJNNMyCHMRaBpEv6xtNdZT3TY7enQgd9UlPC2x+1Ct0I 9CJJTDX5Jjs0X9TYmdcNj9XKdzkSGywlxSG3zzGtzFVOC22+dM0j1cwasx5mjAX3RORV KivinzXciF2IDXCFRv/6rEFBt4cZearyxJrMCP83p4CmvR0OhHp+r3VM6h5LYttccCWx 5kYp8zKamhALP2bfk1OgrknUVg0U4rObDdGiLOuvWgkPOhW322phm23qoZ0iFS71UK2Y VC8g== X-Forwarded-Encrypted: i=1; AFNElJ+0q4SnnCCfgsX8qo2z9klm9ZxV65cxYjejGy9OrSHYC30fGZBoQPOsbi6a7ue7gWprOTpx2B5V29evKRg=@vger.kernel.org X-Gm-Message-State: AOJu0YwjBEnFa97Aeg284kq15oO/CguZ+V3YAWDvTU93TWSaWtwWaTH8 0aB4EMZTJR05B5zdf1YrSZitCBJuXgkJM9NCeBLRjKp1YejDAXdHlXbOU6r2f6GCsU0PPXgewT2 Fr9XyfQ== X-Received: from pgab3.prod.google.com ([2002:a63:3403:0:b0:c89:356d:606a]) (user=seanjc job=prod-delivery.src-stubby-dispatcher) by 2002:a05:6a21:6b04:b0:3b4:8aad:6337 with SMTP id adf61e73a8af0-3bd4ac80c24mr4406701637.15.1782412638064; Thu, 25 Jun 2026 11:37:18 -0700 (PDT) Date: Thu, 25 Jun 2026 11:37:17 -0700 In-Reply-To: <20260527-kvm-locking-docs-v1-0-4fe8b602ff47@google.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Mime-Version: 1.0 References: <20260527-kvm-locking-docs-v1-0-4fe8b602ff47@google.com> Message-ID: Subject: Re: [PATCH RFC 00/12] Document synchronization used in managing guest faults From: Sean Christopherson To: Ackerley Tng Cc: Paolo Bonzini , Jonathan Corbet , Shuah Khan , Tianrui Zhao , Bibo Mao , Huacai Chen , WANG Xuerui , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , Fuad Tabba , vannapurve@google.com, x86@kernel.org, "H. Peter Anvin" , kvm@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, loongarch@lists.linux.dev Content-Type: text/plain; charset="us-ascii" On Wed, May 27, 2026, Ackerley Tng wrote: > Ackerley Tng (12): > Documentation: KVM: Elaborate comment on kvm_usage_lock > Documentation: KVM: Consolidate notes about cpu_read_lock() and kvm_lock > Documentation: KVM: Consolidate notes about kvm->slots_lock and irq_lock > Documentation: KVM: Turn - into bullet point > Documentation: KVM: Explain what rule the exception section is meant for > Documentation: KVM: Have actual headings for exceptions > Documentation: KVM: Drop mention of kvm->lock in SRCU documentation > Documentation: KVM: Add example for kvm->srcu in relation to mutex/lock > Documentation: KVM: Document synchronization for managing guest faults > KVM: guest_memfd: Clarify comment about gmem.file vs kvm->srcu > KVM: mmu: Point users of host_pfn_mapping_level() to docs > Documentation: KVM: Focus acquisition order section on preventing deadlocks Please split these up into standalone patches or small series of patches that are logically related at a finer granularity. "Here's a pile of KVM documentation updates" is not a reasonable level of granularity.